22 replies
Hello everyone,
I've already started my blog about Quality Assurance & also one blog for CSQA aspirants.
I've found out there is a dearth of study resources for CSQA as of date.
The best thing I could imagine is to put my notes on the web so that all the CSQA aspirants can find it useful.
I am putting my study notes online on the following blog :
Note that this is useful for Certified Software Test Engineer (CSTE) aspirants too.
Please post your comments or doubts at that particular post/topic in
the blog so that it will be useful for all those visiting the CSQA blog.
I really hope it will be useful for many.By the way, is there any one who has tech notes as their blog?
Regards,
Prasanna Kumar
----------------
http://ITsQualityAssurance.blogspot.com
http://CSQA.blogspot.com
by taherkapadia
Dear Tech Republic users,
There is also a website I have created to form the community ( FORUMS, BLogs ) of CSQA & CSTE professionals. The site is
Hope you find this site useful, as it has some answers to subjective question, links to resources, List of books you can refer, Forums, Articles, Question bank etc.
Also you can create your own blog here and get noticed amongst the QA community.
Regards
Well,
I've found out there is a dearth of material for CSQA.
This is my sincere attempt to put whatever I can about CSQA here.
I wish this blog becomes the shelter for many CSQA aspirants.
Wish me all the best for this attempt.
Thanx

