DoD Architecture Framework Working Group, DoD Architecture Framework Version Sample Clauses

DoD Architecture Framework Working Group, DoD Architecture Framework Version. 1.0, Deskbook, 2003 ([DoD03]) The Department of Defense (DoD) Architecture Framework (DoDAF) defines a common approach for describing, presenting and comparing DoD enterprise architectures and facilitates the uses of common principles, assumptions and terminology. The DoD Architecture Framework 1.0 was published in 2003 (and the version 1.5 in 2007), and its principal objective is to ensure that architecture descriptions can be compared and related across organizational boundaries including joint and multi-national boundaries. The purpose of the DoD Architecture Framework Version 1.0, is to provide guidance for describing architectures. It establishes data element definitions, rules, and relationships and a baseline set of products for consistent development of systems, integrated, or federated architectures. These architecture descriptions may include Families of Systems (XxXx), Systems of Systems (XxXx), and net-centric capabilities for interoperating and interacting. The DoDAF is a reference model to organize the enterprise architecture (EA) and systems architecture into complementary and consistent views. The DoDAF defines a set of products that act as mechanisms for visualizing, understanding, and assimilating the broad scope and complexities of an architecture description through graphic, tabular, or textual means. It is especially suited to large systems with complex integration and interoperability challenges, and is apparently unique in its use of "operational views" detailing the external customer's operating domain in which the developing system will operate. While it is clearly aimed at military systems, DoDAF has broad applicability across the private, public and voluntary sectors around the world, and represents only one of a large number of systems architecture frameworks
Sample 1
AutoNDA by SimpleDocs

Related to DoD Architecture Framework Working Group, DoD Architecture Framework Version

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

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

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

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Construction Phase Services 3.1.1 – Basic Construction Services

  • Project Management Plan 1 3.4.1 Developer is responsible for all quality assurance and quality control 2 activities necessary to manage the Work, including the Utility Adjustment Work.

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least thirty (30) days written notice to the SLDC and GUVNL, of the date on which it intends to synchronize the Power Project to the Grid System.

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

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