Documenting architectures with patterns

Abstract

Software patterns have been used for a decade or more to describe solutions to design and architecture problems. This paper illustrates the value of using software patterns to describe and generate specific architectures and discusses the objectives and techniques of documenting architectures using these patterns. It defines the specialized system of software patterns called a pattern language and presents example patterns and an example pattern language. Finally, it introduces a set of software patterns that represents service architectures, including service architectures for offering advanced services. © 2004 Lucent Technologies Inc.

Capitalization and reuse with patterns in a Model-Based Systems Engineering (MBSE) framework

“…First of all, it is necessary to acknowledge the fact that similar designs can emerge from independent engineering teams [17]. Those similarities implies one of the first characteristic of patterns: they "are not created from a blank page; they are mined" [18]. The "mining" of pattern appears to be a scientific issues that is essential to resolve as Systems Engineering patterns are embedded in existing designs [4].…”

“…This paper proposes a classification in four levels (Figure 2), ranging from "models" developed by the engineer at the lowest level of abstraction to "abstract patterns" at the highest level of abstraction. [18], [19], [29]) and an implementation process, presented in section III.B.…”

Exploring systems engineering patterns in government acquisition of complex information systems

“…Extending these ideas, Cloutier and Verma [5] described how complexity drives a need to capture implicit knowledge, e.g., patterns, within corporations. Hanmer's and Kocan's [15] work described the idea of separating patterns from development, stating that patterns are mined from existing experience rather than created as part of a definition process. They also discussed how a collection of patterns can enable their application to more complex problems.…”

“…From the test results, it can be observed that the model appears to have some forecasting strength and that values at each of the lower levels of the SE REI model provide insight Interpersonal skills (4) Competence Trust (5) Decision making (6) Integrity (7) Sense of purpose Vision (8) Systems thinking (9) Transformational planning (10) Political and organization Enterprise environment management Business (11) Policy and procedure (12) Accountability and authority (13) Team management Stakeholder management (14) Customer relationship management (15) Communications (16) Acquisition Planning and provisioning (17) Risk management (18) Control and assessment (19) Info management Engineering management Technical (20) Resource management (21) Cyber security management (22) Analysis and design Lifecycle management (23) Development (24) Implementation (25) SE change management Process management (26) Measurement (27) Quality into the patterns that determine group membership. The authors then researched the patterns in the 27 competency areas underlying group membership to derive patterns prevalent in successful and conversely challenged projects.…”

Comparing reliability and security: Concepts, requirements, and techniques

“…The pattern form allows a discussion of the aspects of the problem that must be weighed and balanced to achieve the best possible solution for a given situation. The pattern literature contains works that range from objectoriented design [5] to patterns that describe specific techniques in a particular domain, for example, those in [6,7,16]. Patterns allow design information to be exchanged in a way that facilitates its reuse.…”