我认为这种 OO 技术很有前途，但是告诉我，既然对象共享行为和数据，那么您如何称呼对象为实现它的行为义务而做的事情呢？

您可能得到如下答案：

• "它是一个职责！"（Wirfs-Brock）
• "它是一项操作"（Booch）
• "它是一项服务"（Coad/Yourdon）
• "它是一个（虚）函数"（Stourstrup）
• "它是一个方法"（其他很多人）

如果这还不足以让您混淆的话，那么就不要问您如何用图形表示我们称之为对象和类的东西了。（它是一个矩形、一片云，等等。）虽然这看上去很愚蠢，但是实际情况是，我们软件工程领袖的其中一些最显著的共识（继承、关系、封装），由于在术语和表示法上的微小区别而无法得到共享，或者至少变得混乱。换言之，不管是 OO 工程科学还是将要获得的利益都不能继续向前发展，因为还没有发明用来描述该科学的语言。当然，要在这些作者、方法学家 和独立思想者中达成共识不是一件小事情，但是最终UML面世了，软件工程科学又向前迈进了一大步。

虽然需求管理方法学可能不像 UML 出现之前的 OO 方法学所形成的巴比塔那样糟，但是它却经历了同样的一些问题--尤其是对常见词汇的模糊、不一致和过度使用非常盛行。这些词汇（包括诸如"用例"、"特性"和"需求"这样的基本概念）是"每个人都理解"的日常词汇，但是在给定的上下文中每个人又赋予了它们自己的含义。结果就是沟通不畅。这种情况仅在将达成共识作为成功标准的领域中发生。Booch [Booch 1994]引用了 Stepp 的说法：

科学中普遍存在的一个问题是为观察到的对象和情形构造有意义的分类。这样的分类能推动人们对观察以及后续的科学理论开发的理解。

为了推动需求的"科学理论"，我们不得不面对术语的问题。

本文的目的在于，通过定义并描述用于说明系统软件需求的一些最常见术语和概念，来初步探讨一下软件工程的原理。为此，我们希望提供一个能让所有涉众（用户、经理、开发人员等）达成共识的基础。当然如果我们更有效地交流并因此获得一致看法，那么就可能更快地开发并交付更高质量的系统。

本文重点不在于需求管理的原理--关于这方面笔者在建议读物中推荐了很多参考书目。本文的目的仅是帮助该领域中的从业者提高他们对系统正确行为的基本认识。

问题域与解决方案域的对比
在开始描述具体的术语之前，我们首先要意识到需要从两个完全不同的方面定义术语：问题方面和解决方案方面。我们分别称之为问题域和解决方案域。

问题域
如果我们在问题域上做一次"低空滑翔"，就会发现许多实际生活周围的事物。比如"滑翔"过人力资源部门时，会看到雇员、负责发工资的职员以及工资支票。"滑翔"过重型设备工厂时，我们会看到焊工、焊接控制器、焊接机器人和电极。"滑翔"过万维网时，我们会看到路由器和服务器群集，以及具有浏览器、电话机和调制解调器的用户。换句话说，在任何问题域中，我们可以轻易地识别出我们看到和接触到的事物（实体）。有时候，我们甚至可以看到这些事物之间的关系；比如，web 用户和浏览器之间就是一对一的关系。我们可能还会看到从一个事物传递到另一个事物的消息："焊接工似乎正在往焊接机器人的'大脑'中编制工作次序"。

如果我们是敏锐的观察者，可能会发现亟待解决的问题："焊接工对不能安排正确的工作次序感到气馁"或者"注意到雇员输入薪水数据与收到支票之间有令人不愉快的时间延迟！"。有些问题似乎只是在乞求一种解决方案。也许我们可以构建一个系统（更好的可编程控制器、更有效的工资处理）以帮助那些可怜的用户解决这些问题。

 

基于用户和涉众需求

然而在我们构建新系统之前，我们需要确保理解了该问题域内用户的真正需要。如果没有，我们可能会发现焊接工只能愁眉苦脸，因为他就好像脚上得了鸡眼一样痛苦，结果就是他和他的经理都不会对购买我们最新的"SmartBot"自动焊接控制单元感兴趣。我们还注意到当我们试图销售 SmartBot 时，经理是购买决策中的关键涉众。我们不记得在"滑翔"中看见过她。（也许她当时正在吸烟室，而那里正是我们摄像头的盲区）。换言之，不是所有的涉众都是用户，并且如果我们希望有机会卖出SmartBot，则我们必须同时理解两个社区（涉众和用户）的需要。为了简便起见，我们称所有这些需要为涉众需求，但是我们要不断地提醒自己系统的潜在用户有时代表了很重要的一种涉众类型。

我们将涉众需要定义为：

业务、个人或操作问题（或机会）的一种反映，其中这些问题必须得到解决，以使用户相信他们考虑、购买或使用新系统的选择是正确的。

于是涉众需求就成为与问题域关联问题的一种表示。这些涉众需求并未给出解决方案，但是以一个最初的角度，使我们了解需要实现哪些可行的解决方案。比如，如果我们会见重型设备制造厂中管理焊接工的经理，就可能发现焊接大量重复性的焊接件会消耗巨大的制造时间和成本。另外，焊接工似乎不会喜欢这些具体工作，因为他们一直处在被烫伤的危险中。更糟的是，该工作的物理方面（重复、难以琢磨的手工操作位置以及对视力的危害等）带来了个人安全问题以及长远的健康隐患。

充分理解了这些事项，我们就可以开始定义其中一些涉众需求：

• 我们需要一种自动化的方法来制造大量重复的焊接件，而不用让焊接工手动控制电极。
• 我们很乐意能有一位焊接工，但是我们需要将其移到焊接件以外的安全区域并且远离那些移动的机器。
• 我们需要能轻松使用"训练模式"，这样一般的焊接工也能够"训练"机器为他们做大部分工作。
• 我们需要使训练模式中具有更大的灵活性，并且意识到这可能与用户友好性需要的某些方面产生冲突。

当理解了系统的这些不同方面后，主观上我们会将这些发现"堆放"在一个称之为涉众需求的小堆中。

解决方案域
幸运的是，对问题域的"滑翔"不会花很长时间，并且（通常）我们在问题域中发现的东西也不是很复杂。当我们完成"滑翔"并开始构建我们观察到的问题和需要的解决方案时，就开始理解问题。是的，我们已经开始了最难的一部分：构建问题的解决方案。我们考虑活动集（系统定义、设计等）、为了解决问题而发现和构建的"事物"（计算机、机械臂等），以及在解决方案域的处理部分中创建的工件（比如源代码、用例和测试）。

在解决方案域中，我们必须成功地执行很多步骤和活动，这样才能定义、构建并最终部署问题的成功解决方案。它们包括：

1） 理解用户需求

2） 定义系统

3） 管理范围并管理变更

4） 精化系统定义

5） 构建正确的系统

简言之，上述步骤定义了需求管理的一个简化过程。本文不打算详细介绍这些步骤；关于这些内容我们会为您推荐一些参考读物，包括课本"Managing Software Requirements"，[Leffingwell, 1999]。本文与该参考书保持一致，这里提供的大部分定义都来自该参考书。

