Sort Alphabetically
Sort by Category
|
Category: Business Enterprise Architecture
|
|
Description: The BEA is developed using a set of integrated DoDAF, products, including All Views (AV), Operational View (OV), Systems and Services View (SV), and Technical Standards View (TV) products. Together the BEA and ETP provide a blueprint and roadmap for defense business transformation.
|
|
Relationship to the DoD’s SOA Adoption: This is the enterprise architecture for the DoD Business Mission Area and, as such, describes the DoD’s business transformation goals and provides the framework for architecture federation for business systems. All military services, defense agencies, and components must federate their architectures to the BEA and their enterprise systems must be in compliance with the BEA. The BEA is furthermore considered the overarching enterprise architecture for the DoD’s business operations, characterized as the Business Mission Area (as opposed to the Warfighter Mission Area or the Intelligence Mission Area).
|
http://www.bta.mil/products/bea.html
http://www.defenselink.mil/dbt/products/2008_BEA_ETP/bea_5_0.html
|
|
Category: Business Enterprise Architecture
|
| Description: The purpose of this document is to provide guidance on how to assess and document program compliance with the Enterprise Architecture for Defense Business Systems (currently referred to as the BEA) and how to provide a corrective action plan if a program is not fully compliant. The guidance in this document complements the DoD defense business system investment review and certification processes established by section 2222 of title 10 of the United States Code.
|
|
Relationship to the DoD’s SOA Adoption: This document basically explains how military services, defense agencies, and other DoD components should comply with the BEA.
|
http://www.defenselink.mil/dbt/products/investment/BEA_5_0_Compliance_
Guidance_Final.pdf
|
|
Category: Business Enterprise Architecture
|
Description: The CONOPS identifies and describes concepts relative to BEA development that enable the BEA to address the following two types of requirements or improvements:
|
•
|
A "top down and bottom up" approach to BEA development aimed at delivering the right balance of strategic and tactical information within the BEA, making it possible to address the strategic and tactical requirements and federate the BEA with relevant component and system architectures.
|
|
•
|
A governance model and supporting processes to manage priorities.
|
|
|
Relationship to the DoD’s SOA Adoption: This document describes the concept of operations for the BEA, including how stakeholding organizations update and evolve the BEA over time.
|
http://www.defenselink.mil/dbt/products/BEA_CONOPS_14SEP2007.pdf
|
|
Category: BMA Federation Strategy
|
|
Version: 2.4a
|
|
Date: January 29, 2008
|
| Description: This strategic roadmap formally describes the means for the DoD to achieve the business transformation vision – the attainment of interoperability, data sharing, and an environment that fosters the discovery and delivery of business services. It describes the authority and responsibility of the BMA CTO and CA to facilitate and guide the execution within existing technical and business investment governance structures, in compliance with the Ronald W. Reagan NDAA for the 2005 Fiscal Year.
|
|
Relationship to the DoD’s SOA Adoption: This document essentially describes how the business side of the DoD is moving toward a Net-Centric operating environment. As such, it is the foundational guidance for how the Business Mission area will implement SOA as per the BOE pattern and any necessary technical components as well as the associated BTI.
|
http://www.defenselink.mil/dbt/federation_strategy.html
|
|
Category: Business Transformation Guidance (BTG)
|
| Description: The BTG was developed to help DoD organizations understand and apply the DoD business transformation approach and supporting processes and tools. The BTG supports the overarching goals of transforming business operations to achieve improved Warfighter support while enabling financial accountability across the DoD enterprise.
|
|
Relationship to the DoD’s SOA Adoption: The fundamental purpose of this document is to guides DoD transformation efforts for business systems in support of SOA adoption.
|
http://www.defenselink.mil/dbt/products/BTG/index.html
|
|
Category: Business Mission Area
|
|
Version: 3.0
|
|
Authors: Secretary of Defense
|
| Description: This third edition of the Defense Acquisition Transformation Report is issued in response to the semi-annual congressional reporting requirement in Section 804 of the John Warner National Defense Authorization Act for Fiscal Year 2007, Public Law 109-364.
|
|
Relationship to the DoD’s SOA Adoption: Through regulation from Congress, this report provides guidance as to how the DoD should approach business transformation in support of SOA adoption.
|
http://www.dtic.mil/whs/directives/corres/html/811501.htm
|
|
Category: Defense Information Enterprise Architecture
|
|
Version: 1.0
|
|
Date: April 11, 2008
|
|
Authors: DoD CIO
|
| Description: The DIEA document provides a common foundation to support accelerated DoD transformation to net-centric operations and further establishes priorities to address critical barriers to its realization. The Defense Information Enterprise comprises the information, information resources, assets, and processes required to achieve an information advantage and share information across the DoD and with mission partners. DIEA describes the integrated Defense Information Enterprise and the rules for the information assets and resources that enable it.
|
|
Relationship to the DoD’s SOA Adoption: This is the enterprise architecture for the DoD enterprise information management arena, focusing on the infrastructure and standards needed to support and enable net-centric information sharing and SOA.
|
http://www.dtic.mil/whs/directives/corres/pdf/832003p.pdf
|
|
Category: Net-Centricity
|
|
Date: May 4, 2007
|
|
Authors: DoD CIO
|
|
Description: This strategy is considered a key enabler of the DoD's business transformation plan in that it establishes the foundation for managing data in a net-centric environment.
|
The key attributes include:
|
•
|
ensuring data remains visible, available, and usable when needed and where needed
|
|
•
|
"tagging" of all data (intelligence, non-intelligence, raw and processed) with metadata to enable discovery of data by users
|
|
•
|
advancing the DoD from defining interoperability through point-to-point interfaces to enabling the "many-to-many" exchanges typical of a net-centric data environment
|
|
|
Relationship to the DoD’s SOA Adoption: This body of work provides the foundation for how data should be managed to enable and preserve interoperability at the DoD and provides foundational guidance for the Business Mission Area (BMA) Architecture Federation Strategy and Roadmap.
|
http://www.defenselink.mil/cio-nii/docs/Net-Centric-Data-Strategy-2003-05-092.pdf
|
|
Category: Net-Centricity
|
|
Date: March, 2007
|
|
Authors: DoD CIO
|
|
Description: This document describes the DoD’s vision for establishing the NCE that increasingly leverages shared services and SOA. The DoD’s NCE is a framework for human and technical connectivity and interoperability that allows DoD users and mission partners to share and protect information and to make informed decisions. The NCE consists of numerous mission and business services and common and shared infrastructure services.
|
|
This strategy is applicable to Warfighting, Business, DoD Intelligence, and EIE Mission Areas and Joint Capability Portfolios. The NCSS expands upon the DoD Net-Centric Data Strategy (May 2003) by connecting services to the strategy goals. The NCSS is consistent with other DoD net-centric strategies and guidance. Separate DoD issuances will be provided to address NCSS implementation details and specific technical guidance.
|
|
Relationship to the DoD’s SOA Adoption: Provides the foundation for how services should be managed to establish interoperability and provides foundational guidance for the Business Mission Area (BMA) Architecture Federation Strategy and Roadmap.
|
http://www.defenselink.mil/cio-nii/docs/Services_Strategy.pdf
|
|
Category: NetCentric
|
| Description: This guide is issued under the authority of DoD Directive 8320.2, "Data Sharing in a Net-Centric Department of Defense," December 2, 2004. It provides implementation guidance for the community-based transformation of existing and planned IT capabilities across the DoD in support of Department-wide net-centric operations. This guide applies to the Office of the Secretary of Defense, Military Departments, the Chairman of the Joint Chiefs of Staff, the Combatant Commands, the Office of the Inspector General of the DoD, the Defense Agencies, the DoD Field Activities, and all other organizational entities within the DoD.
|
|
Relationship to the DoD’s SOA Adoption: This provides concrete steps as guidance on how to share data at DoD and further complements DoD Directive 8320.02.
|
http://www.dtic.mil/whs/directives/corres/html/832002g.htm
|
|
Category: DoD Architecture Framework
|
|
Version: 1.5
|
| Description: This version of the DoDAF is an evolution of the DoDAF v1.0 and reflects and leverages the experience that the DoD Components have gained in developing and using architecture descriptions. This transitional version provides additional guidance on how to reflect net-centric concepts within architecture descriptions, includes information on architecture data management and federating architectures through the Department, and incorporates the pre-release CADM v1.5, a simplified model of previous CADM versions that includes net-centric elements.
|
|
Relationship to the DoD’s SOA Adoption: The DoDAF is the architectural framework for enterprise architecture in the DoD and this document represents the most current version of this framework.
|
http://jitc.fhu.disa.mil/jitc_dri/pdfs/dodaf_v1v1.pdf
|
|
Category: BMA Federation Strategy
|
|
Authors: Dennis Wisnosky, Dimitry Feldshteyn, Wil Mancuso, Al Gough, Eric J. Riutort, Paul Strassman
|
|
Description: Provides visibility into the analysis that led to the BTI. This article describes the research performed by the BMA CTO Working Group into commercial SOA capabilities in order to determine how feasible it is to implement the BOE pattern given the current state of technology and commercial tools.
|
|
Relationship to the DoD’s SOA Adoption: The article explains the conducted research and presents findings on the state of SOA foundational technology as it pertains to DoD requirements.
|
http://www.stsc.hill.af.mil/crosstalk/2008/10/index.html
|
|
Category: DoD Instruction
|
| Description: This directive updates DoD policy and responsibilities for interoperability and supportability of IT, including NSS, and implements relevant DoD CIO responsibilities. It further defines a capability-focused, effects-based approach to advancing IT and NSS interoperability and supportability across the DoD and establishes the NR-KPP to assess net-ready attributes required for both the technical exchange of information and the end-to-end operational effectiveness of that exchange.
|
|
Note that the NR-KPP replaces the Interoperability KPP and incorporates net-centric concepts for achieving IT and NSS interoperability and supportability.
|
|
Relationship to the DoD’s SOA Adoption: This document provides fundamental guidance that helps illustrate the need for interoperability among DoD IT systems. As such, it is considered foundational to the attainment of net-centricity and, as a directive, its policies must be adhered to. Furthermore, it explains how interoperability can be measured through a process described by Net-Ready Key Performance Parameters.
|
http://www.dtic.mil/whs/directives/corres/pdf/463005p.pdf
|
|
Category: Department of Defense Directive
|
|
|
|
Authors: of the Joint Chiefs of Staff Instruction (CJCSI) 6212.01D
|
| Description: Directs the use of resources to implement data sharing among information capabilities, services, processes, and personnel interconnected within the GIG.
|
|
Relationship to the DoD’s SOA Adoption: This document establishes specific policies regarding the sharing of data within the DoD that, in turn, reinforces the move toward net-centricity and interoperability (which, as a directive, must be adhered to).
|
http://www.dtic.mil/whs/directives/corres/pdf/832002p.pdf
|
|
Category: Department of Defense Directive
|
| Description: This directive establishes policies and prescribes the criteria and responsibilities for the creation, maintenance, and dissemination of UID data standards for discrete entities.
|
|
UID standards enable on-demand information in a net-centric environment, which is an essential element in the accountability, control, and management of DoD assets and resources.
|
|
Relationship to the DoD’s SOA Adoption: This document guides and directs specific data management standards that provide a common context within the DoD. As a directive, the standards must be adhered to.
|
http://jitc.fhu.disa.mil/jitc_dri/pdfs/3170_01b.pdf
|
|
Category: Enterprise Transition Plan
|
|
Description: The ETP is the DoD’s integrated business transformation plan, which incorporates the transition plans of the Military Services, Components, and the DoD Enterprise. It provides a roadmap for achieving the DoD’s business transformation by implementing changes to technology, process, and governance and further contains time-phased milestones, performance metrics, and a statement of resource needs for new and existing systems that are part of the BEA and Component architectures. The ETP also includes a termination schedule for legacy systems that will be replaced by systems in the target environment.
|
|
The September 2008 release of this document marks the DoD’s fourth delivery of an integrated ETP and provides details on the business transformation progress for 80 systems and initiatives, including 11 enterprise resource planning systems.
|
|
Relationship to the DoD’s SOA Adoption: This document explains how the DoD is moving toward the state described by the BEA and the progress made on an annual basis. It further provides a framework for baselining and the performance management of business transformation. All DoD enterprise business systems and component business systems are included in this report.
|
http://www.defenselink.mil/dbt/products/2008_BEA_ETP/Sept2008/ETP.html
|
|
Category: Information Assurance
|
| Description: This plan establishes the strategy for assuring the DoD’s information, information systems and information infrastructure to support its transformation to network and data-centric operations and warfare and the GIG Mission Assurance.
|
|
Relationship to the DoD’s SOA Adoption: This document provides guidance for how information assurance should be handled within the DoD.
|
http://www.defenselink.mil/cio-nii/docs/DoD_IA_Strategic_Plan.pdf
|
|
Category: DoD Instruction
|
| Description: This instruction establishes policy, assigns responsibilities, and provides procedures for the development and/or modification of wireless communications waveforms in order to improve network interoperability in accordance with the guidance in DoD Instruction 5025.01 (and the authority in DoD Directives 5144.1 and 4630.05).
|
|
Relationship to the DoD’s SOA Adoption: This instruction supports the overall SOA initiatives by providing additional guidance on how to achieve interoperability among DoD IT systems and it also complements the DoD Directive 4630.05.
|
http://www.dtic.mil/whs/directives/corres/pdf/463009p.pdf
|
|
Category: DoD Instruction
|
| Description: This DoD instruction establishes a simplified and flexible management framework for translating mission needs and technology opportunities (based on approved mission needs and requirements) into stable, affordable, and well-managed acquisition programs that include weapon systems and AISs. It is consistent with statutory requirements and authorizes MDAs to tailor procedures to achieve cost, schedule, and performance goals.
|
|
Relationship to the DoD’s SOA Adoption: This document provides instructions for how IT systems, including defense business systems, are to be acquired. The BMA currently follows these instructions in its acquisition processes.
|
http://www.dtic.mil/whs/directives/corres/html/
|
|
Category: DoD Instruction
|
| Description: This Instruction implements policies that were originally established in DoD Directive 8115.01 and, under the authority established in DoD directive 5144.1, describes responsibilities for the management of DoD IT investments as portfolios within the DoD Enterprise (to include Mission Areas, Subport Folios, and Components) that focus on improving DoD capabilities and mission outcomes consistent with 40 U.S.C. 11101, OMB Circular A-130, and DoD Directive 8000.1.
|
|
Relationship to the DoD’s SOA Adoption: This document provides additional instruction on how to portfolios relevant to SOA projects are managed and it further complements DoD Directive 8115.1.
|
http://www.dtic.mil/whs/directives/corres/html/811502.htm
|
|
Category: Investment Review Board
|
| Description: This document integrates policies, specifies responsibilities, and identifies the processes to establish and operate IRBs for the purpose of reviewing all business system investments (at least annually) and for certifying business system modernizations and enhancements over one million dollars, as required by 10 U.S.C. 2222 (a) (1). It includes policies that govern the consistent implementation of the 10 U.S.C. 2222 regulation within the DoD.
|
|
Relationship to the DoD’s SOA Adoption: The IRB CONOPS provides the
foundation by which portfolio management is executed for
defense business systems through Investment Review Boards.
These IRBs are considered critical governance structures
for portfolio management and all designated to the DoD
enterprise and component business systems must pass
through their portfolio management process.
|
http://www.defenselink.mil/dbt/products/investment/final_IRB_conops.pdf
http://www.defenselink.mil/dbt/products/investment/IRB_CONOPS_29-AUG-2006.pdf
|
|
Category: MEMO
|
| Description: This memo announces how the joint agreement between the DoD and IC seeks to create a services-based information environment and to reinforce DoD and DNI collaboration towards implementing business and information services and service-oriented architecture. This environment, which leverages commercial practices, offers functionality as 'services' rather than stand-alone applications and is based on building capabilities using standard Web technologies.
|
|
Relationship to the DoD’s SOA Adoption: This memo provided the foundation for the Intelligence Community and the DoD to begin a joint, cooperative SOA adoption initiative with the goals of establishing interoperability and setting standards for interoperability and net-centricity.
|
http://www.defenselink.mil/releases/release.aspx?releaseid=11146
|
|
Category: MEMO
|
| Description: This memo explains the immediate establishment of the BTA in support of the advancement of the defense-wide business transformation. It further announces that until a permanent director is named, the Deputy Under Secretary of Defense for Business Transformation and the Deputy Under Secretary of Defense for Financial Management jointly will perform the function of the Director and will report to the Under Secretary of Defense for Acquisition, Technology and Logistics (USD(AT&L)), as the vice chair of the Defense Business Systems Management Committee (DBSMC). The memo further provides an organization chart for the BTA.
|
|
Relationship to the DoD’s SOA Adoption: This memo was responsible for creating the Defense Business Transformation Agency.
|
http://www.defenselink.mil/dbt/products/BTA_memo.pdf
|
|
Category: MEMO
|
| Description: On October 7, 2005 the Deputy Secretary of Defense signed a memorandum establishing the BTA. This memorandum was followed by the publication of Program Budget Decision 72 1 on December 20, 2005, formalizing the funding and resources allocated to this new organization. This new agency’s mission is to transform business operations to achieve improved Warfighter support while enabling financial accountability across the DoD.
|
|
Relationship to the DoD’s SOA Adoption: This memo described how the Defense Business Transformation Agency would be organized.
|
http://www.defenselink.mil/dbt/products/Organization_of_the_Defense_
Business_Transformation_Agency.pdf
|
|
Category: Business Transformation Infrastructure
|
| Description: The DoD CIO established this DoD Metadata Registry and a related metadata registration process for the collection, storage and dissemination of structural metadata information resources (schemas, data elements, attributes, document type definitions, style-sheets, data structures etc.).
|
|
Relationship to the DoD’s SOA Adoption: The DoD Metadata Registry is registry for the DoD enterprise and the BMA and as such, it is central to the BMA Federation Strategy and Roadmap.
|
https://metadata.dod.mil/mdr/homepage.htm
|
|
Category: Business Transformation Infrastructure
|
| Description: The DoD DDMS defines discovery metadata elements for resources posted to community and organizational shared spaces.
|
|
Relationship to the DoD’s SOA Adoption: This is the basis for searching for services and information in the DoD net-centric environment and therefore also provides these functions in support of the BOE pattern.
|
http://metadata.dod.mil/mdr/irs/DDMS/
|
|
Category: Architecture Federation
|
|
Version: 1.0
|
|
Authors: DoD CIO
|
|
Description: The security challenges of the 21st century are characterized by change and uncertainty. Operations vary widely and partners cannot be anticipated. The DoD is confronting this uncertainty by becoming more agile. Greater levels of organizational agility rest upon leveraging the power of information – the centerpiece of today's defense transformation to NCO. The GIG Architectural Vision document establishes an information sharing environment critical to transformation to NCO to support DoD forces in improving access to timely and trusted information and quickly and seamlessly sharing this information with partners, both known and unanticipated.
|
|
Relationship to the DoD’s SOA Adoption: This strategic document describes the overall architecture vision for the DoD and provides foundational guidance for the Business Mission Area (BMA) Architecture Federation Strategy and Roadmap document.
|
http://www.defenselink.mil/cio-nii/docs/GIGArchVision.pdf
|
|
Category: Business Enterprise Architecture
|
| Description: The BEA contains requirements that a program must adhere to in order to be deemed compliant. ACART™ v4.0 is an automated tool provided by the BTA to the defense community that is used for assessing systems compliance against the data standards, business rules, laws, regulations, and policies defined in the BEA.
|
|
Features within ACART™ filter parts of the architecture that are relevant to a system’s assessment, document the program's compliance plan, provide for PCA approval, and retain the program assessment historical record. ACART™ can be used to generate reports for submission to the IRB to certify compliance with the DoD’s business transformation blueprint.
|
|
Relationship to the DoD’s SOA Adoption: The ACART™ tool is integral to the BMA community in managing compliance to the BEA. Due to the vast number for laws, rules and regulations pertinent to the BMA and the BEA, this tool helps reduce the overhead required to assert BEA compliance.
|
http://www.defenselink.mil/dbt/acart_main.html
|
|
Category: MEMO
|
| Description: This memo explains the establishment of the DBSMC to advance the development of world-class business operations in support of the Warfighter. The DBSMC will recommend policies and procedures required to integrate DoD business transformation and to review and approve the defense business enterprise architecture and cross-Department, end-to-end interoperability of business systems and processes, as outlined in the attached charter. The DBSMC replaces the current Business Management Modernization Program governance structure.
|
|
Relationship to the DoD’s SOA Adoption: This memo created the DBSMC, which is the top-level decision-making and governance entity for the acquisition of business systems in the BMA.
|
http://www.dtic.mil/whs/directives/corres/pdf/dsd050207transform.pdf
|
|
Category: Business Mission Area
|
|
Date: March 15, 2005
|
| Description: This is the official response to the Public Law 108-375 2005 Congressional Report and associated cover letter and the official DoD response to Public law 107-314 submitted to congress.
|
|
Relationship to the DoD’s SOA Adoption: The referenced public law became a catalyst for the establishment of the BEA, ETP, DBSAE and the Defense Business Transformation Agency.
|
http://www.defenselink.mil/cio-nii/docs/DIEAv1.pdf
|
|
|
|
SOADoD.org is operated and maintained jointly by the U.S. Department of Defense and MITRE with the support of Tech Team Government Solutions Inc, CACI and SOA Systems Inc.
SOADoD.org is a community portal that also acts an official resource site for the book SOA Design Patterns by Thomas Erl with contributions by Dennis Wisnosky (Chief Architect, BMA, DoD) and others.
SOADoD.org and SOA Design Patterns are official resources as part of the curriculum for the SOA Certified Professional (SOACP) education program.
|
Official Documents