E X A M   D I F F I C U L T Y • Master CIW Enterprise Dev Articles • Discussion Board Rate Exam DifficultyVery EasyEasyAverageHardVery Hard

CIW’s exam 1D0-538, “CIW Object-Oriented Analysis and Design with UML” is a requirement for the Master CIW Enterprise Developer certification.

It is designed for candidates who know “language theory of object-oriented programming models such as Unified Modeling Language (UML).” These candidates typically fulfill these roles: application developers, programmers, enterprise developers, and Web developers. The prerequisites for this exam are: 1) to fill out the on-line CIW Certification Agreement; and 2) to hold the CIW Associate certification.
CIW also recommends but does not require that “students seeking Master CIW Enterprise Developer status take (and pass) the CIW Web Languages (JavaScript Fundamentals and Perl Fundamentals), CIW Application Developer and Sun/jCert Java Programmer exams prior to taking the Object-Oriented Analysis and Design with UML (CIW 1D0-438 or 1D0-538) exam.”

This exam costs $175 USD and may be taken from Pearson Vue or Thomson Prometric.

The exam is form-based multiple choice. There are 55 questions and the exam has a duration of 135 minutes.

The topics covered by this exam include:

• Apply iterative and incremental processes
• Schedule project activities based on use cases
• Trace requirements both forward and backward through OOAD artifacts
• Utilize use cases to drive other project activities
• Apply appropriate OOAD activities to a given situation, based on strengths and weaknesses
• Control and coordinate interfaces between packages
• Organize project team responsibilities based on OOAD artifacts
• Identify skills and resources needed to write use cases
• Identify actors for a system
• Identify use cases from a requirements document and/or domain expert, and extract business rules for a domain
• Develop and interpret a use case model using UML notation
• Write use cases that focus on a problem domain
• Write use cases using terminology of a target audience
• Derive subsequent OOAD artifacts from use cases
• Use a user interface prototype for customer feedback when appropriate
• Develop view-model-persistence layered architectures and identify the ways in which layers should interact
• Use package diagrams when appropriate, creating and interpreting contractual interfaces and dependencies between packages
• Use cohesion and coupling effectively when grouping classes into packages
• Use deployment diagrams effectively
• Apply brokering to build flexible systems
• Identify issues related to scalability, performance, transactions, and concurrency
• Identify domain objects, services, attributes and their relationships using different techniques, including parts. Determine when a new class is needed
• Select appropriate names for classes and methods
• Describe the business concept and role that each class represents in a domain model
• Develop and interpret UML class diagrams, including effective use of aggregation, generalization and delegation
• Effectively interpret and develop associations in class diagrams, including stereotypes, qualified associations, cardinality of associations, and association classes
• Maintain encapsulation of attributes and visibility of operations effectively
• Recognize and exploit polymorphism
• Create, interpret and exploit interfaces
• Interpret class diagrams from different perspectives, including subclassing and subtyping
• Create and interpret CRC cards as appropriate
• Focus on behavior while modeling a domai
n
• Include an appropriate level of detail in diagrams
• Effectively assign responsibilities to appropriate classes
• Develop UML interaction diagrams (sequence and collaboration) to satisfy requirements
• Interpret interaction diagrams, including the use of iterations, conditionals and concurrency
• Recognize complexities early in a project, and resolve them in an iterative and incremental fashion
• Determine when to use state diagrams
• Develop and interpret UML state diagrams, including use of events, guards, actions, and super state
• Determine when to use activity diagrams
• Develop and interpret UML activity diagrams, including concurrency, iterations, and conditionals
• Design for reuse
• Given its definition, apply a pattern
• Refactor classes to distribute responsibilities and behavior
• Carry OOAD artifacts forward into implementation
• Resolve implementation issues and update OOAD artifacts