比如，在参考书[Leffingwell, 1999]中，我们会发现需求管理是这样定义的：

获取、组织和记录系统需求的系统化方法，在客户与项目团队之间建立并维护对系统需求变更的一致意见的过程。

还是让我们继续寻找并定义用于描述待建系统所需的其他更多的需求管理术语吧。

解决方案域中的常见需求术语
　

产品或系统的特性
当我们开始考虑已识别问题的解决方案时，很自然会匆匆记下系统的特性。特性在系统的开发中占有很有趣的地位。它们看上去介于用户真正需要的表达与系统实现这些需要的详细方式描述之间。这样，它们就为按照抽象的方式描述系统提供了一种方便的构造，或者如果您愿意的话，提供一种"速记方法"。由于需要解决的问题存在很多可能的解决方案，所以在某种意义上特性提供了特定系统解决方案的最初范围；它们描述了系统打算做什么以及不打算做什么。

我们将特性定义为
系统为实现一个或多个涉众需要而提供的服务。

我们可以很容易地使用用户熟悉的术语用自然语言来表示特性。例如：

• 系统使用的是标准的北美电源。
• 树浏览器提供了组织缺陷信息的一种手段。
• 家用照明控制系统具有与标准家用自动化系统的接口。

由于特性是从涉众需求派生而来的，所以我们将它们安排在金字塔的下一层，即需要的下面。与此同时，我们还从问题域（需要）转移到了解决方案域的第一层（特性）。

有一点很重要，需要注意，那就是特性不仅仅是涉众需求的精化（增加了细节）。相反，它们是用户提供的对问题的直接响应，并且它们为我们提供了问题的顶级解决方案。

通常，我们应该能够通过定义 25 到 50 种刻画系统行为的特性来描述系统。如果您发现手头有超过 50 种的特性，那么可能是因为您没能抽象出系统的真正特性或者是系统过于庞大而难于理解，您需要考虑将其分为更小的部分。

特性是用自然语言描述的，所以读到该清单的任何涉众都能立即获得对系统行为的基本理解。特性清单会缺乏细粒度的详细程度。这没关系。我们只是在试着交流目的，并且由于很多涉众都是非技术人员，所以过多的细节可能会让他们混淆甚至干扰理解。通过例子，我们 SmartBot 自动焊接机器人的部分特性清单可能包括：

• 允许焊接工教导机器人焊接哪些路径的"lead through path"训练模式
• 支持重复焊接次序的"step-and-repeat"特性。

用例
当我们进一步考虑系统完成用户任务的方法时，我们可能发现使用用例技术来进一步描述系统行为很有利益。该技术在很多书籍[Jacobson 1992]中已经得到了很好的发展，并且也是行业标准统一建模语言[Booch 1999]的一个组成技术。

从技术上说，用例：

描述了系统执行的、为用户带来价值的一系列动作。

换言之，用例描述了有助于用户实现他们期望的一系列用户和系统交互。再换一种说法，用例描述了用户和系统如何共同合作以实现所识别的特性。

用例还引进了参与者这项构造。参与者只是当时使用系统的用户的一个标签。在 UML 中，用一个简单的椭圆来表示用例，而参与者则用一个带有名称的线条画表示。所以可以如下所示用一个简单的图来说明这两者。

用例技术规定了参与者如何实现用例的一个简单的逐步过程。比如，用于 Step and Repeat 的用例可能如下所示：

步骤1：焊接工按下 step and repeat 按钮，启动该序列。

步骤2：焊接系统为驱动电动机供给电源，以便可以人工控制机器臂移动。

步骤3：焊接工握着扳机，将机器臂移动到焊接部位，并按下"weld here"按钮，焊接每一条需要焊接的线路。

用例技术提供了很多其他有用的构造，比如预描述和后描述（pre and post description）、可选流（alternate flow）等。我们将在后面详细讨论用例时再讨论它们。但是现在，我们只需要知道用例提供了一个优秀的方法用来描述如何实现系统特性。

出于计划的目的，可能需要除用例之外的一些方法来描述如何实现特定的特性。对于每个特性可能只需要几个用例即可（也许 3 到 10 个）。在描述用例过程中，我们详细阐述了系统的行为。随着其他特征的获得，用例也变得更加详细。

远景文档
在很多开发尝试中，问题的声明、关键涉众、用户需求、系统特性清单，也许还有示例用例都可以在一个被称为远景文档的文档中找到。它还有其他很多名称，比如项目章程（Project Charter）、产品需求文档（Product Requirements Document）、市场需求文档（Marketing Requirements Document）等。不管名称如何，远景文档强调了正在构建系统的总体意图和目的，因此，是那些被标明日期的特性和说明性用例的自然容器。换言之，远景文档捕获了系统的完全形态，并使用涉众需求、特性和用例来交流意图。

然而，我们不能简单地把这些特性和初始用例转交到开发团队手中，并期望他们很快开发出真正满足涉众需要的系统。我们可能需要在系统功能方面更加明确，并且可能涉及了各种新的涉众，包括开发人员、测试人员等。这是系统定义的下一层（软件需求）要解决的需要。

软件需求
软件需求在软件定义过程中提供了下一层特异性。在这一层上，我们必须指定足够的需求和用例，以便开发人员可以编写代码，并且测试人员可以测试这些代码是否满足需求。从图形上说，软件需求提供了我们金字塔的塔基。

什么是软件需求？尽管在过去的多年中已经有过很多种定义，但是我们发现需求工程创始人 Dorfman 和 Thayer[Dorfmann 1990]提供的定义最合适：

• 用户解决将实现一个目标的问题所需的软件功能，或者
• 必须被一个系统或者系统组件满足或拥有，以满足合同、标准、规范或其他正式发布文档的软件功能。

应用该定义，开发团队能够开发出更具体的需求集，以完善或精化前面讨论过的特性清单。每个需求都是某种特性，反之亦然。注意这种方法的简单性。我们有一个特性清单，然后通过编写一个为这些特性服务的需求集来精化它们。我们不编写任何其他需求。这避免了只是坐在椅子上、瞪着天花板，并"为该系统捏造一些需求"的诱惑。

该过程简单明了，但是并不容易。每个特性都需要检查，然后编写需求以支持该特性。不可避免地，为某项特性编写需求会引发您为已经检查过的特性添加新的需求，或者对其进行修订。

当然，您知道编写需求并不容易，并且可能需要指定大量需求。我们发现考虑三种类型或者种类的软件需求（功能性需求、非功能性需求和设计约束）很有帮助。

我们发现这三种需求在我们考虑需求的方式以及我们期望需求实现的任务方面很有帮助。让我们看一下这些不同类型的需求，以及您可以如何使用它们来定义期望系统的各个方面。

功能性需求

