difference btw software verfication and software validation

Until now, i used "verification" and "validation" many times in my mails but still didn't recognize and understand their differences totally.

hope you can get the idea from following URL:

http://blues.se.uec.ac.jp/mt/swtest/archives/000055.html(in Japanese)

I also pick up some msgs from following URL to let you grasp the difference btw verfication+ validation.
http://www.allinterview.com/showanswers/163.html

Validation
-----------
1) Am I building the right product
2) Determining if the system complies with the requirements
and performs functions for which it is intended and meets
the organization?s goals and user needs. It is traditional
and is performed at the end of the project.
3) Am I accessing the right data (in terms of the data
required to satisfy the requirement)
4) High level activity
5) Performed after a work product is produced against
established criteria ensuring that the product integrates
correctly into the environment
6) Determination of correctness of the final software
product by a development project with respect to the user
needs and requirements

Verification
------------
1) Am I building the product right
2) The review of interim work steps and interim
deliverables during a project to ensure they are
acceptable. To determine if the system is consistent,
adheres to standards, uses reliable techniques and prudent
practices, and performs the selected functions in the
correct manner.
3) Am I accessing the data right (in the right place; in
the right way).
4) Low level activity
5) Performed during development on key artifacts, like
walkthroughs, reviews and inspections, mentor feedback,
training, checklists and standards
6) Demonstration of consistency, completeness, and
correctness of the software at each stage and between each
stage of the development life cycle.