Please enable JavaScript.
Coggle requires JavaScript to display documents.
Model-Based Requirements Documentation (Use Cases (diagrams| (show the…
Model-Based Requirements
Documentation
Documents
three types of requirements
Goals describe intentions of stakeholders or groups of stakeholders
Use cases and scenarios
Scenarios are grouped together in use cases
System requirements
detailed functions and qualities that the system to be developed shall implement or possess
Model
A model is an abstract representation of an existing reality or a reality to be created
Mapping of reality
can be descriptive
the resulting model documents the existing reality
can be prescriptive
the resulting model serves as a prototype for a fictitious reality
Reduction of reality:
Pragmatic property
A model is always constructed for a special purpose and within a special context.
Requirements Models
Conceptual models that document the requirements of a system
Advantages
Increased understandability
information can be perceived and memorized faster and better graphically
Support perspectives of documentation.
have a strictly
defined focus
Use Cases
To document the functionalities of a planned or existing system on the basis of simple models
diagrams|
show the system’s relevant functions from a user’s perspective
specific relationships between the functions of the system or
between functions of the system and aspects in the system’s context
specifications
templates for textual specification
of use cases
Goal Models
GOALS
are a stakeholder’s description of a characteristic property of the system to be developed or the development project
very well suited to refine the vision of the system
goal decomposition
AND/OR trees
AND-decomposition
every sub-goal must be fulfilled so that the super-goal (the root) is
fulfilled.
OR-decomposition
at least one subgoal
is fulfilled so that the super-goal is met