Login
Username:

Password:


Lost Password?
Register now!
Page « 1 ... 3 4 5 (6) 7 »
Articles : Configuration Management and ISO 9001
on 2008/1/18 12:41:43 (3057 reads)
Articles


Summary - ISO 9001 and configuration management

As described in the preceding paragraphs, of the 20 sections of ISO 9001 that define a supplier's capability to meet customer requirements, CM practices directly impact the following. The [x] marks in the following table indicate clauses of ISO 9001 that are addressed by CM practices.

Section of ISO 9001
   
4.1  Management responsibility [x]
4.2 Quality system [x]
4.3 Contract review  
4.4 Design control[x]
4.5 Document and data control [x]
4.6 Purchasing [x]
4.7 Control of customer-supplied product [x]
4.8 Product identification and traceability [x]
4.9 Process control [x]
4.10 Inspection and testing  
4.11 Control of inspection, measuring and test equipment  
4.12 Inspection and test status [x]
4.13 Control of nonconforming product [x]
4.14 Corrective and preventive action [x]
4.15 Handling, storage, packaging, preservation and delivery [x]
4.16 Control of quality records [x]
4.17 Internal quality audits  
4.18 Training   
4.19  Servicing [x]
4.20  Statistical techniques [x]

 

In terms of improved efficiency, major opportunities exist in ensuring that the CM, project management, customer technical support, build management, and problem reporting and tracking systems are as tightly coupled as possible.

Beyond CM - Product Attributes and Tool Selection

Nothing in ISO 9001 requires that a specific tool or technology be employed. ISO's sole concern is that the implemented systems be effective in delivering the promised product or service. Tools that automate CM practices may improve the effectiveness and will improve the efficiency of systems that require significant manual intervention.

From an ISO implementation perspective, automation represents an opportunity to:
* Reduce process and project documentation
* Reduce requirements for training
* Ensure that required steps are completed
* Record progress and activity

The tool selection process should ensure that the selected tools support the current or planned software engineering practices. While some minor changes to engineering practices may be required (especially if standard tools with minimum customization are selected), the tools cannot be the basis for formulating engineering practices.

Page « 1 ... 3 4 5 (6) 7 »
Printer Friendly Page Send this Story to a Friend Create a PDF from the article


Bookmark this article at these sites

                   

Polls
Do you use tools to execute functional tests?
My organisation has no tool for functional software tests
My organisation has tools, but my project or I do not use them
I use tools
Jobs

Resources: Methods & Tools | SD Tools | SD Articles | SD Directory | SD Videos | SD Jobs | DevAgile | DevBazar | Ajax Alliance | SD News | SD Conferences
SD Blogs | Forum Logiciel | Software Project Planet | SQA Planet | UML Planet | Cloud Voices | Java TV | .NET TV | Testing TV | TV Agile | RIATube
Java Voices | .NET Voices | PHP Voices | DBA Voices | Agile Voices | Scrum Planet | Ajax Voices | RIA Voices | The Waterfall Manifesto