Pattern-Oriented Software Architecture, Volume 1¶
Buschmann, F. (1996). Pattern-Oriented Software Architecture, Volume 1: A System of Patterns. Wiley.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Design Patterns
- From this software foundation, pattern thinking generalized: Fowler's (2002) enterprise application patterns (Repository, Service Layer, Unit of Work, Active Record, Data Mapper), cloud-infrastructure patterns (Sidecar, Ambassador, Blue-Green Deployment, Canary Release), distributed-systems patterns (Circuit Breaker, Bulkhead, Saga, CQRS, Event Sourcing) catalogued in Buschmann, Meunier, Rohnert, Sommerlad, and Stal (1996), security-architecture patterns (Defense in Depth, Zero Trust, Threat Modeling), instructional-design patterns, organizational-change patterns (Fearless Change), domain-driven design patterns (Evans, 2003), and game-design patterns all follow Alexander's documented-solution template.
This sourceArchitectural-scale pattern catalog (Layers, Pipes and Filters, Blackboard, Broker, MVC). Cited inline in §3 and §9 (tier B — supports the architectural-pattern-lineage and catalog claims).
- From this software foundation, pattern thinking generalized: Fowler's (2002) enterprise application patterns (Repository, Service Layer, Unit of Work, Active Record, Data Mapper), cloud-infrastructure patterns (Sidecar, Ambassador, Blue-Green Deployment, Canary Release), distributed-systems patterns (Circuit Breaker, Bulkhead, Saga, CQRS, Event Sourcing) catalogued in Buschmann, Meunier, Rohnert, Sommerlad, and Stal (1996), security-architecture patterns (Defense in Depth, Zero Trust, Threat Modeling), instructional-design patterns, organizational-change patterns (Fearless Change), domain-driven design patterns (Evans, 2003), and game-design patterns all follow Alexander's documented-solution template.
Domain-specific¶
Verification¶
Does it exist? Confirmed. This work's ISBN resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Not recorded. Neither this nor any other of the 2 citations of this work carries a recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:2036731a1fba · see in the full table