Software Development Plan Sample Clauses

Software Development Plan. The Contractor shall provide a Software Development Plan in accordance with normally accepted commercial practice. The plan shall be delivered in final at the Kick-Off Meeting.
AutoNDA by SimpleDocs
Software Development Plan. The Contractor shall provide a Software Deployment Plan (SDP) in accordance with paragraph 3.11.1.5 of this SOW. The S/W development shall be managed in accordance with the SDP through delivery of all three functionality releases.
Software Development Plan. The Contractor shall provide a Software Development Plan (SDP) (CDRL H002). The SDP shall describe how the Contractor will align their software engineering processes to the Government’s processes. Specific areas to address in the SDP include:
Software Development Plan. (a) As part of the proposal, offerors shall submit an SDP that, at a minimum, addresses the requirements of Section C of the solicitation. The SDP shall not be subject to the technical proposal page limitation of the solicitation.
Software Development Plan. Objective The Software Development Plan (SDP) establishes the plan for developing the Computer Software Configuration Items (CSCIs) for the BATMAV System. Governing Documentation MIL-STD-498 Software Development and Documentation QSP 7.3.7 Control of Design and Development Changes
Software Development Plan. The Contractor shall provide a Software Development Plan (SDP) in accordance with paragraph 3.7.1.5 of this SOW. The S/W development shall be managed in accordance with the SDP through delivery of [***]. The Contractor shall support the integration and testing of the satellite chipset into the UE and the S-BSS. Use or disclosure of the data contained on this sheet is subject to the restriction on the title page. TerreStar Satellite Chipset SOW

Related to Software Development Plan

  • Initial Development Plan Not later than the Effective Date, Licensee shall have provided Merck with an initial Development plan for the Licensed Product in the Field in the Territory, which shall be incorporated as part of this Agreement as Attachment 3.02(a) (as may be amended in accordance with this Agreement, the “Development Plan”). **CERTAIN INFORMATION IN THIS EXHIBIT HAS BEEN OMITTED AND WILL BE FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION PURSUANT TO A CONFIDENTIAL TREATMENT REQUEST.

  • Development Plans 4.3.1 For each Licensed Indication and corresponding Licensed Product in the Field, Licensee will prepare and deliver to Licensor a development plan and budget (each a “Development Plan”). The initial Development Plans for each Licensed Indication will be delivered within […***…] after the Grant Date for such Licensed Indication.

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Contract Area, including its abandonment.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Commercialization Plan On a Product by Product basis, not later than sixty (60) days after the filing of the first application for Regulatory Approval of a Product in the Copromotion Territory, the MSC shall prepare and approve a rolling multiyear (not less than three (3) years) plan for Commercializing such Product in the Copromotion Territory (the "Copromotion Territory Commercialization Plan"), which plan includes a comprehensive market development, marketing, sales, supply and distribution strategy for such Product in the Copromotion Territory. The Copromotion Territory Commercialization Plan shall be updated by the MSC at least once each calendar year such that it addresses no less than the three (3) upcoming years. Not later than thirty (30) days after the filing of the first application for Regulatory Approval of a Product in the Copromotion Territory and thereafter on or before September 30 of each calendar year, the MSC shall prepare an annual commercialization plan and budget (the "Annual Commercialization Plan and Budget"), which plan is based on the then current Copromotion Territory Commercialization Plan and includes a comprehensive market development, marketing, sales, supply and distribution strategy, including an overall budget for anticipated marketing, promotion and sales efforts in the upcoming calendar year (the first such Annual Development Plan and Budget shall cover the remainder of the calendar year in which such Product is anticipated to be approved plus the first full calendar year thereafter). The Annual Commercialization Plan and Budget will specify which Target Markets and distribution channels each Party shall devote its respective Promotion efforts towards, the personnel and other resources to be devoted by each Party to such efforts, the number and positioning of Details to be performed by each Party, as well as market and sales forecasts and related operating expenses, for the Product in each country of the Copromotion Territory, and budgets for projected Pre-Marketing Expenses, Sales and Marketing Expenses and Post-Approval Research and Regulatory Expenses. In preparing and updating the Copromotion Territory Commercialization Plan and each Annual Commercialization Plan and Budget, the MSC will take into consideration factors such as market conditions, regulatory issues and competition.

  • Commercialization Plans As soon as practicable after formation of the JCC (following Acucela’s exercise of an Opt-In Right under Section 3.1), the JCC shall prepare and approve the initial Commercialization Plan for Commercialization of the Licensed Product for the Initial Indication in the Initial Formulation (and, if applicable, any New Formulation or Other Indication Product) in the Territory. The Parties shall use Commercially Reasonable Efforts to ensure that such initial Commercialization Plan for Commercialization of the Licensed Product for the Initial Indication in the Initial Formulation is consistent with the general Commercialization Plan outline set forth in Exhibit C attached hereto and incorporated herein (the “General Commercialization Plan Outline”). The JCC shall prepare and approve a separate Commercialization Plan for Commercialization of Licensed Product for the Initial Indication in the Initial Formulation in the Territory and for Commercialization of each Other Indication Product and New Formulation (if any) in the Territory, and shall update and amend each Commercialization Plan not less than annually or more frequently as needed to take into account changed circumstances or completion, commencement or cessation of Commercialization activities not contemplated by the then-current Commercialization Plan. Amendments and revisions to the Commercialization Plan shall be reviewed and discussed, in advance, by the JCC, and Otsuka agrees to consider proposals and suggestions made by Acucela regarding amendments and revisions to the Commercialization Plan. Any amendment or revision to the Commercialization Plan that provides for an increase or decrease in the number of FTEs for any Phase 3b Clinical Trials or Post-Approval Studies as compared to the previous version of the Commercialization Plan, or that provides for addition or discontinuation of tasks or activities as compared to the previous version of the Commercialization Plan, or that moves forward the timetable for activities reflected in the Commercialization Plan, shall provide for a reasonable ramp-up or wind-down period, as applicable, to accommodate a smooth and orderly transition of Commercialization activities to the amended or revised Commercialization Plan. Each Commercialization Plan shall identify the goals of Commercialization contemplated thereunder and shall address Commercialization (including Co-Promotion) activities related to the Licensed Product (including, if applicable, any Other Indication Product), including:

  • 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").

  • Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times.

  • Development Program A. Development activities to be undertaken (Please break activities into subunits with the date of completion of major milestones)

  • Statement of Work The Contractor shall provide the services and staff, and otherwise do all things necessary for or incidental to the performance of work, as set forth below:

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