没有合适的资源?快使用搜索试试~ 我知道了~
资源详情
资源评论
资源推荐
1
Chapter 5
Understanding Requirements
Software Engineering: A Practitioner’s Approach, 7/e
by Roger S. Pressman
2
软件需求分析的目标是准确理解用户的要求,进行细致的调
查分析,将用户的非形式化的要求转化为完整的需求定义(
需求规格说明书)。
需求包括:
功能要求
性能要求
运行环境要求
数据要求
可靠性要求
安全保密要求
用户界面要求
可移植性需求
可复用性需求
外部接口要求
资源使用要求
软件成本消耗与开发进度要求
其它非功能性的限制和要求,如法
规需求、质量标准、验收标准、可
维护性要求等
What is Requirement ?
3
Requirements Engineering-I
Inception( 起始 )—ask a set of questions that establish …
basic understanding of the problem
the people who want a solution
the nature of the solution that is desired, and
the effectiveness of preliminary communication and
collaboration between the customer and the developer
Elicitation( 导出 )—elicit requirements from all stakeholders
Elaboration( 精化 )—create an analysis model that identifies
data, function and behavioral requirements
4
Requirements Engineering-II
Negotiation( 协商 )—agree on a deliverable system that is realistic for
developers and customers
Specification ( 规格说明 )—can be any one (or more) of the following:
A written document
A set of models
A formal mathematical
A collection of user scenarios (use-cases)
A prototype
Validation ( 确认 )—a review mechanism that looks for
errors in content or interpretation
areas where clarification may be required
missing information
inconsistencies (a major problem when large products or systems
are engineered)
conflicting or unrealistic (unachievable) requirements.
5
Inception
Identify stakeholders
“who else do you think I should talk to?”
Recognize multiple points of view
Work toward collaboration
The first questions
Who is behind the request for this work?
Who will use the solution?
What will be the economic benefit of a successful solution
Is there another source for the solution that you need?
剩余25页未读,继续阅读
wxg520cxl
- 粉丝: 23
- 资源: 3万+
下载权益
C知道特权
VIP文章
课程特权
开通VIP
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功
评论0