Abstract
AbstractI 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.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
