Vision Document

Introduction
This vision document is to define the high-level scope and purpose of the ThBook System, product, or project. A clear statement of the problem, proposed solution, and the high-level features of the application will help establish expectations and reduce risks.

Positioning
A theater organises Events that Customers can register for. It needs to keep a record of these registrations. It also needs to allow multiple customer to register at the same time.

Product Perspective
This subsection of the Vision document puts the ThBook in perspective to other related products and the user’s environment. One easy way to display the major components of the larger system, interconnections, and external interfaces is with a block diagram.

Assumptions and Dependencies
List of assumptions that, if changed, will alter the Vision document.

Other Product Requirements
This section includes all requirements that have not been captured in the feature set.

Concurrency
The system must allow multiple simultaneous user activities (a user activity refers to a Use case scenarios) at all times.

Documentation Requirements
In order to increase the maintainability of the sytem, the following documentation artifacts must be provided :
 * A Design Document that will describe the system's architecture and design.
 * A User Manual
 * An Installation Manual that will provide instructions on how to deploy the application in a production environment.