Architecture Design Sample Clauses

Architecture Design. Work Package WP 3.1, Architecture Design Lead Author (Org) Xxxxxx Xxxxxxxxx (Do IT Systems) & Xxxxx Xxxx (UCit) Contributing Author(s) (Org) Xxxxxxx Xxxxxxxxxxx (UCit), Xxxxxxxx Xxxxxxxx (UCit), Xxxxxx Xxxxxxxx (UCit), Xxxx Xxxxxx (HPCNow!), Xxxxxx Xxxxxxxx (BSC), Xxxxxx Xxxx (UCit) Reviewed by Xxx Xxxxxxxxx (HPCNow!), Xxxx Xxxxxx (HPCNow!), Xxxxxxx Xxxxxxxx (UCit), Xxxxxxxx Xxxxxxx (UCit) Approved by Management Board Due Date 31.08.2021 Date 03.09.2021 Version V4.0 Dissemination Level X PU: Public PP: Restricted to other program participants (including the Commission) RE: Restricted to a group specified by the consortium (including the Commission) CO: Confidential, only for members of the consortium (including the Commission) Versioning and contribution history Version Date Author Notes
Sample 1
AutoNDA by SimpleDocs
Architecture Design. Task – Frontend Architecture Outline of the logical and physical structure of the Web-Application’s user-side interfaces. Task – Backend Architecture Outline of the logical and physical structure of the Web-Application’s backend administrative interfaces. Task – Database Architecture Data model phase in which the tables, fields, indexes, and relationships of the database are established.
Sample 1
Architecture Design. This section is targeted to to describe the modelling methodology applicable to the three phases of an eDIANA platform architecture design, namely, the Application Architecture Design phase, the Platform Architecture Design phase and the System Allocation phase. The models involved in each of these phases will be explained in terms of views, modelling languages, etc. and a set of modelling guidelines and constraints will be given. In order to develop a completely coherent model-driven development framework, it is necessary to constrain the modelling languages to a subset in order to enable the reusability of the model transformation engines, e.g. to connect system designs with analysis tools. Lastly, eDIANA specific components will be addressed in the methodology framework in order to ease the designers’ job to use this modelling methodology.
Sample 1
Architecture Design. This Task investigated emerging architectures in European projects as well as novel extensions to those architectures. The design of the overall IoT Lab architecture also considers the requirements coming from Task 1.1. WP1 coordinates and aligns the overall strategy and facilitates activities for the overall project.
Sample 1

Related to Architecture Design

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

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

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

  • Technology Upgrades Notwithstanding any other provision of this Agreement, Verizon shall have the right to deploy, upgrade, migrate and maintain its network at its discretion. The Parties acknowledge that Verizon, at its election, may deploy fiber throughout its network and that such fiber deployment may inhibit or facilitate PNG’s ability to provide service using certain technologies. Nothing in this Agreement shall limit Verizon's ability to modify its network through the incorporation of new equipment or software or otherwise. PNG shall be solely responsible for the cost and activities associated with accommodating such changes in its own network.

  • Creative Work The Executive agrees that all creative work and work product, including but not limited to all technology, business management tools, processes, software, patents, trademarks, and copyrights developed by the Executive during the term of this Agreement, regardless of when or where such work or work product was produced, constitutes work made for hire, all rights of which are owned by the Employer. The Executive hereby assigns to the Employer all rights, title, and interest, whether by way of copyrights, trade secret, trademark, patent, or otherwise, in all such work or work product, regardless of whether the same is subject to protection by patent, trademark, or copyright laws.

  • Design At no cost to SCE, Seller shall be responsible for:

  • Programming Phase 2.2.1.2. Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK Firms and/or individuals that assisted in the development or drafting of the specifications, requirements, statements of work, or solicitation documents contained herein are excluded from competing for this solicitation. This shall not be applicable to firms and/or individuals providing responses to a publicly posted Request for Information (RFI) associated with a solicitation.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

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