I have a clarification regarding the CMM levels and Testing. From which level of CMM onwards testing is defined in the process? I dont really know this question is Good enough. I am asking this here in the forum because someone else has asked me this question and i felt that all levels have testing define. Correct me if I am wrong.
It looks like u r yet to give a close look in to CMM.
You can't really say where testing will come in Level wise. After all, Level's are for whole of the Organization.
If you go by the CMM Levels, Level 1 is characterized by Chaos. Nothing is defined. U may have a QA Team also. Still only when the suggested Processes are followed, they move to Level 2 from Level 1.
Any organization which doesn't follow any process is bound to fall under Level 1.(i.e Initial Level)
"CMM is a goal but not a method"
If you take Testing, its one of the several parts that constitute a Project Environment.
Its one of the Teams which would adhere to some specific well defined processes to acheive its own objectives.
An Organization or a Team may follow a defined model like for eg..V-model.Only in the model can one say where Testing Phase starts or plays a crucial role.If you take V-model into consideration, Testing/QA starts from the very beginning. It starts right from the Requirements Analysis Level.
This holds good only when Testing and QA can be used mutually. Actually going by the defenitions,
QA and Testing can be used mutually and only QC is different from QA.
I would suggest you to go thru the CMM document
which is available in the SEI site specified by JP.
if you are interested,I can send across a presentation about the basics of the CMM, which may be of some use to you.
I would be very much interested in reading through the presentation that youve done about CMM. I was working in a CMM level 5 company earlier, but I dont find any differences in processes with the company which Im working for now (which is not assessed for CMM. So am trying to research whether CMM is worthwhile.
I dont mind sending the presentation to you. But it looks like you have already worked for a CMM Level 5 Company. So u may dont find anything new and interesting. Offcourse, it tell you the Basics of CMM and elaborates the KPA's involved in all Levels.
Get back to me if you want and let me know how do i send it across to u.
I dont mind sending the presentation to you. But it looks like you have already worked for a CMM Level 5 Company. So u may dont find anything new and interesting. Offcourse, it tells you the Basics of CMM and elaborates the KPA's involved in all Levels.
Get back to me if you still need it and let me know how do i send it across to u.
CMM doesn't tell much in detail about testing. Most of the key process areas have a relation with testing.
E.g. there are test activities to define during project planning. These must be monitored during 'project monitoring'. In the 'Software Product Engineering' process area there are also some references to testing. In requirements development you need to think about quality requirements such as testability. Configuration management talks about a suitabile environment for testing. Etc.
The newer model CMMI is more specific about testing activities. In fact they have 2 process areas: 'Verification' and 'Validation'.
Personally I'm currently using another approach: I selected a model that is only about testing, and then I mapped it to the CMMI. In fact I use CMMI to see what processes and process requirements are necessary when implementing the other model.
Now the model I used is TPI (Test Process Improvement - more information on http://www.sogeti.nl/index.html?/ios....cfm?uNr=151). But there are other models on the market such as TMM (Test Maturity Model)