Library Management System123

8/4/2019 Library Management System123

1/29


2/29

OBJECT DIAGRAM

CLASS DIAGRAM

USE CASE DIAGRAM

SEQUENCE DIAGRAM

COLLABORATION DIAGRAM

ACTIVITY DIAGRAM

COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM


3/29

Object diagram shows a snapshot of instancesof things in class diagrams. Similar to class diagrams,object diagrams show the static design of system butfrom the real or prototypical perspective.

Object diagrams are also closely linked to classdiagrams. Just as an object is an instance of a class, anobject diagram could be viewed as an instance of a class

diagram. Object diagrams describe the static structure ofa system at a particular time and they are used to test theaccuracy of class diagrams.


4/29

NOTATIONS DESCRIPTION

Each object is represented as a rectangle,

which contains the name of the object and

its class underlined and separated by acolon.

Links are instances of associations. You can

draw a link using the lines used in classdiagrams.


5/29


6/29

Class Diagram providesan overview of thetarget system by describing the objects and classesinside the system and the relationships betweenthem. It provides a wide variety of usages; from

modelling the domain-specific data structure todetailed design of the target system. With the sharemodel facilities, you can reuse your class model inthe interaction diagram for modelling the detailed

design of the dynamic behaviour.


7/29


A class is a classifier that has object as its

instance. A class provide the template from

which objects are created. It also defines itsattributes & operations.

An association specifies a relationship that

appear between two classifiers.


8/29


9/29

Use case diagrams model thefunctionality of a system using actors and use cases.Use cases are services or functions provided by thesystem to its users.


10/29


Actorrepresents any one or any thing that

interacts with the system.

Use Cases represent the functionality

provided by the system.

In Include / Uses relationship, a use caseincludes a functionality describes in

another use case as a part of its business

process flow.


11/29


12/29

Sequence diagrams describeinteractions among classes in terms of anexchange of messages over time.

Sequence Diagram models thecollaboration of objects based on a time sequence.It shows how the objects interact with others in aparticular scenario of a use case.


13/29


Sequence diagram represents an

interaction between objects that focuses

on the message broadcast chronology. Anobject is represented by a rectangle & a

vertical bar called the objects lifeline

Objects communicates by exchangingmessages, represented by horizontal

arrows drawn from the message sender to

the message recipient.


14/29


An activation corresponds to the time

during which an object performs an action.

Activation are represented by rectangularstripes positioned along lifelines. The

beginning & the end of a stripe correspond

respectively to the beginning & the end of

an activation.

A note (comment) gives the ability to

attach various remarks to elements. It may

contain information that is useful to a

modeller.


15/29


16/29

A collaboration diagram describesinteractions among objects in terms of sequencedmessages. Collaboration diagrams represent acombination of information taken from class,sequence, and use case diagrams describing boththe static structure and dynamic behaviour of asystem.


17/29


Class roles describe how objects behave.

Sequence diagram number the message inorder of execution. Sequence number for

indication of the time order of message.

We can prefix the message with a number

(starting with the messages numbered 1),increasing for each new message in the

flow of control(2,3,4 and so on).


18/29


19/29

TheActivity Diagram can help to describethe flow of control of the target system, such as the

exploring complex business rules and operations,describing the use case also the business process.


20/29


Activity states represent the non-

interruptible actions of objects. You can

draw an action state using a rectangle with

rounded corners.

A filled circle followed by an arrow

represents the initial action state.

A synchronization bar helps illustrate

parallel transitions. Synchronization is also

called forking and joining.


21/29


Action flow arrows illustrate the

relationships among action states.

An arrow pointing to a filled circle nested

inside another circle represents the final

action state.

In Branching, a diamond represents a

decision with alternate paths. The outgoing

alternates should be labelled with a

condition or guard expression.


22/29


23/29

The Component Diagram helps tomodel the physical aspect of an Object-Orientedsoftware system. It illustrates the architectures of

the software components and the dependenciesbetween them. Those software componentsincluding run-time components, executablecomponents also the source code components.


24/29


A componentis a physical building block of

the system. It is represented as a rectangle

with tabs.

A dependencyis a relationship that signifies

that a single or a set of model elements

requires other model elements for theirspecification or implementation.


25/29


26/29

The Deployment Diagram also helpsto model the physical aspect of an Object-Oriented software system. It models the run-time

configuration in a static view and visualizes thedistribution of components in an application. Inmost cases, it involves modelling the hardwareconfigurations together with the softwarecomponents that lived on.


27/29


A processor is a physical resource that

executes code components.

Association refers to a physical connection

between nodes, such as Ethernet.


28/29


29/29

Documents

Library Management System123