Please enable JavaScript.
Coggle requires JavaScript to display documents.
Use Case (Include: (Model: (Postcondition: (Precondition: (A constraint…
Use Case
Include:
In UML, a relationship from a base use case to an included use case specifying how the behavior defined for the included use case can be inserted into the behavior defined for the base use case.
Model:
A semantically closed abstraction of a system or a complete description of a system from a particular perspective. Examples include use case, architecture, and domain models and code.
-
Scenario:
A description of a specific sequence of actions. In use case sce
narios, specific persons or actor instances replace actors, and only one path is taken through the use case’s possible basic and alternate flows. Also called use case instance.
Requirement:
A condition or capability to which a system must conform. Requirements are either derived from user needs or stated in a contract, standard, specification, or other formally imposed document.
relationship:
A semantic connection between model elements. Examples include associations, dependencies, and generalizations. Relationships to use cases include association, extend, and include.
-
Alternate flow
The part of a use case that describes its alternative implementations. Its also used to describe error conditions, since errors can be considered a kind of alternative. Also called alternate path.
Basic flow
Describe its most common implementation. The basic fkow is writen assuming that no errors or alternatives exist. Also called basic path pr happy day scenario.
Constraint:
A semantic condition or restriction that describes a limitation or state. For example, a constraint might be a limitation on some data’s range of values or on some behavior of the application, or it could be a description of a required state of the system at a particular point in time.
Extend:
In UML, a relationship from an extending use case to a base use case specifying how the behavior defined for the extending use case can be optionally inserted into the behavior defined for the base use case.
Association:
: In UML, a relationship between an actor and a use case that indicates that the actor interacts with the system by means of the use case.
Actor
In UML, someone or something outside the system that interacts with the syste