功能需求表达了系统行为。更具体地说，功能需求描述了输入和输出分别是什么、以及特定输入如何在不同时刻被转化成特定的输出。能有效工作的大部分软件应用程序都具有丰富的功能性需求。在指定这些需求时，要权衡模糊性（"当您按下 On 钮之后，系统就会打开"）与具体性这二者的关系，这一点很重要。给予设计人员和实现人员以尽可能多的设计和实现选择也很重要。如果我们过于具体，那么就可能过于限制开发团队，如果过于宽松，则开发团队就不知道系统应该实现哪些功能。

指定需求的正确方法不只一种。其中一种技术只简单采用了声明性的方法，并写下系统需要做的每一件详细的事件。

比如：在"weld here"输入被激活时，系统通过每 100 毫秒读取一次光编码器来数字化电极端的位置。

细化用例

在很多系统中，通过精化以前定义的用例并开发其他用例，则易于组织规范活动来全面细化系统。利用这项技术，您可以将用例步骤精化成更详细的系统交互。您还需要定义前置条件和后置条件（在用例之前和之后陈述系统假设），以及由于异常条件而需要的备用动作等。

由于用例在语义上是良好结构的，因此它们提供了一种组织和捕获系统行为的结构。下面是 Smartbot 的代表性用例。

非功能性需求

除了像输入转换为输出这样的功能性需求，大多数系统还需要定义一组着重指定其他系统"属性"的非功能性需求，比如性能需求、吞吐量、可用性、可靠性和可支持性。这些需求和面向输入输出的功能需求同样重要。通常，非功能性需求的表达方式是声明性的，如： "系统的平均故障间隔时间应该为 2000 小时"，"系统的平均修复时间应为 0.5 小时"，以及"Smartbot 最多应该能够存储和检索 100 条焊接路径"。

设计约束

与定义系统行为不同，第三类需求通常对系统设计或者我们用来构建系统的过程施加了限制。我们将设计约束定义为：

系统设计上的限制，或者系统开发步骤上的限制，它不影响系统的外部行为，但是必须被实现，以满足技术、业务或合同要求。

典型的设计约束可能是这样表达的："用 Java 为焊接工控制单元编程"。一般来说，我们将合理的设计约束看作其他需求，尽管符合这些限制的测试可能需要不同的技术。正如功能性和非功能性需求一样，这些约束在系统的设计和测试中扮演了不可或缺的角色。

分层结构需求

很多项目通过利用分层或父子结构表达这些需求而受益。父子结构需求是利用父需求表达的特异性的一种扩大。父子需求为您提供了一种增强和扩大规范的灵活的方法，同时还可以组织提供的详细程度。只看父需求，很容易按照易被用户理解的方法提供顶级规范。同时，实施人员可以快速检查详尽的"子需求"规范，以保证他们能够理解所有的实施细节。

注意，分层结构需求由三种标准类型的需求组成--功能性、非功能性和设计约束。这里只定义了这些需求间的细化关系。

可跟踪性
除了为描述我们用来说明系统需求的事物而定义的术语之外，我们现在将注意力转移到关键关系，即可跟踪性，也就是在这些事项之间可能存在的关系。

开发出高质量软件的一个重要因素就是在规范、构架、设计、实现和测试阶段理解或跟踪需求的能力。历史数据表明变更的影响通常被遗漏，系统的小小变更可能带来显著的可靠性问题。因此，跟踪关系并在发生变更时关联这些关系的能力，形成了很多现代软件质量保证过程的关键线程，尤其是在任务关键活动比如安全关键系统（医疗和运输产品），和故障的经济成本很高的系统（在线交易）中，形成了一个关键线程。

下面看一下我们如何定义需求可跟踪性：

可跟踪性关系是一种依赖关系，其中实体（故障、用例和需求）"traced to"在某种程度上依赖于它"traced from"的实体。

比如，我们已经描述了如何创建一个或更多软件需求，以支持远景文档中给定的特性或用例。因此，我们可以说这些软件需求与一个或更多特性具有可跟踪性关系。

影响分析和怀疑

另外，可跟踪性关系超出了简单依赖关系的范围，因为它提供了利用我们称之为"怀疑"的概念进行影响分析的能力。当变更出现在"traced from"（独立）需求中时，可跟踪性关系就开始"怀疑"，因此必须对"traced to "（依赖需求）进行检查，以保证它与源需求保持一致。

比如，如果我们使用可跟踪性将需求与特定测试关联，并且如果诸如"Smartbot 应该能够存储和检索最多 100 条焊接路径"这样的需求变为"Smartbot 应该能够存储和检索最多 200 条焊接路径"，那么从该需求跟踪而来的测试就值得怀疑，因为为测试第一个需求而设计的测试不太可能适合测试第二个需求。

变更请求和变更管理系统
最后，变更是不可避免的。对于有希望成功的项目，管理变更的过程是必不可少的。不管它们的来源是什么以及来源如何众多，所有变更包括影响特性和需求的请求需要有序地被引进和管理。任何变更管理系统的关键元素都是变更请求本身。

我们将变更请求定义为：

对系统的特性和/或需求作出修订或添加的正式请求。变更请求需要作为提议变更的结构化和形式化的陈述，以及围绕该变更的任何细节进入系统。为了管理这些变更，每个变更都要在系统中有自己的身份，这很重要。变更请求的简化形式可能为：

在大部分项目中，您会发现不缺少变更！实际上，您的问题是按照有序的方式管理、集成和（根据需要）拒绝不必要的变更。换言之，您需要一个管理变更过程。您的变更管理系统应该用于捕获所有输入，并将它们提交给变更控制委员会（CCB）来解决。CCB 由不超过 3 到 5 个代表项目关键涉众（客户、市场和项目管理）的人员组成，它管理和控制系统变更，因而在帮助项目成功方面扮演了关键角色。

结束语
刚一开始，我们就指出本文的目的在于帮助该领域的从业者提高他们回答下列基本问题的能力：
"系统究竟应该实施哪些行为？"

作为实现这一目标的第一步，我们定义和描述了分析人员以及负责描述问题域中问题的其他人员所使用的，用于表达将施加在预期解决方案上的需求的一些常见术语（比如涉众需要、特性、用例、软件需求等）。在这个过程中，我们还阐述了有效需求管理的一些关键概念。通过使用本文提供的术语和方法，您能够更有效地理解用户需要，并与开发人员、测试人员以及负责构建满足客户和用户需要的系统的其他技术团队成员交流提议解决方案的需求。

进一步定义和交流软件解决方案的其他更多关键方面的一项重要技术就是标准建模语言。统一建模语言（UML）是一种用于可视化、指定和文档化软件密集系统的工件的语言，并且提供了按照语义上更精确的方式表达这些技术构造的手段。本文的姊妹篇，Modeling the Requirements Artifacts with UML（利用 UML 建模需求工件），建立了更有效执行需求管理任务所必需的 UML 构造和扩展。

建议读物
[Leffingwell 1999] Leffingwell, Dean, and Don Widrig. Managing Software Requirements: A Unified Approach. Reading, MA: Addison Wesley Longman, 1999.

[Weigers 1999] Weigers, Karl. Software Requirements, Redmond Washington: Microsoft Press, 1999.

参考资料

