Learn More
Informally described design patterns are useful for communicating proven solutions for recurring design problems to developers, but they cannot be used as compliance points against which solutions that claim to conform to the patterns are checked. Pattern specification languages that utilize mathematical notation provide the needed formality, but often at(More)
An aspect-oriented design model consists of a set of aspect models and a primary model. Each aspect model describes a feature that crosscuts elements in the primary model. Aspect and primary models are composed to obtain an integrated design view. In this paper we describe a composition approach that utilizes a composition algorithm and composition(More)
The increasing use of Web-based applications continues to broaden the user groups of enterprise applications at large. Since ordinary users often equate the quality of user interface (UI) with the quality of the entire application, the importance of providing easy-to-use UIs has been significantly increasing. Unfortunately, designing a single UI satisfying(More)
An aspect-oriented design model consists of a set of aspect models and a primary model. Each of these models consists of a number of different kinds of UML diagrams. The models must be composed to identify conflicts and analyze the system as a whole. We have developed a systematic approach for composing class diagrams in which a default composition(More)
A design pattern describes a generic solution for problems that occur repeatedly. Current descriptions of design patterns describe solutions with graphical notation and complementing text. To encourage the use of design patterns, the development of pattern supporting tools is imperative. This requires design patterns to be specified precisely. There has(More)
class implemented_by Image Display (applying the Bridge pattern) displayed_on Display ImageImpl1 Figure 1. An example of pattern-based model refactoring. ConcreteImpB ConcreteImpA Implementor RefinedAbstraction Abstraction implemented_by Figure 2. A diagram of the Bridge pattern. tion of the UML designs representing solutions of the pattern Transformation(More)
The development of reusable requirements and design artifacts often requires one to characterize families of problem and solution models. This paper presents a metamodeling approach to characterizing a family of models. A characterization is expressed as a Role Model that consists of roles that can be played by UML model elemets. In this paper we describe(More)
Cost-effective development of large, integrated computer-based systems can be realized through systematic reuse of development experiences throughout the development process. We describe a technique for representing reusable modeling experiences. The technique allows developers to express domain-specific design patterns as a sub-language of the modeling(More)
Abstract The Unified Modeling Language (UML) is being used as the de-facto standard in the software industry. With the adoption of UML 2.0, the new enhancements allow this version to describe many of the elements found in today’s software technology as well as Model Driven Architecture and Service-Oriented Architecture. Although OMG has released several UML(More)