Principles of Software Engineering
,Task 1
1.1 Use case diagram
Figure 1
The diagram describes a summary, but the volume of the explanation is held, as text, in
documents related with the use cases. These use case explanations present the entire story of
the use case. In every use case model, there are a proper explanation how does the actors and
the system collaborate to achieve the aim signified by the use case. (Spence, 2003).
Extend relationship
An extended relationship provides a use-case to be expanded with some additional curricula.
If a use case has the same actions with another, this is useful.
2
, Figure 1: Extend relationship
Include relationship
Include relationship allowing a use case to gain the classification of a group of activities in a
different use case. This is a good way to capture and describe typical habits that are
controlled through multiple cases of use.
Figure 2: Include relationship
The definition of use case includes characters and use cases. Actors are modelled frameworks
of processes, and use cases form the framework. Actors are objects which communicate with
the device for destination. Usage cases are the tools and functionalities used by the actors.
Usage cases would meet actor specifications. The diagram of the use case describes the
preferences of external objects for the system and specific features of the system. The
diagram does not, however, apply to the programme implementation details.
3
,Task 1
1.1 Use case diagram
Figure 1
The diagram describes a summary, but the volume of the explanation is held, as text, in
documents related with the use cases. These use case explanations present the entire story of
the use case. In every use case model, there are a proper explanation how does the actors and
the system collaborate to achieve the aim signified by the use case. (Spence, 2003).
Extend relationship
An extended relationship provides a use-case to be expanded with some additional curricula.
If a use case has the same actions with another, this is useful.
2
, Figure 1: Extend relationship
Include relationship
Include relationship allowing a use case to gain the classification of a group of activities in a
different use case. This is a good way to capture and describe typical habits that are
controlled through multiple cases of use.
Figure 2: Include relationship
The definition of use case includes characters and use cases. Actors are modelled frameworks
of processes, and use cases form the framework. Actors are objects which communicate with
the device for destination. Usage cases are the tools and functionalities used by the actors.
Usage cases would meet actor specifications. The diagram of the use case describes the
preferences of external objects for the system and specific features of the system. The
diagram does not, however, apply to the programme implementation details.
3
