Certified Software Q lit A l tQuality Analyst€¦ · Certified Software Q lit A l tQuality Analyst...

Certified SoftwareQ lit A l tQuality Analyst

Exam Prep CourseExam Prep Course

Steve Bender PMP CSQA CSTE CQESteve Bender, PMP, CSQA, CSTE, CQE1 (303) 290-8111

[email protected]

Quality Assurance InstituteOrlando, FL

© 2013 Quality Assurance Institute

CSQA Course ObjectivesCSQA Course Objectives• Help the quality professional study and prepare for the

CSQA examinationCSQA examination.• Reinforce current knowledge• Re-introduce concepts that may not be used everyday• Explain the rationale for use within the IT Industry• Highlight sample questions, both multiple choice and essay

type responses.yp p• Provide you with a background of the IT quality

fundamentals

– Due to time limitations of this course, it is not intended to cover all the components of the common body of knowledge in great depth

© 2013 Quality Assurance InstituteCSQA - 2

knowledge in great depth.

IntroductionsIntroductions

• Who are you and your company• Why and when are you taking the examy y g• Have you taken an exam before –

where/whenTi d t d i• Time you spend studying now

• Study group experience


Why Become Certified?Why Become Certified?

• The IT and software quality industry is competitive• Recognition by peers

P f f f i d kill i th IT fi ld• Proof of your profession and skills in the IT field• Increased confidence in personal capabilities • Indicates a professional level of competence• Indicates a professional level of competence • Potentially more rapid career advancement • Greater acceptance in the role as advisor to p

management


The Process

• Satisfy all of the prerequisites required prior to applying for candidacycandidacy– $350.00 Administration fee (includes study guide)

• One of the following must be met:– 4 + 2 = Bachelor’s degree in an accredited college-level

institution and 2 years experience or…– 2 + 4 = Associate’s degree and 4 years experience or…g y p– 0 + 6 = No degree and 6 years experience in the IT service

area• Subscribe to the Code of EthicsSubscribe to the Code of Ethics • Submit a completed Certification Candidacy Application


About The ExamAbout The ExamTwo parts to the exam

Part Questions Type

1 100 Objective or multiple choice questions.1 100 Objective or multiple choice questions.

2 12 Essay or Scenario based questions.

• Minimum passing = overall average of 70%


p g g

Course Table of ContentsCourse Table of ContentsReview of Skill Categories in the Common Body of Knowledge (CBOK) for the Certified Software Quality Analyst:(CBOK) for the Certified Software Quality Analyst:

• Quality Principles• Quality Leadershipy p• Quality Baselines• Quality Assurance• Quality Planning• Quality Planning• Define, Build, Implement, and Improve Work Processes• Quality Control Practices• Metrics and Measurement• Internal Control and Security• Outsourcing, COTS, and Contracting Quality


g g y

Skill Category 1Skill Category 1

Quality Principles and ConceptsQuality Principles and Concepts• Vocabulary• Different Views of Quality• Quality Concepts and Practices• Quality Control and Quality Assurance• Quality Pioneers Approach to Quality

© 2013 Quality Assurance Institute

Quality VocabularyQuality Vocabulary

Understand the technical terms used to describe various testing techniques, tools, principles, concepts and activities

DefectDefect


Quality VocabularyQuality Assurance

• Activities that modify the development process to prevent the• Activities that modify the development process to prevent the introduction of flaws

– Staff functionI l t t’ lit li i– Implements management’s quality policies

– Responsible for continuous improvement of the software development process

• Proactive approach focused on defect prevention• Examples:

– Defining change control proceduresDefining change control procedures– Analyzing metrics to identify opportunities for process

improvement

CSQA - 10 © Copyright 2007 / All rights reserved

Quality VocabularyQuality Control

• Activities within the development process to detect the• Activities within the development process to detect the introduction of flaws

– Test planning and executionQ lit t l d t i t th i t f– Quality control measures a product against the existence of an attribute

– Determines whether the product conforms to a standard or d ( l k li h ki )procedure (also known as compliance checking).

• Proactive approach focused on defect detection• Examples:

– Writing and executing test cases and scripts– Participating in verification and validation activities

Reporting defects to identify opportunities for process


– Reporting defects to identify opportunities for process improvement

