Software Quality Professional - Volume 1 Index - ASQ

Software Quality Professional - Volume 1 Index

Contents

Author Index
Subject Index

AUTHOR INDEX

B

Barber, Glenn A. See Brennan, Lorin

Beizer, Boris, “Software Is Different,” (vol. 1, no. 1):44-54.

Ben-Yaacov, Giora, and Arun Joshi, “Investing in Quality Does Indeed Pay: A Software Process Improvement Case Study,” (vol. 1, no. 3):45-53.

Bøegh, Jørgen, “Quality Evaluation of Software Products,” (vol. 1, no. 2):26-37.

Boehm, Barry, and Hoh In, “Cost vs. Quality Requirements: Conflict Analysis and Negotiation Aids,” (vol. 1, no. 2):38-50.

Brennan, Lorin, and Glenn A. Barber, “A Response to: Why Software Quality Professionals Should Actively Oppose the Uniform Computer Information Transactions Act,” (vol. 1, no. 4):49-54.

Burnstein, Ilene, Ariya Homyen, Taratip Suwanassart, Gary Saxena, and Rob Grom, “A Testing Maturity Model for Software Test Process Assessment and Improvement,” (vol. 1, no. 4):8-21.

D

Davis, Alan M., “Achieving Quality in Software Requirements,” (vol. 1, no. 3):37-44.

Dekkers, Carol, “Overcoming the Myths of Software Development,” (vol. 1, no. 2):17-25.

G

Grom, Rob. See Burnstein, Ilene

H

Hadden, Rita, “Simple Ways to Succeed at Software Process Improvement,” (vol. 1, no. 1):38-43.

Harauz, John “International Trends in Software Engineering and Quality System Standards: Ontario Hydro’s Perspective,” (vol. 1, no. 2):51-58.
“International Trends in Software Engineering and Quality System Standards: Ontario Hydro’s Perspective, Part 2,” (vol. 1, no. 3):30-36.

Homyen, Ariya. See Burnstein, Ilene

Houston, Dan, “Cost of Software Quality: Justifying Software Process Improvement to Managers,” (vol. 1, no. 2):8-16.

Humphrey, Watts S., “The Software Quality Profile,” (vol. 1, no. 1):8-18.

I

In, Hoh. See Boehm, Barry

J

Joshi, Arun. See Ben-Yaacov, Giora

K

Kaner, Cem, “Why Software Quality Professionals Should Actively Oppose the Uniform Computer Information Transactions Act,” (vol. 1, no. 4):41-48. Kassab, Lora. See Voas, Jeffrey

M

Munyan, R. Jack. See Weimer, Alan L. Musa, John D., “More Reliable, Faster, Cheaper Testing with Software Reliability Engineering,” (vol. 1, no. 1):27-37.

P

Paulk, Mark C., “Using the Software CMM with Good Judgment,” (vol. 1, no. 3):19-29.

R

Rakitin, Steven R., “Balancing Time to Market and Quality,” (vol. 1, no. 3):54-57.

S

Saxena, Gary. See Burnstein, Ilene

Suwanassart, Taratip. See Burnstein, Ilene

V

Van Veenendaal, Erik P. W. M., “Practical Quality Assurance for Embedded Software,” (vol. 1, no. 3):7-18.

Voas, Jeffrey, and Lora Kassab, “Using Assertions to Make Untestable Software More Testable,” (vol. 1, no. 4):31-40.

W

Wallace, Dolores. See Zelkowitz, Marvin V.

Weimer, Alan L., and R. Jack Munyan, “Recipe for a Successful System: Human Elements in System Development,” (vol. 1, no. 4):22-30.

Z

Zelkowitz, Marvin V., and Dolores Wallace, “Validating the Benefit of New Software Technology, “ (vol. 1, no. 1):19-26.

SUBJECT INDEX

Accreditation

Bøegh, Jørgen, “Quality Evaluation of Software Products,” (vol. 1, no. 2):26-37.

Appraisal. See also Assessment; Evaluation

Houston, Dan, “Cost of Software Quality: Justifying Software Process Improvement to Managers,” (vol. 1, no. 2):8-16.

Assertions

Voas, Jeffrey, and Lora Kassab, “Using Assertions to Make Untestable Software More Testable,” (vol. 1, no. 4):31-40.

Assessment. See also Appraisal; Evaluation

Burnstein, Ilene, Ariya Homyen, Taratip Suwanassart, Gary Saxena, and Rob Grom, “A Testing Maturity Model for Software Test Process Assessment and Improvement,” (vol. 1, no. 4):8-21.

