"PRIDE"-Information Systems Engineering Methodology (ISEM)

PRIDE

-ISEM

Information Systems Engineering Methodology
PHASE 4-II - SOFTWARE ENGINEERING
ACTIVITY E - PHASE 4-II REVIEW

FUNCTIONAL MATRIX CHECKLIST SUPPORT FORMS

TRANSLATE THIS PAGE TO... Chinese (simple) Japanese Dutch French German Italian
Free Translation courtesy of ALS Chinese (traditional) Korean Portuguese Russian Spanish

CONTENTS

This section contains the following:

BUSINESS PURPOSE

OVERVIEW

STEPS IN EXECUTION

SUPPLEMENTAL INFORMATION (separate sections)
- Phase 4-II Review Checklist

BUSINESS PURPOSE

The purpose of this activity is to review the results of Phase 4-II with DP Operations, Systems Resource Management, Data Resource Management, Project Management, and Systems Engineering (the sub-system designer).

OVERVIEW

This represents the last major review prior to the development of software. Error correction from now on will involve computer time for recompilations, reformatting of data, etc. The review at this point is concerned with the technical problems of implementation. Primarily, two questions need to be resolved:

Will the software design satisfy the requirements as specified in the Phase 3 "Sub-System Design Manual"?

What are the technical implications on the current computer environment?

Copies of the Phase 4-II "Computer Run Book" should be distributed to pertinent managers well in advance of the review meeting. This allows ample time to study the report and prepare for the meeting.

The intent of the review meeting is not necessarily to explain each section of the report, but to answer questions and summarize the conclusions. The report, thereby, is the focal point of the meeting.

There are two possible outcomes from the review meeting:

The software is approved to proceed as proposed.
Revise the software accordingly.

SOFTWARE APPROVED

Systems Engineering advises all meeting attendees of the results of the meeting by memo or letter. The project proceeds as required.

REVISE SOFTWARE

During the review meeting, decisions or discussions may have indicated a change or revision. Software Engineering modifies the report and establishes another review meeting (if necessary) to consider the revised report.

A final and approved copy of the Phase 4-II "Computer Run Book," with the initials or signatures of management, is sent to the Technical Library for filing in the project file.

STEPS IN EXECUTION

Software Engineering conducts a formal review of the Phase 4-II "Computer Run Book" with DP Operations, Systems Resource Management, Data Resource Management, Project Management, and Systems Engineering. Data Base Administration participates in the review by answering pertinent questions as they arise.

Management determines project outcome: Approve project as proposed, or revise.

Software Engineering forwards a formal copy of the "Computer Run Book: along with miscellaneous project documentation to the Technical LibraryTechnical Library for filing.