Requests for Software Development Sample Clauses

Requests for Software Development. For each project that Customer desires CSG to undertake, Customer will complete the CSG Business Requirements Specification Document (“BRD”) in the form approved by the Parties from time-to-time. This document will be validated and submitted to CSG by Customer’s Contract Administrator, Technical Coordinator, or other Authorized Customer Representative. • BRD – The Customer will define the project scope, background, and objectives, along with use cases for the requested software development or customization project(s). In response to receiving a BRD Trigger Document, CSG will complete the following Response Document: - Initial Project Analysis (“IPA”) in the form approved by the Parties from time-to-time • IPA- After trigger document is submitted, CSG may need to engage Customer in additional information collection, fact-finding, and clarification activities as required to fully comprehend Customer’s intended usage and implementation plans. After such activities are complete, CSG will respond to Customer with an IPA. The purpose of the Initial Project Analysis (IPA) is to provide a proposed solution to a BRD that can be used to develop a detailed design, and to provide CSG and Customer an overall estimate of the size of the development request. This document will be provided to Customer for approval and signature. Upon the Customer approval of the IPA, CSG will complete the following Response Documents: - D-SOW - SOW • D-SOW - The purpose of the D-SOW is to produce a detailed functional specification for development of the CSG proposed solution to Customer requirements, as specified in the BRD and further clarified in the IPA. If the size of the estimate provided in the IPA is greater than **** *****, a D-SOW is created for completion of the design phase and then after D-SOW Customer approval, an SOW is created once the design is completed. If the size of the estimate is less than **** *****, an SOW only is created for the complete development life cycle. • SOW – The purpose of the SOW is to provide formal acceptance by the Customer of the project design, cost and implementation schedule. The SOW will provide reliable cost and schedule estimates along with a description of the tasks to be completed and the deliverables to be produced. Upon Customer’s execution of the SOW, CSG will commence providing the requested services. An SOW will be used for reoccurring services regardless of the dollar amount. Except as otherwise specifically provided in a Statement o...
AutoNDA by SimpleDocs

Related to Requests for Software Development

  • Licensed Software Section 3.17(f).......................................27

  • TECHNICAL SUPPORT SERVICES 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").

  • Technology For purposes of this Agreement, “Technology” means all Software, information, designs, formulae, algorithms, procedures, methods, techniques, ideas, know-how, research and development, technical data, programs, subroutines, tools, materials, specifications, processes, inventions (whether or not patentable and whether or not reduced to practice), apparatus, creations, improvements and other similar materials, and all recordings, graphs, drawings, reports, analyses, and other writings, and other embodiments of any of the foregoing, in any form or media whether or not specifically listed herein. Further, for purposes of this Agreement, “Software” means any and all computer programs, whether in source code or object code; databases and compilations, whether machine readable or otherwise; descriptions, flow-charts and other work product used to design, plan, organize and develop any of the foregoing; and all documentation, including user manuals and other training documentation, related to any of the foregoing.

  • USE OF THIRD PARTY SYSTEMS-LEVEL SOFTWARE State Street and the Fund acknowledge that in connection with the Data Access Services provided under this Addendum, the Fund will have access, through the Data Access Services, to Fund Data and to functions of State Street’s proprietary systems; provided, however that in no event will the Fund have direct access to any third party systems-level software that retrieves data for, stores data from, or otherwise supports the System.

  • Computer Software All computer applications software, owned or licensed, whether for general business usage (e.g., accounting, word processing, graphics, spreadsheet analysis, etc.), or specific, unique-to-the-business usage, and all computer operating, security or programming software, owned or licensed by Seller and used in the operation of the Business; and

  • Software Additional provisions relating to software.

  • Support Services Other than the assistance provided in the Information, the BNPP Entities do not offer any support services in connection with the Software.

  • Maintenance and Support Services Distributor shall provide Maintenance and Support Services to all of its Customers of Licensed Software as set forth in Sections 3.4(a) and 3.4(b) below. Distributor may require Customers to provide the own First-Line Support: however, in no event shall Siebel be responsible for First-Line or Second-Line Support. Subject to Distributor's payment of the Maintenance Fees set forth in EXHIBIT A Siebel shall provide Third-Line Support to Distributor in accordance with Siebel's then current Maintenance and Support Services Policy. Distributor shall be responsible for all support related to the Value Added Offering.

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Deliverables Upon completion of each Test for each Reviewable Receivable, the Asset Representations Reviewer shall record a finding based on the issues discovered. Findings categories are listed as follows: • Evidence that the applicable Test was satisfied (“Satisfied Test”); • Evidence that the applicable Test was not satisfied (“Unsatisfied Test”); and • Test incomplete as a result of missing or insufficient documentation (“Unsatisfied Test – Missing Required Documents”).

Time is Money Join Law Insider Premium to draft better contracts faster.