PRIDE ® -ISEM
Information Systems Engineering Methodology
PHASE 7 - SUB-SYSTEM TEST

ACTIVITY A   ACTIVITY B   ACTIVITY C   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

"How a system is implemented is of little importance if it solves the problem effectively."
- Bryce's Law

This section contains the following:


 
    BUSINESS PURPOSE

    Sub-System testing represents a test of both the administrative and computer procedures in a sub-system. Several events occur during this phase:

    • Test data from the previous phases are assembled.

    • The procedures are tested in accordance with the Test Criteria of the Phase 3 "Sub-System Design Manual."

    • Test results are produced and reviewed with Quality Assurance. They are then filed with the master copy of the Sub-System Design Manual in the Technical Library.
     

    METHODOLOGY NAVIGATION

    A Phase 7 may be performed only after Phase 4-I and Phase 6 have been completed. There is a one-to-one relationship between Phase 7 and a sub-system. As such, the Project Manager may bind the procedure number to the project/phase key. For example:

    PD-00123 - Project TS-01 - Process Customer Orders 7 - Phase 7 identifier

    The formal deliverables resulting from Phase 7 will be the test data and test results, which are reviewed by Quality Assurance.

    Phase 7 will then proceed to Phase 8 where it will rejoin other sub-systems and put into production.  

    GENERAL DISCUSSION

    Testing in Phase 7 is performed in a similar manner as in Phase 6, except at a higher level. Whereas Phase 6 "Software Testing," is performed by Software Engineering for all of the programs within the computer procedure, Phase 7 is performed by Systems Engineering for all of the procedures in the sub-system, both administrative and computer.

    During Computer Procedure Design, Software Engineering prepared the computer procedure that will be used by DP Operations. In order to test this procedure, it is recommended that DP Operations actually perform the tests under Software Engineering's direction. In this way, the operating procedures are tested along with the programs used to implement the procedure. Often the operating people will point out areas for procedure improvement.

    During Phase 3, Systems Engineering specified a testing criteria for the overall sub-system. This included the validation of input/output processing, along with anticipated transaction volume for the sub-system. Phase 7, therefore, is used to verify the test criteria and benchmarks.

    Following Phase 7, the sub-system is essentially ready for operation. However, considerable care should be exercised to avoid a premature installation of the sub-system for day-to-day operation. This situation could cause panic conditions if other parts of the system are not ready. This is why Phase 8 is used to release sub-systems.  

    DESCRIPTION OF PHASE ACTIVITIES

    Activity A - Prepare Test Data

    Systems Engineering prepares a Detail estimate and schedule for the activities of Phase 7 (A through C) which is reviewed with Project Management for approval.

    Systems Engineering (the Sub-System Designer) assembles the test data from the previous phases and in accordance with the Test Criteria defined in the Sub-System Design Manual.

    Activity B - Test/Debug Sub-System

    Systems Engineering tests and debugs the sub-system in its entirety, including all procedures. Software Engineering provides assistance as required.

    Activity C - Phase 7 Review

    Systems Engineering reviews the test results with the system designer and Quality Assurance for compliance with installation standards, and to assure that the system design requirements are satisfied.

   


Copyright © 1971-2008 by M. Bryce & Associates
Palm Harbor, Florida, USA
All rights reserved.