Skip to content

📊 Diagram: Component Testing System Case Study

🔗 Link to Original Paper/Article

View Full Main Source

📝 Short Description

This diagram illustrates the first case study in the paper, which briefly describes a system focused on component testing. The diagram shows the flow of data between the different components in the system. The paper does not describe the structure of these systems as they belong to private companies. For this reason we took the liberty of adding some components to the very brief description that is given.

🔤 Abbreviations

  • UI: User Interface
  • I/O: Input/Output

📖 Extensive Description (if possible)

Starting from the left side of the diagram there is the Test Operator node, which sends its credentials to an Authorization Service and a test_request (request to test a component) to the Platform UI. From the Authorization Service an access token is generated (after the credentials of the operator have been checked) and sent to the Platform UI and View Measurements (at the right end of the diagram) nodes. From the Platform UI the test_request is forwarded to the Schedule Test for scheduling a test, and the selected component data (component) is sent to the Select Component node. This node then forwards it to the Run Test node, which in addition receives the simulation_data from the Simulator node. From the Run Test node test_data is generated and sent to the Real Time Processor. From here one the test_data is forwarded throughout various nodes (I/O and ECU) till it reaches the Component node, where the test_data is going to be tested physically. After testing it in the component, the measurements are sent to the Collect Measurements node. From here the measurements flow to the View Measurements and Store In The CLoud node. Measurements can be viewed by the operator with the previously access_token in the View Measurements node. Lastly from the Store In The Cloud node the measurements flow to the Private Cloud node where they are stored.

🏷️ Label description

  • 🗂️ Data Labels:

    • Data:

      • Credentials: Credentials data from the operator
      • TestRequest: Request from the operator to test a component
      • AccessToken: Access token generated after the credentials have been checked to do some operations
      • Component: Component which the test data will be tested on
      • SimulationData: Data from the simulatior
      • Measurements: Measurements from the testing of the component
      • TestData: Data from running the test
  • 🏷️ Node Labels:

    None

⚠️ Constraints

  • None

🚨 Violations

  • None