The Role Object Pattern.

Bäumer, D., Riehle, D., Siberski, W., & Wulf, M. (1997). The Role Object Pattern. Proceedings of the 4th Pattern Languages of Programming Conference (PLoP '97).

Type

Conference paper

Intellectual base

Primary research

Year

1997

Link

https://hillside.net/plop/plop97/Proceedings/riehle.pdf

Cited from

philosophy

Cited by

1 citation across 1 artifact.

Each citation links to the sentence it supports in the citing article.

Primes

• Aspectual Individual
  • In object-oriented software, the same structure appears as interface polymorphism: one underlying object is addressed as a Reviewer in one subsystem and as a Customer in another, each interface exposing only the responsibilities of that role.

    This sourceA design pattern in which one core object plays multiple roles via transparently attached role objects, each exposing only its context's responsibilities — the software instance of one base addressed as different aspect-bound bearers (Reviewer, Customer).

    Supported in partVerified against the work's full text

    The Role Object pattern shows one core object presenting context-specific role views (Customer as Borrower or Investor); it uses a banking example, not Reviewer/Customer, and is not framed as interface polymorphism.

    “The Role Object pattern suggests to model context-specific views of an object as separate role objects which are dynamically attached to and removed from the core object.”

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