• [Booch 1994] Booch, Grady. Object-Oriented Analysis and Design with Applications, 2nd ed. Redwood City, CA. Benjamin Cummings, 1994.
  
  　
• [Booch 1999] Booch, Grady, James Rumbaugh, Ivar Jacobson. The Unified Modeling Language User Guide. Reading, MA: Addison Wesley Longman,1999.
  
  　
• [Dorfmann 1990] Dorfmann, Merlin, and Richard H. Thayer. Standards, Guidelines, and Examples of System and Software Requirements Engineering. Los Alamitos, CA: IEEE Computer Society Press, 1990.
  
  　
• [Jacobson 1992] Jacobson, Ivar, Magnus Christerson, Patrik Jonsson, and Gunnar ?vergaard. Object-Oriented Software Engineering: A Use Case Driven Approach. Harlow, Essex, England: Addison Wesley Longman, 1992.
  
  　
• [Rumbaugh 1999] Rumbaugh, James, Ivar Jacobson, Grady Booch. The Unified Modeling Language Reference Manual. Reading, MA: Addison Wesley Longman, 1999.
  　
• 请参加Rational 中国论坛关于本文的讨论。
  　

其中第二点的"直接"要注意:如果一个顾客通过售票员买机票,那么对于售票系统来说,售票员是参与者而顾客不是.
由此又产生了业务建模和系统建模的区别:对于售票系统来说,当业务建模的时候,我们描述的是顾客来订票,可能还有票务中心的主任来询问售票情况等等事件.但是系统建模的时候,他们都不是我们的对象,我们描述为售票员要售票和提供售票情况的事件的描述,因此这两者在建模的不同阶段是不一样的.

在有些自动系统中,时间往往是触发系统工作的外部事物,因此参与者是时间,不可忽略.

识别参与者方法:面对一个系统时,你应该问这些问题:
谁使用系统?
谁改变系统数据?
谁从系统获取信息?
谁需要系统的支持来完成日常工作?
谁负责管理并维护系统正常运行?
系统要应付那些硬设备?
系统要和其他的系统交互吗?
谁对系统产生的结果感兴趣?
时间,气候等外部条件呢?
当你回答完这些问题之后,你的答案基本上就涵盖了参与者的候选人.

识别参与者的重要性:
1.根据参与者识别系统用例:因此为了完整系统的功能,你识别的系统参与者宁多勿少.
2.测试部署阶段你可能会通过识别者的角度去了解系统的完整性.
3.用例文档编写阶段,参与者不是很重要,但是你应该考虑参与者的泛化关系,避免出现用例的重复功能.



二.识别事件
罗列清楚系统事件,是正确建立系统用例的必要条件.

系统事件分为两类:系统外部事件和系统内部事件
外部事件就是外部参与者对系统交互的具体工作,内部事件就是系统内部触发的工作,通常由时间触发.

识别事件的方法:头脑风暴法-主语+谓语+宾语,描述系统可能发生的事情,尽可能全面,同样是宁多勿少的原则,不过你可以根据事件的重要程度进行一个排序,这能加深你对系统的认识.

通常把识别出来的事件列成一个表格:称为3A表
Actor  Action Aim
参与者  作甚么  业务目的
...  ...  ...

三.识别用例
用例定义:用例是一组用例实例
用例实例定义:系统执行的一系列动作,用以产生参与者可观测到的结果值

用例要点:
1.位于系统  --必须由系统运行
2.目标导向  --用例运行必须有所目的
3.止于边界  --可以观测到结果,并且是在边界和外部有所交互的
4.用户观点  --参与者观测
5.粒度   --是一组有共同目标或者可以类聚的目标的实例们组成

识别用例是从业务建模开始的,也就是说我们描述用例是从用户的角度即用户观点出发的识别行为,描述用例是用纯粹的业务语言,而不是技术语言.比如描述为清缴税款,而不是J2ee架构.因此,用户的命名也是从用户的角度出发,描述用户要做的一件通过系统完成有目的,有结果的行为.

用例的粒度不宜过细,过细的分解会导致用例描述的错误:
1.把交互的步骤成为一个用例,而不是把一类一系列步骤作为一个用例.例如,用户登陆是一个用例,错误的做法是把请求输入用户名也作为一个用例.
2.把必要的处理过程中的一些系统内部活动称作用例:验证用户,连接数据库,发送SQL请求等称作一个用例,其实都是用户登陆这一次交互的步骤而已.
3.把识别用例的工作当成是关系数据库分析的工作:称作四轮马车的错误,即CRUD(Create Read Update Delete).例如管理用户是一个用例,但是可能变成了增加用户,查询用户,修改用户,删除用户的"系统就是数据的增删改查"的认识论错误.

识别用例的一个关键性原则就是:站在用户的角度分析用户的目的,而不是站在系统的角度,更不是站在数据的角度.

通过建立的系统事件可以很顺利的画出用例图,但是应该记住"用例的本质是文字",所以我们最终要将用例图转化成用例文档.可以用下面的例子格式书写用例文档:
用例编号:
用例名:
用例描述:
参与者:
前置条件:开始该用例时的所必需的系统和环境状态
后置条件:结束该用例时的所具备的系统和环境状态
基本路径:
1…..××××
2……××××
3…..××××
扩展点:
2a.××××
2a1….×××××
补充说明:

前置条件和后置条件可以反应用例间的相互依赖关系.还可以防止漏掉某些用例

用例之间的关系:扩展extends,包含include,泛化

Abuky

http://abuky.sunsite.dk/index.html

Description:

Abuky stands for the Aoo BUg tracKing sYstem, while AOO stands for Art Of Open Source. Abuky is a system for tracking bugs and aiding the developer to fix them, written in Java with JSP as web interface.

Requirement:

Linux, Windows, Solaris

Download data:

No data feed available

Anthill Bug Manager

http://anthillbm.sourceforge.net/

Description:

Anthill is a tool that aids code development by keeping track of bugs in a multi-project, multi-developer environment. It accomplishes this with a clean, simple, and fast interface that contains all the essential features but avoids the enormous complexity associated with most other projects of this type.

Requirement:

OS Independent

Download data:

Downloadable files: 1617 total downloads to date

BTsys

http://btsys.sourceforge.net/

Description:

BTsys is a lightweight desktop bug tracking system, written using C# and ADO.NET for small developer teams. Easy to install and learn how to use.

Requirement:

All 32-bit MS Windows (95/98/NT/2000/XP)

Download data:

Downloadable files: 0 total downloads to date

BugBye

http://bugbye.sourceforge.net/

Description:

BugBye is a web-based bugtracking system developed using ASP.NET technology and C# as scripting language. It offers all the features needed to manage improvement, bugs, and so on. It also provide statistics help-desk management, and further options which allow the user to simplify all the stage of project development and maintainance.

Requirement:

All 32-bit MS Windows (95/98/NT/2000/XP)

Download data:

Downloadable files: 3077 total downloads to date

Bugfree

http://bugfree.1zsoft.com/English.html

Description:

A lightweight and simple web-based bug tracking system available in Chinese and English.

Requirement:

Windows

Download data:

Downloadable files: 4312 total downloads to date

Buglog

