Previous Next Methods Allocation  
4.41 Elementary Method "Test" (T)  

  4.41 Elementarmethode "Testen" (T)

Contents  
  • 1 Identification/Definition of the Method
  • 2 Brief Characteristic of the Method
  • 3 Limits of the Methods Application
  • 4 Specification of the Methods Allocation
  • 5 Interfaces
  • 6 Further Literature
  • 7 Functional Tool Requirements
  • 1 Identification/Definition of the Method

    /Myers, 1991/ chap. 5, pp. 18-29; chap. 6, pp. 102-127

    2 Brief Characteristic of the Method

    Objective and Purpose

    The objective of "Test" (T) is to discover errors or to check if specified requirements have been met.

    Operational Sequence

    The principle of method Test is to prove that the object to be assessed does not contain errors with regard to the defined test cases by executing this object by means of the defined test cases. The following criteria have to be met: the test must include a unique reference to the specification and the test must be repeatable, reconstructible and measurable.

    The implementation of a test comprises the following steps:

  • test preparation
  • test realization
  • test evaluation
  • The preparation of the test comprises the supply of the test cases, the generation of the test bed, and the preparation and installation of the test recording.

    The test realization includes the test runs and the recording of the test results.

    Within the scope of the test evaluation, the expected and the actual results will be compared. In this connection, special analysis types can be carried out:

  • coverage analysis
  • data flow analysis
  • data coverage analysis
  • function coverage analysis
  • 3 Limits of the Methods Application

    - not applicable -

    4 Specification of the Methods Allocation

    - not applicable -

    5 Interfaces

    No. Activity Description
    4.1 SD4.2
    Design of Internal
    and External
    SW Interfaces
    Method T is applied to assess the following objects:
  • User Requirements
  • Technical Requirements
  • System Architecture
  • SW Architecture
  • SW Design (Module/Database)
  • SW Module
  • SW Component
  • Database
  • SW Unit
  • Segment
  • System
  • Operational Information (Information for the User Manual, Information for the Diagnosis Manual, Information for the Operator Manual and Other Application Information)
  • Assessment Procedure
  • With regard to the objects to be assessed User Requirements, Technical Requirements, System Architecture and SW Architecture, a test only refers to those contents of the object that are structured according to a predefined formalism permitting it to be executed.

    Testing the Information for the User Manual, the Diagnosis Manual, the Operator Manual , and the Other Application Information is to result in the discovery of deviations from the actually realized system in the described Operational Information.

    With regard to the listed objects to be assessed, method T completely covers the assessment if applied in combination with other methods. With regard to the objects to be assessed User Requirements, Technical Requirements, System Architecture, SW Architecture, SW Design (Module/Database), Operational Information, and Assessment Procedure the application of method REV - Review is additionally required.

    In case the contents of the object to be assessed are structured in accordance with a predefined formalism, the application of method STAT - Static Analysis is additionally required for the objects User Requirements, Technical Requirements, System Architecture, SW Architecture and SW Design (Module/Database).

    For the objects to be assessed User Requirements, Technical Requirements, SW Module, SW Component, Database, SW Unit, Segment and System the application of method SIMU - Simulation Models is additionally required.

    6 Further Literature

    /Deutsch, 1982/ Software Verification and Validation
    /Myers, 1991/ Methodisches Testen von Programmen
    /Sneed, 1988/ Software-Qualitätssicherung

    7 Functional Tool Requirements

    SQA15 - Supporting Dynamic Assessments

    Previous Next GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster