-- TimMiner - 04 May 2002

Here is a "structure" thing: There is really no such thing as an optional requirement. If you think about it, putting an option into a design after it has reached the market involves a redesign and is usually called a product improvement. If it is writen into the spec as an option or optional item, any contractor in the world will completely ignore it in an effort to complete the contract on schedule. TM18 and TM39 in MinimumSystem are examples of requirements that create what the world calls options or optional items in the products they buy. (moved from MinimumSystem -- TimMiner - 04 May 2002

We also need to not use the words "may" or "will" or "should" or "could" when we are writing a requirement for related semantic reasons. Basically, they WILL give someone too much "weasle room". -- TimMiner - 04 May 2002

Please avoid run-on or run-away requirements where they encompass too much territory. This can happen easily when we are composing the thinking. So, if the word "and" appears in the statement of a requirement, beware. If there is more than one sentence in the requirement, beware. It is recommended (that in these documents) you start with high level concepts, define them and then work your way down in detail, but do it one requirement at a time.-- TimMiner - 04 May 2002