Your task is to develop a detailed document of the requirements of an e-commerce website. Use the project scenario (below), as well as the information below and the Requirements Document Template (attached below). You should have a minimum of 25 specific functional and non-functional requirements.

Directions

The folks at LACC helped develop high-level requirements for their web-based system, and they are eager to see that system put into action. You have been assigned the task of turning their high-level requirements into a basic prototype.

However, this is a challenge. Their high-level requirements are simply general statements about what the system should be able to do. As such, their requirements aren't detailed enough to spell out exactly how the system should look or behave. The high-level requirements will need to be broken down into more specific and detailed functional and non-functional requirements.

You will need to first expand on the high-level requirements (R1) through (R6).

Requirements Document Template: Review the Lakeshore Angels Community Connections (LACC) project scenario, along with the high-level system requirements (R1) through (R6), shown below. Break down the high-level requirements into specific and testable functional and non-functional requirements. By the time you complete documenting the requirements, it is anticipated that you will have a minimum of 25 specific functional and non-functional requirements. Specific requirements avoid ambiguity. For example, a requirement such as "The website will enable users to search the company's products in multiple ways" is not a specific requirement. Instead, rewriting it as follows would yield a specific requirement: "The website will enable users to search the company's products by text description, keywords, price range, and product type." High-level requirements for the LACC information system: (R1) Maintain volunteers and their information. (R2) Maintain stations (places) at which volunteers volunteer their time and the activities of the volunteers. (R3) Maintain information on the donors to the LACC and the donations. . (R4) Generate reports for LACC management, and donors, which may include government agencies, private foundations. (R5) Maintain and track expenses and budget. (R6) Need to convert/transform current data into the new system, once the new system is built. Functional Requirements: Example: 1. Product Catalogue (M) a. All the consumer products are categorized by departments and listed. Non-Functional Requirements: Example: 1. Operational Requirements: a. Amazon should be functioning in multiple browsers: Independent of the amount of data stored on the servers. Servers should be scalable to meet the increasing memory requirements