High-Level Design – Architecture Sample Clauses

High-Level Design – Architecture. ‌ In order to guide the design of an ensemble-based system from high-level strategic goals, require- ments and patterns (described by SOTA) to their low-level realization in terms of system architecture (components and ensembles) we use the Invariant Refinement Method (IRM) [KBP+13b]. The main idea of IRM is to capture the high-level system goals and requirements in terms of in- teraction invariants. In compliance to SOTA’s notion of “striving to achieve”, invariants describe the desired state of the system-to-be at every time instant. In general, invariants are to be maintained by the coordination of the different system components. At the design stage, by component we refer to a participant or actor of the system-to-be. A special type of invariant, called assumption, describes a condition that is expected to hold about the environment; an assumption is not intended to be main- tained explicitly by the system-to-be. As a design decision, identified top-level invariants are decomposed into more concrete sub- invariants forming a decomposition graph (Figure 7). The decomposition is essentially a refinement, where the composition of the children exhibits all the behavior expected from the parent and (poten- tially) some more. By this decomposition, we strive to get to the level of abstraction where the (leaf) invariants represent detailed design of the particular system constituents components, component pro- cesses, and ensembles. Two special types of invariants, namely the process invariants (denoted by “P”) and exchange invariants (denoted by “X”), are used to model the low-level component computation (processes) and interaction (ensembles), respectively. A possible system-level graph corresponding to the simplified e-Mobility scenario is depicted in Figure 7. In this case, the IRM design mainly captures the necessity to keep the vehicles plan updated (invariant (5)) and to check whether the current plan remains feasible with respect to measured battery level (invariant (6)). The identified leaf invariants are easily mappable to component activities, which are further formally captured by SCEL or SCLP.
Sample 1
AutoNDA by SimpleDocs

Related to High-Level Design – Architecture

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

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

  • Design Development Phase Services 3.3.1 Based on the Owner’s approval of the Schematic Design Documents, and on the Owner’s authorization of any adjustments in the Project requirements and the budget for the Cost of the Work, the Architect shall prepare Design Development Documents for the Owner’s approval. The Design Development Documents shall illustrate and describe the development of the approved Schematic Design Documents and shall consist of drawings and other documents including plans, sections, elevations, typical construction details, and diagrammatic layouts of building systems to fix and describe the size and character of the Project as to architectural, structural, mechanical and electrical systems, and other appropriate elements. The Design Development Documents shall also include outline specifications that identify major materials and systems and establish, in general, their quality levels.

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

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

  • 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 Development Phase INDICATE IN STATEMENT OF WORK “NOT APPLICABLE” IF SECTION IS NOT APPLICABLE

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

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

  • SCOPE OF ARCHITECT’S BASIC SERVICES 3.1 The Architect’s Basic Services consist of those described in this Article 3 and include usual and customary structural, mechanical, and electrical engineering services. Services not set forth in this Article 3 are Supplemental or Additional Services.

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