Learn about Innoslate's compliance with numerous SysML diagrams
Introduction
Systems Modeling Language (SysML) plays an integral role in Systems Engineering, and Innoslate seamlessly incorporates SysML models and constructs into its software platform. While Innoslate mainly utilizes the Lifecycle Modeling Language (LML), it accomodates users familiar with SysML, encompassing all its essential artifacts and model types. This integration allows for smooth transitions between modeling languages, empowering users to choose the most suitable option(s) for their projects.
By embracing SysML, Innoslate ensures the efficient creation and management of complex models, providing a robust solution for system modeling and design. Innoslate supports all 12 SysML Diagrams, including Activity Diagram, Block Definition Diagram (BDD), Parametric Diagram, Internal Block Diagram (IBD), Package Diagram, Requirements Diagram, Sequence Diagram, State Machine Diagram, and Use Case Diagram.
* To follow along and try out the features mentioned, click here to download the AV SysML Project .INNO File and import it into a new Innoslate project.
Walkthrough Use Case
This walkthrough introduces three primary SysML modeling techniques, all accessible across all Innoslate environments. The aim is to showcase how Innoslate supports users who have to favor SysML and are looking to shift to a web-based cloud platform to meet their requirements more effectively.
The article will cover the following widely used SysML diagrams:
Block Definition Diagram
The Block Definition Diagram (BDD) in Innoslate provides a high-level overview of the system’s structure, highlighting its components, their properties, constraints, operations, and interrelationships. This diagram is crucial for understanding the overall architecture of the system while displaying its properties in sections of each block.
The figure below shows the Autonomous Vehicle (AV) System and provides a high-level overview of the system's structure, illustrating the primary subsystems, their properties, and the relationships between them. At the top of the hierarchy is the Autonomous Vehicle System, which is decomposed into several key subsystems.
To detail some of the decomposing lower-level blocks in the hierarchy:
- Vehicle Control System includes values such as acceleration (ft/s²), braking force (lbf), and cruise/max speed (mph), with constraints equations like the maximum speed limit. Including Sensor Data Input, Route Input, and Control Input ports.
- The Navigation System handles values such as Accuracy (ft), Route planning (ft), and Updates Frequency (Hz), with Operations to Calculate Optimal Routes(). Supported by GPS Data Input, Traffic Data Input, and Route Output Ports.
- Adaptive Perception System manages values including camera frame rate (fps), camera resolution (pixels), radar range (ft), sensor fusion latency (ms), and ultrasonic sensor frequency (kHz) and range (ft). Operates under the maintaining sensor fusion latency < 100 ms constraint. The key operation is ProcessSensorData(), with ports for Sensor Data Input and Processed Data Output.
- Communication System handles values such as internal network latency (ms) and V2X communication range (miles). It is constrained by maintaining internal network latency ≤ 10 ms to ensure rapid data transfer within the system. The system’s operation Establish V2X Connection(), supported by ports for External Data I/O and Internal Data Output.
- Human-Machine Interface includes values such as control interface response time (ms), user display resolution (pixels), and user display size (inches). The key operation is to Update User Display() to refresh information presented to the user. The HMI is equipped with ports for User Command Input.
- Safety System includes values such as collision avoidance response time (ms), emergency response time (ms), and health monitoring check interval (minute). Constrained by the need to maintain emergency response times ≤ 500 ms. The main operation is to Activate Emergency Protocols() to handle emergencies, with an emergency control output port.
This BDD effectively captures the intricate details and interdependencies within the AV system, offering a clear and organized representation of the overall system structure.
Internal Block Diagram
The Internal Block Diagram (IBD) in Innoslate provides a detailed view of the structure of the Autonomous Vehicle (AV) System, highlighting the interactions and data flows between its block components. This diagram is essential for understanding how different subsystems communicate and collaborate through their ports to achieve the overall system functionality.
In the IBD, connection lines create relationships between the blocks, showing how data and control signals flow between subsystems. Ports marked with small arrows indicate the direction of data flow: arrows pointing inward represent input ports, arrows pointing outward represent output ports, and arrows pointing both ways indicate bidirectional (Input/Output) ports.
There are countless examples of interactions and relationships created in the diagram. To mention a few, the IBD showcases the Vehicle Control System receiving route data from the Navigation System and processed data output from the Adaptive Perception System, which are crucial for real-time vehicle control. Additionally, the Communication System is responsible for both internal and external data exchanges, enabling the system to stay updated with current traffic conditions and external communications. The Safety System responds to emergencies promptly through its connection to the Vehicle Control System control outputs.
Overall, the IBD contributes significantly by providing a clear and organized representation of the system’s internal structure, highlighting the critical connections that facilitate the efficient and safe functioning of the AV System.
Activity Diagram
The Activity Diagram in Innoslate plays a critical role in illustrating the operational behavior of a system, allowing users to navigate through the diagram with simulation capabilities to gain a deeper understanding of the process. These diagrams are particularly useful in visualizing the sequence of actions, decision points, concurrent processes and inputs and output flows within the system, providing a comprehensive view of how different components interact to perform a specific function or achieve a particular goal.
For the Autonomous Vehicle (AV) System, Activity Diagrams offer valuable insights into the step-by-step processes involved in tasks such as project planning, analysis and design, prototype development, and testing the prototype.
The figure below details the lower-level decomposition of "WBS.2 Build AV Prototype", showing how modelers can decompose their activity diagrams further to create detailed activity diagrams. Notably, the Activity Diagram uses a decision node that verifies the built system constructs on the prototype, enabling a verification system before moving into assembling the prototype. Meaning if there are missing elements, the diagram reworks its system elements, and loops as long as there are still missing elements. Once the system verifies all elements are appropriately constructed, the diagram moves into assembly.
As for all action entities on Innoslate, these activity nodes include attributes for Number, Name, Description, Start, Duration, % Complete, Due Date, Finish, Status, and Assignee, along with cost relationships to be incurred. It should be mentioned that users can manually create their custom attributes and utilize additional elements to their liking.
Note: Import the provided .INNO files into your projects for additional decompositions and examples.
The final part of our Activity Diagram analysis involves examining the simulation results, which provide critical insights into the time and cost efficiency of the Autonomous Vehicle (AV) System development process. Using Innoslate's Discrete Event Simulator, we were able to model and analyze the durations and interactions of all the entities involved in the project.
The simulation results dashboard displays various metrics, including:
- Total Time: The entire project is estimated to take approximately 1.73 years. This duration encompasses all phases, from AV Project Management to the final testing of the AV prototype.
- Action Trace 3D: The visual trace of the model is shown in a 3D model in the simulation dashboard that allows users to interact with the action diagram nodes, makeup, and its detailed construction.
- Gantt Chart: The Gantt chart provides a detailed timeline breakdown for each task, showing dependencies, the sequential flow of activities, and simulation start/finish times.
- Tree Map: This visual represents the duration of each task, highlighting the most time-consuming activities, such as the “WBS.3 Test AV Prototype,” which is expected to take 6.33 months.
The simulation results offer several key takeaways for the AV System project, providing significant insights into time management, resource allocation, project efficiency, and decision-making. With a total project duration of 1.73 years, project managers can effectively allocate resources and schedule tasks, identifying critical path activities and potential bottlenecks, such as the lengthy testing phase, using the Gantt chart and tree map. Overall, the simulation results from the Activity Diagram provide a comprehensive overview of the project timeline and critical activities, offering invaluable insights for planning, managing, and optimizing the development process of the Autonomous Vehicle System to ensure efficient and effective completion of all necessary steps.
Conclusion
Innoslate is a versatile tool that empowers users to create SysML diagrams and collaborate seamlessly with various model types. Its user-friendly interface and robust features empower users to design, analyze, and simulate complex systems efficiently, enabling informed decision-making and project optimization. Users can rely on Innoslate for developing SysML diagrams to streamline workflow and improve system development processes.