Platform Architecture Design phase Platform Architecture Sample Clauses

Platform Architecture Design phase Platform Architecture. Design Description The goal of this phase is to obtain first an abstract model of the platform architecture that supports the execution of the embedded application. The phase will use both existing models and new models to obtain a platform model that meets the requirements described in the platform requirements document provided as input for this phase. In order for the models to be fully eDIANA compatible, the models used and generated during this stage must follow the eDIANA modelling style described in section 5.4. Start conditions This phase will start whenever the platform requirements are available. Once this phase has ended for the first time, it will restart if the Early V&V phase detects a quality error in the platform model. Triggers System Allocation phase. Inputs Platform requirements document Platform components repository. Outputs Platform model of the system under development. Specification method and language UML2 + XXXXX (GRM, HRM, SRM and NFPs subprofiles) SystemC / pseudo code/Verilog/VHDL Tool support Papyrus, Rational Software Architect. CADENCE IUS
AutoNDA by SimpleDocs

Related to Platform Architecture Design phase Platform Architecture

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Schematic Design Phase Services § 3.2.1 The Architect shall review the program and other information furnished by the Owner, and shall review laws, codes, and regulations applicable to the Architect’s services.

  • Design Phase Services § 3.2.1 The Architect shall review the program and other information furnished by the Owner, and shall review laws, codes, and regulations applicable to the Architect’s services.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Design Professional to Design Work The Design Professional Contract requires the Design Professional to design and to prepare the Contract Documents, a copy of which shall be furnished to the Contractor upon request. The Design Professional Contract requires the Design Professional to designate a readily accessible representative (either on Site or by computer, phone or fax or otherwise) who shall have authority promptly to render decisions and to furnish information required of the Design Professional.

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

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Physical Architecture 59.2.1 CenturyLink's network architecture in any given local exchange area and/or LATA can vary markedly from another local exchange area/LATA. Using one or more of the NIMs herein, the Parties will agree to a physical architecture plan for a specific LATA, or if appropriate based on other requirements in Section 59, Local Calling Area. The physical architecture plan, as described in the Local Interconnection POI Profile, will be discussed during joint implementation planning. CLEC and CenturyLink agree to Interconnect their networks through existing and/or new Interconnection Facilities between CLEC switch(es) and CenturyLink's End Office Switch(es) and/or Tandem Switch(es). The physical architecture plan will be in accordance with Forecasting and Planning requirements in Article IV.

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

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