Security • Safety • Reliability • Availability • Maintainability • An efficient way of writing better requirements is to ensure they are clearly mapped to test cases. Making sure each requirement is clearly verifiable from the start, not only helps prepare later phases of the project, it also puts the developer in the correct state of mind. Requirements and their associated tests must also indicate what the system should not do, and what happens at the limits (degraded mode). This rule also applies for compliance requirements: indicating how they shall be tested is a good way to write better requirements. The TRD need to implement a reliable and repeatable change control process that turn this challenge into an opportunity. By providing examples and counter-examples of good requirements and documents, IEEE can enhance the quality, consistency, and completeness of the requirements. These can originally be templates, industry standards and rules inside a repository, such as the IEEE server. Requirement typical sentence construction Defects to avoid: Vagueness Weakness Over specification Subjectivity Multiplicity Unclear meaning Implicit meaning Some words to be used with caution: practice”, “adequate”, “applicable”, “appropriate”, “approximate”, “bad”, “best “between”, to”, “clearly”, “compatible”, “completely”, “consider”, “down “easy/easily”, “effective”, “efficient”, “equivalent”, “excellent”, “good”, “his/her”, “however”, “ideal”, order to”, but shall not be limited to”, “etc”, “in “include “least”, “like”, “low”, “maximise”, “may”, “most”, “minimum/mal”, “must”, “nearly”, “necessary”, “needed”, “normal”, “or”, “possible/bly“, “practicable”, “provide”, “quality”, “readily”, “relevant”, “safe/ly“, “same”, as”, to”, “should”, “significant”, “similar”, “so “subject “substantial”, “sufficient”, “suitable”, to”, friendly”, “support”, “target”, “typical”, “up “user “whether”, “will”, “with”, “worse”.
• Security • Safety • Reliability • Availability • Maintainability An efficient way of writing better requirements is to ensure they are clearly mapped to test cases. Making sure each requirement is clearly verifiable from the start, not only helps prepare later phases of the project, it also puts the developer in the correct state of mind. Requirements and their associated tests must also indicate what the system should not do, and what happens at the limits (degraded mode). This rule also applies for compliance requirements: indicating how they shall be tested is a good way to write better requirements. The TRD need to implement a reliable and repeatable change control process that turn this challenge into an opportunity. By providing examples and counter-examples of good requirements and documents, IEEE can enhance the quality, consistency, and completeness of the requirements. These can originally be templates, industry standards and rules inside a repository, such as the IEEE server. Requirement typical sentence construction Defects to avoid: Vagueness Weakness Over specification Subjectivity Multiplicity Unclear meaning Implicit meaning Some words to be used with caution: “adequate”, “applicable”, “appropriate”, “approximate”, “bad”, “best practice”, “between”, “clearly”, “compatible”, “completely”, “consider”, “down to”, “easy/easily”, “effective”, “efficient”, “equivalent”, “excellent”, “good”, “his/her”, “however”, “ideal”, “etc”, “in order to”, “include but shall not be limited to”, “least”, “like”, “low”, “maximise”, “may”, “most”, “minimum/mal”, “must”, “nearly”, “necessary”, “needed”, “normal”, “or”, “possible/bly“, “practicable”, “provide”, “quality”, “readily”, “relevant”, “safe/ly“, “same”, “should”, “significant”, “similar”, “so as”, “subject to”, “substantial”, “sufficient”, “suitable”, “support”, “target”, “typical”, “up to”, “user friendly”, “whether”, “will”, “with”, “worse”.
15-14-0309-06-003d-technical-requirements-document.docx