UML Diagram

UML is Unified Modelling Language which is used in object oriented programming.

Besides being used in software engineering , it also can be used in application structure,
behaviour and business process.UML are divided into 14 diagram type and these 14 diagram
are divided into two group that is structural diagram and behavioural diagram.

Structure diagrams purpose are to show the things being modelled while
behavioural diagrams is to show what would happen in system.

Case Diagram
Case diagram gives a graphic overview of the actor involved in a system,
different functions needed by those actors and how those difference function
interact.
By using Case diagram you could easily identify the main actor involved and the
main processes of the system.
Case diagram consist of :
Actor : a person, organization or external system that play a role in
1 or more interaction in your system,actor to usually are drawn as
stick figures.
Use cases. A use case describes a sequence of actions that provide
something of measurable value to an actor and is drawn as a
horizontal ellipse.
Associations : Associations between actors and use cases are
indicated in use case diagrams by solid lines. An association exists
whenever an actor is involved with an interaction described by a
use case. Associations are modeled as lines connecting use cases
and actors to one another, with an optional arrowhead on one end
of the line. The arrowhead is often used to indicating the direction of
the initial invocation of the relationship or to indicate the primary
actor within the use case. The arrowheads are typically confused
with data flow and as a result I avoid their use.
System boundary boxes (optional): a rectangle drawn around
the use cases. They are called the system boundary box, to
indicates the scope of your system. Anything within the box
represents functionality that is in scope and anything outside the
box is not. System boundary boxes are rarely used, although on
occasion they are used them to identify which use cases will be
delivered in each major release of a system.

Packages (optional) : Packages are UML constructs that enable

you to organize model elements (such as use cases) into groups.
Packages are depicted as file folders and can be used on any of the
UML diagrams, including both use case diagrams and class
diagrams

System boundary boxes

Association
s

Several more examples of use case diagram:

1) Software Protection and Licensing

Purpose: Use case diagram example shows some
simplified view of software licensing use cases
supported by Sentinel EMS Application.

2)Hospital Management
Purpose: Describe major services (functionality)
provided by a hospital's reception.

3)Restaurant business model

Purpose: Two alternative examples of business use case
diagram for a Restaurant - external and internal business
views of a restaurant.

Sequence Diagram

Sequence diagrams shows how object interact with each other and the order
those interactions occur. Its important to note that they show the interactions
for a particular scenario

The diagrams is also used to show how exactly the business presently works by
illustrating how the different business objects interact

sequence diagrams could also be utilized to document how objects in an existing

system currently interacts.

The basic of sequence diagram are :

Lifeline: Lifelines are representative of roles or object instances

that partake in the sequence being modelled.Lifeline are place at
the top of the diagram and it is shown as box with dashed line
descending from the center of the bottom edge.

Message: The message that is being sent to the receiving object

represents an operation/method that the receiving objects class
implements.

Guards: Guards are conditions that need to be used throughout

UML diagram to control flow. Guard can only be assigned to a single
message and to use guard you must laced the guard element above
the message line being guarded and in front of the message name.

Lifeline

Guards

Message

Several examples of sequence diagram:

1)Online bookshop UML sequence diagram

Purpose: An example of high level UML sequence
diagram for Online Bookshop.

2)Facebook user authentication in a web application

Purpose: To shows how Facebook user could be authenticated in
a web application to allow access to his/her Facebook resources.

Class Diagram
Class diagram is a type of static structure diagram that describe the structure of a
system
It shows the classes in a system, attributes and operations of each class and the relationship
between each class.
In large systems with many related classes, classes are grouped together to create
class diagrams. Different relationships between classes are shown by different types of
arrows.
Arrows in class diagram:

Association: A relationship between the members of two classifiers.

Aggregation: An association representing a shared ownership

relationship. The Aggregation property of the owner role is set
to Shared.

Composition: An association representing a whole-part relationship.

The Aggregation property of the owner role is set to Composite.

Generalization: The specific classifier inherits part of its definition from

the general classifier. The general classifier is at the arrow end of the

connector. Attributes, associations, and operations are inherited by the

specific classifier. Use the Inheritance tool to create a generalization
between two classifiers.

Import: A relationship between packages, indicating that one package

includes all the definitions of another.

Dependency: The definition or implementation of the dependent

classifier might change if the classifier at the arrowhead end is changed.

Realization(15): The class implements the operations and attributes

defined by the interface. Use the Inheritance tool to create a realization
between a class and an interface.

Realization(16): An alternative presentation of the same relationship.

The label on the lollipop symbol identifies the interface.

No

Element

Association

5a

Aggregation

5b

Composition

Generalization

13

Import

14

Dependency

15

Realization

16

Realization

Several examples of class

diagram:

1)Library domain model

Purpose: Describe domain area for an Integrated
Library System (ILS), also known as a Library
Management System (LMS) - Library, Catalog,
Book, Patron, Account.

2)Online shopping domain model

Purpose: Show some domain model for online
shopping - Customer, Account, Shopping Cart,
Product, Order, Payment.