Introduction

The module is part 1 of a trilogy called "Shoulda Woulda Coulda". In this module, the importance of using the active voice in requirements is introduced.

Active Voice in Requirements

• Using active voice helps to be clear and direct in capturing functional requirements.

• Benjamin Franklin's quote "Tell me and I forget, teach me and I remember, involve me and I learn" emphasizes the importance of being an active learner.

Valid Requirement Statements

This section discusses how consistency with terms and language used in requirements is important. The imperative verb that denotes the presence of a requirement is crucial.

Importance of Imperative Verb

• Consistency with terms and language used in requirements is important.

• The imperative verb denotes the presence of a requirement.

Shall vs Must

• The word "shall" should be used instead of "must" according to style rules for projects.

• Contractors and suppliers are looking for "shall" statements when scanning documents to extract requirements.

Use of Will

• "Will" statements are not requirements but rather statements of fact about future purpose.

Hidden Requirements

This section discusses how some statements intended to be requirements use verbs like will instead of shall which can lead to hidden requirements.

Identifying Hidden Requirements

• Some statements intended to be requirements use verbs like will instead of shall which can lead to hidden requirements.

• It's best practice to make keywords stand out by using bold fonts on the word shall so that readers can easily identify them as requirements.

Conclusion

This section provides a quick recap of the importance of using the imperative verb "shall" to denote requirements and avoiding confusion with "will" and "must". It also emphasizes the use of bold fonts to make requirements stand out.

Recap

• The verb "shall" denotes a requirement, avoid confusing it with "wills" and "musts".

• Bold fonts can be used to make requirements stand out and reduce cognitive burden on readers.