lOMoARcPSD|25857742

Software Engineering Practical File of 6th sem

b.tech (GL Bajaj Institute of Technology and Management)

Studocu is not sponsored or endorsed by any college or university

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)
 lOMoARcPSD|25857742

SOFTWARE ENGINEERING LAB

KCS-651

Submitted By: Debid Yadav & Hemant Singh Submitted To: Ms. Chitvan Gupta
Section: B Roll number: 1901920100089
1901920100147

Department of Computer Science &

Engineering
GL Bajaj Institute of Technology and
Management Greater Noida – 201306
Downloaded by Aditya Kushwaha (tannut8202@gmail.com)
 lOMoARcPSD|25857742

List of
Experiments

S.No. Name of Experiment Signature

1 Prepare a SRS document in line with the IEEE
recommended standards
2 Draw the use case diagram and specify the role
of each of the actors. Also state the precondition,
post condition and function of each use case.
3 Draw Level-0 and Level-1 Data Flow Diagram
4 Draw Sequence Diagram
5 Draw Activity diagram
6 Draw the class diagram
7 Draw the collaboration diagram
8 Draw state chart diagram

9 Draw component diagram

10 Draw deployment diagram
11 Draw ER diagram

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)

 lOMoARcPSD|25857742

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)

 lOMoARcPSD|25857742

Experiment – 1

Aim: Prepare a SRS document in line with the IEEE standards.

Purpose: The purpose of railway reservation system is to create reservation, cancel Reservation
, Viewing Train information, Viewing Reservation Details, Updating Train information, Updating
Reservation details, and generate reports.

Document Conventions: This Document was created based on the IEEE template for System
Requirement Specification documents.

Intended Audience and Reading Suggestions:

The different types of readers are:
 Customers
 Developers
 Management
 Passengers
 Counter Clerk

Product Scope:
The extent of this system in making Reservation is that, from any Railway Station we can create
Reservation, which is refreshed naturally in all the stations. Subsequently, there is no perplexity
In the mind of the Reservation Clerk in all the stations to make the Reservation. This can be
Conceivable by keeping up the Global Database, Representatives present at various stations can
Get to the worldwide information database and the clients can without much of an effort or stretch
Can easily be able reservation seats. It provides various options and diversity to the customer as
well as more time to book tickets.

Scope:
The extent of venture characterizes the undertaking achievability the innovation, account,
Time and assets best characterize in innovation whether the imperfections can be
Decreased in the task and up which level monetarily, climate the general venture cost
Is moderate. Time portrays whether the projection completing point will be accomplish
On schedule or before time assets required should be accessible at the pace of cost and
Time.

OVERALL DESCRIPION

Product Perspective:
It will empower us to the railway train info like their journey time, Arrival/Departure
Time, Seat availability and reservation biling and cancellation of the tickets.

Product Functions:
It will have two users interface layers; first one is user interface and the second one is Train
Management Interface.

Guest Interface:
Downloaded by Aditya Kushwaha (tannut8202@gmail.com)
 lOMoARcPSD|25857742

 View_Train_Info
 Search_Train
 Create_Account
 Customer_Login
 Purchase_Ticket
 Purchase_History

Train Management Interface:

 Login_Function
 Staff_Module
 Reservation_Module
 Ticket_Module
 Membership_Module
 Train_Module
 Cost_Module
 Availability_Module
 Report_Module
 Access_Module

Operating Environment
 Linux-8
 Windows-7
 Windows-8
 Windows-10
 Mac OS

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)

 lOMoARcPSD|25857742

Operations:
Book at ticket counter from 6 am to 11 pm anytime.
Book well before 50 days of travel.
One-form for 4 people only.
To spare time and long lines of people at the booking counter, online reservation is a great tool.

User Interfaces:
The system will give an assistance (clarification) link from each showed HTML page to
Disclose how to utilize that page. The Web page of RRS will allow total route, train choice,
Ticket reservation and ticket/train data queries using input devices be it keyboard, mouse
Or touch screen in Smart-phones.

Hardware Interfaces:
Nothing special interface is required.

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)

 lOMoARcPSD|25857742

Experiment – 2

Aim: Draw the use case diagram and specify the role of each of the actors. Also
State the precondition, post condition and function of each use case.

Use Case analysis:

Use Case Analysis is an article situated technique for planning data frameworks by
separating necessities into client capacities. Each case is an exchange or grouping
of occasions performed by client. Use Cases are concentrated to figure out what
items are needed to achieve them and how they connect with different articles.

Goals of use case analysis:

 Design system from user’s perspective
 Communicate system behavior in user terms.

Characteristics of use case analysis:

 Use-Case: The certain ways in which the system is being used.
 Each use case represents a “complete idea” or end-to-end transaction of
user/server request.

Some key components of use case analysis:

 Actors: In software model actors are basically people who interact with the
