6.2.2 CatalystSM Structure

Catalyst’s structure is identified in six phases performed against sets of related activities, called framework areas, as shown in figure 6-1.

Figure 6-1. The Catalyst Project Management Structure

CSC/PBFI Advantage: Catalyst will provide flexible paths and consistent results for all CHART II Tasks. Phases

Phases are Catalyst’s structure for sequencing and describing the work of business change and system development. They are a convenient mechanisms for establishing an overall sequence, are the basis for planning and estimating, facilitate project and program wide synchronization of activities, and chart decision points for management. There are six phases:

The Vision and Strategy phase examines the enterprise itself, its processes, and its overall automated support philosophy—a necessary first step to ensure that the automated systems provide tangible value to the enterprise.

The remaining four development phases address, respectively, what traditional life-cycle methodologies cover in system requirements and design, system implementation, system integration and test, and system deployment. Because much of the design required to support CHART II is being accomplished as part of this design runoff, it is the final development, integration, and deployment phases of Catalyst that are of particular interest for the implementation of CHART II. Framework Areas

The Catalyst framework is a flexible and adaptable structure within which the CSC/PBFI Team will plan, execute, integrate, test, deploy and maintain CHART II applications and systems. The framework areas are as follows: Paths

Paths are Catalyst’s approach to the development and maintenance of application systems. Separate paths flow horizontally through the Process Enablement parts of the architecture and development phases shown in figure 6-1. Each path satisfies different customer needs and initial conditions for the effort. In addition, four development paths, one maintenance path, and one application reengineering path is provided.

For CHART II we will be employing a combination of two development paths: the traditional development approach combined with accelerated application development.

The RDD path offers a comprehensive life-cycle approach for our customers who require a comprehensive life cycle with checkpoints at each stage of the development. RDD is especially suited to large/complex systems with formally issued requirements, safety or mission critical criteria, and customer mandates. It is designed for large-scale system development.

A combination of these paths is required for CHART II because while we have a very specific set of software functional requirements that must be met, we also wish to retain the flexibility to use extensive prototyping, accept changes as development and implementation proceeds, and to employ accelerated application deployment. We will document this task-specific approach in the Program Management Plan to be provided to the MDSHA at the beginning of the project. (See Section 6.3, Our Five-Step Management Approach.)

Table 6-1 summarizes the major activities of each Catalyst phase and specialty area. While it is the Development phase and later phases that are most applicable to CHART II, a review of information normally obtained during the Vision and Strategy and Architecture phases will be made to ensure true understanding and a common point of beginning between MDSHA and its CSC/PBFI partners.

Catalyst provides the methodology to ensure that:

Table 6-1. Major Activities of Each Catalyst Phase.

CSC/PBFI Advantage: We will select the right Catalyst activities for each CHART II Activity.

Vision and Strategy Phase (Enterprise Planning)

  • Understand the business and its environment
  • Understand customer perspectives
  • Define business strategy by establishing performance and process objectives
  • Develop IT strategy to support business strategy

  • Establish business vision and underlying principles
  • Identify implications of vision and principles
  • Define and prioritize change programs targeted to cross business areas
  • Align and mobilize organization to support activity

Architecture Phase (Overall Enterprise Systems Architecture and
System-Specific Concept Definition, Requirements Analysis, and Design)

  • Specify overall enterprise systems architecture characteristics
  • Assess enterprise application system portfolio
  • Assess the enterprise’s software process
  • Understand the business issues associated with the processes for the targeted business area of the enterprise
  • Develop/update vision, principles, and performance objectives for business area to set direction for the future

  • Investigate potential solution approaches (best practices, technology trends, existing components, COTS, GOTS, reuse)
  • Perform cost-benefit analyses
  • Develop implementation plans; plan development/enhancement activities in a series of releases

Process Enablement


Infrastructure (TI)


  • Design/modify processes to support business vision and principles
  • Develop/modify system and operations concept (in conjunction with TI)
  • Develop/modify functional, performance, operational, and programmatic requirements for the system (in conjunction with TI)
  • Evaluate and select GOTS, COTS, reuse components
  • Develop/modify and evaluate system architectures (in conjunction with TI)
  • Develop/modify and evaluate system configurations to determine best value system design that satisfies all customer requirements (in conjunction with TI)
  • Perform evaluations and trade-off analyses
  • Plan system testing and data acquisition, conversion, and transition

  • Assess current organization structure, culture, and competencies
  • Profile future organization structure, culture, and competencies
  • Outline transition strategy

  • Create technical infrastructure component of the system architecture
  • Create logical TI design
  • Evaluate and modify for performance
  • Specify development environment and plan acquisition

  • Determine general facilities requirements by location type

Development Phase (Configuration Item-Level
Requirements Analysis, Design, Implementation, and Test)

Process Enablement

Organizational Change

Infrastructure (TI)


  • Complete process design
  • Identify application software and data requirements
  • Perform value recovery of existing applications, recovering design from code, analysis from design
  • Install any GOTS, COTS, and reuse software
  • Design, prototype, build, test, and performance engineer applications
  • Perform release-based maintenance
  • Perform Regression Testing

  • Develop/update training materials and procedures, documentation, and help materials
  • Develop/update programs to improve staff performance

  • Develop/update detailed hardware, systems software, and network configuration
  • Order, install, and integrate technical infrastructure components for pilot site
  • Test technical infrastructure components individually or in small groups
  • Begin informal integration testing

  • Select sites
  • Design and build new sites
  • Make major changes to existing sites

(System) Integration Phase

  • Integrate application and technical infrastructure components with legacy components and test together
  • Acquire, load, and convert test and production data
  • Perform regression testing

  • Set up pilot operation with actual user/site personnel to validate the functionality and usability of all components (training, procedures, application, technology)
  • Validate systems management activities
  • Certify readiness of release for deployment

(System) Deployment Phase

  • Validate readiness of site for deployment
  • Train site personnel

  • Deploy component(s) to target locations–order, install, integrate, and test application and technical infrastructure components at the locations

Operational Services

  • Support system operations
  • Provide system administration

  • Provide operational maintenance; both emergency maintenance/ preventive maintenance
  • Train targeted business users and customers