SOFTWARE ENGINEERING LAB

BACHELORS OF TECHNOLOGY IN COMPUTER

SCIENCE AND ENGINEERING

Amity of School of Engineering & Technology

Amity University

UNDER THE GUIDANCE OF: Ms. SHWETA BHARDWAJ

SUBMITTED BY:

SHRADHA SINGH
A2305216308
BTECH 5 CSE 5 X
2016-2020
ASET,AUUP
 INDEX
S. Categor Code Exp. Name of experiment Date of Date of Max. Mark Sign.
No y of exp. No. allotm Evaluan Mark s Of
. ent of s Obt. faculty
exp.
1. Mandat LR 1 IntroductionTo UML. 1
2. o-ry (10) CLASS DIAGRAM
2 1
Exp. To design an Class
Diagram for Hoapital
Management System.

3. 3 USE CASE DIAGRAM 1

To design a Use Case
Diagram for Library
Management System.

4. 4 STATE DIAGRAM 1
To design an State Chart
Diagram for ATM.
5. 5 OBJECT DIAGRAM 1
To design an Object
Diagram for Railway
Management System.
6. 6 ACTVITY DIAGRAM 1
To design an Activity
Diagram for ATM
7. 7 SEQUENCE DIAGRAM 1
To design an Sequence
Diagram for Library
Management System.
8. 8 COLLABORATION 1
DIAGRAM
To design an
Collaboration Diagram
for Library Management
System..

9. 9 COMPONENT 1
DIAGRAM
To design an Object
Diagram for ATM
Management System
10. 10 DEPLOYMENT 1
DIAGRAM
To design an Object
Diagram for libraray
Management System.

11. Design PR 10
Based (10)
Open
Ended
experim
ent
12. Viva Viva 5
(5)
 EXPERIMENT – 1

Name: Shradha Singh

Enrollment no: A2305216308
Date:

1. OBJECTIVE: Introduction To UML.

2. EQUIPMENT/SOFTWARE USED:

S.No. Hardware Software

1. I7 Processor Rational Rose
2. 16GB RAM Microsoft Word
3. Keyboard
4. Mouse
5. Monitor
6. Printer

3. THEORY:

UML stands for Unified Modeling Language. The Unified Modeling

Language is a standard visual modeling language intended to be used for

 modeling business and similar processes,

 analysis, design, and implementation of software-based systems

UML is a common language for business analysts, software architects and

developers used to describe, specify, design, and document existing or new
business processes, structure and behavior of artifacts of software systems. It is
a standard language for specifying, visualizing, constructing, and documenting
the artifacts of software systems.
UML is different from the other common programming languages like C++,
Java, COBOL etc. It is a pictorial language used to make software blue prints.

UML is a standard modeling language, not a software development process. It

explained that process:

 provides guidance as to the order of a team’s activities,

 specifies what artifacts should be developed,
 directs the tasks of individual developers and the team as a whole, and
 offers criteria for monitoring and measuring a project’s products and
activities.
 UML is intentionally process independent and could be applied in the context
of different processes. Still, it is most suitable for use case driven, iterative and
incremental development processes.

So UML can be described as a general purpose visual modelling language to visualize,

specify, construct and document software system. Although UML is generally used to
model software systems but it is not limited within this boundary. It is also used to
model non software systems as well like process flow in a manufacturing unit etc.

UML is not a programming language but tools can be used to generate code in various
languages using UML diagrams. UML has a direct relation with object oriented
analysis and design. After some standardization UML is become an OMG (Object
Management Group) standard.

Faculty Name: Ms. Shweta Bhardwaj

Signature:
Date:
 EXPERIMENT – 2

Name: Shradha Singh

Enrollment no: A2305216308
Date:

1. OBJECTIVE:To create a class diagram for Hospital Management System in UML.

2. EQUIPMENT/SOFTWARE USED:

S.No. Hardware Software

1. I7 Processor Rational Rose
2. 16GB RAM Microsoft Word
3. Keyboard
4. Mouse
5. Monitor
6. Printer

3. THEORY:

The class diagram is a static diagram. It represents the static view of an application.
Class diagram is not only used for visualizing, describing and documenting different
aspects of a system but also for constructing executable code of the software application.

The class diagram describes the attributes and operations of a class and also the
constraints imposed on the system. The class diagrams are widely used in the modelling
of object oriented systems because they are the only UML diagrams which can be mapped
directly with object oriented languages.

The class diagram shows a collection of classes, interfaces, associations, collaborations

and constraints. It is also known as a structural diagram.

