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.

-- DanielAmyot - 11 Oct 2005

Discussion

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

FormForVirtualLibrary edit

Title Designing and Evolving Business Models with URN
Authors M. Weiss and D. Amyot
Type Conference
Conference/Journal Title Montreal Conference on eTechnologies (MCETECH05)
Volume/Number
Editors
Publisher
Month January
Year 2005
Pages 149-162
Keywords Business Proess Modeling, Evolution, User Requirements Notation, URN
Topic attachments
I Attachment Action Size Date Who Comment
MCeTech05.pdfpdf MCeTech05.pdf manage 385 K 11 Oct 2005 - 13:49 DanielAmyot Paper
MCeTech05.pptppt MCeTech05.ppt manage 605 K 11 Oct 2005 - 13:49 DanielAmyot Accompanying presentation
Topic revision: r2 - 12 Oct 2005, GunterMussbacher
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback