29 NESMA 桩和驱动 练习题

29 STUBS AND DRIVERS(桩和驱动)

名词解释

Stub译为桩，Driver译为驱动，在我看来，可以不管翻译直接去使用这两个英文单词，只因为翻译过来实在差点意思。

• Stub is used to simulate the calling modules in tested module working process. Generally they only process few data.
  Stub位于被测模块的下层，用于模拟测试模块工作过程中的调用模块。通常它们只处理很少的数据。

• Driver module is used to simulate superior module of tested module. It receives testing data, transmits related to tested module, starts tested module and prints corresponding results.
  Driver位于被测模块的上层，用于模拟被测模块的上级模块。接收测试数据，传送测试模块相关信息，启动测试模块，打印测试结果。

问题描述

为了测试系统或部分系统的目的，经常需要建立被称为桩和驱动的程序。桩是一个模拟程序，用于替换程序，包括相关的输入和输出流，并由测试对象调用。驱动是一种模拟程序，它取代了提供对测试对象的控制或调用的程序。

在功能点分析中是否应考虑项目团队开发的存根和驱动程序？

讨论

开发工作涉及到构建桩和驱动程序。它们在交付时不是产品的一部分，因此在任何情况下都不属于产品规模，例如，类似于转换软件。问题是，它们（例如转换软件）是否可以被视为项目规模的一部分。

转换软件即使只使用一次，也不会为开发的系统添加任何功能，并作为项目结果交付给客户。

桩和驱动是在项目期间使用的测试工具，可能会转移到应用程序维护中。桩和驱动是必须完全在系统开发领域内本地化的工具，以及在项目期间为使项目圆满结束而应采取的所有其他规定。它们不是用户可以识别的特征，从用户的角度来看，它们毫无意义。

答案

桩和驱动既不应包含在产品规模中，也不应包含于项目规模中。

---

Problem description

For the purpose of testing systems or parts of systems, often so-called stubs and drivers are built. A stub is a simulation program that replaces a program, including the associated input and output streams, and is called upon by the test object. A driver is a simulation program that replaces a program that provides the control or call to the test object.

Should the stubs and drivers, developed by a project team be considered in a function point analysis?

Discussion

Development effort is involved to build stubs and drivers. They are not a part of the product at delivery and thus in any case do not belong to the product size, similar to conversion software for example. The question remains whether they, like for example conversion software, can be considered as a part of the project size.

Conversion software is, even if used only once, and adding no functionality to the system developed, delivered to the client as a project result.

Stubs and drivers are testing tools that are used during the project and potentially are transferred to application maintenance. Stubs and drivers are tools that must be localized entirely within the domain of system development as well as all other provisions that should be taken during the project to bring the project to a successful conclusion. They are no features that are recognized by the user and they are meaningless from the user’s perspective.

Solution

Stubs and drivers should neither be included in the product size, nor in the project size.