Think of the complexity of your development process like a family. It starts with the simple life of the child: You define, in your development process, what the expected outcome is.
In the main part, parents take over the process and manage the relationships between the 4 complex areas, calculate the risks, e.g. with FMEA/TARA, FTA, HARA and perform virtual analysis to find the best way for their child – your product.
- This is also a shift in complexity that is being driven into hardware and software.
- The complexity of policiesis the continual increase in requirements, e.g., security and cybersecurity concerns, create a huge volume of documents and data under ever-evolving policies.
- The consequences are increased complexity of system elements and increased complexity of sub-systems of systems embedded in their networked environment.
In the end, we come to the grandparents who doubt the process and cite the performance of a test as evidence.
A project can involve hundreds or thousands of people, all of whom need an overview, understand the system architecture, and deal with various change requests. How are you going to manage the family – the big complexity?
At this point, MBSE helps your organization to one view for each member, when a change occurs, engineers are able to adapt their work faster.