This chapter demonstrates how the User Requirements Notation (URN) can be used to model business processes. 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 focus on telecommunications systems and services. This chapter argues that the URN can also be applied to business process modeling. To this end, it illustrates the notation, its use, and its benefits with a supply chain management case study. It then briefly compares this approach to related modeling approaches, namely, use case-driven design, service-oriented architecture analysis, and conceptual value modeling. The authors believe that a URN-based approach will provide usable and useful tools to assist researchers and practitioners with the modeling, analysis, integration, and evolution of existing and emerging business processes.
- Please feel free to discuss this article directly on this page. Constructive comments are welcomed! Please sign your TWiki name.
- Document available upon request.
- 13 Feb 2007
| Title || Business Process Modeling with the User Requirements Notation |
| Authors || M. Weiss and D. Amyot |
| Type || Book |
| Conference/Journal Title || Advances in E-Business Research: E-Business Innovation and Process Management |
| Volume/Number || 1 |
| Editors || In Lee |
| Publisher || Cybertech Publishing |
| Month || December |
| Year || 2006 |
| Pages || 162-193 |
| Keywords || Architectural changes, BPM, goals, MSC, scenarios, supply chain management, UCM, URN |