OCUP 2 certification guide preparing for the OMG certified UML 2.5 professional 2 foundation exam

OCUP 2 Certification Guide: Preparing for the OMG Certified UML 2.5 Professional 2 Foundation Exam both teaches UML® 2.5 and prepares candidates to become certified. UML® (Unified Modeling Language) is the most popular graphical language used by software analysts, designers, and developers to model,...

Descripción completa

Detalles Bibliográficos
Otros Autores: Chonoles, Michael Jesse, author (author)
Formato: Libro electrónico
Idioma:Inglés
Publicado: Cambridge, Massachusetts : Morgan Kaufmann Publishers 2017.
Materias:
Ver en Biblioteca Universitat Ramon Llull:https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009630629906719
Tabla de Contenidos:
  • Front Cover
  • OCUP 2 Certification Guide
  • Copyright Page
  • Contents
  • Foreword
  • Acknowledgments
  • Discount Information
  • 1 What is OCUP 2?
  • 1.1 The OCUP Programs
  • 1.1.1 OMG Certified UML Professional 1
  • 1.1.2 OMG Certified UML Professional 2
  • 1.1.3 Why Does OMG Offer It?
  • 1.1.4 Why Should You Take It?
  • 1.2 The Levels
  • 1.2.1 Foundation Level
  • 1.2.2 Intermediate Level
  • 1.2.3 Advanced Level
  • 1.3 What Do You Get If You Pass?
  • 1.4 Taking the Exam
  • 1.4.1 Signing Up for the Exam
  • 1.5 How to Prepare
  • 1.5.1 Cheating
  • 1.5.2 Coverage Map
  • 1.6 What an Exam Is Like
  • 1.6.1 Exam Structure
  • 1.6.2 Question Structure
  • 1.7 How We Wrote the Examinations
  • 1.7.1 Team
  • 1.7.2 Review Process and Criteria
  • 1.7.3 Beta Review and Criteria
  • 2 What is UML?
  • 2.1 What Does UML Stand for?
  • 2.1.1 How is UML a Language?
  • 2.1.2 How is UML a Modeling Language?
  • 2.1.3 How is UML a Unified Modeling Language?
  • 2.2 UML Goals
  • 2.2.1 The Original Goals of UML
  • 2.2.2 Updated Goals for UML
  • 2.3 What is the Object Management Group (OMG)?
  • 2.3.1 The Standards-Making Process of OMG
  • 2.3.2 The History of UML
  • 2.4 Modeling
  • 2.4.1 What Kind of Modeling
  • 2.4.2 Purposes for UML Modeling
  • 2.4.2.1 Analysis
  • 2.4.2.2 Design
  • 2.4.2.3 Implementation
  • 2.4.2.4 Communication
  • 2.4.3 Principles of Modeling
  • 2.4.3.1 Risk Mitigation
  • 2.4.3.2 Information Hiding and Simplicity
  • 2.4.3.3 Whole-Part Relationships
  • 2.4.3.4 Classification and Generalization
  • 3 Questions for Chapter 2
  • Answers for Chapter 2
  • 4 The Organization of UML
  • 4.1 The UML 2.5 Specification
  • 4.1.1 Target Audience
  • 4.1.2 The Document Layout
  • 4.2 The Language Definition-The Clauses
  • 4.3 The Subclauses
  • 4.4 The Abstract Syntax
  • 4.5 The Layered Metamodel
  • 4.6 Diagrams
  • 4.6.1 Structure Diagrams
  • 4.6.2 Behavior Diagrams.
  • 4.6.3 General Diagram Features
  • 4.6.3.1 Views
  • 4.6.3.2 Diagram Frame and Header
  • 4.6.3.3 Diagram Kind
  • 4.6.3.4 Namespace
  • 4.6.3.5 Comments
  • 4.6.3.6 Constraints
  • 5 Questions for Chapter 4
  • Answers for Chapter 4
  • 6 Objects and Classes
  • 6.1 Finding Objects and Classes
  • 6.1.1 Attributes
  • 6.1.2 Operations
  • 6.1.3 Referring to a Member Feature
  • 6.1.4 Static Features
  • 6.2 Types
  • 6.2.1 Class Versus Datatype
  • 6.2.2 Primitive Types
  • 6.2.3 Enumerations
  • 6.2.4 DataTypes
  • 6.2.4.1 Abstraction
  • 6.3 Modifiers
  • 6.3.1 Derived Properties
  • 6.3.2 Default Value
  • 6.3.2.1 Default Values for Attributes/Properties
  • 6.3.2.2 Default Values for Arguments/Parameters
  • 6.3.3 Protecting from Change
  • 6.3.3.1 ReadOnly
  • 6.3.3.2 Queries
  • 6.3.4 Parameter Direction
  • 6.4 Assigning Value
  • 6.4.1 Literals
  • 6.4.2 Instance Specifications
  • 6.4.3 Expressions
  • 7 Questions for Chapter 6
  • Answers for Chapter 6
  • 8 Packages and Namespaces
  • 8.1 Package Notation
  • 8.1.1 Packages and Their Contents
  • 8.1.2 Diagrams of Packages
  • 8.1.3 Uniform Resource Identifiers
  • 8.2 Packages and Visibility
  • 8.2.1 Package Member Visibility
  • 8.2.2 Inner and Outer Names
  • 8.2.3 Namespaces and Distinguishable Names
  • 8.3 Packages and Their Contents
  • 8.3.1 Package Dependencies
  • 8.3.2 Specific Elements from Other Packages
  • 8.3.2.1 Package Import
  • 8.3.2.2 Element Import
  • 8.3.2.3 Comparison of Package vs Element Import
  • 8.3.2.4 Access
  • 8.3.2.5 Package Dependencies and Cycles
  • 8.3.2.6 Package Merge
  • 8.4 Package Stereotypes
  • 8.4.1 Packages and Models
  • 8.4.2 Miscellaneous Stereotypes of Packages
  • 8.4.2.1 ModelLibrary
  • 8.4.2.2 Framework
  • 8.4.2.3 Profiles
  • 8.4.2.4 Diagrams
  • 9 Questions for Chapter 8
  • Answers for Chapter 8
  • 10 Finishing the Static Model
  • 10.1 Multiplicity.
  • 10.1.1 Representing the Multiplicity of Attributes
  • 10.1.2 Representing Argument Multiplicity
  • 10.1.3 Multiplicity Properties and Collection Types
  • 10.1.3.1 Set
  • 10.1.3.2 Ordered Set
  • 10.1.3.3 Unique
  • 10.1.3.4 Bag
  • 10.1.3.5 Sequence
  • 10.1.4 Discontinuity
  • 10.2 Associations
  • 10.2.1 Attribute and Role Adornments
  • 10.2.2 Reading Associations
  • 10.2.3 Associations and Datatypes
  • 10.2.4 Links and Instances
  • 10.2.5 Composition and Aggregation
  • 10.2.5.1 Composition
  • 10.2.5.2 Aggregation
  • 10.2.5.3 Physical vs Catalog Composition
  • 10.3 Generalization, Specialization, and Inheritance
  • 10.3.1 Reflexive Structures Using Generalization
  • 10.3.2 The Process
  • 10.3.2.1 The Generalization Process
  • 10.3.2.2 The Specialization Process
  • 10.3.3 Polymorphism
  • 11 Questions for Chapter 10
  • Answers for Chapter 10
  • 12 Use Cases
  • 12.1 Finding Use Cases
  • 12.1.1 Naming Use Cases
  • 12.1.2 Actors
  • 12.1.2.1 Human Actors
  • 12.1.2.2 External System Actors
  • 12.1.2.3 Database Actors
  • 12.1.3 Subject
  • 12.1.4 Other Use Cases
  • 12.2 Simplifying Use Cases
  • 12.2.1 Generalization
  • 12.2.2 Include
  • 12.2.3 Extend
  • 12.2.3.1 Using an Extension
  • 12.2.3.2 The «Extend» Notation
  • 12.2.3.3 Extension Points
  • 12.2.4 Owners
  • 12.2.5 Use Case Diagrams
  • 13 Questions for Chapter 12
  • Answers for Chapter 12
  • 14 Behavior: Sequence Diagrams
  • 14.1 Sequence Diagram History
  • 14.2 Lifelines
  • 14.3 Messages
  • 14.3.1 Synchronous Messages
  • 14.3.2 Asynchronous Messages
  • 14.4 Time & Occurrences
  • 14.5 Execution Specification
  • 14.6 Sequence Diagrams
  • 14.7 Practical Sequence Diagrams
  • 15 Questions for Chapter 14
  • Answers for Chapter 14
  • 16 Behavior: Activity Diagrams
  • 16.1 What is an Activity Diagram?
  • 16.1.1 Activity Diagram History
  • 16.1.2 Single Token Diagrams
  • 16.1.3 Concurrent (Multi-Token) Diagrams.
  • 16.1.3.1 Explicit Token Creation
  • 16.1.3.2 Implicit Token Creation: Forking a New Path
  • 16.1.3.3 Multiple Forks
  • 16.1.3.4 Forking vs Spawning
  • 16.1.4 Consuming Tokens
  • 16.1.4.1 Multiple Forks
  • 16.1.4.2 Flow Final
  • 16.1.5 Joining at an Action
  • 16.2 Timers and Timing Events
  • 16.3 Object Flows/Edges
  • 16.4 Advanced Topics
  • 16.4.1 Weights
  • 16.4.2 Stream
  • 16.4.3 Send/Receive Messages/Events
  • 16.4.4 Local Pre/Postconditions
  • 16.5 Activity Diagrams
  • 16.5.1 Activities
  • 16.5.2 Invoking an Activity
  • 16.5.3 Calling an Operation
  • 17 Questions for Chapter 16
  • Answers for Chapter 16
  • 18 Behavior: State Machine Diagrams
  • 18.1 What is a State and State Machine
  • 18.1.1 States and Modes
  • 18.1.2 Differences Between States
  • 18.1.3 Qualitatively Different States
  • 18.1.4 Naming States
  • 18.1.5 Overlapping States
  • 18.1.6 Finding States
  • 18.2 Transitions
  • 18.2.1 Events
  • 18.2.2 Simple State Machine
  • 18.2.3 Guard Conditions
  • 18.2.4 Transition Effect
  • 18.2.5 Transition Syntax
  • 18.2.6 Ongoing Behavior
  • 18.2.6.1 Implicit Behavior
  • 18.2.6.2 Do Behavior
  • 18.2.7 State Setup and Teardown
  • 18.2.8 Exit/Entry Action Equivalents
  • 18.2.9 Completion
  • 18.2.10 Internal Transitions
  • 18.3 State Machine Processing
  • 18.3.1 Run-to-Completion
  • 18.3.2 States and Pseudostates
  • 18.3.3 Types of Transitions
  • 18.3.4 State Diagrams and Machines
  • 18.3.5 Hierarchy of States
  • 18.3.6 States Contours
  • 18.4 State vs Activity Semantics
  • 19 Questions for Chapter 18
  • Answers for Chapter 18
  • Index
  • Back Cover.