Traceability Types for Mastering Change in Collaborative Software Quality Management

Software is constantly evolving and to successfully comprehend and manage this evolutionary change is a challenging task which requires traceability support. In this paper we propose a novel approach to traceability as a cornerstone for successful impact analysis and change management, in the context of collaborative software quality management. We first motivate the crucial role of traceability within lifecycle management of the new generation of distributed fragmented software services. Based on the model-based collaborative software quality management framework of Living Models, we then categorize software quality management services and identify novel types of traceability. This is followed by an overview and classification of sample software quality management services from literature, enabled by the interrelation with the identified types of traceability. From this classification we derive the need for further research on traceability in collaborative software quality management.

[1]  Ruth Breu,et al.  Integrating Manual and Automatic Risk Assessment for Risk-Based Testing , 2012, SWQD.

[2]  Ruth Breu,et al.  Automation Processes for Enterprise Architecture Management , 2011, 2011 IEEE 15th International Enterprise Distributed Object Computing Conference Workshops.

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

[4]  Balasubramaniam Ramesh,et al.  Implementing requirements traceability: a case study , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[5]  Tiziana Margaria,et al.  Service Engineering: Linking Business and IT , 2006, 2006 30th Annual IEEE/NASA Software Engineering Workshop.

[6]  Peng Xu,et al.  Supporting Workflow Management Systems with traceability , 2002, Proceedings of the 35th Annual Hawaii International Conference on System Sciences.

[7]  Jonathan I. Maletic,et al.  An XML based approach to support the evolution of model-to-model traceability links , 2005, TEFSE '05.

[8]  Amrit Tiwana,et al.  Supporting Collaborative Process Knowledge Management in New Product Development Teams , 1999, Decis. Support Syst..

[9]  Olly Gotel,et al.  Contribution structures [Requirements artifacts] , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[10]  Ruth Breu,et al.  On Enterprise Architecture Change Events , 2012, TEAR/PRET.

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

[12]  Jon Oldevik,et al.  Scenarios of Traceability in Model to Text Transformations , 2007, ECMDA-FA.

[13]  David W. Binkley,et al.  Source Code Analysis: A Road Map , 2007, Future of Software Engineering (FOSE '07).

[14]  Balasubramaniam Ramesh,et al.  Representing and reasoning with traceability in model life cycle management , 1997, Ann. Oper. Res..

[15]  C.J.H. Mann,et al.  Object-Oriented Metrics in Practice: Using Software Metrics to Characterize, Evaluate, and Improve the Design of Object-Oriented Systems , 2007 .

[16]  Eun Man Choi,et al.  Rigorous Vertical Software System Testing In IDE , 2007, 5th ACIS International Conference on Software Engineering Research, Management & Applications (SERA 2007).

[17]  Bernhard Steffen,et al.  Risk-based testing via active continuous quality control , 2014, International Journal on Software Tools for Technology Transfer.

[18]  Jens von Pilgrim,et al.  A survey of traceability in requirements engineering and model-driven development , 2010, Software & Systems Modeling.

[19]  Florian Matthes,et al.  Automating Enterprise Architecture Documentation using an Enterprise Service Bus , 2012, AMCIS.

[20]  Ruth Breu,et al.  A Meta-Model for Automated Enterprise Architecture Model Maintenance , 2012, 2012 IEEE 16th International Enterprise Distributed Object Computing Conference.

[21]  Ruth Breu,et al.  Living Models - Ten Principles for Change-Driven Software Engineering , 2011, Int. J. Softw. Informatics.

[22]  Osamu Mizuno,et al.  Bug prediction based on fine-grained module histories , 2012, 2012 34th International Conference on Software Engineering (ICSE).

[23]  Tiziana Margaria,et al.  Continuous Model-Driven Engineering , 2009, Computer.

[24]  Alexander Egyed,et al.  Instant consistency checking for the UML , 2006, ICSE.

[25]  Ruth Breu,et al.  Managing legal compliance through security requirements across service provider chains: A case study on the German Federal Data Protection Act , 2012, GI-Jahrestagung.

[26]  Juan Trujillo,et al.  A Trace Metamodel Proposal Based on the Model Driven Architecture Framework for the Traceability of User Requirements in Data Warehouses , 2011, CAiSE.

[27]  Klaus Pohl,et al.  An automated technique for risk-based test case generation and prioritization , 2008, AST '08.

[28]  George Spanoudakis,et al.  Software Traceability : A Roadmap , 2005 .

[29]  Harry M. Sneed.  Testing Web Services in the Cloud , 2013, SWQD.

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

[31]  Markus Buschle,et al.  Automatic data collection for enterprise architecture models , 2012, Software & Systems Modeling.

[32]  José Ambrosio Toval Álvarez,et al.  A systematic review of UML model consistency management , 2009, Inf. Softw. Technol..

[33]  Tiziana Margaria,et al.  Business Process Modeling in the jABC , 2009, Handbook of Research on Business Process Modeling.

[34]  Andreas Zeller,et al.  Mining version histories to guide software changes , 2005, Proceedings. 26th International Conference on Software Engineering.

[35]  Ruth Breu,et al.  Evolution of Security Requirements Tests for Service-Centric Systems , 2011, ESSoS.

[36]  Yang Li,et al.  Which Traceability Visualization Is Suitable in This Context? A Comparative Study , 2012, REFSQ.

[37]  Ruth Breu,et al.  Model Validation in a Tool-Based Methodology for System Testing of Service-Oriented Systems , 2011 .

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

[39]  Arda Goknil,et al.  Survey of Traceability Approaches in Model-Driven Engineering , 2007, 11th IEEE International Enterprise Distributed Object Computing Conference (EDOC 2007).

[40]  Ivan Kurtev,et al.  Semantics of trace relations in requirements models for consistency checking and inferencing , 2011, Software & Systems Modeling.

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

[42]  Denys Poshyvanyk,et al.  When and how to visualize traceability links? , 2005, TEFSE '05.

[43]  Richard F. Paige,et al.  Building Model-Driven Engineering Traceability Classifications , 2008 .

[44]  Ruth Breu,et al.  Towards a Model- and Learning-Based Framework for Security Anomaly Detection , 2011, FMCO.

[45]  Kannan Mohan,et al.  Managing variability with traceability in product and service families , 2002, Proceedings of the 35th Annual Hawaii International Conference on System Sciences.

[46]  Tiziana Margaria,et al.  Model-Driven Development with the jABC , 2006, Haifa Verification Conference.

[47]  Ruth Breu,et al.  Model-Driven Security Engineering of Service Oriented Systems , 2008, UNISCON.

[48]  Ruth Breu,et al.  A Tool-Based Methodology for System Testing of Service-Oriented Systems , 2010, 2010 Second International Conference on Advances in System Testing and Validation Lifecycle.

[49]  Darijus Strasunskas,et al.  Domain model-driven software engineering: A method for discovery of dependency links , 2012, Inf. Softw. Technol..