Capability Maturity Model (CMM)

Burnstein, Ilene, Ariya Homyen, Taratip Suwanassart, Gary Saxena, and Rob Grom, “A Testing Maturity Model for Software Test Process Assessment and Improvement,” (vol. 1, no. 4):8-21.

Hadden, Rita, “Simple Ways to Succeed at Software Process Improvement,” (vol. 1, no. 1):38-43.

Paulk, Mark C., “Using the Software CMM with Good Judgment,” (vol. 1, no. 3):19-29.

Case Studies

Harauz, John “International Trends in Software Engineering and Quality System Standards: Ontario Hydro’s Perspective,” (vol. 1, no. 2):51-58. “International Trends in Software Engineering and Quality System Standards: Ontario Hydro’s Perspective, Part 2,” (vol. 1, no. 3):30-36.

Change Management

Ben-Yaacov, Giora, and Arun Joshi, “Investing in Quality Does Indeed Pay: A Software Process Improvement Case Study,” (vol. 1, no. 3):45-53.

Dekkers, Carol, “Overcoming the Myths of Software Development,” (vol. 1, no. 2):17-25.

Hadden, Rita, “Simple Ways to Succeed at Software Process Improvement,” (vol. 1, no. 1):38-43.

Classification

Zelkowitz, Marvin V., and Dolores Wallace, “Validating the Benefit of New Software Technology, “ (vol. 1, no. 1):19-26.

Communication

Beizer, Boris, “Software Is Different,” (vol. 1, no. 1):44-54.

Dekkers, Carol, “Overcoming the Myths of Software Development,” (vol. 1, no. 2):17-25.

Weimer, Alan L., and R. Jack Munyan, “Recipe for a Successful System: Human Elements in System Development,” (vol. 1, no. 4):22-30.

Complexity

Beizer, Boris, “Software Is Different,” (vol. 1, no. 1):44-54.

Conflict Resolution

Boehm, Barry, and Hoh In, “Cost vs. Quality Requirements: Conflict Analysis and Negotiation Aids,” (vol. 1, no. 2):38-50.

Cost of Quality

Houston, Dan, “Cost of Software Quality: Justifying Software Process Improvement to Managers,” (vol. 1, no. 2):8-16.

Humphrey, Watts S., “The Software Quality Profile,” (vol. 1, no. 1):8-18.

Kaner, Cem, “Why Software Quality Professionals Should Actively Oppose the Uniform Computer Information Transactions Act,” (vol. 1, no. 4):41-48.

Costs

Boehm, Barry, and Hoh In, “Cost vs. Quality Requirements: Conflict Analysis and Negotiation Aids,” (vol. 1, no. 2):38-50.

Cultural Change

Dekkers, Carol, “Overcoming the Myths of Software Development,” (vol. 1, no. 2):17-25.

Hadden, Rita, “Simple Ways to Succeed at Software Process Improvement,” (vol. 1, no. 1):38-43.

Customer Expectations

Davis, Alan M., “Achieving Quality in Software Requirements,” (vol. 1, no. 3):37-44.

Rakitin, Steven R., “Balancing Time to Market and Quality,” (vol. 1, no. 3):54-57.

Customer Satisfaction

Rakitin, Steven R., “Balancing Time to Market and Quality,” (vol. 1, no. 3):54-57.

Defects. See also Failures

Humphrey, Watts S., “The Software Quality Profile,” (vol. 1, no. 1):8-18.

Van Veenendaal, Erik P. W. M., “Practical Quality Assurance for Embedded Software,” (vol. 1, no. 3):7-18.

Voas, Jeffrey, and Lora Kassab, “Using Assertions to Make Untestable Software More Testable,” (vol. 1, no. 4):31-40.

Electronic Commerce

Brennan, Lorin, and Glenn A. Barber, “A Response to: Why Software Quality Professionals Should Actively Oppose the Uniform Computer Information Transactions Act,” (vol. 1, no. 4):49-54.

Kaner, Cem, “Why Software Quality Professionals Should Actively Oppose the Uniform Computer Information Transactions Act,” (vol. 1, no. 4):41-48.

End Users

Weimer, Alan L., and R. Jack Munyan, “Recipe for a Successful System: Human Elements in System Development,” (vol. 1, no. 4):22-30.

Evaluation. See also Appraisal; Assessment

Bøegh, Jørgen, “Quality Evaluation of Software Products,” (vol. 1, no. 2):26-37.

