1

SE LAB FILE

Submitted to

By
Hanut Singh
5CS2 (Y)
522
A2305208235
 1

INDEX
S.N PROGRAM DATE SIGN
O
1 UML

2 USE CASE DIAGRAM

3 REGISTRATION PROCESS

4 LIBRARY MANAGEMENT

5 STEREOTYPING

6 CLASS DIAGRAM

7 INHERITANCE

8 SINGLE INHERITANCE

9 MULTILEVEL INHERITANCE

10 HYBRID INHERITANCE

11 HEIRARCHICAL INHERITANCE

12 MULTIPLE INHERITANCE

13 STATE CHART DIAGRAM

14 ACTIVITY DIAGRAM

15 What is the difference between activity and state

diagram?

UML
 1

UML -:
Unified Markup Language used for specifying visualization, constructing and documenting the
artifacts of the software system

UML represents a collection of best engineering practices that have proven successful in
modeling of large complex system

UML uses graphical notation to express the design of software projects. UML helps project team
communicate, explore potential design and validate he architectural design of the software

Goals Of UML

 Manage project complexity

 Changes in the project can be made easily

 Provides users with a ready to use expressive visual modeling language so they can
develop and exchange meaningful models

Types of UML diagrams

 Use Case Diagram

 Class Diagram

 Object Diagram

 Activity Diagram

 State Machine Diagram

 Sequence Diagram

 Interaction Diagram

 Component Diagram

 Deployment Diagram
 1

USE CASE DIAGRAM

 Actor

 Use Case

Use Case Model captures requirements of a system, use cases are means of communicating with
user and other stake holders.

Two main components are

 Actor

 Use Case

Actor – A usecase diagram shows the interaction between the system and entities in the sytem
are referred to as actor. Actor represents the role which may include human users, external
hardware or other system

UseCase - It is a single unit of meaning full work

 1

REGISTRATION PROCESS

Amity University

Whenever a student enters another year, he has to get him/her re-registered. During this process a
student has to get affidavit, indemnity bond, fee receipt, registration form and registration fees.
The documents submitted are re verified by the faculty incharge and finally by the program
leader. Following use case diagram describes this process
 1

REGISTRATION PROCESS
 1

LIBRARY MANAGEMENT

The Library Management System is designed & developed for a receipt and issuance of books in
the library along with the student’s details. The books received in the library are entered in
Books Entry form and the new student is entered in the student entry form. When the student
wants to get the desired book the same is issued on the availability basis to the student. The
issuance and due date for the returning of the book is also entered into the Book Issue form under
third menu Book Issue. The student has to pay the fine if any on the basis of no. of days delayed
deposit of the book in the library.
 1

LIBRARY MANAGEMENT
 1

STEREOTYPING
 1

add book details m aintain database

delete book details

< < inc lude> >

m odify book details

book return < < inc lude> > return date

LIB R A RIA N
m is c ellaneous
< < inc lude> >

book is s ue

m aintain dis c ipline is s ue date

is s ue library c ards

< < inc lude> >

verific ation book return

< < inc lude> >

by nam e

book is s ue
< < ex tend> >
by s ubjec t

< < ex tend> >

read reference book s
s earc h book s

by publis her < < ex tend> > S TUDE N T

by author
 1

CLASS DIAGRAM
Classes are depicted as boxes with three sections, the top one indicates the name of the class, the
middle one lists the attributes of the class, and the third one lists the methods.

cars vehicles
name reg no
manyear model
kmsdone
speed()
getname() vehicleinfo()
getmanyear()

A basic class diagram

INHERITANCE
 1

In object-oriented programming (OOP), Inheritance is a way to compartmentalize and reuse code by

creating collections of attributes and behaviors called objects which can be based on previously created
objects. In classical inheritance where objects are defined by classes, classes can inherit other classes.
The new classes, known as Sub-classes (or derived classes), inherit attributes and behavior of the pre-
existing classes, which are referred to as Super-classes (or ancestor classes).

There are FIVE types of inheritance:

1) Single Inheritance
2) Multi Level Inheritance
3) Hierarchical Inheritance
4) Hybrid Inheritance

5) Multiple Inheritance

Single inheritance
 1

Multilevel inheritance
 1

salary
hra
basic

date()
overtime()

finance
transfer
tax management

issue()
dailysheet()

administration
account no
bank name

deposit()
withdraw()

Hybrid Inheritance
 1

hos pital
doc tors
patients
room s
s y nergy c a rd

void details ()

ic u ge neral ward
ventia lator fac ilities
no of beds
g etm edic als tatus ()
g etroom s ()

m edic al fac ility

m edic ines
nurs es s or h

opreq()
getm edic ines ()

Hierarchical Inheritance
 1

Multiple Inheritance
 1

vehicles
reg no
model

speed()
vehicleinfo()

cars
name bike
manyear name
kmsdone kms done

getname() getdetails()
getmanyear()

STATE CHART DIAGRAM

 1

State chart diagram is one of the five UML diagrams used to model dynamic nature of a system.
They define different states of an object during its lifetime. And these states are changed by
events. So State chart diagrams are useful to model reactive systems. Reactive systems can be
defined as a system that responds to external or internal events.

State chart diagram describes the flow of control from one state to another state. States are
defined as a condition in which an object exists and it changes when some event is triggered. So
the most important purpose of State chart diagram is to model life time of an object from
creation to termination.

State chart diagrams are also used for forward and reverse engineering of a system. But the main
purpose is to model reactive system.

Following are the main purposes of using State chart diagrams:

• To model dynamic aspect of a system.

• To model life time of a reactive system.
• To describe different states of an object during its life time.
• Define a state machine to model states of an object.
 1

State diagram of State diagram of

A computer A mobile
 1

ACTIVITY DIAGRAM

Activity diagram is another important diagram in UML to describe dynamic aspects of the
system.

Activity diagram is basically a flow chart to represent the flow form one activity to another
activity. The activity can be described as an operation of the system.

So the control flow is drawn from one operation to another. This flow can be sequential,
branched or concurrent. Activity diagrams deals with all type of flow control by using different
elements like fork, join etc.

Purpose:

The basic purposes of activity diagrams are similar to other four diagrams. It captures the
dynamic behaviour of the system. Other four diagrams are used to show the message flow from
one object to another but activity diagram is used to show message flow from one activity to
another.
 1

no button
pressed

press up / down button

if up button pressed
on top floor or down
button pressed in
basement
door open
floor not
present

floor button not

pressed

press button

floor button
pressed

close door

move to
floor

Activity diagram of a lift

 1

What is the difference between activity and state diagram?

State diagram shows the object undergoing a process. It gives a clear picture of the changes in
the object's state in this process.
e.g: ATM withdraw
Card object state: Checking, Approving, Rejecting

Activity diagram is a fancy flow chart which shows the flow of activity of a process.
e.g: ATM withdraw
Withdraw activity: Insert Card, Enter PIN, Check balance, with draw money, get card
 1

Software
Engineer
ing
Lab
File
Submitted by:
1

Navjot kaur
5CS2(Y)
A2305208210