3.3.1 Iterative Requirements Identification, Analysis, and Management

The CSC/PBFI Team is committed to working in partnership with MDSHA and in ensuring open communications at all levels. This cooperative relationship begins with the generation of requirements and continues throughout the life cycle of the project.

Initial system requirements were, of course, provided in the MDSHA CHART Software Functional Requirements Document. These requirements are, however, only a beginning. A key element of our design approach is the iterative identification, analysis, and management of new system requirements throughout the life of the project.

We use the word iterative to describe a process in which (1) requirements can be generated at any stage of the development process (not just at its beginning); and

(2) the CSC/PBFI Team and MDSHA personnel analyze and manage these requirements through a process of mutual discussion and cooperation.

To that end, the CSC/PBFI Team has participated in joint meetings with key MDSHA "stakeholders," attended CHART Working Group Meetings, met individually with MDSHA officials and system users, and initiated system prototype demonstrations at which a number of new requirements have been identified. These ideas were then discussed with the appropriate MDSHA personnel and have been incorporated in this design document.

During this design phase of this project, new requirements are managed through the internal Configuration Management processes employed by the CSC/PBFI Team. However, once award has been made, a formal configuration management process to which appropriate MDSHA personnel have access will be employed throughout the remainder of the project.

An iterative requirements process ensures that the final CHART II design will fully meet MDSHA requirements on the day it is delivered and reflect the "lessons learned" from the one-on-one discussions between CSC/PBFI and MDSHA Team members and from the prototyping of the proposed CHART II system.