[software development] 需求分析checklist


// */
// ]]>

 

[software development] 需求分析checklist

1 Specific Functional Requirements, 功能上的需求

  1. Are all the inputs to the system specified, including their source, accuracy, range of values, and frequency?

    是不是所有系统的输入都已经详细说明了, 包括输入源, 精度, 输入的范围, 以及不同输入的频率?

  2. Are all the outputs from the system specified, including their destination, accuracy, range of values, frequency, and format?

    是不是所有系统的输出都已经详细说明了, 包括输出的地点, 精度, 数值的范围, 频率以及格式?

  3. Are all output formats specified for web pages, reports, and so on?

    是不是所有的输出格式(用于网页, 报告等)都被详细说明了?

  4. Are all the external hardware and software interfaces specified?

    是不是所有的外部的软件接口以及硬件接口都被详细说明了?

  5. Are all the external communication interfaces specified, including handshaking, error-checking, and communication protocols?

    是不是所有的外部通信接口都被详细说明了, 包括握手协议, 错误检测, 以及通信协议

  6. Are all the tasks the user wants to perform specified?

    是不是所有的用户相要的任务都被详细说明了?

  7. Is the data used in the each task and the data resulting from each task specified?

    每一个任务的输入数据和输出结果是不是都被详细说明了?

2 Specific Non-Functional (Quality) Requirements, 非功能需求

  1. Is the expected response time, from the user's point of view, specified for all necessary operations?

    从用户的角度看, 所有的必要操作的响应时间是否被详细说明了?

  2. Are other timing considerations specified, such as processing time, data-transfer rate, and system throughput?

    其他的运行时间有没有被详细说明, 如处理时间, 数据传输率, 系统的吞吐量

  3. Is the level of security specified?

    安全的级别有没有被详细说明?

  4. 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?

    可靠性有没有被详细说明, 包括软件错误的后果, 错误发生时关键信息的保护, 错误检测以及自我修复的策略?

  5. Is maximum memory specified?

    最大的内存需求有没有被详细说明?

  6. Is the maximum storage specified?

    最大的存储需求有没有被详细说明?

  7. 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?

    系统的可维护性有没有被详细说明, 包括个别功能的改变, 操作环境的改变, 与其他软件之间的接口的改变等?

  8. Is the definition of success included? Of failure?

    有没有说到什么程度算是成功, 怎样又叫做失败?

3 Requirements Quality, 需求的质量

  1. Are the requirements written in the user's language? Do the users think so?

    需求是不是以用户能够理解的方式写的? 用户是这么认为的吗?

  2. Does each requirement avoid conflicts with other requriements?

    每一个需求和其他的需求有没有冲突?

  3. Are acceptable trade-offs between competing attributes specified – for example, between robustness and correctness?

    互相矛盾的特性之间有没有达到一个可以接受的平衡关系, 如稳健性和准确性之间?

  4. Do the requirements avoid specifying the design?

    需求分析有没有避免详细的设计?

  5. 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?

    是否有些需求过于细化, 或是不够细化?

  6. Are the requirements clear enough to be turned over to an independent group for construction and still be understood?

    需求是否足够清晰, 清晰到能够让一个独立的小组充分理解需求, 并进行下一步的构件?

  7. Is each Item relevant to the problem and its solution? Can each item be traced to its origin in the problem environment?

    每一项都与问题和结果相关吗? 能够将每一项追溯到原始问题?

  8. Is each requirement testable? Will it be possible for independent testing to determine whether each requirement bas been satisfied?

    每个需求都能够被测试吗? 能否通过独立的测试确定各个需求的满足情况?

  9. Are all possible changes to the requriements specified, including the likelihood of each change?

    所有可能引起需求改变的因素都详细说明了吗, 包括不同改变的可能性?

4 Requirements Completeness, 需求完成

  1. Where information isn't available before development begins, are the areas of incompleteness specified?

    开发之前没有完成的需求是不是被详细说明了?

  2. Are the requirements complete in the sense that if the product satisfied every requirement, it will be acceptable?

    当需求结束后, 确认产品是否能够满足所有的需求?

  3. 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

Validate XHTML 1.0

