IBM®
Skip to main content
    Country/region [change]    Terms of use
 
 
 
    Home    Products    Services & solutions    Support & downloads    My account    

IBM Systems Journal
Model-Driven Software Development   Volume 45, Number 3, 2006
Table of contents: HTMLPDF This article: HTMLPDF   Copyright info

Model traceability - References

 by N. Aizenbud-Reshef,
B. T. Nolan,
J. Rubin,
and Y. Shaham-Gafni
Cited references

  1. IEEE Std 610.12-1990, “IEEE Standard Glossary of Software Engineering Terminology,” © IEEE, New York (September 1990).
  2. O. C. Z. Gotel and A. C. W. Finkelstein, “An Analysis of the Requirements Traceability Problem,” Proceedings of the First International Conference on Requirements Engineering, Utrecht, The Netherlands (1994), pp. 94–101.
  3. Capability Maturity Model Integration (CMMI), http://www.sei.cmu.edu/cmmi/.
  4. G. Stehle, “Requirements Traceability for Real-Time Systems,” Proceedings of EuroCASE II, London, England (April 1990), pp. 1–27.
  5. M. Edwards and S. Howell, A Methodology for System Requirements Specification and Traceability for Large Real-Time Complex Systems, Technical Report, U.S. Naval Surface Warfare Center Daahlgren Division, Dahlgren, VA 22448 (1991).
  6. P. Arkley, P. Mason, and S. Riddle, “Position Paper: Enabling Traceability,” Proceedings of the 1st International Workshop on Traceability in Emerging Forms of Software Engineering, Edinburgh, Scotland (September 2002), pp. 61–65.
  7. A. M. Davis, Software Requirements: Analysis and Specification, Prentice-Hall, Upper Saddle River, NJ (1990).
  8. M. West, “Quality Function Deployment in Software Development,” IEE Colloquium on Tools and Techniques for Maintaining Traceability During Design 180, 5/5–5/7 (December 2, 1991).
  9. J. Jackson, “A Keyphrase Based Traceability Scheme,” IEE Colloquium on Tools and Techniques for Maintaining Traceability During Design 180, 2/1–2/4 (December 2, 1991).
  10. I. Alexander, “Toward Automatic Traceability in Industrial Practice,” Proceedings of the 1st International Workshop on Traceability in Emerging Forms of Software Engineering, Edinburgh, Scotland (September 2002), pp. 26–31.
  11. F. A. C. Pinheiro and J. A. Goguen, “An Object-Oriented Tool for Tracing Requirements,” IEEE Software 13, No. 2, 52–64 (1996).
  12. J. Cooke and R. Stone, “A Formal Development Framework and Its Use to Manage Software Production,” IEE Colloquium on Tools and Techniques for Maintaining Traceability During Design 180, 10/1 (December 2, 1991).
  13. E. Tryggeseth and O. Nytrø, “Dynamic Traceability Links Supported by a System Architecture Description,” Proceedings of the IEEE International Conference on Software Maintenance, Bari, Italy (1997), pp. 180–187.
  14. Rational RequisitePro, IBM Corporation, http://www-306.ibm.com/software/awdtools/reqpro/.
  15. DOORS, Telelogic, http://www.telelogic.com/products/doorsers/index.cfm.
  16. B. Ramesh and M. Jarke, “Toward Reference Models for Requirements Traceability,” IEEE Transactions on Software Engineering 27, No. 1, 58–93 (January 2001).
  17. J. Dick, “Rich Traceability,” Proceedings of the 1st International Workshop on Traceability in Emerging Forms of Software Engineering, Edinburgh, Scotland (September 2002), http://www.soi.city.ac.uk/~zisman/WSTPapers/Dick.pdf.
  18. P. Letelier, “A Framework for Requirements Traceability in UML-Based Projects,” Proceedings of the 1st International Workshop on Traceability in Emerging Forms of Software Engineering, Edinburgh, Scotland (September 2002), pp. 30–41.
  19. VeroTrace, Verocel Inc., http://www.verocel.com/verotrace.htm.
  20. European Computer Manufacturers Association (ECMA), Reference Model for Frameworks of Software Engineering Environments, ECMA TR/55, Third Edition, (June 1993), http://www.ecma-international.org/publications/files/ECMA-TR/TR-055.pdf.
  21. P. A. Wilcox, M. J. Smith, A. D. Smith, R. J. Pooley, L. M. MacKinnon, and R. G. Dewar, “OPHELIA: An Architecture to Facilitate Software Engineering in a Distributed Environment,” Proceedings of the 15th International Conference on Software and Systems Engineering and Their Applications, Paris, France (2002), Volume 2, pp. 1/7–7/7.
  22. S. A. Sherba, K. M. Anderson, and M. Faisal, “A Framework for Mapping Traceability Relationships,” Proceedings of the 2nd International Workshop on Traceability in Emerging Forms of Software Engineering, Montreal, Canada (September 2003), http://www.soi.city.ac.uk/~gespan/paper5.pdf.
  23. J. Huffman Hayes, A. Dekhtyar, and J. Osbourne, “Improving Requirements Tracing via Information Retrieval,” Proceedings of the 11th IEEE International Requirements Engineering Conference, Monterey Bay, CA (2003), p. 138–150.
  24. G. Antoniol, G. Canfora, G. Casazza, A. De Lucia, and E. Merlo, “Recovering Traceability Links between Code and Documentation,” IEEE Transactions on Software Engineering 28, No. 10, 970–983 (October 2002).
  25. A. Marcus and J. I. Maletic, “Recovering Documentation-to-Source-Code Traceability Links Using Latent Semantic Indexing,” Proceedings of the 25th IEEE/ACM International Conference on Software Engineering, Portland, OR (May 2003), pp. 125–136.
  26. A. Egyed and P. Grünbacher, “Automating Requirements Traceability: Beyond the Record & Replay Paradigm,” Proceedings of the 17th IEEE International Conference on Automated Software Engineering, Edinburgh, Scotland (September 2002), pp. 163–171.
  27. A. T. T. Ying, G. C. Murphy, R. Ng, and M. C. Chu-Carroll, “Predicting Source Code Changes by Mining Change History,” IEEE Transactions on Software Engineering 30, No. 9, 574–586 (September 2004).
  28. T. Zimmermann, P. Weißgerber, S. Diehl, and A. Zeller, “Mining Version Histories to Guide Software Changes,” Proceedings of the 26th International Conference on Software Engineering, Edinburgh, Scotland (2004) pp. 563–572.
  29. K. Czarnecki and S. Helsen, “Feature-based Survey of Model Transformation Approaches,” IBM Systems Journal 45, No. 3, 621–646 (2006, this issue).
  30. J. Huang-Cleland, C. K. Chang, and M. Christensen, “Event-Based Traceability for Managing Evolutionary Change,” IEEE Transactions in Software Engineering 29, No. 9, 796–810 (September 2003).
  31. T. Olsson and J. Grundy, “Supporting Traceability and Inconsistency Management Between Software Artifacts,” Proceedings of the IASTED International Conference on Software Engineering and Applications, Boston, MA (November 2002), http://serg.telecom.lth.se/research/publications/docs/99_sea_information_tool.pdf.
  32. R. Freude and A. Königs, “Tool Integration with Consistency Relations and Their Visualization,” ESEC/FSE Workshop on Tool Integration in System Development, Helsinki, Finland (September 2003), pp. 6–10.
  33. R. Watson, Smarter Requirements Management with Intelligent Traceability, White Paper, Telelogic North America Inc., Irvine, CA (July 2003).
  34. P. Kruchten, The Rational Unified Process—An Introduction, Second Edition, Addison-Wesley-Longman, Reading, MA (2000).
  35. I. Jacobson, M. Christerson, P. Jonsson, and G. Overgaard, Object-Oriented Software Engineering: A Use-Case Driven Approach, Addison-Wesley, Boston, MA (1992).
  36. M. Cantor, “Rational Unified Process for Systems Engineering,” The Rational Edge (August 2003), http://www-128.ibm.com/developerworks/rational/library/content/RationalEdge/aug03/f_rupse_mc.pdf.
  37. R. Paige and Y. Shaham-Gafni, Model Composition: Development of Consistency Rules, Modelware Report D1.5 (September 2005), http://www.modelware-ist.org/index.php?option=com_remository&Itemid=79&func=fileinfo&id=11.
  38. J. Grundy, J. Hosking, and W. B. Mugridge, “Inconsistency Management for Multiple-View Software Development Environments,” IEEE Transactions on Software Engineering 24, No. 11, 960–981 (November 1998).
  39. P. Desfray, MDA—When a Major Software Industry Trend Meets Our Toolset, Implemented Since 1994, White Paper, Softeam (2001), http://www.omg.org/mda/mda_files/MDA-Softeam-WhitePaper.pdf.
  40. N. Aizenbud-Reshef, R. F. Paige, J. Rubin, Y. Shaham-Gafni, and D. S. Kolovos, “Operational Semantics for Traceability,” ECMDA Traceability Workshop, Nuremberg, Germany (November 2005), pp. 7–14.
  41. MDA Guide Version 1.0.1, OMG Document omg/2003-06-01, Object Management Group, Inc. (June 2003).
  42. MOF 2.0 Query/Views/Transformations RFP, OMG Document ad/2002-04-10, Object Management Group, Inc. (revised on April 24, 2002).
  43. MOF Model to Text Transformation Language RFP, OMG Document ad/2004-04-07, Object Management Group, Inc. (revised on May 27, 2004).
  44. J. Bézivin, B. Rumpe, A. Schürr, and L. Tratt, “Model Transformations in Practice,” ACM/IEEE 8th International Conference on Model Driven Engineering Languages and Systems, Montego Bay, Jamaica (October 2005), http://sosym.dcs.kcl.ac.uk/events/mtip05/long_cfp.pdf.
  45. F. Jouault, “Loosely Coupled Traceability for ATL,” Proceedings of the European Conference on Model Driven Architecture Workshop on Traceability, Nuremberg, Germany (November 2005), http://www.sciences.univ-nantes.fr/lina/atl/www/papers/ECMDATraceability05.pdf.
  46. Revised Submission for MOF 2.0 Query/View/Transformations RFP(ad/2002-04-10), QVT-Merge Group, Version 2.1, OMG Document ad/05-07-01, Object Management Group, Inc. (August 2005).


    About IBM    Privacy    Contact