Write "System Requirements Specification" "Functional Requirements" subsection of Requirements and Specifications

[MetzgerH]

Write section 2.2 of the Requirements and Specifications document deliverable.

Include a subsection for each main part/module of your product and list the requirements for the module in that subsection. (Please note that we are not considering any design issues yet. Each module (subsection) refers to a major part/functionality of the product, not to sub-section in the architecture. This classification of requirements is intended to improve the readability of the document.)

Generally, functional requirements are expressed in the form "system must do ”

Briefly describe each requirement and specify the client/stakeholder need(s) that requirement maps to. Each requirement should appear in ONLY ONE sub-section of the document.

Here is an example template for requirement specification:

II.2.1. [The name of the module/component/part] List your requirements for this project module here. Each listed requirement MAY INCLUDE the following items: [Enter a Concise Requirement Name]: [provide a concise description, in clear and easily understandable language to specify the requirement] Source: [specify who/what originated this requirement, specify the client/stakeholder need(s) that requirement maps to] Priority: specify the priority of this requirement, you may use the following scale to specify priority of the requirements: Priority Level 0: Essential and required functionality Priority Level 1: Desirable functionality Priority Level 2: Extra features or stretch goals

Repeat the above for each requirement.

[MetzgerH]

Re-opening because this section is missing an opening paragraph.