Advertisement

Tackling Semi-automatic Trace Recovery for Large Specifications

  • Jörg Leuser
  • Daniel Ott
Part of the Lecture Notes in Computer Science book series (LNCS, volume 6182)

Abstract

[Context and motivation] Traceability is not as well established in the automobile industry as it is for instance in avionics. However, new standards require specifications to contain traces. Manually creating and maintaining traceability in large specifications is cumbersome and expensive. [Question/problem] This work investigates whether it is possible to semi-automatically recover traceability within natural language specifications (e.g. requirement and test specifications) using information retrieval algorithms. More specifically, this work deals with large, German specifications from the automobile industry. [Principal ideas/results] Using optimized algorithms, we are able to retrieve most of the traces. The remaining problem is the reduction of false-positive candidate traces. [Contribution] We identified optimizations that improve the retrieval quality: Use of meta-data, filtering of redundant texts, use of domain language, and dynamic identification of signals.

Keywords

Traceability Traceability Recovery German Specifications Large Specifications Natural Language Information Retrieval 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Antoniol, G., Canfora, G., Casazza, G., De Lucia, A.: Identifying the Starting Impact Set of a Maintenance Request: a Case Study. In: Proceedings of the Fourth European Software Maintenance and Reengineering, pp. 227–230 (2000)Google Scholar
  2. 2.
    Asuncion, H.U., Taylor, R.N.: Capturing Custom Link Semantics among Heterogeneous Artifacts and Tools. In: ICSE Workshop on Traceability in Emerging Forms of Software Engineering (2009)Google Scholar
  3. 3.
    Baeza-Yates, R., Ribeiro-Neto, B.A.: Modern Information Retrieval, reprint edn. Pearson Addison-Wesley (2006)Google Scholar
  4. 4.
    Boutkova, E.: Variantendokumentation in Lastenheften: State-of-the-Practice (Variant Documentation in Requirement Specifications). In: Systems Engineering Infrastructure Conference (November 2009)Google Scholar
  5. 5.
    Braschler, M., Ripplinger, B.: How Effective is Stemming and Decompounding for German Text Retrieval? Information Retrieval 7(3-4), 291–316 (2004)CrossRefGoogle Scholar
  6. 6.
    Cleland-Huang, J., Settimi, R., Duan, C., Zou, X.: Utilizing Supporting Evidence to Improve Dynamic Requirements Traceability. In: 13th IEEE International Conference on Requirements Engineering, pp. 135–144. IEEE CS, Los Alamitos (2005)CrossRefGoogle Scholar
  7. 7.
    De Lucia, A., Fasano, F., Oliveto, R., Tortora, G.: Enhancing an Artefact Management System with Traceability Recovery Features. In: 20th IEEE International Conference on Software Maintenance, pp. 306–315. IEEE CS, Los Alamitos (2004)CrossRefGoogle Scholar
  8. 8.
    De Lucia, A., Fasano, F., Oliveto, R., Tortora, G.: Can Information Retrieval Techniques effectively Support Traceability Link Recovery? In: 14th IEEE International Conference on Program Comprehension, pp. 307–316 (2006)Google Scholar
  9. 9.
    De Lucia, A., Fasano, F., Oliveto, R., Tortora, G.: Recovering Traceability Links in Software Artifact Management Systems Using Information Retrieval Methods. ACM Transactions on Software Engineering and Methodology 16(4), 13 (2007)CrossRefGoogle Scholar
  10. 10.
    Dreher, M.: Konstruktive und analytische Methoden zur Qualitätssicherung von Anforderungen in der Softwareentwicklung (Constructive and Analytical Methods for Quality Assurance of Requirements in SW Development). Stuttgart Media University, Diplomarbeit (2004)Google Scholar
  11. 11.
    Hayes, J.H., Dekhtyar, A., Osborne, J.: Improving Requirements Tracing via Information Retrieval. In: 11th IEEE International Requirements Engineering Conference, pp. 138–147 (2003)Google Scholar
  12. 12.
    Hayes, J.H., Dekhtyar, A.: Humans in the Traceability Loop: Can’t Live with ’em, Can’t Live without ’em. In: Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering, pp. 20–23. ACM, New York (2005)CrossRefGoogle Scholar
  13. 13.
    Hayes, J.H., Dekhtyar, A., Sundaram, S.K.: Advancing Candidate Link Generation for Requirements Tracing: The Study of Methods. IEEE Transactions on Software Engineering 32(1), 4–19 (2006)CrossRefGoogle Scholar
  14. 14.
    ISO/DIS 26262: Road Vehicles – Functional Safety. ISO (2009)Google Scholar
  15. 15.
    Kof, L.: Translation of Textual Specifications to Automata by Means of Discourse Context Modeling. In: Glinz, M., Heymans, P. (eds.) REFSQ 2009. LNCS, vol. 5512, pp. 197–211. Springer, Heidelberg (2009)CrossRefGoogle Scholar
  16. 16.
    Konrad, S., Gall, M.: Requirements Engineering in the Development of Large-Scale Systems. In: 16th IEEE International Conference on Requirements Engineering, pp. 217–222 (2008)Google Scholar
  17. 17.
    Leuser, J.: Challenges for Semi-automatic Trace Recovery in the Automotive Domain. In: ICSE Workshop on Traceability in Emerging Forms of Software Engineering, pp. 31–35 (May 2009)Google Scholar
  18. 18.
    Leuser, J.: Herausforderungen für halbautomatische Traceability-Erkennung (Challenges for Semi-automatic Trace Recovery). In: Systems Engineering Infrastructure Conference (November 2009)Google Scholar
  19. 19.
    Lormans, M., van Deursen, A.: Can LSI Help Reconstructing Requirements Traceability in Design and Test? In: Proceedings of the Conference on Software Maintenance and Reengineering, pp. 47–56. IEEE CS, Los Alamitos (2006)Google Scholar
  20. 20.
    Marcus, A., Maletic, J.I.: Recovering Documentation-to-Source-Code Traceability Links Using Latent Semantic Indexing. In: 25th International Conference on Software Engineering, 3rd edn., pp. 3–10 (2003)Google Scholar
  21. 21.
    McMillan, C., Poshyvanyk, D., Revelle, M.: Combining Textual and Structural Analysis of Software Artifacts for Traceability Link Recovery. In: ICSE Workshop on Traceability in Emerging Forms of Software Engineering, pp. 41–48 (May 2009)Google Scholar
  22. 22.
    Powers, T., Stubbs, C.: A Study on Current Practices of Requirements Traceability in Systems Development. Masterthesis, Naval Postgrad. School Monterey CA (1993)Google Scholar
  23. 23.
    Ratanotayanon, S., Sim, S.E., Raycraft, D.J.: Cross-Artifact Traceability Using Lightweight Links. In: ICSE Workshop on Traceability in Emerging Forms of Software Engineering, pp. 57–64 (May 2009)Google Scholar
  24. 24.
    Regnell, B., Svensson, R.B., Wnuk, K.: Can we Beat the Complexity of very Large-Scale Requirements Engineering? In: Paech, B., Rolland, C. (eds.) REFSQ 2008. LNCS, vol. 5025, pp. 123–128. Springer, Heidelberg (2008)CrossRefGoogle Scholar
  25. 25.
    Winkler, S.: Trace Retrieval for Evolving Artifacts. In: ICSE Workshop on Traceability in Emerging Forms of Software Engineering, pp. 49–56 (May 2009)Google Scholar
  26. 26.
    Yakoubi, R.: Empirische Bewertung von Qualitätsindikatoren für Anforderungsdokumente (Empirical Assessment of Quality Indicators for Requirement Specifications). Ulm University, Diplomarbeit (2009)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2010

Authors and Affiliations

  • Jörg Leuser
    • 1
  • Daniel Ott
    • 1
  1. 1.Daimler AG, Group Research & Advanced EngineeringUlmGermany

Personalised recommendations