Virtualization - Course Details

DSAPSS(EBA250) Designing Strategically Aligned Public Sector Solutions (EBA250)

Virtualization Course Description:
Through lecture and case study-driven workshops, you will learn how to bridgethe gap between planning and implementation. You will relate the impact ofdifferent solution strategies on the Enterprise Business Architecture (EBA) andbe able to use EBA designs in Requests for Proposals (RFPs). You will learn therelationship between EBA and functional, information, business rules, andsecurity requirements. You will learn to map the relationship between businessprocesses and software services in Service-Oriented Architectures (SOA). Youwill also learn the nature and use of EA repositories to support architecturalreuse.
Virtualization Course Duration:
2 DAYS
Virtualization Course Target Audience:
Policy and planning analysts, program review analysts, business architects, business analysts, business designers, business solution consultants, business transformation analysts and designers
Virtualization Course Prerequisite:
NONE
Course Content:

  • 1. Planning Vs. Implementation

    • Strategically Aligned Solutions vs. Traditional Stovepipe Solutions
    • Planning a Transformation Initiative vs. Planning a Solution
    • Project Portfolio Management vs. Project Management
    • Role of the Enterprise Business Architect in Transitioning theOrganization from Portfolio Planning to Solution Implementation
    • Role of Architectural Governance in Project Portfolio Management andSolution Implementation Lifecycles

  • 2. How Enterprise Models Support Solutions Strategies

    • How Target Business and System Models Support the Selection andImplementation of a Solution Strategy
    • Re-Use As Is
    • Custom Building
      • Extending Existing
      • Building New
    • Commercial Off-the-Shelf (COTS) Software
      • Acquire New
      • Extend Existing (Additional Off-the-Shelf Functions)
    • Using EBA Models to Support Solutions Acquisition
    • Elaborating EBA Models in Project Repositories: Check Out/Check In

  • 3. EBA and Functional Requirement Analysis

    • Using the Function Model to Set the Scope of the Solution
    • Using Business and System Use Cases to Align Solution with BusinessRequirements
      • Specification Level
      • Acceptance Testing Level
    • Using the Logical Integration Model to Specify Integration with LegacySystems

  • 4. EBA and Information Requirements

    • Using the Information Model to Define Solution Requirements for ManagingInformation
    • Using Data Mastering to Define the Requirements for Data Integration

  • 5. EBA and Business Rules

    • Using the Policy Model to Define Solution Requirements for ManagingBusiness Rules
    • Strategies for Making Business Rules Available to Future Solutions
    • Strategies for Making Legacy Systems' Business Rules Available for Re-Useby other Systems

  • 6. EBA and Security and Privacy Requirements

    • Using the Trust Model to Define Security and Privacy Requirements forSolutions (Authentication, Authorization, Administration)
    • Using EBA Models to Support the Development of Privacy Impact Assessmentsand Threat Risk Assessments (TRAs)
    • Using Role-Responsibility Models to Define User Privileges for Solutions

  • 7. Aligning Application Services with Business Processes

    • Using the Business Models to Ensure that Solution Designs MeetCross-Functional Business Process Requirements
    • Applying Use Case and Swim Lane Models to Align Application Services withBusiness Process Requirements

  • 8. Solution Benefits Tracking - Closing the Loop on Alignment

    • Role of Solution Benefits Tracking in Achieving Alignment and CompletingSolution Architecture Validation
    • What Is Needed to Meet Business Expectations and Project Commitments
    • Defining Strategies for Tracking Benefits of the Solution