http://buglogv2.sourceforge.net/

Description:

Allows you to easily record bugs into a database along with description and screenshots of the bugs (file upload feature). The BLT allows tracking of all bugs on a project-wise basis thus making it a bug logging and tracking solution. BuglogV2 incorporates a powerful search feature allowing developers to locate bugs effortlessly.

Requirement:

All 32-bit MS Windows (95/98/NT/2000/XP)

Download data:

Downloadable files: 3763 total downloads to date

BugNet

http://www.bugnetproject.com/

Description:

A web based bug / issue tracking application programmed in C# and asp.net. The main goals are to keep the codebase simple, well documented, easy to deploy and scalable. Major features include: Generic DAL / XHTML and CSS layout.

Requirement:

All 32-bit MS Windows (95/98/NT/2000/XP)

Download data:

Downloadable files: 4859 total downloads to date

BugRat

http://www.gjt.org/pkg/bugrat/

Description:

BugRat is free Java software that provides a sophisticated, flexible bug reporting and tracking system.

Requirement:

TBC

Download data:

No data feed available

Bugs Online

http://bugsonline.sourceforge.net/

Description:

Bugs Online was originally developed in 1997 to serve as the primary bug and issue tracking system to be utilized during a large development oriented project. The Bugs Online system is a very flexible and capable system for bug and issue tracking.

Requirement:

Windows NT 4.0 SP3+, MS IIS 3 w/ ASP

Download data:

Downloadable files: 20254 total downloads to date

Bugtrack

http://sourceforge.net/projects/btrack

Description:

Web based bug tracking system written in Perl/DBI. Supports multiple users, projects, components, versions and email notification.

Requirement:

Linux, Solaris, Windows

Download data:

Downloadable files: 3361 total downloads to date

BugTracker.NET

http://btnet.sourceforge.net/bugtrackernet.html

Description:

BugTracker.NET is a free, web-based bug or issue tracker written using ASP.NET, C#, and Microsoft SQL Server/MSDE. It is in daily use by hundreds (maybe thousands) of development and support teams around the world.

Requirement:

All 32-bit MS Windows (95/98/NT/2000/XP)

Download data:

Downloadable files: 71096 total downloads to date

Bugzilla

http://www.mozilla.org/projects/bugzilla/

Description:

Bugzilla has matured immensely, and now boasts many advanced features. These include: integrated, product-based granular security schema, inter-bug dependencies and dependency graphing, advanced reporting capabilities, a robust, stable RDBMS back-end, extensive configurability, a very well-understood and well-thought-out natural bug resolution protocol, email, XML, console, and HTTP APIs, available integration with automated software configuration management systems, including Perforce and CVS (through the Bugzilla email interface and checkin/checkout scripts), too many more features to list

Requirement:

TBC

Download data:

No data feed available

CodeTrack

http://kennwhite.sourceforge.net/codetrack/

Description:

Bug database with a friendly web front end aimed at medium and small development shops. Particularly suited for intranet and extranet environments, CodeTrack includes built-in strong authentication, and allows custom access control to individual projects. No database is required as bug data and developer notes are stored using simple XML text files.

Requirement:

Apache and PHP

Download data:

Downloadable files: 5723 total downloads to date

Debian bug tracking software

http://www.chiark.greenend.org.uk/~ian/debbugs/

Description:

The Debian bug tracking system is a set of scripts which maintain a database of problem reports.

Requirement:

Unix

Download data:

No data feed available

Eventum

http://eventum.mysql.org/wiki/index.php/Main_Page

Description:

Eventum is a user-friendly and flexible issue tracking system that can be used by a support department to track incoming technical support requests, or by a software development team to quickly organize tasks and bugs.

Requirement:

PHP, MySQL

Download data:

No data feed available

Flyspray

http://flyspray.rocks.cc/

Description:

Originally developed for the Psi project, Flyspray is an easy to use bug tracking system for those who do not require all the complexities of something like Bugzilla. It supports multiple users, file attachments, and Jabber notifications.

Requirement:

Web Environment

Download data:

No data feed available

GNATS

http://www.gnu.org/software/gnats/

Description:

GNATS is a portable incident/bug report/help request-tracking system which runs on UNIX-like operating systems. It easily handles thousands of problem reports, has been in wide use since the early 90s, and can do most of its operations over e-mail. Several front end interfaces exist, including command line, emacs, and Tcl/Tk interfaces. There are also a number of Web (CGI) interfaces written in scripting languages like Perl and Python.

Requirement:

OS Independent

Download data:

No data feed available

Helis

http://linux.softpedia.com/get/Programming/Bug-Tracking/Helis-962.shtml

Description:

Helis includes the main features of most bug tracking systems.

Requirement:

Linux web server (php 4/mysql + cgi)

Download data:

No data feed available

Issue Tracker Product

http://www.issuetrackerproduct.com/

Description:

A straight forward and user friendly web application built on top of the Zope application server.

Requirement:

OS Independent, Zope

Download data:

Downloadable files: 797 total downloads to date

JIRA

http://www.atlassian.com/software/jira/

Description:

JIRA is an issue tracking and project management application developed to make this process easier for your team. JIRA has been designed with a focus on task achievement, is instantly usable and is flexible to work with. Free to academic and open source projects, commercial licenses come with the complete source code.

Requirement:

JDK

Download data:

No data feed available

JitterBug

http://samba.anu.edu.au/cgi-bin/jitterbug

Description:

JitterBug is a web based bug tracking system. JitterBug operates by receiving bug reports via email or a web form. Authenticated users can then reply to the message, move it between different categories or add notes to it. In some ways JitterBug is like a communal web based email system. This web page is itself a JitterBug page.

Requirement:

TBC

Download data:

Downloadable files: 0 total downloads to date

JTrac

http://jtrac.info

Description:

Trac is a generic issue-tracking web-application that can be easily customized by adding custom fields and drop-downs. Features include customizable workflow, field level permissions, e-mail integration, file attachments and a detailed history view.

Requirement:

OS Independent

Download data:

Downloadable files: 2323 total downloads to date

Mantis

http://mantisbt.sourceforge.net/

Description:

Mantis is a php/MySQL/web based bugtracking system.

Requirement:

Windows, MacOS, OS/2, and a variety of Unix operating systems. Any web browser should be able to function as a clientWindows, MacOS, OS/2, and a

Download data:

Downloadable files: 276848 total downloads to date

Open Track

http://www.tumblin.com/aws/opentrack.html

Description:

OpenTrack is a problem tracking(PR) system that is table driven and easily configurable/customizable for a variety of PR applications. Project defect tracking, help desk tracking, and requirements gathering can be easily handled by OpenTrack.

Requirement:

TBC

Download data:

No data feed available

PEST

http://sourceforge.net/projects/pest/

Description:

PEST is a bug tracking system written especially for a web enviroment. It supports good testing and bug tracking processes, as well as notification.

Requirement:

TBC

Download data:

Downloadable files: 1881 total downloads to date

phpBugTracker

http://phpbt.sourceforge.net/

Description:

phpBugTracker is an attempt to copy the functionality of Bugzilla while providing a codebase that is independent of the database and presentation layers.

