R. Clayton (rclayton@monmouth.edu)
Mon, 31 Jan 2000 09:15:35 -0500 (EST)
Please elaborate on the topic of Verification requirements, as found under
sec 3.0 - Specific Requirements of the SRD template.
It seems to involve the aspect of self-verification from the system
perspective.
That's about right, but remember these requirements are client-generated, so
the verification would relate to the client's need to be assured the system's
working correctly. You can view client-perspective verification as external
(to the system) verification requirements, while system-perspective
verification are internal (to the system) verification requirements. Because
they involve the design of the solution, internal verification requirements are
properly introduced in the system-design phase of the project, unless the
client wants specific internal verification requirements included in the
solution (which is not to imply that it's a good idea for a client to specify
internal verification requirements).
An example of a external verification requirement would be to have an
accounting system produce a weekly audit trail of all transactions occurring
during the previous week. An independent expert (an accountant, for example)
could then go over the audit trail to determine if the accounting system is
working correctly. In the case of a control system for an oil refinery,
external verification requirements may involve direct read-outs of all sensors
and gauges under the system's control.
External verification requirements may not only arise from the client, but also
from the context within which the client operates. For example, database
software written for a European client may have to comply with external
verification requirements set by the EU to insure that data-privacy laws are
not being violated by the database's operation.
Note also that a well organized and consistent SRD will probably have some
meaningful relation between Sections 3.6 and 3.7.
This archive was generated by hypermail 2.0b3 on Thu Mar 30 2000 - 20:50:05 EST