search

KeyserSoze01 / Team14

Intro to SE
0 stars 0 forks source link

SRS Section 1 #5

Closed truizbon closed 1 year ago

truizbon commented 1 year ago

Write up SRS Section 1

KeyserSoze01 commented 1 year ago

1.1 Purpose 

This Software Requirements Specification (SRS) document details the requirements for an online book shopping, designed to provide an easy and safe experience for customers. The site will enable users to browse a diverse selection of books, view book details such as price, description, and reviews, and manage their orders and account information. The SRS encompasses both functional and non-functional requirements and outlines any constraints and assumptions during the development process. This document is essential in ensuring that the platform meets customer needs and expectations, and is delivered with top-notch quality and on schedule.

1.2 Document Conventions

1. Font: Times New Roman should be used consistently throughout the document. Font size of 11 or 12 points

2. Headings: Headings should be clearly distinguishable from body text and should be formatted consistently throughout the document. 
       The headings in this document are as follows:
            1. Description. Each section of this SRS includes a description of said section.
            2. Stimulus. Want the customer intends for that section.
            3. Response. Software response to customer intentions
            4. Functional Requirements (FR). Minimum requirements needed for the software to perform as expected.

3. Highlighting: Highlighting will/can be used to emphasize important information, such as requirements or assumptions. This can be achieved through the use of bold, italic, or underlined text, or by using color coding.

4. Lists: Any lists will be formatted consistently and should be used to present information in a clear and organized manner. Numbered lists can be used to present sequential information, while bullet lists can be used to present unordered information.

5. Tables: Any tables used to present information will be in a structured and organized manner, and should be formatted consistently throughout the document.

6. Images and diagrams: Images and diagrams can be used to provide additional information and context, and should be formatted consistently and clearly labeled.

7. Line spacing and margins: Adequate line spacing and margins are used to ensure that the document is easy to read and navigate.

1.3 Intended Audience and Reading 

Project stakeholders. This includes the project manager, business owner, product manager, and other stakeholders who are invested in the success of the project. The development team. This includes software developers, testers, designers, and other technical staff who are responsible for building and maintaining the e-commerce site. The quality assurance team. This includes testers and quality assurance personnel who are responsible for ensuring that the e-commerce site meets the required standards and specifications. Management. This includes senior management and executive personnel who are responsible for making decisions regarding the project, including budget, timelines, and resource allocation.

1.4 Product Scope

The purpose of this online e-commerce site for books is to create an easy to use, convenient and intuitive site for customers buying books online. The system will use a database able to support high volumes of customers at once. We hope this system is a comfortable, easy system able to provide customers with the best experience possible.

1.5 References

Anything referenced will be listed here.