毕设外文文献翻译

xxxxxxxxx

毕业设计（论文）外文文献翻译

（本科学生用）

题目：Poduct Line Engineering: The State of the Practice

生产线工程：实践的形态

学生姓名：学号：

学部（系）:

专业年级:

指导教师：职称或学位：

2011年3月10日

外文文献翻译（译成中文1000字左右）：

【主要阅读文献不少于5篇，译文后附注文献信息，包括：作者、书名（或论文题目）、出版社（或刊物名称）、出版时间（或刊号）、页码。提供所译外文资料附件（印刷类含封面、封底、目录、翻译部分的复印件等，网站类的请附网址及原文】

Requirements engineering practices

A precise requirements engineering process— a main driver for successful software development —is even more important for product line engineering. Usually, the product line’s scope addresses various domains simultaneously. This makes requirements engineering more complex. Furthermore, SPL development involves more tasks than single-product development. Many product line requirements are complex, interlinked, and divided into common and product-specific requirements. So, several requirements engineering practices are important specifically in SPL development:

? Domain identification and modeling, as well as commonalities and variations across product instances

Separate specification and verification for platform and product requirements

? Management of integrating future requirements into the platform and products

? Identification, modeling, and management of requirement dependencies

The first two practices are specific to SPL engineering. The latter two are common to software development but have much higher importance for SPLs.

Issues with performing these additional activities can severely affect the product line’s long-term success. During the investigation, we found that most organizations today apply organizational and procedural measures to master these challenges. The applicability of more formal requirements engineering techniques and tools appeared rather limited, partly because such techniques are not yet designed to cope with product line evelopment’s inherent complexities. The investigation determined that the following three SPL requirements engineering practices were most important to SPL success.

Domain analysis and domain description.

Before starting SPL development, organizations should perform a thorough domain analysis. A well-understood domain is a prerequisite for defining a suitable scope for the product line. It’s the foundation for efficiently identifying and distinguishing platform and product requirements. Among the five participants in our investigation, three explicitly modeled the product line requirements. The others used experienced architects and domain experts to develop the SPL core assets without extensive requirements elicitation. Two organizations from the first group established a continuous requirements management that maintained links between product line and product instance requirements. The three other organizations managed their core assets’ evolution using change management procedures and versioning concepts. Their business did not force them to maintain more detailed links between the requirements on core assets and product instances.

The impact of architectural decisions on requirements negotiations.

A stable but flexible architecture is important for SPL development. However, focusing SPL evolution too much on architectural issues will lead to shallow or even incorrect specifications. It can cause core assets to ignore important SPL requirements so that the core assets lose relevance for SPL development. Organizations can avoid this problem by establishing clear responsibilities for requirements management in addition to architectural roles.

The work group participants reported that a suitable organizational tool for balancing requirements and architecture is roundtable meetings in which requirements engineers,

lead architects, and marketing and sales personnel discuss SPL implementation. Also,integrating the architects into customer negotiations will solve many problems that can arise from conflicting requirements. Another measure is to effectively document requirements and architectural vision so that product marketing and SPL architects can understand each other and agree on implementation.

Effective tool support

We often discussed tool support for SPL requirements engineering during the investigation. Because requirements engineering for SPL can become highly complex, effective tool support is important. Existing tools don’t satisfactorily support aspects such as variability management, version management for requirements collections, management of different views on requirements, or dependency modeling and evolution. So, an SPL organization must design custom solutions for these issues. Specifically, the two participants in the investigation that had established continuous requirements management had to maintain expensive customization and support infrastructures for their tool environment. The other organizations tried to avoid these costs by mitigating insufficient tool support through organizational measures such as strict staging of the requirements specification.

工程实践要求

精确的需求工程过程，它是一个成功的软件开发的主要动力，更是对产品线工程的重要。通常，产品线的范围涉及各个领域同时进行。它要求工程更加复杂。此外，SPL（1）的发展涉及的任务往往不止一个。许多产品线的需求是复杂的，相互关联的，为普通和特定产品的要求不一。如此，一些重要的需求工程具体做法是在SPL发展：

1、域辨识与建模，以及在产品实例的共性和差异

2、单独的规范和验证平台和产品的要求

3、管理融入平台和产品的未来需求

4、辨识，建模和属地管理的要求

前两个做法是与SPL工程有关的，后两个通常用来发展软件但对SPL更重要。可以确定这些适应性的活动会严重影响产品线的长期成功运行。在调查过程中，我们发现，大多数企业使用这些组织性和程序性的措施来掌握这些挑战。而更多基本的工业技术要求和工具的适应性也被相当程度的限制住了，部分原因可能是这些技术还没被设计出能够完全拷贝生产线的功能。调查指出以下三个SPL工程要求表现是SPL取得成功的重要保证。

域分析和域描述

在开始发展SPL之前，我们应进行彻底域分析。一个容易理解的定义域是生产线的产品适用范围的先决条件。这是更有效的识别和区分平台和产品的要求。在我们调查的五个参与者，三个人有明确的对产品线建模的要求。其他人不依靠已有的经验而是用艺术和域分析的方法来发展SPL。从第一组的两个组织建立一个连续的要求管理，保持产品线和产品之间的副本要求的链接。其他三个组织管理其核心资产的演化使用变更管理程序和版本概念。它们的联系并没有强迫他们更关心核心资产和产品实例之间的细微联系。

于平台要求协商中的冲击

一个稳定而灵活的平台对SPL的发展是十分重要的。但是，过于在平台上过于注重SPL则会产生一些阴影，甚至是不可收拾的结果。它可以让我们忽视SPL要求的重要性，故而使SPL的发展失去连贯性。组织性可以通过清除除了平台以外的责任要求避免这种问题。

参加该工作的工作组报告说，一个合适组织性工具对于平衡性要求与平台是符

合工程人员要求的，并领导平台、市场以及私人贩卖者来讨论SPL的发展。与此同时，将平台整合日常的生活也可以解决很多导致冲突性要求上升的问题。另一个措施能更好的展现文件要求和平台视觉，那样的话，产品市场与SPL设计师能更好的了解对方并相互讨论。

有效的工具支持

在调查过程中我们经常讨论的工具SPL的需求工程的支持。由于工程SPL的要求可以变得非常复杂，有效的工具支持也很重要。对于重要的环节，现有的工具并没有令人满意地支持，如变性管理，版本管理的要求收集，管理上的不同意见、要求，或依赖建模和演化方面。所以，一个SPL组织必须为这些问题的设计定制解决方案。具体来说，在调查的两个要求，建立了管理的不断参与者必须维持昂贵的定制和支持他们的工具环境的基础设施。其他组织试图避免这种代价，他们通过有组织的措施诸如严格规范的生产工艺来缓解这些不足。

注（1）:Standard PHP Library 标准PHP类库

指导教师审阅意见：

指导教师：

年月日