Premium
8.1.1 The Use of Planguage to Improve Requirement Specifications
Author(s) -
Gilb Tom
Publication year - 2004
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2004.tb00598.x
Subject(s) - computer science , specification language , requirements analysis , requirements management , testability , clarity , risk analysis (engineering) , system requirements specification , software requirements specification , quality (philosophy) , requirement prioritization , software engineering , non functional requirement , reliability engineering , engineering , programming language , software , software development , software design , business , biochemistry , chemistry , philosophy , software construction , epistemology
I believe that most current requirement specifications lack clarity, and are very poor in their supporting information. We need to make requirement specifications ‘work harder’ by adding more ‘background’ to the requirements By ‘background’ I mean information related to the requirement that is not the core requirement itself. The background information I am referring to includes: prioritization (expressed by such means as ‘Justification’), risk management (expressed using such means as ‘Assumptions’), change management (for example, the integration requirements), and quality control (for example, the testability requirements). To improve requirement specification, I have developed a requirement specification language, as a subset of my planning language, ‘Planguage‘. This language has developed by practical need, in international industry over three decades, and is supplemented here with some recent ideas. This paper will give an overview of the conceptual basis and some sample detail.