External Failures

Houston, Dan, “Cost of Software Quality: Justifying Software Process Improvement to Managers,” (vol. 1, no. 2):8-16.

Failures. See also Defects

Houston, Dan, “Cost of Software Quality: Justifying Software Process Improvement to Managers,” (vol. 1, no. 2):8-16.

Musa, John D., “More Reliable, Faster, Cheaper Testing with Software Reliability Engineering,” (vol. 1, no. 1):27-37.

Faults. See Defects; Failures

Human Factors

Weimer, Alan L., and R. Jack Munyan, “Recipe for a Successful System: Human Elements in System Development,” (vol. 1, no. 4):22-30.

Incentives

Hadden, Rita, “Simple Ways to Succeed at Software Process Improvement,” (vol. 1, no. 1):38-43.

Inspection

Van Veenendaal, Erik P. W. M., “Practical Quality Assurance for Embedded Software,” (vol. 1, no. 3):7-18.

Intellectual Property Rights

Brennan, Lorin, and Glenn A. Barber, “A Response to: Why Software Quality Professionals Should Actively Oppose the Uniform Computer Information Transactions Act,” (vol. 1, no. 4):49-54.

Kaner, Cem, “Why Software Quality Professionals Should Actively Oppose the Uniform Computer Information Transactions Act,” (vol. 1, no. 4):41-48.

Internal Failures

Houston, Dan, “Cost of Software Quality: Justifying Software Process Improvement to Managers,” (vol. 1, no. 2):8-16.

International Issues

Harauz, John,“International Trends in Software Engineering and Quality System Standards: Ontario Hydro’s Perspective,” (vol. 1, no. 2):51-58.

Harauz, John,“International Trends in Software Engineering and Quality System Standards: Ontario Hydro’s Perspective, Part 2,” (vol. 1, no. 3):30-36.

Internet. See Electronic commerce

ISO 9000 Series

Ben-Yaacov, Giora, and Arun Joshi, “Investing in Quality Does Indeed Pay: A Software Process Improvement Case Study,” (vol. 1, no. 3):45-53.

Harauz, John, “International Trends in Software Engineering and Quality System Standards: Ontario Hydro’s Perspective,” (vol. 1, no. 2):51-58.

Legislation

Brennan, Lorin, and Glenn A. Barber, “A Response to: Why Software Quality Professionals Should Actively Oppose the Uniform Computer Information Transactions Act,” (vol. 1, no. 4):49-54.

Kaner, Cem, “Why Software Quality Professionals Should Actively Oppose the Uniform Computer Information Transactions Act,” (vol. 1, no. 4):41-48.

Maturity Models

Burnstein, Ilene, Ariya Homyen, Taratip Suwanassart, Gary Saxena, and Rob Grom, “A Testing Maturity Model for Software Test Process Assessment and Improvement,” (vol. 1, no. 4):8-21.

Hadden, Rita, “Simple Ways to Succeed at Software Process Improvement,” (vol. 1, no. 1):38-43.

Measurement

Dekkers, Carol, “Overcoming the Myths of Software Development,” (vol. 1, no. 2):17-25.

Hadden, Rita, “Simple Ways to Succeed at Software Process Improvement,” (vol. 1, no. 1):38-43.

Humphrey, Watts S., “The Software Quality Profile,” (vol. 1, no. 1):8-18.

Metrics

Beizer, Boris, “Software Is Different,” (vol. 1, no. 1):44-54.

Houston, Dan, “Cost of Software Quality: Justifying Software Process Improvement to Managers,” (vol. 1, no. 2):8-16.

Negotiation

Boehm, Barry, and Hoh In, “Cost vs. Quality Requirements: Conflict Analysis and Negotiation Aids,” (vol. 1, no. 2):38-50.

Paradigms

Beizer, Boris, “Software Is Different,” (vol. 1, no. 1):44-54. Plan-Do-Check-Act (PDCA) Cycle

Ben-Yaacov, Giora, and Arun Joshi, “Investing in Quality Does Indeed Pay: A Software Process Improvement Case Study,” (vol. 1, no. 3):45-53.

Prevention

Houston, Dan, “Cost of Software Quality: Justifying Software Process Improvement to Managers,” (vol. 1, no. 2):8-16.

Process Improvement

Ben-Yaacov, Giora, and Arun Joshi, “Investing in Quality Does Indeed Pay: A Software Process Improvement Case Study,” (vol. 1, no. 3):45-53.

