翻譯：測試成熟度模型集成（TMMi）（9）

TMMi Level 2: Managed
TMMi2級：管理級
In level 2, testing becomes a managed process and is clearly separated from debugging. The process discipline
reflected by maturity level 2 helps to ensure that existing practices are retained during times of stress. However, it
is by many stakeholders still perceived as being a project phase that follows coding. In the context of improving the
test process, a company-wide or program-wide test strategy is established. Test plan are also being developed.
Within the test plan a test approach is defined, whereby the approach is based on the level of risk. Risk
management techniques are used to identify the product risks based on documented requirements. The test plan
will define what testing is required, when, how and by whom. Commitments are established among relevant
stakeholders and revised as needed. Testing is monitored and controlled to ensure it is going according to plan and
actions can be taken if deviations occur. The status of the work products and the delivery of testing services are
visible to management. For deriving and selecting test cases from specifications test design techniques are
applied. However, testing may still start relatively late in the development lifecycle, e.g. during the design or even
during the coding phase. Testing is multi-leveled: there are unit, integration, system and acceptance test levels. For
each identified test level there are specific testing objectives defined in the organization-wide or program-wide test
strategy. The main objective of testing in a TMMi level 2 organizations is to verify that the product satisfies the
specified requirements. The purpose is also to clearly differentiate the processes of testing and debugging. Many
quality problems at this TMMi level occur because testing occurs late in the development lifecycle. Defects are
propagated from the requirements and design into code. There are no review programs as yet to address this
important issue. Post code, execution based testing is by many stakeholders still considered the primary testing
activity.
在第2級，測試成爲了管理過程，並明確地從調試中分開。由成熟度2級反射出的過程訓練有助於確信在時間壓力下，現行慣例被保留。然而，許多利益相關者仍然感覺它是編碼過後的一個階段。在改進測試過程的背景下，一個公司範圍或者產品範圍的測試策略被建立了。測試計劃也被制定。在測試計劃中，測試方法被定義，該方法基於這個級別的風險。風險管理技術被用來識別基於文檔化需求的產品風險。測試計劃將會定義需要測試什麼，什麼時候測試，如何測試以及有誰來測試。在利益相關者中間建立承諾，並根據需要修改。測試過程被監控以確保它按照計劃執行，一旦有背離發生會有相應的動作。工作產品的狀態和測試服務的遞交對管理來說是可見的。從詳細規格說明中選擇測試用例的測試設計技術被應用了。然而，在開發生命週期測試仍然開始的比較晚，比如要在設計或者在編碼階段纔開始。測試分了多個層次，有單元測試，綜合測試，系統測試和驗收測試。對於每個確定的測試層次有指定的測試目標定義在組織範圍或者產品範圍的測試策略。2級TMMi組織的主要測試目標是檢驗產品是否符合指定的需求。還有一個目的是清楚地界定測試和調試。這個級別的TMMi有許多的質量問題是因爲測試
啓動太晚。缺陷被引入從需求階段，設計階段到編碼階段。沒有正式的評審程序去定位這個重要的問題。許多人認爲編碼過後的測試執行是主要的測試活動。
The process areas at TMMi level 2 are:
2.1 Test Policy and Strategy
2.2 Test Planning
2.3 Test Monitoring and Control
2.4 Test Design and Execution
2.5 Test Environment
2級TMMi有過程域如下：
2.1 測試政策和策略
2.2 測試計劃
2.3 測試監控
2.4 測試設計和執行
2.5 測試環境

PA2.1 Test Policy and Strategy
PA2.1 測試政策和策略
Purpose
目標
The purpose of Test Policy and Strategy is to develop and establish a test policy and an organization-wide or
program-wide test strategy in which the test levels are unambiguously defined. To measure test performance, test
performance indicators are introduced.
測試政策和策略的目標是開發和建立測試策略和組織範圍或者產品範圍的策略，在此測試級別被明確定義。爲了衡量測試性能，測試性能指標被引入。
Introductory Notes
介紹性說明
When an organization wants to improve its test process, it should first clearly define a test policy. The test policy
defines the organization’s overall test objectives, goals and strategic views regarding testing. It is important that the
test policy is aligned with the overall business (quality) policy of the organization. A test policy is necessary to attain
a common view on testing between all stakeholders within an organization. This common view is indispensable to
align test (process improvement) activities. The test policy should address both new development and maintenance
testing activities. Within the test policy the objectives for test process improvement should be stated. These
objectives will subsequently be translated into a set of key test performance indicators. The test policy and the
accompanying performance indicators provide a clear direction, and a means to communicate expected and
achieved levels of test performance. The performance indicators have the objective to show the value of testing
and test process improvement to stakeholders.
當組織想改進它的測試過程的時候，它首先應該清楚的定義測試政策。測試政策定義了組織總體測試目的，目標和測試相關的戰略視圖。重要的是測試政策與組

