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.
View SourceView Similar (33)
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.
View SourceView Similar (24)
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.
View Source
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 向客戶宣告已完成特性驗收測試的準備，驗收測試期間即就此開始。
View Source

Related to Waterfall Lifecycle

  • Loss Leader; Recycled Products Contractor shall not sell or use any article or product as a “loss leader” as defined in Section 17030 of the Business and Professions Code. If Contractor will sell to the Judicial Council, or use in the performance of this Agreement, goods specified in PCC 12207 (for example, certain paper products, office supplies, mulch, glass products, lubricating oils, plastic products, paint, antifreeze, tires and tire-derived products, and metal products), then with respect to those goods: (i) Contractor shall use recycled products in the performance of this Agreement to the maximum extent doing so is economically feasible, and (ii) upon request, Contractor shall certify in writing under penalty of perjury, the minimum, if not exact, percentage of post consumer material as defined in the PCC 12200, in such goods regardless of whether the goods meet the requirements of PCC 12209.

  • Recovery Procedures 38.7.10.1 The nature and severity of any disaster will influence the recovery procedures. One crucial factor in determining how AT&T TENNESSEE will proceed with restoration is whether or not AT&T TENNESSEE’s equipment is incapacitated. Regardless of whose equipment is out of service, AT&T TENNESSEE will move as quickly as possible to aid with service recovery; however, the approach that will be taken may differ depending upon the location of the problem.

  • Investment Program The Subadviser is hereby authorized and directed and hereby agrees, subject to the stated investment objective and policies of the Fund as set forth in the Trust’s current Registration Statement and subject to the supervision of the Adviser and the Board of Trustees of the Trust, to (i) develop and furnish continuously an investment program and strategy for the Fund in compliance with the Fund’s investment objective and policies as set forth in the Trust’s current Registration Statement, (ii) provide research and analysis relative to the investment program and investments of the Fund, (iii) determine (subject to the overall supervision of the Board of Trustees of the Trust) what investments shall be purchased, held, sold or exchanged by the Fund and what portion, if any, of the assets of the Fund shall be held in cash or cash equivalents, and (iv) make changes on behalf of the Trust in the investments of the Fund. In accordance with paragraph 2(ii)(b), the Subadviser shall arrange for the placing of all orders for the purchase and sale of securities and other investments for the Fund’s account and will exercise full discretion and act for the Trust in the same manner and with the same force and effect as the Trust might or could do with respect to such purchases, sales or other transactions, as well as with respect to all other things necessary or incidental to the furtherance or conduct of such purchases, sales or transactions. The Subadviser will make its officers and employees available to meet with the Adviser’s officers and directors on due notice at reasonable times to review the investments and investment program of the Fund in light of current and prospective economic and market conditions. The Subadviser is authorized on behalf of the Fund to enter into agreements and execute any documents required to make investments pursuant to the Prospectus as may be amended from time to time. The Subadviser’s responsibility for providing portfolio management services hereunder shall be limited to only those assets of the Fund which the Adviser determines to allocate to the Subadviser (those assets being referred to as the “Fund Account”), and the Subadviser agrees that it shall not consult with any investment advisor(s) (within the meaning of the ▇▇▇▇ ▇▇▇) to the Fund or any other registered investment company or portfolio series thereof under common control with the Fund concerning transactions for the Fund Account in securities or other assets such that the exemptions under Rule 10f-3, Rule 12d-3 and/or Rule 17a-10 under the 1940 Act would not be available with respect to the Fund. The Subadviser shall exercise voting authority with respect to proxies that the Fund is entitled to vote by virtue of the ownership of assets attributable to that portion of the Fund for which the Subadviser has investment management responsibility; provided that the exercise of such authority shall be subject to periodic review by the Adviser and the Trustees of the Trust; provided, further that such authority may be revoked in whole or in part by the Adviser if required by applicable law. The Subadviser shall exercise its proxy voting authority hereunder in accordance with such proxy voting policies and procedures as the Trust may designate from time to time. The Subadviser shall provide such information relating to its exercise of proxy voting authority hereunder (including the manner in which it has voted proxies and its resolution of conflicts of interest) as reasonably requested by the Adviser from time to time. In the performance of its duties hereunder, the Subadviser is and shall be an independent contractor and except as expressly provided for herein or otherwise expressly provided or authorized shall have no authority to act for or represent the Fund or the Trust in any way or otherwise be deemed to be an agent of the Fund, the Trust or of the Adviser. If any occasion should arise in which the Subadviser gives any advice to its clients concerning the shares of a Fund, the Subadviser will act solely as investment counsel for such clients and not in any way on behalf of the Trust or the Fund.

  • Framework Management Structure The Supplier shall provide a suitably qualified nominated contact (the “Supplier Framework Manager”) who will take overall responsibility for delivering the Goods and/or Services required within this Framework Agreement, as well as a suitably qualified deputy to act in their absence. The Supplier shall put in place a structure to manage the Framework in accordance with Framework Schedule 2 (Goods and/or Services and Key Performance Indicators). A full governance structure for the Framework will be agreed between the Parties during the Framework Agreement implementation stage. Following discussions between the Parties following the Framework Commencement Date, the Authority shall produce and issue to the Supplier a draft Supplier Action Plan. The Supplier shall not unreasonably withhold its agreement to the draft Supplier Action Plan. The Supplier Action Plan shall, unless the Authority otherwise Approves, be agreed between the Parties and come into effect within two weeks from receipt by the Supplier of the draft Supplier Action Plan. The Supplier Action Plan shall be maintained and updated on an ongoing basis by the Authority. Any changes to the Supplier Action Plan shall be notified by the Authority to the Supplier. The Supplier shall not unreasonably withhold its agreement to any changes to the Supplier Action Plan. Any such changes shall, unless the Authority otherwise Approves, be agreed between the Parties and come into effect within two weeks from receipt by the Supplier of the Authority’s notification. Regular performance review meetings will take place at the Authority’s premises throughout the Framework Period and thereafter until the Framework Expiry Date (“Supplier Review Meetings”). The exact timings and frequencies of such Supplier Review Meetings will be determined by the Authority following the conclusion of the Framework Agreement. It is anticipated that the frequency of the Supplier Review Meetings will be once every month or less. The Parties shall be flexible about the timings of these meetings. The purpose of the Supplier Review Meetings will be to review the Supplier’s performance under this Framework Agreement and, where applicable, the Supplier’s adherence to the Supplier Action Plan. The agenda for each Supplier Review Meeting shall be set by the Authority and communicated to the Supplier in advance of that meeting. The Supplier Review Meetings shall be attended, as a minimum, by the Authority Representative(s) and the Supplier Framework Manager.