1.Multiple choices.(多选题)
(1)Standard of software engineering project is defined as a of the developed product.
a.the minimal level of performance
b.the maximum level of performance
c.robustness
d.organization
(2)Quality assurance of software is .
a.an emerging subdiscipline of software engineering
b.a management function
c.as a verification function
d.as a validation function
(3)Quality criteria suggested by Boehm and other persons include more than .
a.19 b.20 c.21 d.22
(4)A quality assurance team should be .
a.associated with any particular development group
b.depended upon any particular development group
c.responsible for reporting directly to management
d.in-depended upon any particular development group
(5)The main goals of research in software engineering are .
a.development of usable software standards
b.development of accepted applicable standards
c.development of generally applicable standards
d.to overcome the major hurdle in the path of software management
(6)Some software standards developed by IEEE and ANSI describe .
a.configuration management plans
b.documentation
c.specification practices
d.software comparison
(7)The activity of quality assurance involves .
a.verification activity
b.program walkthroughs
c.design reviews
d.validation activity
(8)The process of software development includes .
a.verification function
b.management function
c.validation function
d.writing code
2.Fill in the blanks with appropriate words or phrases.(填空)
(1)The development team’s responsibility is to ____.
(2)Quality assurance must ensure that.
(3)Software quality assurance is now an of software engineering.
(4)Assessment of software quality still relies on
(5)We are not yet capable of quantifying .
(6)At each stage of the software life cycle the activity of software quality assurance is clo-sely related to.
(7)One of the elusive nature of software quality is .
(8)The activity of quality assurance also involves .
a.emerging subdiscipline of software engineering
b.checking the finished product and its associated documentation to be conformed with exist standards
c.most software characteristics
d.validating the system
e.verification and validation activities
f.a product meets or exceeds prespecified standards
g.the judgement of skilled individuals
h.to develop software standards for quality assurance
答案：
1 (1)a，c，d (2)a，b (3)a，b (4)c，d
(5)a，b，c，d (6)a，b，c，d (7)b，c (8)a，c，d
2 (1)d (2)f (3)a (4)g (5)c (6)e (7)h
SOFTWARE QUALITY ASSURANCE
The activity of software quality assurance is closely related to verification and validation activities carried out at each stage of the software life cycle[1].Indeed，in many organizations there is no distinction made between these activities.However，quality assurance and other verification and validation activities are actually quite separate，with quality assurance being a management function and verification and validation being part of the process of software development[2].
An appropriate definition of software quality assurance is provided by Bersoff(1984)：Quality assurance consists of those procedures，techniques and tools applied by professionals to ensure that a product meets or exceeds prespecified standards during a products development cycle[3];and without specific prescribed standards，quality assurance entails ensuring that a product meets or exceed a minimal industrial and / or commercially acceptable level of excellence.
This definition is，of course[4]，a fairly general one and it suggests that，firstly，software standards can be established and，secondly，the level of excellence of a software product can be estimated.
The development of software engineering project standards is an extremely difficult process. A standard is some abstract representation of a product which defines the minimal level of performance，robustness，organization，etc.，which the developed product must attain[5].At the time of writing，some software standards have been developed by the IEEE，ANSI and military organizations.
These standards describe configuration management plans，documentation，specification practices，software comparisons，etc.Other standards which are currently under development include standards for reliability，measurement，the use of Ada as PDL[6]，software testing and others.Bransta d and Powell(1984)describe both existing and planned software standards as well as discussing standardization in more general terms.
The problem with national software standards is that they tend to be very general in nature. This is inevitable as，unlike hardware，we are not yet capable of quantifying most software characteristics.Effective quality assurance within an organization thus requires the development of more specific organizational standards.
Of course，the problem which arises in developing software standards for quality assurance and which makes the assessment of the level of excellence of a software product difficult to assess is the elusive nature of software quality.Boehm et al.(1978)suggest that quality criteria include but are not limited to：
Economy Correctness Resilience
Integrity Reliability Usability
Documentation Modifiability Clarity
Understandability Validity Maintainability
Flexibility Generality Portability
Interoperability Testability Efficiency
Modularity Reusability
Exactly how some of these criteria may be quantified is not clear.Furthermore，as Buckley and Poston(1984)point out，parts of this definition may have no value for a particular product.It may be possible to transfer a system from a microcomputer to a large mainframe but this is often a nonsensical thing to do.Assessment of software quality thus still relies on the judgement of skilled individuals although this does not mean that it is necessarily inferior to quantitative assessment.After all，we cannot assess a painting or a play quantitatively yet this does not preclude a judgement of its quality.
Within an organization，quality assurance should be carried out by an independent software quality assurance team who reports directly to management above the project manager level.The quality assurance team should not be associated with any particular development group but should be responsible for quality assurance across all project groups in an organization.
The activity of quality assurance involves sitting in on design reviews[7]，program walkthroughs，etc. ，and reporting on the overall quality of the product as it is developed.It also involves checking that the finished product and its associated documentation conform to those standards which exist.The quality assurance team may also assess if the different representations of a product(requirements，design，code)are consistent and complete.
Notice that quality assurance is not the same as system testing.It is the development or testing team’s responsibility to validate the system，with the quality assurance team reporting on both the validation and the adequacy of the validation effort.This naturally involves quality assurance being closely associated with the final integration testing of the system.
Software quality assurance is now an emerging subdiscipline of software engineering[8].As Buckly and Poston point out，effective software quality assurance is likely to lead to an ultimate reduction in software costs.However，the major hurdle in the path of software management in this area is the lack of usable software standards.The development of accepted and generally applicable standards should be one of the principal goals of research in software engineering.
NOTES：
[1] carried out... 分词短语修饰activities。
[2] with quality assurance... development介词with引导的独立分词结构，起补充说明的作用。
[3] 主句谓语是consists of，其宾语为分词短语修饰的procedures，techniques，and tools。
[4] of course：插入语，译为“当然”。
[5] 此句包括两个定语从句：第一个定语从句which defines中which指representation;第二个定语从句which the developed修饰performance，robustness，organization。
[6] Ada语言(一种程序设计语言，以Agusta Ada Byron命名);PDL：程序设计语言。
[7] sitting in on design reviews：列席设计评审会议。
[8] emerging subdiscipline of... ：……的新兴分支。
KEYWORDS
software quality assurance 软件质量保证
software standard 软件标准
翻译:
软件质量保证活动与软件生存周期各阶段的验证和有效性确认活动紧密关联。事实上，在许多组织中这些活动没有明显的区别。尽管如此，质量保证实际上与其他验证和有效性确认活动相差甚远，质量保证是一个管理功能，而验证和有效性确认是软件开发过程的一部分。
Bersoff(1984)给出了软件质量保证的恰当定义：质量保证由在产品开发周期中专业人员要确保产品达到或超过某些预先设定的标准所要用到的那些过程、技术和工具所组成。如果没有具体的规定性的标准，质量保证则需要保证产品达到或超过工商业可接受的优良性能的最低标准。
当然这是一种相当笼统的定义。它首先指出软件标准可以建立;其次软件产品的优良程度可以评测。
软件工程项目标准的开发是一个非常困难的过程。一个标准是一个产品的某种抽象表示，它定义了被开发产品必须达到的最低性能、健壮性、结构等。在写此文章时，一些软件产品标准已经由IEEE，ANSI和一些军事机构制定了。
这些标准描述了配置管理计划、文档、规范实施、软件对照等。其他一些处于开发阶段的标准包括可靠性、测量方法、Ada用作为程序设计语言、软件测试和其他方面的标准。Bransta和Powell(1984)描述了已有的和已规划的软件标准，用更概括的语言讨论了标准化问题。
软件的国家标准问题在于这些标准过于笼统，这是必然的，因为不像硬件，我们至今尚不能将大多数软件特性进行量化。因此有效的质量保证就要求开发更多特定的组织标准。
当然，为质量保证而开发软件标准所带来的问题及软件产品的优良程度难于评估是软件质量难以把握的本质。Boehm等人(1978)提出的质量准则包括但不局限于：
经济性 正确性 弹性
完整性 可靠性 可使用性
文档 可修改性 明晰性
易理解性 合法性 可维护性
灵活性 通用性 可移植性
互操作性 可测试性 效率
模块性 可重用性
如何精确量化其中的某些准则尚不清楚。而且，正如Buckley 和 Poston(1984)指出的那样，此定义的某些部分对特定产品也许毫无价值。把一个系统从一台微机移到一台大型机上是可能的，但这样做往往是毫无用处的。因此，软件质量的评估仍然依赖于熟练的个人判断。尽管这并不意味着此方法一定比定量评估差。尽管我们不能定量地评价一幅画或一场演出，但这毕竟不能阻止对其质量的判断。
在一个组织内，质量保证应由一个独立的软件质量保证小组来实施，该小组直接向项目经理层之上的管理层报告。质量保证小组不应与任何开发小组有联系，但要对本组织中所有的项目组的质量保证负责。
质量保证活动包括旁听设计复审、程序走查等，并报告开发过程中产品的整体质量。质量保证也包括检查已完成产品及其有关的文件说明是否与现有标准一致。质量保证小组也可以评估一件产品的不同表示方式(需求、设计、代码)是否一致和完备。
注意，质量保证不同于系统测试。系统有效性确认是开发或测试小组的责任，而质量保证小组要报告确认和确认工作是否充分。这自然意味着质量保证与系统最后阶段的综合测试有着密切的联系。
软件质量保证正成为软件工程的一个新兴分支。正如Buckley 和Poston所指出的，有效的软件质量保证很可能导致软件费用的最终降低。然而，在这一领域中软件管理的最主要障碍是缺乏适用的软件标准。为人们所接受和普遍适用的标准的开发应成为软件工程研究的一个主要目标。