Course Outline

Best Practices

  • Addressing the Software Crisis
  • Best Practices in Software Development for Government
    • Iterative Development
    • Management Requirements
    • Component-Based Architecture
    • Visual Modeling
    • Quality Verification
    • Change Management

RUP (Rational Unified Process)

  • Characteristics of RUP for Government
  • Two Dimensions of RUP
  • UML for RUP

Create an Object Model

  • Using UML 2 to Represent the Model
    • The Object Model
  • Practical Analysis of Use Case Specifications for Government
    • Actor
    • Use Case
    • Association
    • Include and Extend Relationships

Some Object-Oriented Concepts in Practice for Government

  • Abstraction
  • Encapsulation
  • Generalization
  • Polymorphism

The System Architecture for Government

  • Mapping the Structure and Behavior of the System
    • Two Categories of UML Diagrams
    • Modeling the Relationship Between Structure and Behavior
    • Different Levels of Modeling Behavior
  • Mapping Class Analytical Design Elements for Government
    • Refinement Relationships
    • Building Strong Relationships Between Analysis and Design Phases
  • Modeling Design Classes for Government
    • Class
    • Association
    • Enumeration
    • Forward/Reverse Engineering
  • Subsystem Design for Government
    • Component
    • Delegation Relationship
    • Connector Assembly
  • Description of Concurrency Aspects in System Architecture
    • Examples of Activity Diagrams, Sequence Diagrams, and State Machine Diagrams
  • Description of Distributed System Architecture Aspects for Government
  • Different Perspectives on Architecture Description for Government

Requirements

Basic knowledge of the commonly used UML diagrams (use case, class, sequence) is essential for government professionals to effectively model and communicate system requirements and processes within public sector workflows.

 21 Hours

Number of participants


Price per participant

Testimonials (4)

Upcoming Courses

Related Categories