Component Breakdown of Functional Architecture Sample Clauses

Component Breakdown of Functional Architecture. This section discusses the functional architecture at the software component level. The discussion explains what parts of the architecture will run within same processes and which will be executed in different processes or requires own threads to execute tasks in parallel. Main interfaces that enable communication and data exchange between functional components are shown to illustrate the flow of data and control between the components of the architecture and to further highlight which components will gain access to data handled by the platform. Interfaces Notation provides requires Service Platform «Background Process» provisionListener User Interfaces «Foreground Activity» provides services bundleListener seekSender seeks services provides bundles sends bundles provisionLocally bundleListener announces services provideService contextListener receives requests notifies Context provisionListener updateAttributes requestResponseaskNotification notifiesContext contextListener askNetworkService provideNetworkService MusicProvider Application Specific Services «Foreground or Background Activity» ConnectionManager Opportunistic Stack «Background Thread» Connections ContextManager MultimodalManager EnvironmentManager LocationManager SecurityManager IncentiveManager TrustManager IdentityManager ChatRoom NeighborDiscovery PlatformSecurity ContextAndEnergyAwareness ServiceMappings OpportunisticOSN SocialManager TemporalRelevanceManager ContentInterestManager FriendshipManager Figure 10: Functional breakdown of SCAMPI components. On the left in Figure 10, the opportunistic communication stack runs in its own thread in the same background process as the SCAMPI platform. The rationale is that the platform must be able to execute at all times and the opportunistic stack must be able to manage contacts and send and receive messages in parallel with the operation of the SCAMPI service platform. The user interface runs as a foreground activity, meaning that a process for executing it is started when user interacts with the platform. The communication between the foreground activity and the platform components takes place through inter process communications (IPC) interfaces. The rationale for separating user interface to separate process is that the platform can independently execute in the background even when user interface does not exist. The execution of the background service can be of course interrupted if user so explicitly requires. Moreover, using simple socket-b...
Sample 1
AutoNDA by SimpleDocs

Related to Component Breakdown of Functional 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.

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

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

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Attachment A, Scope of Services The scope of services is amended as follows:

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

  • Disturbance Analysis Data Exchange The Parties will cooperate with one another and the NYISO in the analysis of disturbances to either the Large Generating Facility or the New York State Transmission System by gathering and providing access to any information relating to any disturbance, including information from disturbance recording equipment, protective relay targets, breaker operations and sequence of events records, and any disturbance information required by Good Utility Practice.

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

  • Drug-Free Workplace Certification As required by Executive Order No. 90-5 dated April 12, 1990, issued by the Governor of Indiana, the Contractor hereby covenants and agrees to make a good faith effort to provide and maintain a drug-free workplace. The Contractor will give written notice to the State within ten (10) days after receiving actual notice that the Contractor, or an employee of the Contractor in the State of Indiana, has been convicted of a criminal drug violation occurring in the workplace. False certification or violation of this certification may result in sanctions including, but not limited to, suspension of contract payments, termination of this Contract and/or debarment of contracting opportunities with the State for up to three (3) years. In addition to the provisions of the above paragraph, if the total amount set forth in this Contract is in excess of $25,000.00, the Contractor certifies and agrees that it will provide a drug-free workplace by:

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

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