Are Your Requirements Complete?
Are Your Requirements Complete?
复制标题
您的要求完成了吗？
DOI：
10.5381/jot.2005.4.1.c3
复制
发表时间：
2005
期刊：
影响因子：
--
通讯作者：
D. Firesmith
中科院分区：
文献类型：
--
作者：
D. Firesmith
好的需求具有几个有用的属性，例如一致性、必要性和明确性。几乎总是列出的另一个基本特征是“需求应该是完整的”。但是完整性到底意味着什么，您应该如何确保您的需求是完整的呢？在本专栏中，我们将开始讨论这两个问题：（1）需求完整性的重要性，（2）需求模型的完整性，（3）各种类型的单个需求的完整性，以及（4）需求元数据的完整性。在下一期的专栏中，我们将继续讨论（5）需求存储库的完整性，（6）从这样的需求存储库派生的需求文档的完整性，（7）需求文档集的完整性，（8）需求基线的完整性，以及最后（9）当使用增量和迭代开发周期时，确定完整性的程度。
Good requirements have several useful properties, such as being consistent, necessary, and unambiguous. Another essential characteristic that is almost always listed is that ‘requirements should be complete.’ But just what does completeness mean, and how should you ensure that your requirements are complete? In this column, we will begin to address these two questions by looking at (1) the importance of requirements completeness, (2) the completeness of requirements models, (3) the completeness of various types of individual requirements, , and (4) the completeness of requirements metadata. In next issue’s column, we will continue by addressing (5) the completeness of requirements repositories, (6) the completeness of requirements documents derived from such repositories of requirements, (7) the completeness of sets of requirements documents, (8) the completeness of requirements baselines, and finally (9) determining how complete is complete enough when using an incremental and iterative development cycle.