Online Railway Reservation System_Documentation.pdf

7/31/2019 Online Railway Reservation System_Documentation.pdf

1/25


2/25

Index

1. Abstract2. Project Organization3. Methods and Tools4. Software Project Estimation using Function

Point5. Risk Management6. Scope7. Requirement8. Data Model

9. Function Model10. Conclusion11. Reference


3/25

Abstract (Problem Statement)

Information about the route, cancellation of tickets,departure time, arrival time, number of trains availableand other such information are provided.

Store and retrieve information about the varioustransactions related to Rail travel.

Keep track of all its passengers and thus schedule their journey accordingly.

Maintains records of passengers travelling in thedifferent trains on different dates reaching differentdestinations in the system.

User can enquire about the PNR status, seat availabilityand trains on a route.

User friendly interface to administrator and customer.


4/25

Spiral Model

Spiral Development Model

The spiral model is a software development processcombining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts. This model of development combines the features of the prototypingmodel and the waterfall model. The spiral model isintended for large, expensive and complicatedprojects.

A spiral model is divided into a number of frameworkactivities Typically, there are between three and sixtask regions. Fig depicts a spiral model that containssix task regions:


5/25

Customer Communication: Tasks required toestablish effective communication betweendeveloper and customer.

Planning : Tasks required to define resources,timelines, and other project related information.

Risk analysis : Tasks required to assess bothtechnical and management risks.

Engineering : Tasks required to build one or morerepresentations of the application.

Construction and release : Tasks required toconstruct, test, install, and provide user support(e.g., documentation and training).

Customer evaluation : Tasks required to obtaincustomer feedback based on evaluation of thesoftware representations created during the

engineering stage and implemented during theinstallation stage.

The following diagram illustrates the information,document and product flow between the lifecycleprocess.


6/25

Work Breakdown Structure

Identify ActivitiesProject is divided into major activities. The activities shouldbe neither too small nor too long.

1. Communication: It involves meeting with stakeholders, and communicate their requirements,information, and specific needs.In this project the specified needs are:-

Databases required Categories of trains

Information about the working of the system


7/25

2. Planning: With reference to the information gatheredplanning is done to determine how the system willwork.

It includes:- Planning about booking Planning about cancellation Planning about enquiry Planning about the availability status

Planning about PNR Generation

3. Data Dictionary, ERD and DFD: Different databases of the system are decided and the entity relationship anddata floe diagram is generated.

Database of trains Database of PNR No. Database of registered accounts Transaction database

4. Design: Layout of the railway system is made whichacts as an interface to the user.

5. Testing and Construction: Testing is done to check thereliability of the code and the project.


8/25

6. Deployment: The project is developed at thecustomers workplace explai ning the user about thefunctionality of the project.

Dependencies

Tasks and subtasks have dependencies based on theirsequencing that is, starting one task will depend on thecompletion of another task.

In the Online Railway Reservation System thedependencies will be

Communication Planning

Planning Data Dictionary, ERD, DFD and Design

Design Testing and Construction

Testing and Construction Deployment and UserFeedback


9/25

1.Dependency Diagram


10/25

Schedule Allocation

Software project scheduling is an activity thatdistributes estimated effort across the plannedproject duration by allocating the effort to specificsoftware engineering tasks.

Furthermore these activities are made concreteand the schedule along with start date, end date

and duration is made.

Activity Time Allocated Resource Gathering 3 days Cost Estimation 2 days

Project Scheduling 3 days Risk Management 3 days Backend Coding 10 days Frontend Coding 7 days Module Coding 7 days Testing 8 days Backend Refinement 4 days Frontend Refinement 3 days Deployment 3 days

Total 31 days


11/25

Resource Allocation

This distributes the work and responsibilities among the

team members. The Resource Allocation Table is as below:

SrNo.

Phase of SDLC TeamMembersInvolved

Responsibility

ResourceGathering

AkshatAman

Prepare report of the initialdeveloper meeting, SRSdocument

Analysis Anubhav Project Plan with effort and costestimation

Design AmanAkshat Prepare case diagram withspecifications, Data Flow Diagram,Activity Diagram

Implementation AmanAkshatAnubhav

Develop Source Code of the System

