Traceability in the Co-evolution of Architectural Requirements and Design

Requirements and architectural design specifications can be conflicting and inconsistent, especially during the design period when requirements and architectural design are co-evolving. One reason is that stakeholders do not have up-to-date knowledge of each other’s work to fully understand potential conflicts and inconsistencies. Specifications are often documented in a natural language, which also makes it difficult for tracing related information automatically. In this chapter, we introduce a general-purpose ontology that we have developed to address this problem. We demonstrate an implementation of semantic wiki that supports traceability of co-evolving requirements specifications and architecture design.

[1]  Andrea Zisman,et al.  Rule-based generation of requirements traceability relations , 2004, J. Syst. Softw..

[2]  Felix Bachmann,et al.  Experience Using the Web-Based Tool Wiki for Architecture Documentation , 2005 .

[3]  Axel Korthaus,et al.  New Applications for Wikis in Software Engineering , 2008, PRIMIUM.

[4]  Carl K. Chang,et al.  Event-Based Traceability for Managing Evolutionary Change , 2003, IEEE Trans. Software Eng..

[5]  Dan Brickley,et al.  Resource Description Framework (RDF) Model and Syntax Specification , 2002 .

[6]  Peng Liang,et al.  Requirements Reasoning for Distributed Requirements Analysis Using Semantic Wiki , 2009, 2009 Fourth IEEE International Conference on Global Software Engineering.

[7]  Jane Huffman Hayes,et al.  Advancing candidate link generation for requirements tracing: the study of methods , 2006, IEEE Transactions on Software Engineering.

[8]  Jane Huffman Hayes,et al.  Improving requirements tracing via information retrieval , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[9]  Philippe Kruchten,et al.  An Ontology of Architectural Design Decisions in Software-Intensive Systems , 2004 .

[10]  Patricia Lago,et al.  A Just-In-Time Architectural Knowledge Sharing Portal , 2008, Seventh Working IEEE/IFIP Conference on Software Architecture (WICSA 2008).

[11]  Peng Liang,et al.  A Survey of Semantic Wikis for Requirements Engineering , 2009 .

[12]  Suzanne Robertson,et al.  Mastering the Requirements Process , 1999 .

[13]  Klaus Pohl,et al.  Adapting traceability environments to project-specific needs , 1998, CACM.

[14]  Ademar Aguiar,et al.  WikiWiki weaving heterogeneous software artifacts , 2005, Int. Sym. Wikis.

[15]  Deborah L. McGuinness,et al.  OWL Web ontology language overview , 2004 .

[16]  Matthias Jarke,et al.  Toward Reference Models of Requirements Traceability , 2001, IEEE Trans. Software Eng..

[17]  Nigel Shadbolt,et al.  Resource Description Framework (RDF) , 2009 .

[18]  John Grundy,et al.  Collaborative Software Engineering , 2010 .

[19]  E. Prud hommeaux,et al.  SPARQL query language for RDF , 2011 .

[20]  Paris Avgeriou,et al.  The GRIFFIN Collaborative Virtual Community for Architectural Knowledge Management , 2010, Collaborative Software Engineering.

[21]  Paul Clements,et al.  Software Architecture in Practice: Addison-Wesley , 1998 .

[22]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[23]  Morten T. Hansen,et al.  What's your strategy for managing knowledge? , 1999, Harvard business review.

[24]  N. F. Noy,et al.  Ontology Development 101: A Guide to Creating Your First Ontology , 2001 .

[25]  Henry Muccini,et al.  A scoped approach to traceability management , 2009, J. Syst. Softw..

[26]  Antony Tang,et al.  A rationale-based architecture model for design traceability and reasoning , 2007, J. Syst. Softw..

[27]  Alexander Egyed,et al.  Supporting Software Understanding with Automated Requirements Traceability , 2005, Int. J. Softw. Eng. Knowl. Eng..

[28]  Kuntz Werner,et al.  Issues as Elements of Information Systems , 1970 .

[29]  Steffen Lohmann,et al.  Mapping Cognitive Models to Social Semantic Spaces - Collaborative Development of Project Ontologies , 2007, CSSW.

[30]  François Bry,et al.  Semantic Wikis , 2008, IEEE Software.

[31]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[32]  Muhammad Ali Babar,et al.  Architectural Knowlege Management Strategies: Approaches in Research and Industry , 2007, Second Workshop on Sharing and Reusing Architectural Knowledge - Architecture, Rationale, and Design Intent (SHARK/ADI'07: ICSE Workshops 2007).

[33]  Thanwadee Sunetnanta,et al.  MUPRET: An Ontology-Driven Traceability Tool for Multiperspective Requirements Artifacts , 2009, 2009 Eighth IEEE/ACIS International Conference on Computer and Information Science.

[34]  Markus Krötzsch,et al.  Semantic MediaWiki , 2006, International Semantic Web Conference.

[35]  M. Lindvall,et al.  Knowledge management in software engineering , 2002, IEEE Software.

[36]  Panagiotis Louridas,et al.  Using wikis in software development , 2006, IEEE Software.

[37]  HanJun,et al.  A rationale-based architecture model for design traceability and reasoning , 2007 .