Abstract

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.

-- DanielAmyot - 15 Mar 2007

Discussion

FormForVirtualLibrary edit

Title Formalizing Patterns with the User Requirements Notation
Authors Mussbacher, G., Amyot, D., and Weiss, M.
Type Book
Conference/Journal Title Design Pattern Formalization Techniques
Volume/Number
Editors T. Taibi
Publisher Idea Group Inc.
Month -
Year 2007
Pages 304-325
Keywords Architecture, Formalization, GRL, Patterns, Trade-off Analysis, UCM, URN
Topic revision: r1 - 14 Mar 2007, DanielAmyot
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