PRIDE ® -ISEM
Information Systems Engineering Methodology
PHASE 7 - SUB-SYSTEM TEST
ACTIVITY B - TEST/DEBUG SUB-SYSTEM

TOOLS & TECHNIQUES   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

    The purpose of this activity is to test the sub-system for procedural conformity and to assure the correct processing of data.  

    OVERVIEW

    This activity tries to simulate live conditions. In addition to verifying the processing of data, Systems Engineering assures that there is a smooth flow of work between people and equipment. Procedural "bottle-necks" are identified and expedited.

    Using the data prepared in Activity A, Systems Engineering tests the sub-system for normal operation. All program errors found are corrected by Software Engineering. Test data used in Phases 5 and 6 should be revised to detect these errors.

    Sub-system testing is considered complete when it can handle all test data correctly and meets environmental operating specifications.

    In addition to Systems Engineering and Software Engineering, Data Base Administration and DP Operations may participate in the test.  

    STEPS IN EXECUTION

    1. Systems Engineering tests the sub-system until all logic errors have been eliminated.

    2. Systems Engineering retains the test data and test results for review in the next activity. If necessary, Software Engineering updates the Phase 5 and 6 test data.

   


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