From the Syndeia dashboard, we will take our Jama requirements hierarchy, shown on the right side, and drag and drop it into our SysML model shown on the left side. We’re going to do this with Syndeia as shown in Figure 2. We want to bring all or some of the requirements hierarchy into the SysML model in a way in which, if the requirement changes later, either on the Jama or on the SysML side, we will be able to recognize the changes and reconcile the two versions so that model unity and consistency is maintained.įigure 2 Syndeia Model Transform of system requirements from Jama Connect to MagicDraw SysML Flash chain of custody, for example, talks about maintaining chain of custody of the flash memory cards used to transmit ballots or votes.
MBSE MAGICDRAW SERIES
A common pattern here is that requirements are managed in a specialized requirements management tool like Jama Connect and brought into the SysML model, either en masse or selectively, as part of the development process, so that we can relate those requirements to other aspects of the system.įigure 1 EVS Requirements in Jama ConnectĪ screenshot of the web interface to the Jama Connect repository where we have created a whole series of requirements is shown in Figure 1. Having established the system domain and high-level objectives of our Electronic Voting System (EVS) in Part 1, the typical next step in systems engineering is requirements process in which we generate the requirements that the system must meet.
0 kommentar(er)
