1 / 12

Artifact Traceability using XML

Chris Baker. Artifact Traceability using XML. Agenda. Traceability Problem Proposed Solution Benefits Evolutionary Possibilities Questions. Traceability. Meriam -Webster definition: “to discover by going backward over the evidence step by step” Generally applies to requirements.

wattan
Download Presentation

Artifact Traceability using XML

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chris Baker Artifact Traceability using XML

  2. Agenda • Traceability • Problem • Proposed Solution • Benefits • Evolutionary Possibilities • Questions Chris Baker

  3. Traceability • Meriam-Webster definition: • “to discover by going backward over the evidence step by step” • Generally applies to requirements Chris Baker

  4. Problem • Implicit artifact dependencies • Potential for miscommunication • Ripple effect of small changes • Review cost to verify consistency Chris Baker

  5. Problem - OCD Example Chris Baker

  6. Proposed Solution • Artifact Represented in XML • “Mirror” of Table of Contents/Figures/etc - Artifact Traceability Using XML Chris Baker

  7. Why XML? • Well known standard representing data • Large tool support and community • Human readable format • Versions may be compared Chris Baker

  8. Mechanisms • ICM artifact/XML templates provided • Project tailors XML files to fit artifacts • Ideally through a GUI • Change communication among team Chris Baker

  9. Benefits • Artifact authors better see change impacts • Reviewer can better focus time • Better package consistency • Students better visualize the ICM • Aids in research Chris Baker

  10. Evolutionary Possibilities • Embed artifact links with XLink (or similar) • Not just for documents • Tags within source code • XML representation of UML model • Dynamic generation from an artifact • Graphical representation of dependencies • Generated UML diagram or hierarchy Chris Baker

  11. References • Maletic, J. I., Collard, M. L., and Simoes, B. 2005. An XML based approach to support the evolution of model-to-model traceability links. In Proceedings of the 3rd international Workshop on Traceability in Emerging Forms of Software Engineering (Long Beach, California, November 08 - 08, 2005). TEFSE '05. ACM, New York, NY, 67-72. • Rönnau, S., Scheffczyk, J., and Borghoff, U. M. 2005. Towards XML version control of office documents. In Proceedings of the 2005 ACM Symposium on Document Engineering (Bristol, United Kingdom, November 02 - 04, 2005). DocEng '05. ACM, New York, NY, 10-19. • Meriam-Webster’s Online Dictionary, http://www.merriam-webster.com/dictionary/traceability, April 21, 2010 • University of Southern California, Center for Software and Systems Engineering. Incremental Commitment Model - Software: Electronic Process Guide. 2010. 21April 2010 <http://greenbay.usc.edu/IICMSw/index.htm>. • University of Southern California, Center for Software and Systems Engineering Redevelopment Commitment Review Package Evaluation. 08 March 2010. 30 March 2010 <http://greenbay.usc.edu/csci577/spring2010/site/assignments/IIVV/Evaluation_of_RDCP.rar>. • DeRose, S., Maler, E., and Orchard, D. XML Linking Language (XLink) Version 1.0, W3C Recommendation 27 June2001. 18 April 2010 http://www.w3.org/TR/xlink/ Chris Baker

  12. Questions? Chris Baker

More Related