Vision and Scope Document

for

Movie Ticket Booking System

Version 1.0 approved

Prepared by Karl Wiegers

Process Impact

August 22, 2013

Copyright © 2013 by Karl Wiegers and Seilevel

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

Vision and Scope

1.1. Background
The movie ticket booking system is being developed to replace outdated
manual ticketing processes. It aims to solve problems like long queues,
limited seat availability information, and poor customer experience. The
rise of digital solutions and the need for convenience make this system
essential.
1.2. Business Opportunity

The system addresses the need for a modern, user-friendly platform for
booking movie tickets. Current solutions lack features like real-time seat
availability, personalized recommendations, and integration with other
services. The target market includes moviegoers who want convenience
and cinema operators looking to improve efficiency and sales.

1.3. Business Objectives

Copyright © 2013 by Karl Wiegers and Seilevel

  Achieve 90% customer satisfaction.
 Reduce booking time from 10 minutes to 2 minutes.
 Increase seat occupancy from 70% to 85%.

1.4. Success Metrics

 80% of tickets sold online within 6 months.

 5 minutes average session time on the platform.
 50% reduction in manual errors.

1.5. Vision Statement

For customer who want a convenient booking experience, the Movie

Ticket Booking System is a digital platform that offers real-time seat
availability, secure payments, and personalized recommendations.
Unlike traditional systems, our product provides advanced features like
dynamic pricing and loyalty programs, ensuring a better experience for
customers and efficiency for cinema operators.

1.6. Business Risks

1.6.1. Competition
Risk: Competitors may launch better solutions.
Mitigation: Add unique features like AI recommendations.

1.6.2. Technical Issues

Risk: Problems integrating with existing systems.
Mitigation: Test thoroughly the programs.

1.6.3. Failure to Meet Expectations

Risk: System underperforms, hurting reputation.
Mitigation: Set realistic goals and monitor performance.

Copyright © 2013 by Karl Wiegers and Seilevel

Functional Requirements
For Guests:
1. View Movies List: The system shall display a list of currently available
movies.
2. View Movie Information: The system shall show details (e.g., title,
description, rating, cast) for a selected movie.
3. View Movie Showtime: The system shall display showtimes for a selected
movie.
4. Signup/Login: The system shall allow users to create an account or log in to
an existing account.

For Customers:
5. View List Movies: The system shall display a list of available movies.
6. View Movie Information: The system shall show detailed information for a
selected movie.
7. View Movie Showtime: The system shall display showtimes for a selected
movie.
8. Create Booking: The system shall allow customers to book tickets for a
selected showtime.
9. Assign Seat: The system shall allow customers to select and assign seats for
their booking.
10.Manage Account: The system shall allow customers to update their account
details (e.g., name, password, payment methods).

For Admin:
11.Modify Ticket Price: The system shall allow admins to update ticket prices
for movies or showtimes.
12.View Revenue: The system shall display revenue reports (e.g., daily, weekly,
monthly).

Copyright © 2013 by Karl Wiegers and Seilevel

 13.Add Movie: The system shall allow admins to add new movies to the
system.
14.Modify Movie: The system shall allow admins to edit movie details (e.g.,
title, description, rating).
15.Add Showtime: The system shall allow admins to add new showtimes for
movies.
16.Modify Showtime: The system shall allow admins to edit existing
showtimes.

For Manager:
17.Create Booking: The system shall allow managers to create bookings on
behalf of customers.
18.Assign Seat: The system shall allow managers to assign seats for bookings.
19.Manage Seat: The system shall allow managers to add, remove, or modify
seat arrangements in cinema rooms.
20.Manage Cinema Room: The system shall allow managers to add, remove, or
modify cinema rooms.
21.Change Customer Account Status: The system shall allow managers to
activate, deactivate, or modify customer accounts.

Use Case
Primary Actor Use cases
Guest 1. View Movies List
2. View Movie Information
3. View Movie Showtime
4. Signup/Login
Customer 5. View List Movies
6. View Movie Information
7. View Movie Showtime
8. Create Booking

