本人服务于恩杰软件科技(杭州)有限公司(http://hangzhou.ask.com/)。本网页内容仅为个人思想,不代表公司观点
需求阶段测试介入的一些步骤
上一篇 /
下一篇 2007-02-27 16:09:37
引自QAI最新的Seminar讨论。感觉对自己最近在做的需求
测试介入很有帮助,可惜具体内容要交美刀才看得到,只能看看提纲有个大致印象了。
Step | Phase | Deliverable | Tools |
1 | Identify Business Needs | User Statement of Reqts
| Process Charts Problem Statement Requirements User List Critical Success Factors Problem Stmt User Stmt of Reqts |
2 | Analyze Bus. Reqts | Preliminary Stmt of Reqts
| Modeling/Prototyping Quality Survey System Characteristics User Concerns List Interview Questionnaire
|
3 | Analyze Implementation Reqts | Preliminary Stmt of Reqts
| Quality Criteria Control Analysis Implementation List
|
4 | Resolve Conflicts & Trade-offs | Final Stmt of Reqts
| JAD Cost/Benefit Analysis Risk Analysis Conflict Matrix
|
5 | Verify Reqts
| Final Stmt of Reqts
| Measures Model Balancing Walkthroughs, Reviews User Rating
|
6 | Validate Reqts
| Final Stmt of Reqts
| Reverse Engineering Reqts Tracing Testing
|
The Requirements Model is a 6 step requirements gathering process useful for end users, business analysts, and developers. By means of its structure, it automatically assures mission-based, needs-based requirements that are not solutions-driven.
Resolving Conflicts and Trade-offsWhat to do—without playing the “You-bet-your -job-game” - when, for example:
- Users can’t agree and are scrimmaging
- Business analysts are ignoring customer input
- Customers are ignoring business analysts
- Powerful people are skirting or manipulating the priority-setting process …and other requirements gathering people-related problems?
Answer: Agree on a process to resolve these conflicts like the process we'll demonstrate in this WEBinar.
Verifying RequirementsThe objective of Step 5 - Verify Requirements is to ensure that the requirements in the Statement of Requirements do, in fact, not only meet the business need but are also defect-free.
Important Points about Validating RequirementsMany of the tools in this step ought to be carried out by or with the assistance of the customer.
The more tools that are used, the higher the quality of the requirements.
Defects During Requirements DefinitionThe following are defects that frequently occur during the requirements definition phase because they are inadequate or partially missing:
- Operating rules (or information)
- Performance Criteria
- Environment information
- System mission information
Validating Requirements, Step 6This WEBinar will describe important techniques to quality control check the accuracy of the Final Requirements Statements before they are distributed. In addition, important techniques will be shown to insure that these correct, QC'ed requirements are correctly installed.
收藏
举报
TAG: