Improving reviews of conceptual models by extended traceability to captured system usage

Abstract When specifying change for an existing system, the history and functionality of the system to be replaced has to be considered. This avoids neglecting important system functionality and repeating errors. The properties and the rationale behind the existing system can be elicited by analysing concrete system-usage scenarios [Pohl, K., Weidenhaupt, K., Domges, R., Haumer, P., Jarke, M., Klamma, R., 1999. Process-integrated (modelling) environments (PRIME): foundation and implementation framework. ACM Transactions on Software Engineering and Methodology (TOSEM), vol. 8, no. 4, pp. 343–410]. The results of the analysis of the existing system are then typically represented using conceptual models. To establish conceptual models of high quality reviewing the models is common practice. The problem faced with when reviewing conceptual models, is that the reviewer cannot assess and therefore understand the basis (concrete system usage) on which the conceptual models were built. In this paper, we present an approach to overcome this problem. We establish Extended Traceability, by recording concrete system-usage scenarios using rich media (e.g. video, speech, graphic) and interrelating the recorded observations with the conceptual models. We discuss the main improvements for review processes and illustrate the advantages with excerpts from a case study performed in a mechanical engineering company.

[1]  Karen Holtzblatt,et al.  Contextual design , 1997, INTR.

[2]  John Mylopoulos,et al.  Why Goal-Oriented Requirements Engineering , 1998, Requirements Engineering: Foundation for Software Quality.

[3]  Tom Rodden,et al.  Presenting ethnography in the requirements process , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[4]  Morten Kyng,et al.  Design at Work , 1992 .

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

[6]  Mark Weiser,et al.  Project Memory: Information Management for Project Teams , 1998, J. Manag. Inf. Syst..

[7]  Klaus Pohl,et al.  Interrelating Goal Models and Multimedia Scenes: An Empirical Investigation , 1999 .

[8]  Klaus Pohl,et al.  PRO-ART: enabling requirements pre-traceability , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[9]  Klaus Pohl,et al.  Process-Centered Requirements Engineering , 1996 .

[10]  Eric S. K. Yu,et al.  Towards modelling and reasoning support for early-phase requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[11]  Douglas Schuler,et al.  Participatory Design: Principles and Practices , 1993 .

[12]  Matthias Jarke,et al.  PRIME—toward process-integrated modeling environments: 1 , 1999, TSEM.

[13]  Mark Neal,et al.  Why and how of requirements tracing , 1994, IEEE Software.

[14]  Gerald M. Weinberg,et al.  Handbook of Walkthroughs, Inspections, and Technical Reviews: Evaluating Programs, Projects, and Products , 1990 .

[15]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[16]  Annie I. Antón,et al.  Goal-based requirements analysis , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[17]  Karan Harbison,et al.  User-Centered Requirements: The Scenario-Based Engineering Process , 1997 .

[18]  Francoise Brun-Cottan,et al.  Using video to re-present the user , 1995, CACM.

[19]  Joseph A. Goguen,et al.  An Object-Oriented Tool for Tracing Requirements , 1996, IEEE Softw..

[20]  Matthias Jarke,et al.  Scenario usage in system development: a report on current practice , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[21]  Lucy Suchman,et al.  Understanding practice: video as a medium for reflection and design (excerpt) , 1992 .

[22]  Nicola Millard,et al.  Child's play: using techniques developed to elicit requirements from children with adults , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[23]  Barbara Farbey,et al.  Exploring Requirements: Quality Before Design , 1991 .

[24]  Michael A. Jackson,et al.  Software requirements and specifications - a lexicon of practice, principles and prejudices , 1995 .

[25]  Balasubramaniam Ramesh,et al.  Requirements traceability: Theory and practice , 1997, Ann. Softw. Eng..

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

[27]  Klaus Pohl,et al.  Requirements Elicitation and Validation with Real World Scenes , 1998, IEEE Trans. Software Eng..

[28]  Keld Bødker,et al.  Workplace Cultures: Looking at Artifacts, Symbols and Practices , 1992 .