Testing Akshat Prepare Testing document

Deployment AnubhavAkshatAman

Deliver System as an installablepackage, User manual and guide


12/25

Timeline Chart

Activity Chart


13/25

Methods and Tools

Development Methodology:

The project shall use the spiral software developmentmethodology to deliver the software products.The decision to use the Spiral methodology is due tothe following characteristics of the project:

The product definition is stableRequirements and implementation of theproduct are both very well-understoodTechnical tools and hardware technology arefamiliar and well-understoodWaterfall methodology has proven successfulfor projects of this nature

Tools:

MySQL for database creation OLEDB for integration of databases PHP and java script for web pages and interfacing Microsoft Office


14/25

Context Diagram

Effort and Cost Estimation: Function Point

Fi Calculation:

Factor Value

Backup and recovery 5Data communications 5Distributed processing 3Performance critical 4Existing operating environment 4


15/25

On-line data entry 5Input transaction over multiple screens 4Master files updated on-line 4Information domain values complex 5Internal processing complex 5Code designed for reuse 4Conversion/installation in design 4Multiple installations 5Application designed for change 5

Total 62

Count Total

Domain Count Complex TotalNo. of user inputs 8 6 48No. of user outputs 2 7 14No. of user inquiries 2 6 12No. of files 4 15 60No. of external interfaces 1 10 10Total 144

FP=Count Total (0.65+0.01*62)

FP=144*(1.27)

FP=182.88FP~=183


16/25

Cost per FP=$500

Total Cost=Cost/FP*FP

Total Cost=$500*183

Total Cost=$91500

Productivity=5 FP/PM

Effort=FP/Productivity

Effort=183/5 PMEffort=36.6 PM

Effort=~37 PM

The total cost is $91,500 and effort is 37 PM.


17/25

Risk Management

Risk Description

Project Risks Identifies potential budgetary,schedule, personnel (staffing andorganization), resource, customer, andrequirements problems and their impact on a software project. Itthreatensthe project plan. That is, if project risksbecome real, it is likely that projectschedule will slip and that costs willincrease.

Technical Risks Identifies potential design,implementation, interface, verification,and maintenance problems. Technicalrisks threaten the quality andtimeliness of the software to beproduced. If a technical risk becomes areality, implementation may become

difficult or impossible.Market Risks Building a excellent product or system

that no one really wants

Budget Risks Losing budgetary or personnelcommitment

Known Risks Those that can be uncovered after careful evaluation of the project plan.

Predictable Risks Extrapolated from past projectexperience

Unpredictable Risks They can and do occur, but they areextremely difficult to identify inadvance.

Support Risks The degree of uncertainty that theresultant software will be easy tocorrect, adapt, and enhance.

Schedule Risks The degree of uncertainty that theproject schedule will be maintained

and that the product will be deliveredon time.


18/25

System Requirement Specification

Scope

The idea of efficient reservation is expected to prove veryuseful in the daily life of passengers as compared to theconventional system. If it turns out as expected, then it

would create a huge impact on the turnaround of passengers toward the railways, increasing their level of trust.

Specific Hardware Requirements

Intel Dedicated Server Family

High Speed Storage

Dedicated lines for connectivity

Network Storage

Printer

Monitor and other general peripherals


19/25

Data Model and Description

Entity Relationship Diagram


20/25

Functional Model and Description

User Level 1


21/25

Admin Level 1


22/25

User Level 2


23/25


24/25

Conclusion

The proposed system is error free, stable and capable of

Handling load at the server even in the peak hours withoutlosing stability or giving a down time.

The software provides security to the user, administratorand the server.

As for the user, the task of booking, cancelling a ticket ormaking an enquiry is made much easier and hassle free.

Reference

The material has been taken from the following places:

www.wikipedia.org

www.Scribd.com www.Handouts.org www.google.com
http://www.wikipedia.org/http://www.wikipedia.org/http://www.scribd.com/http://www.scribd.com/http://www.handouts.org/http://www.handouts.org/http://www.google.com/http://www.google.com/http://www.google.com/http://www.handouts.org/http://www.scribd.com/http://www.wikipedia.org/


25/25

Documents

Online Railway Reservation System_Documentation.pdf