Application Architecture Sample Clauses

Application Architecture. OLIN's application architecture shall at all times be developed and maintained by XXXX and shall be OLIN's responsibility. OLIN's application architecture shall govern the technological direction and specifications developed by XXXX in consultation with ARCH.
Sample 1Sample 2
AutoNDA by SimpleDocs
Application Architecture. As we continued, we considered the architecture of the application that surrounds the IA model. Doing so allowed us to compare how each IA model interfaces with the users and the database. Each IA model has a unique interface when considering the interactions of the individual centers and the ALTCDSS. The application architecture that surrounds each model can require more emphasis in data services on the individual healthcare centers or on the lead center depending on model. Furthermore, when concerned about data integrity, we could pinpoint weaknesses and strengths in the data conversion processes through this comparison. An application would need to be created to interact with the ALTCDSS. There are four main application layers that would exist, regardless of IA model: v Presentation Interface- this is the layer that customers most often interact with. In this case, it would be the front-end of the ALTCDSS.
Sample 1
Application Architecture provides a blueprint for the individual applications to be deployed, their interactions, and their relationships to the core business processes of the organization. (TOGAF 9.1) In this segment, we identified the data and integration component of the ALTCDSS, studied several types of information architecture models, and conducted analysis to weigh the pros and cons of each as they applied to the ALTCDSS. Then, we considered the application architecture as it relates to each model to determine who and/or what would interface with the system and their complexities within.
Sample 1
Application Architecture o The offeror must describe any compatibility or interoperability with desktop productivity tools (Microsoft Office, etc.) o The offeror must describe the Application Programming Interface (API) if available. o The offeror must describe the Application Server environment required for the proposed solution. o Software sold or licensed to CU to be installed, maintained, or run by CU personnel must not have a dependency on Oracle Java (JDK, SE, EE, or ME) unless licensing and maintenance costs for Oracle Java, for the life of the product, are included in the purchase price. Preference for software based on Java technology will be given to vendors utilizing the OpenJDK framework. o Offeror must include in their proposal recommended architectural designs for resilience. ● CU Hosted or Managed Database Services o Solutions requiring CU support must be compatible with one of the following currently supported database technologies: Oracle or MS SQL. Other technologies will be evaluated individually. o The offeror must provide technical documentation regarding configuration and installation, including backup/maintenance scripts for the proposed solution. ● CU Hosted or Managed Operating Systems Versions and Releases - minimums o Solutions must be: ▪ For Linux-based on-premise systems: ● After 2022/02/02 Oracle Linux 8 (OL8) ▪ For Windows-based on-premise systems: ● Windows Server 2019 or above is acceptable ● On and after 2024/02/02 Windows Server 2022 is required (preferred now) ▪ Any other systems must be currently supported with the latest security patches installed and maintained. Other environments will be evaluated individually. o Please note that Oracle Enterprise Linux is a variant of RedHat Enterprise Linux (RHEL) ● Accessibility o Offerors must provide an Accessibility Conformance Report (ACR) for their solution. ▪ The ACR must be based on a Voluntary Product Accessibility Template® (VPAT®) version 2.1 or higher, provided by the Industry Technology Industry Council (ITIC). ▪ The ACR must include conformance to Web Content Accessibility Guidelines (WCAG) version 2.0 levels A and AA. ▪ The ACR must be completed according to the instructions. ▪ If the solution has multiple forms (i.e., web version, desktop version, mobile app, support documentation), then either the provided ACR clearly covers the results of each form or an ACR for each form is provided. o Offerors must provide a supplemental accessibility statement including the following: ▪ Confirm the off...
Sample 1
Application Architecture. [Graphics] System description: The system is generally divided into three parts: Online Shopping Mall website subsystem, background management system and system support. · Online Shopping Mall website subsystem
Sample 1
Application Architecture. Let’s consider an example of Web 2.0 application depicted in Figure 3-7. This is a typical 3-tier application consisting of three sets of components – the set of Web Servers, the set of Application Servers, and a set of Database Servers. Web Servers need to communicate with the external clients and with the Application Servers but not with the Database Servers and not between themselves. Application Servers need to communicate with the Web Servers and with the Database Servers but not with the external clients and not between themselves. Database Servers need to communicate between themselves and with the Application Servers but not with the Web Servers and not with the external clients. Additional requirements must be specified regarding the quality of the allowed connections, in terms of bandwidth, latency, packet loss, etc. Security and other service requirements, e.g. monitoring, traffic shaping, caching, can be specified by stating which of the allowed connections should be served by which types of service appliances. In traditional DCs, deploying the application described in Figure 2-1 usually requires interaction with the network administrator who will create network design, pre-provision the required subnets and services and let the application owner know where to deploy the application components and how to configure them over the network. Some of this work can be automated but the application owner is still exposed to network related aspects such as subnets, ports, gateways, IP addresses, etc. In VDC use case, the users are given an isolated slice of the networking underlying infrastructure where they can create and configure diverse networking designs suitable to the applications at hand. In multi-tenant software cloud use case, however, the user is the application owner and prefers to be isolated from the networking design aspects, concentrating on the application architecture and functionality. For a very large subset of typical cloud applications, e.g. multi-tier web applications, MapReduce applications, application clusters, networked storage application, etc., the patterns can be pre-provisioned. Moreover, both the cloud management stack and the underlying infrastructural resources can be optimized to better suit the specific patterns when they are deployed. In this use case, the user is the application owner (who can be either the developer or the operator). The application owner is knowledgeable about the application architecture, its com...
Sample 1
Application Architecture. Decision Lens exposes our decision technology via a web service API and provides user interfaces for delivering the decision process within a rich user experience. The user interfaces consist of standard web technologies, such as HTML, Javascript, CSS, and Flash. The user interfaces communicate with the web service API over the Internet to provide functionality to the end user. The web service API, and other related services, are implemented as Java web applications. These applications are deployed in Tomcat Application Server and are exposed to the Internet through an Apache HTTP Server proxy. The proxy enforces authentication and authorization logic for all web services based on user roles and data ownership rules. All application data is stored in a MySQL database. Application data is only accessible to web service API code and Decision Lens administrators via a secure, private network. All Ordering Activity data is logically separated for data integrity and security. Hosting Infrastructure Decision Lens utilizes Amazon Web Services IaaS* to provide a stable, reliable, scalable, and secure cloud-based SaaS platform. The multi-tenant architecture of the platform allows for Ordering Activity organizations to get up and running with Decision Lens quickly and easily. Additionally, Decision Lens supports Ordering Activity-hosted, on-premises installations of the platform. Decision Lens may be hosted in a single server environment, or in a multi-tiered, clustered environment, on virtual machines or dedicated hardware. Ordering Activity-hosted installations may be deployed with a custom architecture suitable for Ordering Activity needs. Please see the Technical Services section for more information regarding Ordering Activity-hosted installations. *See Appendix A for technical documentation regarding Amazon Web Services.
Sample 1
AutoNDA by SimpleDocs

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

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

  • Application Submission Submissions of a rental application does not guarantee approval or acceptance. It does not bind us to accept the application or to sign a Lease contact. APPLICANT SCREENING CRITERIA Fair Housing Statement. Xxxxx Management is an equal housing opportunity & fair housing provider. We do not discriminate against persons on the basis of race, color, religion, national origin, sex, familial status, disability, creed, marital status, public assistance, ancestry, and sexual or affectional orientation. Identification and Application Process. Every person over 18 must give consent to be screened and provide a government issued photo ID. Social Security Number verification may be required for specific housing programs. Application Requirements. Applications must be filled out completely and accurately. Any misstatements or omissions made on your application, whether or not discovered before you move into the building, is grounds for denial of an application or termination of an existing lease. Information must be legible and verifiable. If information given on the application cannot be verified, this is a reason for rejection. Omission of information, such as an address or employer, may be grounds for rejection. Occupancy. The initial maximum number of residents in a unit is equal to two persons per bedroom unless otherwise stated in the property’s Resident Selection Plan, where applicable. Each unit is limited to no more than two (2) unrelated or four (4) related adult persons per unit. Xxxxx Management defines a related adult person as either a child, dependent, or parent of the head of household. General occupancy standards and any federal, state, or local housing ordinances will supersede this policy. Housing History. We require the name and last known telephone number of each landlord/property manager for each address you have had for the last three years. Roommate references are not acceptable. The refusal of a prior landlord to give a reference, or a negative reference, may be grounds for rejection. In the case of first-time renters, or applicants without prior rental history, this requirement may be varied subject to additional requirements of management. Eviction Filings. Unlawful detainers or evictions within the past five (5) years is a basis for denial of an application.

  • Application Process The employees wishing to enter into a job share arrangement will apply in writing to the Employer and forward a copy to the Union outlining the proposed commencement date of the job share, how the hours and days of work will be shared and how communication and continuity of work will be maintained. The Employer shall communicate a decision on a job share request in writing to the applicants. Applications to Job Sharing shall not be unreasonably denied.

  • Application Form The applicant can secure application forms from the principal's office or from the Personnel office. The application shall be filed with the appropriate administrator.

  • Application Procedure 7.4.1. Application Priority........................................ 7.4.2. [Reserved].................................................. 7.4.3. Advance Payments............................................

  • Application Procedures a) An employee applies for a listing on the system-wide registry through the employee’s Human Resources Department by completing the form in Appendix B.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

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