Chapter 1

Question 1

The two working definitions of Quality

Answer 1

Producers viewpoint: The product meets requirements Customers viewpoint: The product is “fit for use:

Question 2

Define Quality Assurance

Answer 2

An activity that establishes and evaluates the processes that produce products. QA is a staff function.

Question 3

Define Quality Control

Answer 3

A process where a product compares to applicable standards and requirements. QC is considered a line function. Testing is a QC activity.

Question 4

Define Internal Auditing

Answer 4

A managerial control that functions by measuring and evaluating other functions and controls.

Question 5

Five perspectives of Quality

Answer 5

1- TRANSCENDENT- I know it when I see it 2- PRODUCT BASED- Possesses desired features 3- USER BASED- Fit for use 4- DEVELOPING AND MANUFACTURING BASED- Conform to requirements 5- VALUE BASED- At an acceptable cost

Question 6

The First Quality Gap

Answer 6

The Producer Gap. It is between what was expected to be delivered and what was actually delivered

Question 7

The Second Quality Gap

Answer 7

The Customer Gap. The second gap is between what the Producer actually delivered and what the Customer expected.

Question 8

Closing the Producer’s Gap The “McDonald’s Effect”

Answer 8

This occurs when IT closes the Producer’s gap with consistent practices. A Big Mac should be made and taste the same in any McDonald’s around the world because the processes are consistent

Question 9

Closing the Customer’s Gap

Answer 9

This occurs when Quality understands the needs of the user. This can be done by: Customer surveys Joint application development More user involvement Implementing Agile development strategies

Question 10

The Quality Message

Answer 10

Identifying customers needs in when, what, why and how are essential and can only occur with communication

Question 11

Internal and External Customers

Answer 11

Internal customers would include peers, co-workers, management and any other groups in the organization. External customers are those using the service or produced product by the organization. Organizations must identify and understand their customers both internal and external, and be dedicated to exceeding customer expectations.

Question 12

Cost of Quality (CoQ)

Answer 12

CoQ takes the total cost of prevention and appraisal as well as costs associated with failure of the product. CoQ is the cost beyond “getting it right the first time.”

Question 13

Three costs for CoQ

Answer 13

Prevention costs- Resources spent for ‘getting it right the first time”. These include spending for training workers, acquiring tools and planning. These are spent up front before production. Appraisal costs- Resources spent to create quality across the life cycle to meet the customers needs. Includes cost of in-process reviews, dynamic testing and final inspections. Failure costs- Costs accrued for not meeting the customers needs. These can be internal or external failures. Internal costs include rework, retesting, delays and lack of quality. External costs include law suits, complaints, bad debt, loss of revenue and costs of creating a help desk.

Question 14

Costs of Control

Answer 14

The total of Preventative and Appraisal costs. These are considered “good quality”. Costs of failure control are “poor quality” The greater number of issues caught up front will save money and resources.

Question 15

Software Quality Factors

Answer 15

Attribute of software that, if they are wanted and not present, constitute a business risk. Consists of: Product Operations- Correctness, Reliability, Efficiency, Integrity, Usability Product Revision- Maintainability, Testability, Flexibility Product Transition- Portability, Reusability, Interoperability

Question 16

Defect

Answer 16

An undesirable state. Two types: Process Defect- ex. Not following a test plan Product Defect- ex. Not having a Requirements document for the test plan

Question 17

Variability

Answer 17

The enemy of quality. ex. If a process takes 100 hours when executed, it should always take 100 hours. If it is run and takes 110 hours, this extra 10 hours are defined as variability. In software testing, the two types are: Variance from specifications- A defect from the perspective of the developer of a product Variance from what is desired: A defect from a user/customers perspective

Question 18

Process improvement models

Answer 18

CMMI-Dev- Process improvement model for software development (CMMI is only an IMPROVEMENT model) TMMI- Process improvement model for software development (TMMI is only an IMPROVEMENT model. It is often the second stage of combined CMMI and TMMI improvement models) ISO/IEC/IEEE 29119- A set of standards for software testing that can be used with any software in the organization.

Question 19

Software testing

Answer 19

The process of evaluating a deliverable with the intent of finding errors. Testing is NOT: A stage/phase of the product, Just finding broken code, a final exam or “Debugging”

Question 20

Principles of Software Testing

Answer 20

Principle can be defined as:

1. A general or fundamental law, doctrine or assumption
2. A rule or code of conduct
3. The laws and facts of nature underlying the working of an artificial device

Question 21

Developers are not good Testers

Answer 21

Reasons why:

1. Misunderstandings will not be detected because the programmer will assume what they heard is correct.
2. Improper use of the development process as the programmer may not understand the process
3. The individual may be blinded during testing by falling into the same trap
4. They may believe that they do defect-free work thus not thinking extensive testing is necessary

