The Solution Designer is an individual who provides services related to developing use
case, software architecture, software analysis, and software design models using Unified
Modeling Language Version 2 (UML 2). The Solution Developer is expected to be
knowledgeable of the aspects of the software development lifecycle that relate to
modeling. He or she is expected to be able to conceive and describe the static and the
dynamic aspects of software systems, making use of all UML 2 diagram types.
Certification can be achieved if you have experience with effectively analyzing and
designing software systems and/or hardware/software systems using UML 2 and if your
modeling efforts have included describing your systems using both static diagrams (such
as class and composite structure diagrams) and dynamic diagrams (such as activity,
sequence, and state chart diagrams).
Design vUML 2 certification, candidates must pass 2 tests. To prepare for these
tests, based upon the job role and test objectives, refer to the Recommended
Educational Resources under Core Requirements below.
The test consists of four sections containing a total of approximately 50 multiple-choice questions. The percentages after each section reflect the approximate distribution of the total question set across the sections.
a. The Unified Modeling Language
b. Process and Visual Modeling
c. Analysis & Design Key Concepts
b. Define high-level organization of the model
c. Identify analysis mechanisms
d. Identify key abstractions
e. Create use-case realizations
b. For each Use-Case Realization
1. Find Classes from Use-Case Behavior
2. Distribute Use-Case Behavior to Classes
The test consists of six sections containing a total of approximately 60 multiple-choice
questions. The percentages after each section reflect the approximate distribution of the total
question set across the sections.
a. Identify classes and subsystems
b. Identify subsystem interfaces
c. Update the organization of the Design Model
a. Define the network configuration
b. Allocate processes to nodes
c. Define the distribution mechanism
a. Describe interaction among design objects
b. Simplify sequence diagrams using subsystems
c. Describe persistence-related behavior
d. Refine the flow of events description
e. Unify classes and subsystems
a. Distribute subsystem behavior to subsystem elements
b. Document subsystem elements
c. Describe subsystem dependencies
Now bringing you back...
Does that email address look wrong? Try again with a different email.
This action might not be possible to undo. Are you sure you want to continue?