Quality management tin software engineering with respect to S.Q.C., S.Q.P., S.Q.A. ISO QUALITY Factors, McCall's Quality Factors, Garvin's Quality Factors and all aspects about quality in software engineering.

1. Quality Management in Software
Engineering
Quality, Garvin’s Quality Dimensions, ISO 9216 Quality Factors,
McCall’s Quality Factors, SQP, SQA, SQC
ZAIN-UL-ABIDEEN
1

2. Quality (School of Business Point of Views)
• Transcendental view
• User view
• Manufacture’s view
• Product view
• Value based view
ZAIN-UL-ABIDEEN
2

3. Quality (Transcendental View)
• This view argues that quality is something you immediately
recognize through experience but can not explicitly define in some
tractable view.
• A good quality objects stands out, and is easily recognized.
ZAIN-UL-ABIDEEN
3

4. Quality (User View)
• Quality inn terms of end user’s specific goals.
• If a product meets these goals
ZAIN-UL-ABIDEEN
4

5. Quality (Product View)
• Quality can be tied to inherent
characteristics(example: Functions
and features) of a product.
ZAIN-UL-ABIDEEN
5

6. Quality (Value Based View)
• This measures how much a consumer is willing to pay for a
product.
ZAIN-UL-ABIDEEN
6

7. Software Quality
SQM, Garvin’s Quality Dimensions
ZAIN-UL-ABIDEEN
7

8. Software Quality
• An effective software process applied in a manner that creates a
useful product that provide measurable values for those who
produce it and those who use it.
ZAIN-UL-ABIDEEN
8

9. Software Quality Management
Software quality management (SQM) is a management process that
aims to develop and manage the quality of software in such a way
so as the best ensure the product meets the quality standards
expected by the customer while also meeting any necessary
regulatory and developer requirements, if any. Software quality
managers require software to be tested before it is released to the
market, and they do this using a cyclical process-based quality
assessment in order to reveal and fix bugs before release
ZAIN-UL-ABIDEEN
9

10. Garvin’s Quality Dimensions
• Performance Quality: Does the software deliver all content
functions and features?
• Feature Quality: Does the software provide features that surprise
and delight user first time end users?
• Reliability: Does the software deliver all features and capability
without failure? Does it deliver functionality that is error free
ZAIN-UL-ABIDEEN
10

11. Garvin’s Quality Dimensions
• Conformance: Does the software conform to local and external
software standards that are relevant to the application?
• Durability: How much software is durable.
• Serviceability: Can a software be maintained or corrected in an
acceptably short time period.
ZAIN-UL-ABIDEEN
11

12. Garvin’s Quality Dimensions
• Aesthetics: How much our software is interesting?
• Perception: In some situation, you have a set of prejudices that
will influence tour perception of quality.
ZAIN-UL-ABIDEEN
12

13. ISO 9216 Quality Factors
ZAIN-UL-ABIDEEN
13

14. ISO 9126 Quality Factors
• Functionality
• Reliability
• Usability
• Efficiency
• Maintainability
• Portability
ZAIN-UL-ABIDEEN
14

15. ZAIN-UL-ABIDEEN
15

16. ISO 9126 Quality Factors
• Functionality – “A set of attributes that bear on the existence of a
set of functions and their specified properties. The functions are
those that satisfy stated or implied needs.”
• Reliability- "A set of attributes that bear on the capability of
software to maintain its level of performance under stated
conditions for a stated period of time."
ZAIN-UL-ABIDEEN
16

17. ISO 9126 Quality Factors
• Usability - "A set of attributes that bear on the effort needed for
use, and on the individual assessment of such use, by a stated or
implied set of users.“
• Efficiency- "A set of attributes that bear on the relationship
between the level of performance of the software and the amount
of resources used, under stated conditions."
ZAIN-UL-ABIDEEN
17

18. ISO 9126 Quality Factors
• Maintainability- "A set of attributes that bear on the effort
needed to make specified modifications."
• Portability- "A set of attributes that bear on the ability of
software to be transferred from one environment to another."
ZAIN-UL-ABIDEEN
18

19. McCall’s Quality Factors
ZAIN-UL-ABIDEEN
19

20. McCall’s Quality Factors
ZAIN-UL-ABIDEEN
20

21. ZAIN-UL-ABIDEEN
21

22. Achieving Quality
ZAIN-UL-ABIDEEN
22

23. Achieving Software Quality
• Software Quality Plan
• Software Quality Control
• Software Quality Assurance
ZAIN-UL-ABIDEEN
23

24. Software Quality Plan
• Process of developing quality plan for a
project.
• Defines quality requirements of software.
• Describes how these are assessed.
• A quality plan describes how an organization
will achieve its quality objectives.
ZAIN-UL-ABIDEEN
24

25. Software Quality Plan
• Techniques and tools used to ensure that a product meets the
requirements specified in software requirements specification.
• The quality plan selects those organizational standards that are
appropriate to a particular product and development process.
• Quality plans should be short, succinct documents
• If they are too long, no-one will read them
ZAIN-UL-ABIDEEN
25

26. Software Quality Plan
Qulaity plan has following parts:
• Introduction of product.
• Product plans.
• Process descriptions.
• Quality goals.
• Risks and risk management
ZAIN-UL-ABIDEEN
26

27. Software Quality Assurance
ZAIN-UL-ABIDEEN
27

28. Software Quality Assurance
• A set of activities for ensuring quality in software engineering
processes (that ultimately result in quality in software products).
The activities establish and evaluate the processes that produce
products.
• Process focused
ZAIN-UL-ABIDEEN
28

29. Software Quality Assurance
• Prevention oriented
• Organization wide
• Relates to all products that will ever be created by a process
ZAIN-UL-ABIDEEN
29

30. Software Quality Assurance
• SQA Activities
• Process definition and implementation
• Auditing
• Training
ZAIN-UL-ABIDEEN
30

31. Software Quality Assurance
• SQA Processes
• Software Development Methodology
• Project Management
• Configuration Management
• Requirements Development/Management
• Estimation
• Software Design
• Testing
ZAIN-UL-ABIDEEN
31

32. Software Quality Control
ZAIN-UL-ABIDEEN
32

33. Software Quality Control
• A set of activities for ensuring quality in software products.
Software Quality Control is limited to the Review/Testing phases
of the SDLC and the goal is to ensure that the products meet
specifications/requirements.
ZAIN-UL-ABIDEEN
33

34. Software Quality Control
• Product focused
• Detection oriented
• Product/project specific
• Relates to specific product
ZAIN-UL-ABIDEEN
34

35. Software Quality Control
• SQC Activities
1. Reviews
• Requirement Review
• Design Review
• Code Review
• Deployment Plan Review
• Test Plan Review
• Test Cases Review
ZAIN-UL-ABIDEEN
35

36. Software Quality Control
• SQC Activities
2. Testing
• Unit Testing
• Integration Testing
• System Testing
• Acceptance Testing
ZAIN-UL-ABIDEEN
36

37. Conclusion
• Quality management in software engineering is that a software should be
good in quality.
• This tells about the process or steps to be followed and build a good
enough software.
• The quality management system under which the software system is
created is normally based on one or more of the following
models/standards:
• CMMI
• Six Sigma
• ISO 9000
• SQP, SQA, SQC are used for achieving quality.
ZAIN-UL-ABIDEEN
37