Using pattern languages for object-oriented programs.

Beck, K., & Cunningham, W. (1987). Using pattern languages for object-oriented programs.

Type

Web resource

Intellectual base

Web

Year

1987

Link

https://c2.com/doc/oopsla87.html

Cited from

architecture_urban_planning

Cited by

1 citation across 1 artifact.

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 sourceFirst application of Alexander's pattern-language methodology to OO programming (a five-pattern language for Smalltalk UIs); foundational for the software pattern movement.

    Supported in partVerified against the work's full text

    Beck and Cunningham's paper itself adapts Alexander's pattern language to object-oriented programming, but it does not claim to be first or say anything about Alexander's architectural influence.

    “We outline our adaptation of Pattern Language to object-oriented programming.”

    Read by an automated reader; not a human review. How support was checked

Verification

Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.

Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.

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:c642e369f1df · see in the full table