2.7. Realizing Use Cases

We have identified and modeled the requirements to the system in the previous steps in Sections 2.2 through 2.5. That’s the area we generally call “analysis.” We now dedicate ourselves to the design of the system. This means that we describe structures and behaviors that realize the requirements we identified and determined in the analysis.[17]

[17] Note that the transition from the analysis to the design is flowing. This is the reason why there are often discussions about the exact delimitation of the two terms that lead to no result. In fact, we already took solutions, such as the card reader, into account in the analysis.

We now have to deal with the issue of how the results from the analysis should be transferred into ...

Get Systems Engineering with SysML/UML now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.