Get in Touch

award icon svg Certificate

 Duration 21 hours

Course Outline

Introduction

  • Exam information for government professionals
  • Coverage table for government use
  • OMG Certified Professionals Directory for government reference
  • Taking the exam (online or at a test center) for government participants

Why We Model

  • The value of modeling in government operations
  • When to model for government projects
  • When not to model for government initiatives
  • Abstraction in government systems design
  • MDA introduction for government applications
  • Domain model for government sectors
  • Model Value Analysis for government decision-making

The Class Diagram

Common Structure

  • Type for government systems
  • Dependency in government contexts
  • Namespace for government applications
  • VisibilityKind (public, private, protected) for government use
  • MultiplicityElement for government data models
  • Constraint for government compliance
  • Comment for government documentation

Simple Classifiers

  • PrimitiveType for government data types
  • DataType for government information systems
  • Enumeration for government standards
  • EnumerationLiteral for government classifications
  • Interface for government interoperability
  • InterfaceRealization for government integration
  • Signal for government communications
  • Reception for government alerts

Structured Classifiers

  • Association for government relationships
  • Class for government objects

Classification

  • Generalization for government hierarchies
  • Feature for government attributes
  • Structural Feature for government components
  • Behavioral Feature for government functions
  • Property for government characteristics
  • Operation for government processes
  • Parameter for government inputs and outputs
  • AggregationKind (Composition, Aggregation) for government structures

Values

  • LiteralBoolean for government boolean values
  • LiteralInteger for government numerical data
  • LiteralReal for government floating-point numbers
  • LiteralUnlimitedNatural for government non-negative integers
  • LiteralNull for government undefined values
  • LiteralString for government text data
  • Opaque Expression for government custom expressions

The Object Diagram

  • InstanceSpecification for government instances
  • Slot for government attribute values

The Package Diagram

Packages

  • Package for government modules
  • PackageImport for government integration

The Use Case Diagram

Use Cases

  • UseCase for government scenarios
  • Actor for government roles
  • Include for government interactions

The Activity Diagram

Activities

  • Activity for government processes
  • ActivityFinalNode for government process termination
  • ActivityParameterNode for government input and output parameters
  • ControlFlow for government control sequences
  • InitialNode for government process initiation
  • DecisionNode for government decision points
  • FlowFinalNode for government flow termination
  • ForkNode for government parallel processes
  • JoinNode for government process convergence
  • MergeNode for government decision merging
  • ObjectFlow for government data movement
  • ObjectNode for government data storage

Actions

  • Action for government tasks
  • CallBehaviorAction for government behavior calls
  • CallOperationAction for government operation calls
  • SendSignalAction for government signal sending
  • AcceptEventAction for government event handling
  • Pin for government data points
  • InputPin, OutputPin for government input and output parameters
  • OpaqueAction for government custom actions

The Sequence Diagram

Interactions

  • Interaction for government interactions
  • OccurrenceSpecification for government event occurrences
  • ExecutionSpecification for government execution details
  • ExecutionOccurrenceSpecification for government execution events
  • DestructionOccurrenceSpecification for government object destruction
  • Lifeline for government object lifetimes
  • Message for government communications
  • MessageOccurrenceSpecification for government message occurrences
  • MessageSort for government message types
  • MessageEnd for government message endpoints

Common Behavior

  • CallEvent for government call events
  • SignalEvent for government signal events
  • Trigger for government event triggers
  • OpaqueBehavior for government custom behaviors

The State Machine Diagram

State Machines

  • StateMachine for government state management
  • State for government states
  • Transition for government state changes
  • Pseudostate: choice, junction, initial for government decision points
  • FinalState for government final states

Requirements

A foundational understanding of object-oriented concepts or basic UML knowledge is required for government projects to ensure effective design and development processes.

Number of participants


Price per participant

Testimonials (7)

Upcoming Courses

Related Categories