Abstract
Eliciting change requirements in the context of system evolution is different from eliciting requirements for a system developed from scratch. Indeed, there is a system and documentation that should be referred to. Therefore, the issue is not only to identify new functions, but to uncover and understand differences with the current situation. There is few approaches that systematise the identification and documentation of such change requirements. Our approach is based on the analysis at the model level of the fitness relationship between the business and the system. Our experience showed us that another kind of change requirements could also be found when asking the question of continuity at the instance level. The literature already proposes so called “modification policies" that allow to manage current instances of the system workflows and business processes when their model evolve. However, these approaches are not interested in the elicitation of the requirements that relate to these modification policies, but to the technical solutions that these policies provide. The position taken in this paper is that change requirements can be elicited by analysing system evolutions through modification policies at the instance level. The paper proposes to document these requirements using the same approach as other change requirements.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Salinesi, C., Rolland, C.: Fitting Business Models to Systems Functionality Exploring the Fitness Relationship. In: Eder, J., Missikoff, M. (eds.) CAiSE 2003. LNCS, vol. 2681, pp. 16–20. Springer, Heidelberg (2003)
Salinesi, C., Presso, M.J.: A Method to Analyse Changes in the Realisation of Business Intentions and Strategies for Information System Adaptation. In: Proceedings of EDOC 2002, Lausanne, Switzerland (September 2002)
Rolland, C., Salinesi, C., Etien, A.: Eliciting Gaps in Requirements Change. To appear in Requirement Engineering Journal (2003)
Etien, A., Salinesi, C.: Towards a Systematic Definition of Requirements for Software Evolution: A Case-study Driven Investigation. In: Proc of EMMSAD 2003 Velden, Austria (2003)
Sadiq, S.: Handling Dynamic Schema Change in Process Models. Australian Database Conference, Canberra, Australia. January 27- Febraury 02 (2000)
Liu, C., Orlowska, M., Li., H.: Automating Handover in Dynamic Workflow Environments. In: Pernici, B., Thanos, C. (eds.) CAiSE 1998. LNCS, vol. 1413, p. 159. Springer, Heidelberg (1998)
Bandinelli, S., Fuggetta, A., Ghezzi, C.: Software Process Model Evolution in the SPADE. IEEE Transactions on Software Engineering 19(12), 1128–1144 (1993)
Jarke, M., Pohl, K.: Requirements Engineering in 2001: Managing a Changing Reality. IEEE Software Engineering Journal, 257–266 ((November 1994)
Van der Aalst, W.: Generic Workflow Models: How to Handle Dynamic Change and Capture Management Information. In: Lenzerini, M., Dayal, U. (eds.) Proceedings of the Fourth IFCIS International Conference on Cooperative Information Systems, Edinburgh, Scotland, pp. 115–126 (1999)
Conradi, R., Fernström, C., Fuggetta, A.: A Conceptual Framework for Evolving Software Process. ACM SIGSOFT Software Engineering Notes 18(4), 26–34 (1993)
Sadiq, S., Orlowska, M.: Architectural Considerations in Systems Supporting Dynamic Workflow Modification. In: Proceedings of the workshop on Software Architectures for Business Process Management at CAiSE 1999, Heidelberg, Germany, June14-18 (1999)
Joeris, G., Herzog, O.: Managing Evolving Workflow Specifications With Schema Versioning and Migration Rules. TZI Technical Report 15, University of Bremen (1999)
Salinesi, C., Wäyrynen, J.: A Methodological Framework for Understanding IS Adaptation through Enterprise Change. In: Proceedings of OOIS 2002, 8th International Conference on Object-Oriented Information Systems, Montpellier, France (2002)
Rolland, C., Prakash, N.: Matching ERP System Functionality to Customer Requirements. In: Proceedings of RE 2001, Toronto, Canada, pp. 66–75 (2001)
Rolland, C., Prakash, N., Benjamen, A.: A Multi-Model View of process Modelling. Requirements Engineering Journal 4, 169–187 (1999)
Han, J.: Supporting Impact Analysis and Change Propagation in Software Engineering Environments. In Proceedings of 8th International Workshop on Software Technology and Engineering Practice (STEP 1997/CASE 1997), London, UK, July 1997, pp. 172–182 (1997)
Deruelle, L., Bouneffa, M., Goncalves, G., Nicolas, J.C.: Local and Federated Database Schemas Evolution An Impact Propagation Model. In: Bench-Capon, T.J.M., Soda, G., Tjoa, A.M. (eds.) DEXA 1999. LNCS, vol. 1677, pp. 902–911. Springer, Heidelberg (1999)
Chauman, M.A., Kabaili, H., Keller, R.K., Lustman, F.: A Change Impact Model for Changeability Assessment in Object Oriented Software Systems. In: Proceedings of the Third European Conference on Software Maintenance and Reengineering, IEEE Comput. Soc, Los Alamitos (1999)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2003 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Salinesi, C., Etien, A. (2003). Compliance Gaps: A Requirements Elicitation Approach in the Context of System Evolution. In: Konstantas, D., Léonard, M., Pigneur, Y., Patel, S. (eds) Object-Oriented Information Systems. OOIS 2003. Lecture Notes in Computer Science, vol 2817. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-45242-3_8
Download citation
DOI: https://doi.org/10.1007/978-3-540-45242-3_8
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-40860-4
Online ISBN: 978-3-540-45242-3
eBook Packages: Springer Book Archive