[software development] 需求分析checklist的更多相关文章

  1. 关于敏捷开发方法(Agile Software Development)的阅读笔记

    对“敏捷开发”(Agile Software Development)这个词,我是在这学期邹欣老师<现代程序设计>课上第一次听到的,刚听到时并不知道其具体指什么,只是从字面上直觉其意思应该 ...

  2. 敏捷软件开发 Agile software Development(转)

    原文链接: http://www.cnblogs.com/kkun/archive/2011/07/06/2099253.html 敏捷软件开发 Agile software Development ...

  3. 敏捷软件工程(agile software development) VS传统软件工程(traditional software development)

    敏捷软件工程(agile software development) VS传统软件工程(traditional software development)      Agile principle  ...

  4. Agile software Development

    转自:https://www.cnblogs.com/kkun/archive/2011/07/06/agile_software_development.html 敏捷软件开发 Agile soft ...

  5. 软件开发流程 Software development process

    软件开发流程(Software development process)即软件设计思路和方法的一般过程,包括设计软件的功能和实现的算法和方法.软件的总体结构设计和模块设计.编程和调试.程序联调和测试以 ...

  6. Software Development Engineer - Database Services

    http://stackoverflow.com/jobs/116486/software-development-engineer-database-services-amazon?med=clc& ...

  7. 微软职位内部推荐-Software Development Engineer

    微软近期Open的职位: Job Title: Software Development Engineer Work Location: Suzhou, China The Office 365 Co ...

  8. FBX Software Development Kit

    FBX Software Development Kit The FBX Software Development Kit (FBX SDK) allows software developers t ...

  9. Agile Software Development ——敏捷开发

    敏捷? 过去几年中,软件行业中出现了一个新词汇——agile:与此同时,一个关于新的软件开发方式的变革正悄然兴起. 在老师的引导下,我阅读了Agile Guide网站上的几篇文章,并查阅了相关资料.不 ...

随机推荐

  1. 第一次自己写jquery图片延迟加载插件,不通用,但修改一下还是可以使用到很多页面上的

    不断修改完善中…… /*! * jquery.lazyoading.js *自定义的页面图片延迟加载插件,比网上的jquery.lazyload简单,也更适合自己的网站 *使用方法: 把img 的cl ...

  2. 理解一下单片机的I2C和SPI通信

    应某位网友要求,今天说一下单片机的I2C SPI通信,可能说不清楚,因为这毕竟要做实验才可完全理解. I2C和SPI是两种不同的通信协议. 听到协议,似乎高不可攀,其实协议就是人们定义的一个标准而已, ...

  3. go json null字段的转换

    最近试了试go中对json null字段进行转换,代码如下: struct 转 json: package main import ( "encoding/json" " ...

  4. windows下与linux下安装redis及redis扩展

    1.        Redis的介绍 Redis是一个开源的使用ANSI C语言编写.支持网络.可基于内存亦可持久化的日志型.Key-Value数据库,并提供多种语言的API.从2010年3月15日起 ...

  5. java 多线程(wait/notify/notifyall)

    package com.example; public class App { /* wait\notify\notifyAll 都属于object的内置方法 * wait: 持有该对象的线程把该对象 ...

  6. Jquery相册插件(开源下载)

    一,导言 上次 “不定义JQuery插件,不要说会JQuery” 的博客写的肤浅,漏洞百出,而且最重要的是从理论上说如何定义一个jQuery插件,没有实质性的写一个jQuery插件出来,这未免是纸上谈 ...

  7. alwaysOn为什么不支持分布式事务

    Alwayson是微软从SQL2012开始引入的一种高可用和高性能架构,它既可以实现故障转移,同时又能实现查询分离,是当前SQL server的所有架构中最优秀的一种. 因此,一般我们都会推荐使用Al ...

  8. 据说每个大牛、小牛都应该有自己的库——Event处理

    今天抽时间写了一部分Event处理方面的函数愈发的觉得jQuery的优秀,自己前期的想法太粗糙,造成后面这些函数参数很多,操作很很不直观,看样子是要重构的节奏,还好小伙儿伴们安慰,架构都是改出来的.继 ...

  9. 为 WSUS 服务器定期运行清理向导

    在 WSUS 的管理界面的 Options 里面,可以找到 Server Cleanup Wizard 然后运行.后来想了一下,为什么不把它弄成定期运行呢! 找了一下,从 Windows Server ...

  10. Post方式的Http流请求调用

    HttpRequest公共类: public static class HttpRequestAction { /// <summary> /// 发送http请求并返回响应 /// &l ...