The purpose of the class diagram is to model the static view of an application. 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.

The UML diagrams like activity diagram, sequence diagram can only give the
sequence flow of the application but class diagram is a bit different. So it is the most
popular UML diagram in the coder community.

So the purpose of the class diagram can be summarized as:

 Analysis and design of the static view of an application.

 Describe responsibilities of a system.

 Base for component and deployment diagrams.

 Forward and reverse engineering.

4. OUTPUT:

Faculty Name: Ms. Shweta Bhardwaj

Signature:
Date:
 EXPERIMENT – 3

Name: Shradha Singh

Enrollment no: A2305216308
Date:

1. OBJECTIVE:To create a use case diagram for Library Management System in UML.

2. EQUIPMENT/SOFTWARE USED:

S.No. Hardware Software

1. I7 Processor Rational Rose
2. 16GB RAM Microsoft Word
3. Keyboard
4. Mouse
5. Monitor
6. Printer
3. THEORY:

A use case diagram is a behaviourial diagram, which aims to present a graphical overview of
the functionalities provided by the system. The diagram is used to model the
system/subsystem of an application. A single use case diagram captures a particular
functionality of a system. Use case diagrams are used to gather the requirements of a system
including internal and external influences. These requirements are mostly design
requirements. So when a system is analyzed to gather its functionalities use cases are
prepared and actors are identified.
the purposes of use case diagrams can be as follows:

 Used to gather requirements of a system.

 Used to get an outside view of a system.

 Identify external and internal factors influencing the system.

 Show the interacting among the requirements are actors.

Use case diagrams consists of actors, use cases and their relationships.

Actor - An actor can be defined as an object or set of objects, external to the system, but
interacts directly with the system to get some meaningful work done. Actors could be human,
devices, or even other systems.

Actors can be classified as below :

Primary actor: Primary actors fulfil their goal by using some service from the system.
Supporting actor: They provide some service to the system.

In a use case diagram primary actors are usually drawn on the top left side of the diagram.

Use case -A use case can be defined as a functionality that a system can provide by
interacting with the actor(s).Use cases include both successful and unsuccessful scenarios of
user interactions with the system. For example, authentication of a customer by the ATM
would fail if he enters wrong PIN. In such case, an error message is displayed on the screen
of the ATM.

Association between Actors and Use Cases - A use case describes a specific functionality
that the system provides to its users. The functionality is triggered by actor. Actors are
connected to use cases through binary associations. The association indicates that the actor
and use case communicates through message passing. An actor must be associated with at
least one use case. Similarly, a given use case must be associated with at least one actor.
However, when a use case is associated with multiple actors, it might not be clear who
triggers the functionality. No association among the actors are shown.

4. OUTPUT:

check book availability

enquiry

issue book
librarian student

verify members
registered members

return book

calculating fine

maintaining book

Faculty Name: Ms. Shweta Bhardwaj

Signature:
Date:
 EXPERIMENT – 4

Name: Shradha Singh

Enrollment no: A2305216308
Date:

1. OBJECTIVE:To create a use state diagram for ATM management system in UML.

2. EQUIPMENT/SOFTWARE USED:

S.No. Hardware Software

1. I7 Processor Rational Rose
2. 16GB RAM Microsoft Word
3. Keyboard
4. Mouse
5. Monitor
6. Printer
3. THEORY:

State 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 diagrams are useful to model reactive
systems. Reactive systems can be defined as a system that responds to external or
internal events.

State 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 diagram is to model life
time of an object from creation to termination.

State 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 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.

State diagram defines the states of a component and these state changes are dynamic in
nature. So its specific purpose is to define state changes triggered by events. Events are
internal or external factors influencing the system.

State diagrams are used to model states and also events operating on the system. When
implementing a system it is very important to clarify different states of an object during its
life time and state diagrams are used for this purpose. When these states and events are
identified they are used to model it and these models are used during implementation of the
system.

4. OUTPUT:

reading card not readable

card

card read sucessfully

reading pin cancel pressed

pin read sucessfully

choosing cancel pressed

transaction

customer wants to do another

transaction choosen

performing
transaction

customer finished

ejecting
card
abort due to too many invalid pin
card retained

Faculty Name: Ms. Shweta Bhardwaj

Signature:
Date:
 EXPERIMENT – 5

Name: Shradha Singh

Enrollment no: A2305216308
Date:

1. OBJECTIVE:To create a use object diagram for railway management system in UML.

2. EQUIPMENT/SOFTWARE USED:

S.No. Hardware Software

