Software Title Development Sample Clauses

Software Title Development. Licensee's development activities with respect to each Software Title shall be in accordance with the development schedule set forth in the applicable Exhibit A-n. Furthermore, Licensee agrees to be bound by all provisions contained in the then-applicable version of the "Xbox Guide", the current version of which Microsoft or its affiliate will deliver to Licensee when it is completed, after the execution of this Agreement. Licensee understands and agrees that Microsoft may, in its discretion, supplement, revise and update the Xbox Guide from time to time and that upon Licensee's receipt of the applicable supplement, revision or updated version, Licensee automatically shall be bound by all provisions of the then-current Xbox Guide; Microsoft will specify in each such supplement, revision or updated version a reasonable effective date of each change if such change or revision is not required to be effective immediately. If Licensee proceeds with the development of a Software Title, Licensee shall deliver each milestone (as described in this Section 2.1) to Microsoft for approval in writing. All certification and playtesting (and applicable fees therefor, if any) will be in accordance with the then-applicable version of the Xbox Guide. If Microsoft does not approve Licensee's submission for a given milestone then Licensee shall either correct the problems that contributed to the lack of approval or, if Microsoft gives Licensee written notice to cease development, Licensee shall immediately cease all development activities for the applicable Software Title's subsequent milestones. Each successive milestone shall comply in all material respects with the characteristics of previously approved milestones. Each software milestone shall be delivered in compiled object code form.
Sample 1Sample 2Sample 3See All (9)
AutoNDA by SimpleDocs
Software Title Development. Licensee's development activities with respect to each Software Title shall be in accordance with the development schedule set forth in the applicable Exhibit A-n. Furthermore, Licensee agrees to be bound by all provisions contained in the then-applicable version of the "Xbox Guide", the current version of which Microsoft or its affiliate will deliver to Licensee when it is completed, after the execution of this Agreement. Licensee understands and agrees that Microsoft may, in its discretion, supplement, revise and update the Xbox Guide from time to time and that upon Licensee's receipt of the applicable supplement, revision or updated version, Licensee automatically shall be bound by all provisions of the then-current Xbox Guide; Microsoft will specify in each such supplement, revision or updated version a reasonable effective date of each change if such change or revision is not required to be effective immediately. If Licensee proceeds with the development of a Software Title, Licensee shall deliver each milestone (i.e., Concept milestone as described in Section 2.1.1, optional Preliminary Version milestones(s) as described in Section 2.1.2, Feature-Complete Version milestone as described in Section 2.1.3, and Final Release Version milestone as described in Section 2.1.4) to Microsoft for approval in writing, and Microsoft agrees to use good faith efforts to promptly review each milestone and render its approvals or rejections thereof within a reasonable period of time. All certification and playtesting (and applicable fees therefor, if any) will be in accordance with the then-applicable version of the Xbox Guide. If Microsoft does not approve Licensee's submission for a given milestone then Licensee shall either correct the problems that contributed to the lack of approval or, if Microsoft gives Licensee written notice to cease development, Licensee shall immediately cease all development activities for the applicable Software Title's subsequent milestones. Each successive milestone shall comply in all material respects with the characteristics of previously approved milestones. Each software milestone shall be delivered in compiled object code form.
Sample 1

Related to Software Title Development

  • Software Development Software designs, prototypes, and all documentation for the final designs developed under this agreement must be made fully transferable upon direction of NSF. NSF may make the software design, prototype, and documentation for the final design available to competitors for review during any anticipated re-competition of the project.

  • Curriculum Development This includes the analysis and coordination of textual materials; constant review of current literature in the field, some of which are selected for the college library collection, the preparation of selective, descriptive materials such as outlines and syllabi; conferring with other faculty and administration on curricular problems; and, the attendance and participation in inter and intra-college conferences and advisory committees.

  • Design Development An interim step in the design process. Design Development documents consist of plans, elevations, and other drawings and outline specifications. These documents will fix and illustrate the size and character of the entire project in its essentials as to kinds of materials, type of structure, grade elevations, sidewalks, utilities, roads, parking areas, mechanical and electrical systems, and such other work as may be required.

  • Program Development NWESD agrees that priority in the development of new applications services by XXXXX shall be in accordance with the expressed direction of the XXXXX Board of Directors operating under their bylaws.

  • Project Development a. Collaborate with COUNTY and project clients to identify requirements and develop a project Scope Statement.

  • Development Work Do, or cause to be done, such development and other work as may be reasonably necessary to protect from diminution and production capacity of the Mortgaged Property and each producing well thereon.

  • Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.

  • Project Planning GOVERNMENTAL APPROVALS; ENVIRONMENTAL COMPLIANCE; PUBLIC INFORMATION 30 4.1 Planning and Engineering Activities 30 4.2 Site Conditions 30 4.3 Governmental Approvals 30 4.4 Environmental Compliance 34 4.5 Community Outreach and Public Information 35

  • Information Systems Acquisition Development and Maintenance Security of System Files. To protect City Information Processing Systems and system files containing information, Service Provider will ensure that access to source code is restricted to authorized users whose specific job function necessitates such access.

  • Design Development Phase INDICATE IN STATEMENT OF WORK “NOT APPLICABLE” IF SECTION IS NOT APPLICABLE

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