Some patterns for software architectures
Mary Shaw · 1996
Design patterns for software architectures interactions. The architectural diagrams are often highly specific to the systems they describe, especially in the labeling of components. Shaw 2 The diagrams are supported by prose descriptions. This prose uses terms with common, if informal, definitions: "Camelot is based on the client-server model and uses remote procedure calls both locally and remotely to provide communication among applications and servers." [Spector 87] "Abstraction layering and system decomposition provide the appearance of system uniformity to clients, yet allow Helix to accommodate a diversity of autonomous devices. The architecture encourages a client-server model for the structuring of applications." [Fridrich 85] "We have chosen a distributed, object-oriented approach to managing information." [Linton 87] "The easiest way to make the canonical sequential compiler into a concurrent compiler is to pipeline the execution of the compiler phases over a number of proc...
Cited by 72 works.
Authors
References
- Design Patterns: Elements of Reusable Object-Oriented Software
- On the criteria to be used in decomposing systems into modules
- A cookbook for using the model-view controller user interface paradigm in Smalltalk-80
- The Semantics of a Simple Language for Parallel Programming.
- Introduction to Software Architecture
- The Design of the UNIX Operating System
- Object-oriented development
- PLANNER: a language for proving theorems in robots
- Abstractions for software architecture and tools to support them
- Gandalf: Software development environments