Vision and Scope Document

for

Coach Ticket Ordering

Management System
Version 1.0 approved

Prepared by Group 3

FPT UNIVERSITY

June 17, 2019

Copyright © 2013 by Karl Wiegers and Seilevel

Vision and Scope for Cafeteria Ordering System Page 1

Table of Contents
Table of Contents ................................................................................................................ 1
Revision History ................................................................Error! Bookmark not defined.
1. Business Requirements ................................................................................................. 1
1.1. Background ............................................................................................................ 1
1.2. Business Opportunity ............................................................................................ 1
1.3. Business Objectives ............................................................................................... 2
1.4. Success Metrics ..................................................................................................... 2
1.5. Vision Statement.................................................................................................... 2
1.6. Business Risks ....................................................................................................... 2
1.7. Business Assumptions and Dependencies ............................................................. 3
2. Scope and Limitations................................................................................................... 3
2.1. Major Features ....................................................................................................... 3
2.2. Scope of Initial and Subsequent Releases ............................................................. 4
2.3. Limitations and Exclusions ..................................Error! Bookmark not defined.
3. Business Context........................................................................................................... 5
3.1. Stakeholder Profiles ............................................................................................... 5
3.2. Project Priorities .................................................................................................... 6
3.3. Deployment Considerations .................................................................................. 6

1. Business Requirements
1.1. Background
Nowadays, the number of people travel by coach is increasing rapidly. However, tickets booking
procedure is difficult for both coach station and the customers. Normally to get to the coach
station, a customer needs get to the ticket retailer by some means of transportation. Leads to
waste of transportation time and money. And when the customer got to the station, he or she still
have to wait in a very long queue before they can buy the ticket. Taking advantage of the
situation, a lot of thievery happens. On the other hand, with the traditional tickets ordering
management method, the coach station cannot handle effectively. For instance, spending too
much money on phone calls and cheating, the lack of customer’s information and all the data is
still stored on papers.

1.2. Business Opportunity

Many ticket buyers have requested an alternative method that would permit them to book coach
tickets without having to go to the coach station. Such a method would save buyers time and
money, and it also helps booking ticket more initiative. In terms of the coach managers, their
revenue will increase dramatically due to the increase of tickets buyers. Automating work
procedure. Human resource management will become more efficiently. Furthermore, user’s data
will be exploited and standardized, reduce the cost in making phone calls and cheating wastage
and the company will look more professional.

Copyright © 2013 by Karl Wiegers and Seilevel

Vision and Scope for Cafeteria Ordering System Page 2

1.3. Business Objectives

BO-1: Reduce the cost in human resource by 20% within 3 months following initial release.
BO-2: Reduce coach station operating costs by 15% within 12 months following initial release.
BO-3: Reduce the cost of making phone calls and cheating by 50%.
BO-4: Increase the revenue by 20% every year.
BO-5: Increase the number of potential customers by 45%.

1.4. Success Metrics

SM-1: 80% number of people who travel by coach at least 5 times per month during Q4 2019 use
the Coach Tickets Ordering Management System at least once in 5 travels within 6
months following initial release.
SM-2: 15% of the coach station revenue will be increased from the Q2 2019.
SM-3: The average rating on the quarterly coach booking satisfaction survey increases by 0.5 on
a scale of 1 to 6 from the Q2 2019 rating within 2 months following initial release and by
1.0 within 12 months.
SM-4: The amount of money wasted in making phone calls decreases 70% in the first month
after release and continue to decrease significantly.

1.5. Vision Statement

For the coach stations who are having difficulties in managing their tickets, the Coach Tickets
Ordering Management System is a management system that will provide a convenient and
effective method to manage tickets. The system will be a marketplace for coach tickets. It will
automate the ticket transactions and store all the related data. This will save 20% company costs
on human resource. Unlike the current manual ordering processes, our product will manage the
tickets automatically and store all information in the system instead of papers.

For the ticket buyers who are having difficulties in booking their tickets, the CTOMS is a
marketplace that will provide a fast and easy method to buy tickets. The system will show all the
available coach trips as well as the remaining seats. The customers will be able to buy the tickets
online on computers or smart phones. This will save 90% total booking time. Unlike the current
manual ordering processes, our product will allow to buy coach tickets from anywhere that
have access to the internet.

1.6. Business Risks

RI-1: The CTOMS might require the customers to have access to internet and smart devices to
book tickets (Probability = 0.6; Impact = 3)
RI-2: Too few employees might use the system, reducing the return on investment from the
system development and the changes in cafeteria operating procedures. (Probability = 0.3;
Impact = 9)
RI-3: Local restaurants might not agree to offer delivery, which would reduce employee
satisfaction with the system and possibly their usage of it. (Probability = 0.3; Impact = 3)

