Professional Documents
Culture Documents
BCS
BCS
BCS
BCS
BCS
BCS
BCS
Actor
User, External devices, External systems can will be
represented as Actor.
Actor interact with system by send / receive messages from/to
system
BCS
Use case
Each use case represents what the system does (system
functionality)
Represented using an ovals.
Place Order
BCS
10
Associations
A relationship between an actor and a use case in which an
interaction occurs between them.
Modeled as a solid line connecting the actor and the use case
Maybe bidirectional or unidirectional
BCS
11
2)Extends
Shows optional behavior of a use case.
3)Generalization
Child use cases inherits.
BCS
12
BCS
13
BCS
14
BCS
15
2 - Class Diagrams
The purpose of the class diagram is to model the static view of
an application.
The class diagram is a static diagram. It represents the static
view of an application. It is also known as a structural
diagram.
The class diagram describes the attributes and operations of a
class.
The class diagrams are the only diagrams which can be
directly mapped with object oriented languages and thus
widely used at the time of construction.
BCS
16
A class
Represents a kind of person, place, or thing about which the system must
capture and store information.
An attribute
Represents properties that describe the state of an object.
A method
Represents the actions or functions that a class can perform.
An association
Represents a relationship between multiple classes, or a class and itself.
Cardinality/Multiplicity
Its refers to one object can communicate with how many objects of
another class
BCS
17
Class Notation
Class notation will have 3 parts.
1)Class name
BCS
18
BCS
19
BCS
One
1..*
One or many
Many
1.. N
One or N objects
20
BCS
21
BCS
22
BCS
23
Object Diagram
Object diagrams are derived from class diagrams so object
diagrams are dependent upon class diagrams.
Object diagrams represent an instance of a class diagram.
The basic concepts are similar for class diagrams and
object diagrams.
Object diagrams also represent the static view of a system
but this static view is a snapshot of the system at a
particular moment.
Object diagrams are used to render a set of objects and
their relationships as an instance.
BCS
24
BCS
25
BCS
26
Component Diagrams
It does not describe the functionality of the system but it
describes the components used to make those
functionalities.
component diagrams are used to visualize the physical
components (libraries, packages, files etc. ) in a system &
relationships among these components.
Component diagrams can also be described as a static
implementation view of a system.
A single component diagram cannot represent the entire
system but a collection of diagrams are used to represent
the whole.
Deployment Diagrams
Deployment diagrams are used for describing the hardware
components where software components are deployed.
Component diagrams and deployment diagrams are closely
related.
Component diagrams are used to describe the components
and deployment diagrams shows how they are deployed in
hardware.
But these two diagrams are special diagrams used to focus on
software components and hardware components.
Deployment diagram includes Nodes and the Relationship
among Nodes
Sequence Diagrams
The purposes of diagrams are to visualize the interactive
behavior of the system and to capture the different aspects of
the interaction.
The sequence diagram captures the time sequence of
message flow from one object to another .
So the following things are to identified clearly before drawing
the interaction diagram:
Objects taking part in the interaction.
Message flows among the objects.
The sequence in which the messages are flowing.
Object organization.
Diagram 1
1. The medical receptionist triggers the View Info method in an
instance P of the PatientInfo object class, supplying the patients
identifier, PID. P is a user interface object, which is displayed as a
form showing patient information.
2. The instance P calls the database to return the information
required, supplying the receptionists identifier to allow security
checking (at this stage, we do not care where this UID comes from).
3. The database checks with an authorization system that the user
is authorized for this action.
4. If authorized, the patient information is returned and a form on
the users screen is filled in. If authorization fails, then an error
message is returned.
Diagram 2
1. The receptionist logs on to the PRS.
2. There are two options available. These allow the direct transfer of
updated
patient information to the PRS and the transfer of summary health data
from the MHC-PMS to the PRS.
3. In each case, the receptionists permissions are checked using the
authorization system.
4. Personal information may be transferred directly from the user
interface object to the PRS. Alternatively, a summary record may be
created from the database and that record is then transferred.
5. On completion of the transfer, the PRS issues a status message and
the user
logs off.
PMS:DataB
ase
Collaboration Diagram
It shows the object organization as shown below. In
collaboration diagram the method call sequence is
indicated by some numbering.
The number indicates how the methods are called one
after another.
The method calls are similar to that of a sequence diagram.
But the difference is that the sequence diagram does not
describe the object organization where as the collaboration
diagram shows the object organization.
If the time sequence is important then sequence diagram is
used and if organization is required then collaboration
diagram is used.
Activity Diagram