View Module

An error occurred while attempting to get the requested module. Cannot open database "AspNetForums" requested by the login. The login failed. Login failed for user 'swenet'. at AspNetForums.Data.SqlDataProvider.GetRatingForUser(String username, Int32 parentID) at AspNetForums.Ratings.GetRatingForUser(String username, Int32 parentID) at SwenetDev.ModuleRatingsControl.getRatingForUser(String username, ModuleRatingInfo ratingInfo) at SwenetDev.viewModule.Page_Load(Object sender, EventArgs e)

General Information

Title Verification and Validation: A Quick Introduction
Version Info Version 1 , submitted by towhid on 7/11/2005 at 3:50 PM
View Revision History
Module Identifier towhid.2005.2
Abstract This module introduces the concepts of verification and validation, and how they fit into a traditional software development lifecycle. It is intended for an introductory course in software engineering, or an advanced programming class. A traditional approach is provided to make it easier for the student to grasp the incremental nature of V&V. The presentation is at a very high level and little detail is provided on different techniques for verification and validation.
Size Lecture: 60-120 min
Exercise: 20 minutes
Comments This module is intended for an introductory course in software engineering, or an advanced programming class.

SEEK Categories

  1. V&V terminology and foundations (VAV.fnd)


  1. Massood Towhidnejad
  2. Mike Rowe
  3. David Dampier


  1. Programming Experience
  2. Basic knowledge of requirements and life cycle

Learning Objectives

  1. Knowledge - The student will be able to define both verification and validation, and to know the difference between them.
  2. Knowledge - The student will be able to identify the appropriate activities and their classification as either verification or validation.
  3. Comprehension - The student will be able to distinguish between verification and validation, given a set of activities.
  4. Comprehension - Given a set of software artifacts, the student will understand the appropriate verification or validation activity to that artifact.
  5. Comprehension - Given a set of projects in different categories, the student will be able to determine which category of projects would require more V&V activity, and which would require less.
  6. Comprehension - Given a set of defects and the phases of development in which they were found, the student will be able to estimate the relative cost of correcting errors early or late in the lifecycle.


  1. Verification & Validation (Definitions, Difference, Where Applied (lifecycle))
  2. Which Artifacts are verified? Which are validated?
  3. Importance of V & V.
  4. Categories: When is it good enough?
  5. Cost of V & V activity.


  1. Presentation Slides in MS Powerpoint. Teaching Tips in Notes Section of Slides. (Powerpoint) 0.00/5 [Rate Material]

  2. Exercises for In Class or Exam Questions (Word) 0.00/5 [Rate Material]


See Also...

No alternate modules.

Other Resources

  1. 1. Sommerville, Ian, Software Engineering, 7th Edition, Addison Wesley, 2005.
    2. Bach, James, "A Framework for Good Enough Testing," Computer, vol. 31, no. 10, pp. 124-126, October 1998.
    3. Jorgenson, Paul, Software Testing: A Craftsman’s Approach, 2nd Ediion, CRC Press, 2002.


Number of Ratings:   0

Log in to rate this module.


Discuss this module in the forums.

Related Modules