Software of Safety Important I&C Systems - Nuclear Power Plant Instrumentation and Control Systems for Safety and Security - page 173

These features allow classifying of tools as
follow.

verification and expert examination of software
and, as a rule, are automated, local or composite
tools of non-intelligent or combined type, which
support, above all, verification and expert exami-
nation of products.
Tools of this kind provide:

1. By functional purpose one can distinguish
tools for informational, analytical, and or-
ganizational support.
2. By degree of process automation tools
can be subdivided into manual (partially
formalized), automated, and automatic. In
determining the type of tool based on this
feature one must consider the degree of
automation of preparation, input, analysis,
documentation and display of information.
3. By the number of supported stages tools
are divided into local, compositional, and
end-to-end. This feature determines the
boundaries and scope of the operation of
a tool.
4. By kind of project components one can
distinguish tools that support evaluation
of: products (requirements, specifications,
design components, codes, methods, reports
and so forth); processes (specification,
design, coding, testing, verification and so
forth).
5. By level of intelligence one can distinguish:
non-intelligent tools, or traditional kind
of tools (without using knowledge-based
methods); intelligent tools; and combined
tools.
6. According to possibility of integration tools
are divided into integratable, which allow
one to use a given tool together with other
ones, and non-integratable.

1. Generation of a profile-like base of national
and international normative documents,
which determine the software requirements
and order of evaluating their execution
during verification and software expert
examination.
2. The generation of general and particular
normative profiles of software based on an
analysis of profile-like documents:
a. Software requirements (structure and
properties; inspection and diagnostics;
reliability and tolerance; development;
verification).
b. Methods of evaluating the fulfillment
of requirements.
c. Evaluation of the quality of the process
and expert examination results.
3. The formalized analysis of the general and
functional requirements for the software that
has been examined by experts based on the
submitted documents.
4. Formalized preparation of data on the expert
analyzed software and processes of its devel-
opment and verification based on templates
(questionnaires).
5. Databases on software expert examination
that have been carried out and are being
carried out, which include full systematized
information on tasks, expert analysis object,
course and results of the expert examination.
6. A transition from verbal to formal descrip-
tion of software requirements (partially
formalized verbal matrices, semantic trees,
product rules, Z-notations).
7. Databases of quality metrics and software
reliability.
8. Database of software reliability models.

By grouping the different (by purpose, level
of intelligence and so forth) tools it is possible
for carrying out various scenarios of the expert
examination, which require use of analytical,
information and organizational type tools, intel-
ligent or combined tools and so forth.
Informational tools are intended for the gen-
eration, preliminary processing and analysis of
information required for carrying out independent