Trang chủ segvn


In lúc 21:45:18 20-05-2012

Gửi bởi datpp lúc 09:50:22 04-02-2009
Re: CMMi Verification & Validation và Test
Bài này tôi viết cho báo nội bộ khi làm cho dự án CMMI của FSOFT năm 2005. Anh chị tham khảo. Hope it helps smile

To understand the concept
VERIFICATION versus VALIDATION
DatPP

These are 2 PAs (Process Area) belonging to Engineering Category that we know as VER and VAL. They are very similar – both are about checking if we go the right way. I have asked many FSOFT people if they can clearly tell one from another. Most (about 90%) could not give answers. The rest did, but not as clear as wanted (I checked by asking the others if they understand their colleague’s explanation – reply was negative). The popular e-dictionary also could not give any light. In this paper, I will try to explain as I understand. Discussion is welcome.



Let’s have a look at the picture. It begins from the customer’s need. Then they explain us, and we understand about their need. At the end, we make the product based on our understanding, and we hope the product will meet the customer’s need. Thus, the information undergoes 2 transformations T1 and T2, each of that can (and certainly will) cause information loss.

During the process of understanding the need and making the product, both sides have necessity of confirming whether the need was understood properly and the product is being made correctly. Here we reveal the difference between VER and VAL: verification happens when we check whether we make product according to our understanding, and validation - when we check (1) if we understand properly and (2) if the product meets the need. Because of that, they say VAL as “do the right thing” and VER as “do the thing right”.

So, have another look at the picture to see VAL and VER. To be sure that you understood their difference, just spend few minutes to do the exercise: mapping the below listed activities in FSOFT project to VER, VAL1 and VAL2 (Sample: code review by peer – VER): Requirement clarification with customer, external design review, unit test, system test, acceptance test.