Product Requirements Document definition

Product Requirements Document or “PRD” shall mean the detailed device requirements for the AEROSURF System and assumptions and data supplied by Discovery Labs to Battelle, and which is included in the Project Plan.
Product Requirements Document or "PRD" means the specifications and other requirements for Instruments, as set forth in Exhibit 7.
Product Requirements Document or “PRD” shall mean the technical requirements provided by XPLORE for the Deliverables, as set forth in Exhibit C.

Examples of Product Requirements Document in a sentence

  • The Instrument requirements, including without limitation the specifications, are set forth in the Product Requirements Document.

  • Interplay shall use all commercially reasonable efforts to ensure that each PC Partner Product runs in the various hardware and software configurations in which the Partner Product is designed to run, and with all peripherals with which the PC Partner Product is designed to work, in a manner that is consistent with: (a) the Partner Product Requirements Document, (b) the Partner Product Concept and Description Document, and (c) the Partner Product's documentation prepared by Interplay.

  • If the Supervisory Board determines that the changes are sufficiently minor that they can be implemented under this Ultrio Addendum, then the parties shall implement the process more particularly described in Section 3.3 above, and the Supervisory Board may approve a new Ultrio Development Program, consisting of a new modified Product Requirements Document, Software Requirements Specifications, Technical Plan, Resource Plan and Budget, for the purpose of developing such changes.

  • The features the first episode of each of the four Titles must posses are more particularly described in the Product Requirements Document ("PRD") set forth in Attachment A.

  • As used herein, “Reliability Requirements” shall mean the document attached as Exhibit C, approved by both Parties, setting forth the reliability requirements necessary to meet the Product Requirements Document.

  • Products must conform to the following specifications (including any subsequent revisions, as mutually agreed to between the parties), which are hereby incorporated by reference, and sold exclusively to IBM including providing supporting Services: • Brocade 16Gb Fibre Channel Switch Module Product Requirements Document (“PRD”), filename “Brocade 16Gb ScSe for Beacon PRD 1.0.doc”, version 1.0 and any subsequent versions.

  • At such time as the parties (or, if applicable, the Supervisory Board) shall have accepted a modified Ultrio Development Program incorporating a Material Modification, or any portion thereof, the parties shall evidence such agreement by initialing the revised Product Requirements Document, Software Requirements Specification, Technical Plan, Resource Plan or Budget, as applicable.

  • If the Supervisory Board determines that the changes are sufficiently minor that they can be implemented under this West Nile Virus Addendum, then the parties shall implement the process more particularly described in Section 3.3 above, and the Supervisory Board may approve a new WNV Development Program, consisting of a new modified Product Requirements Document, Software Requirements Specifications, Technical Plan, Resource Plan and Budget, for the purpose of developing such changes.

  • Unless Chiron terminates the eSAS 2 Development Program under Section 8.3 below or elects to continue the eSAS 2 Development Program unaffected without such Material Modification under Section 3.3.2, promptly upon completion of the review and analysis under Section 3.3.2, Chiron shall complete and deliver to Gen-Probe revisions to the Product Requirements Document, Software Requirements Specification, Technical Plan, Resource Plan or Budget, as applicable, responsive to the request.

  • Exhibit A - Content Provider Deliverables Exhibit B - T-Mobile Deliverables Exhibit C - Compensation and Payment Exhibit D - T-Mobile Java Platform Applications Product Requirements Document ("Java PRD") Exhibit E - T-Mobile Java Applications Submission Document -------------------------------------------------------------------------------- EACH PARTY'S SIGNATURE BELOW ACKNOWLEDGES THAT SUCH PARTY HAS READ AND UNDERSTANDS EACH OF THE TERMS AND CONDITIONS OF THIS AGREEMENT AND AGREES TO BE BOUND BY THEM.


More Definitions of Product Requirements Document

Product Requirements Document. (or "PRD") means the specifications for the Ultrio Assay Product, and includes as a component thereof the Software Requirements Specifications. The initial Product Requirements Document is described in the Binder, under the heading "Product Requirements Document (PRD, Revision A, dated May 16, 2001)," and may be amended from time to time under the provisions of Section 3 below.
Product Requirements Document. (or “PRD”) means the specifications for each module within the eSAS 2 Instrument system, each of which includes as a component thereof the applicable Software Requirements Specifications. The initial Product Requirements Document for two of the five (5) modules described in Schedule 1.4 are attached hereto as Schedule 1.12-A and Schedule 1.12-B. The PRD for each of the remaining three (3) modules described in Schedule 1.4 will be developed, and each PRD after agreement between the parties may be amended from time to time in accordance with the provisions of Section 3 below. Each PRD, as it may be developed and/or amended from time to time, shall be retained in the Binder under the heading “Product Requirements Document (PRD, Revision , dated xx/xx/xx).”
Product Requirements Document. (As defined in Lani▇▇'▇ ▇▇▇duct To Market Handbook ("The PTM Handbook") incorporated herein by reference).
Product Requirements Document means the document(s) attached hereto as Exhibit 1 setting forth, at a minimum, a description of the Product and the timetable for delivery of the Product.