Requirement:

webserver with PHP 4.1.0+

Download data:

Downloadable files: 54426 total downloads to date

Request Tracker

http://www.bestpractical.com/rt/index.html

Description:

RT is an industrial-grade ticketing system. It lets a group of people intelligently and efficiently manage requests submitted by a community of users. RT is used by systems administrators, customer support staffs, NOCs, developers and even marketing departments at over a thousand sites around the world.

Requirement:

Written in object-oriented Perl, RT is a high-level, portable, platform independent system

Download data:

No data feed available

Roundup Issue Tracker

http://roundup.sourceforge.net/

Description:

Roundup is a simple-to-use and -install issue-tracking system with command-line, web and e-mail interfaces. It is based on the winning design from Ka-Ping Yee in the Software Carpentry "Track" design competition.

Requirement:

TBC

Download data:

Downloadable files: 33852 total downloads to date

Scarab

http://scarab.tigris.org/

Description:

The goal of the Scarab project is to build an Issue / Defect tracking system that has the following features: A full feature set similar to those found in other Issue / Defect tracking systems: data entry, queries, reports, notifications to interested parties, collaborative accumulation of comments, dependency tracking In addition to the standard features, Scarab has fully customizable and unlimited numbers of Modules (your various projects), Issue types (Defect, Enhancement, etc), Attributes (Operating System, Status, Priority, etc), Attribute options (P1, P2, P3) which can all be defined on a per Module basis so that each of your modules is configured for your specific tracking requirements. Built using Java Servlet technology for speed, scalability, maintainability, and ease of installation. Import/Export ability via XML allowing for easy migration from other systems (like Bugzilla). Modular code design that allows manageable modifications of existing and new features over time. Fully customizable through a set of administrative pages. Easily modified UI look and feel. Can be integrated into larger systems by re-implementing key interfaces.

Requirement:

TBC

Download data:

No data feed available

Stabilizer

http://stabilizer.sf.net

Description:

The Stabilizer bug tracking system aims to quickly stabilize buggy GUI applications so that people can get real work done with them. Users collaboratively and quickly stabilize a buggy GUI application simply by using the application normally and reporting any bugs that they encounter. As soon as a few people report the same bug, warnings will be issued to all users whenever they are about to trigger that bug and they will be given the opportunity to abort the input event -- thus avoiding the bug altogether and keeping the application stable.

Requirement:

All POSIX (Linux/BSD/UNIX-like OSes), Linux

Download data:

No data feed available

Trac

http://projects.edgewall.com/trac/

Description:

Trac is an enhanced wiki and issue tracking system for software development projects. Trac allows wiki markup in issue descriptions and commit messages, creating links and seamless references between bugs, tasks, changesets, files and wiki pages. A timeline shows all project events in order, making getting an overview of the project and tracking progress very easy.

Requirement:

Python, CGI-capable web server

Download data:

No data feed available

Track+

http://www.trackplus.com

Description:

Track+ is a web based issue tracking and project management application targeted at medium to large commercial development projects. Track+ can be used instantly, yet it is flexible and configurable. Track+ is easy to use, provides user centric as well as project centric views, has configurable workflows, supports e-mail submission of issues, and has a comprehensive time and cost tracking module. Track+ is free to academic institutions, open source projects, and charities, and generally free to anybody up to 10 active users in the database. Track+ comes with the complete source code.

Requirement:

OS Independent (Written in an interpreted language)

Download data:

Downloadable files: 79969 total downloads to date

TrackIt

http://trackit.sourceforge.net/

Description:

TrackIt is a Web-based project tracking tool that incorporates defect tracking functionality. It is designed from the ground up to provide maximum flexibility, customization, and most importantly, usefulness to the developer. It has built-in support for various Extreme Programming constructs, as well as full CVS and Subversion integration. It also supports simple listings via HQL and advanced reporting via SQL.

Requirement:

JRE 1.5

Download data:

Downloadable files: 9588 total downloads to date

WREQ

http://www.math.duke.edu/~yu/wreq/

Description:

Wreq is designed to be a distributed request/problem tracking system with builtin knowledge database to help systems personnel to stay on top of requests and to prompt knowledge sharing among all local support groups.

Requirement:

To use wreq, first you must have perl version 5 with GDBM support installed on your web server.

Download data:

No data feed available

For those projects hosted on SourceForge, the project activity data is updated weekly using live newsfeeds powered by CaRP

Apache JMeter

http://jakarta.apache.org/jmeter/

Description:

Apache JMeter is a 100% pure Java desktop application designed to load test functional behavior and measure performance. It was originally designed for testing Web Applications but has since expanded to other test functions. Apache JMeter may be used to test performance both on static and dynamic resources (files, Servlets, Perl scripts, Java Objects, Data Bases and Queries, FTP Servers and more). It can be used to simulate a heavy load on a server, network or object to test its strength or to analyze overall performance under different load types. You can use it to make a graphical analysis of performance or to test your server/script/object behavior under heavy concurrent load.

Requirement:

Solaris, Linux, Windows (98, NT, 2000). JDK1.4 (or higher).

Download data:

No data feed available

Database Opensource Test Suite

http://ltp.sourceforge.net/

Description:

The Database Opensource Test Suite (DOTS) is a set of test cases designed for the purpose of stress-testing database server systems in order to measure database server performance and reliability.

Requirement:

Linux, POSIX

Download data:

Downloadable files: 55872 total downloads to date

DBMonster

http://sourceforge.net/projects/dbmonster/

Description:

DBMonster is an application to generate random data for testing SQL database driven applications under heavy load.

Requirement:

OS Independent

Download data:

Downloadable files: 7958 total downloads to date

Deluge

http://deluge.sourceforge.net/

Description:

An open-source web site stress test tool. Simulates multiple user types and counts. Includes proxy server for recording playback scripts, and log evaluator for generating result statistics. Note: this tool is no longer under active development although it is still available on Sourceforge.

Requirement:

OS independent

Download data:

Downloadable files: 7097 total downloads to date

Dieseltest

http://sourceforge.net/projects/dieseltest/

Description:

Contains the high-end features common to packages costing $50,000 or more. Dieseltest is a Windows application that simulates hundreds or thousands of users hitting a website. To run a load test, you first create a test script using our script editor. The script contains all of the requests that a real-world user would make of a website. You then load the script and run the test. The system will show you real-time results while the script is running, and produce a report analyzing the results at the conclusion.

Requirement:

Windows

Download data:

Downloadable files: 6015 total downloads to date

FunkLoad

http://funkload.nuxeo.org/

Description:

FunkLoad is a functional and load web tester, written in Python, whose main use cases are functional and regression testing of web projects, performance testing by loading the web application and monitoring your servers, load testing to expose bugs that do not surface in cursory testing, and stress testing to overwhelm the web application resources and test the application recoverability, and writing web agents by scripting any web repetitive task, like checking if a site is alive.

Requirement:

OS independent - except for the monitoring which is Linux specific.

Download data:

No data feed available

Grinder

http://grinder.sourceforge.net/

Description:

