Software module testing

To provide input to the software module test specifications To ensure a structured approach to the presentation of information that can be carried forward into the software module test specifications... [Pg.600]

The structure of the software module design specification should be similar to that of the software design specification to facilitate checking between the two documents. Once the software module design specification is produced and approved it is possible to generate a software module test specification. [Pg.600]

Software module test specification—for testing individual software components against the software module specification Hardware test specification—for testing the hardware components against the hardware design specification... [Pg.606]

Project Quality Plan Software Quality Assurance Program Functional Design Specification Hardware Design Specification Software Design Specification Software Module Design Specification Software Review Software Module Test Records Hardware Test Records Integration Test Records Instrument Spccs/Data Sheets Instrument Calibration Records Material Certificates... [Pg.630]

Conduct Software Module Testing and Integration Testing... [Pg.88]

Test hardware/peripherals Test software modules Test integrated software code... [Pg.98]

Where the OCS has a standard interface to a particular Fieldbus and the number of installations is such that this can be deemed as standard feature, there is little need for software module testing. This is true of any Fieldbus interface to any control system. In a traditional scenario, where data need to be transferred via the OCS to a maintenance application or a laboratory analysis package, the actual transfer of the data needs to be fully tested as a bespoke application. [Pg.180]

The tests of the application software module testing shall be documented. [Pg.258]

The procedure for an appropriate change-control-process shall be established with defining a unique baseline of the version of the SRECS and a definition of all configuration items (e.g., specifications, design documents, hardware/software modules, test plans and results, verification and validation reports, tools, change control procedures and effect analyses) of a baseline. [Pg.262]

Is each software module tested individually as fully as possible before incorporation into the full program ... [Pg.105]

Requirements for application software module testing This shall be done through review, simulation, and testing such as configuration (input through logic to output), and result shall be readily available. [Pg.460]

Software module testing This shall be carried out as per specification to show whether each module is performing the intended function. All test results shall be documented and corrective action shall be initiated. [Pg.592]

Timing performance Software module testing Software integration testing PE integration testing Software aspect—system validation Data structure... [Pg.594]

Adaptation of the phases of the SLCM to the specific development project. We normally experienced merging of phases. We observed that the hardware and software integration happened earlier than expected, even before the software integration. In many cases the software module test already required the software and hardware integration. [Pg.143]

Big Chemical Encyclopedia

Chemical substances, components, reactions, process design ...