本文的圖表等摘抄自 書 Effective Software Testing: 50 Specific Ways to Improve Your Testing 的 第12 章，作為學習之用。
如果有版權問題，請給我留言
估算測試量
Ideally, test estimation should always begin with either a work breakdown structure (WBS) or a detailed list of testing tasks from which a "testing WBS" can be built.
根據項目的需求和公司的組織架構將測試工作分解：
http://www.mypm.net/special/wbs/
http://baike.baidu.com/view/530736.html?wtp=tt
Development Ratio Method 開發人員比例法
Table 12.1. Test-Team Size Calculated Using the Development-Ratio Method
|
|
Product Type
|
Number of Developers
|
Ratio of Developers to Testers
|
Number of Testers
|
|
Commercial Product (Large Market)
|
30
|
3:2
|
20
|
|
Commercial Product (Small Market)
|
30
|
3:1
|
10
|
|
Development & Heavy COTS Integration for Individual Client
|
30
|
4:1
|
7
|
|
Government (Internal) Application Development
|
30
|
5:1
|
6
|
|
Corporate (Internal) Application Development
|
30
|
4:1
|
7
|
在圖表中， Number of developers 的developer 包含(design-, development-, and unit-level test activities) 設計，開發，單元測試的人力。
針對項目的類型，比例不同。
在軟件工程中，項目后期緊張時，研發和PM也會參與測試，因此可以保證測試人員的數量。
本方法在對于醫療，航空等需要完全沒有差錯的項目，不適用的。
Project Staff Ratio Method 項目人員比例法
|
Table 12.2. Test-Team Size Calculated Using the Project Staff Ratio Method
|
|
Development Type
|
Project Staffing Level
|
Test Team Size Factor
|
Number of Testers
|
|
Commercial Product (Large Market)
|
50
|
27%
|
13
|
|
Commercial Product (Small Market)
|
50
|
16%
|
8
|
|
Application Development for Individual Client
|
50
|
10%
|
5
|
|
Development & Heavy COTS Integration for Individual Client
|
50
|
14%
|
7
|
|
Government (Internal) Application Development
|
50
|
11%
|
5
|
|
Corporate (Internal) Application Development
|
50
|
14%
|
7
|
本表為經驗數據。
對于開發人員經常變動或者對開發量估計不充分的團隊比較有效。
Test Procedure Method 測試過程法
|
Table 12.3. Test-Team Size Calculated Using the Test-Procedure Method
|
|
|
Number of Test Procedures
|
Factor
|
Number of Person Hours
|
Performance Period
|
Number of Testers
|
|
Historical Record (Average of Two or More Similar Projects)
|
860
|
6.16
|
5,300
|
9 months (1,560 hrs)
|
3.4
|
|
New Project Estimate
|
1,120
|
6.16
|
6,900
|
12 months (2,080 hrs)
|
3.3
|
860*6.16/1560=3.4
按照組織已有的經驗估算測試過程和系數。
5300怎么算出來的呢？見下：
Task Planning Method 計劃任務法
|
Table 12.4. Test-Personnel Hours Calculated Using the Task-Planning Method
|
|
|
Number of Test Procedures
|
Factor
|
Test-Personnel Hours
|
|
Historical Record (Similar Project)
|
860
|
6.16
|
5,300
|
|
New Project Estimate
|
1,120
|
6.16
|
6,900
|
|
Table 12.5. Hours Expended in Each Testing Phase, Task-Planning Method
|
|
Phase
|
Historical Value
|
% of Project
|
Preliminary Estimate
|
Adjusted Estimate
|
|
1
|
Project Startup
|
140
|
2.6
|
179
|
179
|
|
2
|
Early Project Support (requirements analysis, etc.)
|
120
|
2.2
|
152
|
152
|
|
3
|
Decision to Automate Testing
|
90
|
1.7
|
117
|
-
|
|
4
|
Test Tool Selection and Evaluation
|
160
|
3
|
207
|
-
|
|
5
|
Test Tool Introduction
|
260
|
5
|
345
|
345
|
|
6
|
Test Planning
|
530
|
10
|
690
|
690
|
|
7
|
Test Design
|
540
|
10
|
690
|
690
|
|
8
|
Test Development
|
1,980
|
37
|
2,553
|
2,553
|
|
9
|
Test Execution
|
870
|
17
|
1,173
|
1,173
|
|
10
|
Test Management and Support
|
470
|
9
|
621
|
621
|
|
11
|
Test Process Improvement
|
140
|
2.5
|
173
|
-
|
|
|
PROJECT TOTAL
|
5,300
|
100%
|
6,900
|
6,403
|
因為新項目和歷史項目大同小異，或者在于技術的選擇上已經有定義，一些步驟就可以省略。
|
Table 12.6. Test-Team Size Based on Personnel-Hour Estimate
|
|
|
Number of Test Procedures
|
Personnel-Hour Estimate
|
Adjusted Estimate
|
Performance Period
|
Number of Testers
|
|
New Project Estimate
|
1,120
|
5.71
|
6,403
|
12 months (2,080 hrs)
|
3.1
|
根據人月估算測試人數。
posted on 2008-02-22 12:48
Becky 閱讀(333)
評論(1) 編輯 收藏 所屬分類:
測試