Anjuman-I-Islam

M.H. Saboo Siddik Polytechnic

SOFTWARE ENGINEERING (SEN)

Microproject
Computer Engineering
Department
Co-4i
Title: railway management system
Year: 2023-24
PREPARED BY:
 220402: Ansari Abdullah
 220406: Ansari Zahoor
 220436: Molapiya Nadeem
 220447: Sayyed Abdul Mannan
 220463: Deepak Yadav

Under the guidance of: Miss Khan Ghazala

 MAHARASHTRA STATE
BOARD OF TECHNICAL EDUCATION

Certificate
This is to certify that Mr Ansari Abdullah Roll no. 220402
of fourth semester of Diploma in Computer Engineering of
institute M.H. Saboo Siddik Polytechnic(code: 0002) has
completed microproject satisfactorily in the subject:
Software Engineering (22413) for the academic year 2023-
24 as prescribed in the curriculum.

Place: Byculla, Mumbai Enrolment no: 2200020328

Date: ______________ Exam seat no:

Signature Signature Signature

Project guide H. O. D Principal

SEAL OF
INSTITUDE
 MAHARASHTRA STATE
BOARD OF TECHNICAL EDUCATION

Certificate
This is to certify that Mr Ansari Mohammed Zahoor Roll
no. 220406 of fourth semester of Diploma in Computer
Engineering of institute M.H. Saboo Siddik Polytechnic
(code:0002) has completed microproject satisfactorily in the
subject: Software Engineering (22413) for the academic
year 2022-23 as prescribed in the curriculum.

Place: Byculla, Mumbai Enrolment no: 2200020341

Date: ______________ Exam seat no:

Signature Signature Signature

Project guide H. O. D Principal

SEAL OF
INSTITUDE
 MAHARASHTRA STATE
BOARD OF TECHNICAL EDUCATION

Certificate
This is to certify that Mr Molapiya Nadeem Roll no. 220436
of fourth semester of Diploma in Computer Engineering of
institute M.H. Saboo Siddik Polytechnic (code:0002) has
completed microproject satisfactorily in the subject:
Software Engineering (22413) for the academic year 2022-
23 as prescribed in the curriculum.

Place: Byculla, Mumbai Enrolment no: 2200020351

Date: ______________ Exam seat no:

Signature Signature Signature

Project guide H. O. D Principal

SEAL OF
INSTITUDE
 MAHARASHTRA STATE
BOARD OF TECHNICAL EDUCATION

Certificate
This is to certify that Mr Sayyed Abdul Mannan Roll no.
220447 of fourth semester of Diploma in Computer
Engineering of institute M.H. Saboo Siddik Polytechnic
(code:0002) has completed microproject satisfactorily in the
subject: Software Engineering (22413) for the academic
year 2022-23 as prescribed in the curriculum.

Place: Byculla, Mumbai Enrolment no: 2200020319

Date: ______________ Exam seat no:

Signature Signature Signature

Project guide H. O. D Principal

SEAL OF
INSTITUDE
 MAHARASHTRA STATE
BOARD OF TECHNICAL EDUCATION

Certificate
This is to certify that Mr Yadav Deepak Roll no. 220463 of
fourth semester of Diploma in Computer Engineering of
institute M.H. Saboo Siddik Polytechnic (code:0002) has
completed microproject satisfactorily in the subject:
Software Engineering (22413) for the academic year 2022-
23 as prescribed in the curriculum.

Place: Byculla, Mumbai Enrolment no: 2200020343

Date: ______________ Exam seat no:

Signature Signature Signature

Project guide H. O. D Principal

SEAL OF
INSTITUDE
 Acknowledgment
We wish to express our profound gratitude to our guide Ms. Khan Ghazala
Ma’am who guided us endlessly in the framing and completion of the micro
project. He guided us on all the main points in that micro project. We are
indebted to his/her constant encouragement, cooperation, and help. It was
his/her enthusiastic support that helped us in overcoming various obstacles in
the micro-project.

We are also thankful to our Principal, HOD, faculty members and classmates of
Computer Engineering department for extending their support and motivation in
the completion of this micro-project.

Names of Team Members with Roll Nos.

 220402: Ansari Abdullah

 220406: Ansari Mohammed Zahoor
 220436: Molapiya Nadeem
 220447: Sayyed Abdul Mannan
 220463: Yadav Deepak
 Annexure-I
Microproject proposal
Title of microproject: Railway Management System

I. Aims/Benefits of microproject
Software Engineering is the foundation for professional processes to be followed
involving principles, practices and techniques for software development. This project
aims to make a software based on the problem statement. Identifying scope of project,
selecting relevant process models, preparing ER diagrams and use case models.
Benefit mainly will be making us independent enough to develop a software.

II. Course outcomes addressed

a) Select suitable Software Process model for software development
b) Prepare software requirement specification.
c) Use software modelling to create data designs.
d) Estimate size & cost of software product.
e) Apply project management and quality assurance principles in software development.

III. Proposed methodology

