quality management

1. 1

2. 2

3. 3
Software Quality Management ensures that the required
level of quality is achieved by submitting improvements to
the product development process. SQA aims to develop a
culture within the team and it is seen as everyone's
responsibility.
Software Quality management should be independent of
project management to ensure independence of cost and
schedule adherences. It directly affects the process quality
and indirectly affects the product quality.

4. 4
 Quality Assurance - QA aims at developing
Organizational procedures and standards for quality
at Organizational level.
 Quality Planning - Select applicable procedures and
standards for a particular project and modify as
required to develop a quality plan.
 Quality Control - Ensure that best practices and
standards are followed by the software development
team to produce quality products.

5. 5

6. 6
Software quality assurance (SQA) is a process which
assures that all software engineering processes,
methods, activities and work items are monitored and
comply against the defined standards. These defined
standards could be one or a combination of any like ISO
9000, CMMI model, ISO15504, etc.
SQA incorporates all software development processes
starting from defining requirements to coding until
release. Its prime goal is to ensure quality.

7. 7
The software quality assurance plan
comprises of the procedures, techniques,
and tools that are employed to make sure
that a product or service aligns with the
requirements defined in the SRS(software
requirement specification).

8. 8

9. 9
 Purpose section
 Reference section
 Software configuration
management section
 Problem reporting and corrective
action section
 Tools, technologies and
methodologies section
 Code control section
 Records: Collection, maintenance
and retention section
 Testing methodology

10. 10
SQA Management Plan:
Make a plan for how you will carry out the sqa
through out the project. Think about which set
of software engineering activities are the best
for project. check level of SQA team skills.
Set The Check Points:
SQA team should set checkpoints. Evaluate
the performance of the project on the basis of
collected data on different check points.

11. 11
Multi testing Strategy:
Do not depend on a single testing approach. When you
have a lot of testing approaches available use them.
Measure Change Impact:
The changes for making the correction of an error
sometimes re introduces more errors keep the measure
of impact of change on project. Reset the new change to
change check the compatibility of this fix with whole
project.
Manage Good Relations:
In the working environment managing good relations
with other teams involved in the project development is
mandatory. Bad relation of sqa team with programmers
team will impact directly and badly on project. Don’t play
politics

12. 12
There are 5 primary Quality Assurance Functions:
 Technology transfer: This function involves getting a product
design document as well as trial and error data and its
evaluation. The documents are distributed, checked and
approved
 Validation: Here validation master plan for the entire system is
prepared. Approval of test criteria for validating product and
process is set. Resource planning for execution of a validation
plan is done.
 Documentation: This function controls the distribution and
archiving of documents. Any change in a document is made by
adopting the proper change control procedure. Approval of all
types of documents.
 Assuring Quality of products
Quality improvement plans

13. 13
There are 10 essential elements of SQA which are
enlisted below for your reference:
1.Software engineering Standards
2.Technical reviews and audits
3.Software Testing for quality control
4.Error collection and analysis
5.Change management
6.Educational programs
7.Vendor management
8.Security management
9.Safety
10.Risk management

14. 14
The role of quality planning is to
design a process that will be able to
meet established goals under
operating conditions.

15. 15
Quality planning is a methodology which can be
used when a situation exhibits one or more of the
following characteristics:
•A service has never existed before.
•Customer requirements are not known
•The existing service/process performance is not
capable of meeting customer requirements
•The service/process is ad hoc; extremely
variable; never been well defined or worked on
before as a whole
•The environment is unstable, characterized by
major market, technology or organizational
change
•Performance data does not exist or it would
require excessive time/expense to collect data [1]

16. 16
Quality Planning Steps [1]
•Identify customers, both external and internal
•Determine customer needs
•Develop service/product features that respond to
customer needs
•Establish quality goals that meet the needs of
customers and suppliers alike, and do so at a
minimum combined cost
•Develop a process that can produce the needed
service/product features
•Prove process capability—prove that the process can
meet the quality goals under operating conditions

17. 17

18. 18
Software Quality Control (SQC, or QC)
is a set of activities for ensuring the
quality of software products. It is a
process governed by QA and its main
goal is to identify defects in the actual
product produced, be it bugs,
glitches, or differences from
specifications.

19. 19

20. 20
The three class parameters that control
software quality are:
•Products
•Processes
•Resources
The total quality control process consists of:
•Plan - It is the stage where the Quality control
processes are planned
•Do - Use a defined parameter to develop the quality
•Check - Stage to verify if the quality of the parameters
are met
•Act - Take corrective action if needed and repeat the
work

21. 21
•Process adopted to deliver a quality
product to the clients at best cost.
•Goal is to learn from other
organizations so that quality would
be better each time.
•To avoid making errors by proper
planning and execution with correct
review process.

22. 22

23. 23
Software Process Improvement (SPI)
methodology is defined as a sequence of
tasks, tools, and techniques to plan and
implement improvement activities to achieve
specific goals such as increasing development
speed, achieving higher product quality or
reducing costs.

24. 24
 A software process is a set of
activities and associated outcome
whose objective is the advance
development or evolution of
software.
 There are four fundamental
software process activities that
are general to all software
processes. These processes
activates are as follows:

25. 25
 Software specification: In the software specification process
activity customers and software engineers define the
software to be produced and the constraints on its operation
and functions.
 Software development: In software development the
software is designed and programmed as per the customer
specification by the software development engineer team.
 Software validation: Software validation of software process
activity is checked the software to ensure that it is what the
customer requires as in the specification.
 Software evolution: Software evolution process activity
includes the software modified to adapt it to varying
customer and markets promote requirements.

26. 26
Software process improvement is a
cyclical activity.
it involves three principal stages.
Process measurement: Process
measurement involves the
measurement of current project
attributes or the product. The aim is to
advance the measured attributes as per
the goals of the organization involved
in process improvement.

27. 27

28. 28
Process analysis: It involves the current
process is assessed, and process
weaknesses and bottlenecks are
identified. Process models that describe
the process are usually developed during
process analysis stage.
Process change: Changes to the process
that have been identified during analysis
are introduced.

29. 29
•Understandability: To what extent is the process
explicitly defined and how easy is it to understand
the process definition?
•Visibility: Do the process activities culminate in
clear results so that the progress of the process is
externally visible?
•Supportability: To what extent can CASE tools be
used to support the process activities?
•Acceptability: Is the defined process acceptable to
and usable by the engineers responsible for
producing the software product?

30. 30
Reliability: Is the process designed in such a way
that process errors are avoided or trapped before
they result in product error?
Robustness: Can the process continue in spite of
unexpected problem?
Maintainability: Can the process evolve to reflect
changing organizational requirements or
identified process improvements?
Rapidly: How fast can the process of delivering a
system from a given specification be completed?

31. 31