Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 17

Panchsal Nimesh

Group Members: Gohil Hardik


Aghara Vasudev

ONLINE RAILWAY TICKET RESERVATION


SYSTEM
SUBSYSTEMS:
Ticket Reservation Management System
Customer can reserve the ticket
Customer can cancel the ticket
Customer can cancel the Railway
Admin can cancel the Railway
Admin can change arrival or departure time
Admin can update the Railway detail
FUNCTION..
 Register
 Customer can sign up or sign in
 Customer can recover the password
 Customer can change the password
 Admin approval the customer
 Admin can update the user
COUNTD.

 
 Time Table
 User can view the Railway the time table
 Admin can update the Railway time table
 System can give output for relating search
COUNTD.

 Railway Detail
 User can view the Railway detail
 Admin can update the Railway time table
COUNTD.
 Agent
 New Agent can join the System
 Admin can approve the new agent
 Admin can delete or edit the all agent’s detail
 Agent can reserve the ticket or book bus/buses
 Admin has all details of all agents
 Agent can give some suggestion to which time
customer want to more buses
 Admin can approve the agent require buses
COUNTD.
 Searching for Railway
 User can searching Railway for a entering source and
destination
 System can give output for relating search
GENERIC PROCESS FRAMEWORK
 Requirements Gathering:
 Prepare the questionnaire ticket giver for knowing the
problems.
 Interviewing the ticket for the new system what
features we have to include.
 Prepare the questionnaire for some of the customer to
know what kind of problems they are facing.
COUNTD.
 Project Conception:
 Defining the scope of the project.
 Doing the feasibility study of the project.
 Detailing the cost will incurred in the project.
 Detailing the technical specifications in the project.
PLANNING
 Resources:
 Find appropriate resources needed.
 Allocate the resources.
COUNTD.
 Scheduling:
 After allocation of resources find the dependences of
the resources and the activities associated with each
resource.
 Prepare GANTT chart for scheduling the activities.
 Prepare the PERT diagram for estimating the time for
whole project as well as finding the Critical path.
COUNTD.
 Risk management:
 Brainstorm Potential risks.
 Estimate the impact of each risk.
 Build the risk plan.
MODELING:
 UML:
 Make textual use cases.
 Make use diagrams
 Find out the classes and separate them.
 Make class dependency diagram.
 Interaction:
 Make interaction diagram based on class dependency
diagram.
 Make state transition diagram based on interaction diagram.
DEPLOYMENT:
 Deploy:
 Test the software and find out the errors.
 Rectify the errors if any.
 Deploy the software on client machine.
 Feedback and Maintenance:
 Get the feedback about the software.
 Rectify the errors or any other problem if any.
 Deploy the upgrades if any.
PROCESS MODEL
 Spiral Model
 Iterative model
 We can do changes in previous iteration.
PROCESS PATTERNS
 Process pattern define a set of activities, actions,
work tasks, work products and related behaviors.
 A process pattern provides us with a template
 For example
 Customer communication (a process activity)
 Analysis (an action)
 Requirements gathering (a process task)
 Reviewing a work product (a process task)
 Design model (a work product)
THANK YOU

You might also like