1. To search the information about the project. (Collect relevant data from different
sources (books/internet/market/suppliers/experts and others through
surveys/interviews etc.).
2. To collect all relevant content / materials to complete the project.
3. To prepare the report of micro project.
4. To deliver presentation/ appear for viva-voice

 Discussion of the given topic among group members.

 Literature survey
 Submission of project proposal
 Analysis of data
 Work divided among group members
 Compilation of content
 Representation
 Editing the content as per the instructions
 Report Preparation
 Viva and presentation
 Annexure-I
IV. Action Plan
Planned Name of
Planned
Weeks Details of activity finish responsible
start date
date team members

1& 2 Discussions & finalization of topics

3 Preparation of abstract

4 Literature review

5 Submission of microproject proposal(Annexure -I)

6 Collection of information on given topic

7 Collection of all relevant contents

8 Discussion and submission of outline of the project

Analysis/execution of collected data/information and

9 Preparation of prototypes/drawings/charts/graphs/
tables/models/circuits/programs etc.

10 Compilation of contents of project

11 Compilation of weekly progress report

12 Preparation of the project report (Annexure II)

13 Viva Voce / Delivery of presentation.

V. Resources required
Name of
Sr. no. Specifications Qty Remarks
resources
Learning resources and
1. Online 3 sites
various websites
Microsoft word, Tools with
2. Desktop 1 for each
internet facility.

Names of Team Members with Roll Nos.

1. Ansari Abdullah 220402

2. Ansari Mohammed Zahoor 220406
3. Molapiya Nadeem 220436
4. Sayyed Abdul Mannan 220447
5. Yadav Deepak 220463

Name of faculty: Ms Khan Ghazala

 Annexure-II
Microproject Report
Title of Micro-project: Railway Management System
I. Rationale
Implementation of a Railway Management System offers passengers convenience by
enabling online booking, saving time and effort. It enhances railway operations
through streamlined ticketing, resource management, and real-time updates, leading to
cost savings, increased revenue, and a competitive edge in the transportation industry.
II. Aims/Benefits of microproject
Software Engineering is the foundation for professional processes to be followed
involving principles, practices and techniques for software development. This project
aims to make a software based on the problem statement. Identifying scope of project,
selecting relevant process models, preparing ER diagrams and use case models.
Benefit mainly will be making us independent enough to develop a software.

III. Course outcomes achieved

 Select suitable Software Process model for software development
 Prepare software requirement specification.
 Use software modelling to create data designs.
 Estimate size & cost of software product.
 Apply project management and quality assurance principles in software development.

IV. Literature review

All the information was gathered through different websites and scrutiny was done.
All relevant & required information/pictures were added in the project.

V. Actual Methodology Followed

We were assigned with the microproject topic and time was assigned to us to complete
the project in 11 weeks. All team members worked together in these 11 weeks together
in order to complete this microproject. Data was collected according to our topic.
Presentation was prepared and finally at last technical report was prepared.

VI. Actual resources used

Name of
Sr. no. Specifications Qty Remarks
resources
1. Software MS-Word 1 for each
www.geeksforgeeks.com,
2. Websites www.tutorialspoint.com, 1 for each

s
VII. Outputs of the microproject

ONLINE RAILWAY RESERVATION SYSTEM

PROBLEM STATEMENT:
 A problem statement is a clear description of issue, it includes a vision, an issue
statement & method used to solve the problem.
 It is usually one or two sentences to explain your problem process
improvement project will address.
 It also serves as great communication tool, helping to get buy in and support
from others.

PROBLEM STATEMENT FOR

RAILWAY RESERVATION
SYSTEM:
The project seeks to create a Railway
Management System simplifying
ticket booking and providing
passengers with real-time updates,
optimizing railway operations and
enhancing user experience.

 Some tasks that need to be done are:

1) All customers must have an E-Mail ID and password to login.
2) Login credentials provided should be highly secured.
3) Upon successful login they must be able to interact with ease
 SCOPE OF THE PROJECT:
 A project scope statement is a tool used to describe the major deliverable of a
project including the key milestone, high level requirements, assumptions and
constraints.
 It provides a detailed description of the work that must be done to deliver the
output of a project on time and within the allotted budget.
 A well-written project scope includes goals, objectives, deliverables, a task
plan, costs and deadlines of a project.

SCOPE OF RAILWAY RESERVATION SYSTEM:

- Authenticate users for booking and accessing railway services securely.
- Present comprehensive information on train schedules, routes, and ticket
availability.
- Offer options to select seats, classes, and amenities, facilitating easy booking.
- Manage ticket bookings efficiently and ensure timely delivery of tickets to
passengers.
- Enable smooth interaction with the system for passengers and railway staff.
- Ensure punctual delivery of services, maintaining reliability and satisfaction for
all users.

 Feedback is mandatory. It should be taken from user and as per their

recommendation changes should take place.
 Multiple payment choices should be provided. Online payment, Cash on
delivery, etc. Also debit card and credit card options should be given.

PROCESS MODELS:
 Software process models are systematic methods for controlling &
coordinating the development of software product achieving all stated
objectives or goals.
 A process model provides a basis of containing various activities required to
develop and maintain the software.
 A software process model is simplified representation of a software process.
 It is a set of activities & associated results, which produce a software product.
 IEEE defines a process model as ‘A framework containing the processes,
activities and tasks involved in development cooperation and maintenance of a
software product, spanning the life of system from definition of its requirements
in termination of its users.’
 Types of process models:

1. Waterfall Model:

 The Waterfall Model was the first Process Model to be introduced. It is

also referred to as a linear-sequential life cycle model.
 It is very simple to understand and use. In a waterfall model, each phase
must be completed before the next phase can begin and there is no
overlapping in the phases.
 The waterfall Model illustrates the software development process in a
linear sequential flow. This means that any phase in the development
process begins only if the previous phase is complete.
 The sequential phases in Waterfall model are:
 i. Requirement Gathering and analysis − All possible requirements
of the system to be developed are captured in this phase and
documented in a requirement specification document.

ii.System Design − The requirement specifications from first phase