Question 22

Peter Scholtes

Answer 22

Created the contrast between effectiveness and efficiancy

Question 23

Patrick Townsend

Answer 23

Examines Quality in fact and Quality in perception

Question 24

Testing Strategy

Answer 24

Planning and conducting both Static testing (reviews, inspections) and Dynamic testing (unit, integrations, System and User acceptance testing).

Question 25

Factors affecting Software Testing

Answer 25

• People Relationships
• Scope of Testing
• Understanding the value of life cycle testing
• Poor test planning
• Testing constraints

Question 26

People Relationships

Answer 26

Some people believe that testing tries a person’s patience, fairness, ambition, credibility and capability and therefore, have a negative view of testers

Question 27

Scope of Testing

Answer 27

The extentsiveness of the test process. May begin as a narrow scope function and then become more broad as the project continues.

Question 28

Understanding the Value of Lifecycle Testing

Answer 28

Do not place testing toward the end of the lifecycle. Errors are more costly the further the project goes. Testing should be done in ALL phases of the project.

Question 29

Life Cycle Phase #1 - Requirements

Answer 29

Testing Activities

– Determine verification approach

– Determine adequacy of requirements

– Build a test plan

– Generate functional test cases/data based on

requirements

Question 30

Life Cycle Phase #2- Design

Answer 30

Testing activities

– Determine consistency of design with requirements

– Determine adequacy of design

– Generate structual and functional test cases/ data based on design

– Refine test cases written in the requirements phase

Question 31

Life Cycle Phase #3- Program (build/construction)

Answer 31

Testing activities

– Determine consistency of code with design

– Determine adequacy of implementation

– Generate and refine structual and functional test cases/data

Question 32

Life Cycle Phase #4- Test

Answer 32

Testing activities

– Test application system

Question 33

Life Cycle Phase #5- Installation

Answer 33

Testing activities

– Place tested system into production

Question 34

Life Cycle Phase #6- Maintainence

Answer 34

Testing activities

– Modify and retest

Question 35

Testing Constraints

Answer 35

Anything that inhibits the tester’s ability to fulfill their responsibilities is a constraint. These include:

– Limited schedule and budget

– Lacking or poorly written requirements

– Limited tester skills

– Lack of independence of the test team

Question 36

Most issues in testing occur due to

Answer 36

– Failing to define testing objective

– Testing at the wrong phase in the life cycle

– Using ineffective test techniques

Question 37

Ad-Hoc Testing

Answer 37

Testing with little structure and relying on familiarity of the system or program being tested. Limited to knowledge.

Question 38

Waterfall Model

Answer 38

The earliest method of structured system development. Often considered too rigid.

Question 39

Steps of the Waterfall Model

Answer 39

System Conceptualization- The consideration of all aspects of the targeted business function or process, determining how the aspects relate with one another and which aspects will be placed in the system.

Systems Analysis- Gathering system requirements to determine how requirements will be accomadating in the system.

System Design- Focused on data requirements, the software construction, and the interface construction

Coding- Creation of the software in regards to the data requirements

Testing- Focused on two areas: internal efficiency and external effectiveness. External effectiveness verifies the software is functioning as designed. Internal efficiancy verifies the code is efficient, standardized and well documented.

Question 40

The V Model

Answer 40

An extension of the Waterfall Model. Uses Verification testing in the shape of a V. The left of the V is the specification side. The left side uses Verification techniques. The right side of the V is the testing side. This side uses Validation techniques.

Question 41

Incremental Model

Answer 41

Sub-divides requirements into smaller modules and each increment adds additional functionality to the application.

Question 42

Iterative Model

Answer 42

The project is split into smaller pieces. allowing development to demonstrate results earlier on in the process and obtain valuble feedback from system users.

Question 43

Problems with the Iterative Model

Answer 43

Because the Iterative Model requires user feedback, this can lead to scope creep” as users may bring up desired functions outside of the process as they become familiar with the product.

Question 44

Prototype Model

Answer 44

The customer presents a product and the developer designs a prototype based on the needs of the customer. The prototype is coded, and is then shown to the customer who gives feedback.

Question 45

Steps of the Prototyping Model

Answer 45

Requirements Definition/Collection- Gathers a sub-set of the complete system requirements.

Design- After requirements are collected, the information is integrated into a new or existing design so it may be folded into the prototype

Prototype Creation/Modification- The information from the design is rapidly folded into the prototype

Assessment- The prototype is submitted to the users for review. Information is taken from user feedback.

Prototype Refinement- Information from the user is taken and the prototype is refined.

System Implementation- In most cases, the system is rewritten once requirements are understood.

Question 46

Problems with the Prototyping Model

Answer 46

Customers may think that the request for data is a final step in the prototype.