About-network-video:
video-solution:
Related-links:
|
| Software Testing
|
|
1 The contractor is required to carry out software testing, including, but
not limited to the following:
a) review of specifications
b) review of
the code module
c) Module Test
d) FBI software
e) system FBI
f)
verification
g) recognition software
h) Durability testing and load
testing
i) back to the old test
j) Factory Acceptance Test
k) test
run
2 system software only factory acceptance testing requirements and
test run. Approved for use by engineers dedicated commercial soft
Pieces
does not mean acceptance of the software. Contractor has full responsibility to
ensure that all of these standard packages (not
Tube separately or
simultaneously implemented) to achieve the required functionality and
performance.
3 Review of specifications
a) contractor to the
software specification review to ensure that specifications to standardize the
documentation phase
Software will be generated.
b) review of
specifications should be:
i. to ensure that the document in line with
engineering standards;
ii. to confirm the technical programs to meet the
requirements;
iii. to ensure that documents are complete, clear and clear.
55
c) review the record of
specifications to be submitted as part of the test documents.
4 module
code review
a) all the software modules must be strictly reviewed to ensure
that the software code in accordance with design requirements and in accordance
with the
The requirements of the standard programming.
b) As a minimum,
code review module to "demonstrate" a list of software code.
c) the code
review module to the contractor is composed of representatives of the quality of
the independent group.
d) code review module records submitted shall
constitute a part of the test documents.
5 Module test
a) each
module must be tested to ensure that procedures accurately reflect the design
and ensure that by
According to the requirements of the specifications to
run.
b) test will be to prove:
i. any valid input, or a combination of
several input can generate the correct output.
ii. by control of the correct
way to deal with invalid input.
iii. the meaning of clear and display
appropriate error message.
c) After each module programmer coding proofing
done after the pre-integration after a successful demonstration
Should be
tested.
d) for each software module must follow the "special requirements"
under Chapter XIV of the Software Measurement Standard
Prospective.
e)
module test record shall constitute a document submitted as part of testing,
including test specifications,
The use of test tools and methods as well as
the input parameters and output results. Test module
Version and revise part
of the document must be recorded in the.
FBI software 6
a) in the
control module integrated with the environment, and then tested to ensure that
the software can be integrated
Accurately reflect the program design and to
meet the "exclusive specification" requirements.
b) test will be to prove:
i. any valid input or a combination of input to produce the correct output.
ii. dialogue and the transfer of information between modules of the sort is
correct.
iii. by control of the correct way to deal with invalid input.
iv. the meaning of clear and display appropriate error message.
56
c) integration software must be followed
for each "special requirements" under Chapter XIV of the Software Measurement
Standard
Prospective.
d) software, FBI records shall constitute a
document submitted as part of the test, including test specifications,
Module version, the use of test tools and methodologies, as well as test
input and output parameters of the node
Fruit.
FBI 7 system
a)
combination of software and hardware to conduct tests to ensure the system can
accurately reflect the system set up
Dollars, and to ensure that in
accordance with the "exclusive specification" requirement to run.
b) FBI
records system shall constitute a document submitted as part of testing,
including test specifications
Books, software version, use the test tools
and methodologies, as well as test input and output parameters
Results.
8 Authentication (Verification)
In each design phase, the contractor
must verify that the output stage of the design must be able to meet the
previous
Seeking. Therefore, the special requirements of the verification
process to ensure the continuity and traceability.
9 software to confirm
(Software Validation)
a) The contractor is required to identify and confirm
that in line with the special requirements of software. Integrated software to
pre-acceptance tests
To be confirmed.
b) the contractor to record all
test results, constraints, observation and unusual. Trouble in mind
Then
recorded to indicate the corrective measures taken.
10 durability
testing and load testing (Endurance and Load Test)
a) software system to
carry out durability testing and load testing. Constitute the two tests to
confirm the test
Or part of factory acceptance testing.
b) durability
testing to prove the system is running in the design of the data environment to
the time overrun
Paragraph work.
c) load testing to prove the system in
a given load conditions (including the peak load) can be reached
To the
requirements of performance.
d) the use of a complete system and with
external interfaces to the simulation system durability testing and load testing
Test.
11 Old test (Regression Test)
Throughout the testing
phase, the contractor shall be modified in software to carry out back to the old
test. Back to the old test did not prove
The software does not modify the
changes due to damage to software and revised in line with the special
requirements of the software.
57
12 software verification platform test (Software Proofing Platform Test)
Not applicable.
Related Product:
กก
|
| |
|
|