are studied in this phase and the system design is prepared. This
system design helps in specifying hardware and system
requirements and helps in defining the overall system architecture.
iii. Implementation − With inputs from the system design, the system
is first developed in small programs called units, which are
integrated in the next phase. Each unit is developed and tested for
its functionality, which is referred to as Unit Testing.
iv. Integration and Testing − All the units developed in the
implementation phase are integrated into a system after testing of
each unit. Post integration the entire system is tested for any faults
and failures.
v. Deployment − Once the functional and non-functional testing is
done; the product is deployed in the customer environment or
released into the market.
vi. Maintenance − There are some issues which come up in the client
environment. To fix those issues, patches are released. Also to
enhance the product some better versions are released.
Maintenance is done to deliver these changes in the customer
environment.
 Advantages:
 Simple and easy to understand and use
 Clearly defined stages.
 Well understood milestones.
 Easy to arrange tasks.
 Process and results are well documented.
 Disadvantages:
 High amounts of risk and uncertainty.
 Not a good model for complex and object-oriented projects.
 Poor model for long and ongoing projects.
2. Incremental model:

 Incremental Model is a process of software development where

requirements divided into multiple standalone modules of the software
development cycle.
 In this model, each module goes through the requirements, design,
implementation and testing phases. Every subsequent release of the
module adds function to the previous release.
 Phases of incremental model:

i. Requirement analysis: In the first phase of the incremental model,

the product analysis expertise identifies the requirements. And the
system functional requirements are understood by the requirement
analysis team. To develop the software under the incremental
model, this phase performs a crucial role.
ii. Design & Development: In this phase of the Incremental model of
SDLC, the design of the system functionality and the development
method are finished with success. When software develops new
practicality, the incremental model uses style and development
phase.

iii. Testing: In the incremental model, the testing phase checks the
performance of each existing function as well as additional
functionality. In the testing phase, the various methods are used to
test the behavior of each task.
iv. Implementation: Implementation phase enables the coding phase
of the development system. It involves the final coding that design
in the designing and development phase and tests the functionality
in the testing phase. After completion of this phase, the number of
the product working is enhanced and upgraded up to the final
system product.
 Advantages:

 Easier to test and debug

 More flexible.
 Simple to manage risk because it handled during its iteration.

 Disadvantages:
 Need for good planning
 Total Cost is high.
 Well defined module interfaces are needed.

3. Spiral Model

 Spiral model is one of the most important Software Development Life

Cycle models, which provides support for Risk Handling.
 In its diagrammatic representation, it looks like a spiral with many
loops.
 Each loop of the spiral is called a Phase of the software development
process.
 The Spiral Model is a software development life cycle (SDLC) model
that provides a systematic and iterative approach to software
development.
 Phases of spiral model are:

i. Planning: The first phase of the Spiral Model is the planning

phase, where the scope of the project is determined and a plan is
created for the next iteration of the spiral.
ii. Risk Analysis: In the risk analysis phase, the risks associated
with the project are identified and evaluated.

iii. Engineering: In the engineering phase, the software is developed

based on the requirements gathered in the previous iteration.
 iv. Evaluation: In the evaluation phase, the software is evaluated to
determine if it meets the customer’s requirements and if it is of
high quality.
v. Planning: The next iteration of the spiral begins with a new
planning phase, based on the results of the evaluation.
 Advantages:
 Risk Handling
 Good for large projects
 Flexibility in Requirements

 Disadvantages:
 Too much dependability on Risk Analysis
 Difficulty in time management
 Complex & expensive

4. Agile Process Model

 The meaning of Agile is swift or versatile. ‘Agile process model’ refers
to a software development approach based on iterative development.
 Agile methods break tasks into smaller iterations, or parts do not directly
involve long term planning.
 The project scope and requirements are laid down at the beginning of
the development process. Plans regarding the number of iterations, the
duration and the scope of each iteration are clearly defined in advance.
 Each iteration involves a team working through a full software
development life cycle including planning, requirements analysis,
design, coding, and testing before a working product is demonstrated to
the client.
 It has small but dedicated teams with high degree of synchronization.
  Features of Agile Process Model:
1. Simplicity is essential
2. Project is developed around motivated individuals
3. Welcoming changing requirements
4. Close & daily cooperation between business people and
developers.
5. Face to face communication takes place
6. Continuous attention to technical excellence and good design.

 Types of agile modelling include: SCRUM, eXtreme Programming (XP),

Crystal, Dynamic Software Development Method (DSDM), etc.

 Advantages:
 Improved project predictability and flexibility
 High team morale
 Face to face communication with clients.

 Disadvantages:
 Lack of necessary documentation
 Maintainance problems

PROCESS MODEL USED FOR RAILWAY RESERVATION SYSTEM:

 We have selected ‘Waterfall Model’ for our project as it follows sequential

approach.
 An entire plan has been laid down and new process begins after completion of
one process.
 Our process begins with software requirement and customer specification and
processes through planning & testing.
  Process flows from top to bottom like flow of water from hill to ground. It is
pre-planned in nature.
 Any new changes can’t be incorporated in middle of project development.
 Product of this model always defines all constraints of organization.
 ‘Waterfall model’ produces a good quality product in terms of space and time.
It is most commonly used model.
 Companies like ‘Toyota’ follows this model for their software development.

REQUIREMENT ENGINEERING:

 Requirement is a condition possessed by the software or system component in

order to solve real-world problems.
 Requirements are stepping stones to success of any project.
 If software projects get started without properly understanding users needs or
without exploring multiple dimensions of requirements. There will also be mis-
alignment at end between the final result delivered and users expectations of
project resulting in lot of re-work.
 IEEE defines requirement as ‘A condition or capability needed by a user to
solve a problem or achieve an objective(goal).’

TASKS OF REQUIREMENT ENGINEERING

REQUIREMENT
INCEPTION ELABORATION SPECIFICATION MANAGEMENT

ELICITATION NEGOTIATION VALIDATION

