- What This Cheat Sheet Covers (and What It Doesn't)
- Exam Logistics at a Glance
- The Eight Domains and Their Weights
- Activities and Actions: The Heaviest Block
- Basic Structure: Constraints, Types, Namespaces
- Interactions: Lifelines, Messages, Fragments
- StateMachines and Use Cases
- Components and Structured Classifiers
- Common Behavior and Classification
- Confusable Pairs Worth Memorizing
- Scheduling the Domains Across Your Prep
- Boundary Notes: SysML, Foundation, Language
- Frequently Asked Questions
- Activities & Actions carries 20% of the blueprint, the largest single domain; Basic Structure follows at 16%.
- The exam targets UML 2 Intermediate scope per the OMG PDF, based on UML v2.5.1.
- PDF timing is 105 minutes in native-English-speaking countries and 135 minutes elsewhere, subject to the extra-time condition.
- The current page lists US$350; question count, passing score, and renewal rules are unverified.
What This Cheat Sheet Covers (and What It Doesn't)
This page is a compressed review of OMG Certified UML Professional: Intermediate (OCUP), the Object Management Group credential that tests intermediate-level UML 2 knowledge. It is not a substitute for the issuer's own scope document, and it is independent preparation material: nothing here is an actual exam question or an official mock exam. If you are still orienting yourself on the credential itself, start with What Is OCUP Certification? and come back once the basics are settled.
The scope reference is the UML 2 Intermediate Exam PDF published by OMG, which is pinned to UML v2.5.1. Everything below is organized around the chapters that PDF lists, because those chapters are what you will be measured against. Treat the PDF as the authority and this cheat sheet as the memory aid.
Exam Logistics at a Glance
Some logistics are firmly documented, and some are not. Knowing which is which saves you from planning around rumors. For a fuller breakdown of each item, see OCUP Certification Cost 2026: Complete Pricing Breakdown and OCUP Exam Dates 2026: Testing Windows, Deadlines & Scheduling.
| Item | What is documented | Status |
|---|---|---|
| Issuer | Object Management Group (OMG) | Confirmed |
| Scope document | UML 2 Intermediate Exam PDF, UML v2.5.1 | Confirmed |
| Prerequisite | UML Foundation | Confirmed |
| Duration | 105 minutes (native-English-speaking countries); 135 minutes elsewhere, subject to the PDF's extra-time confirmation condition | Confirmed in PDF |
| Fee | US$350 listed on the current page; member vs. nonmember pricing not verified | Partly verified |
| Scheduling | Pearson VUE is referenced | Referenced |
| Question count | Not verified | Unverified |
| Passing threshold | Not verified | Unverified |
| Renewal rules | Not verified | Unverified |
| Pass rate | Not publicly disclosed | Not published |
Two further items deserve a double-check. First, the current OMG page advertises Japanese availability while the pinned PDF lists English, so verify the exam language available to you at registration. Second, because the passing threshold and question count are unverified, avoid any source that quotes a precise cut score as fact. Our write-up on OCUP Passing Score 2026 explains how to reason about this uncertainty, and OCUP Pass Rate 2026: What the Data Shows covers why no pass rate can be cited.
The Eight Domains and Their Weights
The blueprint splits into eight weighted domains. Use the weights to decide where your hours go, but remember the domains overlap heavily in practice: an activity question may lean on constraints, and an interaction question may assume you understand classifiers.
| Domain | Weight | Primary PDF chapters |
|---|---|---|
| 1. Activities & Actions | 20% | Ch. 15, Ch. 16 |
| 2. Basic Structure | 16% | Ch. 7, Ch. 9, Ch. 12 |
| 3. Interactions | 14% | Ch. 17 |
| 4. StateMachines & Use Cases | 13% | Ch. 14, Ch. 18 |
| 5. Components | 12% | Ch. 11, Ch. 19 |
| 6. Common Behavior | 10% | Ch. 13, Ch. 10 |
| 7. Structured Classifiers | 9% | Ch. 11 |
| 8. Classification | 6% | Ch. 9 |
The chapter mapping above is an organizing aid built from the topic lists in the scope PDF, not an official crosswalk, so use it to group your reading rather than to predict question distribution. A deeper treatment lives in OCUP Exam Domains 2026: Complete Guide to All 8 Content Areas.
Activities and Actions: The Heaviest Block
At 20%, this domain deserves the most review time. It draws on Chapter 15 (Activities, Activity Groups, Control Nodes, Object Nodes) and Chapter 16 (Actions, Expansion Regions, Invocation Actions, Structured Actions).
Activities, Groups, Control Nodes, Object Nodes
Be able to read an activity diagram and state exactly what tokens do at each node.
- Control nodes: initial, final (activity vs. flow), decision, merge, fork, join. Know that a join synchronizes concurrent flows while a merge does not.
- Object nodes: how typed pins and object flows carry data, and how buffering behavior differs from simple pass-through.
- Activity groups: partitions (swimlanes) and interruptible regions, and what they do and do not change about execution semantics.
- Distinguish control flow from object flow and recognize when an edge is guarded.
Actions and Their Families
Chapter 16 is broad, so memorize the families rather than every individual action.
- Invocation actions: call behavior, call operation, send signal, and how synchronous and asynchronous invocation differ.
- Expansion regions: iterative, parallel, and streaming modes, and how input and output collections map to element-wise processing.
- Structured actions: conditional and loop nodes, and how their test, body, and setup sections are organized.
- Pins: input vs. output, and how multiplicity on pins governs whether an action can fire.
Questions in this area reward careful reading of token flow. A common failure pattern is knowing the notation but misjudging when an action is enabled. If you want to gauge how this domain feels under time pressure, the OCUP practice test lets you drill token-flow scenarios repeatedly.
Basic Structure: Constraints, Types, Namespaces
Basic Structure (16%) pulls from Chapter 7 (Constraints, Dependencies, Namespaces, Types and Multiplicity), Chapter 9 (Classifiers, Generalization Sets, Instances, Operations and Properties), and Chapter 12 (Packages).
Chapter 7 Essentials
These are the foundation constructs the rest of the exam leans on.
- Multiplicity: lower and upper bounds, plus the ordered and unique flags, and what each combination means for a collection.
- Constraints: what a constraint is attached to, and how it relates to the element it constrains.
- Dependencies: usage, abstraction, and realization flavors and what each communicates.
- Namespaces: how names resolve, ownership vs. membership, and visibility.
Chapter 9 and Chapter 12 Essentials
Classifier-level detail and package mechanics.
- Generalization sets: disjoint vs. overlapping, complete vs. incomplete, and the power-type idea.
- Properties and operations: derived properties, read-only, static features, and query operations.
- Instances: how instance specifications relate to the classifiers they instantiate.
- Packages: package import vs. package merge, and how each affects element visibility.
Interactions: Lifelines, Messages, Fragments
Interactions (14%) maps to Chapter 17: Communication Diagrams, Fragments, Interactions, Interaction Uses, Lifelines, Messages, and Sequence Diagrams. Chapter 8 (Intervals and Time) also supports timing-related reading here.
- Messages: synchronous, asynchronous, reply, create, and delete, and what the arrowhead and line style signify.
- Combined fragments: know the operators and their behavior. Alt, opt, loop, par, break, and neg are the ones that most often trip candidates.
- Interaction uses: how a reference fragment points to another interaction, and what gates do at the boundary.
- Communication diagrams: same semantics as sequence diagrams but expressed through numbered messages on links. Be able to translate between the two forms.
- Intervals and time: duration and time constraints, observations, and how they annotate message timing.
StateMachines and Use Cases
This 13% domain combines Chapter 14 (ProtocolStateMachines and StateMachine topics) with Chapter 18 (Use Cases).
StateMachine Topics
Focus on execution semantics, not just diagram syntax.
- Regions and orthogonality: how concurrent regions run inside a composite state.
- Transitions: triggers, guards, effects, and the difference between external, internal, and local transitions.
- Pseudostates: initial, choice, junction, fork, join, history (shallow vs. deep), entry and exit points.
- Entry, exit, and do behaviors, and the order they execute when a transition crosses state boundaries.
- ProtocolStateMachines: how they constrain legal operation sequences on a classifier rather than describing its internal behavior.
Use Cases
Smaller in notation but easy to misread.
- Include vs. extend: include is mandatory reuse of a base-use-case sub-behavior; extend is conditional, with extension points.
- Actors and subjects: what lies inside versus outside the subject boundary.
- Generalization among actors and among use cases.
Components and Structured Classifiers
Components (12%) and Structured Classifiers (9%) overlap through Chapter 11 and are best studied together, with Chapter 19 (Artifacts and Nodes) and Chapter 20 (Information Flows) rounding out the deployment and flow side.
Components, Interfaces, and Deployment
Know how provided and required interfaces wire together.
- Provided vs. required interfaces: ball-and-socket notation and what connecting them implies.
- Component internals: realizing classifiers and how a component exposes behavior through ports.
- Artifacts and nodes: an artifact is a physical piece of information; a node is where it is deployed. Know the manifestation relationship between artifacts and the elements they implement.
- Information flows: abstract movement of information between elements, distinct from control or object flow in activities.
Structured Classifiers and Collaborations
Internal structure is a recurring theme.
- Parts, ports, and connectors: how an encapsulated classifier hides its internals behind ports.
- Collaborations and collaboration uses: roles bound to parts to describe a pattern of cooperation.
- Receptions: declarations that a classifier can react to a given signal.
- Delegation connectors versus assembly connectors.
Common Behavior and Classification
Common Behavior (10%) centers on Chapter 13 (Events and Behaviors) with support from Chapter 10 (Interfaces and Signals). Classification (6%) is the smallest domain, drawing mainly on Chapter 9 classifier concepts. Do not skip it: a small weight still represents real questions.
- Events: call events, signal events, change events, and time events, and how each triggers behavior.
- Behaviors: how a behavior relates to the classifier that owns it, and what makes a behavior reentrant or not.
- Signals vs. operations: a signal is an asynchronous communication; an operation call is typically synchronous. Receptions connect the two.
- Interfaces: contract declarations that classifiers realize, and the difference between realizing and merely using one.
- Classification: how classifiers, instances, and generalization sets relate when an element can be typed in more than one way.
Confusable Pairs Worth Memorizing
Intermediate-level questions often turn on distinguishing two concepts that look alike. This table is the part of the cheat sheet worth rereading the night before.
| Pair | The distinction |
|---|---|
| Fork vs. decision | Fork splits into concurrent flows; decision chooses exactly one outgoing path. |
| Join vs. merge | Join waits for all incoming flows; merge passes through whichever arrives. |
| Activity final vs. flow final | Activity final ends the whole activity; flow final ends only one flow. |
| Include vs. extend | Include is mandatory sub-behavior; extend is conditional and uses extension points. |
| Package import vs. merge | Import makes elements accessible; merge combines package contents. |
| Shallow vs. deep history | Shallow remembers one level of the composite state; deep remembers the full nested configuration. |
| Assembly vs. delegation connector | Assembly links peer parts; delegation routes a port to an internal part. |
| Signal vs. operation | Signal is asynchronous communication; operation is a callable feature. |
| Artifact vs. node | Artifact is the deployed information; node is the execution environment. |
| Disjoint vs. overlapping | Generalization set property: whether an instance may belong to more than one subclass. |
Scheduling the Domains Across Your Prep
Sequence matters because later domains reuse earlier vocabulary. Put structural constructs first, behavior next, and deployment and flow last. For a fuller roadmap, see OCUP Study Guide 2026: How to Pass on Your First Attempt.
Basic Structure and Classification
- Chapters 7, 9, and 12: multiplicity, constraints, generalization sets, packages.
- Why first: every other domain assumes this vocabulary.
Activities & Actions
- Chapters 15 and 16: token flow, control and object nodes, expansion regions.
- Why now: it is 20% of the blueprint, so give it unhurried time.
Interactions and StateMachines & Use Cases
- Chapters 17, 14, and 18: fragments, history pseudostates, include vs. extend.
Components, Structured Classifiers, Common Behavior
- Chapters 10, 11, 13, 19, and 20: ports, connectors, events, artifacts, information flows.
- Finish with timed practice across all eight domains.
Four weeks is a framing device, not a requirement. If UML Foundation is not yet solid, add time before Week 1. Eligibility and prerequisite details are covered in OCUP Requirements 2026: Eligibility, Prerequisites & How to Qualify, and if you are weighing effort against reward, How Hard Is the OCUP Exam? gives a realistic picture.
Boundary Notes: SysML, Foundation, Language
Three boundaries are worth stating plainly so they do not contaminate your preparation.
- UML Foundation is a prerequisite. The intermediate exam builds on Foundation-level knowledge, so gaps there will surface here.
- SysML is out of scope. OMG publishes SysML Model Builder Fundamental and Intermediate PDFs, but they specify SysML v1.2. Use them only to understand where the UML credential ends. Do not merge SysML material into your UML study, since the notation and constructs differ.
- Language availability needs verification. The pinned PDF lists English, while the current OMG page advertises Japanese. Confirm which language your exam delivery supports before you schedule.
Key Takeaway
Scope discipline is a study skill. Anchor everything to the UML v2.5.1-based Intermediate PDF, keep SysML v1.2 sources out of your notes, and treat any claimed cut score or question count as unverified until OMG states it.
Before you commit, it also helps to think about career payoff. Our pieces on whether the OCUP certification is worth it and on OCUP jobs cover where UML modeling skills tend to matter, without inventing salary numbers. When you are ready to test yourself, head to the OCUP Exam Prep practice tests and work through all eight domains.
Frequently Asked Questions
The OMG scope PDF lists 105 minutes in native-English-speaking countries and 135 minutes elsewhere, subject to its extra-time confirmation condition. The wording is geographic, so confirm your eligibility for the longer window with OMG or Pearson VUE rather than assuming.
Activities & Actions at 20% is the largest, followed by Basic Structure at 16% and Interactions at 14%. Prioritize by weight, but do not neglect Classification at 6%, since every domain contributes to your score.
Neither the question count nor the passing threshold is verified in the sources used for this cheat sheet. Check OMG's current documentation before relying on any figure, and see our passing score guide for how to plan around the uncertainty.
The current OMG page lists US$350. Whether member and nonmember prices differ is not verified, so confirm the exact amount at registration. Scheduling references Pearson VUE.
No. SysML Model Builder credentials are separate and specify SysML v1.2. The OCUP scope is UML 2 Intermediate based on UML v2.5.1, so keep SysML-specific material out of your preparation.