Copyright © 2013 by Karl Wiegers and Seilevel

 9. Assign seat
10.Manage Account
Admin 11.Modify ticket price
12.View Revenue
13.Add Movie
14.Modify Movie
15.Add Showtime
16.Modify Showtime

Manager 17.Create Booking

18.Assign Seat
19.Manage Seat
20.Manage Cinema Room
21.Change Customer Account
Status

Use case diagram

Copyright © 2013 by Karl Wiegers and Seilevel

Use Case ID UC-1
Use Case Name Sign up/Login
Description This use case allows a guest to sign up
for a new account or log into an
existing account to gain access to
customer-specific features like booking
tickets, managing their account
Primary Actor Guest
Secondary Actor None

Copyright © 2013 by Karl Wiegers and Seilevel

Trigger The guest wants to create a new
account or access their existing
account on the system.
Preconditions The guest has a valid email and
password (for login) or necessary
information to create a new account
(for signup)
Postcondition If successful, the guest is logged in and
can access features only available to
registered users (e.g., booking tickets,
managing the account).
If signup is successful, a new customer
account is created and the guest is
logged in.
If login fails, an error message is
shown.
Main Flow 1. Guest navigates to the
"Signup/Login" page.
2. Guest selects whether to "Sign
Up" or "Log In".
3. If "Sign Up" is selected:
 Guest enters required
information (e.g., email,
password, etc.).
 System validates the input and
checks if the email is already in
use.
 If valid, the system creates a
new account and logs the guest
in.
4. If "Log In" is selected:
 Guest enters their email and
password.
 System verifies the credentials.
 If credentials are valid, the
system logs the guest into their
account.

Copyright © 2013 by Karl Wiegers and Seilevel

 5. The guest is redirected to the
homepage/dashboard where
they can access customer-
specific features.

Use Case ID UC-2

Use Case Name View List Movies
Description The guest or customer can view a list
of available movies.
Primary Actor Guest, Customer
Secondary Actor None
Trigger The user wants to see the list of
available movies.
Preconditions The user has access to the website or
application.
Movies are available in the system.
Postcondition The user is presented with a list of
movies currently available.
Main Flow The user navigates to the "Movies"
section.
The system displays a list of available
movies.
The user can scroll and browse the list.

Use Case ID UC-3

Use Case Name View Movie Information
Description The guest or customer can view
detailed information about a specific
movie.
Primary Actor Guest, Customer
Secondary Actor None
Trigger The user wants to view more details
about a specific movie.

Copyright © 2013 by Karl Wiegers and Seilevel

Preconditions The user has accessed the movie list.
The user selects a specific movie.
Postcondition The system displays detailed
information for the selected movie
Main Flow 1. The user clicks on a movie from the
list.
The system displays the detailed movie
information.

Use Case ID UC-4

Use Case Name View Movie Showtime
Description The guest or customer can view the
available showtimes for a specific
movie.
Primary Actor Guest, Customer
Secondary Actor None
Trigger The user wants to know the showtimes
for a specific movie.
Preconditions The user has accessed the movie list.
The system has available showtimes
for the selected movie.
Postcondition The system displays a list of available
showtimes for the selected movie.
Main Flow The user selects the movie for which
they want to view showtimes.
The system displays the available
showtimes for the movie.

Use Case ID UC-5

Use Case Name Create Booking
Description The customer can book tickets for a
selected movie.
Primary Actor Customer
Secondary Actor None
Trigger The customer wants to book tickets for

Copyright © 2013 by Karl Wiegers and Seilevel

 a movie.
Preconditions The customer is logged in.
The customer has selected a movie
and a showtime.
Postcondition The booking is created and saved in
the system.
Main Flow 1. The customer selects a movie
and showtime.
2. The customer proceeds to
booking.
3. The system prompts for
payment and seat selection.
4. The customer confirms the
booking.
5. The system finalizes the booking
and provides confirmation.

Use Case ID UC-6