1. INCEPTION
- Inception means ‘beginning’. It is always problematic for the developer that
from where to start.
- The customer & developer meet and decide the overall scope and nature of
the problem.
- The aim is:
 To have basic understanding of the problem.
 To know the people who will use the software.
 To know exact nature of problem.

2. ELICITATION
 - Elicitation means ‘to draw out the truth from anybody’.
- It is a task that helps customer to define what is required.
- Required:
 Problems of volatility:- Meaning of volatility is change from one
state to another.
 Problem of scope:- Many times customer states unnecessary project
details. These details may confuse developers instead of clarity.
 Problem of understanding: Sometimes both customers and
developers has poor understanding of needed things, capabilities &
limitations of competing environment and understanding of problem
domain.

3. ELABORATION
- Meaning of elaboration is ‘to work in detail.’
- Information obtained during inception & elicitation is expanded and
modified during elaboration.
- It is an analysis of modelling activity.

4. NEGOTIATION
- It is the discussion on financial and other commercial issues.
- Negotiation function is not unusual for customer to ask for more than that
can be achieved, given limited business resources.

5. SPECIFICATION
- It is final work product produced by requirement engineer.
- Specification serves as foundation of all requirement of software
engineering activities.
- Describes performance and function of computer-based system and
constraints that will govern its development.

6. VALIDATION
- All previous work completed will be just meaningless if it is not validated
against customer requirements or expectations.
- Requirement validation includes:
 Does requirement violate any system domain constraints?
 All requirements are stated clearly?
 Are requirements misinterpreted?
 Is system requirement irascible to system model?

7. REQUIREMENT MANAGEMENT
- Requirement management starts with identification. Each and every
requirement is assigned a unique identifier.
 - For this traceability table is developed. Each and every traceability table
is related to the requirement to one or more aspects of the system or its
environment.

QUESTIONARY FOR RAILWAY RESERVATION SYSTEM:

 Inception based questions:

a. What type of software are you preparing?
Ans. We are developing a Railway Management System software. The primary
motivation behind this project is to streamline railway operations and enhance
passenger experience in the digital age.

b. What are the resources required?

Ans. We require a proficient software development team, personnel for managing
ticketing and train operations, and necessary hardware infrastructure equipped with
relevant security measures.

c. How will the software be prepared?

Ans. The software development process will commence with ensuring robust
security measures for user authentication and data protection. Subsequently, we will
focus on implementing features for efficient ticket booking, train scheduling, and
passenger information management.

 Elicitation based questions:

a. State the features available.

Ans. The Railway Management System will offer features such as online ticket
booking, seat selection, real-time train status updates, route information, and secure
payment options tailored to passenger preferences.

b. How will you determine whether users are satisfied or not?

Ans. We will incorporate a feedback mechanism within the system where passengers
can share their experiences, provide suggestions, and express any grievances.
Additionally, periodic surveys and analysis of user interactions will help gauge
overall satisfaction levels and identify areas for improvement.

 Elaboration based questions:

a. What type of modifications will be required?

Ans. Continuous updates to the railway management system are imperative,
including timely adjustments to train schedules, seat availability, and route
information. Incorporating passenger feedback for service enhancements and
addressing any technical glitches promptly will also be essential.
b. What all features are present in your software?
Ans. The railway management system includes features such as online ticket
booking, seat reservation, real-time train tracking, schedule management, passenger
information services, and secure payment options. Additionally, it offers
functionalities for managing staff assignments, train maintenance schedules, and
operational logistics.

 Negotiation based questions:

a. What will be the approximate budget to develop your software?

Ans. The projected budget for developing the railway management system falls
within a range of 100,000 to 150,000 units of currency, subject to adjustments based
on specific project requirements, technology infrastructure, and stakeholder
preferences.

b. What type of work is done according to the given budget?

Ans. The allocated budget encompasses essential development tasks, including
software design, coding, testing, and implementation. Additionally, it covers
expenses related to data integration, security measures, user training, and ongoing
technical support to ensure the system's efficiency and reliability.

 Specification based questions:

a. How will the software work?

Ans.
Step 1: Users will authenticate themselves by logging into their accounts.
Step 2: They can then search for train schedules, check seat availability, and make
reservations.
Step 3: Upon selecting a desired train and seat, passengers can proceed to book
tickets and make payments.
Step 4: Confirmation of booking along with e-ticket details will be provided.
Step 5: Passengers can view and manage their bookings, including cancellations or
modifications.
Step 6: Real-time updates on train status and any announcements will be available to
users.

 Validation based questions:

a. Is your software secured enough?

Ans. Yes, the railway management system is designed with robust security measures
to protect user data, transactions, and system integrity. Encrypted communication
protocols, user authentication mechanisms, and access controls are implemented to
ensure data confidentiality and prevent unauthorized access.
b. What will be the operational hours for using this software?
Ans. The railway management system will operate 24 hours a day, 7 days a week,
365 days a year, providing continuous access to train schedules, ticket booking, and
passenger services. However, specific service timings for ticket reservations and
customer support may vary based on railway operational schedules and maintenance
activities. Delivery timings may differ.

SOFTWARE REQUIREMENT SPECIFICATION(SRS):

 Software requirement is an official statement of what system developers should

implement.
 It should include both: user requirement for a system and a detailed
specification of system requirements.
 It is a requirement specification for a software system and show complete
description of the behavior of a system to be developed.
 Structure of SRS document:

 Features of SRS document:

  Need for SRS document:
 There are 3 major parties interested in a system i.e. the client, the user
and the developer. Somehow requirement for the system that will
satisfy the needs of the clients and concern of user have to
communicate to developers.
 Helping client understand their own need.
 Provides reference for validation of final product.
 A high-quality SRS is a prerequisite to high quality software.
 SRS determine the requirements of the system and thus it enables the
