Waterfall Lifecycle Sample Clauses
The Waterfall Lifecycle clause defines a sequential project management approach where each phase must be completed before the next begins. In practice, this means that requirements are fully gathered and documented before design starts, design is finalized before development, and so on through testing and deployment. This clause ensures a structured and predictable workflow, minimizing overlap and ambiguity between project stages, and is particularly useful for projects with well-defined requirements and minimal expected changes.
Waterfall Lifecycle. (1) According to the Waterfall Lifecycle SAP will start the development of the Features based on the Specification.
a) If no Specification is available, SAP will write the Specification based on the Vision & Scope Document and the Product Backlog attached to the applicable Order Form. The Specification is subject to formal acceptance by Customer. After acceptance by Customer SAP will start the development of the Features.
b) If the Specification is already available, it will be attached to the applicable Order Form and SAP will start the development of the Features based on this Specification.
(2) SAP will offer to demonstrate portions of already developed Features to Customer (“Show & Tell Sessions”) for Customer to provide feedback. The main contacts for the Build Phase will agree on the number, extent and timeline of such sessions.
(3) During the Build Phase and until Customer’s acceptance of all Features, both parties may request changes to the CAE Services in accordance with the Change Request procedure.
(4) Upon completion of the Features, SAP will execute an integration test of all developed Features based on test cases provided by Customer.
(5) After SAP has completed the integration test, SAP will make the Features available for Customer in a development and/or test system landscape. Once SAP declares towards Customer readiness for Acceptance Testing of the Features, the period for conducting Acceptance Tests begins.
Waterfall Lifecycle. (1) According to the Waterfall Lifecycle SAP will start the development of the Features based on the Specification.
a) If no Specification is available, SAP will write the Specification based on the Customer Requirements as set out in the Solution Proposal attached to the applicable Order Form. The Specification is subject to formal acceptance by Customer. After acceptance by Customer SAP will start the development of the Features.
b) If the Specification is already available, it will be attached to the applicable Order Form and SAP will start the development of the Features based on this Specification.
(2) SAP will offer to demonstrate portions of already developed Features to Customer (“Show & Tell Sessions”) for Customer to provide feedback. The main contacts for the Build Phase will agree on the number, extent and timeline of such sessions.
(3) Until all Features have been accepted, both parties may request changes in writing in accordance with the Change Request procedure.
(4) Upon completion of the Features, SAP will execute an integration test of all developed Features based on test cases provided by Customer.
(5) After SAP has completed the integration test, SAP will make the Features available for Customer in a development and/or test system landscape. Once SAP declares towards Customer readiness for Acceptance Testing of the Features, the period for conducting Acceptance Tests begins.
Waterfall Lifecycle. (1) According to the Waterfall Lifecycle HRMANTRA will start the development of the Features based on the Specification.
a) If no Specification is available, HRMANTRA will write the Specification based on the Vision & Scope Document and the Product Backlog attached to the applicable Order Form. The Specification is subject to formal acceptance by Customer. After acceptance by Customer HRMANTRA will start the development of the Features.
b) If the Specification is already available, it will be attached to the applicable Order Form and HRMANTRA will start the development of the Features based on this Specification.
(2) HRMANTRA will offer to demonstrate portions of already developed Features to Customer (“Show & Tell Sessions”) for Customer to provide feedback. The main contacts for the Build Phase will agree on the number, extent and timeline of such sessions.
(3) During the Build Phase and until Customer’s acceptance of all Features, both parties may request changes to the CAE Services in accordance with the Change Request procedure.
(4) Upon completion of the Features, HRMANTRA will execute an integration test of all developed Features based on test cases provided by Customer.
(5) After HRMANTRA has completed the integration test, HRMANTRA will make the Features available for Customer in a development and/or test system landscape. Once HRMANTRA declares towards Customer readiness for Acceptance Testing of the Features, the period for conducting Acceptance Tests begins.
Waterfall Lifecycle. Waterfall 生命週期
(1) According to the Waterfall Lifecycle SAP will start the development of the Features based on the Specification. 根據 Waterfall 生命週期，SAP 會以規格為基礎開始執行特性開發作業。
a) If no Specification is available, SAP will write the Specification based on the Customer Requirements as set out in the Solution Proposal attached to the applicable Order Form. The Specification is subject to formal acceptance by Customer. After acceptance by Customer SAP will start the development of the Features. 若未提供規格，則 SAP 將根據方案建議書 (附加至適用的訂購單) 中所列的客戶需求來撰寫規格。規格必須獲得客戶的正式同意。獲得客戶同意後，SAP 即會開始執行特性開發作業。
b) If the Specification is already available, it will be attached to the applicable Order Form and SAP will start the development of the Features based on this Specification. 若已提供規格，則其會附加至適用的訂購單，且 SAP 將會根據此規格開始執行特性開發作業。
(2) SAP will offer to demonstrate portions of already developed Features to Customer (“Show & Tell Sessions”) for Customer to provide feedback. The main contacts for the Build Phase will agree on the number, extent and timeline of such sessions. SAP 會向客戶提供已開發特性的展示部分 (「展示及講述工作階段」)，以供客戶提供回饋意見。建立階段的主要聯絡人將會就上述工作階段的數字、範圍以及時間表方面，共同達成協議。
(3) Until all Features have been accepted, both parties may request changes in writing in accordance with the Change Request procedure. 在所有特性皆獲得同意之前，各方得根據變更請求程序以書面方式請求變更。
(4) Upon completion of the Features, SAP will execute an integration test of all developed Features based on test cases provided by Customer. 完成特性時，SAP 將會根據客戶提供的測試案例，針對所有已開發特性執行整合測試。 (5) After SAP has completed the integration test, SAP will make the Features available for Customer in a development and/or test system landscape. Once SAP declares towards Customer readiness for Acceptance Testing of the Features, the period for conducting Acceptance Tests begins. SAP 完成整合測試後，SAP 將會在開發和/或測試系統架構中向客戶提供特性。一旦 SAP 向客戶宣告已完成特性驗收測試的準備，驗收測試期間即就此開始。