外文翻译--软件质量保证方法.doc

英文资料翻译

WAYS OF SOFTWARE QUALITY ASSURANCE

一、Introduction of software quality assurance

Even the most jaded software developers will agree that high-quality

software is an important goal. But how do we define quality? A wag once said,

"Every program does something right, it just may not be the thing that we want

it to do."

fact, a definitive definition of software quality could be debated endlessly. For

the purposes of this book, the definition serves to emphasize three important

points:

1) Software requirements are the foundation from which quality is

measured.Lack of conformance to requirements is lack of quality.

2) Specified standards define a set of development criteria that guide the

manner in which software is engineered. If the criteria are not followed, lack of

quality will almost surely result.

3) A set of implicit requirements often goes unmentioned (e.g., the desire

forease of use and good maintainability). If software conforms to its explicit

1916 and spread rapidly throughout the manufacturing world. During the 1940s,

more formal approaches to quality control were suggested. These relied on

measurement and continuous process improvement as key elements of quality

management.

Today, every company has mechanisms to ensure quality in its products. In

fact, explicit statements of a company's concern for quality have become a

marketing ploy during the past few decades.

The history of quality assurance in software development parallels the

history of quality in hardware manufacturing. During the early days of

programmer. Standards for quality assurance for software were introduced in

into software development in the commercial world [IEE94]. Extending the

definition presented earlier, software quality assurance is a "planned and

systematic pattern of actions" [SCH98] that are required to ensure high quality

The SQA group serves as the customer's in-house representative. That is,

the people who perform SQA must look at the software from the customer's

point of view.Does the software adequately meet the quality factors noted in

pre-established standards? Have technical disciplines properly performed their

roles as part of the SQA activity? The SQA group attempts to answer these and

other questions to ensure that software quality is maintained.

2. SQA Activities

Software quality assurance is composed of a variety of tasks associated

with two different constituencies—the software engineers who do technical work

and an SQA group that has responsibility for quality assurance planning,

oversight, record keeping, analysis, and reporting.

Software engineers address quality (and perform quality assurance and

quality control activities) by applying solid technical methods and measures,

conducting formal technical reviews, and performing well-planned software

testing. Only reviews are discussed in this chapter. Technology topics are

discussed in Parts Three through Five of this book.

recommends a set of SQA activities that address quality assurance planning,

planning and is reviewed by all interested parties. Quality assurance activities

performed by the software engineering team and the SQA group are governed by

the plan. The plan identifies:

2) Participates in the development of the project’s software process

The SQA group reviews the process description for compliance with

organizational policy,internal software standards, externally imposed standards

3) Reviews software engineering activities to verify compliance with the