OCUP 2 Advanced case studies
OCUP 2 Advanced · Put your knowledge to work in context.
The OMG UML 2 Advanced certification (OCUP 2) is the top tier of a three-exam UML program that also includes Foundation and Intermediate levels; Intermediate is the stated prerequisite. OMG describes the Advanced exam as testing the complete UML palette of elements and attributes for modeling structure and behavior in the largest system models, plus metamodeling grounded in related UML-family specifications: Alf, fUML, and MOF. The OCUP 2 Advanced case studies are 5 cases and about 4,717 words.
1Ports, Provided and Required Interfaces in a 400-Class Avionics Model
Skyline Systems is merging three legacy flight-management models into a single 400-class component model with about 1,200 ports, exchanged between two vendors' tools as XMI 2.5.1. The original authors declared every protocol with an «interfaceRealization» from the component class to the interface, typed the ports with plain classes, and drew the ball-and-socket symbols by hand on diagrams only.
930 words, about 5 min2Association Ends, Derived Unions and Uniqueness in a Product-Line Model
Northwind's product-line model has grown to 700 classes. Orders are modelled as Order with three subclasses (ConfiguredOrder, SpareOrder, ServiceOrder), each holding its lines as owned attributes typed OrderLine.
929 words, about 5 min3Regions, History and Deferred Events in a 900-State Claims Machine
An insurer's claims platform models adjudication with a 900-state state machine. Adjudication is a composite state with two orthogonal regions, ADJ (Review, Approve) and FRAUD (Screen, Escalate).
973 words, about 5 min4Profile versus MOF Metamodel for a Clinical Pathway Language
A health authority is standardizing clinical pathway models. The first attempt was a UML profile of 300 stereotypes applied to UML activity and class models; two years on it fails in three ways.
975 words, about 5 min5Making a Claims Pipeline Executable on Two fUML Engines with Alf Editing
A claims pipeline is modelled as 60 UML activities and about 300 actions, and must execute on two different fUML engines and be edited as text by actuarial analysts. Current state: 40 actions are OpaqueActions whose bodies are Java snippets; the claim lifecycle (New, Assessing, Pending, Settled) is a StateMachine; a DecisionNode branches on three guards but has no [else]; and one branch uses an ActivityFinalNode inside a loop body to "return the result early".
910 words, about 5 min