100% found this document useful (2 votes)
11K views18 pages

Lab File Software Engineering Lab (KCS-651)

This document contains the lab file submitted by Utkarsh for the Software Engineering Lab course at Galgotias College of Engineering and Technology. The file includes 9 experiments conducted from April 2021 to June 2021 related to software engineering concepts like preparing an SRS document, drawing UML diagrams, and identifying classes. Each experiment has the aim, content, and diagrams submitted by the student for that particular task. The file follows an index and is signed and dated by the student and instructor.

Uploaded by

Utkarsh Rawat
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
100% found this document useful (2 votes)
11K views18 pages

Lab File Software Engineering Lab (KCS-651)

This document contains the lab file submitted by Utkarsh for the Software Engineering Lab course at Galgotias College of Engineering and Technology. The file includes 9 experiments conducted from April 2021 to June 2021 related to software engineering concepts like preparing an SRS document, drawing UML diagrams, and identifying classes. Each experiment has the aim, content, and diagrams submitted by the student for that particular task. The file follows an index and is signed and dated by the student and instructor.

Uploaded by

Utkarsh Rawat
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 18

LAB FILE

SOFTWARE ENGINEERING LAB


(KCS-651)
Bachelor of Technology

(Department of Information Technology)

SUBMITTED BY: Utkarsh(1809713114)

UNDER THE GUIDANCE OF: Ms. Kanika Singhal

GALGOTIAS COLLEGE OF ENGINEEING AND TECHNOLOGY

GREATER NOIDA

2020-21

Affiliated to:
DR. A.P.J. Abdul Kalam Technical University(A.K.T.U)
Lucknow, Uttar Pradesh.
INDEX

S.NO TITLE DATE PAGE SIGN/REMARK


NO.
1 Prepare a SRS document in line with 9-04-21 3-6
the IEEE recommended standards.

2 Draw the use case diagram and 16-04-21 7


specify the role of each of the
actors. Also state the precondition,
post condition and function of each
use case.
3 Draw the activity diagram. 23-04-21 8

4 Identify the classes. Classify them 21-05-21 9


as weak and strong classes and
draw the class diagram.
5 Draw the sequence diagram for 28-05-21 10-11
any two scenarios
6 Draw the collaboration 04-06-21 12
diagram

7 Draw the state chart diagram 11-06-21 13

8 Draw the component diagram 18-06-21 14

9 Draw the deployment diagram 25-06-21 15

Experiment- 1
Aim:- Prepare a SRS document in line with the IEEE recommended standards.

OBJECTIVE
To develop software for railway reservation system with various functional and non- Functional
part of design namely,
• PROBLEM ANALYSIS AND REQUIREMENT ANALYSIS.
• TRAIN ENQUIRY
• TICKET GENERATION
• TICKET CANCELLATION
The ultimate goal of this project is to develop a database that integrates the process of the
Reservation of railway
INTRODUCTION
The purpose of this source is to describe the railway reservation system which provides the
train timing details, reservation, billing and cancellation on various types of reservation namely,
• Confirm Reservation for confirm Seat.
• Reservation against Cancellation.
• Waiting list Reservation.
• Online Reservation.
• PNR Generation
TECHNOLOGY USED
1. USER INTERFACE:
• Keyboard and Mouse
2. HARDWARE REQUIREMENT:
• Printer
• Normal PC
• CPU – Intel Core 2 Duo E7300
• RAM – 512MB (MIN)
• Hard Disk – 80GB
3. SOFTWARE REQUIREMENT:
• Turbo C++, C
4. OPERATING ENVIRONMENT:
The OS used are
• Windows 97
• Windows XP
INTENDED AUDIENCE:
The different types of readers are
• Developers
• Customers
• Management people specifically,
• Passengers
• Clerk
DEFINITIONS, ACRONYMS AND ABBREVIATIONS
• NTES – National Train Enquiry System
• IVRS – Interactive Voice Response system
• PRS – passenger reservation system
It consists of
• Train details
• Reservation form
• Billing
• Cancellation.
GENERAL DESCRIPTION It enables us to maintain the railway train details like their timings,
number of seat available and reservation billing and cancelling the tickets.
COMMUNICATION INTERFACES
• Indian Railway’s web-site, www.indianrail.gov.in offers PRS enquiries on the internet
Berth/Seat availability, Passenger Status, Fare, Train Schedule etc,.
• National Train Enquiry System (NTES) website, www.trainenquiry.comgives dynamic
information about the running status of any train and its expected arrival/departure at
any given station.
• Mobile telephone based SMS enquiry service. A new mobile phone based facility for rail
users’ which is. Country wide extension of Universal Rail Enquiry number “139”through
setting up of Interactive Voice Response System (IVRS).
OPERATIONS
• Any Reservation counter from 8 am to 8 pm.
• Prior to 90 days of Journey.
• One form for 6 persons only.
• To save time & queues Agent is others guides.
PRODUCT FUNCTION
• It tells the short note about the product.
TRAIN DETAILS
• Customers may view the train timing at a date their name and number of tickets.
• Passengers operated Enquiry Terminals.
PERFORMANCE REQUIREMENTS
• It is available during all 24 hours.
• Offered through Mail express, super-fast, Rajdhani & Shatabdi Trains.
• About 1520 Trains runs daily.
Variety of compartments based on comfort:
1. AC first class.
2. AC sleeper.
3. First class.
4. AC three tier.
5. AC chair car.
6. Sleeper class
7. Ordinary chair car.
Types of concerns & complexities:
1. 44 types of quotas.
2. 8 types of trains.
3. 9 types of classes.
4. 162 types of concessions.
5. 127 types of bogies
SOFTWARE SYSTEM ATTRIBUTES:
1. Reliable
2. Available
3. Secure
DOCUMENT APPROVAL
The bill passed on any proposals related to railway management needs approval of
Ministry of railway department.

ER Diagram:
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.
Experiment- 3
Aim:- Draw the activity diagram.
Experiment- 4
Aim:- Identify the classes. Classify them as weak and strong classes and draw the class diagram.
Classes: Manager, Inventory, Receptionist, chef, Guest, Rooms, Bill, Food, Housekeeping.
Experiment- 5

Aim:- Draw the sequence diagram for any two scenarios


Shopping Cart

ATM Withdrawal
Experiment- 6
Aim- Draw the collaboration diagram
Experiment- 7
Aim- Draw the state chart diagram
Experiment- 8

Aim- Draw the component diagram


Experiment- 9

Aim-Draw the deployment diagram

You might also like