The Grinder is a Java load-testing framework making it easy to orchestrate the activities of a test script in many processes across many machines, using a graphical console application.

Requirement:

OS Independent

Download data:

Downloadable files: 102533 total downloads to date

Hammerhead 2 - Web Testing Tool

http://hammerhead.sourceforge.net/

Description:

Hammerhead 2 is a stress testing tool designed to test out your web server and web site. It can initiate multiple connections from IP aliases and simulated numerous (256+) users at any given time. The rate at which Hammerhead 2 attempts to pound your site is fully configurable, there are numerous other options for trying to create problems with a web site (so you can fix them).

Requirement:

Hammerhead has been used with Linux, Solaris and FreeBSD.

Download data:

Downloadable files: 19860 total downloads to date

httperf

http://www.hpl.hp.com/research/linux/httperf/

Description:

Httperf is a tool for measuring web server performance. It provides a flexible facility for generating various HTTP workloads and for measuring server performance. The focus is not on implementing one particular benchmark but on providing a robust, high-performance tool that facilitates the construction of both micro and macro level benchmarks. The three distinguishing characteristics of httperf are its robustness, which includes the ability to generate and sustain server overload, support for the HTTP/1.1 and SSL protocols, and its extensibility.

Requirement:

linux (Debian package available), HP-UX, perhaps other Unix

Download data:

No data feed available

http_load

http://www.acme.com/software/http_load/

Description:

http_load runs multiple HTTP fetches in parallel, to test the throughput of a Web server. However, unlike most such test clients, it runs in a single process, to avoid bogging the client machine down. It can also be configured to do HTTPS fetches.

Requirement:

tbc

Download data:

No data feed available

JCrawler

http://jcrawler.sourceforge.net/

Description:

Stress-Testing Tool for web-applications. It comes with the crawling/exploratory feature. You can give JCrawler a set of starting URLs and it will begin crawling from that point onwards, going through any URLs it can find on its way and generating load on the web application. The load parameters (hits/sec) are configurable.

Requirement:

OS Independent

Download data:

Downloadable files: 4291 total downloads to date

NTime

http://www.codeproject.com/dotnet/ntime.asp

Description:

The NTime tool is very similar to NUnit tool to perform repeatable tasks that help managers, architects, developers and testers to test an application against its performance.

Requirement:

Windows 98 or above, .Net framework 1.1 or 2.0

Download data:

No data feed available

OpenSTA

http://OpenSTA.org/

Description:

A distributed software testing architecture based on CORBA. Using OpenSTA (Open System Testing Architecture) a user can generate realistic heavy loads simulating the activity of hundreds to thousands of virtual users. OpenSTA graphs both virtual user response times and resource utilization information from all Web Servers, Application Servers, Database Servers and Operating Platforms under test, so that precise performance measurements can be gathered during load tests and analysis on these measurements can be performed.

Requirement:

Windows 2000, NT4 and XP

Download data:

Downloadable files: 164360 total downloads to date

OpenWebLoad

http://openwebload.sourceforge.net/

Description:

OpenLoad is a tool for load testing web applications. It aims to be easy to use and providing near real-time performance measurements of the application under test.

Requirement:

Linux, DOS

Download data:

Downloadable files: 25841 total downloads to date

Seagull

http://gull.sourceforge.net/

Description:

Seagull is a multi-protocol traffic generator test tool. Primary aimed at IMS protocols, Seagull is a powerful traffic generator for functional, load, endurance, stress and performance tests for almost any kind of protocol. Currently supports Diameter, XCAP over HTTP, TCAP (GSM Camel, MAP, Win) protocols.

Requirement:

Linux/Unix/Win32-Cygwin

Download data:

Downloadable files: 712 total downloads to date

Siege

http://www.joedog.org/

Description:

SIEGE is an http regression testing and benchmarking utility. It was designed to let web developers measure the performance of their code under duress, to see how it will stand up to load on the internet. It lets the user hit a webserver with a configurable number of concurrent simulated users. Those users place the webserver "under siege." SCOUT surveys a webserver and prepares the urls.txt file for a siege. In order to perform regression testing, siege loads URLs from a file and runs through them sequentially or randomly. Scout makes the process of populating that file easier. You should send out the scout, before you lay siege.

Requirement:

GNU/Linux, AIX, BSD, HP-UX and Solaris.

Download data:

Downloadable files: 554 total downloads to date

Sipp

http://sipp.sourceforge.net/

Description:

SIPp is a performance testing tool for the SIP protocol. Its main features are basic SIPStone scenarios, TCP/UDP transport, customizable (xml based) scenarios, dynamic adjustement of call-rate and a comprehensive set of real-time statistics. It can also generate media (RTP) traffic for audio and video calls.

Requirement:

Linux/Unix/Win32-Cygwin

Download data:

Downloadable files: 41919 total downloads to date

SLAMD

http://www.slamd.com/

Description:

SLAMD Distributed Load Generation Engine is a Java-based application designed for stress testing and performance analysis of network-based applications.

Requirement:

Any system with Java 1.4 or higher

Download data:

No data feed available

Soap-Stone

http://soap-stone.sourceforge.net/

Description:

Network benchmark application which can put your network under load and conduct automatic benchmark and recording activities.

Requirement:

OS Independent

Download data:

Downloadable files: 1482 total downloads to date

stress_driver

http://sourceforge.net/projects/stress-driver/

Description:

General-purpose stress test tool.

Requirement:

Windows NT/2000, Linux

Download data:

Downloadable files: 3034 total downloads to date

TestMaker

http://www.pushtotest.com/ptt/

Description:

TestMaker from PushToTest.com delivers a rich environment for building and running intelligent test agents that test Web-enabled applications for scalability, functionality, and performance. It comes with a friendly graphical user environment, an object-oriented scripting language (Jython) to build intelligent test agents, an extensible library of protocol handlers (HTTP, HTTPS, SOAP, XML-RPC, SMTP, POP3, IMAP), a new agent wizard featuring an Agent Recorder to write scripts for you, a library of fully-functional sample test agents, and shell scripts to run test agents from the command line and from unit test utilities.

Requirement:

Java 1.4 or higher virtual machine on Windows, Linux, Solaris, and Macintosh.

Download data:

No data feed available

TPTEST

http://tptest.sourceforge.net/about.php

Description:

The purpose with TPTEST is to allow users to measure the speed of their Internet connection in a simple way. TPTEST measures the throughput speed to and from various reference servers on the Internet. The use of TPTEST may help increase the consumer/end user knowledge of how Internet services work.

Requirement:

MacOS/Carbon and Win32

Download data:

Downloadable files: 66442 total downloads to date

Tsung

http://tsung.erlang-projects.org/

Description:

Tsung is a distributed load testing tool. It is protocol-independent and can currently be used to stress HTTP, SOAP and Jabber servers (SSL is supported). It simulates complex user's behaviour using an XML description file, reports many measurements in real time (including response times, CPU and memory usage from servers, customized transactions, etc.). HTML reports (with graphics) can be generated during the load. For HTTP, it supports 1.0 and 1.1, has a proxy mode to record sessions, supports GET and POST methods, Cookies, and Basic WWW-authentication. It has already been used to simulate thousands of virtual users.

