4System Requirements Engineering

4.1. Case study

To continue, we discuss here the following process of requirements engineering from the same case study from the subject proposed in the RobAFIS™ 2018 competition [ROB 18]. After defining the needs of stakeholders in the previous chapter from the point of view of the project owner (RobAFIS organization), we will now carry out the analysis of the requirements from the point of view of the system architects (the team participating in the competition).

For the rest of this chapter, we will assume the role of a team of students participating in the competition. The first task of this team is to conduct an analysis of the system requirements that must be met by the system it is to develop.

4.1.1. Structure of the SysML project

As before, we use the CAMEO Systems Modeler software tool [CAM 20], but again, in the case of choosing another modeling tool, the principles we will discuss are transferable.

To structure the project, we are again using the SysML concept of Package. A new package is created for the system requirements engineering activity as well as a sub-package for stakeholder needs and always in accordance with ISO 29110, a sub-package for the system requirements analysis task and a package to ensure traceability of requirements. Figure 4.1 shows the structure that is obtained; it can be seen that the needs are present in another sub-package which contains the SysML requirements. As before, the stereotypes that are adapted ...

Get System Requirements Engineering now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.