Eliciting Gaps in Requirements Change Wouter Westendorp

Publication Published in the Journal of Requirements Engineering 2004, Volume 9, Issue 1 Authors: o Colette Rolland o Camille Salinesi o Anne Etien o.. all from Université Paris Cited by 40 (Google) / 5 (ACM) Applied at the integration of Renault-DIAC into the Renault Group

Context Change Requirements Engineering o From As-Is situation to To-Be situation More specifically: system adaptation o System evolution caused by changes in organizational context (mergers, globalisation) o Legacy software Make changes explicit and traceable

Method Model both situations o Differences imply changes Goal oriented o From high-level strategy to low-level system constraints Iterative method o Top-down approach Participative o Requires domain experts

Related Literature Rolland, C., & Prakash, N. (2001). Matching ERP system functionality to customer requirements. Proceedings of RE’01 5th international symposium on requirements engineering, Toronto, Canada, Lenz, R., & Kuhn, K. A. (2004). Towards a continuous evolution and adaptation of information systems in healthcare. International Journal of Medical Informatics, 73 (1), Christel, M. G., & Kang, K. C. (1992). Issues in requirements elicitation. Technical Report CMU/SEI-92-TR-012

Constructing a Map Identify Intentions (What) o For example: Offer a service o or, Start or Stop Identify Strategies (How) o For example: at a flat fee rate Construct the Map o Source intention -> Strategy -> Target Intention o.. for each intention Refine if necessary

Identify gaps Compare the As-Is map and the To-Be map: Apply an Operator to an Intention or Strategy For example: Rename: Make a contract for a client as Enter into a contract with a client Remove: By phone call

Example: As-Is situation A reader can pay for the magazine by issue or subscription. The payment may be fulfilled by bank transfer or credit-card Start -> By issue -> Pay Start -> Subscription -> Pay Start -> By bank transfer -> Stop Start -> By credit card -> Stop

Example: To-Be Situation A reader can pay for the magazine by issue, monthly or yearly subscription. The payment may be fulfilled by bank transfer or PayPal Start -> By issue -> Pay Start -> By monthly subscription -> Pay Start -> By yearly subscription -> Pay Start -> By bank transfer -> Stop Start -> With PayPal -> Stop

Example: Gaps Remove: By Subscription Add: By monthly subscription Add: By yearly subscription Remove: By credit-card Add: With PayPal

Process Deliverable Diagram

Thank you Any questions?