Abstract

The User Requirements Notation (URN) combines goals and scenarios in order to help capture and reason about user requirements prior to detailed design. In terms of application areas, this emerging standard targets reactive systems in general, with a particular emphasis on telecommunications systems and services. However, URN can also be applied to business process modeling. In this paper, we illustrate how goals can help design suitable business processes expressed as scenarios, and the architectures supporting them. URN models can also help us determine when is the right moment to improve the business model. Through a supply chain management case study, this paper illustrates how architectures can evolve in that context while the scenarios remain untouched.

-- Daniel Amyot - 11 Oct 2005

Discussion

• Please feel free to discuss this article directly on this page. Constructive comments are welcomed! Please sign your TWiki name.