需求跟踪矩阵

需求跟踪矩阵与需求双向跟踪（1）

2006年08月22日 星期二 00:35

刚刚接触CMMI的人在研究Requirement Management这个PA的时候，对SP 1.4 Maintain Bidirectional Traceability of Requirements可能会比较疑惑，足以让国内大多数的没有真正软件工程开发管理的软件工程师，开发管理者不知所云了。   所谓的“Traceability of Requirements”即“需求跟踪矩阵（Requirements Traceability Matrix）”，用比较通俗的话来说，就是不要将需求遗漏了，虽然听来简单，但是真正能够实施此活动的并不多，通常来做的多为“纵向跟踪（Vertical traceability）”，也即生命周期内的跟踪，再说的明白一点就是沿着“用户需求――软件需求――概要设计――详细设计――编码实现――单元测试――集成测试――集成测试――系统测试――验收测试”进行需求的跟踪。   SEI 针对CMMI V1.1的需求跟踪的解释（2008.12.18 翻译）。 注：“纵向跟踪”也有人称为“垂直跟踪”，“水平跟踪”也有人称为“横向跟踪”。       What is bidirectional traceability?   In the Requirements Management (REQM) process area, specific practice 1.4 states, Maintain bidirectional traceability among the requirements and the project plans and work products. Bidirectional traceability primarily applies to vertical traceability and at a minimum needs to be implemented both forward and backward (i.e., from requirements to end products and from end product back to requirements).   需求管理（REQM）这个PA中的 特定实践SP1.4中描述：“维护需求、项目计划和工作产品之间的双向可追溯性”。双向可追溯性主要通过纵向跟踪和至少实现活动的前向和后向（例如：从需求到产品和从产品到需求）跟踪来实现。     Vertical traceability identifies the origin of items (e.g., customer needs) and follows these same items as they travel through the hierarchy of the Work Breakdown Structure to the project teams and eventually to the customer. When the requirements are managed well, traceability can be established from the source requirement to its lower level requirements and from the lower level requirements back to their source. Such bidirectional traceability helps determine that all source requirements have been completely addressed and that all lower level requirements can be traced to a valid source.   “纵向跟踪”是指从其最初的来源（如：客户需求），通过不同层次的工作分解结构得以实现同样的内容，并最终交付给客户的过程。在需求被很好的管理的情况下，跟踪性可以通过从初始需求对应到低级别需求，以及从低级别的需求回溯到其根源来建立。这样的双向可追溯性有助于确定所有初始需求已完全实现，并且所有较低级别的需求可以追溯到一个有效的来源上。     Horizontal traceability is also important and is mentioned in subpractice 3, but it is not required to satisfy bidirectional traceability. Horizontal traceability identifies the relationships among related items across work groups or product components for the purpose of avoiding potential conflicts. It enables the project to anticipate potential problems (and mitigate or solve them) before integration testing. For example, horizontal traceability would follow related requirements across two work groups working on two associated components of a product. The traceability across these two work groups enables the work groups to see when and how a change in a requirement for one of the components may affect the other component. Thus, horizontal traceability enables the project to anticipate potential problems (and mitigate or solve them) before integration testing.   “水平跟踪”也是很重要的，在REQM的subpractice 3中提到 ，但它并不是需要满足双向可追溯性的必要条件。“水平跟踪”通过识别相关的工作组、产品组件的关系来避免潜在的冲突。这使项目可以在集成测试之前预计可能出现的问题（并且减轻或解决这些问题）。例如，同一个产品的两个相关部件，由两个工作组根据同一份需求分别负责。当一个组件对应的需求发生改变时，可能会影响到另一个组件。横跨两个组件的需求跟踪就能及时发现、规避或解决这些问题。因此，“水平跟踪”使项目可以在集成测试之前预计可能出现的问题（并且减轻或解决这些问题）。   纵向跟踪是最普遍的一种跟踪方式，也是CMMI进行SCAMPI最低要求。即针对此PA，或者说这个SP，做到纵向跟踪后，一般的主任评估师就认为已经满足条件了，可以打及格分数了。 CMMI V1.1版本中的要求是：RM SP 1.4 Maintain Bi-directional Traceability of Requirements. 其具体要求是：Maintain bi-directional traceability among the requirements and the project plans and work products. CMMI V1.2版本中的要求是：RM SP 1.4 Maintain Bi-directional Traceability of Requirements. 其具体要求是：Maintain bidirectional traceability among the requirements and work products. 大家从描述上就能看到区别了。 《CMMI® Version 1.2 and Beyond》中的描述如下： v1.2 SP 1.4 practice statement now reads, “Maintain bidirectional traceability among the requirements and work products.”Project plans are no longer mentioned in this SP statement. Bidirectional Traceability description is improved in the notes and Glossary. 这个也证明了SEI发现了此SP的描述或者要求和实际的有出入，难以执行；但是为什么呢？ 其实大家在google上搜索一下关键字“bidirectional traceability ”就会发现很多的资料在解释“bidirectional traceability ”，即所谓的“Vertical traceability ”和“Horizontal traceability ”时，概念并不统一，而且对于“Vertical traceability ”和“Horizontal traceability ”的概念解释甚至是相反的。 话说了这么多，其实归根到底的原因是：什么是“横向跟踪”（Horizontal traceability ）？ SEI的Tim Kasse（CMMI模型制定者之一）在其著作《Practical Insight into CMMI》中曾经对“横向跟踪”（Horizontal traceability ）进行了如下解释： Horizontal traceability refers to the traceability from the requirements to the associated plans such as the project plan, quality assurance plan, Configuration Management plan, risk management plan, and so forth. 即横向跟踪是需求到计划的跟踪。 但是此观念是否正确，我们还可以参考其他资料做一个讨论。

 

 

 需求跟踪矩阵（RTM，

 

requirements traceability matrix）从形式上看类似于WBS（什么是WBS？看看项目管理中的内容吧）

需求跟踪矩阵（RTM，requirements traceability matrix）保证了需求到实现的无遗漏和偏离。