Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • W Wiki Home
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards
Collapse sidebar
  • SDK4ED WikiSDK4ED Wiki
  • Wiki Home
  • Wiki
  • dependability toolbox usage

dependability toolbox usage · Changes

Page history
Update dependability toolbox usage authored May 07, 2020 by Miltos's avatar Miltos
Hide whitespace changes
Inline Side-by-side
dependability-toolbox-usage.md
View page @ b1e29659
...@@ -21,6 +21,24 @@ docker stop dependability-toolbox ...@@ -21,6 +21,24 @@ docker stop dependability-toolbox
## Invocation of the individual services (APIs) ## Invocation of the individual services (APIs)
After starting the Docker Container of the Dependability Toolbox back-end, its web services are up and running. The Dependability Toolbox is accessible through the following end point:
```
<local_IP>:<defined_port>/DependabilityToolbox
```
where the <local_IP> is the IP of the local machine on which the Dependability Toolbox Docker Container has been deployed, whereas the <defined_port> is the port of the Tomcat Server that is defined by the user during the installation (please see the [Installation](dependability-toolbox-installation) Wiki Page). In order to invoke one of the three available web services, the right resource (i.e., end point) should be used. The resources (i.e., end points) of the three web services of the Dependability Toolbox are listed below:
- **Quantitative Security Assessment**: /SecurityAssessment
- **Vulnerability Prediction**: /VulnerabilityPrediction
- **Optimum Checkpoint Interval Recommendation:** /OptimalCheckpoints
In the following, a more detailed description of how these services can be used is provided. Please use the following links to navigae more easily within the page:
- [Quantitative Security Assessment]()
- [Vulnerability Prediction]()
- [Optimum Checkpoint Interval Recommendation]()
### Quantitative Security Assessment Service ### Quantitative Security Assessment Service
The Quantitative Security Assessment web service allows the user to evaluate the internal security level of software applications written in Java, C, and C++ programming languages. This is achieved through a dedicated API exposed by the RESTful web server, which is, in fact, a simple HTTP GET request. Several inputs need to be provided as parameters to this request. These parameters are listed below: The Quantitative Security Assessment web service allows the user to evaluate the internal security level of software applications written in Java, C, and C++ programming languages. This is achieved through a dedicated API exposed by the RESTful web server, which is, in fact, a simple HTTP GET request. Several inputs need to be provided as parameters to this request. These parameters are listed below:
......
Clone repository
  • Advanced
  • Architectural Toolbox Description
  • Architectural Toolbox Front End
  • Architectural Toolbox Home
  • Architectural Toolbox Installation
  • Architectural Toolbox Usage
  • Decision Support Toolbox Description
  • Decision Support Toolbox Front end
  • Decision Support Toolbox Installation
  • Decision Support Toolbox Usage
  • Decision Support Toolbox
  • Energy Toolbox Description
  • Energy Toolbox Front end
  • Energy Toolbox Installation
  • Energy Toolbox Usage
View All Pages