- What the Eight Domains Cover
- Domain Weights at a Glance
- Domain 1: Activities & Actions (20%)
- Domain 2: Basic Structure (16%)
- Domain 3: Interactions (14%)
- Domain 4: StateMachines & Use Cases (13%)
- Domain 5: Components (12%)
- Domains 6-8: Common Behavior, Structured Classifiers, Classification
- Scope Boundaries and Details to Verify
- Sequencing the Domains in Your Plan
- Frequently Asked Questions
- The OMG Certified UML Professional: Intermediate (OCUP) exam is scoped to UML v2.5.1, with UML Foundation as a prerequisite.
- Activities & Actions carries the most weight at 20%, followed by Basic Structure at 16%.
- The first five domains account for 75% of the blueprint, so prioritize them.
- The pinned PDF lists 105 minutes in native-English-speaking countries and 135 minutes elsewhere, subject to its extra-time confirmation condition.
What the Eight Domains Cover
The OMG Certified UML Professional: Intermediate (OCUP) credential tests whether you can read and reason about UML 2 models at a level well beyond basic class and use case diagrams. The exam scope is defined in OMG's "UML 2 Intermediate Exam" PDF, which maps to UML v2.5.1. Rather than testing diagram-drawing in the abstract, it tests your command of the metamodel constructs behind the diagrams: what a construct means, what is legal, and how related constructs interact.
The specification chapters in scope run from Chapter 7 (Constraints, Dependencies, Namespaces, Types and Multiplicity) through Chapter 20 (Information Flows). This guide organizes that material into the eight content areas used across this site. If you are new to the credential itself, start with What Is OCUP Certification? and then return here for the domain-level detail.
One prerequisite deserves emphasis: UML Foundation knowledge is assumed. The intermediate exam does not re-teach basic notation, so if you cannot already distinguish an association from a dependency or a class from an interface at a glance, review that material first. Our OCUP requirements guide covers eligibility and prerequisites in more depth.
Domain Weights at a Glance
The eight domains are not equal. The table below shows the weighting and the main specification areas each domain draws on.
| Domain | Weight | Representative constructs |
|---|---|---|
| Activities & Actions | 20% | Activities, Activity Groups, Control Nodes, Object Nodes, Actions, Expansion Regions, Invocation Actions, Structured Actions |
| Basic Structure | 16% | Constraints, Dependencies, Namespaces, Types, Multiplicity, Packages |
| Interactions | 14% | Communication Diagrams, Fragments, Interactions, Interaction Uses, Lifelines, Messages, Sequence Diagrams |
| StateMachines & Use Cases | 13% | StateMachine topics, ProtocolStateMachines, Use Cases |
| Components | 12% | Components, Artifacts, Nodes, Information Flows |
| Common Behavior | 10% | Events, Behaviors, Intervals and Time |
| Structured Classifiers | 9% | Structured Classifiers, Encapsulated Classifiers, Collaborations, Receptions |
| Classification | 6% | Classifiers, Generalization Sets, Instances, Operations, Properties, Interfaces and Signals |
Treat the construct groupings as a study aid rather than an official mapping; the exam PDF lists constructs by specification chapter, and the domain labels are a convenient way to organize them. For how this weighting translates into difficulty, see How Hard Is the OCUP Exam?
Domain 1: Activities & Actions (20%)
This is the single largest domain and the one most likely to separate prepared candidates from casual ones. It spans Chapters 15 and 16 of the specification: activities with their groups, control nodes and object nodes, plus the many kinds of actions.
Activities, Activity Groups, Control Nodes and Object Nodes
Expect questions that ask what happens at runtime when tokens flow through a diagram, not just what the notation looks like.
- How control nodes (initial, final, decision, merge, fork, join) route tokens, and which combinations are valid or deadlock-prone
- The role of object nodes and how they buffer or constrain tokens moving between actions
- Activity groups such as partitions and interruptible regions, and what each one scopes
- The difference between an activity final node and a flow final node
Actions, Expansion Regions, Invocation Actions and Structured Actions
Chapter 16 covers the building blocks inside activities. Many candidates underestimate it because the notation seems simple while the semantics are not.
- Invocation actions: how call, send and similar actions differ in what they invoke and whether they wait
- Expansion regions and how they process collections, including the distinction between parallel, iterative and stream modes
- Structured actions such as conditional and loop nodes, and how their sections execute
- Pins, inputs and outputs, and how an action's data requirements gate when it can execute
Because this domain is worth a fifth of the exam, schedule it early and revisit it more than once. The token-flow reasoning it demands improves with repeated worked examples rather than one-time reading.
Domain 2: Basic Structure (16%)
Basic Structure covers the foundational modeling vocabulary that every other domain depends on: Chapter 7 (Constraints, Dependencies, Namespaces, Types and Multiplicity) and Chapter 12 (Packages).
Foundational Constructs
These questions often look easy and are routinely missed because of precise-wording traps.
- Multiplicity: lower and upper bounds, and the uniqueness and ordering attributes that determine whether a property is a set, bag, sequence or ordered set
- Constraints: what a constraint can reference, and how it relates to the element it constrains
- Dependencies and their specialized forms, and how to distinguish one from another by intent
- Namespaces and name resolution, including how visibility and imports affect what is accessible
- Packages: package import versus merge, and what each does to the receiving package's contents
Domain 3: Interactions (14%)
Chapter 17 is the source for this domain, and it covers more than sequence diagrams alone. The listed constructs include Communication Diagrams, Fragments, Interactions, Interaction Uses, Lifelines, Messages and Sequence Diagrams.
Reading and Reasoning About Interactions
You should be able to determine which message orderings a diagram permits and which it forbids.
- Combined fragments and their operators, particularly how alternatives, options, loops and parallel regions change the set of valid traces
- Interaction uses and how they reference another interaction, including how gates connect the inside and outside
- Lifelines, execution specifications and how messages attach to them
- Message kinds: synchronous, asynchronous, reply, and the lost and found variants
- How a communication diagram expresses the same interaction as a sequence diagram, and what information each emphasizes
The core skill is trace reasoning: given a diagram, which sequences of events are legal? Practice by enumerating traces by hand for small fragments before attempting larger diagrams.
Domain 4: StateMachines & Use Cases (13%)
This domain pairs Chapter 14 (ProtocolStateMachines and StateMachine topics) with Chapter 18 (Use Cases).
StateMachines
State machine questions test run-to-completion semantics and the details of transitions more than notation.
- Composite states, regions and orthogonality, and how a state configuration is defined
- Pseudostates such as choice, junction, fork, join, history and entry and exit points, and what each does
- Transition triggers, guards and effects, and the order in which exit, effect and entry behaviors execute
- Protocol state machines: how they constrain the order of operation calls without defining behavior, and how they differ from behavioral state machines
Use Cases
Use case content is conceptually lighter but still contains testable rules.
- Include and extend relationships, including extension points and the direction of each relationship
- Actors, subjects and how use cases relate to the system boundary
- Generalization among actors and among use cases
Key Takeaway
Do not let the light conceptual load of use cases tempt you to skip them. Pair each study session on state machines with a short use case review so the smaller topic stays fresh without competing for time.
Domain 5: Components (12%)
The Components domain gathers deployment- and architecture-related material: components themselves from Chapter 11, along with Artifacts and Nodes from Chapter 19 and Information Flows from Chapter 20.
Components, Artifacts, Nodes and Information Flows
- Components as modular units with provided and required interfaces, and how ports and connectors wire them together
- The distinction between a component's internal realization and its external contract
- Artifacts as physical pieces of information and their manifestation of model elements
- Nodes and execution environments, and how artifacts are deployed to them
- Information flows: what they convey, what they abstract, and how they differ from ordinary dependencies
Pay attention to the vocabulary boundaries: a component is a logical modeling unit, an artifact is a physical one, and a node is where artifacts live. Many wrong answers on this domain exploit confusion between those three layers.
Domains 6-8: Common Behavior, Structured Classifiers, Classification
Together these three domains account for 25% of the blueprint. They are smaller individually, but they underpin the larger ones, so skipping them is a mistake.
Domain 6: Common Behavior (10%)
Events, Behaviors, and Time
Drawn from Chapters 8 and 13, this domain covers intervals and time alongside events and behaviors.
- Event kinds: call, signal, change and time events, and how each is detected
- Behaviors as the general concept behind activities, state machines and interactions, including how a behavior is owned and invoked
- Time and interval constructs, including duration and time constraints, and how they annotate a model
Domain 7: Structured Classifiers (9%)
Internal Structure
This domain draws on Chapter 11 and focuses on how classifiers are decomposed into parts.
- Structured classifiers: parts, roles and connectors, and how instances of the whole contain instances of the parts
- Encapsulated classifiers and ports as interaction points
- Collaborations and collaboration uses, including how roles are bound in a particular context
- Receptions and how a classifier declares its readiness to handle a signal
Domain 8: Classification (6%)
Classifiers and Their Features
The smallest domain draws on Chapters 9, 10 and 11 for the classifier-level concepts.
- Generalization sets: disjoint versus overlapping, complete versus incomplete, and how a power type is used
- Instances and instance specifications, and how slots relate to properties
- Operations and properties: derived, read-only, static and redefined features
- Interfaces and signals, and the difference between an interface realization and an interface usage
- Associations and classes, including association ends, navigability and ownership
The 6% weighting can mislead you. Generalization set semantics and interface-versus-signal distinctions recur as background knowledge inside questions from other domains, so a weak grasp here costs more than six percent of your score.
Scope Boundaries and Details to Verify
A few facts about the OMG Certified UML Professional: Intermediate (OCUP) exam are easy to get wrong, so verify them against OMG directly before you commit to a plan.
- Specification version: The exam PDF is tied to UML v2.5.1. Do not substitute material from older UML versions without checking the differences.
- Timing: The PDF states 105 minutes for candidates in native-English-speaking countries and 135 minutes elsewhere, subject to its extra-time confirmation condition. The wording is geographic; do not interpret it as a judgment about any individual's language ability.
- Language availability: OMG's certification page advertises Japanese availability while the pinned PDF lists English. Confirm which language options apply to your sitting.
- Fee and scheduling: The current OMG page lists US$350, and Pearson VUE scheduling is referenced. Whether a member or nonmember distinction applies is unverified, so check at registration. Our OCUP certification cost breakdown and exam dates and scheduling guide explain how to plan around these.
- Question count, passing threshold and renewal: These are unverified here, and OMG does not publicly disclose a pass rate. For what is and is not known, see the OCUP passing score guide and what the pass rate data shows.
Sequencing the Domains in Your Plan
Domain weight should drive the order and the time you give each area, but dependencies between domains matter too. Basic Structure vocabulary supports nearly everything else, so it makes sense to begin there even though Activities & Actions is heavier. One workable sequence:
Basic Structure and Classification
- Multiplicity, constraints, dependencies, namespaces and package import versus merge
- Generalization sets, instances, interfaces and signals
Activities & Actions
- Token-flow tracing through control and object nodes
- Expansion regions, invocation actions and structured actions
Interactions and Common Behavior
- Combined fragment trace enumeration and interaction uses
- Event kinds, behaviors and time constraints
StateMachines, Use Cases, Components and Structured Classifiers
- Pseudostates, transition execution order and protocol state machines
- Components, artifacts, nodes, information flows, ports and collaborations
Integrated review
- Mixed-domain questions that force you to switch constructs mid-session
- Return to your weakest of the first five domains
Adjust the pacing to your own background; a candidate with strong state machine experience might compress Week 5, while someone new to activity semantics may extend Weeks 2-3. For a fuller preparation framework, read the OCUP study guide, and keep the OCUP cheat sheet handy for last-week review. Once you have covered the material, test yourself with scenario-style questions on the OCUP practice test site to find the constructs where your reasoning breaks down.
Remember that independent preparation materials, including everything on this site, are not actual issuer questions or an official mock exam. Use them to build understanding of the constructs, and rely on OMG's published scope document as the authoritative list of what can be tested. If you are weighing whether the effort is justified, the ROI analysis and salary guide discuss the career side, and you can practice with exam-style questions whenever you are ready to check your progress against the domain blueprint.
Frequently Asked Questions
Activities & Actions is the largest at 20%, followed by Basic Structure at 16% and Interactions at 14%. The top five domains together make up 75% of the blueprint, so they deserve the majority of your study time.
The pinned OMG exam PDF is scoped to UML v2.5.1. The scope is organized by specification chapter, from Chapter 7 on constraints, dependencies, namespaces, types and multiplicity through Chapter 20 on information flows.
Yes. UML Foundation is a prerequisite, and the intermediate exam assumes you already know basic notation. Review foundation concepts first, then use the eight domains to structure your intermediate-level preparation.
The pinned PDF lists 105 minutes in native-English-speaking countries and 135 minutes elsewhere, subject to its extra-time confirmation condition. Question count and passing threshold are not confirmed here, so check OMG's current materials before you register.
No. OMG's SysML Model Builder exam PDFs specify SysML v1.2 and serve only as boundary references. Keep your OCUP preparation focused on the UML constructs listed in the Intermediate exam PDF.