PAPER. Abstract:
I believe that most requirements specifications in practice are very poor in clarity, and in
content. I believe that in addition to tackling the clarity problem by a variety of rich
specification devices, we need to make a requirement specification ‘work harder’ to
satisfy a large number of needs by adding ‘background’ to the requirement. The needs I
am referring to include: prioritization, risk management, change management,
presentation, justification, testability, integration, quality control, and other purposes. To
do this I have, over the years developed a requirement specification language, as a subset
of my Planning Language (Planguage). This is has been developed by practical need in
international industry over decades, and supplemented with some recent ideas. The more
detailed version of the Requirements Language is documented in my book Competitive
Engineering, which is a handbook defining concepts rigorously. This paper will give an
overview of the conceptual basis and some detail as a sample. By ‘rich’ I mean
substantially more detail for each requirement than is usual. By ‘background’ I mean
information related to the requirement that is not the requirement itself.
Created / Uploaded:
Last modified:
Hits:
12171