To demonstrate your ability to apply the knowledge gained by completing the coursework, you will complete the following project. Since this is a non-programming-based course, you will use MS Word or Visio to map out the intended software, in lieu of actually programming. The final project is broken down into the deliverables below that will cumulatively result in a Software Requirements Specification (SRS).
Below is a description of the proposed conceptual requirements for a system development project, the Salon Management System. You will, as demonstrated by the Milestones below, develop and describe the detail system requirements that address the systems: functionality; external interfaces; performance characteristics; attributes (portability, correctness, maintainability, security, etc.); and design constraints. The final deliverable will be an SRS (Milestone 6) that integrates information from all of the other milestones.
Course objectives covered in this project include CO 1, CO 5, CO 6
Project Description—Salon Management System
You are hired to design a management system for a local hair salon. These types of businesses usually provide an array of services such as hair styling/cuts, manicures, pedicures, facials, waxing, and so on. Customers who need services from the salon are required to make appointments; however, customers are also accepted as walk-ins on a space-available basis. Most salons are open for a long period of time—sometimes 12 hours a day. Beauty specialists should be assigned to shifts by the manager.
In addition to the services the salon provides, it also sells different beauty products. The salon would like to provide a catalog of the available products to their customers online.
The system should provide the following core requirements (capabilities):
● Allow customers to book appointments.
● Allow the manager to add/delete a specialist.
● Allow the manager to assign a specialist to a particular service.
● Allow the manager to assign a specialist to a time slot.
● Allow the specialist to update their own profile.
● Allow the customer to view the catalog and the offers that the salon has.
● Allow customers to view the available specialists’ profiles.
Depending on the salon that you are working for, you could also be asked to add up to four additional requirements.
Approach to Completion
Normally, you would be directed to use a specific type of software to create this project; however, in this course your project will be a descriptive outline.
Software requirements: You will use Microsoft Word with Design Features, Microsoft Visio, or any other program that will provide you with a diagram of the program you are outlining.
Your project outline should define all of the software requirements.
● A requirement may exist because of the nature of the task to be solved or because of a special characteristic of the project.
● Should not describe any design or implementation details. These should be described in the design state of the project.
You will address the following in this project.
● Functionality—What is the software supposed to do?
● External interfaces—How does the software interact with people, the system’s hardware, other hardware, and other software?
● Performance—What is the speed, availability, response time, and recovery time of various software functions?
● Attributes—What are the portability, correctness, maintainability, security, and so on?
● Design constraints imposed on the implementation—Are there any required standards in effect, implementation language, policies for database integrity, resource limits, operating environments, or any other issues?
● The Software Requirements Specification (SRS) document should be completed in MS Word format using APA style. All text, figures, and tables should each appear on only one page.
● The text of the report should be written in complete sentences.
Milestone 1: Introduction and User Characteristics
Provide an overview of the entire document and address the following:
● What the rest of the document contains.
● An explanation of how the document is organized.
● The characteristics section should describe the general characteristics of the intended users of the system including educational level, experience, and technical expertise.
● This section should also provide the reasons why certain specific requirements, based on the user characteristics, are going to be specified in Section 4 of the SRS.
Note: The User Characteristics section should NOT be used to state specific requirements, only to explain how the user characteristics will cause specific requirements to be included in the SRS, Section 4.