Requirements Traceability Matrix - SJRWMD - Open Source Portal需求跟踪矩阵sjrwmd -开源门户.docVIP

下载本文档

21
0
约3.32万字
约 19页
2018-03-26 发布于江西
举报
版权申诉

Requirements Traceability Matrix - SJRWMD - Open Source Portal需求跟踪矩阵sjrwmd -开源门户.doc

1、有哪些信誉好的足球投注网站（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。。
2、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
4、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
5、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
6、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
7、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

Requirements Traceability Matrix - SJRWMD - Open Source Portal需求跟踪矩阵sjrwmd -开源门户.doc

COMPREHENSIVE WATERSHED MANAGEMENT WATER USE TRACKING PROJECT Requirements Traceability Matrix Southwest Florida Water Management District 2379 Broad Street Brooksville, FL 34604-6899 Date Revision Description Author Table of Contents 1 Introduction 1 1.1 Requirements Management 1 1.2 Purpose 2 1.3 Water Use Tracking RTM Overview 3 2 Functional Requirements by Category 4 2.1 SWUCA 4 2.2 Water Use Permits 8 2.3 Water Use 10 2.4 Water Management Database 11 2.5 Compliance 12 2.6 Minimum Flows and Levels 13 2.7 Water Estimates 14 2.8 External Data 14 2.9 Crop Reports 14 2.10 Data Integration 14 3 Requirements Identified for a Possible Subsequent Release of the WUT System 15 4 Requirements Deleted by Original Requester 17 Requirements Traceability Matrix Introduction Requirements Management One of the six software development best practices identified by the Rational Unified Process and the first of six key process areas identified by the Software Engineering Institute’s Capability Maturity Model (CMM) Level 2: Repeatable is requirements management. According to CMM, the purpose of requirements management is to establish and maintain a common understanding between the customer and the project development team regarding the customer’s requirements that must be addressed by the software project in order for the project to be successful. Typically, requirements are organized into one of the following two categories: Business and functional requirements Non-functional requirements Business and functional requirements are user-specified functions, tasks, or behaviors that the proposed system must support. Within the software engineering process utilized by the Water Use Tracking (WUT) Project Development Team, use cases are used to capture business and functional requirements in order to ensure that these requirements drive the software engineering effort through design, implementation, and validation. For this reason, this software engineering