Business Requirements Specification (BRS) - Requriments-on-engr-analysis-project/future-sponsor-project GitHub Wiki

Business Requirements Specification Document for Shear Image.com Software

Caleb Blackburn 4 March 2023 Version 7

Contents Introduction 3 Business management requirements 4 Business operational requirements 5 Preliminary operational concepts of proposed system 6 5.1 Preliminary operational concept 6 5.2 Preliminary operational scenarios 6 Other preliminary life-cycle concepts 8 Appendix 9 References 9

Introduction This document is a Business Requirements Specification (BRS) document for users of the project. This document will detail the project’s business requirements, potential stakeholders, and the process for creating the project. An overview of what the project may look like once complete will also be provided. Any constraints the project must obey will be listed to ensure the project meets the salon’s standards of quality.

While the old system, SalonIris (SI), functions well It only runs on Windows 7. With Microsoft no longer supporting Windows 7 our systems and client data are now vulnerable to attack if we do not update to a new version of Windows. So, a new system needs to be designed for Windows 10 to secure our systems and provide better service for our clients. The salon itself focuses on providing quality hair cutting services to all clients using organic products. The scope of this project will include the salon’s ordering system, its client/employee data storage systems, and a calendar to track client appointments. The major stakeholders of the project are the employees, owners, and developers or devs of the project. Employees are users of the software, and their reviews of the product will be used to improve the project later. The owner of the project will specify the project requirements and ensure the software meets the standards of their salon. The dev is in charge of creating and maintaining the project and communicating with the owner on the project’s requirements. Business management requirements The project needs to account for the constantly changing business environment and allow for changes to be made to the project by the dev as requested by the owner. This section will explain what factors the business must comply with. The project must account for changes in the salon’s internal environment such as the changing of employees or the owner. The environmental factors the project needs to account for are changes in hairstyle trends and potentially, changes in regulations regarding client data and ordered products. As new products are made almost daily and old ones become outdated or potentially hazardous the owner must be able to modify this data to account for these changes. The project must function similarly to the salon's original software SalonIris but must be useable on Windows 10 to provide increased security for our client's data and the salon’s data. As well as provide a more navigable environment for users to use the project. As the salon falls under the service industry, the project must also fall under that industry and comply with its regulations. So, the business model for the project will follow the service industry’s guidelines. Since the salon deals with clients’ personal information, the project must have a secure storage system for accessing and viewing client information. To help secure the client’s data an authentication system should be implemented. Potentially using a password or calling the user on their cellular device.

Business operational requirements As the project must work with the salon to provide quality service to clients this section will detail how the salon operates and what rules or constraints the salon follows. As well as provide a general structure of the salon’s daily operations to aid in the creation of the project. The general process of the salon’s business is as follows; the client walks into the store. If an appointment is scheduled the salon employee will cut their hair and if not, then the client can schedule an appointment and return later or wait in the store for an opening to get their hair cut. Afterward, any excess hair is thrown away to prevent an outbreak of lice in the salon. When cutting hair, only organic products are used as per the owner’s policy. However, if the client comes in and has lice or other potentially contagious hair problems then the employee refuses business with the potential client until their hair problem is resolved, to prevent an outbreak of that problem within the salon. As the salon requires direct access to the client the salon is only operated in person within the storefront. So, the project will only log appointments on the calendar and not perform any direct service to clients. After the client’s appointment, the quality of service is measured by how much the customer tips the employee and if they schedule another appointment afterward. Both events indicate the quality of service the salon provided to that client. As the salon is small it has a simple structure of owner and employee. Where the owner owns the storefront and provides general maintenance to the building. The employee performs the salon’s services to the client, accepting their payment and finally creating another appointment for the client if they wish for one.

Preliminary operational concepts of the proposed system 5.1 Preliminary operational concept This section will describe some of the policies/constraints the project must follow and some of the required features of the project. The project must follow these policies/constraints: The project shall save data without internet access, the project shall accept user input for its data, and the project shall require a log-in to access and modify data. The project must allow for the storage of client and salon data. While also keeping track of customer preferences and salon orders. The project should also have a built-in Calendar to allow the owner and employees to see upcoming appointments and dates. Employees should also be able to complete client appointments and keep track of how many hours they worked. There will be three user classes: owner, employee, and developer. Finally, the project shall run on Windows 10 laptops and desktops. While being supported with periodic updates and maintenance for 2 or more years after the project’s completion. 5.2 Preliminary operational scenarios This section will detail 3 scenarios of how users will use the product once completed. Scenario 1: The user logs into the system and signs in with their username and password. The user is identified as an employee and opens the home page. From the homepage, the employee can edit their client's information and add new appointments for those clients but is unable to edit other employees' client information. The employee should be able to view the calendar to see upcoming dates and appointments for their and other employees' clients. Finally, the employee should be able to complete client appointments and submit how many hours they worked for a given day.

Scenario 2: The user logs into the system and signs in with their username and password. The user is identified as the owner and opens the home page. From the home page, the owner can use all the same features as an employee but is also able to edit all employee appointments and client information and place/view orders for products the salon needs. The owner shall also be able to create new clients and access employee information. The owner should be able to view the calendar and edit/create appointment information on the calendar. Finally, the owner can access employee payment information and see how long they have worked.

Scenario 3: The user logs into the system and signs in with their username and password. The user is identified as the software developer and opens the home page. The dev shall be able to access the main code and update it with new features or bug fixes. The developer should not have access to employee or client information but instead, have access to a mock version to allow for the testing of new features.

Other preliminary life-cycle concepts This section will detail the project’s lifecycle from implementation to retirement and show how the project will be maintained during its lifecycle. The system solution will be acquired from consistent meetings with the client where the dev and client shall go over and create requirements based on the client's needs and what is possible for the dev. Production will start in the fall as defining the requirements has only just begun. Some requirements will be created based on the salon's previous software SalonIris. Once complete the software shall be delivered initially via download and after a trial period of one month, officially adopted by the salon. After, delivery the software will be supported for two or more years after the salon adopts the software. Updates will be downloaded online with the owner's approval and the owner can email or call the dev if any issues arise with the software in-between updates. When the owner wishes to replace the project the project will be retired by the deletion of all user accounts and client information. Then the project will be uninstalled from the salon's main computer. Finally, its replacement will be installed and launched after the old software is completely removed. As the project will not be started until the fall of next year due to the main dev being busy with internships and other schoolwork, the coding of the project will have a time limit of only one year.

Appendix 8.1 Acronyms and abbreviations Dev stands for developer. Business Requirements Specification (BRS)

References
• 29148-2018 Sections 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 Chapter 1 sections III and IV pages 12-19 (PDF pages 9-18)