Use Case Name Assign Seat
Description The customer can select a seat for
their movie booking.
Primary Actor Customer
Secondary Actor None
Trigger The customer is in the process of
booking tickets and needs to select a
seat.
Preconditions The customer is logged in.
The customer has selected a movie
and a showtime.
Postcondition The customer’s seat is selected and
saved with the booking.
Main Flow 1. The customer choose a seat for
the movie.
2. The system displays available
seats.

Copyright © 2013 by Karl Wiegers and Seilevel

 3. The customer selects a seat.
4. The system updates the seat
availability.

Use Case ID UC-7

Use Case Name Manage Account
Description The customer can update and manage
their account details.
Primary Actor Customer
Secondary Actor None
Trigger The customer wants to update
personal information or settings on
their account.
Preconditions The customer is logged in.
Postcondition The customer's account details are
updated.
Main Flow 1. The customer navigates to the
account settings page.
2. The customer updates the
information.
3. The system saves and confirms
the changes.

Use Case ID UC-8

Use Case Name Modify Ticket Price
Description The admin can modify the price of
movie tickets.
Primary Actor Admin
Secondary Actor None
Trigger The admin wants to change the ticket
prices.
Preconditions The admin is logged in.
Postcondition The system updates the ticket price.
Main Flow 1. The admin navigates to the
ticket management section.
2. The admin enters the new ticket

Copyright © 2013 by Karl Wiegers and Seilevel

 price.
3. The system updates the ticket
prices.

Use Case ID UC-9

Use Case Name View Revenue
Description The admin can view the revenue
generated from ticket sales.
Primary Actor Admin
Secondary Actor None
Trigger The admin wants to view the revenue.
Preconditions The admin is logged in.
Revenue data is available.
Postcondition The system updates the ticket price.
Main Flow 1. The admin navigates to the
revenue dashboard.
2. The system displays the revenue
information.

Use Case ID UC-10

Use Case Name Add Movie
Description The admin can add a new movie to the
system.
Primary Actor Admin
Secondary Actor None
Trigger The admin wants to add a new movie.
Preconditions The admin is logged in.
The admin has necessary information
for the new movie.
Postcondition The new movie is added to the system.
Main Flow 1. The admin navigates to the "Add
Movie" section.
2. The admin enters details about
the movie (e.g., title,
description, rating, etc.).
3. The system adds the movie to

Copyright © 2013 by Karl Wiegers and Seilevel

 the list of available movies.

Use Case ID UC-11

Use Case Name Modify Movie
Description The admin can modify the details of an
existing movie.
Primary Actor Admin
Secondary Actor None
Trigger The admin wants to modify a movie's
details.
Preconditions The admin is logged in.
The movie to be modified exists in the
system.
Postcondition The movie details are updated.
Main Flow 1. The admin selects a movie to
modify.
2. The admin updates the movie
details.
3. The system saves the changes.

Use Case ID UC-12

Use Case Name Add Showtime
Description The admin can add a new showtime
for a movie.
Primary Actor Admin
Secondary Actor None
Trigger The admin wants to add a new
showtime for a movie.
Preconditions The admin is logged in.
The movie to be modified exists in the
system.
Postcondition A new showtime is added for the
movie.
Main Flow 1. The admin selects a movie.
2. The admin adds a new showtime
(e.g., date, time).

Copyright © 2013 by Karl Wiegers and Seilevel

 3. The system saves the new
showtime.

Use Case ID UC-13

Use Case Name Modify Showtime
Description The admin can modify the existing
showtimes for a movie.
Primary Actor Admin
Secondary Actor None
Trigger The admin wants to modify an existing
showtime.
Preconditions The admin is logged in.
The movie and showtime exist in the
system.
Postcondition The showtime details are updated.
Main Flow 1. The admin selects the movie
and showtime to modify.
2. The admin updates the
showtime details.
3. The system saves the changes.

Use Case ID UC-14

