This PPT contains the topic called The Quality Standard: ISO 9000 , CMM and Six Sigma of the subject called Software Engineering

1. Presentation on
The Quality Standards: ISO
9000,CMM,Six Sigma
 Presented By :
• Deep Dalsania
(160350116002)
• Subject Name:
Software Engineering
• Subject Code: 2160701
• Submitted To:
Prof. Deep Patel

2. Outline
•What is Quality Standards
•ISO 9000
•Capability Maturity Model (CMM)
•Six Sigma

3. What is Quality Standards
•American National Standard Institute (ANSI) talks about
standards as the base of a module on which the correctness or
accuracy of others modules can be determined through thorough
comparison and contrasting.
•Software engineering is a vast field, and the products created by
software engineers must be of upmost quality. For this quality to
be achieved, correct measures and grading standards must be
followed, so as to achieve excellent products.

4. ISO 9000
•It stands for International Organization for
Standardization.
•ISO 9000 was created to produce an international
set of process quality standards.
•First published in 1987
•These are standards for quality management and
quality assurance for any business. It applies to
process of creating, and controlling of products and
services an organization provides, by giving an
organized course for activities to be carried out to
ensure that customer’s requirements are made

5. Who uses ISO 9000
• Department of Food and Drug Administration,
Energy, Defense, NASA, GSA
• Qualcomm, Cisco, IBM
• Adopted by the US as The American National
Standards Institute (ANSI)/ASQC Q90 series
• US motor carrier industry
• Fed-Ex
• Banking, Healthcare, Manufacturing, Software,
Service, etc.

6. Main Features of ISO 9000
• Objective: "To promote the development of standardization
and cooperation in the spheres of intellectual, scientific,
technological and economic activities"
• ISO 9000 – concepts behind the management systems It is a
set of standards for quality management and quality
assurance
• ISO 9001 - Model for Quality Assurance in
Design/Development, Production, Installation, and
Servicing
• Generic
• Consistency between processes and results.
• Internal and external benefits

7. Main Features of ISO 9000
• It is based on eight Quality Management Principles
– Customer-Focused Organization
– Leadership
– Involvement of people
– Process Approach
– System Approach
– Factual Approach
– Continual Improvement
– Mutually beneficial supplier relationship
• Customer satisfaction from design through service.

8. Capability Maturity Model (CMM)
• This model describes good practices for
planning, engineering and managing
software development. This practice allows
software engineering organizations to create
quality software while minimizing budget
and time factors. CMM allows software
engineers to judge and compare its processes
to stated practices in the industry.

9. What is CMM?
• Capability Maturity Model is used as a benchmark
to measure the maturity of an organization's
software process.
• CMM was developed at the Software engineering
institute in the late 80's. It was developed as a
result of a study financed by the U.S Air Force as a
way to evaluate the work of subcontractors.

10. What is Capability Maturity
Model (CMM) Levels?

11. • Level 1 (Initial): Where requirements for the system
are usually uncertain, misunderstood and
uncontrolled. The process is usually chaotic.
• Level 2 (Managed): Estimate project cost, schedule,
and functionality. Software standards are defined
• Level 3 (Defined): Makes sure that product meets
the requirements and intended use
• Level 4 (Quantitatively Managed): Manages the
project's processes and sub-processes statistically
• Level 5 (Maturity): Identify and deploy new tools
and process improvements to meet needs and
business objectives

13. How long does it Take to
Implement CMM?
• Typical times for implementation is
3-6 months -> for preparation
6-12 months -> for implementation
3 months -> for assessment preparation
12 months ->for each new level

14. Limitations of CMM Models
• CMM determines what a process should address
instead of how it should be implemented
• It does not explain every possibility of software process
improvement
• It concentrates on software issues but does not consider
strategic business planning, adopting technologies,
establishing product line and managing human
resources
• It does not tell on what kind of business an organization
should be in
• CMM will not be useful in the project having a crisis
right now

15. Six Sigma
• According to David Card, (IEEE Software 2000),
Six sigma is “A generic quantitative approach to
improvement that applies to any process.”
• “Six Sigma is a disciplined, data-driven approach
and methodology for eliminating defects (driving
towards six standard deviations between the mean
and the nearest specification limit) in any process --
from manufacturing to transactional and from
product to service.”
• Six Sigma is a highly disciplined process that helps
us focus on developing and delivering near-perfect
products and services.

16. Key Concepts of Six Sigma
• Critical to Quality − Attributes most important to
the customer.
• Defect − Failing to deliver what the customer
wants.
• Process Capability − What your process can
deliver.
• Variation − What the customer sees and feels.
• Stable Operations − Ensuring consistent,
predictable processes to improve what the
customer sees and feels.
• Design for Six Sigma − Designing to meet
customer needs and process capability.

17. Myths about Six Sigma
• Six Sigma is only concerned with reducing
defects.
• Six Sigma is a process for production or
engineering.
• Six Sigma cannot be applied to engineering
activities.
• Six Sigma uses difficult-to-understand statistics.
• Six Sigma is just training.

18. Six Sigma Methodology
• DMAIC Methodology
• DMADV or DFSS Methodology

19. DMAIC Methodology
• Define --> Measure --> Analyze --> Improve -->Control
• Define − Define the problem or project goal that needs to be
addressed.
• Measure − Measure the problem and process from which it was
produced.
• Analyze − Analyze data and process to determine root causes of
defects and opportunities.
• Improve − Improve the process by finding solutions to fix, diminish,
and prevent future problems.
• Control − Implement, control, and sustain the improvements
solutions to keep the process on the new course.

20. DMADV or DFSS Methodology
• Define --> Measure --> Analyze --> Design -->Verify
• Define − Define the Problem or Project Goal that needs to
be addressed.
• Measure − Measure and determine customers needs and
specifications.
• Analyze − Analyze the process to meet the customer needs.
• Design − Design a process that will meet customers needs.
• Verify − Verify the design performance and ability to meet
customer needs.

21. Benefits of Six Sigma
• Generates sustained success
• Sets a performance goal for everyone
• Enhances value to customers
• Accelerates the rate of improvement
• Promotes learning and cross-pollination(is to
bring these people together their knowledge and
skills to influence each other).
• Executes strategic change
• Example: Mumbai Dabbawala

22. References
• https://sites.google.com/site/advancedsofteng/
quality-in-software-engineering/quality-
standards
• https://www.guru99.com/capability-maturity-
model-cmm-cmm-levels-a-fool-s-guide.html
• https://www.tutorialspoint.com/six_sigma/inde
x.htm
• https://en.wikipedia.org/wiki/Six_Sigma

23. Thank You
Any Question ?