Verification vs Validation

Only available on StudyMode
  • Download(s) : 44
  • Published : February 26, 2013
Open Document
Text Preview
Verification versus Validation:
Verification and Validation are the two forms of testing software.

Verification ensures that the system (software, hardware, documentation, and personnel) complies with an organization’s standards and processes, relying on review of non-executable methods.

Validation physically ensures that the system operates according to plan by executing the system functions through a series of tests that can be observed and evaluated.

Verification answers the question, “Did we build the right system?” while validation addresses, “Did we build the system right?”

Verification requires several types of reviews, including requirements reviews, design reviews, code walkthroughs, code inspections, and test reviews. The system user should be involved in these reviews to find defects before they are built into the system. In the case of purchased systems, user input is needed to assure that the supplier makes the appropriate tests to eliminate defects.

Validation is accomplished simply by executing a real-life function. This includes unit testing, integration testing, system testing and user acceptance testing. In this rigorous testing is conducted to validate if the system meets the functional requirement. The three most important skills that a system analysis should have are the same for any company. They should first and foremost have people skills. You have to be able to work with a variety of people and be able to work in teams. You should be an assertive person also. A good systems analysis should be able to take initiative and do things without being told. Also this person should have good reasoning and problem solving skills. These are all things that should be within the person naturally along with the actual computer skills necessary to analyze systems for a client. -are ability to work well with others,

-good communication skills,
-the ability to ask the right questions

Bidder Responsibility Determination:
To be determined responsible, a bidder must be successfully evaluated against the 7 following criteria: 1. Financial Resources.
The bidder must have adequate financial resources to perform the contract, or the ability to obtain them (see FAR 9.104-3(a)—Ability to Obtain Resources). 2. Performance Schedule.
The bidder must be able to comply with the performance schedule, required or proposed delivery, taking into consideration all existing commercial and governmental business commitments. 3. Performance Record.

The bidder must have have a satisfactory performance history, if any (see FAR 9.104-3(b)—Satisfactory Performance Record and Experience Certificate). Nevertheless, a prospective contractor shall not be determined responsible or non-responsible solely because of a lack of relevant performance history, except when specified in a standard for special acquisitions. 4. Integrity and Ethics.

The bidder must have a satisfactory record of integrity and business ethics including satisfactory compliance with laws related to taxes, labor and employment, environment, antitrust, and consumer protection (see FAR 9.406-2—Causes for debarment and FAR 9.407-2—Causes for suspension). 5. Organization and Skills.

The bidder must have the necessary organization and skills, experience, accounting and operational controls, and technical skills, or the ability to obtain them (see FAR 9.104-3(a)—Ability to Obtain Resources). 6. Equipment and Facilities.

The bidder must have the necessary technical equipment and facilities for production or construction, or ability to obtain them (see FAR 9.104-3(a)—Ability to Obtain Resources); and 7. Other Qualification.

The bidder must be otherwise qualified and eligible to receive an award under applicable laws and regulations.

Systems Engineering V Model
The system life cycle
The system life cycle has seven phases: (1) discovering system requirements, (2) investigating alternatives, (3) full-scale engineering...
tracking img