Advertisement

Tailoring Software Traceability to Value-Based Needs

  • Alexander Egyed

Abstract:

Software development generates and maintains a wide range of artifacts, such as documentation, requirements, design models, and test scenarios; all of which add value to the understanding of the software system. Trace dependencies identify the relationships among these artifacts. They contribute to the better understanding of a software system as they link its distributed knowledge. Trace dependencies are also vital for many automated analyses including the impact of change and consistency checking. This chapter compares the problem of manual traceability versus automated traceability with the Trace/Analyzer approach. This chapter also explores how to tailor precision, completeness, correctness, and timeliness to adjust the trace analysis to value-based needs.

Keywords:

Traceability software modeling trace analysis trade-off analysis consistency impact of change change propagation traceability uncertainties 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References Β

  1. (Antoniol et al., 2002)
    Antoniol, G., Canfora, G., Casazza, G., De Lucia, A., and Merlo, E.: Recovering Traceability Links between Code and Documentation, IEEE Transactions on Software Engineering, 28(10), pp 970–983Google Scholar
  2. (Biffl and Halling, 2003).
    Biffl, S. and Halling M.: Investigating the Defect Detection Effectiveness and Cost-Benefit of Nominal Inspection Teams, IEEE Transactions on Software Engineering, 29(5), pp 385–397Google Scholar
  3. (Boehm, 2003).
    Boehm, B. W.: Value-Based Software Engineering, Software Engineering Notes, 28(2), pp 1–12Google Scholar
  4. (Boehm and Huang, 2003).
    Boehm, B. W. and Huang, L.G.: Value-Based Software Engineering: A Case Study, IEEE Computer, 36(3), pp 33–41Google Scholar
  5. (Boehm et al., 1998)
    Boehm, B. W., Egyed, A., Kwan, J., and Madachy, R.: Using the WinWin Spiral Model: A Case Study, IEEE Computer, pp 33–44Google Scholar
  6. (Boehm et al., 2000)
    Boehm, B. W., Abts, C., Brown, A.W., Chulani, W., Clark, B.K., Horowitz, E., Madacy, R., Reifer, D., and Steece, B.: Software Cost Estimation with COCOMO II, (Prentice Hall, New Jersey, 2000)Google Scholar
  7. (Card, 1992).
    Card, D.N.: Designing Software for Producibility, Journal of Systems and Software, 17(3), pp 219–225Google Scholar
  8. (Cross, 1991).
    Cross, G.M.: Requirements and Traceability Management, Proceedings of the International Conference on Software for Guidance and Control, pp 4/1–4/4Google Scholar
  9. (Egyed, 2002).
    Egyed, A.: A Scenario-Driven Approach to Trace Dependency Analysis, IEEE Transactions on Software Engineering (TSE), Volume 29, Number 2, pp 116–132Google Scholar
  10. (Egyed, 2004).
    Egyed, A.: Resolving Uncertainties during Trace Analysis, Proceedings of the 12th ACM SIGSOFT Symposium on Foundations of Software Engineering (FSE), 3–12Google Scholar
  11. (Egyed and Grünbacher, 2002).
    Egyed, A. and Grünbacher, P.: Automating Requirements Traceability — Beyond the Record and Replay Paradigm, Proceedings of the 17th International Conference on Automated Software Engineering (ASE), pp 163–171Google Scholar
  12. (Egyed and Grünbacher, 2004).
    Egyed, A. and Grünbacher, P.: Identifying Requirements Conflicts and Cooperation: How Quality Attributes and Automated Traceability Can Help, IEEE Software, 21(6), pp 50–58Google Scholar
  13. (Finkelstein et al., 1991)
    Finkelstein, A., Kramer, J., Nuseibeh, B., Finkelstein, L., and Goedicke, M.: Viewpoints: A Framework for Integrating Multiple Perspectives in System Development, International Journal on Software Engineering and Knowledge Engineering, pp 31–58Google Scholar
  14. (Gotel and Finkelstein, 1994).
    Gotel, O.C.Z. and Finkelstein, A.C.W.: An Analysis of the Requirements Traceability Problem, Proceedings of the First International Conference on Requirements Engineering, pp 94–101Google Scholar
  15. (Jacobson, 1987).
    Jacobson, I.: Object Oriented Development in an Industrial Environment, Proceedings of the International Conference on Object-Oriented Programming Systems, Languages, and Applications (OOPSLA), pp 183–191Google Scholar
  16. (Lindvall, 1994).
    Lindvall: A Study of Traceability in Object-Oriented Systems Development, PhD Thesis Tech Report No 462, Linköping University, Institute of Technology, SwedenGoogle Scholar
  17. (Lindvall and Sandahl, 1996).
    Lindvall, M. and Sandahl, K.: Practical Implications of Traceability, Journal on Software — Practice and Experience (SPE), 26(10), pp 1161–1180Google Scholar
  18. (Moore, 1995).
    Moore, G.: Inside the Tornado, (, Harper Collins Publishers, 1995)Google Scholar
  19. (Nuseibeh, 2001).
    Nuseibeh, B.: Weaving Together Requirements and Architectures, IEEE Computer, 34(2), pp 115–117Google Scholar
  20. (Övergaard, 1998).
    Övergaard, G.: A Formal Approach to Relationships in the Unified Modeling Language, Proceedings of the Workshop on Precise Semantics for Software Modeling Techniques (PSMT’98), pp 91–108Google Scholar
  21. (Pfleeger and Bohner, 1990).
    Pfleeger, S.L. and Bohner, S.A.: A Framework for Software Maintenance Metrics, IEEE Transactions on Software Engineering, 16(5), pp 320–327Google Scholar
  22. (Pohl, 1996).
    Pohl, K.: PRO-ART: Enabling Requirements Pre-Traceability, Proceedings of the 2nd International Conference on Requirements Engineering (ICRE), pp 76–85Google Scholar
  23. (Ramesh, 1993).
    Ramesh: A Model of Requirements Traceability for Systems Development, Technical Report, Naval Postgraduate School, MontereyGoogle Scholar
  24. (Rumbaugh et al., 1999)
    Rumbaugh, J., Jacobson, I., and Booch, G.: The Unified Modeling Language Reference Manual, (Addison Wesley1999)Google Scholar
  25. (Tilbury, 1989).
    Tilbury, A.M.: Enabling Software Traceability, In IEE Colloquium on the Application of Computer Aided Software Engineering Tool, London, UKGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Alexander Egyed
    • 1
  1. 1.Teknowledge CorporationMarina Del ReyUSA

Personalised recommendations