A language proposition for system requirements

Foundations for model‐based systems engineering and model‐based safety assessment

“…They can also “execute” models, ie, perform simulations, but this requires formalizing notations so to give them an executable semantics. It is also possible to trace impacts of changes in requirements on state machines describing the lifecycle of the system or on diagrams representing its functional architecture . In any case, these processing tools should be designed from a syntactic point of view as opposed to a semantic point of view, ie, by considering models as structures in which it is possible to navigate and on which some structural operations can be performed, but without interpreting these structures (ie, without assigning them any meaning).…”

“…S2ML was used there both to describe the system architecture (this model has been co‐designed with the scenarios) and as a mean to structure scenarios. The second PhD thesis was on the agile development of corpuses of requirements . The idea was to apply on requirements the syntactic approach discussed Section 2.2 and to elicit them while designing S2ML models of the system architecture (and of course to link the syntactic structures of requirements with these models).…”