1. I7 Processor Rational Rose
2. 16GB RAM Microsoft Word
3. Keyboard
4. Mouse
5. Monitor
6. Printer
3. THEORY:

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.

The difference is that a class diagram represents an abstract model consisting of classes and their
relationships. But an object diagram represents an instance at a particular moment which is concrete
in nature. It means the object diagram is more close to the actual system behaviour. The purpose is to
capture the static view of a system at a particular moment.

So the purpose of the object diagram can be summarized as:

 Forward and reverse engineering.

 Object relationships of a system

 Static view of an interaction.

 Understand object behaviour and their relationship from practical perspective

Object diagrams can be imagined as the snapshot of a running system at a particular moment.

In a brief, object diagrams are used for:

 Making the prototype of a system.

  Reverse engineering.

 Modeling complex data structures.

 Understanding the system from practical perspective.

4. OUTPUT:

home page

Check
availability

modify
cancel
form
ticket

book ticket

fill form

Faculty Name: Ms. Shweta Bhardwaj

Signature:
Date:
 EXPERIMENT – 6

Name: Shradha Singh

Enrollment no: A2305216308
Date:

1. OBJECTIVE: To create a use activity diagram for ATM in UML.

2. EQUIPMENT/SOFTWARE USED:

S.No. Hardware Software

1. I7 Processor Rational Rose
2. 16GB RAM Microsoft Word
3. Keyboard
4. Mouse
5. Monitor
6. Printer
3. THEORY:
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.

It captures the dynamic behaviour of the system. Activity diagram is used to show message flow from
one activity to another.Activity is a particular operation of the system. Activity diagrams are not only
used for visualizing dynamic nature of a system but they are also used to construct the executable
system by using forward and reverse engineering technique.

So the purposes can be described as:

 Draw the activity flow of a system.

 Describe the sequence from one activity to another.

 Describe the parallel, branched and concurrent flow of the system

The activity diagram is suitable for modeling the activity flow of the system. An application
can have multiple systems. Activity diagram also captures these systems and describes flow
from one system to another. This specific usage is not available in other diagrams. These
systems can be database, external queues or any other system.
This diagram is used to model the activities which are nothing but business requirements. So
the diagram has more impact on business understanding rather implementation details.

Following are the main usages of activity diagram:

 Modelling work flow by using activities.

 Modelling business requirements.

 High level understanding of the system's functionalities.

 Investigate business requirements at a later stage.

Action states
Action states represent the non-interruptible actions of objects.

Action Flow
Action flow arrows illustrate the relationships among action states.

Object Flow
Object flow refers to the creation and modification of objects by activities. An object flow
arrow from an action to an object means that the action creates or influences the object. An
object flow arrow from an object to an action indicates that the action state uses the object.

Initial State
A filled circle followed by an arrow represents the initial action state.

Final State
An arrow pointing to a filled circle nested inside another circle represents the final action
state.

Branching
A diamond represents a decision with alternate paths. The outgoing alternates should be
labeled with a condition or guard expression. You can also label one of the paths "else."

4. OUTPUT:
Faculty Name: Ms. Shweta Bhardwaj
Signature:
Date:
 EXPERIMENT – 7

Name: Shradha Singh

Enrollment no: A2305216308
Date:

1. OBJECTIVE: To create a use sequence diagram for library management system in UML.

2. EQUIPMENT/SOFTWARE USED:

S.No. Hardware Software

1. I7 Processor Rational Rose
2. 16GB RAM Microsoft Word
3. Keyboard
4. Mouse
5. Monitor
6. Printer
3. THEORY:
UML sequence diagrams are used to show how objects interact in a given situation. An
important characteristic of a sequence diagram is that time passes from top to bottom : the
interaction starts near the top of the diagram and ends at the bottom (i.e. Lower equals Later).

A popular use for them is to document the dynamics in an object-oriented system. For each
key collaboration, diagrams are created that show how objects interact in various
representative scenarios for that collaboration.

Sequence diagrams describe interactions among classes in terms of an exchange of messages

over time.
Class roles
Class roles describe the way an object will behave in context. Use the UML object symbol to
illustrate class roles, but don't list object attributes.

Activation box and messages

Activation boxes represent the time an object needs to complete a task.
Messages are arrows that represent communication between objects. Use half-arrowed lines
to represent asynchronous messages. Asynchronous messages are sent from an object that
will not wait for a response from the receiver before continuing its tasks.
Lifelines
Lifelines are vertical dashed lines that indicate the object's presence over time.

