26-12-2012, 12:17 PM
Automated Ticketing System
[attachment=45244]
Introduction.
Purpose.
This document describes the software requirements for the Automated Railroad Reservation System built for the Automated Ticketing System (ATS).
Scope.
The ATS is requesting proposals to build a prototype of an Automated Ticketing System for their current system. The system will have a user-friendly PC based interface and will be more cost effective compared to the other. Today’s access control technology with ATS benefits to organizations of every size and scope. The ATS can save money or earn exact money for every visitor and improve security by automatically managing access at entrances. In future you can also safeguard critical information stored in your networks and databases. In an era of high security, you need advanced measures in place to protect this new functionality from internal and external threats. There will be an online portal where the report can be uploaded in a certain format defined by us (.xls, .csv, .txt etc. * any one format) the persons with proper access will be able to show it.
Client customer and other stakeholders.
• The Client: The person/organisation who pays for the product development.
• The Customer: The person/organisations who will use the product or who will benefit by the existence of the product.
• Stakeholders: The person/organisations that have a vested interest of the product
The General Description / Goals of the project.
This section describes the general factors that affect the product and its requirements. This section does not state specific requirements. Each of the subsections makes those requirements easier to understand; it does not specify design or express specific requirements. Such detail is provided in section 5.
Product Perspective.
Automated Ticketing System diagram showing the overview of the system’s modules and the relationship of the system to external interfaces is presented in Figure 2.1.
User Characteristics:
ATS administration that access the reports generated by the system. The visitors are not required to have knowledge in the computer field. The graphical interface provides an easy way of using the ATS system with minimum of training.
[attachment=45244]
Introduction.
Purpose.
This document describes the software requirements for the Automated Railroad Reservation System built for the Automated Ticketing System (ATS).
Scope.
The ATS is requesting proposals to build a prototype of an Automated Ticketing System for their current system. The system will have a user-friendly PC based interface and will be more cost effective compared to the other. Today’s access control technology with ATS benefits to organizations of every size and scope. The ATS can save money or earn exact money for every visitor and improve security by automatically managing access at entrances. In future you can also safeguard critical information stored in your networks and databases. In an era of high security, you need advanced measures in place to protect this new functionality from internal and external threats. There will be an online portal where the report can be uploaded in a certain format defined by us (.xls, .csv, .txt etc. * any one format) the persons with proper access will be able to show it.
Client customer and other stakeholders.
• The Client: The person/organisation who pays for the product development.
• The Customer: The person/organisations who will use the product or who will benefit by the existence of the product.
• Stakeholders: The person/organisations that have a vested interest of the product
The General Description / Goals of the project.
This section describes the general factors that affect the product and its requirements. This section does not state specific requirements. Each of the subsections makes those requirements easier to understand; it does not specify design or express specific requirements. Such detail is provided in section 5.
Product Perspective.
Automated Ticketing System diagram showing the overview of the system’s modules and the relationship of the system to external interfaces is presented in Figure 2.1.
User Characteristics:
ATS administration that access the reports generated by the system. The visitors are not required to have knowledge in the computer field. The graphical interface provides an easy way of using the ATS system with minimum of training.