Requirements modeling is a crucial part of the systems engineering process. In essence, it serves as a bridge between stakeholders’ needs and the final system implementation. By utilizing well-defined terms and concepts from system modeling, requirements modeling ensures clarity, consistency, and completeness. This article delves into the foundational terms and concepts relevant to requirements modeling. Therefore it highlights their relationships and significance in creating effective models.
Using the general terms and concepts found in systems modeling, the following explanation looks at the terms and concepts relevant for modeling requirements. Further it looks at the important relationships between the various terms and concepts.
A graphical approach
The following shows a semantic network of the basic terms and concepts relevant for requirements modeling. You can find the graphic in the CPRE Advanced Level Requirements Modeling – Handbook (opens a new tab). Moreover the Certified Professional Requirements Engineer Advanced Level Requirements Modeling certificate is part of the curriculum of the International Requirements Engineering Board (IREB).
Modeling language
A model is a abstracting image of the properties of a system. To make the scope and complexity of the modeling manageable, diagrams and supplementary textual model elements represent various views of the system. Further they include its its environment and the properties of the system in relation to each specific view. Each diagram bases on a specific diagram type and a modeling language (more precisely by syntax, semantics, and pragmatics). The underlying modeling language of a diagram type defines the set of modeling constructs that applies to construct the corresponding diagrams (e.g., class and association for the construction of class diagrams).
In a modeling language, graphical and/or textual notations are defined for the modeling constructs. A diagram consists of a set of model elements. Each element represents a specific graphical modeling construct of the modeling language, i.e. of the specific diagram type. Examples for diagram types are e.g. class: “person”, association: “is employed by”, class: “company”.
Textual model elements (e.g., textual description of the trigger of a use case) supplement diagrams and graphical model elements which express specific textual modeling constructs (e.g., a section of a use case template). The graphical and textual model elements form the atomic constituents of models.
In essence, a requirements model is a specific type of model (more precisely: a type of system model). It is used to specify the requirements of a system with the aid of diagrams and textual supplements.
Conclusion
In conclusion, understanding the terms and concepts in requirements modeling is essential for creating accurate and effective system models. By leveraging the definitions and relationships outlined in the IREB Glossary (opens in new tab) and supplementing them with additional essential terms, requirements modeling becomes a more structured and manageable process. This approach not only aids in maintaining consistency and clarity. It also enhances communication among stakeholders, ultimately contributing to the successful development of a system.
This text is based on content from the source: International Requirements Engineering Board (ireb.org). The International Requirements Engineering Board is the owner of the copyright.
| Read more about Confluence and How to Use shortcuts in Confluence Assign a task in Confluence Create a Confluence space from a template Delete a Page in Confluence Create a Confluence page |