#1. Introduction

• this can just be a heading

1.1 Purpose

The current software is outdated and only runs on Windows 7 so new software is needed. New software must be created as our client security will be at risk if we continue using the current software. Finally, The old software contained features that were unnecessary or unused by our company, so the new one should not have these features to make the software easier to use for new hires.

1.2 Scope

Product name:

ShearImage.com

Overview:

The software will log client information, employee information, and the salon's stock of hair products. The software will also allow employees to make new appointments for clients and log hours worked.

Goals:

The main goals of the project are as follows, The software must function on Windows 10 The software must be completed by May 9th, 2024 The software must store client, employee, and product data The software must be compatible with old client and employee data The software must be able to create new appointments on a calendar

The software, ShearImage.com will work very similarly to SalonIris but will work with Windows 10 and be updated to a more modern format than SalonIris. These updates will increase client and employee information security and allow for more ease of use by removing outdated features and making the GUI less cluttered. Old data will be manually transferred to the new software as the data will be stored differently but contain the same data.

Out of Scope:

The software will not let employees edit other employee information, and the software will not order new products from outside the store only track how many are in the store.

1.3 Product overview - this can just be a heading

1.3.1 Product Perspective

Constraint 1: The project shall not have bright coloring issues

Constraint 2: The project must run on Windows 10

Constraint 3: The project will have a deadline of May 9th, 2024

Constraint 4: The project shall be coded in python

Constraint 5: The project will only use one coding language.

Constraint 6: The project's memory will be limited to the memory of the computer it is installed on

Constraint 7: The project will only run on computer systems.

Constraint 8: The project will have a plaid color scheme.

1.3.2 Product functions

• The software will connect to a client, employee, and product database and display their data.
• The software will be able to edit the databases it can access.
• The software will allow users to access the homepage but prevent them from moving any further until they log in with their credentials.
• The software will contain a calendar where the owner or employees can create a new appointment and then display them on that calendar
• The software will allow employees to log their hours worked.

1.3.3 User characteristics

The users that will be using the product will have at least a high school education and have general knowledge of hair products. They will have minimal experience with technology and software. Finally, all users of the product will work for or own the hair salon Shear Image.

1.3.4 Limitations

a) Regulatory policies;

b) Hardware limitations (e.g., signal timing requirements);

c) Interfaces with other applications;

d) Parallel operation;

e) Audit functions;

f) Control functions;

g) Higher-order language requirements;

h) Signal handshake protocols (e.g., XON-XOFF, ACK-NACK);

i) Quality requirements (e.g., reliability)

j) Criticality of the application;

k) Safety and security considerations.

l) Physical/mental considerations

M) No more than 2 years of maintenance

N) Password will be no more than 8 characters

O) Data storage is dependent on the computer the software is installed on.

1.4 Definitions

A business requirement is a high-level business objective of the producer

An external interface requirement is a description of a connection between the software and a user, or another software and of hardware

A functional requirement is a description of behavior the system will exhibit under certain conditions

A nonfunctional requirement is a description of a property or characteristic that the system must exbibit a constraint

A System requirement is a top-level requirement for a product that contains many subsystems

A User Requirement A goal or task that specific classes of users must be able to perform with a system or a desired product attribute.

A Business rule A policy, guideline, standard, or regulation that defines or constrains some aspect of the business. Not a software requirement, but the origin of several types of software requirements.

2. References

29148-2018 Sections 5, 6, 7, 8, 9, and Annex B

15288:2015 6.4.2 Stakeholder needs and requirements definition process.

Stakeholder Needs and Requirements sebokwiki

Software Requirements Engineering by Richard H. Thayer and Merlin Dorfman Details Access Chapters 1, 4 and 5

Swebok edited by Bourque Pierre and Dick E. Richard Chapter 1, 11, 13

3. Specific requirements

• content from Activity 6.3.3.3 and 6.4.3.4: your set of requirements with Key, Summary, Description, (Issue) Type, Linked Issues, Priority, and Labels, in that order, plus content from the Use Case assignment: your use cases and use case diagram.

4. Verification

The project requirements will be verified by comparing the current state of the project with the project's requirements to see if there are any features described in the requirements that are not in the software or are not planned to be in the software. If I don't find any discrepancies I would then present the project to the project's stakeholders to get their opinions of the current state of the project. And if the stakeholders had no issues then I would continue as before, but if a stakeholder brings up an issue with the project I would then interview them to see if I can find and remedy the issue. If I did find a discrepancy in the project when comparing the project's requirements to the project I would try to find where the issue lies and correct it by either updating the requirements or adding the missing feature to a future sprint.

5. Appendices - just a heading

5.1 Assumptions and Dependencies

• That the software will run on Windows 10
• That the product will be done by May 9th, 2024
• That I will gain a good understanding of GUI design by the end of summer 2023
• that the software will work similarly to their current software

5.2 Acronyms and Abbreviations

Dev stands for developer.

Business Requirements Specification (BRS)