Related Project Requirements Sample Clauses

Related Project Requirements. The AUTOSAR gateway is mentioned in the following requirement: DOW#0111: The SWC Synthesis ( FDA-IL ) shall be modelled in MAW-AR Gateway plugin [4].
AutoNDA by SimpleDocs
Related Project Requirements. The Timing Analysis plugin is mentioned in the following requirement: DOW#0110: The Timing analysis (DL) shall be modelled in MAW-Timing plugin [4].
Related Project Requirements. DOW#0112: The Simulink import-export (FAA, FDA ) shall be modelled in MAW-Simulink plugin.
Related Project Requirements. UOH#0003: The HiP-HOPS analysis tool should support any ISO 26262 or related concepts (such as ASIL decomposition) necessary to allow ISO-compatible dependability analysis of EAST-ADL models. UOH#0004: EAST-ADL and HiP-HOPS should be able to intercommunicate by means of model transformations provided by a dependability plugin in the MAENAD Analysis Workbench (MAW). Furthermore it should be possible to import or store the results from HiP-HOPS in the Workbench and/or the EAST-ADL model, which will require establishing some form of (perhaps XML based) interchange format.
Related Project Requirements. VTEC#UC006: A model of the validator with timing, dependability and cost annotations as well as design space, variability and take rate annotations is defined and exported to EAXML. An optimization tool computes the optimal design for the defined product line. The resulting optimized model is recorded in the model (design space variability removed) and exported in the EAXML file. UOH#0002: The EAST-ADL error model should fully support automatic optimisation, e.g. through rules that specify a 1:1 mapping from nominal to error models. UOH#0005: To support multi-objective optimisation, there must be a standardised way of passing design candidates to analysis tools/plugins and receiving results in a given format.
Related Project Requirements. This analysis support addresses the following requirements:  DOW#0012 O2-2: Behavioral Simulation of EAST-ADL models  DOW#0017 O4-2: Evaluation of dependability & performance analyses
Related Project Requirements. This analysis support addresses the following requirements:  DOW#0017 O4-2: Evaluation of dependability & performance analyses  VTEC#UC006 Model optimization
AutoNDA by SimpleDocs
Related Project Requirements. This variability resolution plugin addresses the following requirements:  4SG#0039: Variability of EV architectures  TUB#0001 Variability Validation  VTEC#UC006 Model optimization
Related Project Requirements. MODELISAR FMU import is not explicitly mentioned in the requirements, although it relates to behavioural simulation in general.  DOW#0012 O2-2: Behavioural Simulation of EAST-ADL models  4SG#0003: Perform behavioural Simulation of EAST-ADL models according to performance evaluation standards  4SG#0004: Perform behavioural Simulation of EAST-ADL models according to standards covering communication with infrastructures  4SG#0019: The project shall enable to perform behavioural simulation according to ISO 8715: Electric road vehicles - Road operating characteristics There are more similar requirements on behaviour simulations, see e.g. 4SG#0020, 4SG#0021, 4SG#0022, 4SG#0023, 4SG#0024, 4SG#0025, 4SG#0026

Related to Related Project Requirements

  • Project Requirements Failure to comply with the following requirements will result in a suspension of all other operations:

  • Development Requirements The exterior wall standards set forth in this section shall apply to the structures located on the Property. At least ninety percent (90%) of the combined exterior surface area of all walls, including all stories of buildings / structures, shall consist of stone, brick, painted or tinted stucco, and factory tinted (not painted) split faced concrete masonry unit or similar material approved by the Director of Planning.

  • Equipment Requirements No Equipment is provided to Customer as part of this Service.

  • Test requirements 3.1. The limits apply throughout the frequency range 30 to 1,000 MHz for measurements performed in a semi anechoic chamber or an outdoor test site.

  • Space Requirements The Construction Administrator will conduct a review of the adequacy of space allotments for maintenance of mechanical, telephone, and fire protection equipment.

  • Interface Requirements 9.3.1 BellSouth shall offer LIDB in accordance with the requirements of this subsection.

  • Additional Request Requirements In addition to the requirements of Subparagraph 22A, the request for a WA must provide:

  • TITLE VI REQUIREMENTS H-GAC in accordance with the provisions of Title VI of the Civil Rights Act of 1964 (78 Xxxx. 000, 00 X.X.X. §§ 0000x to 2000d-4) and the Regulations, hereby notifies all bidders that it will affirmatively ensure that any disadvantaged business enterprises will be afforded full and fair opportunity to submit in response to this Agreement and will not be discriminated against on the grounds of race, color, or national origin in consideration for an award.

  • DATA ESCROW REQUIREMENTS Registry Operator will engage an independent entity to act as data escrow agent (“Escrow Agent”) for the provision of data escrow services related to the Registry Agreement. The following Technical Specifications set forth in Part A, and Legal Requirements set forth in Part B, will be included in any data escrow agreement between Registry Operator and the Escrow Agent, under which ICANN must be named a third-­‐party beneficiary. In addition to the following requirements, the data escrow agreement may contain other provisions that are not contradictory or intended to subvert the required terms provided below.

  • PJM Requirements The DS Supplier acknowledges and agrees that, as a member of PJM, the Company is bound by all PJM operating instructions, policies and procedures as are currently set forth in the PJM Operating Manual, which are available through the Internet on the PJM Home Page (xxxx://xxx.xxx.xxx), as may be revised from time to time, which are needed to maintain the integrity of the PJM system. The DS Supplier acknowledges and agrees that it will cooperate with the Company so that the Company will be in compliance with all PJM Emergency Operations Procedures, which include, but are not limited to, those procedures pertaining to minimum and maximum generation Emergencies, and measures requiring involuntary Customer participation, such as supply voltage reduction or full interruption of Customer load by either manual or automatic means.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!