Rick Boldt, MathWorks
With Simulink Requirements™, perform requirements coverage analysis to assess the completeness of your architecture. Requirement changes resulting in suspect links are highlighted to support impact analysis.
With the requirements perspective you can analyze the impact a change in a requirement may have on the architecture and check that all the requirements have been implemented by the architecture.
Let’s change the Carrying Capacity requirement. Notice the requirement summary and the implemented by links are now highlighted indicating the requirement changed and may have an impact on the Airframe and Payload components.
The implemented by status bars indicates which requirements have not been implemented and gives a roll-up status in the requirements hierarchy.
In this case we can see that the default payload has not been implemented in our architecture. The payload capabilities hierarchy is also incomplete. By allocating the default payload requirement to the payload component we see that it is now implemented.
This is how you can do requirement coverage and impact analysis of your architecture.