Burnstein, Ilene, Ariya Homyen, Taratip Suwanassart, Gary Saxena, and Rob Grom, “A Testing Maturity Model for Software Test Process Assessment and Improvement,” (vol. 1, no. 4):8-21.

Dekkers, Carol, “Overcoming the Myths of Software Development,” (vol. 1, no. 2):17-25.

Hadden, Rita, “Simple Ways to Succeed at Software Process Improvement,” (vol. 1, no. 1):38-43.

Harauz, John, “International Trends in Software Engineering and Quality System Standards: Ontario Hydro’s Perspective,” (vol. 1, no. 2):51-58.

Houston, Dan, “Cost of Software Quality: Justifying Software Process Improvement to Managers,” (vol. 1, no. 2):8-16.

Humphrey, Watts S., “The Software Quality Profile,” (vol. 1, no. 1):8-18.Paulk, Mark C., “Using the Software CMM with Good Judgment,” (vol. 1, no. 3):19-29.

Product Liability

Brennan, Lorin, and Glenn A. Barber, “A Response to: Why Software Quality Professionals Should Actively Oppose the Uniform Computer Information Transactions Act,” (vol. 1, no. 4):49-54.

Kaner, Cem, “Why Software Quality Professionals Should Actively Oppose the Uniform Computer Information Transactions Act,” (vol. 1, no. 4):41-48.

Productivity

Rakitin, Steven R., “Balancing Time to Market and Quality,” (vol. 1, no. 3):54-57.

Project Management

Rakitin, Steven R., “Balancing Time to Market and Quality,” (vol. 1, no. 3):54-57.

Weimer, Alan L., and R. Jack Munyan, “Recipe for a Successful System: Human Elements in System Development,” (vol. 1, no. 4):22-30.

Quality Assurance

Beizer, Boris, “Software Is Different,” (vol. 1, no. 1):44-54.

Van Veenendaal, Erik P. W. M., “Practical Quality Assurance for Embedded Software,” (vol. 1, no. 3):7-18.

Quality Principles

Beizer, Boris, “Software Is Different,” (vol. 1, no. 1):44-54.

Regulations

Harauz, John, “International Trends in Software Engineering and Quality System Standards: Ontario Hydro’s Perspective, Part 2,” (vol. 1, no. 3):30-36.

Reliability

Musa, John D., “More Reliable, Faster, Cheaper Testing with Software Reliability Engineering,” (vol. 1, no. 1):27-37.

Requirements

Bøegh, Jørgen, “Quality Evaluation of Software Products,” (vol. 1, no. 2):26-37.

Boehm, Barry, and Hoh In, “Cost vs. Quality Requirements: Conflict Analysis and Negotiation Aids,” (vol. 1, no. 2):38-50.

Davis, Alan M., “Achieving Quality in Software Requirements,” (vol. 1, no. 3):37-44.

Harauz, John, “International Trends in Software Engineering and Quality System Standards: Ontario Hydro’s Perspective, Part 2,” (vol. 1, no. 3):30-36.

Rewards

Hadden, Rita, “Simple Ways to Succeed at Software Process Improvement,” (vol. 1, no. 1):38-43.

Risks

Boehm, Barry, and Hoh In, “Cost vs. Quality Requirements: Conflict Analysis and Negotiation Aids,” (vol. 1, no. 2):38-50.

Hadden, Rita, “Simple Ways to Succeed at Software Process Improvement,” (vol. 1, no. 1):38-43.

Musa, John D., “More Reliable, Faster, Cheaper Testing with Software Reliability Engineering,” (vol. 1, no. 1):27-37.

Van Veenendaal, Erik P. W. M., “Practical Quality Assurance for Embedded Software,” (vol. 1, no. 3):7-18.

Safety

Harauz, John, “International Trends in Software Engineering and Quality System Standards: Ontario Hydro’s Perspective,” (vol. 1, no. 2):51-58.

“International Trends in Software Engineering and Quality System Standards: Ontario Hydro’s Perspective, Part 2,” (vol. 1, no. 3):30-36.

Small Organizations

Paulk, Mark C., “Using the Software CMM with Good Judgment,” (vol. 1, no. 3):19-29.

Software Engineering

Harauz, John, “International Trends in Software Engineering and Quality System Standards: Ontario Hydro’s Perspective,” (vol. 1, no. 2):51-58.

Humphrey, Watts S., “The Software Quality Profile,” (vol. 1, no. 1):8-18.

