Dear all, I would like to just add one more statement here. Any template is a part of the process document itself. so, as and when the process document...
Hi, Yes, there is something called a Review Process, either for Document Review or Code Review. I am listing down 3 the steps for the same here: 1. For review,...
Hi, Suggest that you try a Google on "Fagan Inspection Methods" This will provide you with a lots of insights into the Best Guidelines for conducting Effective...
Verification is performed throughtout the life cycle of project to assure the quality of the product. Formal Technical Review of Requirements Design Review /...
Amar Gangwani
mr@...
Jan 2, 2006 6:12 pm
5077
Hi Mahesh, I think you are somewhat confused with the revision history. Actually the revision history of a particular template reveals what changes have been...
hi i have following two problems/confusions. 1. When we write "Description of Processes" its usually .. Purpose Scope Entry Criteria Tasks [Validations] Exit...
Hi Sudha, 1)- To Conduct a Review, there has to a process and guideline Complete Review process - starting from having a Draft version; self review;identifying...
Amar, Although I agree with your statement about Verification, I have to take exception with your position limiting Validation solely to UAT. I believe that...
Just to put this in perspective, I don't perceive Revision History of ANY document, template or otherwise, to be REQUIRED. Rather, I think we're simply...
Pat's right. I've been to lots of organizations that claim they do no validation. Then I ask them "how do you that what you deliver will work for the...
Hi All, One of the challenges I am currently facing is to define criteria and an algorithm to automatically qualify users requests, into something like: -...
Pieber, Eduardo
eduardo.pieber@...
Jan 3, 2006 2:55 am
5085
What Pat has said is absolutely correct. In IBM we have a regular validations in all the phases, i.e. right from the design to production. But for a through...
Dear Saurabh Gupta It is not neccessary that we maintain revision history for changes that have been made in the contents of the template. As we maintain all...
hi prepare a simple template of CHANGE REQUEST,give it to your customer,this template should indicate three typoes of change,the customer should tick the right...
Hi Amit, An object model is a static representation of the system resolution area considered. In a practical term, its the class diagram arrived after detailed...
Dear Bilal I am working as software configuration managmenet engineer in kalsoft pakistan limited. Can you please send us the outline for this CMMI course, as...
The outline for the SEI's "Intro to CMMI" course is attached. If this attachment did not come through, send an email to PACT.otoole@... and I'll be happy...
Rashid, Let me answer your question with a question - would you consider a developer signing off on the Functional Spec to consistitute a "peer review?" Let me...
Hi All, What are differences between data management and CM? In practice, can i combine these two, e.g. store project data to CM libraries ? if so, which...
Thanks for the response guys. But i still have one question regrading validation. For Example If we are doing design inspection in design phase def the...
Amar Gangwani
mr@...
Jan 3, 2006 2:28 pm
5095
Hi Nizar, I agree with you. But what we follow is that if there is a change in the template then we update the revision history of the relevant process...
Hi All, I do agree with Mizra's view. One of the outputs of the Confuguration Management process is traceability on the work products. i.e For each and every...
your definitions are the reverse of the CMMI. Verification is conformance with requirements, and that would include insuring that the design implements the...
the difference is level of formality. By all means combine them if it makes sense. Just don't mandate over rigorous change control on in-work items or make...
In addition to Suzanne's comments, take a look at what the informative material for PP SP2.3 considers 'data:' "Data are the various forms of documentation...
I usually call it "all the stuff your project produces that you need to not lose....." Pat's right, things like measures, correspondence, parts, and hard copy...
I always told my organization it was the non-configuration item stuff the project produces (minutes, notes, email, etc.) that could answer a question later on...