Overall Architecture Sample Clauses

Overall Architecture. Due to the nature of the XXX and its integration within the many different CMS and aggregator systems throughout the Europeana Inside project there can be no one overall ‘system architecture’ in the traditional sense. Rather the XXX will be made up of a set of modular components that may or may not be implemented as standalone services in the Europeana Inside ecosystem rather than as a single monolithic whole. Some of these modules will actually come from existing functionality within CMS systems, others will be developed as part of this project and can be incorporated directly into or interfaced with the CMS or aggregation systems themselves and others might be existing third party components which can be used ‘as is’ or wrapped in a service later with appropriate API calls. This lack of an overall architecture means that the XXX must be specified by the set of high level, functional and non-functional requirements that have been determined by previous stages of the project. In addition the interfaces and interactions between the XXX components and with external tools such as existing CMS components, vocabulary management systems, Europeana itself, etc. will make up a key part of the overall architecture. Figure 1 is a representation of the overall architecture and environment in which the XXX will operate. Some of the functional requirements listed in D2.4 are to be provided by the CMS itself, while other parts are provided by external, shared modules. The connections between the components are of course as important as the individual modules themselves as they represent the interfaces presented by the different modules and the communications that are sent via these interfaces. The figure depicts the overall architecture as consisting of an XXX ‘Core’ with additional modules as external to the XXX core. However, it is expected that many of the modules may actually be implemented within the core itself. They are simply presented this way in order to make the figure more easily understood. Equally it is expected that the aggregator and possibly even Europeana itself will also incorporate the XXX but again this duplication has been left out of the figure for simplification purposes. Figure 1: Representation of the overall XXX architecture and its communication with the CMS and aggregator / Europeana
Sample 1
AutoNDA by SimpleDocs
Overall Architecture. The high-level Go-Lab architecture, illustrated in Fig. 1, consists of two main components with a graphical user interface (GUI), namely the lab repository and the ILS platform. Both are supported by components for user management and tracking user activities for learning analytics and recommendation. By splitting up the portal functionality in this way, each component serves a very different purpose and we aim to satisfy the requirements and design principles stated above. The components have well-specified interfaces and protocols, which allow interchangeability (e.g., the ILS platform could use another repository that implements the same specification of the Publisher & Instantiator interface) and other third-party platforms can make use of each component separately Figure 1: The architecture of the Go-Lab Portal. enabling wider adoption of Go-Lab technology. The next section elaborates on the components of the architecture.‌
Sample 1
Overall Architecture. The overall architecture of the gCore Framework is depicted in Figure 5. Being a software framework, it mainly consists of a series of packages clustering classes implementing the facilities described in the rest of the Section.
Sample 1
Overall Architecture. The overall architecture of the gCube Infrastructure Enabling Services is depicted in Figure 6. It consists of six cooperating subsystems whose role, functions and relations are briefly described in the rest of this section.
Sample 1
Overall Architecture. The Architecture of the Information Organization services is articulated over three fundamental layers, as illustrated in Figure 27, Base Layer, Storage Management Layer, Content Management Layer, Metadata and Annotation Management. Additional information about these layers and their functionality is provided below, while the technical details related to how to interact with the services at each layer are provided in the next sections.
Sample 1
Overall Architecture. ‌ Figure 13: Integration design diagram for the DURAARK framework
Sample 1
Overall Architecture 
Sample 1
AutoNDA by SimpleDocs

Related to Overall 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.

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

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

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

  • Engineering Forest Service completed survey and design for Specified Roads prior to timber sale advertisement, unless otherwise shown in A8 or Purchaser survey and design are specified in A7. On those roads for which Forest Service completes the design during the contract, the design quantities shall be used as the basis for revising estimated costs stated in the Schedule of Items and adjusting Timber Sale Account. Forest Service engineering shall be completed according to the schedule in A8. Should Forest Service be unable to perform the designated survey and design by the completion date or other agreed to time, upon written agreement, Purchaser shall assume responsibility for such work. In such event, Contracting Officer shall revise:

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

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

  • Architect/Engineer (A/E) means a person registered as an architect pursuant to Tex. Occ. Code Xxx., Chapter 1051, as a landscape architect pursuant to Tex. Occ. Code Xxx., Chapter 1052, a person licensed as a professional engineer pursuant to Tex. Occ. Code Xxx., Chapter 1001 and/or a firm employed by Owner or a design-build contractor to provide professional architectural or engineering services and to exercise overall responsibility for the design of a Project or a significant portion thereof, and to perform the contract administration responsibilities set forth in the Contract.

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

  • Project Management Project Management Institute (PMI) certified project manager executing any or all of the following: • Development of Project Charter • Development of project plan and schedule • Coordination and scheduling of project activities across customer and functional areas • Consultation on operational and infrastructure requirements, standards and configurations • Facilitate project status meetings • Timely project status reporting • Address project issues with functional areas and management • Escalation of significant issues to customers and executive management • Manage project scope and deliverable requirements • Document changes to project scope and schedule • Facilitate and document project closeout

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