SYS.5 System Qualification Test 系統合格測試
ASPICE 標準解讀 - 系統工程流程
目錄: Automotive SPICE(ASPICE)標準解讀 / 系統工程流程SYS.1 系統需求獲取
SYS.2 系統需求分析
SYS.3 系統架構設計
SYS.4 系統整合與整合測試
SYS.5 系統合格測試
流程目的(Process Purpose)
The purpose of the System Qualification Test Process is to ensure that the integrated system is tested to provide evidence for compliance with the system requirements and that the system is ready for delivery.
系統合格測試流程的目的是確保對已整合的系統進行測試，並提供符合系統需求的證據，並確保系統已準備好交付。
額外說明：系統合格測試，又稱為系統驗收測試。系統合格測試與系統整合測試的主要差別如下表：
流程結果(Process Outcome)
成功實作系統合格測試流程，其相應的結果如下：
1) [Outcome 1]制定一個與專案計畫書和發佈計畫書保持一致性的系統合格測試策略(包含回歸測試策略)，並據此來測試已整合的系統
2) [Outcome 2]根據系統合格測試策略開發系統合格測試規格書，該測試規格書應適當提供符合系統需求的證據
3) [Outcome 3]根據系統合格測試策略和發佈計畫書，選擇在系統合格測試規格書中的測試案例
4) [Outcome 4]使用所挑選的測試案例去測試已整合的系統，並記錄其測試結果
5) [Outcome 5]建立系統需求(系統需求規格書)與測試案例(系統合格測試規格書)的一致性與雙向可追溯性; 建立測試案例(系統合格測試規格書)與系統合格測試結果的雙向追溯性
6) [Outcome 6]總結系統合格測試結果並與相關單位溝通
基礎實踐(Base Practices)
SYS.5.BP1: Develop system qualification test strategy including regression test strategy.
SYS.5.BP1: 制定系統合格測試策略包含回歸測試策略[Outcome 1]
Develop a strategy for system qualification test consistent with the project plan and the release plan. This includes a regression test strategy for re-testing the integrated system if a system item is changed.
制定一個與專案計劃書和發布計劃書一致的系統合格測試策略，包含當系統元件變更時實施重測的回歸測試策略。
—
SYS.5.BP2: Develop specification for system qualification test.
SYS.5.BP2: 制定系統合格測試規格書[Outcome 2]
Develop the specification for system qualification test including test cases based on the verification criteria according to the qualification test strategy. The test specification shall be suitable to provide evidence for compliance of the integrated system with the system requirements.
根據系統合格測試策略，制定系統合格測試規格書；該規格書需包含依據驗證準則(系統需求)而設計的測試案例。測試規格書應適當地體現已整合系統符合系統需求的證據。
—
SYS.5.BP3: Select test cases.
SYS.5.BP3: 選擇測試案例 [Outcome 3]
Select test cases from the system qualification test specification. The selection of test cases shall have sufficient coverage according to the system qualification test strategy and the release plan.
從系統合格測試規格書中選擇測試案例。選用的測試案例應根據系統合格測試策略和發佈計畫書，並充分體現其覆蓋率。
—
SYS.5.BP4: Test integrated system.
SYS.5.BP4: 測試已整合的系統[Outcome 4]
Test the integrated system using the selected test cases. Record the system qualification test results and logs.
使用選定的測試案例測試已整合的系統，並記錄系統測試結果與日誌。
NOTE 1: See SUP.9 for handling of non-conformances.
備註1: 有關不符合項目的處理，請參見SUP.9。
—
SYS.5.BP5: Establish bidirectional traceability.
SYS.5.BP5: 建立雙向可追溯性 [Outcome 5]
Establish bidirectional traceability between system requirements and test cases included in the system qualification test specification. Establish bidirectional traceability between test cases included in the system qualification test specification and system qualification test results.
建立系統需求與測試案例(系統合格測試規格書)的雙向追溯性。
建立測試案例(系統合格測試規格書)與系統合格測試結果的雙向追溯性。
NOTE 2: Bidirectional traceability supports coverage, consistency and impact analysis.
備註2: 雙向追溯性支援覆蓋性、一致性和影響分析。
—
SYS.5.BP6: Ensure consistency.
SYS.5.BP6: 確保一致性 [Outcome 5]
Ensure consistency between system requirements and test cases included in the system qualification test specification.
確保系統需求(系統需求規格書)與測試案例(系統合格測試規格書)的一致性。
NOTE 3: Consistency is supported by bidirectional traceability and can be demonstrated by review records.
備註3: 一致性可以透過雙向追溯性來支持，且可以透過審查紀錄來體現。
額外說明：請參考下圖藍色框起的部分。系統合格測試規格書(System qualification test specification)需要與：1)系統需求(System Requirement)保持一致性與雙向追溯性；
2)測試結果(Test result)保持雙向追溯性。
—
SYS.5.BP7: Summarize and communicate results.
SYS.5.BP7: 總結和溝通測試結果 [Outcome 6]
Summarize the system qualification test results and communicate them to all affected parties.
總結系統合格測試結果並與相關單位溝通。
NOTE 4: Providing all necessary information from the test case execution in a summary enables other parties to judge the consequences.
備註4: 統整並提供測試案例執行的所有必要資訊將能讓其他單位判斷結果。
工作產出(Output Work product)
08–50 測試規格書 [Outcome 3,5] 08–52 測試計畫書 [Outcome 1] 13-04 溝通記錄 [Outcome 6]13-19 審查記錄 [Outcome 5]13-22 追溯記錄 [Outcome 5]13-50 測試報告 [Outcome 4,6]
感謝閱讀本文章！
如果你對文章內容有任何問題，請隨時與我聯絡。
if you found any question in the article, please feel free to contact me.
email: linchewing@gmail.com
