M. Weiss∗ , D. Amyot†
of Computer Science, Carleton University Ottawa, ON, K1S 5B6 (Canada) Email: firstname.lastname@example.org † SITE, University of Ottawa Ottawa, ON, K1N 6N5 (Canada) Email: email@example.com
Abstract— Companies need to adjust their business models constantly to changes in their environment. In this paper we propose a lightweight approach for evolving business models that allows for a quick evaluation of alternatives, while preserving investments in existing business processes. The approach is based on the User Requirements Notation (URN) for modeling and analysis of early requirements in the form of goals and scenarios. URN models help us model the strategic options available to a business for evolving its business model, and determine when the right moment to apply them has come. We illustrate the systematic and incremental evolution of business model alternatives for an e-business case study.
I. I NTRODUCTION In today’s rapidly evolving world, companies need to adjust their business models constantly to changes in their environment. However, they also need to do so in a controlled manner. An approach to evolving business models needs to strike a balance between capitalizing on new opportunities, and entering uncharted territories by mitigating the risks involved with such a change. The approach must be lightweight in order to quickly evaluate alternative models, but also be reliable. We argue that the User Requirements Notation (URN) ,  enables such an approach. While it allows us to explore alternative business models, it addresses the need to preserve investments in existing business processes. Business processes can be expressed as scenarios, which are deﬁned separately from the participants in the business model that perform them. This allows us to experiment with different business models without changing the underlying business processes. URN has many concepts relevant for business process modeling, such as behavior, structure, goals, and non-functional requirements. URN combines two complementary notations: the Goal-oriented Requirement Language (GRL) , and the Use Case Map (UCM) notation . GRL captures business or system goals, alternative means of achieving goals, and the rationale for goals and alternatives. The notation is especially good for the modeling of non-functional requirements. A UCM model depicts scenarios as causal ﬂows of responsibilities that can be superimposed on underlying structures of components. Responsibilities are scenario activities representing something to be performed (operation, action, task, function, etc.), and can be allocated to components. Components are generic enough to represent software entities