Quality Engineering

notes.md

• A Brief History of Quality: How the Concept of Quality has Evolved
• 14 Steps of Philip Crosby
  1. ensure management buy-in
  2. create the quality-improvement team
  3. measure quality in current processes
  4. determine or estimate cost of quality
  5. raise employee awareness
  6. take corrective action
  7. establish a zero-defect policy
  8. practice quality training for supervisors
  9. hold a zero-defects day
  10. involve everyone in goal-setting -- but isn't the goal zero-defects? And haven't we reached it?
  11. remove causes of error; encourage open communication about risks
  12. recognize participants' effort
  13. create quality councils
  14. repeat
• The History of Quality Management
• History of Quality
• Total Quality. "Rather than relying purely on product inspection, Japanese manufacturers focused on improving all organizational processes through the people who used them." "The U.S. response, emphasizing not only statistics but approaches that embraced the entire organization, became known as Total Quality Management (TQM)."
• Software Quality Engineer Certification CSQE
  • sample exam; I got 57/75, with the most wrong in Verification & Validation and Configuration Management
  • covered body of knowledge
• Introduction to Software Engineering/Quality
  • quality of conformance: implementation
  • quality of design: worthwhile product
  • software quality: correctness, product quality, scalability, completeness, absence of bugs, fault-tolerance, extensibility, maintainability, documentation
  • source code quality: readability; ease of maintenance, testing, debugging, fixing, modification and portability; low complexity; low resource consumption; number of compilation or lint warnings; robust input validation and error handling
  • reliability: fault-free operation in a specified environment for a specified time
• Software Quality
  • "The goal for checking and monitoring Reliability is to reduce and prevent application downtime, application outages and errors that directly affect users, and enhance the image of IT and its impact on a company's business performance."
  • "An analysis of source code efficiency and scalability provides a clear picture of the latent business risks and the harm they can cause to customer satisfaction due to response-time degradation."
• Common Weakness Enumeration
• Moving from Quality Assurance to Quality Engineering
• Quality Assurance and Software Testing: A Brief History
• Which software testing certifications are worth taking?
• Juran's Quality Control Handbook