READING

SUBSYSTEMS AND PROXY SURROGATE PROXY

ACCESS CONTROL

PROTECTION PROXY

DESIGN GLOBAL CONTROL FLOW

Procedure-driven control Event-driven control Threads: Threads are the concurrent variation of procedure-driven control: The system can create an arbitrary number of threads, each responding to a different event. If a thread needs additional data, it waits for input from a specific actor.

IDENTIFY BOUNDARY CONDITIONS

boundary conditions of the systemthat is, to decide how the system is started, initialized, and shut down

CONFIGURATION

EXCEPTIONS
Exceptions: A hardware failure; Changes in the operating environment; A software fault meaningful error message

INTERFACE SPECIFYING TYPES, SIGNATURES, AND VISIBILITY

Attributes are public -> actually private, but with full getter and setter Visibility of method

SPECIFYING PRE- AND POSTCONDITIONS

Instead, we focus on specifying operations using both constraints and natural language and emphasizing boundary cases for the purpose of better communication among developers.

Public methods and contract: define contracts for each public operation of each class. Contract: agreement between the class user and the class implementer CONTRACT: Contracts are constraints on a class that enable class users, implementers, and extenders to share the same assumptions about the class (formal def) The postconditions describe what the class implementer guarantees in the event the class user fulfilled her part of the contract. When refining a class, class extenders inherit the contract from the original class implementer.-> Liskov substitution principle

PORE- AND POST-CONDITIONS

OCL

INVARIANT
Invariants constitute a permanent contract that extends and overwrites the operation-specific contracts. Similar to identify the abstract classes: The activity of identifying invariants is similar to that of finding abstract classes during analysis Commonality: Others can be identified by extracting common properties from operation-specific contracts.