developer to have a rough estimate of total cost.

SRS DOCUMENT FOR RAILWAY RESERVATION SYSTEM:

1. INTRODUCTION

1.1 Purpose:
This document outlines the features of the Railway Reservation System,
serving as both a guide for developers and a validation document for potential
clients. The system aims to streamline the process of booking railway tickets,
enhancing convenience for users while ensuring efficient management for
railway authorities.

The Railway Reservation System provides a comprehensive solution for

ticket booking, catering to both passengers and railway administrators
through an online platform. It facilitates seamless ticket booking and
management, reducing the need for manual intervention and streamlining
operations.
 1.2 Scope:
The Railway Reservation System enables users to book, modify, and cancel
railway tickets online, offering a convenient and efficient alternative to
traditional ticketing methods. It encompasses functionalities such as ticket
availability checking, seat selection, payment processing, and ticket issuance.

1.3 Definition/Abbreviations:
- SRS: System Requirement Specification
- GUI: Graphical User Interface
- Stakeholder: Individuals involved in the system, including passengers,
administrators, etc.
- OSS: Railway Reservation System

1.4 References:
- www.w3schools.com
- "Software Engineering: A Practitioner’s Approach" by Roger S. Pressman

1.5 Overview:
The Railway Reservation System simplifies the process of ticket booking for
both passengers and railway authorities. It provides an intuitive interface for
users to book tickets online, eliminating the need for physical visits to
booking counters. The system is designed to be user-friendly, accessible to
individuals with varying levels of technical expertise. While no specific
educational background or technical knowledge is required, familiarity with
mobile or touchscreen devices can enhance the user experience.

2. OVERALL DESCRIPTION

The RAILWAY RESERVATION SYSTEM application facilitates the setup of

online railway ticket booking platforms for vendors, enables customers to
browse and book tickets, and allows system administrators to manage requests
for new booking platforms and maintain categories of railway services.

2.1 Product Perspective:

The RAILWAY RESERVATION SYSTEM targets individuals who
prefer not to physically visit ticket counters due to time constraints or
a preference for avoiding formalities associated with in-person
transactions.

2.2 Product Functions:

Common functions of the system include user authentication
(login/logout), handling ticket reservations, and managing shipping
orders, processing payments, collecting customer feedback, and
facilitating visits to railway booking sites.
2.3 User Characteristics:
Users of the system should possess familiarity with basic terms such
as login, registration, and the ticket ordering process.

2.4 Constraints:
A robust internet connection is essential for the RAILWAY
RESERVATION SYSTEM to function optimally.

2.5 Assumptions & Dependencies:

It is assumed that the hardware infrastructure operates seamlessly
with the designated operating system and developed software. The
system's functionality relies on users having access to stable internet
connectivity.

3. SPECIFIC REQUIREMENTS

3.1 Functional Requirements:

This section outlines the functional modules of the RAILWAY

RESERVATION SYSTEM:

3.1.1 Registration:
- Users must register to purchase tickets. Unregistered users cannot access
the booking feature.

3.1.2 Login:
- Customers log in using a valid user ID and password to access booking
functionalities.

3.1.3 Changes to Cart:

- Registered users can modify their shopping cart by adding or canceling
ticket orders.

3.1.4 Payment:
- The system supports payment methods including cash and online
transactions (e.g., GPay, PhonePe). Additional payment options may be integrated in
the future.

3.1.5 Logout:
- Customers can log out of the system after completing transactions or
browsing.

3.1.6 Report Generation:

- Upon order completion, the system generates a bill and sends a copy to the
customer's email address while storing another copy in the system database.
3.2 Non-Functional Requirements:

These non-functional requirements ensure system integrity and usability:

3.2.1 Secure Access to Customer Data:

- The system must ensure secure access to customers' confidential
information.

3.2.2 (24*7) Availability:

- The system should be accessible at all times to accommodate users across
different time zones.

3.2.3 Better Component Design for Peak Performance:

- The system should be designed with efficient components to maintain
optimal performance, especially during peak usage periods.

3.2.4 Flexible Service-Based Architecture:

- A service-based architecture is desirable for future scalability and
extension of functionalities.

Other non-functional aspects include Security, Reliability, Maintainability,

Portability, Reusability, and Compatibility.

3.3 Performance Requirements:

To ensure satisfactory performance, the system must meet the following

criteria:

- Maintain acceptable speed even during peak usage periods.

- Accommodate a maximum number of concurrent users.
- Dynamically adjust server connections based on user attributes such as
location.
- Ensure uninterrupted operation 24/7 to cater to users across different time
zones.

USE CASES:
 In software and system engineering, a use case is a list of actions or events
steps typically defining the interactions between a role and a system to achieve
a goal.
 The actor can be a human or other external system. In system engineering use
case are used at higher level than within software engineering often
representing missions or stack holders goal.
 The detail requirements may then be captured in system modeling language as
conceptual statements.
 Use case analysis is an important and valuable requirement analysis technique
that has been widely used in modern software engineering.
 Use case symbols:

 Advantages of Use Case:

i. Use cases add value because they help explain how the system should
behave and in the process, they also help brainstorm what could go
wrong.
ii. They provide a list of goals and this list can be used to establish the cost
and complexity of the system.
iii. Use case can serve on basis for estimating, scheduling and validating
effort.
iv. They are easily traceable.
USE CASE FOR RAILWAY RESERVATION SYSTEM:

ER DIAGRAM:

 ER stands for entity relationship. It is a visual representation of data that

describes how data is related to each other.
 It is a modeling technique used in software engineering to produce a conceptual
