You are on page 1of 23

Quality Standards

Software Engineering
Prepared by: xxx First Prepared on: xx-xx-xx Last Modified on: xx-xx-xx
Quality checked by: xxx
Copyright 2004 Asia Pacific Institute of Information Technology
Software Quality Engineering
CT051-3.5-3
Module Title?
Topic Title ?
Slide 2 of 10
Topic & Structure of the lesson
Why standards are needed
Types of standards documentation,
design, code
Standard models ISO, CMMI

Module Title?
Topic Title ?
Slide 3 of 10
Learning Outcomes
By the end of this lecture, YOU should be
able to :
Explain why standards are important
Document different type standards
such as documentation, design and
code
Explain ISO and CMMI


Module Title?
Topic Title ?
Slide 4 of 10
Key Terms you must be able to use
If you have mastered this topic, you should
be able to use the following terms correctly
in your assignments and exams:

Quality standard
International Standard Organisation
Capability Maturity Model Integrated
Module Title?
Topic Title ?
What is a standard?
Technical agreements
Framework for compatible technology
worldwide
Best practices or state of the art
Context dependent, e.g., measures (meter),
mains (230 V, 50Hz AC), phone standards
(Global System for Mobile communication
(GSM), protocols (IP)
Module Title?
Topic Title ?
Why are standards necessary
Achieve interoperability
Common understanding
Business advantages
Module Title?
Topic Title ?
Categories of Standards
De facto standards
no officially authorized standard
standards followed by convenience
so dominant that everybody seems to follow it
Open standards
available to general public, non-profit/royalty free
E.g., GSM, (Peripheral Component Interconnect
(PCI)), (Accelerated Graphics Port (AGP)), HTML,
Proprietary standards
Not open/available to general public for fees,
most/all of ISO standards
Module Title?
Topic Title ?
Documentation Standards
With out the documentation the software is
useless.
Once created, like software must be
maintained and supported to eliminate
errors and must include any changes
made to the software.
Documents are created for various
purposes.
Requirement and design documents.
Project management documents.
Module Title?
Topic Title ?
Documentation Standards
Four functions to manage documentation.
There should be a documentation plan.
(schedule ,when this documents will produce and
who are the responsible person..)
Standards for the documentation must be
established. (Table of content)
Procedures must be established to ensure that
documentation standards are being followed.
After approval docs must be placed under a change
control to track and monitor any change that may
occur in future.

Module Title?
Topic Title ?
Documentation Standards
Module Title?
Topic Title ?
Software Quality Standards 1
ISO 9000 Standard family
Quality improvement and management
ISO 9000 9004
ISO/IEC 15504
Software engineering standard
Requirements for assessments and process
model
Module Title?
Topic Title ?
Software Quality Standards 2
CMMI
Process model
Reference model of mature practices in a
specified discipline
Improve and apprise a groups capability to
perform that discipline
SCAMPI
Assessment method
Covers CMMI
Slide 12 of 10
Module Title?
Topic Title ?
Software Quality Standards 3
ISO/IEC 12207
Process model
Defines requirements for acquisition, supply
development, operation, and maintenance of
software
SPICE
Assessment method
Covers ISO 12207
Slide 13 of 10
Module Title?
Topic Title ?
Software Quality Standards 4
ISO/IEC 9126
Software quality standard
Defines characteristics representing software
quality and a connecting model
Slide 14 of 10
Module Title?
Topic Title ?
ISO 9000
Standard family ISO 9000-9004
ISO 9000:2005 Quality management systems
Fundamentals and vocabulary
ISO 9001:2000 Quality management systems
Requirements
ISO 9004:2000 Quality management systems
Guidelines for performance improvement
ISO 90003:2004 Quality management and
quality assurance standards
Slide 15 of 10
Module Title?
Topic Title ?
ISO 9000
General standard, not specific to software
engineering
Enables companies to meet specific
requirements
Aims at customer satisfaction
Ordered and systematic way (procedures)
Slide 16 of 10
Module Title?
Topic Title ?
Capability Maturity Model Integration
Process model
Specific to Software engineering, systems engineering, integrated
product and process development, and supplier sourcing
Mature practices in a specified discipline
Improve and apprise a groups capability to perform a discipline
structures approaches and best practices
Covers 24 process areas related to process capability and
improvement
Goal specify common features associated with maturity levels
Practices describe how goals can be achieved
Assessment method: SCAMPI
Slide 17 of 10
Module Title?
Topic Title ?
18
CMMI Maturity Levels
Level 1. Initial chaotic unpredictable (cost, schedule,
quality)
Level 2. Repeatable intuitive; cost/quality highly
variable, some control of schedule, informal/ad hoc
procedures.
Level 3. Defined qualitative; reliable costs and
schedules, improving but unpredictable quality
performance.
Level 4. Managed quantitative reasonable statistical
control over product quality.
Level 5. Optimizing quantitative basis for continuous
improvement.
Module Title?
Topic Title ?
Slide 19 of 10
Quick Review Question
Question 1
Can an organisation skip a maturity level?

Question 2
Discuss the benefits of CMM in a software
development organisation.
Module Title?
Topic Title ?
Slide 20 of 10
Tutorial 4
1. Explain in detail TWO KPAs of CMMI
Level 3.
2. Compare and contrast between CMMI
and ISO/IEC 15504



Module Title?
Topic Title ?
Slide 21 of 10
Summary of Main Teaching Points
1. Why standards are needed
2. Types of standards documentation,
design, code
3. Standard models ISO, CMMI

Module Title?
Topic Title ?
Slide 22 of 10
Q & A
Question and Answer Session
Module Title?
Topic Title ?
Slide 23 of 10
Next Session

Software Quality Activities and Techniques