Architecture Requirements Clause Samples
The Architecture Requirements clause defines the specific standards, guidelines, and criteria that the architectural design and construction of a project must meet. It typically outlines the required codes, performance specifications, and design parameters that the architect or contractor must follow, such as compliance with local building regulations, sustainability targets, or accessibility standards. By clearly establishing these requirements, the clause ensures that the final structure meets the client's expectations and legal obligations, thereby reducing the risk of non-compliance and costly redesigns.
Architecture Requirements. Based on RAGE´s Description of Action the following basic requirements have been identified: The architecture and integration points should be as simple as possible Avoiding platform and hardware dependencies as much as possible Maximum portability between game engines Maximum portability between programming languages Consistent coding style and documentation within each asset Minimum dependencies on external software frameworks Conformance with (subsets of) existing standards in order to minimise overheads
Architecture Requirements. All devices using TCP/IP protocols shall use the common Boeing-provisioned infrastructure through use of either the common Boeing Enterprise Network (BEN) or a private (isolated, standalone) network. If Seller systems/devices architecture requires the use of real-time protocols (such as Process Field Net or PROFINET) then they shall be integrated into existing network infrastructure if one already exists in the location they are implemented in. If a real-time protocol enabled network does not currently exist, the Seller systems/devices must be implemented in such a way that any following systems/devices with the same requirements can use the same common wireless network infrastructure in that location.
1.5.1 Whenever architecturally feasible, Seller systems/devices shall utilize the Boeing Enterprise Network (BEN) for all networking needs. • Seller systems/devices shall utilize only TCP/IP protocols. • Seller systems/devices shall comply with all Boeing security standards (see PRO 2227). • Seller systems/devices should utilize Dynamic Host Configuration Protocol (DHCP) rather than static IP addresses.
1.5.2 If it is not architecturally feasible for Seller systems/devices to utilize the BEN for networking needs, then Seller shall utilize the common Boeing- provisioned infrastructure for all networking needs. • Seller systems/devices shall utilize only TCP/IP protocols. • Seller systems/devices shall utilize Boeing-provisioned isolated private Virtual Local Area Network (VLAN). • Seller systems/devices should use Dynamic Host Configuration Protocol (DHCP) rather than static IP addresses. 1.
Architecture Requirements. [*****] [*****] CERTAIN PORTIONS DENOTED WITH AN ASTERISK HAVE BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION. CONFIDENTIAL TREATMENT HAS BEEN REQUESTED WITH RESPECT TO THE OMITTED PORTIONS. GM CONFIDENTIAL Included in Exhibit B of Data License Agreement [*****]
Architecture Requirements