TABLE OF CONTENTS Requirements analysis and requirements writing are necessary but difficult, sometimes tedious, tasks. In this chapter we will explore four strategies one or more of which, hopefully, will reduce the requirements analysis difficulty by providing mechanisms for gaining insight into the attributes that should be controlled by written requirements statements. The fact is that it is not hard to write requirements. It is hard to know what to write them about and to determine appropriate numerical values to include within them.
In this chapter we will develop a progressive scenario that will be useful in writing simple requirements statements regardless which requirements analysis strategy you choose. Given an organized method for identifying the requirements to write and a simple, progressive method to write them, the task remains to assign appropriate values to our requirements and we close out this chapter with that subject.
So, first we need to understand the very essence of a requirement statement. If we strip away all of the style and format common to a paragraph in a specification, we are left with a residue that we will call a primitive requirements statement. This primitive statement is very easy to phrase. Any engineer without special requirements analysis training can do it. Any engineer who hates English grammar can do it. You can combine several of these primitive statements to form a...
