OCUP 2 Intermediate study materials
OCUP 2 Intermediate study resources

OCUP 2 Intermediate study plan

OCUP 2 Intermediate · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

UML elements and attributes of structures used in complex and larger system models

  • Enumerate the UML 2.5 structural classifiers (Class, Interface, DataType, Enumeration, Component, Artifact, Node, Association, etc.) and their metaclass relationships

  • Diagram a complex system with at least 15 classes using generalization, association classes, and n-ary associations

  • Specify multiplicities, navigability, and role names on associations in a class diagram

  • Distinguish aggregation vs. composition with concrete lifecycle examples

Your checkpoint

A class diagram of a library system (20+ classes) with a written legend explaining each structural notation used

Week 2

UML elements and attributes of structures used in complex and larger system models

  • Model composite structure with ports, connectors, and collaboration roles

  • Apply property stereotypes (<>, <>, <>) in a class hierarchy

  • Construct a component diagram showing provided and required interfaces

  • Use deployment diagrams with nodes, artifacts, and communication paths

Your checkpoint

A composite structure and component diagram for a payment processing subsystem, with annotations for each port and connector

Week 3

Designing and generating interoperating modules

  • Define module boundaries using packages and package merge semantics

  • Model interface contracts with pre/postconditions via OCL constraints

  • Create a component model that exposes only interfaces and hides internal classes

  • Specify dependency and realization relationships between modules

Your checkpoint

A package diagram and interface specification document for a three-module e-commerce application

Week 4

Designing and generating interoperating modules & Improving upon other models

  • Generate class skeletons from a UML model using a forward-engineering tool (e.g., Eclipse Papyrus or Visual Paradigm)

  • Reverse-engineer existing code into a UML class diagram and compare with the original design

  • Identify and refactor at least three design smells (e.g., cyclic dependencies, leaky abstractions) in a provided model

  • Apply the Strategy and Observer patterns in a module design and document the UML representation

Your checkpoint

A refactored module diagram with a before/after comparison and a generated code stub for one module

Week 5

Improving upon other models

  • Review a peer's UML model for consistency and completeness using a checklist

  • Improve an existing model by adding missing constraints, multiplicities, and stereotypes

  • Reorganize a flat class diagram into packages with clear dependencies

  • Document model changes with rationale in a model review log

Your checkpoint

A revised model (diagrams + change log) of a given case study, with a review checklist showing all issues found and resolved

Week 6

Improving upon other models & Explaining the full UML diagram suite to model users

  • Explain the purpose and notation of all 14 UML diagram types to a non-expert audience

  • Create a one-page cheat sheet mapping each diagram type to its primary use

  • Present a 10-minute walkthrough of a complex model to a simulated stakeholder

  • Compare behavioral diagrams (activity, state machine, sequence, communication) with examples

Your checkpoint

A presentation slide deck (or cheat sheet) covering all diagram types with a recorded 10-minute explanation

Week 7

Explaining the full UML diagram suite to model users

  • Explain the semantics of timing, interaction overview, and protocol state machine diagrams

  • Demonstrate how to choose the right diagram for a given scenario (e.g., real-time vs. business process)

  • Answer stakeholder questions about model elements using precise UML terminology

  • Create a glossary of UML terms with examples for each

Your checkpoint

A glossary of 30 UML terms with example diagrams, plus a written response to five stakeholder questions

Week 8

UML elements and attributes of structures used in complex and larger system models & Designing and generating interoperating modules & Improving upon other models & Explaining the full UML diagram suite to model users

  • Complete a timed mock exam covering all domains with a score of at least 80%

  • Review incorrect answers and map them to specific UML specification sections

  • Revisit weak areas identified in the mock exam with targeted diagram exercises

  • Summarize key takeaways and create a personal exam-day checklist

Your checkpoint

Mock exam score report and a personalized study summary with action items for final review

Milestones

Week 2: Can draw a class diagram with advanced structural features (association classes, qualifiers, composite structure) without references

Week 4: Successfully generate code from a UML model and reverse-engineer code back to UML, explaining each step

Week 6: Deliver a clear 10-minute explanation of all UML diagram types to a peer, answering at least 5 questions correctly

Week 8: Score 80% or higher on a full-length practice exam covering all four domains