Copyright © 2013 by Karl Wiegers and Seilevel

Vision and Scope for Cafeteria Ordering System Page 3

RI-4: Sufficient delivery capacity might not be available, which means that employees would
not always receive their meals on time and could not always request delivery for the
desired times. (Probability = 0.5; Impact = 6).

1.7. Business Assumptions and Dependencies

AS-1: Systems with appropriate user interfaces will be available for cafeteria employees to
process the expected volume of meals ordered.
AS-2: Cafeteria staff and vehicles will be available to deliver all meals for specified delivery
time slots within 15 minutes of the requested delivery time.
DE-1: If a restaurant has its own on-line ordering system, the Cafeteria Ordering System must be
able to communicate with it bi-directionally.

2. Scope and Limitations

2.1. Major Features
FE-1: Order and pay for tickets from the mobile app or website.
FE-2: Create, view, modify, delete, and archive coach tickets and coach trips.
FE-3: View the available trips and seats.
FE-4: Provide system access through corporate intranet, smartphone, tablet, and outside Internet
access by authorized employees.
FE-5: Make statistics of revenue annually.

Figure 1. Partial feature tree for the Coach Ticket Ordering Management System.

Copyright © 2013 by Karl Wiegers and Seilevel

Vision and Scope for Cafeteria Ordering System Page 4

2.2. Scope of Initial and Subsequent Releases

Feature Release 1 Release 2 Release 3

FE-1, Order and pay or Buy and pay for tickets Refund bought tickets Fully implemented
refund for tickets
from the mobile
app or website.

FE-2, Provide system Windows, Linux, macOS Android phones and tablets iOS phones and tablets.
access through
corporate intranet,
smartphone, tablet,
and outside Internet
access by authorized
employees.
FE-3, Create, modify, Create, modify, delete, tickets Archive tickets Fully implemented
delete, and
archive coach
tickets and coach
trips.

FE-4, View the View available seats. Fully implemented

available trips
and seats.

Copyright © 2013 by Karl Wiegers and Seilevel

Vision and Scope for Cafeteria Ordering System Page 5

FE-5, Make statistics Retrieve statistics. Make statistics Fully implemented

of revenue annually.

3. Business Context
3.1. Stakeholder Profiles

Stakeholder Major Value Attitudes Major Interests Constraints

Corporate Improved employee Strong commitment Cost and employee None identified
Management productivity; cost through release 2; time savings must
savings for cafeteria support for release 3 exceed development
contingent on earlier and usage costs
results
Cafeteria Staff More efficient use of Concern about union Job preservation Training for staff in
staff time throughout relationships and Internet usage
the day; higher possible downsizing; needed; delivery staff
customer satisfaction otherwise receptive and vehicles needed
Patrons Better food selection; Strong enthusiasm, Simplicity of use; Corporate intranet
time savings; but might not use it as reliability of delivery; access, Internet
convenience much as expected availability of food access, or a mobile
because of social choices device is needed
value of eating
lunches in cafeteria
and restaurants
Payroll No benefit; needs to Not happy about the Minimal changes in No resources yet
Department set up payroll software work current payroll committed to make
deduction registration needed, but applications software changes
scheme recognizes the value
to the company and
employees
Restaurant Increased sales; Receptive but Minimal new Might not have staff
Managers marketing exposure to cautious technology needed; and capacity to handle
generate new concern about order levels; might not
customers resources and costs have all menus online
of delivering meals

Copyright © 2013 by Karl Wiegers and Seilevel

Vision and Scope for Cafeteria Ordering System Page 6

3.2. Project Priorities

Dimension Constraint Driver Degree of Freedom

Features All features scheduled for

release 1.0 must be fully
operational
Quality 95% of user acceptance tests
must pass; all security tests
must pass
Schedule release 1 planned to be
available by end of Q1 of next
year, release 2 by end of Q2;
overrun of up to 2 weeks
acceptable without sponsor
review
Cost budget overrun up to 15%
accept able without sponsor
review
Staff team size is half-time project
manager, half-time BA, 3
developers, and 1 tester;
additional developer and half-
time tester available if necessary

3.3. Deployment Considerations

The web server software will need to be upgraded to the latest version. Apps will have to be
developed for iOS and Android smartphones and tablets as part of the second release, with
corresponding apps for Windows Phone and tablets to follow for the third release. Any
corresponding infrastructure changes must be in place at the time of the second release. Videos
no more than five minutes in length shall be developed to train users in both the Internet-based
and app-based versions of COS.

Copyright © 2013 by Karl Wiegers and Seilevel