Toward an Integrated User Requirements Notation Framework and Tool forBusiness Process Management

2008 ◽  
Author(s):  
Alireza Pourshahid ◽  
Daniel Amyot ◽  
Liam Peyton ◽  
Sepideh Ghanavati ◽  
Pengfei Chen ◽  
...  
Keyword(s):  
Process Management ◽  
User Requirements ◽  
User Requirements Notation

Business process management with the user requirements notation

2009 ◽  
Vol 9 (4) ◽  
pp. 269-316 ◽  
Author(s):  
Alireza Pourshahid ◽  
Daniel Amyot ◽  
Liam Peyton ◽  
Sepideh Ghanavati ◽  
Pengfei Chen ◽  
...  
Keyword(s):  
Business Process ◽  
Business Process Management ◽  
Process Management ◽  
User Requirements ◽  
User Requirements Notation

Formalizing Patterns with the User Requirements Notation

2011 ◽  
pp. 302-323 ◽  
Author(s):  
Gunter Mussbacher ◽  
Daniel Amyot ◽  
Michael Weiss
Keyword(s):  
Design Patterns ◽  
User Requirements ◽  
Trade Off ◽  
User Requirements Notation ◽  
Trade Offs ◽  
Combined Use ◽  
Particular Solution

Patterns need to be described and formalized in ways that enable the reader to determine whether the particular solution presented is useful and applicable to his or her problem in a given context. However, many pattern descriptions tend to focus on the solution to a problem, and not so much on how the various (and often conflicting) forces involved are balanced. This chapter describes the user requirements notation (URN), and demonstrates how it can be used to formalize patterns in a way that enables rigorous trade-off analysis while maintaining the genericity of the solution description. URN combines a graphical goal language, which can be used to capture forces and reason about trade-offs, and a graphical scenario language, which can be used to describe behavioral solutions in an abstract manner. Although each language can be used in isolation in pattern descriptions (and have been in the literature), the focus of this chapter is on their combined use. It includes examples of formalizing Design patterns with URN together with a process for trade-off analysis.

Enterprise modeling with the Joint Use of User Requirements Notation and UML

2011 ◽  
pp. 45-66
Author(s):  
Anna Medve
Keyword(s):  
Process Modeling ◽  
Unified Modeling Language ◽  
Enterprise Modeling ◽  
User Requirements ◽  
Urn Model ◽  
Fully Integrated ◽  
Unified Modeling ◽  
User Requirements Notation ◽  
Design Documentation ◽  
Enterprise Models

This chapter introduces the User Requirements Notation (URN) standardized formal methods and its joint use with Unified Modeling Language (UML) in enterprise modeling. It argues that the joint use of URN and UML can enhance enterprise models and co-evolve with enterprise engineering processes. URN combines goals and scenarios to help reasoning and to capture user requirements prior to detailed design. Furthermore, URN can be integrated partially or entirely into an existing business process modeling approach, without replace current ways of creating and analyzing models in order to be useful. Modelled in the UML, a URN model may be incorporated into the rest of a system’s UML design documentation, seamlessly linking the documentation for the requirements elicitation part of a project to the whole and an be fully integrated with the rest of the design documentation for a software system.

Sign in / Sign up

Export Citation Format

Share Document