Journal of Systems and Software
FBCM: Strategy modeling method for the validation of software requirements
Journal of Systems and Software
Towards evolution of strategic IT requirements
Proceedings of the 2007 ACM symposium on Applied computing
Three integration approaches for map and B-SCP requirements engineering techniques
Proceedings of the 2008 ACM symposium on Applied computing
Integrating B-SCP and MAP to manage the evolution of strategic IT requirements
Information and Software Technology
Towards Engineering Purposeful Systems: A Requirements Engineering Perspective
DEXA '08 Proceedings of the 19th international conference on Database and Expert Systems Applications
Co-Design of Web Information Systems Supported by SPICE
Proceedings of the 2009 conference on Information Modelling and Knowledge Bases XX
Fitting business models to system functionality exploring the fitness relationship
CAiSE'03 Proceedings of the 15th international conference on Advanced information systems engineering
Fitting System Functionality to Business Needs: Alignment issues and challenges
Proceedings of the 2010 conference on New Trends in Software Methodologies, Tools and Techniques: Proceedings of the 9th SoMeT_10
MC Sandbox: Devising a tool for method-user-centered method configuration
Information and Software Technology
From conceptual modeling to requirements engineering
ER'06 Proceedings of the 25th international conference on Conceptual Modeling
Eliciting potential requirements with feature-oriented gap analysis
ICSR'06 Proceedings of the 9th international conference on Reuse of Off-the-Shelf Components
Modelling information requirements in complex engineering services
Computers in Industry
Hi-index | 0.00 |
We consider requirements change due to system evolution which results from contextual forces such as the decision to standardise practices across subsidiaries of a company. Our experience with the financial branch of the French Renault group is that eliciting change requirements poses its own specific problems. We propose to model change as a set of gaps between the requirements specification of the current and the future system. Our approach is to define a generic typology of gaps to facilitate a precise definition of change requirements. It adopts a goal oriented requirements specification and shows how to customise the generic gap typology to this specific requirements representation formalism. The paper presents the approach to elicit gaps and illustrates it with the Renault case study.