需求跟踪系列 IV - More than纵向追踪和横向追踪

最新推荐文章于 2023-12-06 15:22:04 发布

原创

最新推荐文章于 2023-12-06 15:22:04 发布 · 2.2k 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#components #hierarchy #structure #测试 #工作 #产品

本文探讨了CMMI中的纵向和横向追踪在需求管理中的应用，强调了两者在确保需求完整性和避免潜在冲突中的作用。同时提出，不应简单划分追踪关系为横向或纵向，而应关注不同信息模块间的关系类型，如满足、验证、依赖、减轻风险和遵循等，以确保项目中需求的一致性和变更管理。

谈到追踪，CMMI中分了两类帮助我们理解不同的追踪关系：纵向追踪和横向追踪。我们首先来学习一下，原文的描述如下（摘自http://www.sei.cmu.edu/cmmi/faq/term-faq.html）：

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).

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