system in any way. Each actor has a different purpose and one serves the
purpose for the other one. They are interdependent on each other.
 Connections: Relationship from actors to use actors
 Relationships: Links among actors or among use cases.

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)

 lOMoARcPSD|25857742

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)

 lOMoARcPSD|25857742

Experiment – 3

Aim: Draw activity diagram.

Theory: An activity diagram is a behavioral diagram I.e., it depicts the behavior

Of a system. An activity diagram portrays the control flow from a start point to a
Finish point showing the various decision paths that exist while the activity is being
Executed. We can depict both sequential processing and concurrent processing of
Activities using an activity diagram. They are used in business and process modelling
where their primary use is to depict the dynamic aspects of a system.
An activity diagram is very similar to flowchart.

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)

 lOMoARcPSD|25857742

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)

 lOMoARcPSD|25857742

Experiment – 4

Aim: Draw class diagram.

Theory:
Class diagrams are the main building blocks of every object-oriented method. The
class diagram can be used to show the classes, relationships, interface,
association, and collaboration. UML is standardized in class diagrams. Since
classes are the building block of an application that is based on OOPs, so as the
class diagram has an appropriate structure to represent the classes, inheritance,
relationships, and everything that OOPs have in their context. It describes various
kinds of objects and the static relationship between them.

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)

 lOMoARcPSD|25857742

Experiment – 5

Aim: Draw sequence diagram.

Theory:
A sequence diagram is the most commonly
used interaction diagram. Interaction diagram – An interaction diagram is used
to show the interactive behavior of a system. Since visualizing the interactions in
a system can be a cumbersome task, we use different types of interaction
diagrams to capture various features and aspects of interaction in a
system. Sequence Diagrams – A sequence diagram simply depicts interaction
between objects in a sequential order i.e. the order in which these interactions take
place. We can also use the terms event diagrams or event scenarios to refer to a
sequence diagram. Sequence diagrams describe how and in what order the
objects in a system function. These diagrams are widely used by businessmen and
software developers to document and understand requirements for new and
existing systems.

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)

 lOMoARcPSD|25857742

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)

 lOMoARcPSD|25857742

Experiment – 6

Aim: Draw Collaboration diagram.

Theory:
The collaboration diagram is used to show the relationship between the objects in a
system. Both the sequence and the collaboration diagrams represent the same
information but differently. Instead of showing the flow of messages, it depicts the
architecture of the object residing in the system as it is based on object-oriented
programming. An object consists of several features. Multiple objects present in the
system are connected to each other. The collaboration diagram, which is also known
as a communication diagram, is used to portray the object's architecture in the
system.

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)

 lOMoARcPSD|25857742

Experiment – 7

Aim: Draw State chart diagram.

Theory:
The name of the diagram itself clarifies the purpose of the diagram and other details.
It describes different states of a component in a system. The states are specific to a
component/object of a system.
A State Chart diagram describes a state machine. State machine can be defined as
a machine which defines different states of an object and these states are controlled
by external or internal events.
Activity diagram explained in the next chapter, is a special kind of a Statechart
diagram. As State Chart diagram defines the states, it is used to model the lifetime of
an object.

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)

 lOMoARcPSD|25857742

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)

 lOMoARcPSD|25857742

Experiment – 8

Aim: Draw Component diagram.

Theory:
UML Component diagrams are used in modeling the physical aspects of object-
oriented systems that are used for visualizing, specifying, and documenting
component-based systems and also for constructing executable systems through
forward and reverse engineering. Component diagrams are essentially class
diagrams that focus on a system's components that often used to model the static
implementation view of a system.

Components in data classes packages

Components in view level packages

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)

 lOMoARcPSD|25857742

Components in Controller Classes Packages

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)

 lOMoARcPSD|25857742

Experiment – 9

Aim: Draw Deployment diagram.

Theory:
Deployment diagrams are used to visualize the topology of the physical components
of a system, where the software components are deployed.
Deployment diagrams are used to describe the static deployment view of a system.
Deployment diagrams consist of nodes and their relationships.
Purpose of Deployment Diagrams

The term Deployment itself describes the purpose of the diagram. 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.

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)

 lOMoARcPSD|25857742

Experiment – 10
Aim: Draw ER diagram.

Theory
ER Model is used to model the logical view of the system from data perspective
which consists of these components:
Entity, Entity Type, Entity Set –
An Entity may be an object with a physical existence – a particular person, car,
house, or employee – or it may be an object with a conceptual existence – a
company, a job, or a university course.
An Entity is an object of Entity Type and set of all entities is called as entity set.
e.g.; E1 is an entity having Entity Type Student and set of all students is called
Entity Set.

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)

 lOMoARcPSD|25857742

Downloaded by Aditya Kushwaha (tannut8202@gmail.com)