Advertisement

Requirements Definition [1]

  • Erik W. Aslaksen

Abstract

In Sec. B4.2 we saw how a set of stakeholder requirements, as contained e.g. in a Requirements Definition Document (RDD), forms the starting point of the design process. The requirements document the interface between the stakeholders and the engineers, and any incompleteness or ambiguity in the requirements is bound to result in a less than satisfactory progression of the project. It is therefore not surprising that the process of defining and controlling requirements is a subject of much interest and activity in the engineering community, and numerous references can be found in [2]. A lively on-line discussion group is the INCOSE Requirements Working Group (see the corresponding web site at www.incose.org/ ).

Keywords

Unify Modelling Language Requirement Engineer Context Dependency Definition Process Software Requirement Specification 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Much of the material in this Chapter was presented in Aslaksen, E.W., Requirements Definition - A Plea For a Return To English. In: Proc. Thirteenth Int’l Symposium of INCOSE, Arlington, VA, July 1-3 (2003) Google Scholar
  2. 2.
    Some papers that contain substantial lists of references are: van Lamsweerde, A.: Requirements Engineering in the Year 00: A Research Perspective. In: Proc. 22nd Int’l Conference on Software Engineering, Limerick. ACM Press (June 2000); Nuseibeh, B., Easterbrook, S.: Requirements Engineering: A Roadmap. In: Finkelstein, A. (ed.) ICSE 2000, Future of Software Engineering, Limerick, Ireland, June 4-11. ACM Press (2000); Gambhir, S.G.: An Investigation of Facilitor-Assisted and CONOPS-Based Requirements Elicitation Methods Using a 2x2 Factorial Experimental Design. Systems Engineering 4(4), 272–286 (2001); A more recent book is that by Hood, C., Wiedemann, S., Fichtinger, S., Pautz, U.: Requirements Management: Interface Between Requirements Development and All Other Engineering Processes. Springer, Berlin (2007) Google Scholar
  3. 3.
    Thomas, J.D.: Composition for Technical Students, revised. Charles Scribner’s Sons, New York (1957)Google Scholar
  4. 4.
    Alexander, I.: The Glamour of Formalisation - A Warning, http://easyweb.easynet.co.uk/~iany/consultancy/glamour.html
  5. 5.
    The issue of software as a special case within engineering is the topic of the article by Aslaksen, E.W., Why Software Is Different, Systems Engineering Society of Australia (SESA) Newsletter No. 48 (July 2009) Google Scholar
  6. 6.
    Introductions to the relevant parts of Chomsky’s work can be found in Chomsky, N.: Syntactic Structures. Houton & Co., S’Gravenhage (1957); 2nd printing (1962); Chomsky, N.: Language and Mind, Enlarged Edition, Harcourt Brace Jovanovich, Inc. (1972); and Smith, N., Wilson, D.: Modern Linguistics. Penguin Books Ltd. (1979) Google Scholar
  7. 7.
    Aslaksen, E.W.: Systems Engineering and System Specification. J. Electrical and Electronics Eng. Aust. 7(3), 159–165 (1987)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  1. 1.Gumbooya Pty Ltd.Allambie HeightsAustralia

Personalised recommendations