data model for an information system.
 Diagram created using ER modeling technique are known as ER Diagrams or
ERDs.
 Dr. Peter Chen is the originator of Entity Relationship Diagram
 Symbols of ER diagram:
1. Represents an Entity-

2. Represents an Attribute-

3. Represents actions-

4. Links attribute to entity set - ___________________

5. Represents multivalued attribute-

6. Represents weak entity-

7. Connecting lines-

8. Represents process-
ER DIAGRAM FOR RAILWAY RESERVATION SYSTEM:

DATA FLOW DIAGRAM:

 DFD is an abbreviation for Data Flow Diagram. The flow of data of system or
process is represented by DFD.
 It also gives insight into inputs and outputs of each entity and the process itself.
 It provides an overview of:
- What data system processes
- What transformation are performed
- What data are stored
- What results are produced

 Components of DFD:
  Levels of DFD:
 Level 0- It represents entire system as a single process and provides an
overall picture of the system.
 Level 1- Represents main functions of system and how they interact
with each other.
 Level 2- Represents the processes within each function of system.

DFD FOR RAILWAY RESERVATION SYSTEM:

 TEST CASES:
 IEEE defines test case as ‘A set of input values execution preconditions and
expected outcomes developed for a particular object.
 Test condition such as to exercise a particular program path or to verify
compliance with specific requirements.
 A Test case is usually a single step or occasionally a sequence of steps to the
correct behavior / functionality features of an application an expected or
expected outcome is usually given. Additional information may include:
 Test case ID
 Test case expression
 Test step
 Related requirements
 Depth
 Test Category
 Author
 Pass Fail
 Remarks
TEST CASES FOR RAILWAY RESERVATION SYSTEM:

Test Test Case Test Case Step Step Test data Expected result
Case Name Description Name Description
ID
TC 001 Verify admin Admin should
Login with be registered Enter name Email: System display
usernames with valid Step 1 and [email protected] admin
password email password password homepage
& password and click on xyz123
before Login Login button
User should be Click on
TC 002 Verify Login registered with login button Email: system
with valid valid email & Step 2 enter valid [email protected] displays user
user-name & password username & password:abc456 homepage
password before Login. password.
TC 003 Verify user User is not Click on
Login with registered login button Email: displays error
invalid before with Step 3 enter valid [email protected] message login
username & valid email username & password:123Hy failed
password and password password
User should be Click on User will set
registered with Step 4 forget Email: new password
valid email & password [email protected] after verifying
TC 004 Forget password entered Otp:3456 and password
password before clicking registered password:abc123 will change
on forget email Identer successfully
password otp to verify
Test Test Case Test Case Step Step Test data Expected result
Case Name Description Name Description
ID
User must have Click on
TC 005 Register new valid details register button Email ID, All required fields
user required for Step filled required contact are filled
registration I.e. 5 fields of form ,address
email, contact no
Verify otp sent, Registration
TC 006 Verify user Email Id should Step create Otp, successful message
with otp be correct 6 password and password. will be displayed
confirm details
TC 007 User adding User should
Bank details select Step Click on SAVE Bank Save Bank details
for payment appropriate bank 7 name,
account
number

User booking User location Step Open Tickets Display details and
TC 008
tickets should be turned 8 Reservation total amount
ON Window, Click
BOOK
TICKET

Atleast one ticket

Cancel should be Step Remove Tickets Continue booking
TC 009
selected. 9 desired tickets.
Ticket
TC 010 Proceed to Tickets must be Step Click on Source Checkout display
checkout checked and 10 proceed to and
arranged. checkout destination
location,
VIA
(optional)
Project Cost Estimation Technique:
 Estimation of various project parameter is a basic project planning activity.
 The important project parameter that are estimated include: project size effort
required to develop the software project duration and cost.
 The estimate not only help in quoting the project cost to customer, but also
helpful in resource planning and scheduling.
1. COCOMO Model
 Boehm proposed COCOMO (constructive Cost Estimation) Model in 1981.
 COCOMO is one of the most generally used software Estimation in the world.
 COCOMO predicts the efforts and schedule of a software product based on size
of the software.
 In COCOMO, projects are categorized into 3 types:
Organic, Semidetached, Embedded.
a) Organic COCOMO - A development project can be treated of organic type,
if project deals with developing a well understood application program, size
of development team is reasonably small & team members are experienced
in developing similar methods of project.
b) Semidetached COCOMO - A development project can be treated with
semidetached type if development consists of mixture of experienced &
inexperienced staff.
c) Embedded COCOMO - A development project is treated to be of an
embedded type, if software being developed is strongly coupled to complex
hardware or if stringent regulations on operational method exist.
2. COCOMO-II Model
 COCOMO-II is revised version of Original COCOMO and is developed at
University of South California.
 It is the model that allows one to estimate the cost, effort and schedule when
planning a new software development activity.
 It consists of three sub models:
i. End user programming
ii. Intermediate sector
a) Applications generators & Composition Aids
b) Application Composition Sector
c) System Integration
iii. Infrastructure sector
  Difference: COCOMO and COCOMO - II model
COCOMO COCOMO – II
1. It is useful in the waterfall model of It is useful in non- sequential rapid
software development cycle. development and reuse models of
software.
2. It provides estimates of effort and It provides estimates that represent one
schedule. standard deviation around most likely
estimate.
3. Linear reuse formula. Non Linear reuse formula.
4. Size of software stated in terms of Size of software stated in terms of object
lines of code points, function points & lives & of
code.

COCOMO MODEL FOR RAILWAY RESERVATION SYSTEM:

Task name Duration Start Finish Resource Cost

