OMG UML 2 Certification Fundamental

OMG Certified UML Professional (OCUP) – Fundamental :

Test information:

  •  Exam Number : OMG – OCUP – 100
  • Duration : 90 minutes (80 questions)
  • Min Passing Score : 46
  • Exam Fee : US $200
  • Prerequisite : None 


Overview of the UML diagrams

UML diagram

  1. Structure diagram
    1. Class diagram
    2. Object diagram
    3. Package diagram
    4. Component diagram               
    5. Composite Structure diagram
    6. Deployment diagram
  2. Behavior diagram
    1. Activity diagram
    2. Use case diagram
    3. State Machine diagram
    4. Interaction diagrama.
      1. Sequence diagram
      2. Communication diagram
      3. Interaction overview diagram 
      4. Timing diagram 

 Class Diagrams

  • Package : Classes::Kernel
  • Package : Classes::Dependencies
  • Package : Classes::Interfaces

Basic Concepts

  1. The basis of UML is described in the Kernel package of the metamodel.
  2. The UML class model – Element is Superclass (No Notation)
  3. A relationship is an abstract concept to put elements in relation to one another. (No Notation)
  4. Suplier – Element offers something (Set of Source)
  5. Client –  Element wants something (Set of Target)
  6. Comment – can be annoted to any UML model element.
  7. Namespaces – is a named element that can contain named elements. (Unique by their names)
  8. Package – A packageable element is a named element that can belong directly to a package
  9. Packageable element – Visibility is mandatory.
  10. Element import – Act of importing an element (Alias allowed)
  11. Pakagae import – Act of importing a package (Alias not allowed)
  12. Notation and Semantics – + public, – private, # protected, ~ package
  13. <<import>> : Visibility is public
  14. <<access>> : Visibility is private
  15. Typed Element – is a named element that can have a type.
  16. Typed Element – e.g attributes & parameters are typed elements
  17. Type – specifies a set of values for a typed element.
  18. Type – e.g simple data types and classes are types.
  19. Both Type and Typed element are abstract classes in the metamodel.
  20. Both Type and Typed element have no properties
  21. Multiplicity element- interval of + integers to specify allowable cardinalities.
  22. Cardinality – is a concrete number of elements in a set.
  23. Notation of Multiplicity is either a single number or a value range.
  24. Multiplicity – eg 0..1 , 1, * , 1..*, 5..3, -1..0, 3+5..7+1
  25. Value Spec – indicates one or several values in a model
  26. Value Spec – eg simple, mathematical expr (4+2) & expr with values (Int::Max_INT)
  27. Value Spec – class model used to create tree type expr -composite pattern
  28. Constraints – is an expr that contains the sematics of an element and it must always be true.
  29. Constraints – can be formal expr (OCL) or a semiformal or human lang formulation.
  30. Constraints – Notation & Sematics – written between curled brackets
  31. Constraints – written directly after a textual element or within a comment symbol.
  32. Constraints – can have names.
  33. Constraints – Syntax – ‘{‘ [<name> ‘:’] < Boolean expression > ‘}’
  34. Constraints – eg radius:int {radius >0}, {Salary:self.salary > assitant.salary},  {xor}
  35. Instance Spec – a concrete instance in the modeled system.
  36. Instance and object are used synonymosly
  37. Slot – represents for a struture element of an instance spec such as an attr value of an object.
  38. Instance Spec – can be incomplete, don’t have to specify all values of attributes
  39. Classifier – is a abstract base class that classifies the instances with regard to their features.
  40. Classifier – is a namespace and a type, and it can be generalized
  41. Classifier – eg class, component and use case
  42. Classifier – associates a set of features – operations & attributes
  43. Classifier – Notation – rectangle that contains name with name of subclass in guillemets above it.
  44. Classifier – abstract if its desc is incomplete. (no instances can be created)
  45. Classifier – Abstractness is a feature of classifiers
  46. Classifier – Names of abstract classifiers are written in italics GeomFigure {abstract}
  47. Features – desc a structural or behavioral characteristic of a classifier’s instances.
  48. Structural Feature – is an abstract metaclass, which desc a typed structure of instance of a classifier. eg property attribute {readonly} {unrestricted}
  49. Behavioral Feature – is an abstract metaclass, which means that an instance of a classifier can respond to requests by calling certain behavior. eg operation
  50. Behavioral Feature – can throw an exception. parameters can be passed/returned
  51. Parameter – is the spec of an argument that is passed/returned by behavioral feature
  52. Parameter – has a type, a multiplicity and a direction. (optionally – state a default value and a name)
  53. Parameter – directions si specified by keywords – in, out, inout or return
  54. Parameter – directions default value is ‘in’
  55. in – Caller passes the param value to the behavior
  56. out – behavior passes the param value to the caller
  57. inout – Caller first passes the param value to the behavior, which ret it to caller
  58. Return – llr to out, except return explicitly specifies the return values of behavior
  59. Notation – Synt [direction ] name : type [multiplicity ] [= default] [{property string}]
  60. Property String for a param can be one of values known for properties {ordered} & {nonunique}


