Thursday, November 29, 2018

You Can Reuse Without A Big Investment

›
When salvaging you got to be the tug that pulls what you need to the surface. The most effective way to reuse software components is fr...
Wednesday, November 28, 2018

Know Your Application

›
No matter how well the requirements have been written, the selection of optimal architectures and algorithms is very much a function of k...
Tuesday, November 27, 2018

Store Requirements in a Database

›
Keep in mind that the follow quote is from 1995. It is still completely relevant. Requirements are complex and highly volatile. For the...
Monday, November 26, 2018

Self-Destruct TBDs

›
A software requirements specification (SRS) with a TODO or TBD (To Be Determined) note is obviously not complete. There may be good reaso...
Saturday, November 24, 2018

Specify When Environment Violates "Acceptable" Behavior

›
Requirements specifications often define characteristics of the system's environment. This information is used in making intelligent ...
Friday, November 23, 2018

Specify Reliability Specifically

›
Software reliability is difficult to specify. Don't make the problem even more difficult by being vague. For example, "The syste...
Thursday, November 22, 2018

Write Natural Language Before a More Formal Model

›
Augment, Never Replace, Natural Language  says to create requirements specifications that contain both natural language and formal models...
Wednesday, November 21, 2018

Augment, Never Replace, Natural Language

›
"In an effort to reduce ambiguity in requirements, software developers often decide to use a notation that is more precise than natu...
Tuesday, November 20, 2018

Reduce Ambiguity in Requirements

›
Software requirements specifications are often written in a natural language. To reduce the ambiguity of natural language apply the follo...

Separately Number Every Requirement

›
"It is essential that every requirement in the requirements specification be easily referenceable. This is necessary to enable later...