需求跟踪矩阵与需求双向跟踪-参考资料.docVIP

需求跟踪矩阵与需求双向跟踪（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 ident