Environmental Engineering Reference
In-Depth Information
analyzed and eliminated (or a well-founded deci-
sion for their subsequent elimination was made).
Software verification corresponds to the
criterion of documentation if a plan and report
were issued which describe in detail the course
and results of verification. In this case individual
parts of a verification plan and report, which have
individual significance (programs, test methods,
protocols and so forth) can be issued in the form
of individual documents.
Software verification corresponds to the ac-
cessibility criterion if all of the documentation on
software verification was set forth in a form un-
derstandable to specialists who do not participate
in conducting the development and verification.
Evaluation of documents related to software
development:
During the expert evaluation of
documents on software development the require-
ment specification and design documentation are
evaluated. In the expert analysis of the requirement
specification the following are established and
evaluated: the extent to which software require-
ments are correct and not contradictory; to what
extent the functional requirements for software
correspond to requirements for the I&C system;
how fully are general requirements for software
reflected in the feasibility study (requirements,
which are established independently of specific
functional purpose of the I&C system).
The evaluation of software requirements is
conducted with consideration of: safety class of
the I&C system, which includes software is a
component; level of software approval; software
purpose.
During expert examination of the design
documentation one will analyze: description
of the composition, structure and functions of
component parts of the software; information
on methods and means of testing and running
experiments with software.
The evaluation of verification documents:
The
basic verification documents for evaluation are
verification plan and verification report.
The software verification plan (SVP) evalua-
tion is conducted based on criteria of document-
ability, accessibility, completeness, independence.
1. In the evaluation based on documentability
criterion one establishes that the SVP was
issued prior to the beginning of software
verification and defines: choice of veri-
fication strategy; sequence of conducting
verification; methods and devices used in
the verification process; sequence of docu-
mentation of verification actions; sequence
of verification results evaluation.
2. In the evaluation based on accessibility
criterion one establishes that the SVP is set
forth in a form understandable for special-
ists who did not participate in the software
development process.
3. Based on the completeness criterion one
carries out the evaluation of the following
items stipulated in the SVP:
a. Sequence of conducting verification. In
evaluating the sequence of conducting
verification one must establish that the
verification stipulates after each step of
the software development: generation
of requirements for software; design;
coding.
b. Completeness of tests. In evaluating
the completeness of tests it should be
established that the sets of tests that are
selected for verification will assure the
possibility of checking all stipulated
functions and interfaces of the I&C
system, and also the check of fulfill-
ment of requirements for software.
c. Software verification and development
tools. In evaluating the tools of software
verification and development it should
be established that the SVP stipulates
the use of automated design and test-
ing tools and indicates the selection
criteria for them. One should evaluate
the conformity of the proposed criteria
Search WWH ::
Custom Search