Computer Science

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.
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?

MILESTONE 1
Introduction
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.

User Characteristics
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.

MILESTONE 2
Requirements Determination [Week 5]
Describe the different methods that the analysts have used in determining the requirements, and include the following, as appropriate:

A literature review
Search at least five applications or websites, assessing and comparing the features of similar existing systems.
An APA formatted References page of the applications or websites used should be included in the References section.
Stakeholder(s) Interview(s)
Provide the interview transcript that you have used to collect the interview details and a summary of the interview.
Questionnaire
A sample of the analysts’ questionnaire
Questionnaire results analysis table
A summary of the outcomes

MILESTONE 3
The specific requirements section is divided into three subsections: User Requirements; Systems Requirements; and Nonfunctional Requirements.

User Requirements
Identify the user requirements and the software services required by the customer in a high-level natural language.

System Requirements
For each user requirement, system requirements should define the fundamental actions that must take place in the software in accepting and processing the inputs and in processing and generating the outputs. These are generally listed as “shall” statements starting with “The system shall.” The systems requirements should include, but not be limited to, the following:

Validity checks on the inputs
Exact sequence of operations
Responses to abnormal situations, including
Overflow
Communication facilities
Error handling and recovery
Relationship of outputs to inputs, including
Input/output sequences
Formulas for input to output conversion

It might be appropriate to partition the functional requirements into sub-functions or sub-processes, for example, as indicated below.

Specific requirements format:
User requirement
System requirement 1
System requirement 2
System requirement 3, and so on

Nonfunctional Requirements
This section should answer all the special constraints and considerations in the project, including those below.

What are the factors required to establish the required reliability of the software system at time of delivery?
What are the factors required to guarantee a defined availability level for the entire system such as checkpoint, recovery, and restart?
What are the factors required to protect the software from accidental or malicious access, use, modification, destruction, or disclosure?
What are the different attributes of software that relate to the ease of maintenance of the software?
What is the speed, availability, response time, recovery time of various software functions?

MILESTONE 4
his section should illustrate the system models that reflect the overall system processes from different perspectives according to the software type. Model the system using one of the below processes:

A Behavioral Model: Typically modeled using data flow diagram and an entity relation diagram.

OR

An Object Model: Typically modeled using case, sequential, or conceptual diagrams.

Note: All diagrams, for both Milestones 4 and 5 can be done in MS Word or MS Visio.

MILESTONE 5
Submit the last two sections of the Systems Models section of the project, including a Conceptual Diagram and the Class Diagram.

This section is a continuation of Milestone 4 to include the actual diagram of the software mode (SUBMIT MODEL)

MILESTONE 6
Complete the Software Requirements Specification (SRS) template that integrates the submissions from Milestones 1 through 4, including mentor feedback on those submissions.

Note: Be sure to complete all sections of the template, including References and Appendices.