Software Project Management Plan

Software Project Management Plan for “Automated Ticket
issuing System” for an Inter-city (City to City) Bus Service
1. The mission/objective of our system:
 Easily Purchasing Bus ticket using our software or in our website without traveling to the
bus station.
 Saving valuable times of passengers.
 Proper ticket and seat distribution without any black-marketing.
 Achieving proper management with Excellency in performance without having any
ticket counter.
 Proper guidelines for the travelers for their desired trip.
 Payment through via Credit/Debit card or bKash.
2. The problems in the current (manual) system are given below :-
 Purchasing bus tickets by traveling to the bus station.

 Delay of prevailing manual ticket issuing procedure.
 Poor management and performance at ticket counter.
 Long queue of passengers for purchasing tickets of their destination.
 Waste valuable times of the passengers in purchasing tickets.
 Sometimes, Ticket Black-Marketing also causes troubles to the passengers.
3. Identifying the requirements for our “Automated Ticket issuing System”

Software Project:
 24 hours per week ticketing service.

 Ticket availability information display.
 Bus arrival and departure time display.
 Multiple Ticket issue in one transaction.
 Limit the number of ticket issue at same time.
 Cancellation of transaction any time during transaction.
 Credit/Debit card transaction or bKash payment.
4. Choosing a Software Process Model:
RAD Model
RAD model is Rapid Application Development model. It is a type of incremental model.

In RAD, the components are developed in parallel manner. It is faster software
developer process. It generically describes applications that can be designed and
developed within 60-90 days. It was intended to describe a process of development that
involves applications prototyping.
Why this Model
 To save development time, possibly at the expense of economy or product quality.

 To limit a projects exposure to forces of change.
 In certain situation, a usable 80 % solution can be produce in 20 % of time that would
have been required to produce a total solution.
 To converge early toward a design acceptable to the customer and feasible for the
developers.
 To prevent cost overruns.
 To prevent runaway schedules.
5. Features of our product to be tested
 Touch screen monitor and keyboard interface.

 Touch screen menu selection.
 Displayed bus arrival and departure time information.
 Multiple ticket purchase support simultaneously.
 Limiting the number of tickets purchased at the same time by privilege control and
administrator access only.
 Ticket cancellation support before final confirmation of purchase.
 Ticket availability.
Testing Approach
 Identifying the requirements to be tested.
 Identifying which particular test will be used to each module.
 Review the test data and test cases to ensure that unit has been thoroughly verified.
 Identify the expected result for each test.
 Document the test data, test cases and test configuration used during the testing
process.
 Unsuccessful testing requires bug report form to be generated. This document will
describe the test case, the problem encountered, its possible cause and sequence of
events that led to program. It will be used as technical analysis.
Software Risk issues

 Ticket availability information display function to be tested.
 Touch screen menu selection should be test because if it is not working properly then
the whole process will be ruined.
 Transaction function should be tested. It is more than important.
 New version of product should be high risked to match with older one.
 Whole transaction safety issue.
 Real time access of client is big risk issue.
These type of risks are frequently meet with software process.
6. Product Maintenance:
UPDATE Description Price
New Versions Every Three Months Or when 100

needed
Hot fix release when needed 100
Manual - digital copy Every Three Months Free
SUPPORT Training New Employees 1 person per year Free
refresher courses 1 person per a year for a license by Free

our schedule
Reaction In case of a 10
time in problem
hours
On request for 10
training or
consultation
per month for license 1000

Software Project Management Plan

Uploaded by

Copyright:

Available Formats

Software Project Management Plan

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Project Management Plan

Uploaded by

Copyright:

Available Formats

What problems does the current manual ticket issuing system have?

What problems does the current manual ticket issuing system have?

What requirements were identified for the automated ticket issuing system?

What requirements were identified for the automated ticket issuing system?

Software Project Management Plan for “Automated Ticket

issuing System” for an Inter-city (City to City) Bus Service

1. The mission/objective of our system:

2. The problems in the current (manual) system are given below :-

 Purchasing bus tickets by traveling to the bus station.

3. Identifying the requirements for our “Automated Ticket issuing System”

 24 hours per week ticketing service.

RAD model is Rapid Application Development model. It is a type of incremental model.

Why this Model

 To save development time, possibly at the expense of economy or product quality.

5. Features of our product to be tested

 Touch screen monitor and keyboard interface.

Software Risk issues

These type of risks are frequently meet with software process.

New Versions Every Three Months Or when 100

Hot fix release when needed 100

Manual - digital copy Every Three Months Free

SUPPORT Training New Employees 1 person per year Free

refresher courses 1 person per a year for a license by Free

per month for license 1000

You might also like