UML
The static structure defines the kinds of the objects important to a system and to its implementation as well as relationship among the objects. The dynamic behaviour defines history of the objects
UML diagrams
Structural View Behavioral View
Sequence Diagram Collaboration Diagram State-chart Diagram
Class Diagram
Object Diagram
Activity Diagram
Implementation View
Component Diagram
Sequence diagrams
Collaboration diagrams
Activity diagrams
10
11
12
2. Secondary Actors
People that perform administration or maintenance tasks.
The others systems with which the system must interact.
3. Other systems:
13
14
Use-case diagrams
Use-case diagrams present a high-level view of
system usage as viewed from an outsiders (actors) perspective. These diagrams show the functionality of a system or a class and how the system interacts with the outside
world.
Use-case diagrams can be used during analysis to capture the system requirements and to understand how the system should work.
15
Use-case diagrams
During the design phase, use-case diagrams specify the behavior of the system as implemented. Rose automatically creates a Main use-case diagram in the use-case view.
16
Types of Use-case
1.Including Use Cases:
Use cases may contain the functionality of another use case as part of their normal processing. In general it is assumed that any included use case will be called every time the basic path is run.
An example of this is to have the execution of the use case <Card Identification> to be run as part of a use case <Withdraw>.
17
Use Cases may be included by one or more Use Case, helping to reduce the level of duplication of functionality by factoring out common behavior into Use Cases that are re-used many times.
18
another;
this is typically used in exceptional circumstances.
19
20
Use-case Diagram
21
Example:
22
23
24
Ticketing Book
Passenger
Extension
Ticket Booking with Concession
Specialization
Journey and Tariff Special conditions
26
UseCase
courseAvailability
Actor
Student makeClassSelection uses checkConflicts
uses
verifyPrereqs
confirmEnrollment Registrar
27
Figure 1.9: Use Case diagram for an Automated Teller Machine (ATM) system
28
In this example, the bank's customer initiates a number of use cases: Withdraw Money, Deposit Funds, Transfer Funds, Make Payment, View Balance, and Change PIN. A few of the relationships are worthy of further mention.
The bank officer can also initiate the Change PIN use case. The Make Payment use case shows an arrow going to the credit system.
29
30
31