Cste Cbok V6.2, Skill Set 1 Text Cards

Front 1

Quality has two working definitions:

Back 1

"• Producer’s Viewpoint – The quality of the product meets the requirements. newline
• Customer’s Viewpoint – The quality of the product is “fit for use” or meets the customer’s needs."

Front 2

Quality Assurance

Back 2

"a planned and systematic set of activities necessary to provide adequate confidence that products and services will conform to specified requirements and meet user needs. a staff function, responsible for implementing the quality policy defined through the development and continuous improvement of software development processes. • System development methodologies
• Estimation processes
• System maintenance processes
• Requirements definition processes
• Testing processes and standards"

Front 3

Quality Control

Back 3

"The process by which product quality is compared with applicable standards,and the action taken when nonconformance is detected. Quality control is a line function, and the work is done within a process to ensure that the work product conforms to standards and requirements. Quality control activities focus on identifying defects in the actual products produced. These activities begin at the start of the software development process with reviews of requirements, and continue until all application testing is complete.
It is possible to have quality control without quality assurance. For example, a test team may
be in place to conduct system testing at the end of development, regardless of whether that
system is produced using a software development methodology. Quality control relates to a specific product or service."

Front 4

Quality Control VS Quality Assurance

Back 4

• Quality control verifies whether specific attribute(s) are in, or are not in, a specific product or service.
• Quality control identifies defects for the primary purpose of correcting defects.
• Quality control is the responsibility of the team/worker.
• Quality control is concerned with a specific product.• Quality assurance helps establish processes.
• Quality assurance sets up measurement programs to evaluate processes.
• Quality assurance identifies weaknesses in processes and improves them.
• Quality assurance is a management responsibility, frequently performed by a staff
function.
• Quality assurance is concerned with all of the products that will ever be produced by a
process.
• Quality assurance is sometimes called quality control over quality control because it
evaluates whether quality control is working.
• Quality assurance personnel should never perform quality control unless it is to
validate quality control.

Front 5

What is the Cost of Quality?

Back 5

"additional costs associated with assuring that the product
delivered meets the quality goals established for the product. This cost component is called
the Cost of Quality, and includes all costs associated with the prevention, identification, and
correction of product defects. • Prevention Costs
• Appraisal Costs
• Failure Costs"

Front 6

Prevention Costs

Back 6

"Money required to prevent errors and to do the job right the first time. These normally
require up-front costs for benefits that will be derived months or even years later. This
category includes money spent on establishing methods and procedures, training
workers, acquiring tools, and planning for quality. Prevention money is all spent
before the product is actually built."

Front 7

Appraisal Costs

Back 7

"Money spent to review completed products against requirements. Appraisal includes
the cost of inspections, testing, and reviews. This money is spent after the product is
built but before it is shipped to the user or moved into production."

Front 8

Failure Costs

Back 8

"All costs associated with defective products that have been delivered to the user or
moved into production. Some failure costs involve repairing products to make them
meet requirements. Others are costs generated by failures such as the cost of operating
faulty products, damage incurred by using them, and the costs associated with
operating a Help Desk"

Front 9

Correctness

Back 9

Extent to which a program satisfies its specifications and fulfills the user's mission objectives.

Front 10

Reliability

Back 10

Extent to which a program can be expected to perform its intended function with required precision

Front 11

Efficiency

Back 11

The amount of computing resources and code required by a program to perform a function.

Front 12

Integrity

Back 12

Extent to which access to software or data by unauthorized persons can be controlled.

Front 13

Usability

Back 13

Effort required learning, operating, preparing input, and interpreting output of a program

Front 14

Maintainability

Back 14

Effort required locating and fixing an error in an operational program

Front 15

Testability

Back 15

Effort required testing a program to ensure that it performs its intended function

Front 16

Flexibility

Back 16

Effort required modifying an operational program.

Front 17

Portability

Back 17

Effort required to transfer software from one configuration to another

Front 18

Reusability

Back 18

Extent to which a program can be used in other applications - related to the packaging and scope of the functions that programs perform.

Front 19

Interoperability

Back 19

Effort required to couple one system with another.

Front 20

How is Quality Defined?

Back 20

Quality is defined in fact and in perception.

Front 21

What are the markers of Quality in Perception?

Back 21

Delivering the Right Product
Satisfying our Customer's Needs
Meeting the Customer's Expectations
Treating Every Customer with Integrity, Courtesy, and Respect

Front 22

What is "Life Cycle" Testing?

What is not "Life Cycle" Testing?

Back 22

Testing is the process of evaluating a deliverable with the intent of finding errors.
A stage/phase of the project
• Just finding broken code
• A final exam
• “Debugging”

Front 23

What are the markers of Quality in Fact?

Back 23

Doing the Right Thing
Doing it the Right Way
Doing it Right the First Time
Doing it On Time

Front 24

Why Do We Test Software? Prep

Back 24

To Find Defects,
To reduce risk inherent in computer systems.
To Satisfy the customer
Development proceess is defective

Front 25

Why Do We Test Software? CBOK

Back 25

The simple answer as to why we test software is that developers are unable to build defectfree
software.

Front 26

What is a Defect?

Back 26

Statement of Usability as specified in the Requirements
documentation it would be a product defect.

Front 27

Why are defects hard to find?

Back 27

Not looking- Test often are not performed because a particular test condition is unknown.
Looking but not seeing - Like losing your keys only to discover they were in plain sight the entire time.

The size and coplexity of the applications often makes it impossible to test everything

Front 28

Factors Affecting Software Testing
What are the People Related Challenges of SW testing.

Back 28

Training in testing (hardly any)
Releationships with developers.
Using Tools
Getting managers to understand testing.
Making the necessary time for testing.
Testing "over the wall" software
Trying to hit a moving target
Fighting a lose-lose situation
Having to say "no"
What are some of the people related challenges to SW testing.

Front 29

Factors Affecting Software Testing
What is the Scope of Software Testing

Back 29

1. Software testing can compensate for the fact that the software development process does not identify the true needs of the user, and thus test to determine whether or not the user’s needs have been met regardless of the specifications.

2. Finding defects early in the software development process when they can be corrected
at significantly less cost than detected later in the software development process.
3. Removing defects of all types prior to software going into a production state when it is
significantly cheaper than during operation.
4. Identifying weaknesses in the software development process so that those processes
can be improved and thus mature the software development process. Mature processes
produce software more effectively and efficiently.

At what stage in the SDLC is it the cheapest to find defects.

Front 30

Factors Affecting Software Testing
Misunderstanding Life Cycle Testing
What are the Life Cycle phases and definitions?

Back 30

Requirements - Determine verification approach
- Determine adequacy of design
- Generate functional test data
- Determine consistency of design with requirements
Design - Determine adequacy of design
- Generate structural and functional test data
- Determine consistency with design
Program (build/construction) - Determine adequacy of implementation
- Generate structural and functional test data for
programs
Test - Test application system
Installation - Place tested system into production
Maintenance - Modify and retest
Tester should be involved throughout the SDLC

Front 31

Independent Testing
What are some of the test manager's responsiblities:

Back 31

Test planning and estimation
• Designing the test strategy
• Reviewing analysis and design artifacts
• Chairing the Test Readiness Review
• Managing the test effort
• Overseeing acceptance tests

Front 32

Independent Testing
What are testers usually responsible for:

Back 32

Developing test cases and procedures
• Test data planning, capture, and conditioning
• Reviewing analysis and design artifacts
• Testing execution
• Utilizing automated test tools for regression testing
• Preparing test documentation
• Defect tracking and reporting