Quality Vocabulary

Producer’s view of Quality:Per Philip Crosby:

Conformance to requirementsConformance to requirements• Doing the right thing• Doing it the right wayDoing it the right way• Doing it right the first time• Doing it on time without exceeding cost


Quality Vocabulary

Customer’s view of Quality:From Joseph Juran and W. Edwards Deming

Fit for useFit for use• Receiving the right product for use• Being satisfied that needs have been metBeing satisfied that needs have been met• Expectations have been met• Treated with integrity, courtesy, and respect


Quality Vocabulary

Provider’s view of Quality:

The perspective of the organization that delivers theThe perspective of the organization that delivers the products and services to the customer.


Quality Vocabulary

Supplier’s View of Quality:

The perspective of the organization (which may be external to the producer’s company, such as anexternal to the producer s company, such as an independent vendor) that provides either the producer and/or the provider with products and services needed to meet the requirements of theservices needed to meet the requirements of the customer.


Infrastructure for Software Quality Products and Services

Supplier

Producer/Provider

CustomerProcessespp Customer

RequirementsRequirementsProcesses

Products Products

Services

Measurement(Feedback)

Measurement(Feedback)


The Two Quality GapsThe Two Quality Gaps

Prod cer

Start

ProducerGap

Start

CustomerG

Quality as delivered

Gap


Quality Attributes for Information Systemsy


Understanding the Q lit Ch llQuality Challenge

Common Perceptions:

AQL = Acceptable Quality Level

Common Perceptions:

Some level of product defects is normal and acceptable

Quality is frequently associated with cost: Quality is frequently associated with cost:High quality = High Cost?

Quality requires detail specificationsy q p Technicians believe standards inhibit their ability

to be creative


Questions?Questions?


ExerciseExerciseThe extent to which a program satisfies its specifications and

fulfills the user’s mission objectives.R li bilita. Reliability

b. Maintainabilityc. Correctnessd Testabilityd. Testabilitye. All of the Above

The effort required to ensure the program performs its intended function.

a. Reliabilityyb. Maintainabilityc. Correctnessd. Testability


e. All of the Above

ExerciseThe extent to which a program satisfies its specifications and

fulfills the user’s mission objectives.R li bilit

Exercise

a. Reliabilityb. Maintainabilityc. Correctnessd Testabilityd. Testabilitye. All of the Above

The effort required to ensure the program performs its intended function.

a. Reliabilityyb. Maintainabilityc. Correctnessd. Testability


e. None of the Above

ExerciseQuality factors have frequently been used as a basis for measuring the quality of an information system. Listed below are two of those

lit f tquality factors.Define each of the quality factors and provide an effective measure or metric for each of these quality factors?

Ease of Use: • Effort required to learn, operate, prepare input and interpret output of the

/ tprogram/system. • Customer surveys targeted to a specific customer control group.• How many clicks it takes the user to find the object

Maintainability –• The effort required to locate and fix errors in the program/system. • The recording of how long it takes to make a change to code that has

l d b l d


already been released. • The recording of how long it takes to retest a change.

The PDCA CycleThe PDCA Cycle

Act Plan

Check Do


The PDCA CycleThe PDCA CyclePlan (P): Devise a plan( ) p

• Objectives are quantitatively defined• Policies are definedPolicies are defined• Practices/processes used to achieve the goals• Objectives are Identified


The PDCA CycleThe PDCA CycleDo (D): Execute the plan( ) p

• Create the practices (define them)• Provide trainingo de t a g• Perform the work according to the defined practice


The PDCA CycleThe PDCA CycleCheck (C): Check the Results( )

• Determine if work is progressing to plan.• Will anticipated results be realized? a t c pated esu ts be ea ed• Are goals and objectives satisfied?


The PDCA CycleThe PDCA CycleAct (A): Take the Necessary Action( ) y

• Devise measures and appropriate actions if work is not progressing to plan.

• Look for the cause of abnormalities.• Update the plan.• Update training materials if needed• Update training materials if needed.

Tough Love


Certified Software Q lit A l tQuality Analyst€¦ · Certified Software Q lit A l tQuality Analyst...

Documents

Transcript of Certified Software Q lit A l tQuality Analyst€¦ · Certified Software Q lit A l tQuality Analyst...