Names
1. Requirement 32 Days 02/02/23 5/03/23 $320,800
Analysis Analysis
1.1 Develop define 12 Days 02/02/23 14/02/23 Requirement $80000
system architecture analyst-I

1.2 System Security

Analysis 10 Days 14/02/23 24/02/23 Security $64000
Speciality
1.3 Software Quality
and risk analysis 7 Days 24/02/23 02/03/23 Project leader $92000

Requirement
1.4 Create SRS report 5 Days 02/03/23 05/03/23 analyst-II $84800

System 2 System Designing 28 Days 05/03/23 01/04/23 $290,000

Design 2.1 Perform 10 Days 05/03/23 14/03/23 Software $90,000
Architectural architecre-1
Design
2.2 Develop algorithm 10 Days 14/03/23 23/03/23 Software $90,000
& test cases architecre-2
2.3 Create software 8 Days 24/03/23 01/04/23 Software $11,000
design specification architecre-3
 Task name Duration Start Finish Resource Cost
Names
Coding 3 Coding 30 Days 2/04/23 02/05/23 $80,000

3.4 Create test data 7 Days 02/04/23 09/04/23 Database $70,000

Specialist

3.5 Create source 10 Days 09/04/23 18/04/23 Frontend $165,000

code Programmer
(3-4)
11 Days 18/04/23 28/04/23 Java/python $120000
3.6 Generate object Programmer
code (3-4)
5 Days 28/04/23 02/05/23 Programmer $125000

Document project
module
Testing 4. Testing 22 Days 03/05/23 25/05/23 $200000
4.1 Unit testing 10 Days 03/05/23 12/05/23 Software $90000
Component Tester-1
testing 12 Days 12/05/23 25/05/23
4.2 System Software $110000
Tester-1,2
testing
provide
feedback

Operation Operation 40 Days 26/05/23 05/07/23 $320000

& & Maintenance
Maintenance a. Final Check and 10 Days 26/05/23 05/06/23 Project leader $70,000
Verification
b. Documentation 12 Days 05/06/23 17/06/23
Document $110000
& user manual writer(2)
c. Training 08 Days 18/06/23 25/06/23 Trainer $60000
5. Perform 10 Days 26/06/23 05/07/23 $80000
preventive
maintenance
 TIMELINE/GANTT CHART:
 Timeline Chart:
A timeline chart is a chart that depicts how set of resources are used
over time. While managing a software project, a timeline is often a
reasonable visualization choice.

 GANTT Chart:
GANTT stands for Generalized Activity Normalization Timetable
chart. It is a type of 2D chart of sequence of tasks and their
dependencies. This chart offers microscopic view of every detail of
your project like current task progress, task priorities, milestones,
etc.

NOTE: Main difference between Timeline & GANTT chart is that GANTT
charts are used to plan and manage projects, while timeline show start and
finish dates of tasks.

GANTT CHART FOR RAILWAY RESERVATION SYSTEM:

GANTT Chart

Operation & Maintenanace

Testing

Coding

System Designing

Requirement analysis

0 1 2 3 4 5 6 7 8 9

January February March April May June

July August Sept October November December
 SQA PLAN:

 SQA is a planned and systematic way to evaluate quality of software product

standard process and procedure.
 Objectives of SQA:
i. To determine objective of software to be accomplished to establish/develop
s/w plan, when the objectives are determined.
ii. To monitor and adjust s/w plans to satisfy users requirement or
specification.
iii. SQA include process of assuring standard and procedures are established
and are followed throughout s/w cycle.

 Benefits of SQA
i. SQA produces high quality software.
ii. Beneficial for better reliability
iii. Improves the process of creating software.
 Procedure
- They are established criteria to which development and control process are
compared.
- Procedure are explicit steps to be followed in carrying out a process.
- All process should have documented procedures.
 Example:
Example of process for which procedure are headed into configuration management,
Non confirmation reporting and corrective actions, testing and formal inspections.
 Standards
- Standards are criteria to which s/w product are compared specified standard
- They are used to define development criteria that are used to guide the manner
in which s/w is engineered.
- Types
1) Documentation standard - Specify form and contents for planning,
Analysis and product documentation and provide consistency throughout
project.
2) Design standard-Specify form and content. Of design product. They provide,
rules and method for translating the s/w requirement into s/w design.
3) Code standard- Specify the language in which code is to be written and define
Restriction on use of language features they define legal structure style
Convention rules for data structures and interfaces.

 Need of SQA:
- After completion of 7 phases of testing, result looks good. No issues occurred
but Management board asks for evidence to show that you managed the project
well.
 - As a test manager, you are person who takes in charge of activities. However,
you are at highest position in project team. SQA Auditor will review & check the
project management activities are executed to highest possible standard.

 Steps to implement Quality Assurance:

1) Develop SQA plan

Goal of SQA plan is to craft planning processes & procedures to ensure products
manufactured or service delivered by organization are of exceptional quality.
1.1] Identify role & responsibilities of SQA team
In a project team, every member must have responsibility for the quality of his or her
work. Each person has to make sure their work meet the QA criteria.

1.2] List of work products that SQA auditor will review & audit
Test manager should:
 List out all work products of each Test Management process.
 Define which facilitates or equipment SQA auditor can access to perform
SQA tasks.

1.3] Create schedule to perform SQA tasks

Test manager should describe the tasks to be performed by SQA auditor with special
emphasis on SQA activities as well as work product for each task.
2) Define standards/methodology
To review the Management activities against the standards process, you should do the
following steps:

i. Define the policies and procedures intended to prevent defects from

occurring in the management process
ii. Document the policies & procedures
iii. Inform and train the staff to use it
 3) Review the process
Review project activities to verify compliance with the
defined management process. In the management
review, the SQA members have to perform 5 SQA
reviews as following:

