National Tours Online Tour Reservations
Software Requirements Specification
For Reserve Tour Subsystem
Version 1.0
Revision History
October 2005 / 1.0 / Initial Document / CS 472
Table of Contents
1. Introduction 4
1.1 Purpose 4
1.2 Scope 4
1.3 Definitions, Acronyms and Abbreviations 4
1.4 References 4
1.5 Overview 4
2. Overall Description 4
2.1 Use-Case Model Survey 4
2.1.1 Use Cases 6
2.1.2 Actors 6
2.1.3 Use Case Scenarios 6
2.1.3.1 Reserve Tour 6
2.1.3.2 Login 6
2.2 Assumptions and Dependencies 6
Software Requirements Specification
1. Introduction
1.1 Purpose
This SRS describes the behavior of the Reserve Tour subsystem in the National Tours Online Tour Reservation System.
1.2 Scope
This SRS applies to the use cases and use case scenarios listed in section 2.1. The assumptions and dependencies in section 2.2 apply to this subsystem only.
1.3 Definitions, Acronyms and Abbreviations
None
1.4 References
None
1.5 Overview
The remainder of the SRS identifies the actors, use cases, use case scenarios, activity diagram, assumptions and dependencies needed for the analysis and design of the Reserve Tour subsystem. Diagrams conform to UML standards.
2. Overall Description
2.1 Use-Case Model Survey
Figure 1 – Online Tour Reservations for Customer
Figure 2 – Reserve Tour Activity Diagram
2.1.1 Use Cases
Reserve Tour – This use case describes the process by which tours are reserved using the online system.
Login - This use case describes the process by which users can log into the system
2.1.2 Actors
Customer - a person who uses the online tours reservations system
2.1.3 Use Case Scenarios
2.1.3.1 Reserve Tour
· Brief Description
This use case describes the process by which tours are reserved using the online system.
· Actor
Customer
· Basic Flow of Events
The use case begins when the customer selects Reserve Tour.
The system displays the Tour Information screen.
Include Login
The customer chooses a tour
The customer chooses one or more trips to take on the tour
The system provides cost information
The customer enters billing information
The customer selects Submit
The system confirms the reservation
The use case ends
2.1.3.2 Login
· Brief Description
This use case describes the process by which users can log into the system
· Actor
Customer
· Basic Flow of Events
The use case begins when the customer is presented with the login screen
The customer enters a user name and password
The system verifies the username and password
The system displays the main menu page
The use case ends
2.2 Assumptions and Dependencies
· It is assumed that the user is has created a login consisting of user name and password.
· No alternative flows have been considered at this time.
2