The importance of the use of Catalyst and the five key design elements described above can best be appreciated by examining the benefits that accrue to CHART II as a result of their use. Table 3-1 provides a summary of these benefits.

Table 3-1. Features and Benefits of the CSC/PBFI Design Approach

CSC/PBFI Advantage: Our design approach ensures the delivery of a CHART II system fully responsive to MDSHA needs.

Design Element

Benefit to CHART II


  • Provides an integrated, comprehensive approach based on proven commercial and government experience
  • Is meant to be tailored to respond to MDSHA needs and requirements
  • Conforms with established government and industry standards (e.g., SEIís CMM for Software)
  • Responds to complex, changing, and diversified environments
  • Supports diversified new development approaches, legacy systems, data migration, and change management.

Iterative Requirements Identification, Analysis, and Management



  • Ensures continuous improvement throughout the life of the project
  • Provides a flexible process to ensure that all MDSHA requirements will be met
  • Reflects lessons learned from one-on-one discussions with MDSHA personnel and from system prototyping
  • Supports a true partnership with MDSHA personnel in that both CSC/PBFI and MDSHA personnel are fully involved in all requirements decisions

An Open Systems Approach

  • Ensures that all current and envisioned requirements will be met
  • Ensures consistency with the National ITS Architecture and emerging national ITS standards
  • Eases incorporation of legacy systems and communications with external systems
  • Permits interchangeability of system components
  • Facilitates system growth

Object Oriented Analysis, Design, and Implementation

  • Has the ability to store complex data objects (such as those found in CHART II)
  • Allows complex objects to be manipulated in an organized manner
  • Allows the building of new objects by combining properties of previously existing objects
  • Permits applications to be built that are easier to maintain and enhance than those used in previous design approaches
  • Provides for clearer and more robust implementations and applications to be built on top of other applications
  • Permits new applications to be built on old object-oriented applications without the need for restructuring the underlying data and access methodologies, thereby reducing development time

System Prototyping

  • Identifies problems early in the development process
  • Permits MDSHA to "Fly before Buy"
  • Supports an iterative requirements and design process
  • Ensures a delivered system that is fully responsive to MDSHA needs

An Incremental Approach to Deployment

  • Supports more manageable deployment
  • Develops an operating capability sooner
  • Incorporates user operating experience into later deliveries
  • Promotes high morale through a series of successes

Section 4, Technical Approach, describes our technical design solution: a solution that fully reflects the benefits cited in table