Use Case Name Create Booking
Description The manager can create a booking for
a customer.
Primary Actor Manager
Secondary Actor Customer
Trigger The manager is assisting the customer
in making a booking.
Preconditions The manager is logged in.
The customer has chosen a movie and
showtime.
Postcondition A booking is created for the customer.
Main Flow 1. The manager selects the movie
and showtime.
2. The system prompts for seat

Copyright © 2013 by Karl Wiegers and Seilevel

 selection and customer details.
3. The manager completes the
booking process.

Use Case ID UC-15

Use Case Name Assign Seat
Description The manager can assign seats for a
customer’s booking.
Primary Actor Manager
Secondary Actor Customer
Trigger The manager is assisting with seat
selection for a customer’s booking.
Preconditions The manager is logged in.
The customer has a booking.
Postcondition The seat is assigned to the customer’s
booking.
Main Flow 1. The manager selects the
booking.
2. The manager assigns an
available seat.
3. The system updates the booking
with the assigned seat.

Use Case ID UC-16

Use Case Name Manage Seat
Description The manager can manage available
seats in the cinema.
Primary Actor Manager
Secondary Actor None
Trigger The manager wants to manage or
adjust seating availability.
Preconditions The manager is logged in.
The cinema room has been set up with
seats.

Copyright © 2013 by Karl Wiegers and Seilevel

Postcondition The seat availability is adjusted.
Main Flow 1. The manager navigates to the
seating management section.
2. The manager adjusts seating
availability.
3. The system saves the changes.

Use Case ID UC-17

Use Case Name Manage Cinema Room
Description The manager can manage cinema
room.
Primary Actor Manager
Secondary Actor None
Trigger The manager needs to adjust the
configuration of a cinema room.
Preconditions The manager is logged in.
Postcondition The cinema room configuration is
updated.
Main Flow 1. The manager navigates to
cinema room management.
2. The manager adjusts the room
layout or seating.
3. The system saves the
configuration changes.

Use Case ID UC-18

Use Case Name Change Customer Account Status
Description The manager can change the status of
a customer's account
Primary Actor Manager
Secondary Actor None
Trigger The manager needs to change the
status of a customer’s account.
Preconditions The manager is logged in.

Copyright © 2013 by Karl Wiegers and Seilevel

Postcondition The customer’s account status is
updated.
Main Flow 1. The manager navigates to the
customer’s account.
2. The manager changes the status
(e.g., deactivate or activate).
3. The system saves the change.

Design user interface

1. Administrator page
1.1. Revenue Statistic

1.2. Cinema List

Copyright © 2013 by Karl Wiegers and Seilevel

1.3. Cinema Management

1.4. Room list

Copyright © 2013 by Karl Wiegers and Seilevel

1.5. Room Management

Copyright © 2013 by Karl Wiegers and Seilevel

1.6. Showtime List

1.7. Showtime Management

Copyright © 2013 by Karl Wiegers and Seilevel

1.8. Movie Management

1.9. List of seat

Copyright © 2013 by Karl Wiegers and Seilevel

1.10. Seat Management

Copyright © 2013 by Karl Wiegers and Seilevel

 1.11. List of Seat Type

2. Customer page
2.1. Login/Signup

Copyright © 2013 by Karl Wiegers and Seilevel

Copyright © 2013 by Karl Wiegers and Seilevel
2.2. Homepage

Copyright © 2013 by Karl Wiegers and Seilevel

2.3. Movie list

Copyright © 2013 by Karl Wiegers and Seilevel

2.4. Movie details

Copyright © 2013 by Karl Wiegers and Seilevel

2.5. Create booking

Copyright © 2013 by Karl Wiegers and Seilevel

2.6. Seat selection

Copyright © 2013 by Karl Wiegers and Seilevel

2.7. Checkout

Copyright © 2013 by Karl Wiegers and Seilevel

2.8. List Available Cinema

Copyright © 2013 by Karl Wiegers and Seilevel

2.9. List Cinema Room

Copyright © 2013 by Karl Wiegers and Seilevel

Design Database

Copyright © 2013 by Karl Wiegers and Seilevel

Copyright © 2013 by Karl Wiegers and Seilevel