The purpose of this activity is to review the Work Request/Objective and preliminary Project Scope as submitted by Data Resource Management and to prepare a Detail estimate and schedule to complete the activities in Phase 1 (A - G). The Work Request/Objective and preliminary Project Scope specify the business problems/opportunities to be addressed by the project. These are normally prepared as part of the Enterprise Information Strategy (EIS) under the Enterprise Engineering Methodology (EEM).  

OVERVIEW

Work Requests/Objectives are documented in the IRM using the MI resource. The MI may represent NEW development, MAINTENANCE (correction of errors/problems/"bugs"), or MODIFICATION/IMPROVEMENTS (where the "MI" prefix is derived). There is not necessarily a one-to-one relationship between MI's and PD's (Project Descriptions). One project may implement many objectives and one objective may be implemented by many projects. Although these relationships are established during EEM, it is important that the Project Manager understand all of the objectives associated with the project.

A preliminary Project Scope is also prepared under EEM and updated accordingly by the Project Manager. The scope outlines the organizational areas affected by the project. One project may affect many users. Essentially, the scope establishes WHAT is being studied and WHY.

DBEM related projects are initiated primarily in support of ISEM related projects. However, special projects can be initiated to prepare tentative descriptions of Objects and Views in support of the Information Requirements and Functional Entities identified under EEM.

Based on the Work Requests/Objectives and Project Scope, Project Management prepares a Detail estimate and schedule to complete the activities in Phase 1 (A - G). This is reviewed with Data Resource Management for approval. As part of this estimate/schedule, it will be necessary to allocate time for Data Engineering and other functions participating in Phase 1 (e.g., Data Base Administration, Data Communications Administration, Systems Engineering, Software Engineering, DP Operations). The Detail estimate and schedule is documented using the Project Control Sheet.

Prior to undertaking a study in an organizational area, the Project Manager and engineers should be introduced to all pertinent department personnel. This introduction serves two purposes: project members can associate names with faces, and secondly, user personnel are explained their roles and responsibilities during the project, particularly interviews and reviews. People, by nature, have a fear of the unknown. If an engineer enters unannounced to conduct interviews, the user personnel involved may feel insecure and refuse to cooperate during the project.

Project Management reviews the Project Scope, and the Detail estimate/schedule with Data Resource Management for approval. During this review, any requested changes are noted and included.  

STEPS IN EXECUTION

1. Data Resource Management initiates a DBEM project by selecting appropriate project personnel. This includes Project Management, Data Engineering.

2. The project team analyzes the Work Request/Objectives and preliminary Project Scope. These materials are normally prepared as part of the Enterprise Information Strategy (EIS) under the Enterprise Engineering Methodology (EEM). The project team must understand the business problems/objectives of the project and the areas of the business affected.

3. Project Management reviews and, where applicable, updates the Project Scope.

4. The project team is introduced to the the user organization being served. Here, the organizational structure is reviewed. Where available, organization charts, function charts, and job descriptions are consulted.

5. The project team prepares a Detail estimate and schedule to complete the activities in Phase 1 (A - G).

6. The project team reviews the updated Project Scope, and the Detail estimate/schedules with Data Resource Management for approval.