Requirements Notes - Requriments-on-engr-analysis-project/future-sponsor-project GitHub Wiki

General Requirement Statement Notes

 Requirement statements are statements that depict what a product may act or look like. They can come as functional and nonfunctional requirements 
 statements. They can either be simple statements about the product or stories of users using the theoretical product.

Product and Process Requirements

 A product requirement refers so a requirement the product itself needs to adhere to and a process requirement refers to a requirement the method 
 of creating the desired product needs to adhere to.

Functional and Nonfunctional Requirements

 Functional requirements are behaviors the product should show or support. Nonfunctional requirements are requirements that aren't something that 
 the product does but something it should be able to do like have few errors or be easy to use. 

Requirements Construct

 A requirement is a statement that translates a need and any constraints or conditions for that need. 
 The requirements should express a subject, condition, and constraint for its need.
 29148-2018 5.2.4

Characteristics of individual requirements

  While requirements can be worded differently they should be Necessary for the product, appropriate for the product, unambiguous, singular, 
  feasible, verifiable, correct, and conform to a standard template.
  29148-2018 5.2.5

Requirements language criteria

  Requirements should detail what the system needs but not how to do it, while also avoiding any vague or undetailed statements.
  29148-2018 5.2.7

Requirements attributes

Requirements should include attributes that assist in identifying the requirements and help people analyze the requirements.
29148-2018 5.2.8

Sample Requirement Statement

 The product shall limit bright flashing lights to support people with light-sensitive conditions.

Characteristics of this individual requirement

The characteristics of individual requirements are that they must be Necessary for the product, appropriate for the product, unambiguous, singular, 
feasible, verifiable, correct, and conform to a standard template.
The requirement uses the formatting shown in 29148-2018 5.2.4 Figure 1 and uses the languages demonstrated in 29148-2018 5.2.4 page 10.

Requirements language criteria

The requirement meets the criteria from 5.2.7 by avoiding vague wording such as all or most.

Requirements attributes

Identification: Flashing lights limitation. Stakeholder Priority: Medium Type: The requirement is a nonfunctional product requirement as the requirement refers to a nontangible requirement that the product must attain.