Software Engineering reviews the computer procedure design
to assure that its execution will conform to operating standards
and determines the resources the procedure will require, e.g.,
computer time, capacity, and other peripheral resources.
The computer procedure and its programs are then defined
in terms of where they will be both developed and put into
production on the computer. Computer directories/libraries are
established on the computer where the software will reside.
Computer processable control instructions are developed by
Software Engineering that will be used by the operating system
for executing the programs. This may consist of a variety of
things:
- Job Control Language (JCL)
- Digital Command Language (DCL)
- Executive Control Language (ECL)
- CLISTS
- REXX
- CL (Control Language)
- Command Files
Development of these instructions are typically performed
in accordance with installation standards.
PREPARING FOR REVIEW
Software Engineering assures that all of the Phase 4-II
activities and materials have been properly completed. A Phase
Review Checklist is available for this purpose. A formal Phase
4-II "Computer Run Book" is then prepared. The manual is
reviewed and checked by Quality Assurance prior to distribution
for review.
The Phase 4-II run book contains the following items:
- Phase Cover Page - including a Table of Contents,
along with a distribution/approval list.
- Computer Procedure Flowchart - as prepared in
Activity A.
- Computer Procedure Discussion - as prepared in
Activity A.
- Test Criteria - as prepared in Activity B.
- Software Structure Diagram - as prepared in
Activity B.
- Program Specification - as prepared in
Activity B.
- Module Specification - as prepared in Activity B.
- Data Resource Layouts - as prepared in
Activity C.
- Phase Review Checklist - specifying acceptance
criteria for the deliverables mentioned above.