[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网站上的几篇文章,并查阅了相关资料.不 ...
随机推荐
- Atom.io设置ctrl+delete
一般常见的text editor,在文本前面的空白处按下ctrl+delete,只是删除空白符到单词前面停下,但是Atom.io的默认设置,把空白符后遇到的第一个单词也删掉了.改配置方法是在keyma ...
- Perst常用命令
Perst我使用的版本是4, 几乎支持所有的.net环境, 而且效率很高,比较稳定. 使用方法: 1:引用相应dll 2: 创建数据结构 public class Cp_struct : Persis ...
- SSTable 介绍(一)
如果说Protocol Buffers是Google内部表示独立数据记录的单元,那么排序的字符串表--Sorted String Table(SSTable)--是存储,处理和交换数据集的最流行的输出 ...
- Powershell--批量拆分SQL语句为事务并批处理
作为DBA,时不时会遇到将数据导入到数据库的情况,假设业务或研发提供一个包含上百万行INSERT语句的脚本文件,而且这些INSERT 语句没有使用GO来进行批处理拆分,那么直接使用SQLCMD来执行会 ...
- 巧用JS内置对象Function
在做练习的时候也好,做项目的时候也好,我经常会碰到想要的到一个字符串“”里面的东西的这样的需求. 注意,“”里面的东西可以是任何东西[],number等等 于是有了个大神教我一个绝招: 于是世界圆满了 ...
- 我的ef连接mysql之旅
摘要: install-package ef6,mysql.data:增加provider invariantName="MySql.Data.MySqlClient" typ ...
- Redis教程(十三):管线详解
转载于:http://www.itxuexiwang.com/a/shujukujishu/redis/2016/0216/141.html 一.请求应答协议和RTT: Redis是一种典型的基于C/ ...
- EF架构~基于EF数据层的实现
回到目录 之前写过关于实现一个完整的EF架构的文章,文章的阅读量也是满大的,自己很欣慰,但是,那篇文章是我2011年写的,所以,技术有些不成熟,所以今天把我的2014年写的EF底层架构公开一下,这个架 ...
- Node Express 4.0 安装
前言 今天想要用nodejs 写个后台服务,很久之前看过node express 框架,可真当向下手安装的时候,发现好多命令都不记得了.写完后台服务,没事了,总结了下安装过程,记录一下,以便以后查阅方 ...
- flow.ci Beta 上线,将开发工作流自动化
说起未来,我们会想到自动.智能.机器人...,希望可以从眼前重复繁琐的事情中解放出来,让"机器人"自动智能地帮我们做更多的事情:希望开发可以更自动化.智能化.社会化,更少的资源浪费 ...