Software & Systems Modeling

, Volume 9, Issue 4, pp 529–565 | Cite as

A survey of traceability in requirements engineering and model-driven development

Theme Section

Abstract

Traceability—the ability to follow the life of software artifacts—is a topic of great interest to software developers in general, and to requirements engineers and model-driven developers in particular. This article aims to bring those stakeholders together by providing an overview of the current state of traceability research and practice in both areas. As part of an extensive literature survey, we identify commonalities and differences in these areas and uncover several unresolved challenges which affect both domains. A good common foundation for further advances regarding these challenges appears to be a combination of the formal basis and the automated recording opportunities of MDD on the one hand, and the more holistic view of traceability in the requirements engineering domain on the other hand.

Keywords

Requirements engineering Model-driven engineering Model-driven development Traceability 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Aizenbud-Reshef N., Nolan B.T., Rubin J., Shaham-Gafni Y.: Model traceability. IBM Syst. J. 45(3), 515–526 (2006)CrossRefGoogle Scholar
  2. 2.
    Aizenbud-Reshef, N., Paige, R.F., Rubin, J., Shaham-Gafni, Y., Kolovos, D.S.: Operational semantics for traceability. In: ECMDA Traceability Workshop (ECMDA-TW) 2005 Proceedings, pp. 8–14. Sintef, Trondheim (2005). ISBN 978-82-14-03813-2Google Scholar
  3. 3.
    Albinet, A., Boulanger, J.L., Dubois, H., Peraldi-Frati, M.A., Sorel, Y., Van, Q.D.: Model-based methodology for requirements traceability in embedded systems. In: ECMDA Traceability Workshop (ECMDA-TW) 2007 Proceedings, pp. 27–36. Sintef, Trondheim (2007). ISBN 978-82-14-04056-2Google Scholar
  4. 4.
    Alexander, I.: Towards automatic traceability in industrial practice. In: Proceedings of the 1st International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE ’02). ACM, New York (2002)Google Scholar
  5. 5.
    Alexander, I.: Semiautomatic tracing of requirement versions to use cases. In: Proceedings of the 2nd International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE ’03). ACM, New York (2003)Google Scholar
  6. 6.
    Alexander I.: A taxonomy of stakeholders, human roles in system development. In: Stahl, B.C. (eds) Issues and Trends in Technology and Human Interaction., pp. 25–71. IRM Press, Hershey (2006) ISBN 978-1-599-04269-5Google Scholar
  7. 7.
    Alexander, I., Robertson, S., Maiden, N.: What influences the requirements process in industry? A report on industrial practice. In: 13th IEEE International Requirements Engineering Conference (RE’05) Proceedings, pp. 411–415. IEEE Computer Society, New York (2005)Google Scholar
  8. 8.
    Amar, B., Leblanc, H., Coulette, B.: A traceability engine dedicated to model transformation for software engineering. In: ECMDA Traceability Workshop (ECMDA-TW) 2008 Proceedings, pp. 7–16. Sintef, Trondheim (2008). ISBN 978-82-14-04396-9Google Scholar
  9. 9.
    Anderson K.M., Taylor R.N., Whitehead E.J. Jr: Chimera: hypermedia for heterogeneous software development enviroments. ACM Trans. Inf. Syst. 18(3), 211–245 (2000)CrossRefGoogle Scholar
  10. 10.
    Anquetil, N., Grammel, B., Galvão, I., Noppen, J., Khan, S.S., Arboleda, H., Rashid, A., Garcia, A.: Traceability for model driven, software product line engineering. In: ECMDA Traceability Workshop (ECMDA-TW) 2008 Proceedings, pp. 77–86. Sintef, Trondheim (2008). ISBN 978-82-14-04396-9Google Scholar
  11. 11.
    ANSI. ANSI-X3.138-1988: Information Resource Dictionary System (IRDS). American National Standards for Information Systems, New York (1988)Google Scholar
  12. 12.
    Antoniol G., Canfora G., Casazza G., Lucia A.D.: Maintaining traceability links during object-oriented software evolution. Softw. Pract. Experience 31(4), 331–355 (2001)MATHCrossRefGoogle Scholar
  13. 13.
    Antoniol G., Canfora G., Casazza G., Lucia A.D., Merlo E.: Recovering traceability links between code and documentation. IEEE Trans. Softw. Eng. 28(10), 970–983 (2002)CrossRefGoogle Scholar
  14. 14.
    Antoniol, G., Merlo, E., Guéhéneuc, Y.G., Sahraoui, H.: On feature traceability in object oriented programs. In: TEFSE ’05: Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering, pp. 73–78. ACM, New York (2005)Google Scholar
  15. 15.
    Arkley, P., Manson, P., Riddle, S.: Enabling traceability. In: Proceedings of the 1st International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE ’02). ACM, New York (2002)Google Scholar
  16. 16.
    Arkley, P., Riddle, S.: Overcoming the traceability benefit problem. In: 13th IEEE International Conference on Requirements Engineering (RE’05) Proceedings, pp. 385–389. IEEE Computer Society, New York (2005)Google Scholar
  17. 17.
    Asuncion, H.U., François, F., Taylor, R.N.: An end-to-end industrial software traceability tool. In: ESEC-FSE ’07: Proceedings of the 6th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on The Foundations of Software Engineering, pp. 115–124. ACM, New York (2007)Google Scholar
  18. 18.
    Baeza-Yates R.A., Ribeiro-Neto B.: Modern Information Retrieval, 1st edn. Addison-Wesley, Boston (1999) ISBN 978-0-201-39829-8Google Scholar
  19. 19.
    Barbero, M., del Fabro, M.D., Bézivin, J.: Traceability and provenance issues in global model management. In: ECMDA Traceability Workshop (ECMDA-TW) 2007 Proceedings, pp. 47–55. Sintef, Trondheim (2007). ISBN 978-82-14-04056-2Google Scholar
  20. 20.
    Bézivin, J., Jouault, F., Rosenthal, P., Valduriez, P.: Modeling in the large and modeling in the small. In: Aßmann, U., Aksit, M., Rensink, A. (eds.) Model Driven Architecture: MDAFA 2003 and MDAFA 2004 Selected Papers. Lecture Notes in Computer Science, vol. 3599, pp. 33–46. Springer, Berlin (2005). ISBN 978-3-540-28240-2Google Scholar
  21. 21.
    Blanc, X., Gervais, M.P., Sriplakich, P.: Model bus: towards the interoperability of modelling tools. In: Aßmann, U., Aksit, M., Rensink, A. (eds.) Model Driven Architecture: MDAFA 2003 and MDAFA 2004 Selected Papers. Lecture Notes in Computer Science, vol. 3599, pp. 17–32. Springer, Berlin (2005). ISBN 978-3-540-28240-2Google Scholar
  22. 22.
    Boldyreff, C., Nutter, D., Rank, S.: Active artefact management for distributed software engineering. In: Proceedings of the 26th IEEE Annual International Conference on Computer Software and Applications, pp. 1081–1086. IEEE Computer Society, New York (2002)Google Scholar
  23. 23.
    Brasethvik T., Gulla J.A.: Natural language analysis for semantic document modeling. Data Knowl. Eng. 38(1), 45–62 (2001)MATHCrossRefGoogle Scholar
  24. 24.
    Braun, A., Bruegge, B., Dutoit, A.: Supporting informal meetings in requirements engineering. In: Requirements Engineering: Foundation for Software Quality (REFSQ’01) Proceedings, pp. 26–40. http://refsq.org (2001)
  25. 25.
    Brcina, R., Riebisch, M.: Defining a traceability link semantics for design decision support. In: ECMDA Traceability Workshop (ECMDA-TW) 2008 Proceedings, pp. 39–48. Sintef, Trondheim (2008). ISBN 978-82-14-04396-9Google Scholar
  26. 26.
    Briand, L.C., Labiche, Y., O’Sullivan, L.: Impact analysis and change management of UML models. In: ICSM ’03: Proceedings of the International Conference on Software Maintenance, pp. 256–265. IEEE Computer Society, New York (2003)Google Scholar
  27. 27.
    Brinkkemper, S.: Requirements engineering research the industry is and is not waiting for. In: Requirements Engineering: Foundation for Software Quality (REFSQ’04) Proceedings, pp. 41–54. http://refsq.org (2004)
  28. 28.
    Brooks F.P.: No silver bullet: essence and accidents of software engineering. IEEE Comp. 20(4), 10–19 (1987)MathSciNetGoogle Scholar
  29. 29.
    Bui T.X., Bodart F., Ma P.C.: ARBAS: a formal language to support argumentation in network-based organizations. J. Manag. Inf. Syst. 14(3), 223–237 (1997) ISSN 0742-1222Google Scholar
  30. 30.
    Campos P., Nunes N.J.: Practitioner tools and workstyles for user-interface design. IEEE Softw. 24(1), 73–80 (2007)CrossRefGoogle Scholar
  31. 31.
    Card D.N.: Designing software for producibility. J. Syst. Softw. 17(3), 219–225 (1992)CrossRefGoogle Scholar
  32. 32.
    Cerbah F., Euzenat J.: Traceability between models and texts through terminology. Data Knowl. Eng. 38(1), 31–43 (2001)MATHCrossRefGoogle Scholar
  33. 33.
    Chen J.Y.J., Chou S.C.: Consistency management in a process environment. J. Syst. Softw. 47, 105–110 (1999)CrossRefGoogle Scholar
  34. 34.
    Chikofsky E.J., Rubenstein B.L.: CASE: reliability engineering for information systems. IEEE Softw. 5(2), 11–16 (1988)CrossRefGoogle Scholar
  35. 35.
    Cleland-Huang J., Berenbach B., Clark S., Settimi R., Romanova E.: Best practices for automated traceability. IEEE Comp. 40(6), 27–35 (2007)Google Scholar
  36. 36.
    Cleland-Huang J., Chang C.K., Christensen M.: Event-based traceability for managing evolutionary change. IEEE Trans. Softw. Eng. 29(9), 796–810 (2003)CrossRefGoogle Scholar
  37. 37.
    Cleland-Huang, J., Dekhtyar, A., Hayes, J.H.: Problem Statements and Grand Challenges. Tech. Rep. COET-GCT-06-01-0.9, Center of Excellence for Traceability. http://www.traceabilitycenter.org/downloads/documents/GrandChallenges/ (2006)
  38. 38.
    Cleland-Huang, J., Habrat, R.: Visual support in automated tracing. In: 2nd International Workshop on Requirements Engineering Visualization (REV 2007). IEEE Computer Society, New York (2007)Google Scholar
  39. 39.
    Cleland-Huang J., Chang K.C., Wise J.C.: Automating performance related impact analysis through event based traceability. Requir. Eng. J. 8(3), 171–182 (2003)CrossRefGoogle Scholar
  40. 40.
    Cleland-Huang, J., Settimi, R., Duan, C., Zou, X.: Utilizing supporting evidence to improve dynamic requirements traceability. In: 13th IEEE International Requirements Engineering Conference (RE’05) Proceedings, pp. 135–144. IEEE Computer Society, New York (2005)Google Scholar
  41. 41.
    Cleland-Huang, J., Zemont, G., Lukasik, W.: A heterogeneous solution for improving the return on investment of requirements traceability. In: 12th IEEE International Requirements Engineering Conference (RE’04) Proceedings, pp. 230–239. IEEE Computer Society, New York (2004)Google Scholar
  42. 42.
    Conklin J., Begeman M.L.: gIBIS: a hypertext tool for exploratory policy discussion. ACM Trans. Inf. Syst. 6(4), 303–331 (1988)CrossRefGoogle Scholar
  43. 43.
    Costa, M., da Silva, A.R.: RT-MDD framework—a practical approach. In: ECMDA Traceability Workshop (ECMDA-TW) 2007 Proceedings, pp. 17–26. Sintef, Trondheim (2007). ISBN 978-82-14-04056-2Google Scholar
  44. 44.
    Dahlstedt, Å.G., Persson, A.: Requirements interdependencies: state of the art and future challenges. In: Engineering and Managing Software Requirements, pp. 95–116. Springer, Berlin (2005). ISBN 978-3-540-25043-2Google Scholar
  45. 45.
    de Lucia, A., Fasano, F., Oliveto, R., Tortora, G.: ADAMS Re-Trace: a traceability recovery tool. In: CSMR ’05: Proceedings of the 9th European Conference on Software Maintenance and Reengineering, pp. 32–41. IEEE Computer Society, New York (2005)Google Scholar
  46. 46.
    de Lucia A., Fasano F., Oliveto R., Tortora G.: Recovering traceability links in software artefact management systems using information retrieval methods. ACM Trans. Softw. Eng. Meth. 16(4), 13/1–13/50 (2007)Google Scholar
  47. 47.
    Decker, B., Ras, E., Rech, J., Klein, B., Höcht, C.: Self-organized reuse of software engineering knowledge supported by semantic wikis. In: Workshop on Semantic Web Enabled Software Engineering (SWESE) Proceedings. http://www.mel.nist.gov/msid/conferences/SWESE/ (2005)
  48. 48.
    Dekhtyar, A., Hayes, J.H., Sundaram, S., Holbrook, A., Dekhtyar, O.: Technique integration for requirements assessment. In: 15th IEEE International Requirements Engineering Conference (RE’07) Proceedings, pp. 141–150. IEEE Computer Society, New York (2007)Google Scholar
  49. 49.
    Deng M., Stirewalt R.E.K., Cheng B.H.C.: Retrieval by construction: a traceability technique to support verification and validation of UML formalizations. Int. J. Softw. Eng. Knowl. Eng. 15(5), 837–872 (2005)CrossRefGoogle Scholar
  50. 50.
    Derniame, J.C., Kaba, B.A., Wastell, D.G. (eds.): Software Process: Principles, Methodology, Technology. Lecture Notes in Computer Science, vol. 1500. Springer, Berlin (1999). ISBN 978-3-540-65516-9Google Scholar
  51. 51.
    Dick, J.: Rich traceability. In: Proceedings of the 1st International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE ’02). ACM, New York (2002)Google Scholar
  52. 52.
    Dömges R., Pohl K.: Adapting traceability environments to project-specific needs. Commun. ACM 41(12), 54–62 (1998)CrossRefGoogle Scholar
  53. 53.
    dos Santos Soares M., Vrancken J.L.M.: Model-driven user requirements specification using SysML. J. Softw. 3(6), 57–68 (2008)Google Scholar
  54. 54.
    Drivalos, N., Kolovos, D.S., Paige, R.F., Fernandes, K.J.: Engineering a DSL for software traceability. In: Gaševic, D., Lämmel, R., van Wyk, E. (eds) Proceedings of the 1st International Conference on Software Languages Engineering, SLE ’08. Lecture Notes in Computer Science, vol. 5452. Springer, Berlin (2008). ISBN 978-3-642-00433-9Google Scholar
  55. 55.
    Duan, C., Cleland-Huang, J.: Visualization and analysis in automated trace retrieval. In: 1st International Workshop on Requirements Engineering Visualization (REV’06). IEEE Computer Society, New York (2006)Google Scholar
  56. 56.
    Dutoit, A.H., McCall, R., Mistrik, I., Paech, B. (eds): Rationale Management in Software Engineering. Springer, Berlin (2006) ISBN 978-3-540-30997-0Google Scholar
  57. 57.
    Dutoit A.H., Paech B.: Rationale management in software engineering. In: Chang, S.K. (eds) Handbook of Software Engineering and Knowledge Engineering, vol. 1—Fundamentals, pp. 787–816. World Scientific, Singapore (2001) ISBN 978-9-810-24973-1CrossRefGoogle Scholar
  58. 58.
    Ebner G., Kaindl H.: Tracing all around in reengineering. IEEE Softw. 19(3), 70–77 (2002)CrossRefGoogle Scholar
  59. 59.
    Egyed A.: Tailoring software traceability to value-based needs. In: Biffl, S., Aurum, A., Boehm, B., Erdogmus, H., Grünbacher, P. (eds) Value-Based Software Engineering, Springer, Berlin (2005) ISBN 978-3-540-25993-0Google Scholar
  60. 60.
    Egyed, A.: Fixing inconsistencies in UML design models. In ICSE ’07: Proceedings of the 29th International Conference on Software Engineering pp. 292–301. IEEE Computer Society, New York (2007)Google Scholar
  61. 61.
    Egyed A., Grünbacher P.: Supporting software understanding with automated requirements traceability. Int. J. Softw. Eng. Knowl. Eng. 15(5), 783–810 (2005)CrossRefGoogle Scholar
  62. 62.
    Egyed, A., Grünbacher, P., Heindl, M., Biffl, S.: Value-based requirements traceability: lessons learned. In: 15th IEEE International Requirements Engineering Conference (RE’07) Proceedings, pp. 115–118. IEEE Computer Society, New York (2007)Google Scholar
  63. 63.
    Espinoza, A., Alarcon, P.P., Garbajosa, J.: Analyzing and systematizing current traceability schemas. In: Proceedings of the 30th Annual IEEE/NASA Software Engineering Workshop, pp. 21–32. IEEE Computer Society, New York (2006)Google Scholar
  64. 64.
    Falleri, J.R., Huchard, M., Nebut, C.: Towards a traceability framework for model transformations in Kermeta. In: ECMDA Traceability Workshop (ECMDA-TW) 2006 Proceedings, pp. 31–40. Sintef, Trondheim (2006). ISBN 978-82-14-04030-2Google Scholar
  65. 65.
    France, R., Rumpe, B.: Model-driven development of complex software: a research roadmap. In: FOSE ’07: Future of Software Engineering Proceedings, pp. 37–54. IEEE Computer Society, New York (2007)Google Scholar
  66. 66.
    Fritzsche, M., Johannes, J., Zschaler, S., Zherebtsov, A., Terekhov, A.: Application of tracing techniques in model-driven performance engineering. In: ECMDA Traceability Workshop (ECMDA-TW) 2008 Proceedings, pp. 111–120. Sintef, Trondheim (2008). ISBN 978-82-14-04396-9Google Scholar
  67. 67.
    Galvão, I., Göknil, A.: Survey of traceability approaches in model-driven engineering. In: Proceedings of the 11th IEEE International EDOC Enterprise Computing Conference, pp. 313–324. IEEE Computer Society, New York (2007)Google Scholar
  68. 68.
    Gervasi V., Zowghi D.: Reasoning about inconsistencies in natural language requirements. ACM Trans. Softw. Eng. Meth. 14(3), 277–330 (2005)CrossRefGoogle Scholar
  69. 69.
    Gills, M.: Survey of traceability models in IT projects. In: ECMDA Traceability Workshop (ECMDA-TW) 2005 Proceedings, pp. 39–46. Sintef, Trondheim (2005). ISBN 978-82-14-03813-2Google Scholar
  70. 70.
    Glitia F., Etien A., Dumoulin C.: Fine grained traceability for an MDE approach of embedded system conception. In: Oldevik, J., Aagedal, J.Ø. (eds) ECMDA Traceability Workshop (ECMDA-TW) 2008 Proceedings., pp. 27–38. Sintef, Trondheim (2008) ISBN 978-82-14-04396-9Google Scholar
  71. 71.
    Goguen, J.A.: Formality and informality in requirements engineering. In: 2nd International Requirements Engineering Conference (ICRE’96) Proceedings. IEEE Computer Society, New York (1996)Google Scholar
  72. 72.
    Göknil, A., Kurtev, I., van den Berg, K.: Change impact analysis based on formalization of trace relations for requirements. In: ECMDA Traceability Workshop (ECMDA-TW) 2008 Proceedings, pp. 59–75. Sintef, Trondheim (2008). ISBN 978-82-14-04396-9Google Scholar
  73. 73.
    Gotel, O.C.Z.: Contribution Structures for Requirements Traceability. Ph.D. thesis, Imperial College of Science, Technology and Medicine, University of London (1995)Google Scholar
  74. 74.
    Gotel, O.C.Z., Finkelstein, A.C.W.: An analysis of the requirements traceability problem. In: 1st IEEE International Requirements Engineering Conference (RE’94) Proceedings, pp. 94–101. IEEE Computer Society, New York (1994)Google Scholar
  75. 75.
    Gotel, O.C.Z., Morris, S.J.: Macro-level traceability via media transformations. In: Paech, B., Rolland, C. (eds.) Requirements Engineering: Foundation for Software Quality (REFSQ’08) Proceedings. Lecture Notes in Computer Science, vol. 5025, pp. 129–134. Springer, Berlin (2008). ISBN 978-3-540-69060-3Google Scholar
  76. 76.
    Grechanik, M., McKinley, K.S., Perry, D.E.: Recovering and using use-case-diagram-to-source-code traceability links. In: ESEC-FSE ’07: Proceedings of the 6th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on The Foundations of Software Engineering, pp. 95–104. ACM, New York (2007)Google Scholar
  77. 77.
    Hapke, M., Jaszkiewicz, A., Kowalczykiewicz, K., Weiss, D., Zielniewicz, P.: OPHELIA—open platform for distributed software development. In: Open Source for an Information and knowledge society: Proceedings of the Open Source International Conference. Malaga, Spain. http://malaga04.opensourceworldconference.com/ (2004)
  78. 78.
    Hardman L., Bulterman D.C.A., van Rossum G.: The Amsterdam hypermedia model: adding time and context to the Dexter model. Commun. ACM 37(2), 50–62 (1994)CrossRefGoogle Scholar
  79. 79.
    Haumer, P., Pohl, K., Weidenhaupt, K., Jarke, M.: Improving reviews by extended traceability. In: Proceedings of the 32nd Hawaii International Conference on System Sciences. IEEE Computer Society, New York (1999)Google Scholar
  80. 80.
    Hayes J.H., Dekhtyar A.: A framework for comparing requirements tracing experiments. Int. J. Softw. Eng. Knowl. Eng. 15(5), 751–781 (2005)CrossRefGoogle Scholar
  81. 81.
    Hayes, J.H., Dekhtyar, A.: Humans in the traceability loop: can’t live with ’em, can’t live without ’em. In: TEFSE ’05: Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering, pp. 20–23. ACM, New York (2005)Google Scholar
  82. 82.
    Hayes J.H., Dekhtyar A., Sundaram S.K.: Advancing candidate link generation for requirements tracing: the study of methods. IEEE Trans. Softw. Eng. 32(01), 4–19 (2006)CrossRefGoogle Scholar
  83. 83.
    Hayes, J.H., Dekhtyar, A., Sundaram, S.K., Howard, S.: Helping analysts trace requirements: an objective look. In: 12th IEEE International Requirements Engineering Conference (RE’04) Proceedings, pp. 249–259. IEEE Computer Society, New York (2004)Google Scholar
  84. 84.
    Heindl, M., Biffl, S.: A case study on value-based requirements tracing. In: Proceedings of the Joint 10th European Software Engineering Conference (ESEC) and the 13th ACM SIGSOFT Symposium on the Foundations of Software Engineering (FSE-13), pp. 60–69. ACM, New York (2005)Google Scholar
  85. 85.
    Heindl, M., Biffl, S.: Modeling of requirements tracing. In: Meyer, B., Nawrocki, J.R., Walter, B. (eds.) Balancing Agility and Formalism in Software Engineering (CEE-SET 2007). Lecture Notes in Computer Science, vol. 5082, pp. 267–278. Springer, Berlin (2008)Google Scholar
  86. 86.
    Herman I., Melancon G., Marshall M.S.: Graph visualization and navigation in information visualization: a survey. IEEE Trans. Vis. Comp. Graph. 06(1), 24–43 (2000)CrossRefGoogle Scholar
  87. 87.
    Hoffmann, M., Kühn, N., Bittner, M.: Requirements for requirements management tools. In: 12th IEEE International Conference on Requirements Engineering (RE’04) Proceedings, pp. 301–308. IEEE Computer Society, New York (2004)Google Scholar
  88. 88.
    Hofmann H.F., Lehner F.: Requirements engineering as a success factor in software projects. IEEE Softw. 18(4), 58–66 (2001)CrossRefGoogle Scholar
  89. 89.
    IEEE: IEEE Guide to Software Requirements Specification, ANSI/IEEE Std 830-1984. IEEE Press, Piscataway (1984)Google Scholar
  90. 90.
    IEEE: IEEE Standard Glossary of Software Engineering Terminology. IEEE Press, Piscataway (1990)Google Scholar
  91. 91.
    Ilieva, M.G., Ormandjieva, O.: Models derived from automatically analyzed textual user requirements. In: 4th International Conference on Software Engineering Research, Management and Applications, pp. 13–21. IEEE Computer Society, New York (2006)Google Scholar
  92. 92.
    Ilieva, M., Ormandjieva, O.: Automatic transition of natural language software requirements specification into formal presentation. In: Montoyo, A., Muñoz, R., Métais, E. (eds.) Natural Language Processing and Information Systems. Lecture Notes in Computer Science, vol. 3513, pp. 392–397. Springer, Berlin (2005)Google Scholar
  93. 93.
    Jacobson, I.: Object-oriented development in an industrial environment. In: OOPSLA ’87: Conference Proceedings on Object-Oriented Programming Systems, Languages and Applications, pp. 183–191. ACM, New York (1987)Google Scholar
  94. 94.
    Jarke, M., Rolland, C., Sutcliffe, A. (eds): The NATURE of Requirements Engineering. Shaker, Aachen (1999) ISBN 978-3-8265-6174-0Google Scholar
  95. 95.
    Jarke M.: Requirements tracing. Commun. ACM 41(12), 32–36 (1998)CrossRefGoogle Scholar
  96. 96.
    Jarke, M., Pohl, K.: Information systems quality and quality informations systems. In: The Impact of Computer Supported Technologies in Information Systems Development, IFIP Transactions, pp. 345–375. Elsevier Science, North-Holland (1992)Google Scholar
  97. 97.
    Jirapanthong W., Zisman A.: XTraQue: traceability for product line systems. J. Softw. Syst. Model. 8(1), 117–144 (2009)CrossRefGoogle Scholar
  98. 98.
    Jouault, F.: Loosely coupled traceability for ATL. In: ECMDA Traceability Workshop (ECMDA-TW) 2005 Proceedings, pp. 29–37. Sintef, Trondheim (2005). ISBN 978-82-14-03813-2Google Scholar
  99. 99.
    Kaindl, H., Kramer, S., Diallo, P.S.N.: Semiautomatic generation of glossary links: a practical solution. In: HYPERTEXT ’99: Proceedings of the Tenth ACM Conference on Hypertext and Hypermedia: Returning to our Diverse Roots, pp. 3–12. ACM, New York (1999)Google Scholar
  100. 100.
    Kirova V., Kirby N., Kothari D., Childress G.: Effective requirements traceability: models, tools, and practices. Bell Labs Tech. J. 12(4), 143–157 (2008)CrossRefGoogle Scholar
  101. 101.
    Knuth D.E.: Literate programming. Comp. J. 27(2), 97–111 (1984)MATHCrossRefGoogle Scholar
  102. 102.
    Kolovos, D.S., Paige, R.F., Polack, F.A.C.: On-demand merging of traceability links with models. In: ECMDA Traceability Workshop (ECMDA-TW) 2006 Proceedings, pp. 6–14. Sintef, Trondheim (2006). ISBN 978-82-14-04030-2Google Scholar
  103. 103.
    Königs A., Schürr A.: MDI—a rule-based multi-document and tool integration approach. J. Softw. Syst. Model. 5(4), 349–368 (2006)CrossRefGoogle Scholar
  104. 104.
    Kwan, I., Damian, D., Storey, M.A.: Visualizing a requirements-centred social network to maintain awareness within development teams. In: 1st International Workshop on Requirements Engineering Visualization (REV’06). IEEE Computer Society, New York (2006)Google Scholar
  105. 105.
    Lago P., Muccini H., van Vliet H.: A scoped approach to traceability management. J. Syst. Softw. 82(1), 168–182 (2009)CrossRefGoogle Scholar
  106. 106.
    Lago, P., Niemelä, E., van Vliet, H.: Tool support for traceable product evolution. In: CSMR ’04: Proceedings of the 8th Euromicro Working Conference on Software Maintenance and Reengineering, pp. 261–269. IEEE Computer Society, New York (2004)Google Scholar
  107. 107.
    Lee, C., Guadagno, L., Jia, X.: An agile approach to capturing requirements and traceability. In: Proceedings of the 2nd International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE ’03). ACM, New York (2003)Google Scholar
  108. 108.
    Letelier, P.: A framework for requirements traceability in UML-based projects. In: Proceedings of the 1st International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE ’02), pp. 32–41. ACM, New York (2002)Google Scholar
  109. 109.
    Limón, A.E., Garbajosa, J.: The need for a unifying traceability scheme. In: ECMDA Traceability Workshop (ECMDA-TW) 2005 Proceedings, pp. 47–56. Sintef, Trondheim (2005). ISBN 978-82-14-03813-2Google Scholar
  110. 110.
    Lin, J., Lin, C.C., Cleland-Huang, J., Settimi, R., Amaya, J., Bedford, G., Berenbach, B., Khadra, O.B., Duan, C., Zou, X.: Poirot: a distributed tool supporting enterprise-wide traceability. In: 14th IEEE International Requirements Engineering Conference (RE’06) Proceedings, pp. 363–364. IEEE Computer Society, New York (2006)Google Scholar
  111. 111.
    Lindvall, M.: A study of traceability in object-oriented systems development. Ph.D. thesis, Department of Computer and Information Science, Linköping University (1994)Google Scholar
  112. 112.
    Lormans, M., van Deursen, A.: Reconstructing requirements coverage views from design and test using traceability recovery via LSI. In: TEFSE ’05: Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering, pp. 37–42. ACM, New York (2005)Google Scholar
  113. 113.
    Lormans, M., van Deursen, A.: Can LSI help reconstructing requirements traceability in design and test? In: CSMR ’06: Proceedings of the Conference on Software Maintenance and Reengineering, pp. 47–56. IEEE Computer Society, New York (2006)Google Scholar
  114. 114.
    Mäder, P., Gotel, O., Philippow, I.: Rule-based maintenance of post-requirements traceability relations. In: 16th IEEE International Requirements Engineering Conference (RE’08) Proceedings, pp. 23–32. IEEE Computer Society, New York (2008)Google Scholar
  115. 115.
    Mäder, P., Philippow, I., Riebisch, M.: Customizing traceability links for the unified process. In: Overhage, S., Szyperski, C.A., Reussner, R., Stafford, J.A. (eds.) Software Architectures, Components, and Applications (QoSA’07). Lecture Notes in Computer Science, vol. 4880. Springer, Berlin (2008)Google Scholar
  116. 116.
    Maletic, J.I., Collard, M.L., Simoes, B.: An XML based approach to support the evolution of model-to-model traceability links. In: TEFSE ’05: Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering, pp. 67–72. ACM, New York (2005)Google Scholar
  117. 117.
    Marcus A., Maletic J.I., Sergeyev A.: Recovery of traceability links between software documentation and source code. Int. J. Softw. Eng. Knowl. Eng. 15(4), 811–836 (2005)CrossRefGoogle Scholar
  118. 118.
    Marcus, A., Xie, X., Poshyvanyk, D.: When and how to visualize traceability links? In: TEFSE ’05: Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering, pp. 56–61. ACM, New York (2005)Google Scholar
  119. 119.
    Mohan, K., Ramesh, B.: Managing variability with traceability in product and service families. In: Proceedings of the 35th Hawaii International Conference on System Sciences, pp. 76–94. IEEE Computer Society, New York (2002)Google Scholar
  120. 120.
    Mohan K., Ramesh B.: Traceability-based knowledge integration in group decision and negotiation activities. Decis. Support Syst. 43(3), 968–989 (2007)CrossRefGoogle Scholar
  121. 121.
    Mohan K., Xu P., Ramesh B.: Supporting dynamic group decision and negotiation processes: a traceability augmented peer-to-peer network approach. Inf. Manag. 43(5), 650–662 (2006)CrossRefGoogle Scholar
  122. 122.
    Moran, T.P., Carroll, J.M. (eds): Design Rationale: Concepts, Techniques, and Use. Lawrence Erlbaum, Hillsdale (1995) ISBN 978-0-805-81567-2Google Scholar
  123. 123.
    Munson, E.V., Nguyen, T.N.: Concordance, conformance, versions, and traceability. In: TEFSE ’05: Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering, pp. 62–66. ACM, New York (2005)Google Scholar
  124. 124.
    Murta L.G.P., van der Hoek A., Werner C.M.L.: Continuous and automated evolution of architecture-to-implementation traceability links. Autom. Softw. Eng. 15(1), 75–107 (2008)CrossRefGoogle Scholar
  125. 125.
    Natt och Dag J., Gervasi V., Brinkkemper S., Regnell B.: A linguistic-engineering approach to large-scale requirements management. IEEE Softw. 22(1), 32–39 (2005)CrossRefGoogle Scholar
  126. 126.
    Natt och Dag J., Regnell B., Carlshamre P., Andersson M., Karlsson J.: A feasibility study of automated natural language requirements analysis in market-driven development. Requir. Eng. J. 7(1), 20–33 (2002)MATHCrossRefGoogle Scholar
  127. 127.
    Naslavsky, L., Alspaugh, T.A., Richardson, D.J., Ziv, H.: Using scenarios to support traceability. In: TEFSE ’05: Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering, pp. 25–30. ACM, New York (2005)Google Scholar
  128. 128.
    Nentwich C., Emmerich W., Finkelstein A., Ellmer E.: Flexible consistency checking. ACM Trans. Softw. Eng. Meth. 12(1), 28–63 (2003)CrossRefGoogle Scholar
  129. 129.
    Neumuller, C., Grunbacher, P.: Automating software traceability in very small companies: a case study and lessons learne. In: ASE ’06: Proceedings of the 21st IEEE/ACM International Conference on Automated Software Engineering, pp. 145–156. IEEE Computer Society, New York (2006)Google Scholar
  130. 130.
    Nguyen, T.N., Munson, E.V.: The software concordance: a new software document management environment. In: SIGDOC ’03: Proceedings of the 21st Annual International Conference on Documentation, pp. 198–205. ACM, New York (2003)Google Scholar
  131. 131.
    Nguyen, T.N., Thao, C., Munson, E.V.: On product versioning for hypertexts. In: SCM ’05: Proceedings of the 12th International Workshop on Software Configuration Management, pp. 113–132. ACM, New York (2005)Google Scholar
  132. 132.
    Object Management Group: A Proposal for an MDA Foundation Model. Object Management Group, Needham, ormsc/05-04-01 ed. (2005)Google Scholar
  133. 133.
    Object Management Group: The Meta-Object Facility 2.0 Query/View/Transformation Specification. Final Adopted Specifiaction (2005)Google Scholar
  134. 134.
    Object Management Group: The Meta-Object Facility 2.0 Core Specification. Final Adopted Specifiaction (2006)Google Scholar
  135. 135.
    Object Management Group: OMG Systems Modeling Language. Version 1.1 (2008)Google Scholar
  136. 136.
    Oldevik, J., Aagedal, J.: Future Research Topics Discussion. ECMDA Traceability Workshop (ECMDA-TW ’05). http://www.sintef.no/upload/10558/Future-Research-Topics.pdf (2005)
  137. 137.
    Oldevik, J., Neple, T.: Traceability in model to text transformations. In: ECMDA Traceability Workshop (ECMDA-TW) 2006 Proceedings, pp. 64–69. Sintef, Trondheim (2006). ISBN 978-82-14-04030-2Google Scholar
  138. 138.
    Olsen, G.K., Oldevik, J.: Scenarios of traceability in model to text transformations. In: Akehurst, D.H., Vogel, R., Paige, R.F. (eds.) Model Driven Architecture—Foundations and Applications (ECMDA-FA’07). Lecture Notes in Computer Science, vol. 4530, pp. 144–156. Springer, Berlin (2007)Google Scholar
  139. 139.
    Olsson, T., Grundy, J.: Supporting traceability and inconsistency management between software artefacts. In: Proceedings of the 2002 IASTED International Conference on Software Engineering and Applications. ACTA Press, Anaheim (2002). ISBN 978-0-88986-323-1Google Scholar
  140. 140.
    Ozkaya, I.: Representing requirement relationships. In: 1st International Workshop on Requirements Engineering Visualization (REV’06). IEEE Computer Society, New York (2006)Google Scholar
  141. 141.
    Paige, R.F., Olsen, G.K., Kolovos, D.S., Zschaler, S., Power, C.: Building model-driven engineering traceability classifications. In: ECMDA Traceability Workshop (ECMDA-TW) 2008 Proceedings, pp. 49–58. Sintef, Trondheim (2008). ISBN 978-82-14-04396-9Google Scholar
  142. 142.
    Palmer J.D.: Traceabiliy. In: Thayer, R.H., Dorfman, M. (eds) Software Requirements Engineering, 2nd edn, pp. 364–374. IEEE Computer Society Press, Los Alamitos (1997)Google Scholar
  143. 143.
    Pierce, R.A.: A requirements tracing tool. In: Proceedings of the Software Quality Assurance Workshop on Functional and Performance Issues, pp. 53–60. ACM, New York (1978)Google Scholar
  144. 144.
    Pinheiro, F.A.C.: Design of a Hyper-Environment for Tracing Object-Oriented Requirements. Ph.D. thesis, University of Oxford (1996)Google Scholar
  145. 145.
    Pinheiro F.A.C.: Requirements traceability. In: Sampaio do Prado Leite, J.C., Doorn, J.H. (eds) Perspectives on Software Requirements, pp. 93–113. Springer, Berlin (2003)Google Scholar
  146. 146.
    Pinheiro F.A., Goguen J.A.: An object-oriented tool for tracing requirements. IEEE Softw. 13(2), 52–64 (1996)CrossRefGoogle Scholar
  147. 147.
    Pohl, K.: PRO-ART: enabling requirements pre-traceability. In: 2nd International Conference on Requirements Engineering (ICRE’96) Proceedings, pp. 76–84. IEEE Computer Society, New York (1996)Google Scholar
  148. 148.
    Pohl K.: Process-Centered Requirements Engineering. Wiley, New York (1996) ISBN 978-0-863-80193-8Google Scholar
  149. 149.
    Pohl, K., Haumer, P.: HYDRA: a hypertext model for structuring informal requirements representations. In: Requirements Engineering: Foundation for Software Quality (REFSQ’95) Proceedings. http://refsq.org (1995)
  150. 150.
    Potts, C., Bruns, G.: Recording the reasons for design decisions. In: ICSE ’88: Proceedings of the 10th International Conference on Software Engineering, pp. 418–427. IEEE Computer Society, New York (1988)Google Scholar
  151. 151.
    Pressman R.S.: Software Engineering: A Practitioner’s Approach, 6th edn. McGraw-Hill, New York (2004) ISBN 978-0-073-01933-8Google Scholar
  152. 152.
    Ramamoorthy C.V., Garg V., Prakash A.: Support for reus- ability in genesis. IEEE Trans. Softw. Eng. 14(8), 1145–1154 (1988)CrossRefGoogle Scholar
  153. 153.
    Ramesh B.: Factors influencing requirements traceability practice. Commun. ACM 41(12), 37–44 (1998)CrossRefGoogle Scholar
  154. 154.
    Ramesh B., Dhar V.: Supporting systems development by capturing deliberations during requirements engineering. IEEE Trans. Softw. Eng. 18(6), 498–510 (1992)CrossRefGoogle Scholar
  155. 155.
    Ramesh, B., Edwards, M.: Issues in the development of a requirements traceability model. In: Proceedings of the IEEE International Symposium on Requirements Engineering, pp. 256–259. IEEE Computer Society, New York (1993)Google Scholar
  156. 156.
    Ramesh B., Jarke M.: Toward reference models for requirements traceability. IEEE Trans. Softw. Eng. 27(1), 58–93 (2001)CrossRefGoogle Scholar
  157. 157.
    Ramesh, B., Powers, T., Stubbs, C., Edwards, M.: Implementing requirements traceability: a case study. In: 2nd IEEE International Symposium on Requirements Engineering (RE’95) Proceedings, pp. 89–95. IEEE Computer Society, New York (1995)Google Scholar
  158. 158.
    Ramesh B., Stubbs C., Powers T., Edwards M.: Requirements traceability: theory and practice. Ann. Softw. Eng. 3, 397–415 (1997)CrossRefGoogle Scholar
  159. 159.
    Ramsin R., Paige R.F.: Process-centered review of object oriented software development methodologies. ACM Comput. Surv. 40(1), 3:1–3:89 (2008)CrossRefGoogle Scholar
  160. 160.
    Reiss, S.P.: Incremental maintenance of software artifacts. In: 21st IEEE International Conference on Software Maintenance (ICSM’05), pp. 113–122. IEEE Computer Society, New York (2005)Google Scholar
  161. 161.
    Richardson, J., Green, J.: Automating traceability for generated software artifacts. In: Proceedings of the 2nd International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE ’03), pp. 24–33. ACM, New York (2004)Google Scholar
  162. 162.
    Rummler, A., Grammel, B., Pohl, C.: Improving traceability in model-driven development of business applications. In: ECMDA Traceability Workshop (ECMDA-TW) 2007 Proceedings, pp. 7–15. Sintef, Trondheim (2007). ISBN 978-82-14-04056-2Google Scholar
  163. 163.
    Sabetzadeh, M., Easterbrook, S.: Traceability in viewpoint merging: a model management perspective. In: TEFSE ’05: Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering, pp. 44–49. ACM, New York (2005)Google Scholar
  164. 164.
    Sherba, S.A.: Towards automating traceability: an incremental and scalable approach. Ph.D. thesis, University of Colorado at Boulder, USA (2005)Google Scholar
  165. 165.
    Sherba, S.A., Anderson, K.M., Faisal, M.: A framework for mapping traceability relationships. In: Proceedings of the 2nd International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE ’03). ACM, New York (2003)Google Scholar
  166. 166.
    Simpson, J., Weiner, E. (eds): Oxford English Dictionary, vol. 18, 2nd edn. Clarendon Press, Oxford (1989) ISBN 978-0-198-61186-8Google Scholar
  167. 167.
    Sinha V., Sengupta B., Chandra S.: Enabling collaboration in distributed requirements management. IEEE Softw. 23(5), 52–61 (2006)CrossRefGoogle Scholar
  168. 168.
    Smith, M., Weiss, D., Wilcox, P., Dewar, R.: The OPHELIA traceability layer. In: 2nd Workshop on Cooperative Supports for Distributed Software Engineering Processes (CSSE 2003), pp. 150–161. FrancoAngeli, Benevento (2003)Google Scholar
  169. 169.
    Sousa, A., Kulesza, U., Rummler, A., Anquetil, N., Moreira, R.M.A., Amaral, V., Araújo, J.A.: A model-driven traceability framework to software product line development. In: ECMDA Traceability Workshop (ECMDA-TW) 2008 Proceedings, pp. 97–109. Sintef, Trondheim (2008). ISBN 978-82-14-04396-9Google Scholar
  170. 170.
    Spanoudakis, G., d’Avila Garcez, A.S., Zisman, A.: Revising rules to capture requirements traceability relations: a machine learning approach. In: 15th International Conference in Software Engineering and Knowledge Engineering (SEKE 2003) Proceedings, pp. 570–577. Knowledge Systems Institute, Skokie (2003). ISBN 978-1-891706-12-7Google Scholar
  171. 171.
    Spanoudakis G., Zisman A.: Software traceability: a roadmap. In: Chang, S.K. (eds) Handbook of Software Engineering and Knowledge Engineering, vol. 3—Recent Advances, pp. 395–428. World Scientific, Singapore (2005) ISBN 978-9-8125-6273-9CrossRefGoogle Scholar
  172. 172.
    Spanoudakis G., Zisman A., Pérez-Miñana E., Krause P.: Rule-based generation of requirements traceability relations. J. Syst. Softw. 72(2), 105–127 (2004)CrossRefGoogle Scholar
  173. 173.
    Stirewalt, R.E.K., Deng, M., Cheng, B.H.C.: UML formalization is a traceability problem. In: TEFSE ’05: Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering, pp. 31–36. ACM, New York (2005)Google Scholar
  174. 174.
    Stone, A., Sawyer, P.: Finding tacit knowledge by solving the pre-requirements tracing problem. In: Requirements Engineering: Foundation for Software Quality (REFSQ’05) Proceedings. http://refsq.org (2005)
  175. 175.
    Stone A., Sawyer P.: Identifying tacit knowledge-based requirements. IEE Proc. Softw. 153(6), 211–218 (2006)CrossRefGoogle Scholar
  176. 176.
    Strašunskas, D.: Traceability in collaborative systems development from lifecycle perspective. In: Proceedings of the 1st International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE ’02). ACM, New York (2002)Google Scholar
  177. 177.
    Strašunskas, D.: Domain model-centric distributed development: an approach to semantics-based change impact management. Ph.D. thesis, Norwegian University of Science and Technology (NTNU), Norway (2006)Google Scholar
  178. 178.
    Strašunskas D., Hakkarainen S.: Domain model driven approach to change impact assessment. In: Linger, H., Fisher, J., Wojtkowski, W.G., Wojtkowski, W., Zupančič, J., Vigo, K., Arnold, J. (eds) Constructing the Infrastructure for the Knowledge Economy: Methods and Tools, Theory and Practice, pp. 305–316. Springer, Berlin (2004) ISBN 978-0-306-48554-1Google Scholar
  179. 179.
    Tilbury, A.J.M.: Enabling software traceability. In: IEE Colloquium on the Application of Computer Aided Software Engineering Tools, pp. 7/1–7/4. IEEE, London (1989)Google Scholar
  180. 180.
    Trainer, E., Quirk, S., de Souza, C., Redmiles, D.: Bridging the gap between technical and social dependencies with Ariadne. In: Eclipse Technology Exchange (eTX) Workshop. ACM, New York (2005)Google Scholar
  181. 181.
    van den Berg, K., Conejero, J.M., Hernández, J.: Analysis of crosscutting across software development phases based on traceability. In: EA ’06: Proceedings of the 2006 International Workshop on Early Aspects at ICSE, pp. 43–50. IEEE Computer Society, New York (2006)Google Scholar
  182. 182.
    van Gorp, P., Altheide, F., Janssens, D.: Towards 2D traceability in a platform for contract aware visual transformations with tolerated inconsistencies. In: Enterprise Distributed Object Computing Conference, IEEE International, pp. 185–198. IEEE Computer Society, New York (2006)Google Scholar
  183. 183.
    van Gorp P., Janssens D.: CAViT: a consistency maintenance framework based on transformation contracts. In: Cordy, J.R., Lämmel, R., Winter, A. (eds) Transformation Techniques in Software Engineering, no. 05161 in Dagstuhl Seminar Proceedings, LZI, Wadern (2006) ISSN 1862-4405Google Scholar
  184. 184.
    van Lamsweerde, A.: Formal specification: a roadmap. In: Proceedings of the Conference on The Future of Software Engineering (at ICSE ’00), pp. 147–159. IEEE Computer Society, New York (2000)Google Scholar
  185. 185.
    van Lamsweerde, A.: Goal-oriented requirements engineering: a guided tour. In: 5th IEEE International Symposium on Requirements Engineering (RE ’01) Proceedings. IEEE Computer Society, New York (2001)Google Scholar
  186. 186.
    von Pilgrim, J.: Mental map and model driven development. In: Fish, A., Knapp, A., Störrle, H. (eds.) Proceedings of the Workshop on the Layout of (Software) Engineering Diagrams (LED 2007), Electronic Communications of the EASST, vol. 7, pp. 17–32 (2007). ISSN 1863-2122Google Scholar
  187. 187.
    von Pilgrim, J., Vanhooff, B., Schulz-Gerlach, I., Berbers, Y.: Constructing and visualizing transformation chains. In: Model Driven Architecture—Foundations and Applications (ECMDA-FA’08). Lecture Notes in Computer Science, vol. 5095, pp. 17–32. Springer, Berlin (2008). ISBN 978-3-540-69095-5Google Scholar
  188. 188.
    van der Straeten, R., Mens, T., Simmonds, J., Jonckers, V.: Using description logic to maintain consistency between UML models. In: UML 2003: The Unified Modeling Language Proceedings. Lecture Notes in Computer Science, vol. 2863, pp. 326–340. Springer, Berlin (2003)Google Scholar
  189. 189.
    Vanhooff, B., Ayed, D., Van Baelen, S., Joosen, W., Berbers, Y.: UniTI: a unified transformation infrastructure. In: Engels, G., Opdyke, B., Schmidt, D.C., Weil, F. (eds.) Model Driven Engineering Languages and Systems, Proceedings of the 10th International Conference (MoDELS 2007). Lecture Notes in Computer Science, vol. 4735, pp. 31–45. Springer, Berlin (2007). ISBN 978-3-540-75208-0Google Scholar
  190. 190.
    Vanhooff, B., Baelen, S.V., Joosen, W., Berbers, Y.: Traceability as input for model transformations. In: ECMDA Traceability Workshop (ECMDA-TW) 2007 Proceedings, pp. 37–46. Sintef, Trondheim (2007). ISBN 978-82-14-04056-2Google Scholar
  191. 191.
    von Knethen, A.: Change-Oriented Requirements Engineering. Support for Evolution of Embedded Systems. Ph.D. thesis, Universität Kaiserslautern, Germany (2001)Google Scholar
  192. 192.
    von Knethen, A., Grund, M.: QuaTrace: a tool environment for (semi-) automatic impact analysis based on traces. In: Proceedings of the IEEE International Conference on Software Maintenance (ICSM 2003), pp. 246–255. IEEE Computer Society, New York (2003)Google Scholar
  193. 193.
    von Knethen, A., Paech, B.: A survey on tracing approaches in practice and research. Research Report 095.01/E, Fraunhofer IESE, Kaiserslautern, Germany (2002)Google Scholar
  194. 194.
    Walderhaug, S., Johansen, U., Stav, E., Aagedal, J.: Towards a generic solution for traceability in MDD. In: ECMDA Traceability Workshop (ECMDA-TW) 2006 Proceedings, pp. 41–50. Sintef, Trondheim (2006). ISBN 978-82-14-04030-2Google Scholar
  195. 195.
    Walderhaug S., Stav E., Johansen U., Olsen G.K.: Traceability in model-driven software development. In: Tiako, P.F. (eds) Designing Software-Intensive Systems: Methods and Principles, pp. 133–159. Idea Group Publishing, Hershey (2008) ISBN: 978-1599046990Google Scholar
  196. 196.
    Watkins R., Neal M.: Why and how of requirements tracing. IEEE Softw. 11(4), 104–106 (1994)CrossRefGoogle Scholar
  197. 197.
    Wenzel, S., Hutter, H., Kelter, U.: Tracing model elements. In: 23rd International Conference on Software Maintenance (ISCM’07), pp. 104–113. IEEE Computer Society, New York (2007)Google Scholar
  198. 198.
    Whittle, J., Baalen, J.V., Schumann, J., Robinson, P., Pressburger, T., Penix, J., Oh, P., Lowry, M., Brat, G.: Amphion/NAV: deductive synthesis of state estimation software. In: ASE ’01: Proceedings of the 16th IEEE International Conference on Automated Software Engineering, pp. 395–399. IEEE Computer Society, New York (2001)Google Scholar
  199. 199.
    Wiegers K.E.: Software Requirements, 2nd end. Microsoft Press, Redmond (2003) ISBN 978-0-735-61879-4Google Scholar
  200. 200.
    Wieringa, R.: An introduction to requirements traceability. Tech. rep., Institute for Mathematics and Computer Science, Vrije Universiteit, Amsterdam, The Netherlands (1995)Google Scholar
  201. 201.
    Winkler, S.: On usability in requirements trace. Visualizations. In: 3rd International Workshop on Requirements Engineering Visualization (REV’08). IEEE Computer Society, New York (2008)Google Scholar
  202. 202.
    Zou, X., Settimi, R., Cleland-Huang, J.: Phrasing in dynamic requirements trace retrieval. In: 30th Annual International Computer Software and Applications Conference (COMPSAC’06), pp. 265–272. IEEE Computer Society, New York (2006)Google Scholar

Copyright information

© Springer-Verlag 2009

Authors and Affiliations

  1. 1.FernUniversität in HagenHagenGermany

Personalised recommendations