[software development] 需求分析checklist
[software development] 需求分析checklist
// */
// ]]>
[software development] 需求分析checklist
Table of Contents
1 Specific Functional Requirements, 功能上的需求
- Are all the inputs to the system specified, including their source, accuracy, range of values, and frequency?
是不是所有系统的输入都已经详细说明了, 包括输入源, 精度, 输入的范围, 以及不同输入的频率?
- Are all the outputs from the system specified, including their destination, accuracy, range of values, frequency, and format?
是不是所有系统的输出都已经详细说明了, 包括输出的地点, 精度, 数值的范围, 频率以及格式?
- Are all output formats specified for web pages, reports, and so on?
是不是所有的输出格式(用于网页, 报告等)都被详细说明了?
- Are all the external hardware and software interfaces specified?
是不是所有的外部的软件接口以及硬件接口都被详细说明了?
- Are all the external communication interfaces specified, including handshaking, error-checking, and communication protocols?
是不是所有的外部通信接口都被详细说明了, 包括握手协议, 错误检测, 以及通信协议
- Are all the tasks the user wants to perform specified?
是不是所有的用户相要的任务都被详细说明了?
- Is the data used in the each task and the data resulting from each task specified?
每一个任务的输入数据和输出结果是不是都被详细说明了?
2 Specific Non-Functional (Quality) Requirements, 非功能需求
- Is the expected response time, from the user's point of view, specified for all necessary operations?
从用户的角度看, 所有的必要操作的响应时间是否被详细说明了?
- Are other timing considerations specified, such as processing time, data-transfer rate, and system throughput?
其他的运行时间有没有被详细说明, 如处理时间, 数据传输率, 系统的吞吐量
- Is the level of security specified?
安全的级别有没有被详细说明?
- Is the reliability specified, including the consequences of software failure, the vital information that needs to be protected from failure, and the strategy for error detection and recovery?
可靠性有没有被详细说明, 包括软件错误的后果, 错误发生时关键信息的保护, 错误检测以及自我修复的策略?
- Is maximum memory specified?
最大的内存需求有没有被详细说明?
- Is the maximum storage specified?
最大的存储需求有没有被详细说明?
- Is the maintainability of the system specified, including its ability to adapt to changes in specific functionality, changes in the operating environment, and changes in its interfaces with other software?
系统的可维护性有没有被详细说明, 包括个别功能的改变, 操作环境的改变, 与其他软件之间的接口的改变等?
- Is the definition of success included? Of failure?
有没有说到什么程度算是成功, 怎样又叫做失败?
3 Requirements Quality, 需求的质量
- Are the requirements written in the user's language? Do the users think so?
需求是不是以用户能够理解的方式写的? 用户是这么认为的吗?
- Does each requirement avoid conflicts with other requriements?
每一个需求和其他的需求有没有冲突?
- Are acceptable trade-offs between competing attributes specified – for example, between robustness and correctness?
互相矛盾的特性之间有没有达到一个可以接受的平衡关系, 如稳健性和准确性之间?
- Do the requirements avoid specifying the design?
需求分析有没有避免详细的设计?
- Are the requirements at a fairly consistent level of detail? Should any requirement be specified in more detail? Should any requirement be specified in less detail?
是否有些需求过于细化, 或是不够细化?
- Are the requirements clear enough to be turned over to an independent group for construction and still be understood?
需求是否足够清晰, 清晰到能够让一个独立的小组充分理解需求, 并进行下一步的构件?
- Is each Item relevant to the problem and its solution? Can each item be traced to its origin in the problem environment?
每一项都与问题和结果相关吗? 能够将每一项追溯到原始问题?
- Is each requirement testable? Will it be possible for independent testing to determine whether each requirement bas been satisfied?
每个需求都能够被测试吗? 能否通过独立的测试确定各个需求的满足情况?
- Are all possible changes to the requriements specified, including the likelihood of each change?
所有可能引起需求改变的因素都详细说明了吗, 包括不同改变的可能性?
4 Requirements Completeness, 需求完成
- Where information isn't available before development begins, are the areas of incompleteness specified?
开发之前没有完成的需求是不是被详细说明了?
- Are the requirements complete in the sense that if the product satisfied every requirement, it will be acceptable?
当需求结束后, 确认产品是否能够满足所有的需求?
- Are you comfortable with all the requirements? Have you eliminated requirements that are impossible to implement and included just to appease your customer or your boss?
你对于所有的需求满足吗? 你是否要消除那些无法实现的或是为了迎合顾客或老板的需求呢?
5 出自
Code complete second edition
Date: 2014-04-23 Wed
Author: Zhong Xiewei
Org version 7.8.11 with Emacs version 24
[software development] 需求分析checklist的更多相关文章
- 关于敏捷开发方法(Agile Software Development)的阅读笔记
对“敏捷开发”(Agile Software Development)这个词,我是在这学期邹欣老师<现代程序设计>课上第一次听到的,刚听到时并不知道其具体指什么,只是从字面上直觉其意思应该 ...
- 敏捷软件开发 Agile software Development(转)
原文链接: http://www.cnblogs.com/kkun/archive/2011/07/06/2099253.html 敏捷软件开发 Agile software Development ...
- 敏捷软件工程(agile software development) VS传统软件工程(traditional software development)
敏捷软件工程(agile software development) VS传统软件工程(traditional software development) Agile principle ...
- Agile software Development
转自:https://www.cnblogs.com/kkun/archive/2011/07/06/agile_software_development.html 敏捷软件开发 Agile soft ...
- 软件开发流程 Software development process
软件开发流程(Software development process)即软件设计思路和方法的一般过程,包括设计软件的功能和实现的算法和方法.软件的总体结构设计和模块设计.编程和调试.程序联调和测试以 ...
- Software Development Engineer - Database Services
http://stackoverflow.com/jobs/116486/software-development-engineer-database-services-amazon?med=clc& ...
- 微软职位内部推荐-Software Development Engineer
微软近期Open的职位: Job Title: Software Development Engineer Work Location: Suzhou, China The Office 365 Co ...
- FBX Software Development Kit
FBX Software Development Kit The FBX Software Development Kit (FBX SDK) allows software developers t ...
- Agile Software Development ——敏捷开发
敏捷? 过去几年中,软件行业中出现了一个新词汇——agile:与此同时,一个关于新的软件开发方式的变革正悄然兴起. 在老师的引导下,我阅读了Agile Guide网站上的几篇文章,并查阅了相关资料.不 ...
随机推荐
- 解决web中的乱码
统一使用utf-8进行编码数据库的编码格式也是utf-8 对于页面post传过来的不会出现乱码 对于页面get 传过来值解决乱码 方法一:在业务层:userName = new String(user ...
- 解决PHP move_uploaded_file函数移动图片失败
出现的问题描述:今天在实现一个在用户注册时上传头像图片文件的PHP脚本时,出现了问题:PHP脚本在前面已经确定 浏览器端上传文件没有错误.上传的文件是合法的.上传的文件是图像文件.已经在服务器端生成了 ...
- myrocks之事务处理
前言 mysql目前支持的事务引擎有innodb,tokudb. rocksdb加入mysql阵营后,mysql支持的事务引擎增长至3个.myrocks目前支持的事务隔离级别有read-committ ...
- MicroPHP 2.2.0 发布
ver 2.2.0: 增加了: 1.$this->cache为最新的phpfastcache2.1,缓存功能更加强大,而且编写自己的缓存类非常容易. 2.自定义缓存类说明: ...
- Centos6下安装Mono和Jexus部署ASP.NET应用程序(纯干货)
一.服务器 腾讯云VPS,Centos6.6系统 二.安装 1.yum升级 yum –y update 2.安装Mono所需要的库 yum -y install gcc gcc-c++ bison p ...
- windows设置笔记
1. 使用Sudo提升权限 http://www.alexblair.org/user-alexblair-post-1046.html 新建 sudo.js 放到 C:\windows\下面,内容如 ...
- 可在广域网部署运行的QQ高仿版 -- GG叽叽V3.5,增加自拍头像功能、细节优化(源码)
距离上次发版本(GG叽叽V3.4,增加系统设置.最近联系人.群功能)又有1个月了,在这个月内,由于空闲时间不是很多,所以,GG增加的主要功能只是拍照并设定其为自己头像.修改密码.删除好友.以及一些bu ...
- 最少知识原则(Least Knowledge Principle)
最少知识原则(Least Knowledge Principle),或者称迪米特法则(Law of Demeter),是一种面向对象程序设计的指导原则,它描述了一种保持代码松耦合的策略.其可简单的归纳 ...
- Asp.Net MVC中使用ACE模板之Jqgrid
第一次看到ACE模板,有种感动,有种相见恨晚的感觉,于是迅速来研究.它本身是基于bootstrap和jqueryui,但更nice,整合之后为后台开发节省了大量时间. 发现虽然不是完美,整体效果还是不 ...
- 达洛克战记3 即将开服! What's New!
历经数个月的开发,达洛克战记3即将全新开服! 剧情: 回归到三大种族起源时期,三大种族并没有像现在三足鼎立.人类一直处于统治地位.但是突然间一群巨人的出现,让人类损失惨重,身为勇者,需要探索巨人背后的 ...