4. OUTPUT:

Faculty Name: Ms. Shweta Bhardwaj

Signature:
Date
 EXPERIMENT – 8

Name: Shradha Singh

Enrollment no: A2305216308
Date:

1. OBJECTIVE:To create a collaboration diagram for elevator system in UML.

2. EQUIPMENT/SOFTWARE USED:

S.No. Hardware Software

1. I7 Processor Rational Rose
2. 16GB RAM Microsoft Word
3. Keyboard
4. Mouse
5. Monitor
6. Printer

3. THEORY:

A collaboration diagram, also called a communication diagram or interaction diagram, is an

illustration of the relationships and interactions among software objects in the Unified
Modelling Language (UML). The concept is more than a decade old although it has been
refined as modelling paradigms have evolved.

A collaboration diagram resembles a flowchart that portrays the roles, functionality and
behaviour of individual objects as well as the overall operation of the system in real time.
Objects are shown as rectangles with naming labels inside. These labels are preceded by
colons and may be underlined. The relationships between the objects are shown as lines
connecting the rectangles. The messages between objects are shown as arrows connecting the
relevant rectangles along with labels that define the message sequencing.

Collaboration diagrams are best suited to the portrayal of simple interactions among
relatively small numbers of objects. As the number of objects and messages grows, a
collaboration diagram can become difficult to read.

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.
Now to choose between these two diagrams the main emphasis is given on the type of
requirement. If the time sequence is important then sequence diagram is used and if
organization is required then collaboration diagram is used.

In a brief the following are the usages of interaction diagrams:

 To model flow of control by time sequence.

 To model flow of control by structural organizations.

 For forward engineering.

 For reverse engineering.

4. OUTPUT:

Faculty Name: Ms. Shweta Bhardwaj

Signature:
Date:
 EXPERIMENT – 9

Name: Shradha Singh

Enrollment no: A2305216308
Date:

1. OBJECTIVE: To create a component diagram for online shopping system in UML.

2. EQUIPMENT/SOFTWARE USED:

S.No. Hardware Software

1. I7 Processor Rational Rose
2. 16GB RAM Microsoft Word
3. Keyboard
4. Mouse
5. Monitor
6. Printer

3. THEORY:

Component diagrams are used to model physical aspects of a system. Physical aspects are the
elements like executables, libraries, files, documents etc which resides in a node. So
component diagrams are used to visualize the organization and relationships among
components in a system. These diagrams are also used to make executable systems.

It does not describe the functionality of the system but it describes the components used to
make those functionalities.

So from that point component diagrams are used to visualize the physical components in a
system. These components are libraries, packages, files etc.

Component diagrams can also be described as a static implementation view of a system.

Static implementation represents the organization of the components at a particular moment.

A single component diagram cannot represent the entire system but a collection of diagrams
are used to represent the whole.

So the purpose of the component diagram can be summarized as:

 Visualize the components of a system.

 Construct executables by using forward and reverse engineering.

  Describe the organization and relationships of the components.

4. OUTPUT:

Faculty Name: Ms. Shweta Bhardwaj

Signature:
Date:
 EXPERIMENT – 10

Name: Shradha Singh

Enrollment no: A2305216308
Date:

1. OBJECTIVE: To create a deployment diagram for online reading system in UML.

2. EQUIPMENT/SOFTWARE USED:

S.No. Hardware Software

1. I7 Processor Rational Rose
2. 16GB RAM Microsoft Word
3. Keyboard
4. Mouse
5. Monitor
6. Printer

3. THEORY:

A deployment diagram in the Unified Modelling Language models the physical deployment of
artifacts on nodes.

To describe a web site, for example, a deployment diagram would show what hardware components
("nodes") exist (e.g., a web server, an application server, and a database server), what software
components ("artifacts") run on each node (e.g., web application, database), and how the different
pieces are connected (e.g. JDBC, REST, RMI).

The nodes appear as boxes, and the artifacts allocated to each node appear as rectangles within the
boxes. Nodes may have sub-nodes, which appear as nested boxes. A single node in a deployment
diagram may conceptually represent multiple physical nodes, such as a cluster of database servers.

There are two types of Nodes:

a) Device Node

b) Execution Environment Node

Device nodes are physical computing resources with processing memory and services to execute
software, such as typical computers or mobile phones. An execution environment node (EEN) is a
software computing resource that runs within an outer node and which itself provides a service to host
and execute otherexecutable software elements.
4. OUTPUT:

Faculty Name: Ms. Shweta Bhardwaj

Signature:
Date: