Prince Georgeís Community College
NASA Goddard/PGCC Space Technology Institute
Quality Assurance Option
ENT 201 Quality Assurance II.3 College credits
Principles of Configuration Management and Project Integrity.
This course will study Configuration Management (CM). This will include CM principles and implementation, project integrity assurance, and the ISO 9000 Quality Standard CM requirements. Hardware, software, and firmware applications will be developed and will be illustrated by a comprehensive case study. Three class hours/week for 15 weeks.
Note: ENT 201 is part of the core Quality Assurance (QA) sequence of courses. The QA course sequence serves both as preparation for ASQ professional certification, and towards a degree. The other courses in the core QA sequence are ENT 186, ENT 171, ENT 192, and ENT 202. Refer to the college catalog for the complete list of degree requirements.
Textbook:Implementing Configuration Management: Hardware, Software, Firmware, 2nd Edition, Fletcher Buckley.
Location:Largo, MD campus
Registration:PGCC main campus, Bladen Hall. 301 Largo Road, Largo, MD (301) 322-0819
College Contact:Professor Charles Hendrickson, CQE (301) 322-0760. PG College Engineering Technology Faculty member. Email at firstname.lastname@example.org
Instructor:Joe Ludford, CQE, CRE, CSQE, CQM (301) 843-3087. Joe is on the executive board of the Washington DC chapter of the American Society for Quality (ASQ), and is the owner and principal consultant of White Hart Associates. Joe has a distinguished teaching background. Email at Jludford@radix.net
Major Topics To Be Covered
Configuration Management: Hardware, Software, and Firmware applications
Additional topics- detailed objectives
EXPECTED COURSE OUTCOMES: The student will be able to explain:
1. The purpose and function of configuration management (CM) and its place in a quality system. Relevance of CM to the ISO 9000:2000 Intíl Quality Standards.
2. Exercise of CM and project integrity
3. The CM environment: hardware, software, firmware processes
4. Configuration identification (ID) including baselines, selection, inputs, process outputs, and a software CM library (SCML)
5. Configuration status and be able to describe a CM database
The student will be able to implement:
6. CM planning activities: CM and project metrics, procedures
7. CM document controls including ID and classifications
8. Configuration controls: problem reporting, failure analysis, corrective action, evaluation, coordination, approvals, and changes.
9. Configuration control of hardware: nonconforming materials &n product, retrofits
10. Configuration control of software: vendor considerations, product support, maintainability, CM library
11. Configuration control documentation (CC)
∑ Changes to base-lined: items, hardware, software, firmware, documents, drawings
∑ CC documents, engineering change notice and approval, deviations, waivers, specification changes
∑ Automating process improvements
12. Configuration status using a CM database
13. CM and facility: establish requirements, resources
14. Configuration auditing: functional, physical, in-process audits
15. The student will develop a comprehensive CM implementation for an assigned project involving all of the important CM functions studied. Student will present this project to the class.
Week 2 CM environment: hardware, software, firmware. CM planning. Configuration items.
Week 3 Configuration identification: baselines, selection, CM library. Hardware, software, firmware ID considerations.
Week 4 Document controls, ID, and classifications
Week 5 Examination
Week 6 Configuration controls: hardware nonconforming materials and product; software product support, maintainability, vendor considerations
Week 7 Configuration controls: control board, configuration status accounting
Week 8 CM applied to production: CMP, material review board, problem resolution board
Week 9 Configuration control (CC) documentation: changes to base-lined items, hardware, software, firmware, documents, drawings, engineering change notices, deviations, waivers, specification changes and approval
Week 10 Examination
Week 11 CM software commonly used for documentation and implementation. Automated CM practices and PDM.
Week 12 CM planning and auditing: functional, physical, and in-process audits
Week 13 CM implementation and facility: establish requirements, resources, and implementation of plan.
Week 14 Review CM functions. Demonstrate when and how each configuration control should be implemented. Students will present their CM implementation projects to the class.
Week 15 Examination- comprehensive
Practical CM: Best Configuration Management Practices for the 21st Century, 4th edition By: David D. Lyon Raven Publishing, 866-443-6533 http://www.configuration.org D_Lyon@compuserve.com ISBN 0966124820