Techniques for validating requirements

The plan analyzes in detail what the functions of the software would be, how it would interact with existing systems and what the user interfaces would look like.For example, the head librarian requests that the new software provide a user-friendly interface with a large font so that searching the library catalog is quick and the results are easy to read.A local software company has volunteered to design a database for use on the library's PCs that would streamline library services.Before the company starts to write the programming code for the database, the software developers have to gather detailed information about what the current library processes are and map out the specifications for automating the components of those processes.It may include simple physical manipulation and the verification of a product or system using a controlled and predefined series of inputs, data, or stimuli to ensure that the product or system will produce a very specific and predefined output as specified by the requirements.It may be performed on an iterative basis on every produced engineering element during development and may begin with the validation of the expressed stakeholder requirements.

My views: Requirement verification is about ensuring that they are defined clearly and precisely to the extent that they can be designed, developed and tested.

It is important to remember that while system validation is separate from verification, the activities are complementary and intended to be performed in conjunction.

Validation is the confirmation, through the provision of objective evidence, that the requirements for a specific intended use or application have been fulfilled.

I will provide a description of each with two brief examples of how each could be used to verify the requirements for a car and a software application.

is the nondestructive examination of a product or system using one or more of the five senses (visual, auditory, olfactory, tactile, taste).


Leave a Reply