TOGAF: Business Scenarios and Business Goals

From Glitchdata
Jump to navigation Jump to search

A business scenario describes:

  • A business process, application, or set of applications that can be enabled by the architecture
  • The business and technology environment
  • The people and computing components (called "actors") who execute the scenario
  • The desired outcome of proper execution


A good business scenario is representative of a significant business need or problem, and enables vendors to understand the value to the customer organization of a developed solution.

A good business scenario is also "SMART":

  • Specific, by defining what needs to be done in the business
  • Measurable, through clear metrics for success
  • Actionable, by:
    • Clearly segmenting the problem
    • Providing the basis for determining elements and plans for the solution
  • Realistic, in that the problem can be solved within the bounds of physical reality, time, and cost constraints
  • Time-bound, in that there is a clear statement of when the solution opportunity expires

Process

  1. Identifying, documenting, and ranking the problem driving the scenario
  2. Identifying the business and technical environment of the scenario and documenting it in scenario models
  3. Identifying and documenting desired objectives (the results of handling the problems successfully); get "SMART"
  4. Identifying the human actors (participants) and their place in the business model
  5. Identifying computer actors (computing elements) and their place in the technology model
  6. Identifying and documenting roles, responsibilities, and measures of success per actor; documenting the required scripts per actor, and the results of handling the situation
  7. Checking for "fitness-for-purpose" and refining only if necessary


Phases

  • Gather
  • Analyse
  • Review

Developing Business Scenarios

  • Identifying, Documenting, and Ranking the Problem
  • Identifying the Business & Technical Environment, and Documenting in Models
  • Identifying and Documenting Objectives
  • Identifying Human Actors and their Place in the Business Model
  • Identifying Computer Actors and their Place in the Technology Model
  • Documenting Roles, Responsibilities, Measures of Success, Required Scripts
  • Checking for Fitness-for-Purpose, and refining if necessary

Guidelines on Goals and Objectives

SMART Objectives (as noted above):

  • Specific
  • Measurable
  • Actionable
  • Realistic
  • Time-bound

Categories of Goals and Objectives

  • Goal: Improve Business Process Performance
  • Goal: Decrease Costs
  • Goal: Improve Business Operations
  • Goal: Improve Management Efficacy
  • Goal: Reduce Risk
  • Goal: Improve Effectiveness of IT Organisation
  • Goal: Improve User Productivity
  • Goal: Improve Portability and Scalability
  • Goal: Improve Interoperability
  • Goal: Increase Vendor Independence
  • Goal: Reduce Lifecycle Costs
  • Goal: Improve Security
  • Goal: Improve Manageability

Links


Related ADM Guidelines & Techniques