Course Outline

Best Practices for Government

  • Software Crisis
  • Best Practices in Software Development
    • Iterative Development
    • Management Requirements
    • Component-Based Architecture
    • Visual Modeling
    • Verification of Quality
    • Change Management

RUP for Government

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

Create an Object Model for Government

  • UML 2 as a Way to Represent the Model
    • The Object Model
    • Methods of Describing the Model
  • Practical Analysis of the Specification of Use Cases
    • Actor
    • A Use Case
    • Association
    • Relations Include, Extend

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
    • Relations Refine
    • Building Strong Relationships Between the Results of the Analysis Phase and the Design Phase
  • Modeling Design Classes
    • Class
    • Association
    • Enumeration
    • Forward/Reverse Engineering
  • Subsystem Design
    • Component
    • The Relationship of Delegation
    • Connector Assembly
  • Description of the Aspects of Concurrency in the System Architecture
    • Examples of Activity Diagrams, Sequence and State Machine
  • Description of the Aspects of the Architecture of Dispersion
  • The Different Perspectives of Architecture Description

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