Requirements Engineering

, Volume 3, Issue 2, pp 107–114 | Cite as

Requirement decomposition and traceability

  • David P. Kirkman


When producing large systems, it is important that the requirement decomposition process is performed correctly, with requirement traceability maintained. This paper explores this area, using examples from industry to illustrate the problems which can be encountered if traceability/decomposition is not performed correctly. It is hoped that this paper will assist the reader in generating a more precise definition of some general system engineering concerns such as when decomposition needs to be performed, with the requirements hierarchy extended. For the problems covered, this paper also suggests methods by which they can be alleviated or recognised once they have occurred. This additional information is primarily aimed at people who are using tools to manage their requirements, as there may be mechanisms to automate these methods. This paper presents the personal view of the author, based on his many years of experience in this area.


Requirements decomposition Requirements hierarchy Requirements management Requirements problems Requirements traceability 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Mazza C, Fairclough J, Melton B, De Pablo D, Scheffer A, Stevens R. Software engineering standards. Prentice-Hall, Englewood Cliffs, NJ, 1994 (earlier version in 1987)Google Scholar
  2. 2.
    BS6719. Specifying user requirements for a computer based system, 1986Google Scholar
  3. 3.
    IEE 830. Guide to software requirements specifications, 1984Google Scholar
  4. 4.
    IEE 1220. Standard for application and management of the system engineering process, Issue 1Google Scholar
  5. 5.
    DOD STD 490A. Military standard specification practices, Issue 1Google Scholar
  6. 6.
    Paulk M, Curtis W, Chrissis M, Weber C. Maturity model for software, Version 1.1, CMU/SEI-93-TR-24. Software Engineering Institute. Pittsburg, PA, 1993Google Scholar
  7. 7.
    Davis A. Tracing: a simple necessity neglected. IEEE Software 1995; 12(5)Google Scholar
  8. 8.
    Ramesh B, Powers T, Stubbs C. Implementing requirements traceability: a case study. In: Proceedings of the 2nd IEEE international symposium on requirements engineering (RE 95), York, 1995Google Scholar
  9. 9.
    Nelsen E. System engineering and requirements allocation. In: Thayer R, Dorfman M (eds), System and software requirements engineering. IEEE Computer Society Press, Washington, DC, 1990.Google Scholar
  10. 10.
    Hutchings A, Knox S. Creating products customers demand. Commun ACM 195;38(5)Google Scholar
  11. 11.
    Potts C. Invented requirements and imagined customers: requirements engineering for off-the-shelf software. In: Proceedings of the 2nd IEEE international symposium on requirements engineering (RE 95), York, 1995Google Scholar

Copyright information

© Springer-Verlag London Limited 1998

Authors and Affiliations

  1. 1.Logical UK Ltd (Bristol Office)BristolUK

Personalised recommendations