需求文档

{"title":"需求文档","authors":"","doi":"10.1142/9781786348838_0012","DOIUrl":null,"url":null,"abstract":"The purpose of the Requirements Documentation is to establish an agreement about what the project is to accomplish. It provides a baseline for validation and verification, and it should reduce the development effort by avoiding omissions, misunderstandings, and inconsistencies early in the design lifecycle. All items in the Requirements Documentation should be consistent with other documentation (e.g., project description, design diagrams, task lists, timelines) but it should be readable as a stand-alone document.","PeriodicalId":332689,"journal":{"name":"Requirements Modeling and Coding","volume":"8 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2020-10-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Requirements Documentation\",\"authors\":\"\",\"doi\":\"10.1142/9781786348838_0012\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The purpose of the Requirements Documentation is to establish an agreement about what the project is to accomplish. It provides a baseline for validation and verification, and it should reduce the development effort by avoiding omissions, misunderstandings, and inconsistencies early in the design lifecycle. All items in the Requirements Documentation should be consistent with other documentation (e.g., project description, design diagrams, task lists, timelines) but it should be readable as a stand-alone document.\",\"PeriodicalId\":332689,\"journal\":{\"name\":\"Requirements Modeling and Coding\",\"volume\":\"8 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2020-10-27\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"Requirements Modeling and Coding\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1142/9781786348838_0012\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"Requirements Modeling and Coding","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1142/9781786348838_0012","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0

摘要

需求文档的目的是建立一个关于项目要完成什么的协议。它为确认和验证提供了一个基线,并且它应该通过避免设计生命周期早期的遗漏、误解和不一致来减少开发工作。需求文档中的所有条目应该与其他文档(例如,项目描述、设计图、任务列表、时间表)一致,但它应该作为一个独立的文档可读。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
Requirements Documentation
The purpose of the Requirements Documentation is to establish an agreement about what the project is to accomplish. It provides a baseline for validation and verification, and it should reduce the development effort by avoiding omissions, misunderstandings, and inconsistencies early in the design lifecycle. All items in the Requirements Documentation should be consistent with other documentation (e.g., project description, design diagrams, task lists, timelines) but it should be readable as a stand-alone document.
求助全文
通过发布文献求助,成功后即可免费获取论文全文。 去求助
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术官方微信