Waterfall Lifecycle Sample Clauses

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.
Sample 1Sample 2Sample 3See All (33)
AutoNDA by SimpleDocs
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.
Sample 1Sample 2Sample 3See All (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.
Sample 1
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 向客戶宣告已完成特性驗收測試的準備，驗收測試期間即就此開始。
Sample 1

Related to Waterfall Lifecycle

  • Investment Analysis and Implementation In carrying out its obligations under Section 1 hereof, the Advisor shall: (a) supervise all aspects of the operations of the Funds; (b) obtain and evaluate pertinent information about significant developments and economic, statistical and financial data, domestic, foreign or otherwise, whether affecting the economy generally or the Funds, and whether concerning the individual issuers whose securities are included in the assets of the Funds or the activities in which such issuers engage, or with respect to securities which the Advisor considers desirable for inclusion in the Funds' assets; (c) determine which issuers and securities shall be represented in the Funds' investment portfolios and regularly report thereon to the Board of Trustees; (d) formulate and implement continuing programs for the purchases and sales of the securities of such issuers and regularly report thereon to the Board of Trustees; and (e) take, on behalf of the Trust and the Funds, all actions which appear to the Trust and the Funds necessary to carry into effect such purchase and sale programs and supervisory functions as aforesaid, including but not limited to the placing of orders for the purchase and sale of securities for the Funds.

  • Program Monitoring The Contractor will make all records and documents required under this Agreement as outlined here, in OEC Policies and NHECC Policies available to the SRO or its designee, the SR Fiscal Officer or their designee and the OEC. Scheduled monitoring visits will take place twice a year. The SRO and OEC reserve the right to make unannounced visits.

  • Anti-Layering The Company shall not incur, create, issue, assume, guarantee or otherwise become liable for any Indebtedness that is both (a) subordinate or junior in right of payment to any Senior Debt and (b) senior in any respect in right of payment to the Notes. No Subsidiary Guarantor shall incur, create, issue, assume, guarantee or otherwise become liable for any Indebtedness that is both (a) subordinate or junior in right of payment to its Senior Debt and (b) senior in right of the Section 4.9 hereof.

  • Reducing Text Messaging While Driving Pursuant to Executive Order 13513, 74 FR 51225 (Oct. 6, 2009), Recipient should encourage its employees, subrecipients, and contractors to adopt and enforce policies that ban text messaging while driving, and Recipient should establish workplace safety policies to decrease accidents caused by distracted drivers.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Single Source Selection Services for tasks in circumstances which meet the requirements of paragraph 3.10 of the Consultant Guidelines for Single Source Selection, may, with the Association's prior agreement, be procured in accordance with the provisions of paragraphs 3.9 through 3.13 of the Consultant Guidelines.

  • Quality control system (i) The Contractor shall establish a quality control mechanism to ensure compliance with the provisions of this Agreement (the “Quality Assurance Plan” or “QAP”). (ii) The Contractor shall, within 30 (thirty) days of the Appointed Date, submit to the Authority’s Engineer its Quality Assurance Plan which shall include the following: (a) organisation, duties and responsibilities, procedures, inspections and documentation; (b) quality control mechanism including sampling and testing of Materials, test frequencies, standards, acceptance criteria, testing facilities, reporting, recording and interpretation of test results, approvals, check list for site activities, and proforma for testing and calibration in accordance with the Specifications for Road and Bridge Works issued by MORTH, relevant IRC specifications and Good Industry Practice; and (c) internal quality audit system. The Authority’s Engineer shall convey its approval to the Contractor within a period of 21 (twenty-one) days of receipt of the QAP stating the modifications, if any, required, and the Contractor shall incorporate those in the QAP to the extent required for conforming with the provisions of this Clause 11.2. (iii) The Contractor shall procure all documents, apparatus and instruments, fuel, consumables, water, electricity, labour, Materials, samples, and qualified personnel as are necessary for examining and testing the Project Assets and workmanship in accordance with the Quality Assurance Plan. (iv) The cost of testing of Construction, Materials and workmanship under this Article 11 shall be borne by the Contractor.

  • ANALYSIS AND MONITORING The Custodian shall (a) provide the Fund (or its duly-authorized investment manager or investment adviser) with an analysis of the custody risks associated with maintaining assets with the Eligible Securities Depositories set forth on Schedule B hereto in accordance with section (a)(1)(i)(A) of Rule 17f-7, and (b) monitor such risks on a continuing basis, and promptly notify the Fund (or its duly-authorized investment manager or investment adviser) of any material change in such risks, in accordance with section (a)(1)(i)(B) of Rule 17f-7.

  • TOOL STORAGE 1. A company shall provide on all construction jobs in towns and cities, and elsewhere where reasonably necessary and practicable (or if requested buy the employee), a suitable and secure waterproof lock-up solely for the purpose of storing employees’ tools, and on multi-storey and major projects the company shall provide, where possible, a suitable lock-up for employees’ tools within a reasonable distance of the work area of large groups of employees. 2. Where an employee is absent from work because of illness or accident and has advised the company in accordance with Clause 33 – Personal Leave of the award, the company shall ensure that the employee’s tools are securely stored during his/her absence.

  • Dark Fiber Transport Dark Fiber Transport is defined as Dedicated Transport that consists of unactivated optical interoffice transmission facilities without attached signal regeneration, multiplexing, aggregation or other electronics. Except as set forth in Section 6.9.1 below, BellSouth shall not be required to provide access to Dark Fiber Transport Entrance Facilities pursuant to this Agreement.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!