Patterns, frameworks, and middleware: their synergistic relationships

Schmidt, Douglas C.; Buschmann, Frank

doi:10.1109/icse.2003.1201256

Cited by 58 publications

(36 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Architectural patterns capture reusable architectural knowledge in the form of well-proven solutions to recurring software design problems arising in particular contexts and domains [17]. Patterns concern some of the most important architectural decisions, are easy Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page.…”

Section: Introductionmentioning

confidence: 99%

Architecting as decision making with patterns and primitives

Zdun

Avgeriou

Hentrich³

et al. 2008

Proceedings of the 3rd International Workshop on Sharing and Reusing Architectural Knowledge

View full text Add to dashboard Cite

The application of patterns is used as a foundation for many central design decisions in software architecture, but because of the informal nature of patterns, these design decisions are usually not precisely documented in the models. In our earlier work, we had proposed pattern primitives as a solution to precisely model the patterns in the corresponding architectural views. Building upon that approach, this paper introduces a pattern-based architecting process that aims at inexpensively documenting design decisions in the architectural views alongside the natural flow of design. The decisions that are made explicit, concern the selection of patterns, their variants and the corresponding primitives, as well as the resolution of inconsistencies between the architectural views. The approach is demonstrated in the domain of process-driven SOA for two architectural views: Component-and-Connector and Process Flow.

show abstract

Section: Introductionmentioning

confidence: 99%

Architecting as decision making with patterns and primitives

Zdun

Avgeriou

Hentrich³

et al. 2008

Proceedings of the 3rd International Workshop on Sharing and Reusing Architectural Knowledge

View full text Add to dashboard Cite

show abstract

“…Schmidt & Buschmann (2003) Even though these properties of the pattern approach are highly valuable in the software design process, they also make pattern instances hard to trace in the models and implementations. To overcome this problem, we introduced an approach to document precisely specified primitive abstractions that can be found in the patterns (cf.…”

Section: Software Patterns and Pattern Primitivesmentioning

confidence: 99%

“…Software patterns capture reusable design knowledge and expertize that provides proven solutions to recurring software design problems that arise in particular contexts and domains (cf. Schmidt & Buschmann (2003)). A software pattern, however, is described in an informal form and cannot easily be described formally, e.g., by using a parameterizable, template-style description.…”

Section: Introductionmentioning

confidence: 99%

Model-driven and pattern-based integration of process-driven SOA models

Zdun¹,

Dustdar²

2007

IJBPIM

View full text Add to dashboard Cite

Service-oriented architectures (SOA) are increasingly used in the context of business processes. However, the modeling approaches for process-driven SOAs do not yet sufficiently integrate the various kinds of models relevant for a processdriven SOA -ranging from process models to software architectural models to software design models. We propose to integrate process-driven SOA models via a modeldriven software development approach that is based on proven practices documented as software patterns. We introduce pattern primitives as an intermediate abstraction to precisely model the participants in the solutions that patterns convey. To enable model-driven development, we develop domain-specific modeling languages for each kind of process-driven SOA model -based on meta-models that are extended with the pattern primitives. The various process-driven SOA models are integrated in a modeldriven tool chain via the meta-models. Our tool chain validates the process-driven SOA models with regard to the constraints given by the meta-models and primitives.

show abstract

“…An object-oriented framework is characterized by an inversion in the normal control relationship between the programmer and the library [6]. In the traditional usage of a library, the programmer decides when to invoke library functions and which ones to invoke.…”

Section: Frameworkmentioning

confidence: 99%