I would like to implement a structured unit testing strategy and am going to be using this as a means of ongoing software validation.

My company is currently working to be compliant with ISO9001:2000 along with CMMI Level 3 and what I would really be interested in hearing other organizations experiences with unit testing within the ISO/CMMI frameworks.

Also as the software area seems pretty slow lately I thought this might be a good conversation starter.

--
Thanks
Blaine

Any takers on this post?

Yes - The software forum has never been real popular here.

Coming up with a Plan for implementing Software Quality Assurance Activites is a hard JOB. You need to know the Processes in your company indepth.
Quality Assurance in software development does not mean just software Testing. Software Testing just helps you find Bugs/errors. But Wat you do to Prevent errors from occuring in first Place is very Important.
People think more about solving problems(High Visibility), but i personally feel that people must start think about preventing problem(Low visibility).
The biggest Problem that software companies faces is completing the software for the end user for acceptance test, b4 the dead-line arrives.
But a Well Planned Software Development Process, backed by Quality Assurance Activites can help Reduce the SDLC(Software Development Life cycle) including the Testing and Maintenance COST(in terms of time and hence Revenue).

Upendra Purao.
(Lead Auditor ISO 9001-2000)
:agree1:

I would like to implement a structured unit testing strategy and am going to be using this as a means of ongoing software validation.

My company is currently working to be compliant with ISO9001:2000 along with CMMI Level 3 and what I would really be interested in hearing other organizations experiences with unit testing within the ISO/CMMI frameworks.

Also as the software area seems pretty slow lately I thought this might be a good conversation starter.

--
Thanks
Blaine

Coming up with a Plan for implementing Software Quality Assurance Activites is a hard JOB. You need to know the Processes in your company indepth...
To introduce a new software QA process, it depends on the size of the organization and the risks involved. For large organizations with high-risk projects, a serious management buy-in is required and a formalized QA process is necessary. For medium size organizations with lower risk projects, management and organizational buy-in and a slower, step-by-step process is required. Generally speaking, QA processes should be balanced with productivity, in order to keep any bureaucracy from getting out of hand. For smaller groups or projects, an ad-hoc process is more appropriate. A lot depends on team leads and managers, feedback to developers and good communication is essential among customers, managers, developers, test engineers and testers. Regardless the size of the company, the greatest value for effort is in managing requirement processes, where the goal is requirements that are clear, complete and testable.

I hope this helps.

Regards,

Rob
Software QA Engineer