Just came across this S/W Quality Icerberg - showing the importance of internal Quality maintenance which is invisible to the external agent. Looking at this iceberg, the amount by which the Orgnanisation spends towards reducing the Cost of Poor Quality should idealy be more compared to the cost incurred in meeting the external defects identified.
Read more on this Quality Icerberg here:
http://www.asq.org/pub/qualityprogress/past/0501/qp0501defeo.pdf
The Total Quality View is given in the figure below. Realize from the figure that as the emphasis on Prevention & Appraisal Cost is increasing, the failure cost is reducing at a linear slope. Also see the slope of the Prevention & Appraisal Cost is less than that of the Cost of Failure which clearly indicates the cost reduction because of the difference in slope gives you the net profit. Also shown below is the ideal divisions among the different Costs of Quality.
Interested ones can go to this to find out why more organisations cannot use it effectively.
http://www.asq.org/ed/conferences/aqc/public_proceedings/57_2003/19384.pdf
Cost of Quality (COQ) is one of the very important sub domain of the Knowledge Domain-1 in the CSQA BOK. Getting this concept clarified is very important for any QA Professional and more importantly for CSQA aspirants. I am starting here with the definitions and the best possible sources here on COQ.
Cost Of Quality
The cost associated with the quality of a work product.
As defined by Crosby ("Quality Is Free"), Cost Of Quality (COQ) has two main components: *Cost Of Conformance* and *Cost Of Non-Conformance* (see respective definitions).
Cost of quality is the amount of money a business loses because its product or service was not done right in the first place. From fixing a warped piece on the assembly line to having to deal with a lawsuit because of a malfunctioning machine or a badly performed service, businesses lose money every day due to poor quality. For most businesses, this can run from 15 to 30 percent of their total costs.
Cost of Poor Quality - COPQ
COPQ consists of those costs which are generated as a result of producing defective material.
This cost includes the cost involved in fulfilling the gap between the desired and actual product/service quality. It also includes the cost of lost opportunity due to the loss of resources used in rectifying the defect. This cost includes all the labor cost, rework cost, disposition costs, and material costs that have been added to the unit up to the point of rejection. COPQ does not include detection and prevention cost.
There usually goes confusion between these two definitions COQ and COPQ.
Cost of quality (COQ) is actually a phrase coined by Philip Crosby, noted quality expert and author and originator of the ?zero defects? concept, to refer to the costs associated with providing poor-quality products or services. Many quality practitioners thus prefer the term cost of poor quality (COPQ).
To illustrate the impact this can have on the workforce can not be underestimated. With a little imagination you could imagine the impact of storing all scrap for one year then presenting it as an "in-your-face" visual presentation tactic at a business improvement initiative.
Cost Of Conformance
(COC) A component of the *Cost Of Quality* for a work product. Cost of conformance is the total cost of ensuring that a product is of good *Quality*. It includes costs of *Quality Assurance* activities such as standards, training, and processes; and costs of *Quality Control* activities such as reviews, audits, inspections, and testing.
COC represents an organisation's investment in the quality of its products.
Cost Of Non-Conformance
(CONC.) The element of the *Cost Of Quality* representing the total cost to the organisation of failure to achieve a good *Quality* product.
CONC includes both in-process costs generated by quality failures, particularly the cost of *Rework*; and post-delivery costs including further *Rework*, re-performance of lost work (for products used internally), possible loss of business, possible legal redress, and other potential costs.
Cost of Quality (COQ )
1. Cost of Control (Conformance)
- Prevention Cost
- Appraisal Cost
2. Cost of not controlling (Non-conformance)
- Internal Failure Cost
- External Failure Cost
Wanna know the definitons more clearly? Here they are:
Four categories of costs contribute to an organization?s overall COQ:
- Internal failure costs - costs associated with defects found before the customer receives the product or service
- External failure costs - costs associated with defects found after the customer receives the product or service
- Appraisal costs - costs incurred to determine the degree of conformance to quality requirements
- Prevention Costs - Costs incurred to keep failure and appraisal costs to minimum.
Table - Examples of Quality Costs Associated with Software Products
|
Prevention |
Appraisal |
|
|
|
Internal Failure |
External Failure |
|
|
The minimum total cost,for example is shown below as being achieved at 98% perfection. This percentage is also known as best practice. That is, the cost of achieving an improvement outweighs the benefits of that improvement.
In my previous post, similar cost curve created doubts to few as the X-axis was labelled "Defects" there. In fact it is the Degree of perfection achieved towards the individual curves like Appraisal, Prevention etc. In few instances, this axis is taken with increasing Quality of Design.
Sources referred:
http://www.isixsigma.com/dictionary/glossary
http://www.asq.org/topics/coq.html
http://www.educesoft.com/quality/costofquality.htm
http://www.hq.nasa.gov/office/hqlibrary/ppm/ppm35.htm
Certified Software Quality Analyst (CSQA)
Acquiring the designation of Certified Software Quality Analyst (CSQA) indicates a professional level of competence in the principles and practices of quality assurance in the IT profession. CSQAs become members of a recognized professional group and receive recognition of their competence by business and professional associates, potentially more rapid career advancement, and greater acceptance in the role as advisor to management.
To become certified as a Certified Software Quality Analyst, every candidate must:
- Satisfy all applicant Prerequisites.
- Subscribe to the Code of Ethics.
- Submit a Character Reference.
- Pass a comprehensive written Examination.
If you're ready to begin the certification process, see Applying for Candidacy.
According to the announcement by QAI, starting from March, 2006, candidates will be tested on the new version of CBOK and current candidates will need to start obtaining CPE credits based on this version and the levels of certification will use this version.
CSQA 2006 Common Body of Knowledge
QAI made it clear that the CBOK below is for anyone sitting for the exam prior to March, 2006 only.
Skill Categories/Knowledge Domains:
- Quality Principles
- Software Development, Acquisition, and Operation Processes
- Quality Models and Quality Assessment
- Quality Management/Leadership
- Quality Assurance
- Quality Control Practices
- Define, Build, Implement, and Improve Work Processes
- Quantitative Methods
CSQA certified candidates must be recertified 3 years after passing CSQA to stay current in the field. This can be demonstrated by 1) submitting a Recertification Journal of qualified Continuing Professional Education activities, or 2) by taking an Examination for Recertification to demonstrate the maintenance of the certification.
The individual seven categories eligible for CPE reporting include:
- Category A - Education
- Category B - Publishing
- Category C - Teaching
- Category D - Participation in Profession
- Category E - Self-Study
- Category F - Unique and Innovative Activities
- Category G - On The Job Activities
There are Advanced Levels of Certifications too - Do check them out @ SoftwareCertifications
CSTE/CSQA Study for and pass a four part examination developed by peers to evaluate the candidates knowledge of the principles and concepts incorporated into the common body of knowledge plus the ability to relate those principles and concepts to the challenges faced by IT organizations.
ASTP/ASQP Candidates must demonstrate their ability to develop real solutions to challenges in their IT organizations, by proposing a solution to a real world problem. If accepted by the Certification Board, to develop and submit for evaluation the step-by-step solution the candidate developed for that IT challenge. This must be done for five (5) common body of knowledge categories. Each accepted solution will be awarded a certificate of competency for that CBOK category.
MSQA/MSTE Candidate must demonstrate the ability to innovate beyond current practice in solving IT challenges, as well as, demonstrate public service in the IT Quality profession. (available starting in 2006)
For further details on the Schedule of the exam, Application procedures, Recertification, Obtaining & Using Credentials etc can go to www.softwarecertifications.org/qai_cqa.htm
Source: www.softwarecertifications.org
I would like to start with the notes that I have made & other sources for the sections of the CBOK. Starting from the 1st Knowledge Domain i.e., Quality Principles, I would like to take each sub domain of it from my next post. Keep checking for the new updated notes. Please note that I have already posted the notes on "Cost of Quality(COQ)". Please check my previous posts for COQ.
CSQA CBOK - Skill Category 1
Quality Principles
- Definitions of Quality: Producer?s view of quality & Customer?s view of quality
- Quality Concepts: Cost of quality;Plan-Do-Check-Act;Six Sigma;Benchmarking; Continuous improvement; Best Practices
- Quality Objectives: Improve customer satisfaction;Reduce development costs/improve time-to-market capability;Improve processes
- Quality Attributes - Examples like: Reliability;Maintainability;Usability;Portability
- Quality Assurance vs. Quality Control
- Quality Pioneers: Deming;Juran;Crosby & their contributions
- Quality Vocabulary
The definitions in summary are given below. For those who love to read more, further info is given.
From the customer's perspective, satisfaction after the delivering of the product is the ultimate validation of the product quality. It is clear that the concept of quality must involve customers or, simply put, quallity is conformance to customers' expectations and requirements. Crosby's "conformance to requirements" and Juran's "fitness for use" both implied the customers' perspective.
From the producer's perspective, developing and producing the product in accordance with the specifications is the path to achieving quality.
Therefore the three ideal metrics any organization should have are product quality, process quality, and customer satisfaction (referred to as the big capital ?Q?).
From a high-level definition of a concept, to a product being operationally defined, many steps are involved, each of which may be exposed to possible shortcomings. For example, to achieve the state of conformance to requirements, customers' requirements must first be gathered and analyzed, then specifications from those requirements must be developed, and the product must be developed and manufactured appropriately. In each phase of the process, errors may have occurred that will negatively affect the quality of the finished product. The requirements may be erroneous (especially in the case of software development), the development and manufacturing process may be subject to variable that induce defects, and so forth. Form the customer's perspective, satisfaction after the purchase of the product is the ultimate validation that the product conforms to requirements and is fit to use. From the producer's perspective, once requirements are specified, developing and producing the product in accordance with the specifications is the basic step to achieving quality. Usually, for product quality, lack of functional defeats and good reliability are the most basic measures. In order to be "fit for use," the product first has to be reliably functional.
Because of the two perspectives on quality (i.e., customer satisfaction as the ultimate validation of quality, alnd the producer's adherence to requirements to achieve quality), the de facto definition of quality consists of two levels. The first is the intrinsic product quality, often operationally limited to product quality,often operationally limited to product defect rate and reliability; this narrow definition is referred to as the "small" q (q for quality). The broader level of the definition of quality includes both product quality and customer satisfaction; it is referred to as the "big" Q.
In software, the norrowest sense of product quality is comonly recongnized as lack of "bugs" in the product. This definition is usually expressed in two ways: defect rate (e.g., number of defects per million lines of source code, or per function point), and reliability (e.g., number of failure per n hours of operation, mean time to failure, or the probability of failure-free operation in a specified time). Customer satisfaction is usually measured by the percentage of those satisfied or nonsatisfied (neutral and dissatisfied) on customer satisfaction surveys. To reduce bias, usually techniques such as double-blind surveys (the interviewer not knowing who the customer is, and the customer not knowing what company the interviewer represents) are used. In addition to overall customer satisfaction with the software product, satisfaction toward specific attributes is CUPRIMDSO satisfaction levels of its software products (i.e., capability [functionality], usability, performance, reliability, instalability, maintainability, documentation/information, service, and overall satisfaction). The Hewlett-Packard Co. focuses on FURPS (functionalilty, usability, relability, performance, and supportability)[1].
For people with much more interest, here is the link from HP's Center for Quality Management Journal. I believe the differences between Customer's & Producer's view of qualities cant be better enumerated. The copyrights do not allow to reproduce any part of it. You can go to this link to find this quite a long paper: http://cqmextra.cqm.org/cqmjournal.nsf/reprints/rp08300
The PDF form of this article can be downloaded from this link: DOWNLOAD Article(PDF)
References:
Correctness
The software system?s fulfillment of the specifications underlying its development. The correctness of a software system refers to:
- Agreement of program code with specifications
- Independence of the actual application of the software system.
The correctness of a program becomes especially critical when it is embedded in a complex software system.
Example 1.1
Let p be the probability that an individual program is correct; then the probability P of correctness of the software system consisting of n programs is computed as P = pn
.
If n is very large, then p must be nearly 1 in order to allow P to deviate significantly from 0 [Dijkstra 1972b].
Reliability
Reliability of a software system derives from
- Correctness, and
- Availability.
The behavior over time for the fulfillment of a given specification depends on the reliability of the software system.
Reliability of a software system is defined as the probability that this system fulfills a function (determined by the specifications) for a specified number of input trials under specified input conditions in a specified time interval (assuming that hardware and input are free of errors).
A software system can be seen as reliable if this test produces a low error rate (i.e., the probability that an error will occur in a specified time interval.)
The error rate depends on the frequency of inputs and on the probability that an individual input will lead to an error.
User friendliness:
- Adequacy
- Learnability
- Robustness
Adequacy
Factors for the requirement of Adequacy:
- The input required of the user should be limited to only what is necessary. The software system should expect information only if it is necessary for the functions that the user wishes to carry out. The software system should enable flexible data input on the part of the user and should carry out plausibility checks on the input. In dialog-driven software systems, we vest particular importance in the uniformity, clarity and simplicity of the dialogs.
- The performance offered by the software system should be adapted to the wishes of the user with the consideration given to extensibility; i.e., the functions should be limited to these in the specification.
-
The results produced by the software system:
The results that a software system delivers should be output in a clear and well-structured form and be easy to interpret. The software system should afford the user flexibility with respect to the scope, the degree of detail, and the form of presentation of the results.Error messages must be provided in a form that is comprehensible for the user.
Learnability
Learnability of a software system depends on:
- The design of user interfaces
- The clarity and the simplicity of the user instructions (tutorial or user manual).
The user interface should present information as close to reality as possible and permit efficient utilization of the software?s failures.
The user manual should be structured clearly and simply and be free of all dead weight. It should explain to the user what the software system should do, how the individual functions are activated, what relationships exist between functions, and which exceptions might arise and how they can be corrected. In addition, the user manual should serve as a reference that supports the user in quickly and comfortably finding the correct answers to questions.
Robustness
Robustness reduces the impact of operational mistakes, erroneous input data, and hardware errors.
A software system is robust if the consequences of an error in its operation, in the input, or in the hardware, in relation to a given application, are inversely proportional to the probability of the occurrence of this error in the given application.
- Frequent errors (e.g. erroneous commands, typing errors) must be handled with particular care
- Less frequent errors (e.g. power failure) can be handled more laxly, but still must not lead to irreversible consequences.
Maintainability
Maintainability = suitability for debugging (localization and correction of errors) and for modification and extension of functionality.
The maintainability of a software system depends on its:
- Readability
- Extensibility
- Testability
Readability
Readability of a software system depends on its:
- Form of representation
- Programming style
- Consistency
- Readability of the implementation programming languages
- Structuredness of the system
- Quality of the documentation
- Tools available for inspection
Extensibility
Extensibility allows required modifications at the appropriate locations to be made without undesirable side effects.
Extensibility of a software system depends on its:
- Structuredness (modularity) of the software system
- Possibilities that the implementation language provides for this purpose
- Readability (to find the appropriate location) of the code
- Availability of comprehensible program documentation
Testability
Testability: suitability for allowing the programmer to follow program execution (run-time behavior under given conditions) and for debugging.
The testability of a software system depends on its:
- Modularity
- Structuredness
Modular, well-structured programs prove more suitable for systematic, stepwise testing than monolithic, unstructured programs.
Testing tools and the possibility of formulating consistency conditions (assertions) in the source code reduce the testing effort and provide important prerequisites for the extensive, systematic testing of all system components.
Efficiency
Efficiency: ability of a software system to fulfill its purpose with the best possible utilization of all necessary resources (time, storage, transmission channels, and peripherals).
Portability
Portability: the ease with which a software system can be adapted to run on computers other than the one for which it was designed.
The portability of a software system depends on:
- Degree of hardware independence
- Implementation language
- Extent of exploitation of specialized system functions
- Hardware properties
- Structuredness: System-dependent elements are collected in easily interchangeable program components.
A software system can be said to be portable if the effort required for porting it proves significantly less than the effort necessary for a new implementation.
Find out more info on Quality Attributes in the Technical Report of Carnegie Mellon University on
QUALITY ATTRIBUTES.
You can also download this paper from:
THIS LINK of SEI
.
Reference:
SOFTWARE ENGINEERING
By Nguyen Xuan Huy
Deming's 14 Points
- Create constancy of purpose for improvement of product and service. Dr. Deming suggests a radical new definition of a company's role: A better way to make money is to stay in business and provide jobs through innovation, research, constant improvement and maintenance.
- Adopt the new philosophy. For the new economic age, management need to take leadership for change into a 'learning organisation'. Furthermore, we need a new belief in which mistakes and negativism are unacceptable.
- Cease dependence on mass inspection. Eliminate the need for mass inspection by building quality into the product.
- End awarding business on price. Instead, aim at minimum total cost and move towards single suppliers.
- Improve constantly and forever the system of production and service. Improvement is not a one-time effort. Management is obligated to continually look for ways to reduce waste and improve quality.
- Institute training. Too often, workers have learned their job from other workers who have never been trained properly. They are forced to follow unintelligible instructions. They can't do their jobs well because no one tells them how to do so.
- Institute leadership. The job of a supervisor is not to tell people what to do nor to punish them, but to lead. Leading consists of helping people to do a better job and to learn by objective methods.
- Drive out fear. Many employees are afraid to ask questions or to take a position, even when they do not understand what their job is or what is right or wrong. They will continue to do things the wrong way, or not do them at all. The economic losses from fear are appalling. To assure better quality and productivity, it is necessary that people feel secure. "The only stupid question is the one that is not asked."
- Break down barriers between departments. Often a company's departments or units are competing with each other or have goals that conflict. They do not work as a team, therefore they cannot solve or foresee problems. Even worse, one department's goal may cause trouble for another.
- Eliminate slogans, exhortations and numerical targets for the workforce. These never help anybody do a good job. Let workers formulate their own slogans. Then they will be committed to the contents.
- Eliminate numerical quotas or work standards. Quotas take into account only numbers, not quality or methods. They are usually a guarantee of inefficiency and high cost. A person, in order to hold a job, will try to meet a quota at any cost, including doing damage to his company.
- Remove barriers to taking pride in workmanship. People are eager to do a good job and distressed when they cannot. Too often, misguided supervisors, faulty equipment and defective materials stand in the way of good performance. These barriers must be removed.
- Institute a vigorous programme of education. Both management and the work force will have to be educated in the new knowledge and understanding, including teamwork and statistical techniques.
- Take action to accomplish the transformation. It will require a special top management team with a plan of action to carry out the quality mission. Workers cannot do it on their own, nor can managers. A critical mass of people in the company must understand the 14 points.
I am giving simple definitions of P-D-C-A here. There are very good resources available for PDCA cycle which is also known as Deming's Cycle or Schewart's Cycle. Please go through the sources below for better info on PDCA cycle.
- PLAN: Design or revise business process components to improve results
- DO: Implement the plan and measure its performance
- CHECK or STUDY: Assess the measurements and report the results to decision makers
- ACT: Decide on changes needed to improve the process
Benefits of the PDCA cycle:
- Daily routine management-for the individual and/or the team
- Problem-solving process
- Project management
- Continuous development
- Vendor development
- Human resources development
- New product development
- Process trials
Note: The PDCA cycle was in fact originally developed by Walter A, Shewhart, a Bell Laboratories scientist who was Deming's friend and mentor, and the developer of Statistical Process Control

Kaoru Ishikawa has expanded Deming's four steps into Six
- Determine goals and targets.
- Determine methods of reaching goals.
- Engage in education and training.
- Implement work.
- Check the effects of implementation.
- Take appropriate action.
PDCA Resources:
I dont feel there is need of long notes here as many resources are available on the web. So I am just briefly giving their definitions with the related resources.
Six Sigma
The goal of Six Sigma is to increase profits by eliminating variability, defects and waste that undermine customer loyalty.
Six Sigma can be understood/perceived at three levels:
- Metric: 3.4 Defects Per Million Opportunities. DPMO allows you to take complexity of product/process into account. Rule of thumb is to consider at least three opportunities for a physical part/component - one for form, one for fit and one for function, in absence of better considerations. Also you want to be Six Sigma in the Critical to Quality characteristics and not the whole unit/characteristics.
- Methodology: DMAIC/DFSS structured problem solving roadmap and tools.
- Philosophy: Reduce variation in your business and take customer-focused, data driven decisions.
Six Sigma is a methodology that provides businesses with the tools to improve the capability of their business processes. This increase in performance and decrease in process variation leads to defect reduction and vast improvement in profits, employee morale and quality of product.
Resources:
Benchmarking
The concept of discovering what is the best performance being achieved, whether in your company, by a competitor, or by an entirely different industry.
Benchmarking is an improvement tool whereby a company measures its performance or process against other companies' best practices, determines how those companies achieved their performance levels, and uses the information to improve its own performance.
Benchmarking is a continuous process whereby an enterprise measures and compares all its functions, systems and practices against strong competitors, identifying quality gaps in the organization, and striving to achieve competitive advantage locally and globally.
Resources:
- Complete info on Benchmarking
- Benchmarking ? Uncovering Best Practices & Lessons Learnt from others
- Is Benchmarking And Identifying Best Practices Worth It?
- iSixSigma's resources on Benchmarking
Best Practice
A way or method of accomplishing a business function or process that is considered to be superior to all other known methods.
A lesson learned from one area of a business that can be passed on to another area of the business or between businesses.
Continuous Improvement (CI)
Continuous Improvement (CI): Adopting new activities and eliminating those which are found to add little or no value. The goal is to increase effectiveness by reducing inefficiencies, frustrations, and waste (rework, time, effort, material, etc). The Japanese term is Kaizen, which is taken from the words "Kai" means change and "zen" means good.
Resources:
Quality Assurance
A planned and systematic set of activities to ensure that variances in processes are clearly identified, assessed and improving defined processes for fullfilling the requirements of customers and product or service makers.
A planned and systematic pattern of all actions necessary to provide adequate confidence that the product optimally fulfils customer's expectations.
A planned and systematic set of activities to ensure that requirements are clearly established and the defined process complies to these requirements.
"Work done to ensure that Quality is built into work products, rather than Defects." This is by (a) identifying what "quality" means in context; (b) specifying methods by which its presence can be ensured; and (c) specifying ways in which it can be measured to ensure conformance (see *Quality Control*, also *Quality*).
Quality Control
Also called statistical quality control. The managerial process during which actual process performance is evaluated and actions are taken on unusual performance.It is a process to ensure whether a product meets predefined standards and requisite action taken if the standards are not met.
Quality Control measures both products and processes for conformance to quality requirements (including both the specific requirements prescribed by the product specification, and the more general requirements prescribed by *Quality Assurance*); identifies acceptable limits for significant *Quality Attributes*; identifies whether products and processes fall within those limits (conform to requirements) or fall outside them (exhibit defects); and reports accordingly. Correction of product failures generally lies outside the ambit of Quality Control; correction of process failures may or may not be included.
The Certified Software Quality Analyst (CSQA) certification is undoubtedly one of the best certifications available in the IT profession. But the level of awareness about CSQA is very limited among the Software community compared to many other software certifications. Probably this may be due to the low awareness and myths about Quality Assurance.
Here I would like to say something about CSQA examination.
According to the CBOK, this examination is actually designed to test the ability of a professional understanding both the principles and practices of good quality management. The bookish knowledge from the CBOK will only help in understanding the vocabulary, concepts & principles of quality. According to many CSQA certified professionals, most of the Objective papers of CSQA examination are from the basic concepts & principles of CBOK. Where as the practice of these principles are tested in the Subjective Papers.
For example, there may be objective questions related to Deming's Principles. Coming to the Subjective papers, the question can be asked as (infact it is a recent question):
Deming Stresses in "Drive out fear". As a QA Manager how will you
drive out fear. Explain briefly.
This is how the candidate's ability to face real world challenges are tested.
So, my sincere advise to all the CSQA aspirants is to go for the certification in a planned manner so that by the exam time, you have adequate real world exposure to QA practices. Some may be worrying if doing the certification is difficult after the new CBOK is introduced. This is purely a myth. Never worry for the study materials. Infact the new CBOK has few additional concepts along with the concepts in the current version of the CBOK. In this global village, it is never a tough task to find out the relavent material. All you need is persistence. Go for the certification in a way to learn & apply the QA principles in the day to day QA operations, apart from getting certified; not for the purpose of just getting certified. Why dont you choose to go for two birds at one shot? In fact, that is the basic idea behind CSQA!!
The definitions in summary are given below. For those who love to read more, further info is given.
From the customer's perspective, satisfaction after the delivering of the product is the ultimate validation of the product quality. It is clear that the concept of quality must involve customers or, simply put, quallity is conformance to customers' expectations and requirements. Crosby's "conformance to requirements" and Juran's "fitness for use" both implied the customers' perspective.
From the producer's perspective, developing and producing the product in accordance with the specifications is the path to achieving quality.
Therefore the three ideal metrics any organization should have are product quality, process quality, and customer satisfaction (referred to as the big capital ?Q?).
From a high-level definition of a concept, to a product being operationally defined, many steps are involved, each of which may be exposed to possible shortcomings. For example, to achieve the state of conformance to requirements, customers' requirements must first be gathered and analyzed, then specifications from those requirements must be developed, and the product must be developed and manufactured appropriately. In each phase of the process, errors may have occurred that will negatively affect the quality of the finished product. The requirements may be erroneous (especially in the case of software development), the development and manufacturing process may be subject to variable that induce defects, and so forth. Form the customer's perspective, satisfaction after the purchase of the product is the ultimate validation that the product conforms to requirements and is fit to use. From the producer's perspective, once requirements are specified, developing and producing the product in accordance with the specifications is the basic step to achieving quality. Usually, for product quality, lack of functional defeats and good reliability are the most basic measures. In order to be "fit for use," the product first has to be reliably functional.
Because of the two perspectives on quality (i.e., customer satisfaction as the ultimate validation of quality, alnd the producer's adherence to requirements to achieve quality), the de facto definition of quality consists of two levels. The first is the intrinsic product quality, often operationally limited to product quality,often operationally limited to product defect rate and reliability; this narrow definition is referred to as the "small" q (q for quality). The broader level of the definition of quality includes both product quality and customer satisfaction; it is referred to as the "big" Q.
In software, the norrowest sense of product quality is comonly recongnized as lack of "bugs" in the product. This definition is usually expressed in two ways: defect rate (e.g., number of defects per million lines of source code, or per function point), and reliability (e.g., number of failure per n hours of operation, mean time to failure, or the probability of failure-free operation in a specified time). Customer satisfaction is usually measured by the percentage of those satisfied or nonsatisfied (neutral and dissatisfied) on customer satisfaction surveys. To reduce bias, usually techniques such as double-blind surveys (the interviewer not knowing who the customer is, and the customer not knowing what company the interviewer represents) are used. In addition to overall customer satisfaction with the software product, satisfaction toward specific attributes is CUPRIMDSO satisfaction levels of its software products (i.e., capability [functionality], usability, performance, reliability, instalability, maintainability, documentation/information, service, and overall satisfaction). The Hewlett-Packard Co. focuses on FURPS (functionalilty, usability, relability, performance, and supportability)[1].
For people with much more interest, here is the link from HP's Center for Quality Management Journal. I believe the differences between Customer's & Producer's view of qualities cant be better enumerated. The copyrights do not allow to reproduce any part of it. You can go to this link to find this quite a long paper: http://cqmextra.cqm.org/cqmjournal.nsf/reprints/rp08300
The PDF form of this article can be downloaded from this link: DOWNLOAD Article(PDF)
References:
TQM used to be mentioned as one of the parts of the Quality Concepts Sub-domain in CBOK Skill Category-1 of CBOK. But now, though it is not explicitly mentioned, it is still a buzz word among QA professionals. So, I am putting it as a part of Quality Vocabulary & am giving the necessary resources for it.
TQM - Introduction
Total Quality Management (TQM), a buzzword phrase of the 1980's, has been killed and resurrected on a number of occasions. The concept and principles, though simple seem to be creeping back into existence by "bits and pieces" through the evolution of the ISO9001 Management Quality System standard.
Companies who have implemented TQM include Ford Motor Company, Phillips Semiconductor, SGL Carbon, Motorola and Toyota Motor Company.
The latest changes coming up for the ISO 9001:2000 standard?s "Process Model" seem to complete the embodiment. TQM is the concept that quality can be managed and that it is a process. The following information is provided to give an understanding of the key elements of this process.
Total Quality Management (TQM)
Total = Quality involves everyone and all activities in the company.
Quality = Conformance to Requirements (Meeting Customer Requirements).
Management = Quality can and must be managed.
TQM = A process for managing quality; it must be a continuous way of life; a philosophy of perpetual improvement in everything we do.
TQM Compared to ISO 9001
ISO 9000 is a Quality System Management Standard. TQM is a philosophy of perpetual improvement. The ISO Quality Standard sets in place a system to deploy policy and verifiable objectives. An ISO implementation is a basis for a Total Quality Management implementation. Where there is an ISO system, about 75 percent of the steps are in place for TQM. The requirements for TQM can be considered ISO plus. Another aspect relating to the ISO Standard is that the proposed changes for the next revision (1999) will contain customer satisfaction and measurement requirements. In short, implementing TQM is being proactive concerning quality rather than reactive.
|
TQM Process Improvement and Problem Solving Sequence |
|||||
|
PLAN (PLAN A CHANGE) |
DO (IMPLEMENT THE CHANGE) |
CHECK (OBSERVE THE EFFECTS) |
ACTION |
||
|
DEFINE |
IDENTIFY |
EVALUATE |
MAKE |
TEST |
TAKE |
| 1. Recognize that what you are doing is a "PROCESS"
2. Identify the commodity 3. Define some measurable characteristics of value to the commodity. 4. Describe the "PROCESS" 5. Identify the "Big" problem |
6. "BRAINSTORM" what is causing the problem.
7. Determine what past data shows. |
8. Determine the relationship between cause and effect o Scatter diagrams o Regression analysis 9. Determine what the |
10. Determine what change would help
****Then make |
11. Determine what change worked (confirmation).
|
12. Ensure the fix is embedded in the process and that the resulting process is used.
Continue to monitor the process to ensure: A. The problem is fixed for good. and B. The process is good enough o Control charts ****To ensure continuous |
Courtesy:
Resources:
Dr. W. Edwards Deming
If you can't describe what you are doing as a process, you don't know what you're doing.
W. Edwards Deming
Dr. W. Edwards Deming is known as the father of the Japanese post-war industrial revival and was regarded by many as the leading quality guru in the United States. He passed on in 1993.
Trained as a statistician, his expertise was used during World War II to assist the United States in its effort to improve the quality of war materials.
He was invited to Japan at the end of World War II by Japanese industrial leaders and engineers. They asked Dr. Deming how long it would take to shift the perception of the world from the existing paradigm that Japan produced cheap, shoddy imitations to one of producing innovative quality products.
Dr. Deming told the group that if they would follow his directions, they could achieve the desired outcome in five years. Few of the leaders believed him. But they were ashamed to say so and would be embarrassed if they failed to follow his suggestions.
As Dr. Deming told it, "They surprised me and did it in four years."
He was invited back to Japan time after time where he became a revered counselor. For his efforts he was awarded the Second Order of the Sacred Treasure by the former Emperor Hirohito.
Japanese scientists and engineers named the famed Deming Prize after him. It is bestowed on organizations that apply and achieve stringent quality-performance criteria.
Deming's business philosophy is summarized in his famous "14 Points," listed in my previous post. These points have inspired significant changes among a number of leading US companies striving to compete in the world's increasingly competitive environment.
But the 14 Points pose a challenge for many firms to figure out how to apply them in a meaningful way that will result in continual improvement. Leadership Institute has developed powerful processes for coaching executive teams, and eventually their entire organizations, to begin accomplishing what Deming referred to as "the transformation."
His work is outlined in two books: Out of the Crisis and The New Economics, in which he spells out his System of Profound Knowledge.
Courtesy: www.lii.net
Other Very good resources on Edwards Deming:

Joseph M. Juran
Joseph M. Juran made many contributions to the field of quality management in his 70+ active working years. His book, the Quality Control Handbook, is a classic reference for quality engineers. He revolutionized the Japanese philosophy on quality management and in no small way worked to help shape their economy into the industrial leader it is today. Dr. Juran was the first to incorporate the human aspect of quality management which is referred to as Total Quality Management.
The process of developing ideas was a gradual one for Dr. Juran. Top management involvement, the Pareto principle, the need for widespread training in quality, the definition of quality as fitness for use, the project-by-project approach to quality improvement--these are the ideas for which Juran is best known, and all emerged gradually.
Juran is well known for his Quality Trilogy.
The following table outlines the major points of Dr. Juran's quality management ideas:
Quality Trilogy:
| Quality Planning |
|
| Quality Improvement |
|
| Quality Control |
|
You can find out more at the links given below:
Philip Crosby
"Do It Right the First Time"
Dr. Deming and Dr. Juran were the great brains of the quality revolution. Where Phil Crosby excelled was in finding a terminology for quality that mere mortals could understand. His books, "Quality Without Tears" and "Quality is Free" were easy to read, so people read them. He popularized the idea of the "cost of poor quality", that is, figuring out how much it really costs to do things badly.
Like Frederick Taylor, Philip Crosby's ideas came from his experience on an assembly line. He focused on zero defects, not unlike the focus of the modern Six Sigma Quality movement. Mr. Crosby was quick to point out, however, that zero defects is not something that originates on the assembly line. To create a manufacturing process that has zero defects management must set the tone and atmosphere for employees to follow. If management does not create a system by which zero defects are clearly the objective then employees are not to blame when things go astray and defects occur. The benefit for companies of such a system is a dramatic decrease in wasted resources and time spent producing goods that consumer's do not want.
Mr. Crosby defined quality as a conformity to certain specifications set forth by management and not some vague concept of "goodness." These specifications are not arbitrary either; they must be set according to customer needs and wants.
Four Absolutes of Quality Management
- Quality is defined as conformance to requirements, not as 'goodness' or 'elegance'.
- The system for causing quality is prevention, not appraisal.
- The performance standard must be Zero Defects, not "that's close enough".
- The measurement of quality is the Price of Nonconformance, not indices.
Courtesy: www.skymark.com
More Resources:
Introduction to CSQA
- All you wanted to know about CSQA-Application to Certification to Recertification
- Understand the idea behind CSQA
CBOK Skill Category-1: QUALITY PRINCIPLES
- Quality Principles - Subcategories
- A - Definitions of Quality: Producer?s view of quality & Customer?s view of quality
- B.1 - Cost of Quality & it's Components
- Further Notes on Cost of Quality - Quality Iceberg
- B.2 -Six Sigma, Benchmarking, Continuous Improvement & Best Practices
- B.2 - The Deming's PDCA Cycle
- D - Software quality attributes
- E - Quality Assurance vs. Quality Control
- F.1 - Quality Pioneers - Edwards Deming
- F.1 - Deming's 14 Principles
- F.1 - Quality Pioneers - Philip Crosby
- F.1 - Quality Pioneers - Joseph M. Juran
- G - Quality Vocabulary-TQM
CBOK 2006 material coming up shortly!
There has been a tremendous response to CSQA blog - meant for the aspirants of CSQA certification. Enormous amount of requests have been received to update the material to suit the new Body of Knowledge for CSQA - CBOK 2006.
In response to the requests, the blog is currently undergoing few changes to incorporate the material according to the new CBOK which is going to come into effect from March 2006. Apart from this, there are many other things planned to be put in here - Many Questions from previous papers, my responses to the Frequently Asked Questions - FAQs (a collection of common queries mailed across to me), the paper patterns - how to plan & fare accordingly, common pitfalls & alternatives.
Since all of these are going to take some time, I sincerly request everyone to bear the delay & wait for the new version of the material.
CBOK 2006 material is evolving!
Click here...
There has been a tremendous response to CSQA blog - meant for the aspirants of CSQA certification. Enormous amount of requests have been received to update the material to suit the new Body of Knowledge for CSQA - CBOK 2006.
In response to the requests, the blog is currently undergoing few changes to incorporate the material according to the new CBOK which is going to come into effect from March 2006. Apart from this, there are many other things planned to be put in here - Many Questions from previous papers, my responses to the Frequently Asked Questions - FAQs (a collection of common queries mailed across to me), the paper patterns - how to plan & fare accordingly, common pitfalls & alternatives.
Though the old version is still available, there may be problem with few links. Since all of these are going to take some time, I sincerly request everyone to bear the delay & wait for the new version of the material.
The old version of the material is still available.
Click here to go there
This discussion is closed to new replies.
Trending After Hours posts
Sort by Trending