IBM UML Certification Guide

UML Exam Part 1 (Analysis)

Test 000-833: Object Oriented Analysis and Design – Part 1 (Analysis)

Test information:
* Number of questions: 50
* Time allowed in minutes: 75
* Required passing score: 60%

 Cost : 200 USD (Prometric Test Center)

Section 1: UML and the Modeling Process (20%)
   1. The Unified Modeling Language
   2. Process and Visual Modeling
   3. Analysis & Design Key Concepts

Section 2: Concepts of Object Orientation (40%)
   1. Relationships
   2. Class
   3. Polymorphism
   4. Interface
         1. Provided
         2. Required
   5. Structured Classes & Ports

Section 3: Architectural Analysis (20%)
   1. Key Concepts
   2. Define high-level organization of the model
   3. Identify analysis mechanisms
   4. Identify key abstractions
   5. Create use-case realizations

Section 4: Use Case Analysis (20%)
   1. Supplement the Use-Case Description
   2. For each Use-Case Realization
         1. Find Classes from Use-Case Behavior
         2. Distribute Use-Case Behavior to Classes
   3. For each resulting analysis class
         1. Describe Responsibilities
         2. Describe Attributes and Associations
         3. Qualify Analysis Mechanisms
   4. Unify Analysis Classes

IBM UML Exam Part 2

Test 000-834: Object Oriented Analysis and Design – Part 2 (Design)


Test information:

  • Number of questions: 60
  • Time allowed in minutes: 75
  • Required passing score: 60%
  • Test languages: English

Section1: Identify Design Elements (17%)
   1. Identify classes and subsystems
   2. Identify subsystem interfaces
   3. Update the organization of the Design Model

Section 2: Identify Design Mechanisms (8%)
   1. Categorize clients of analysis mechanisms
   2. Document architectural mechanisms

Section 3: Distribution (17%)
   1. Define the network configuration
   2. Allocate processes to nodes
   3. Define the distribution mechanism

Section 4: Use Case Design (22%)
   1. Describe interaction among design objects
   2. Simplify sequence diagrams using subsystems
   3. Describe persistence-related behavior
   4. Refine the flow of events description
   5. Unify classes and subsystems

Section 5: Subsystem Design (11%)
   1. Distribute subsystem behavior to subsystem elements
   2. Document subsystem elements
   3. Describe subsystem dependencies

Section 6: Class Design (25%)
   1. Create Initial Design Classes
   2. Define Operations
   3. Define Methods
   4. Define States
   5. Define Attributes
   6. Define Dependencies
   7. Define Associations
   8. Define Internal Structure
   9. Define Generalizations
  10. Resolve Use-Case Collisions
  11. Handle Nonfunctional Requirements in General

By identityguru Posted in UML

IBM UML Certification – Section 1

Section 1: UML and the Modeling Process (20%)

  1. The Unified Modeling Language
  2. Process an Visual Modeling
  3. Analysis and Design Key Concepts

The Unified Modeling Language (UML)

The UML is a language for specifying, visualizing, constructing, and documenting the artifacts of software systems, as well as for business modeling and other non-software systems.

Analysis and Design Concepts

Analysis emphsizes an investigation of the problem and requirements, rather than a solution. For example, If a new computerized library information system is desired,how will it be used?

Requiredment Analysis : An Investigation of the requirements

Object Analysis : An Insestigation of the domain objects

Design emphasizes a conceptual solution that fulfills the requirements, rather than its implementation. For example, a description of a database schema and software objects.

Object-Oriented Analysis and Design

During, object-oriented analysis, there is an emphasis on finding and describing the objects or concepts in the problem domain. For example, in the case of the library information system, some of the concepts include Book, Library, and Patron.

During object-orientied design, there is an emphasis on defining software objects and how they collobrate to fulfill the requirements. For example, in the library system, a Book software object may have a title attribute and a getChatpter method.

Finally, during implementation, design objects are implemented, such as a Book class in Java

public class Book{
private String tile;
   public Chapter getChapter(int pageNumber){....}