object-oriented programming

Object-oriented organisation

Records how responsibilities and interactions are organised around objects within the selected boundary.

1. Which codebase, subsystem or design proposal is assessed, and which responsibilities are assigned to objects? boundary
2. Which code examples or design records demonstrate object-centred behaviour rather than classes used only as namespaces or records? provenance

Classes, prototypes and instance structure

Records the mechanisms used to define, instantiate and alter objects without treating classes as mandatory.

1. Do objects obtain behaviour from classes, prototypes, per-instance members or another documented mechanism? definition
2. Can an object's members or behaviour providers change after creation, and what language or runtime evidence establishes this? provenance

Identity, equality and copy contracts

Records when references denote the same object and when distinct objects count as equal.

1. How are object identity and value equality distinguished, including any equality and hashing contract? definition
2. When an object is copied or replaced, which identities and references remain shared, and which caller observations must remain equivalent? action

Invariant enforcement boundary

Records valid object states, permitted mutation paths and the limits of encapsulation.

1. Which conditions must hold at observable operation boundaries, and which constructors or methods establish and preserve them? definition
2. Can callers bypass those methods through public fields, mutable values returned by accessors, aliases or reflective access? boundary

Method lookup and dispatch

Records binding, overriding and lookup rules used by the assessed implementation.

1. For a representative operation, which receiver, declared types, runtime types or prototype links determine the selected implementation? definition
2. Which language rules and code evidence distinguish overloading, overriding, member hiding and delegation where they occur? provenance

Substitution obligations

Records preconditions, outcomes, failures and state effects that implementations must preserve.

1. What inputs, results, exceptions and state changes may callers rely on through the shared interface? definition
2. What evidence shows that a proposed replacement accepts the required inputs and preserves those guarantees? action

Collaboration and knowledge boundaries

Records which objects perform a task and how much each knows about others' internals.

1. For a representative task, which object owns each decision and which collaborators does it invoke? definition
2. Which interactions depend on collaborators' internal representation or long navigation chains, and what changes would those dependencies propagate? boundary

Inheritance, composition and delegation

Records the intent and consequences of each mechanism used to reuse or extend behaviour.

1. Which relationships provide implementation reuse, which promise substitution, and which forward work to contained or referenced objects? definition
2. For a proposed extension, what caller contracts, override dependencies and ownership assumptions determine whether inheritance, composition or delegation is appropriate? action

Lifecycle validity

Records how objects become valid, which operations are legal in each state and how obligations end.

1. When does an object become valid for use, and can partially initialised state escape through callbacks, registration or overridable constructor calls? boundary
2. Which operations are permitted after each lifecycle transition, and who must release any resources the object owns? action

Refactoring evidence

Records whether a proposed structural change preserves required contracts, identity effects and interactions.

1. Which observable results, state transitions, identity relationships and collaborator effects must a proposed refactoring preserve? boundary
2. Which contract checks and representative interaction tests support the change, and which affected behaviours remain unchecked? action

Kinds and varieties

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these kinds and varieties hold for the sense of object-oriented programming this model covers, and on what evidence? provenance

Identifiers and schemes

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these identifiers and schemes hold for the sense of object-oriented programming this model covers, and on what evidence? provenance

Standards and regulation

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these standards and regulation hold for the sense of object-oriented programming this model covers, and on what evidence? provenance

Real-world use

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these real-world use hold for the sense of object-oriented programming this model covers, and on what evidence? provenance

Typical measurements

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these typical measurements hold for the sense of object-oriented programming this model covers, and on what evidence? provenance

Failure modes and hazards

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these failure modes and hazards hold for the sense of object-oriented programming this model covers, and on what evidence? provenance

Regional variation

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these regional variation hold for the sense of object-oriented programming this model covers, and on what evidence? provenance

Neighbouring kinds and how to tell them apart

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

1. Which of these neighbouring kinds and how to tell them apart hold for the sense of object-oriented programming this model covers, and on what evidence? provenance