Musa, John D., “More Reliable, Faster, Cheaper Testing with Software Reliability Engineering,” (vol. 1, no. 1):27-37.

Software Quality Management

Beizer, Boris, “Software Is Different,” (vol. 1, no. 1):44-54.

Burnstein, Ilene, Ariya Homyen, Taratip Suwanassart, Gary Saxena, and Rob Grom, “A Testing Maturity Model for Software Test Process Assessment and Improvement,” (vol. 1, no. 4):8-21.

Van Veenendaal, Erik P. W. M., “Practical Quality Assurance for Embedded Software,” (vol. 1, no. 3):7-18.

Weimer, Alan L., and R. Jack Munyan, “Recipe for a Successful System: Human Elements in System Development,” (vol. 1, no. 4):22-30.

Zelkowitz, Marvin V., and Dolores Wallace, “Validating the Benefit of New Software Technology, “ (vol. 1, no. 1):19-26.

Specifications

Davis, Alan M., “Achieving Quality in Software Requirements,” (vol. 1, no. 3):37-44.

Stakeholders

Boehm, Barry, and Hoh In, “Cost vs. Quality Requirements: Conflict Analysis and Negotiation Aids,” (vol. 1, no. 2):38-50.

Standards

Ben-Yaacov, Giora, and Arun Joshi, “Investing in Quality Does Indeed Pay: A Software Process Improvement Case Study,” (vol. 1, no. 3):45-53.

Bøegh, Jørgen, “Quality Evaluation of Software Products,” (vol. 1, no. 2):26-37.

Harauz, John, “International Trends in Software Engineering and Quality System Standards: Ontario Hydro’s Perspective,” (vol. 1, no. 2):51-58.

Harauz, John, “International Trends in Software Engineering and Quality System Standards: Ontario Hydro’s Perspective, Part 2,” (vol. 1, no. 3):30-36.

Static Analysis

Voas, Jeffrey, and Lora Kassab, “Using Assertions to Make Untestable Software More Testable,” (vol. 1, no. 4):31-40.

Surveys

Weimer, Alan L., and R. Jack Munyan, “Recipe for a Successful System: Human Elements in System Development,” (vol. 1, no. 4):22-30.

Technology Transfer

Zelkowitz, Marvin V., and Dolores Wallace, “Validating the Benefit of New Software Technology, “ (vol. 1, no. 1):19-26.

Testing

Bøegh, Jørgen, “Quality Evaluation of Software Products,” (vol. 1, no. 2):26-37.

Burnstein, Ilene, Ariya Homyen, Taratip Suwanassart, Gary Saxena, and Rob Grom, “A Testing Maturity Model for Software Test Process Assessment and Improvement,” (vol. 1, no. 4):8-21.

Musa, John D., “More Reliable, Faster, Cheaper Testing with Software Reliability Engineering,” (vol. 1, no. 1):27-37.

Van Veenendaal, Erik P. W. M., “Practical Quality Assurance for Embedded Software,” (vol. 1, no. 3):7-18.

Voas, Jeffrey, and Lora Kassab, “Using Assertions to Make Untestable Software More Testable,” (vol. 1, no. 4):31-40.

Training

Weimer, Alan L., and R. Jack Munyan, “Recipe for a Successful System: Human Elements in System Development,” (vol. 1, no. 4):22-30.

Uniform Commercial Code (UCC)

Brennan, Lorin, and Glenn A. Barber, “A Response to: Why Software Quality Professionals Should Actively Oppose the Uniform Computer Information Transactions Act,” (vol. 1, no. 4):49-54.

Kaner, Cem, “Why Software Quality Professionals Should Actively Oppose the Uniform Computer Information Transactions Act,” (vol. 1, no. 4):41-48.

Validation

Zelkowitz, Marvin V., and Dolores Wallace, “Validating the Benefit of New Software Technology, “ (vol. 1, no. 1):19-26.

Warranties

Brennan, Lorin, and Glenn A. Barber, “A Response to: Why Software Quality Professionals Should Actively Oppose the Uniform Computer Information Transactions Act,” (vol. 1, no. 4):49-54.

Kaner, Cem, “Why Software Quality Professionals Should Actively Oppose the Uniform Computer Information Transactions Act,” (vol. 1, no. 4):41-48.

 

Software Quality Professional Journal Cover

Featured advertisers


ASQ is a global community of people passionate about quality, who use the tools, their ideas and expertise to make our world work better. ASQ: The Global Voice of Quality.