織的商業（質量）政策相一致。測試政策有必要對組織所有相關人員實現一個統一的測試視圖。這個統一的測試視圖對於測試活動（過程改進）是必需的。測試

政策必須實現新的開發，和維護測試活動。在測試政策中，測試過程改進的目標需要被說明。隨後這些目標將會轉成一套關鍵性能指標。測試政策及其相隨的性

能指標提供了明確的指示，溝通的方法，以期望和實現測試的性能級別。性能指示器客觀的向相關人員展示了測試和測試過程改進的數值。
Based upon the test policy a test strategy will be defined. The test strategy covers the generic test requirements for
an organization or program (one or more projects). The test strategy addresses the generic product risks and
presents a process for mitigating those risks in line with the testing policy.

The test strategy therefore starts by
performing a generic product risk assessment studying the products being developed within a program or
organization. A typical test strategy will include a description of the test levels that are to be applied, for example:
unit, integration, system and acceptance test. For each test level amongst others the objectives, responsibilities,
main tasks and entry/exit criteria are defined.

The test strategy serves as a starting point for the testing activities
within projects. The projects are set up in accordance with the organization-wide or program-wide test strategy.
When a test strategy is defined and followed, less overlap between the test levels is likely to occur leading to a
more efficient test process. Also since the test objectives and approach of the various levels is aligned fewer holes
are likely to remain leading to a more effective test process.
在測試政策的基礎上定義了測試策略。測試策略包含了組織或者產品（一個或多個項目）的通用測試需求。測試策略解決了通用產品風險，提出了減輕風險並與

測試政策相一致的過程。因此測試策略通過執行通用產品風險評估--研究在產品或者組織內的正在被開發的產品。一個典型的測試策略包括需要被實現的測試類

別的描述，例如，單元測試，綜合測試，系統測試和驗收測試。對於每個測試類別中的人的目標，職責，主要任務和進入/退出標準被定義。測試策略作爲項目測

試活動的起始點。項目依照組織範圍或者產品範圍的測試策略被建立。當測試策略被定義且被遵守的時候，測試類別只有少的重疊，且會導向一個更加有效的測

試過程。此外，由於測試的目標和各個層次的做法是一致的，較少的漏洞被遺留，這也會導致更有效的測試過程。
Scope
範圍
The process area Test Policy and Strategy involves the definition and deployment of a test policy and test strategy.
Within the test strategy, test levels are identified. For each test level, amongst other test objectives, responsibilities
and main tasks are defined. To measure test performance and the accomplishment of test (improvement) goals,
test performance indicators are defined and deployed.
測試政策和策略過程域包括測試政策和測試策略的定義和部署。在測試策略中，測試級別被定義。對於每個測試級別，其中包括的測試目標，職責和主要任務被

定義。爲了測量測試性能和測試（改進）目標的完成度，測試性能指標被定義和部署。
Specific Goal and Practice Summary
SG1 Establish a test policy
SP 1.1 Define test goals
SP 1.2 Define test policy
SP 1.3 Distribute the test policy to stakeholders
SG2 Establish a test strategy
SP 2.1 Perform a generic product risk assessment
SP 2.2 Define test strategy
SP 2.3 Distribute the test strategy to stakeholders
SG3 Establish test performance indicators
SP 3.1 Define test performance indicators
SP 3.2 Deploy test performance indicators
具體目標和實踐小結
SG1 建立測試政策
SP1.1 定義測試目標
SP1.2 定義測試政策
SP1.3 分配測試政策到相關人員
SG2 建立測試策略
SP2.1 執行通用產品風險管理
SP2.2 定義測試策略
SP2.3 分配測試策略到相關人員
SG3 定義測試性能指標
SP 3.1 定義測試性能指標
SP 3.2 實施測試性能指標