Requirement:

Tested on Linux, but should work on MacOSX and Windows.

Download data:

No data feed available

Web Application Load Simulator

http://jobmanager.sourceforge.net/openware_pub/

Description:

LoadSim is a web application load simulator. It allows you to create simulations and have those simulations run against your webserver.

Requirement:

JDK 1.3 or above

Download data:

Downloadable files: 7971 total downloads to date

Web Polygraph

http://www.web-polygraph.org/

Description:

Benchmarking tool for caching proxies, origin server accelerators, L4/7 switches, content filters, and other Web intermediaries.

Requirement:

C++ compiler

Download data:

No data feed available

For those projects hosted on SourceForge, the project activity data is updated weekly using live newsfeeds powered by CaRP

Boost

http://www.boost.org/libs/test/doc/index.html

Description:

The Boost Test Library provides a matched set of components for writing test programs, organizing tests in to simple test cases and test suites, and controlling their runtime execution.

Requirement:

Download data:

No data feed available

C Unit Test System

http://sourceforge.net/projects/cut/

Description:

CUT is a simple, to-the-point unit testing system. It's different from other unit test packages in that it follows the KISS principle. It's designed for C testing, not designed to emulate SUnit.

Requirement:

OS Independent

Download data:

Downloadable files: 4744 total downloads to date

Check

http://check.sourceforge.net/

Description:

Check is a unit test framework for C. It features a simple interface for defining unit tests, putting little in the way of the developer. Tests are run in a separate address space, so Check can catch both assertion failures and code errors that cause segmentation faults or other signals. The output from unit tests can be used within source code editors and IDEs.

Requirement:

POSIX

Download data:

Downloadable files: 17934 total downloads to date

CppTest

http://cpptest.sourceforge.net/

Description:

CppTest is a portable and powerful, yet simple, unit testing framework for handling automated tests in C++. The focus lies on usability and extendability. Several output formats are supported and new ones are easily added.

Requirement:

OS Independent

Download data:

Downloadable files: 4445 total downloads to date

CppUnit

http://cppunit.sourceforge.net/

Description:

CppUnit is the C++ port of the famous JUnit framework for unit testing. Test output is in XML or text format for automatic testing and GUI based for supervised tests.

Requirement:

BeOS, MacOS, Windows, OS Independent, Linux

Download data:

Downloadable files: 293875 total downloads to date

cutee

http://codesink.org/cutee_unit_testing.html

Description:

C++ unit testing environment that makes it really easy to create and run tests of a library or application. It will automatically generate Makefiles, runner classes (classes that execute test functions), and main test application code. It will also automatically update Makefiles and support classes whenever you add new test functions or modify old ones.

Requirement:

UNIX

Download data:

Downloadable files: 9 total downloads to date

CUTest

http://cutest.sourceforge.net/

Description:

CuTest is a unit testing library for the C language.

Requirement:

Download data:

Downloadable files: 9356 total downloads to date

CxxTest

http://cxxtest.sourceforge.net/

Description:

CxxTest is a JUnit/CppUnit/xUnit-like framework for C++. Its advantages over existing alternatives are that it doesn't require RTTI, doesn't require member template functions, doesn't require exception handling, doesn't require any external libraries (including memory management, file/console I/O, graphics libraries) and is distributed entirely as a set of header files. This makes it extremely portable and usable.

Requirement:

OS Independent (Written in an interpreted language)

Download data:

Downloadable files: 26641 total downloads to date

Embedded Unit

https://sourceforge.net/projects/embunit/

Description:

Unit testing framework for Embedded C System. Its design was copied from JUnit and CUnit and more, and then adapted somewhat for Embedded C System.

Requirement:

OS Independent

Download data:

Downloadable files: 3933 total downloads to date

GUNit

http://kooditakomo.cs.tut.fi/projects/gunit/

Description:

GUNit is a C unit testing framework in the spirit of JUnit. The framework incorporates an easy to use GUI based on the Gnome libraries.

Requirement:

Linux

Download data:

No data feed available

ObjcUnit

http://oops.se/objcunit/

Description:

ObjcUnit is a unit testing framework for Objective-C on Mac OS X. Its design was copied from JUnit, written by Erich Gamma and Kent Beck, and then adapted somewhat for Objective-C. It also has support for mock objects, adapted from the Java Mock Objects framework.

Requirement:

Mac OS X

Download data:

No data feed available

OCUnit

http://www.sente.ch/software/ocunit/

Description:

OCUnit is a testing framework for Objective C in the Mac OS X, GNUSTEP and other environments. It is based on the original SUnit framework of Kent Beck, but also include a JUnit like API. Test suites are automatically created at runtime. On Mac OS X it provides full integration with the XCode IDE: tests can be run after each compilation and failures and errors are reported in the build panel.

Requirement:

Mac OS X, GNUstep, OPENSTEP or WebObjects 4

Download data:

No data feed available

QtUnit

http://www.uwyn.com/projects/qtunit/

Description:

QtUnit is a unit testing framework for C++ which compiles into a shared library. It uses the Qt library for platform independence. Tests can be compiled into modules which are automatically reloaded after modification. The text and graphical testrunners are fully localized and integrate perfectly into IDEs for the display of the exact source location where failures occurred.

Requirement:

Qt 3.0

Download data:

No data feed available

simplectest

http://simplectest.sourceforge.net/index.php

Description:

Aims to be a simple but effective testing framework for C and C++ projects, without having too much overhead.

Requirement:

Cygwin (MS Windows), OS Portable

Download data:

Downloadable files: 685 total downloads to date

Splint

http://www.splint.org/

Description:

Splint is a tool for statically checking C programs for coding errors and security vulnerabilities. If effort is invested adding annotations to programs, Splint can perform stronger checking than is possible with traditional lints.

Requirement:

Win32, Solaris, Linux, FreeBSD

Download data:

Downloadable files: 0 total downloads to date

TestKit

http://testkit.sourceforge.net

Description:

Testing framework for Mac OS X and the Objective-C language. Includes testing framework, developer tool integration, easy test organization and packaging, GUI Test Runner, and a command-line version for test automation. Modelled after JUnit, but targets the specific needs of the OS X developer in the Cocoa environment.

Requirement:

MacOS X

Download data:

Downloadable files: 1340 total downloads to date

TUT

http://tut-framework.sourceforge.net/

Description:

TUT simplifies tests organization and provides basic framework to run them. All developers have to do is to fill tests bodies with the actual test code.

Requirement:

C++

Download data:

No data feed available

UnitTest++

http://unittest-cpp.sourceforge.net/

Description:

UnitTest++ is a unit testing framework for C++ designed for simplicity and portability. Features include no explicit test registration, good crash handling, fixtures, rich condition-checking functionality, minimal footprint for embedded environments.

Requirement:

Win32, Linux, Mac OS X

Download data:

Downloadable files: 1490 total downloads to date

For those projects hosted on SourceForge, the project activity data is updated weekly using live newsfeeds powered by CaRP