Re: [CMMi Process Improvement] Is walkthrough a validation technique?
It's an interesting question. Is a walkthrough a "peer review?" Just because the CMMI says peer reviews are part of VER, does that mean one can't be VAL?
I have a client that would like to validate their requirements by way of a "cranial use case." This technique involves a peer review of the requirements and each attendee describes a situation where the requirement might work (or not work in some cases). The group listens, debates the pros and cons, potential defects in the requirement, and then records issues that came up that could impact the requirements. These issues are delivered to the relevant stakeholders for consideration.
Is this a "review?" Yes, I think it is. Let's call it a "review plus." It's not quite a "simulation" or a "use case" though. But it sure feels like VAL to me.
Jeff
--- On Wed, 11/19/08, Robert Leinen <rob.leinen@...> wrote:
From: Robert Leinen <rob.leinen@...> Subject: Re: [CMMi Process Improvement] Is walkthrough a validation technique? To: cmmi_process_improvement@yahoogroups.com Date: Wednesday, November 19, 2008, 8:28 PM
It can be depending on the review criteria and audience.
It's an interesting question. Is a walkthrough a "peer review?" Just because the CMMI says peer reviews are part of VER, does that mean one can't be VAL? ...
Jeff, I don't perceive activities falling cleanly into verification OR validation; sometimes it has both (in varying degrees, perhaps, but both nonetheless). ...
Pat, I couldn't agree more. My example was intended to demonstrate that VER and VAL sometimes look and feel similar, and specifically that a "review" is not...
Pat, In your message below, you just disregard the intended environment part of VAL and reduced the VAL into involvement of customer/end user/or their...
Hello all, Very interesting conversation. Personally,I think a code walk through can be only a verification technique having to do with peer review. I think...
If it is performed with the (end) customer, with the intention to capture the intention of the customer, then yes, in my view. Andre. Groet, Gru, Regards, ...
Andre, You disappointed me. I was thinking you were the only one (other than me:) who really understood what VAL is all about, but you too reduced VAL into...
Hi Orhan, I think you missed the bit on "intended use" in the VAL purpose. Isn't the user/customer the only one who can determine what the intended use is? ...
Hi Andre, You did not miss the intended use part of VAL which is good but do you think it is a valid excuse to forget the other two parts: Intended ...
Orhan, You give yourself way too much credit. Peace _____ From: cmmi_process_improvement@yahoogroups.com [mailto:cmmi_process_improvement@yahoogroups.com] On...
Larry, You would think someone would at least be an LA or instructor before being so smug! Jeff Sent from my Verizon Wireless BlackBerry ... From: "Larry...
Orhan, You are participating in a forum attended by many experts with years of experience in this area, you are the only one that shares your interpretation of...
Rob, Orhan is also the only one who understands the "spirit" of CMMI. So VAL is not the only topic in which he is the expert. He appears to be making an...
Yes, Rob, there is something wrong here I should be either an idiot or a genius :) Pease, Orhan Toronto Http://groups.yahoo.com/group/SpiritofCMMI Sent from...
Karyn, On the other hand, when our testers get around to testing that requirement by putting the military radio in extreme cold for 6 or more hours, that would...
Orhan, When generating use cases, customers are projecting the use of the system in the intended environment and by the people intended to use it. Isn't that...
Pat, Yes, you are missing something :) - You are missing the importance of seeing the product or product component in the intended environment. I hope after ...
Orhan, I think we probably agree on this more than we disagree, but I also think we're coming at it from orthogonal view points. From my point of view, I...
Pat, You disappointed me, too :) Disappointment 1 - There are three attributes of Validation - 1) Intended use 2) Intended Environment 3) End product or...
Dear all, I think it is not the way of review (peer review, walkthrough, UAT...) to distinguish Var from Ver. It is decided by who did the activity. If the...
Actually, if the question being asked in a review or walkthrough is "will this work as needed in the future environment" as opposed to "is this doing what we...
An inspection is a structured team review of a software product. A walkthrough is less formal than an inspection. The product is presented to an audience that...
Do not forget the Heather's comment - Validation is interested in future and verification in past. To validate a work product we should create the future...
Inspection is formal & Tollgate review , an entry criteria for most of the validation task it is having structured process with defined roles for participant...
Hi, I like to view Validation as any activity that tries to catch defects introduced due to inherent limitations of the 'requirements definition process'....