OCUP 2 Advanced study plan

Enumerate every UML 2.5 classifier kind (Class, Interface, DataType, Enumeration, PrimitiveType, Association, Component, Node, Artifact, Signal, Actor, UseCase, Collaboration, Activity, Interaction, StateMachine, ProtocolStateMachine, InformationItem) and state one modeling use for each.

Draw a class diagram that applies all seven property attributes (name, type, multiplicity, visibility, isStatic, isReadOnly, isDerived) and all four association-end attributes (navigability, aggregation, composition, multiplicity).

Differentiate the four BehavioralFeature kinds (Operation, Reception, BehavioralFeature specializations) and map which classifier kinds may own each.

Build a stereotype-application table showing how Profile, Stereotype, Extension, and TaggedValue extend the metamodel for a domain-specific model.

Construct a state machine using entry, exit, do, internal transitions, composite states, regions, and history pseudostates for a realistic device controller.

Model an activity with partitions, object flows, pins, expansion regions, and all control node types (initial, final, decision, merge, fork, join, flow final).

Draw a sequence diagram containing synchronous and asynchronous messages, creation and destruction events, combined fragments (alt, opt, loop, par, critical, break), and interaction uses.

Specify the semantics of each diagram kind's notation variants (e.g., communication vs. sequence, timing diagrams) and when each is preferred.

Scale a structural model to 100+ elements using packages, imports, namespace nesting, and dependency relationships, and verify no name collisions.

Apply all constraint mechanisms (OCL constraints, guards, pre/postconditions on operations, invariants) to a class model and distinguish their evaluation points.

Configure a component-and-deployment model with ports, provided/required interfaces, connectors, nodes, and artifact manifestations.

Reconcile model views by tracing one requirement through use case, class, activity, and deployment diagrams without notation drift.

Explain the four MOF meta-levels (M0–M3) and place UML, a UML profile, and a user model on the correct level with justification.

Map each UML metaclass needed for class, state, and activity modeling to its MOF metaclass and inherited features.

Distinguish MOF reflection, extension, and the role of the UML Infrastructure library in metamodel reuse.

Identify which UML elements are defined by composition versus inheritance in the metamodel and predict the modeling consequences.

Describe fUML execution semantics: the token-based activity execution model, event dispatch, and the role of the execution model in the fUML specification.

Trace the fUML subset restriction: list which UML activity and class features are excluded from fUML and why.

Model a small executable activity in fUML terms (initial node, action activation, token flow, final node) and simulate one run by hand.

Explain how fUML relates to UML through the foundational subset and what conformance levels exist.

Explain ALF's position as a textual action language for fUML and its mapping to the fUML action model.

Write ALF snippets covering variable declaration, assignment, invocation, loops, conditionals, and sequence construction, then translate each to its fUML action equivalent.

Identify ALF's scope boundaries (what it cannot express) and the conformance points defined in the ALF specification.

Compare ALF with OCL and with UML action semantics to state which layer each occupies.

Integrate a profile, a metamodel extension, and an fUML execution model in one coherent case study spanning both domains.

Resolve cross-specification conflicts (e.g., stereotype attributes versus MOF properties, ALF actions versus UML actions) with documented decisions.

Design a metamodel for a small domain using MOF constructs and validate it against UML profile constraints.

Produce a conformance checklist that tests a model against UML, MOF, fUML, and ALF rules simultaneously.

Complete a timed 60-question mock exam weighted 50/50 across both domains and score each section separately.

Re-derive from memory the UML element palette, MOF meta-levels, fUML execution rules, and ALF mapping without notes.

Review every missed item, trace it to a specification clause, and write a corrected one-line rule for each.

Compress the entire plan into a two-page final review sheet organized by domain.