1. System Overview

This is a reservation system for a network of exercise studios located in BarbaraTown, USA. The program will allow users to create a reservation at one of the exercise company's many locations. Users will specify a time and date for their arrival, as well as an instructor or class if applicable. After a reservation is made and confirmed the program will allow the User to view their reservations and make amendments if needed.

  1. Technical Requirements
  2. Functional Requirements
  3. Accepts email as a User login
  4. Accepts an exercise location and time slot, as well as class/trainer slot if applicable
  5. Emails the User their confirmation number or informs them the class is full
  6. Allows the User to view their classes and time slots
  7. Allows system administrators to view a class roster and class schedule for different locations
  8. Allows system administrators to add available classes and time slots, as well as updated availabilities.
  9. Non-functional Requirements
  10. Cannot allow more then the person limit into a given time slot
  11. Gives options if the given time slot is unavailable
  12. User Interface Specification
  13. Web based application
  14. Simple design, easy to read and navigate
  15. Gives a list of all available time slots and classes and their dates/times up on the front page
  16. Database will need to be encrypted as to keep peoples private information secure
  17. User Task Flow

  1. Input/Output and other Data Specifications
  2. Email: Input
  3. Schedule: Ouput
  4. Interface specifications to other systems
  5. Web app to Database Interface
  1. Acceptance Criteria/Interaction Scenarios
  2. How-to:
  3. How will the web application interface with the database
  4. How will the application specify separate locations
  5. How will the system administrators upload available classes and time slots
  6. Who:
  7. Who will maintain the database
  8. Who will update website information
  9. What-kind-of:
  10. What kind of Database Management System will be used
  11. What kind of images will be used to guide the users with ease
  12. When:
  13. When will website maintenance be done
  14. When will class availabilities and schedules be updated
  15. Relationship:
  16. Relation between user location and Exercise facility location
  17. What-if-questions:
  18. How will the system deal with canceled classes.
  19. How will the system deal with facility shutdowns (For example: due to inclement weather)
  1. Verification/Validation

The system will be verified with the client in early stage planning and then again at the end of Design phase. During implementation there will be verification testing with focus groups to get an idea of how user friendliness can be improved. Validation testing will be done at the end of implementation.

  1. Requirements considerations

This section should contain the following:

  1. Assumptions
  2. Client has their own web domain and server to maintain their own data
  3. End Users
  4. A large range of young to old, with varying adeptness with technology
  5. Existing systems
  6. N/A
  7. Environment
  8. Continual web based application