SQA FOR RAILWAY RESERVATION SYSTEM:

Step 1:

1.1) Role & Responsibilities of SQA team

No. Member Role Responsibility

1. Abdullah SQA Leader Develop & document quality
standard and process for all
management process.

Manage software quality assurance

activities for project
2. Mannan SQA Auditor Perform SQA tasks, report to SQA
leader the result of SQA review.

1.2) List work products that SQA auditor will review

No. Management Work Product Responsible
phase member
1. Risk Analysis Risk Management All
document
2. Estimation Estimation & Metrics Abdullah
report
3. Planning Test planning document All
4. Organization Human resource plan, All
training plan
 5. Monitoring & Collected metrics of project Mannan
Control report
6. Issue Management Report Deepak
7. Test report Test report document All

DATE SQA Tasks In charge Description Output

Evaluate project Software SQA planning
planning, specification report
05/08/23 tracking and Mannan review,
oversight estimation of
process schedule and
project plan
review
30/09/23 Review Review the Process audit
requirement Mannan software report
analysis requirement
development
10/12/23 Review test Review and SQA report,
design Mannan evaluate SQA review
document
10/12/23 Review release Deepak Process audit: SQA process
Final release audit report
10/12/23 Review project Deepak External review SQA process
closing audit report

1.3) Create schedule

Step 2: Define standards/methodology

1. Instructing the staff to use it
2. Document all the policies

Step 3: Review the process

VIII. Skills developed/ Learning outcomes
- Derive: Derive different possible solutions creatively.
- Data Collection: Collect relevant data from different sources (books/the internet/the
market/suppliers/experts and others through surveys/interviews)
- Designing- Designing microproject with minimum required resources and at low cost.
- Teamwork- Learning to work in team and boost individual confidence.
- Time management- Completion of microproject as scheduled.
- Technical writing- Preparing a report of proposed plan and report.
- Confidence: Confidently, answer the questions asked about the project.

IX. Applications of this microproject

- Software engineering project help us to define problem statement and understand the
project scope
- Identification of appropriate process model
- Preparing DFDs, ERDs, Test cases, Estimation techniques was learnt
- SQA plan development was learnt
 Micro Project Evaluation Sheet

Name of student: Ansari Abdullah Enrolment no: 2200020328

Name of programme: Computer Engineering Semester: 4th
Course title: Software Engineering Code: 22413
Title of microproject: RAILWAY RESERVATION SYSTEM
Course outcomes achieved:
i. Select suitable Software Process model for software development
ii. Prepare software requirement specification.
iii. Use software modelling to create data designs.
iv. Estimate size & cost of software product.
v. Apply project management and quality assurance principles in software development.

Comments/Suggestions about teamwork/leadership/interpersonal communication

___________________________________________________________________________
___________________________________________________________________________

Name and designation of teacher: _____________________________________________

Dated signature: ______________________
 Micro Project Evaluation Sheet

Name of student: Ansari Mohammed Zahoor Enrolment no: 2200020341

Name of programme: Computer Engineering Semester: 4th
Course title: Software Engineering Code: 22413
Title of microproject: RAILWAY RESERVATION SYSTEM
Course outcomes achieved:
i. Select suitable Software Process model for software development
ii. Prepare software requirement specification.
iii. Use software modelling to create data designs.
iv. Estimate size & cost of software product.
v. Apply project management and quality assurance principles in software development.

Comments/Suggestions about teamwork/leadership/interpersonal communication

___________________________________________________________________________
___________________________________________________________________________

Name and designation of teacher: _____________________________________________

Dated signature: ______________________
 Micro Project Evaluation Sheet

Name of student: Molapiya Nadeem Enrolment no: 2200020351

Name of programme: Computer Engineering Semester: 4th
Course title: Software Engineering Code: 22413
Title of microproject: RAILWAY RESERVATION SYSTEM
Course outcomes achieved:
vi. Select suitable Software Process model for software development
vii. Prepare software requirement specification.
viii. Use software modelling to create data designs.
ix. Estimate size & cost of software product.
x. Apply project management and quality assurance principles in software development.

Comments/Suggestions about teamwork/leadership/interpersonal communication

___________________________________________________________________________
___________________________________________________________________________

Name and designation of teacher: _____________________________________________

Dated signature: ______________________
 Micro Project Evaluation Sheet

Name of student: Sayyed Abdul Mannan Enrolment no: 2200020319

Name of programme: Computer Engineering Semester: 4th
Course title: Software Engineering Code: 22413
Title of microproject: RAILWAY RESERVATION SYSTEM
Course outcomes achieved:
i. Select suitable Software Process model for software development
ii. Prepare software requirement specification.
iii. Use software modelling to create data designs.
iv. Estimate size & cost of software product.
v. Apply project management and quality assurance principles in software development.

Comments/Suggestions about teamwork/leadership/interpersonal communication

___________________________________________________________________________
___________________________________________________________________________

Name and designation of teacher: _____________________________________________

Dated signature: ______________________
 Micro Project Evaluation Sheet

Name of student: Yadav Deepak Enrolment no: 2200020343

Name of programme: Computer Engineering Semester: 4th
Course title: Software Engineering Code: 22413
Title of microproject: RAILWAY RESERVATION SYSTEM
Course outcomes achieved:
i. Select suitable Software Process model for software development
ii. Prepare software requirement specification.
iii. Use software modelling to create data designs.
iv. Estimate size & cost of software product.
v. Apply project management and quality assurance principles in software development.

Comments/Suggestions about teamwork/leadership/interpersonal communication

___________________________________________________________________________
___________________________________________________________________________

Name and designation of teacher: _____________________________________________

Dated signature: ______________________