Software Requirements
Specification for
SmartShoppers System Version 1.0
Copyright By PowCoder代写 加微信 powcoder
Table of Contents
1. Introduction 4 1.1 Purpose 4 1.2 Document Conventions 4 1.3 Intended Audience and Reading Suggestions 4 1.4 Product Scope 5 1.5 References 5
2. Overall Description 6 2.1 Product Perspective 6 2.2 Product Functions 6 2.3 User Classes and Characteristics 7 2.4 Operating Environment 7 2.5 Design and Implementation Constraints 8
2.6 User Documentation
2.7 Assumptions and Dependencies
3. External Interface Requirements
3.1 User Interfaces
3.2 Hardware Interfaces
3.3 Software Interfaces
3.4 Communications Interfaces
4. System Features
4.1 User Authentication 4.2 User Profile
4.3 Resource Management
4.3.1 Item Management 4.3.2 Store Management 4.3.3 Human Resources
4.4 Online Service
4.4.1 Store Look-up & Preferences 4.4.2 Item Search & View
4.4.3 Shopping List
4.4.4 Order
4.5 Recommendation
5. Other Nonfunctional Requirements
5.1 Performance Requirements 5.2 Safety Requirements
5.3 Security Requirements
19 19 19 19
5.4 Software Quality Attributes 5.5 Business Rules
6. Other Requirements
6.1 Database Requirements 6.2 Legal Requirements
6.3 Compatibility Requirements 6.4 Accessibility Requirements 6.5 Compliance Requirements
A. Definitions and Abbreviations
A.1 Definitions A.2 Acronyms
2022/02/26
Reason For Changes
Initial Draft
1. Introduction 1.1 Purpose
The primary goal for this SRS is to document a complete and accurate list of requirements for the SmartShoppers online system. These are the software requirements for version 1.0. The SmartShoppers online system is required by a leading retail chain in Canada called ShoppersLand Inc. This document will provide the development team with specifications of the SmartShoppers online system. The development team will understand the needs of the stakeholders, the details of the product, and the requirements of the product through this SRS document. In this document, the whole software system will be covered which will comprise of components and subsystems.
1.2 Document Conventions
Higher priority requirements are ordered from top to bottom where the first requirement documented it has the highest priority in that section. The priority levels of requirements in this document are scaled by the following scale.
High = essential Medium = important Low = desirable
High priority requirements must be designed and built in the software as they are critical to the functionality of the software system. Medium priority requirements are important for the quality of the system but are not essential for the system to operate. The low priority & some of the medium priority requirements should be decided upon through various requirements prioritization techniques. These techniques would include quantitative and qualitative prioritization techniques. Priorities for higher-level requirements are assumed to be inherited by detailed requirements unless there is priority accompanying the requirement statement.
1.3 Intended Audience and Reading Suggestions
This document is intended for the development team of the SmartShoppers online system, as well as the stakeholders. The rest of the SRS gets more descriptive about the software system. Sections 3 to 6 detail the requirements of the system and covers the core of this document. These sections contain both the functional requirements which explain the function that the software system must perform, and non-functional requirements which describe the system¡¯s attributes. A developer is recommended to read section 2 to get a description of the software system to build,
and Sections 3-5 to understand the requirements of the SmartShoppers online system. Section 2 is a recommended read for the end users.
1.4 Product Scope
The SmartShoppers system is an online system that allows customers to find products in the physical retail stores with a greater precision. The main goal of the software system is to provide the customers with a faster and smooth shopping experience in store. SmartShoppers would allow customers to find the products that are available in a specific store and its location in the store. This product will have many benefits to the customer and the ShoppersLand Inc. The customer will have financial benefits as they are able to save money by being provided all the on- sale items. The customer also is able to find recommended products which they might not have had a chance to find in store. The customer saves time shopping because they know the exact locations of the products which they would like to purchase. ShoppersLand Inc. would benefit financially as they will sell more products because of the SmartShoppers online system. ShoppersLand¡¯s employees would also be able to work efficiently as they will be asked fewer questions by the customers regarding the products.
1.5 References
WCAG – Web Content Accessibility Guidelines https://www.w3.org/WAI/standards-
guidelines/wcag/
Educaloi – Law regarding language requirements in Quebec https://educaloi.qc.ca/en/capsules/language-laws-and-doing-business-in-quebec
2. Overall Description 2.1 Product Perspective
ShoppersLand Inc is a retail chain in Canada looking to allow customers to virtually browse their in-store products as a way to improve customers’ shopping experience.
This means that customers can search for a store or find the nearest store (to a specified location or theirs) and see the availability of items at that store. They can create shopping lists and add available items to their shopping list. The shopping list will auto-sort by aisle to optimize customers’ shopping time.
This system uses a database containing information regarding stores, each store has managers who can track and update their stores inventory. The entire system is overseen by administrators who have the same privileges as managers in addition to the ability to add and remove managers.
Customers select the store nearest a location of their choice and can browse the items available at that store, search for specific items or view items that are on sale and add them to their shopping list.
2.2 Product Functions
The following is a list of functions that the system will provide:
Customers:
¡ñ The ability to sign up.
¡ñ The ability to log in.
¡ñ The ability to log out.
¡ñ The ability to find nearest stores based on current location.
¡ñ The ability to find stores based on inputted location (max 50km).
¡ñ The ability to save locations.
¡ñ The ability to search for items by name.
¡ñ The ability to view item information.
¡ñ The ability to search by category.
¡ñ The ability to shop by category.
¡ñ Sale items are in a Sale category and in their usual category.
¡ñ The ability to add items to the shopping list (quantity > 1).
¡ñ The ability to remove items from the shopping list.
¡ñ The ability to view shopping lists (sorted).
¡ñ The ability to view recommended items list (based on their current shopping list)
¡ñ The ability to add Items
¡ñ The ability to remove items
¡ñ The ability to modify items
¡ñ The ability to modify sale item list
Administrators:
¡ñ The ability to add Items
¡ñ The ability to remove items
¡ñ The ability to modify items
¡ñ The ability to modify sale item list
¡ñ The ability to add/remove Managers
2.3 User Classes and Characteristics Customer
Customers are individuals part of the general public. They require the ability to view the website, login/logout, select a store, browse store inventory, interact with shopping lists, add/remove items to/from their shopping list and to view their shopping list.
Manager¡¯s have the ability to update item information in inventory as well as update items¡¯ stock count for the stores they manage. They also require the ability to put items on sale for a chosen amount of time.
Administrator
The administrators role is to manage the overall system including managing the managers, stores and items in stores. This means they need the ability to add/remove and edit the aforementioned groups.
2.4 Operating Environment
Since the primary users of the system are customers of a grocery store, a general audience, a wide range of popular web browsers should be compatible with the system. Moreover, the website should be operating system agnostic and function with any modern operating system for both desktops and mobile devices. At a minimum, the system should run on Linux, Windows, Android, iOS and Mac operating systems provided they are up to date and are not legacy operating system versions. Provided is a detailed description of the operating systems that should be able to run detail descriptions about the operating systems that the system can operate functionally:
¡ñ Macintosh (Mac OS X or greater).
¡ñ iOS (10+)
¡ñ Android (10+)
¡ñ Microsoft Windows (7+)
¡ñ Linux (Ubuntu, CentOS etc.)
Web browsers that the system should be compatible with:
¡ñ Mozilla Firefox
¡ñ Google Chrome
¡ñ Microsoft Edge
¡ñ Samsung Internet
2.5 Design and Implementation Constraints
If this product must be available in Quebec at the time of launch it must have a French translated version of the website in accordance with the Charter of the French Language (educaloi).
There are no limits to the technologies used as long as they meet security standards and are capable of performing the required tasks. The manager may use a different application to access and update store database information.
There are only two pieces of information being communicated that require security considerations. One, the login information. Which should be implemented according to industry standard or using verified, secure 3rd party systems e.g. oauth. The second is the browsing information, customers browsing trends, which when collected should not include identifiable customer information (anonymize data).
2.6 User Documentation
Navigation and use of the system should be straightforward. However, a help section with a Frequently Asked Questions section and a way to report an issue such as an email address or a form should be present.
2.7 Assumptions and Dependencies
We assume that managers, customers and administrators are using the same website. There is no assumption of third-party or commercial components being used at present, the document will be modified if this changes.
3. External Interface Requirements 3.1 User Interfaces
The SmartShoppers GUI requires the use of a web browser for any user or device. The GUI will be automatically scaled to the size of the users¡¯ screen for mobile devices, or resized to the window for PC users, should the user change window size the GUI will automatically rescale. The web-based interface will provide forms of accommodation for users with disabilities, including but not limited to: screen-reader functionality, user colour customization, on-screen keyboards.
Every screen will have a link for customers to view their shopping list. The shopping list link will be in the form of a button, when the button is clicked the shopping list will take up the entire screen of the device.
3.2 Hardware Interfaces
The SmartShoppers System will be a web-based service. Supported operating environments are listed in Section 2.4. Normal users will not be able to change the system¡¯s databases, rather they will only be able to access information through the interface by providing inputs (items, locations, log-ins).
3.3 Software Interfaces
The SmartShoppers System will save users¡¯ shopping lists as items are added, this is for user convenience and accommodates for the event that users may leave part way while creating their lists (internet disconnections, intentionally closing the page and coming back to it later, etc.). Inputs from the users will mainly come in the form of searching items, the output of the system will be information pertaining to the item, or an error message if the item does not exist, or is out of stock.
3.4 Communications Interfaces
The system must be accessed by using one of the supported browsers (see Section 2.4 for details). Users will be prompted for a log-in to access their accounts, first time users will be provided with an electronic form to fill out. This information will be stored in the database. Sensitive information including but not limited to: passwords, e-mail addresses must be encrypted to
prevent security breaches and hacking. The database must have an up-time of 98% of the year, with downtime being allotted for scheduled maintenance. The database must update in real-time when new items get added or existing items get changed/deleted.
4. System Features
This section will discuss in more detail about the main requirements of the SmartShoppers Online System for all defined users in section 2.1.
4.1 User Authentication
4.1.1 Description and Priority
Before accessing the system and utilizing any functionality and service that the system provides, users must initiate a registered identity in the system and access the system through authentication measures. Any failure should direct the users to the accordingly section for further registration or logging. This feature is considered High Priority.
4.1.2 Stimulus/Response Sequences
When users come to the online system and want to save a specific store in the system, the login section of the system should appear and ask users to enter an identifier and a password. If it is a new user, the user can access the registration form with an action and create the account. After that, the system would presume the current activity of the user.
Functional Requirements
4.1 – Req 1: Each user must identify self.
Priority: High
4.1 – Req 2: New users must create an account in the system for the system to provide its service, mainly to save the stores¡¯ location.
Priority: High
4.1 – Req 3: The system must display proper warnings when an user fails to access the system.
Priority: High
User Profile
4.2.1 Description and Priority
Users with different authority must have the ability to customize their profile/account within the system. In detail, users can access and modify personal information, store preferences and security in the profile. This feature is considered High Priority.
4.2.2 Stimulus/Response Sequences
Each user would be able to identify the profile in the online system. In the profile, the system would present the fundamental features such as security and personal information modification as well as supported features like store¡¯s location for preferences. The system would ask for confirmation and update the user¡¯s profile based on the actions the user takes in the profile.
Functional Requirements
4.2 – Req 1: Each user must have the ability to change the account identifier and password.
Priority: High
4.2 – Req 2: Each user must be able to establish security methods for further use of the system.
Priority: High
4.2 – Req 3: Each user must be able to view and modify the preferences of store location.
Priority: High
4.2 – Req 4: Each user can request for personal information and account deletion from the system.
Priority: High
Resource Management
Item Management
Description and Priority
Users with the appropriate privilege (managers and administrators) can manage the items that are presented in the online system. In detail, they will have the authority to add and remove items
from the system; modify, update items¡¯ availability and the number of items in inventory; arrange categories and update lists of sale items. This feature is considered High Priority
4.3.1.2 Stimulus/Response Sequences
When the user performs any action from adding, removing and updating items, the system would ask the user for confirmation, connect to the external databases from the main system and proceed the instructions. After executing the instructions, the system would then present the user with the current state of the item management after the changes.
Functional Requirements
4.3.1 – Req 1: All managers must have the authority to add, remove and update the items from the system to the store they are assigned.
Priority: High
4.3.1 – Req 2: All managers must have the ability to update the items¡¯ availability in the store they are assigned.
Priority: High
4.3.1 – Req 3: All managers must have access to the lists of sale items in the system and have the authority to modify the items in the lists from the system to apply on the store they are assigned.
Priority: High
4.3.1 – Req 4: All administrators can interact with the items in every store any operations that the managers can perform.
Priority: High
Store Management
Description and Priority
information about the stores of which SmartShoppers Inc. is in charge. Moreover, they can update the fundamental information of the store, for instance, opening and closing hours, the store¡¯s map with each item categorical section. For administrators, they can modify the list of stores within the system, including their locations. This feature is considered High Priority.
4.3.2.2 Stimulus/Response Sequences
with appropriate privilege (managers and administrators) can update the relevant
Accessing a specific shop would display all relevant information of the store. If the user chooses the option for modification, the system would change the read-only mode into editable-mode and the user can change the information within that particular store. After the user confirms the changes, the system would then save the change and direct the user back to the store¡¯s view.
Functional Requirements
4.3.2 – Req 1: All administrators must have the ability to add and remove a specific store within the system.
Priority: High
4.3.2 – Req 2: All administrators must have the ability to update the stores¡¯ availability, opening and closing hours within the system.
Priority: High
4.3.2 – Req 3: All administrators must have the ability to update the store¡¯s map along with the categorical sections inside the stores within the system.
Priority: High
4.3.2 – Req 4: All managers must have the ability to update the availability, opening and closing hours of the specific store they are in charge of.
Priority: High
4.3.2 – Req 5: All managers must have the ability to update the map of the store of which they are assigned along with the categorical section inside the store.
Priority: Medium
Human Resources
Description and Priority
The system along with users with the highest privilege (administrators) can add and remove managers within the system. Furthemore, the system can grant privileges to managers to access and update other resources within the system as long as they have granted permission.This feature is considered High Priority.
4.3.3.2 Stimulus/Response Sequences
If administrators add a manager into the system, the system would create an account, grant that account with the access privilege for item and store management. Then the system would display the identifier and temporary password to the administrators.
If administrators remove a manager from the system, the system can either revoke the privilege from the manager¡¯s account or delete the manager¡¯s account from the system.
Functional Requirements
4.3.3 – Req 1: The system as well as the administrators must be able to add, remove and update managers for a specific store.
Priority: High
4.3.3 – Req 2: The managers who are removed by the administrator must have no access to the system management for items and stores.
Priority: High
4.3.3 – Req 3: The managers whose store is modified by the administrator must only have the access to all functionalities of the latest store and have no access to the functionalities of the previous stores.
Priority: High
Online Service
Store Look-up & Preferences
Description and Priority
Customers can interact with the system on finding and saving Smart
程序代写 CS代考 加微信: powcoder QQ: 1823890830 Email: powcoder@163.com