Department Of Defense Architecture Framework Research Articles

Architecture Design Space Generation via Decision Pattern-Guided Department of Defense Architecture Framework Modeling

The importance of architecture design keeps increasing as the complexity of systems and system-of-systems (SoSs) continues rising. While the architecture frameworks such as the Department of Defense Architecture Framework (DoDAF) are commonly used to guide architecture design, many perspectives are still hindering their effective use. Instead of generating a set of architecture description models probably only for satisfying the milestone review, the architecture frameworks should be used to organize the vague or incomplete information, identify and formulate the decision-making problem, and guide the architecture decision-making. Unfortunately, the decision points are hidden in the architecture models and the ambiguity often leads to a confusion of whether the architecture models are built incorrectly due to the lack of modeling experience or the lack of adequate decision analysis. Therefore, this paper identifies the key decision points and decision types during the architecture model development based on the DoDAF. Plus, this paper proposes a set of decision patterns and a guide to their use to provide qualitative decision analysis for developing architecture models and generating alternatives. An illustrative example to anti-submarine SoSs demonstrates the process of applying the decision patterns to the DoDAF model’s development and the generated architecture alternatives.

The on-orbit mission analysis of OTV based on DoDAF

PurposeThe purpose of this paper is to improve the efficiency of on-orbit operations through the top-level task design based on DoDAF. Based on the existing upper stage rocket technology, orbit transfer vehicles (OTVs) have developed rapidly in recent years. However, the lack of decision guidance based on overall task analysis requires integrating top-level analysis and bottom-level execution to achieve the smooth development of full-process tasks.Design/methodology/approachUsing the Department of Defense Architecture Framework (DoDAF) as a reference, this paper performs the top-level mission analysis modeling of the on-orbit rendezvous and capture of the OTV. Moreover, the typical operational view products are obtained, and the cooperative relations among the mission requirements, the system requirements, and the functional requirements are also analyzed.FindingsThe results show that the attitude of the OTV changes violently during the maneuver and rendezvous phases. In addition, the view products can be optimized based on the results.Originality/valueThe proposed DoDAF-based on-orbit task integration analysis method achieves the effective fusion of high-level analysis and bottom-level execution of OTV on-orbit rendezvous and capture task through the top-level task modeling, operation view generation and task relationship analysis. According to the requirements and constraints of the on-orbit rendezvous and capture task, the control instructions of the vehicle are efficiently generated under the DoDAF framework.

Bridging Joint Operations and Engineering Management through an Operational Mission Architecture Framework

The paper presents an organizing framework for directly incorporating United States Department of Defense (DoD) joint operational concepts into early-stage engineering management and system design. It translates operational level guidance from DoD Joint Publications to a concise Operational Mission Architecture Framework (OMAF) that can be used as a starting point for engineering management efforts. The OMAF is used to orient the development of systems architecture products per Department of Defense Architecture Framework (DoDAF) standards. Resultantly, the OMAF serves as a bridging mechanism between the language and terminology employed in the joint operational community and the engineering management community.

Development of Transportation Management System with the Use of Ontological and Architectural Approaches to Ensure Trucking Reliability

With the wide variety of information systems and applications for motor transport and transport logistics control we have today, one may think we are already living in the digital era of general welfare, and digital tools would easily ensure sustainable development and prosperity of businesses. However, the experience of deployment and introduction of such solutions shows that their value for transport business is significantly lower than expected. Moreover, in some projects, business performance of transport companies had no correlation with introduction of information systems. In the best-case scenario, they provided for a slight decrease in document flow transaction costs. The change of the strategic status of a company in the transportation service market is a fairly complicated task, which, as analysis of literary sources shows, is achievable for few enterprises, primarily small and medium-sized businesses. Such situations show that information solutions were introduced without analyzing or assessing the business models of certain companies which could be used a basis for digital landscape of business as a whole. In recent years, the basic concept of forming a single information space of an enterprise has been the enterprise architecture. It provided for coordination between all the business processes in order to achieve a company’s strategic goals. The fundamentals of the concept were developed by J. Zachman in his famous Zachman Framework, and it was later developed with numerous models of enterprise architecture (e.g., TOGAF (Department of Defense Architecture Framework), GERAM (Generalised Enterprise Reference Architecture and Methodology), DoDAF (Department of Defense Architecture Framework)). However, currently some researchers note that sustainable corporate development should stem not only from a “correct assembly” of all its business elements, which was the purpose of enterprise architecture, but also from the interaction of these elements when reaching the emergence effect. In this context, one should pay attention to comprehensive activity analysis of a transport and logistics business using ontological and architecture approaches.

Integrating Security into Enterprise Architecture with UAF and PLE

ABSTRACTAt the systems of systems and enterprise levels, systems engineers and architects must plan for system security from system concept inception ensuring security embeds into every process, procedure, system, and component as well as the enterprise's mindset. While the various United States Department of Defense Architecture Framework (DoDAF) views contain security attributes, there is no integrated view set defining system security goals, threats, risks, mitigating elements, and demonstrating how these integrate and implement into the operational, system, standards, and services views. The Unified Architecture Framework (UAF) implements DoDAF using the Systems Modeling Language (SysML) as well as the British Ministry of Defence Architecture Framework (MODAF) and NATO Architecture Framework. In addition, UAF has integrated a security view set facilitating engineers defining security goals and requirements and demonstrating how these implement throughout the architecture. By using these integrated security views, engineers can design system protection as well as system protection options and variants.

Analysis of architecture framework and intelligent development of air-to-ground precision strike system

By the analytical method of system engineering, the air-to-ground precise strike system is set up. Using DoDAF (Department of Defense Architectural Framework, DoDAF), the concept of air-to-ground precision strike is built. The organization is definite and the capability requirement is analyzed. On the basis, the intelligent applications of command and control system, aircraft platform and guided munition are summarized. At last, some suggestion is put forward for the intelligent development of air-to-ground precision strike system.

Research on the strategy of the architecture modeling of aviation ammunition system-of-systems based on mission and capability

The development of the aviation ammunition system has evolved from equipment-based capacity-based. The mapping relations of aviation ammunition mission-ability-weaponry and the capacity-need of different mission are analyzed in this paper. Foreign ammunition development trends and capacity-supported are discussed. Based on the advantages and disadvantages of foreign weapon system architecture, the DODAF (Department of Defense Architecture Framework) and Agent-based system construction strategy is used in the modeling process. This method can provide a certain reference for aviation ammunition architecture.

Architectural Models Enabled Dynamic Optimization for System-of-Systems Evolution

System of Systems (SoS) is designed to deliver value to participant stakeholders in a dynamic and uncertain environment where new systems are added and current systems are removed continuously and on their own volition. This requires effective evolution management at the SoS architectural level with adequate support of process, methods, and tools. This paper follows the principle of Model-Based Systems Engineering (MBSE) and develops a holistic framework integrating MBSE conceptual representations and approximate dynamic programming (ADP) to support the SoS evolution. The conceptual models provide a common architectural representation to improve communication between various decision makers while the dynamic optimization method suggests evolution planning decisions from the analytical perspective. The Department of Defense Architecture Framework (DoDAF) models using Systems Modeling Language (SysML) are used as MBSE artifacts to connect with ADP modeling elements through DoDAF metamodels to increase information traceability and reduce unnecessary information loss. Using a surface warfare SoS as an example, this paper demonstrates and explains the procedures of developing DoDAF models, mapping DoDAF models to ADP elements, formulating ADP formulation, and generating evolutionary decisions. The effectiveness of using ADP in supporting evolution to achieve a near-optimal solution that can maximize the SoS capability over time is illustrated by comparing ADP solution to other alternative solutions. The entire framework also sheds light on bridging the DoDAF-based conceptual models and other mathematical optimization methods.

Reconfigurable Modeling Method of Task-Oriented Architecture for Space Information Networks Based on DaaC

As an important national strategy infrastructure, the Space Information Network (SIN) is a powerful platform for future information support. The architecture model of the SIN is of great significance to the construction and development of the SIN. For the problems related to the poor versatility, portability, and recombination of the existing architecture modeling methods of the SIN, in this paper, based on the Data as a Center (DaaC) modeling idea, we propose a reconfigurable model of the task-oriented architecture of the SIN. Combining with the typical characteristics of the SIN, and drawing on the advantages of activity-based flexibility, service-oriented integrity, and object-oriented reusability, we propose a DaaC modeling idea with space data. The DaaC modeling idea can solve the problems related to the poor versatility and portability of the SIN architecture. Based on the DaaC idea, we analyze the requirements of the task-oriented architecture, and define the basic concepts of SIN reorganization, including the reconfigurable target, reconfigurable scheme, and reconfigurable SIN. We establish the reconfigurable principles of loose coupling, compatibility, isolation, and deconstruction. Meanwhile, we analyze the realization mechanism and methods of the task-oriented reconfigurable model of the SIN based on DaaC. Finally, we take a typical SIN as an example, and make a case study on land-based anti-missile combat activities as the task background based on the DoDAF2.0 (Department of Defense Architectural Framework 2.0) framework and the STK (Satellite Tool Kit) simulation platform. The case results are consistent with the theoretical expectation, and it verifies the feasibility and effectiveness of our proposed method.

A model‐based systems engineering approach to critical infrastructure vulnerability assessment and decision analysis

AbstractSecuring critical infrastructure against attack presents significant challenges. As new infrastructure is built and existing infrastructure is maintained, a method to assess the vulnerabilities and support decision makers in determining the best use of security resources is needed. In response to this need, this research develops a methodology for performing vulnerability assessment and decision analysis of critical infrastructure using model‐based systems engineering, an approach that has not been applied to this problem. The approach presented allows architects to link regulatory requirements, system architecture, subject matter expert opinion and attack vectors to a Department of Defense Architecture Framework (DoDAF)‐based model that allows decision makers to evaluate system vulnerability and determine alternatives to securing their systems based on their budget constraints. The decision analysis is done using an integer linear program that is integrated with DoDAF to provide solutions for how to allocate scarce security resources. Securing an electrical substation is used as an illustrative case study to demonstrate the methodology. The case study shows that the method presented here can be used to answer key questions, for example, what security resources should a decision maker invest in based on their budget constraints? Results show that the modeling and analysis approach provides a means to effectively evaluate the infrastructure vulnerability and presents a set of security alternatives for decision makers to choose from, based on their vulnerabilities and budget profile.

Case Study: Application of DoD Architecture Framework to Characterizing a Hospital Emergency Department as the Intended Use Environment for Medical Devices

AbstractThis paper presents a case study by the Biomedical‐Healthcare Model‐Based Systems Engineering (MBSE) Challenge Team in response to inputs received during workshops held at the 2015 and 2016 INCOSE International Workshops. At IW2015 and IW2016, the Challenge Team held workshops, including clinicians and systems engineers, to assess potential contributions of systems engineering, and MBSE, to clinical operations. At these workshops it was claimed that clinical operations were too complex to be modeled with existing MBSE tools from defense and aerospace. It was further claimed that there would be very limited value to MBSE products. Based on these claims, the MBSE Challenge team undertook several case studies to evaluate the ability of MBSE tools to represent clinical operations and to address problems relevant to healthcare. This paper describes the outcomes of applying one MBSE tool, the DoD Architecture Framework, to characterize clinical operations as the intended use environment for medical devices.

Enterprise-level business component identification in business architecture integration

The component-based business architecture integration of military information systems is a popular research topic in the field of military operational research. Identifying enterprise-level business components is an important issue in business architecture integration. Currently used methodologies for business component identification tend to focus on software-level business components, and ignore such enterprise concerns in business architectures as organizations and resources. Moreover, approaches to enterprise-level business component identification have proven laborious. In this study, we propose a novel approach to enterprise-level business component identification by considering overall cohesion, coupling, granularity, maintainability, and reusability. We first define and formulate enterprise-level business components based on the component business model and the Department of Defense Architecture Framework (DoDAF) models. To quantify the indices of business components, we formulate a create, read, update, and delete (CRUD) matrix and use six metrics as criteria. We then formulate business component identification as a multi-objective optimization problem and solve it by a novel meta-heuristic optimization algorithm called the ‘simulated annealing hybrid genetic algorithm (SHGA)’. Case studies showed that our approach is more practical and efficient for enterprise-level business component identification than prevalent approaches.

TECHNOLOGY UPDATE ON THE UNIFIED ARCHITECTURE FRAMEWORK (UAF)

ABSTRACTArchitecture frameworks continue to evolve. The unified profile for the US Department of Defense (DoD) Architecture Framework (DoDAF) and the UK Ministry of Defence Architecture Framework (MODAF) (UPDM) provides a standard means of representing DoDAF, MODAF, and the North Atlantic Treaty Organization (NATO) architecture framework (NAF) conformant architectures using the Unified Modeling Language (UML), and Systems Modeling Language (SysML). Since the UPDM V2.0 publication, further information has emerged such as the June 2011 NATO study entitled: “Development of The AMN (Afghanistan Mission Network) Architecture In 2010 – Lessons Learned,” by Torsten Graeber of the NATO C3 Agency. This report identified the following in section 4.1‐ARCHITECTURE FRAMEWORKS, sub‐section 4.1.2 Observations (Need for a Unified Architecture Framework) and stated that: Differences in DoDAF, MODAF, and NAF make it difficult to match the metamodel one to one. Some of the concepts in the frameworks have the same name but different definitions, such as different semantics. Difficult to crosswalk the concepts between the different frameworks lead to miscommunication between architects using different frameworks.Based on the above, the NATO Architecture Capability Team (Architecture CaT) meeting on 10‐11 September 2012 committed to moving to a single worldwide architecture framework. Consequently, a new architecture framework profile supporting a unified framework is needed. It is intended that this framework bring the different architecture frameworks together. The UPDM V3.0 domain metamodel shall be derived from MODEM (the MODAF metamodel) and the DoDAF 2.0 metamodel (DM2), both of which are based on the International Defence Enterprise Architecture Specification Foundation (IDEAS). This paper will document the rationale behind the UPDM 3.0 as well as its new name of the unified architecture framework (UAF).

Architecture‐Based SCMILE Service Framework for Systems' Integration

AbstractThe SCMILE Service framework (SSF) is a method to model and analyse the relationships and dependencies between military capability systems. In line with service interactions in the assembly and operation of any military unit, the SSF categorises services into six generic types: Sensing, Command and control, physical Mobility, Information mobility, Logistics and support, and Engagement. Previous research has shown SSF is versatile enough to adapt to military and non‐military domains. In this paper, we will be discussing how SSF can adapt into a system architecture framework, in particular the Department of Defense Architecture Framework (DoDAF) version 2.0. We will discuss in detail how a service‐oriented thinking based approach using SSF can be used to conduct system dependency analysis. To do this, a test case based on a Humanitarian Assistance scenario where the Australian Amphibious Capability is employed to provide support to a disaster affected area, will be used to explore the application of SSF.

Agile digital transformation of System-of-Systems architecture models using Zachman framework

Abstract Emergent behavior is behavior of a system that does not depend on its individual parts, but on their relationships to one another. Such behavior exists in biological systems, physical systems as well as in the human performance. It is an inherited nature of a System-of-Systems (SoS). A suitable framework is needed to guide the development of SoS architecture, which includes emergent behavior. Enterprise architecture (EA) is a discipline driving change within organizations. Aligning and integrating business and IT thereby belongs to strategic management. The management of EA change is a challenging task for enterprise architects, due to complex dependencies amongst EA models, when evolving towards different alternatives. In this paper, various architecture frameworks are explored for an application on SoS architecture: the Department of Defense Architecture Framework (DoDAF) and Ministry of Defense Architecture Framework (MODAF) are declared inappropriate. The Open Group Architecture Framework (TOGAF), the Federal Enterprise Architecture Framework (FEAF) and the Zachman Framework on the other hand are suitable. The use of Zachman Framework to guide the architecture development is described in step-by-step details in this paper. The agent-based simulation is recommended to develop the SoS architectural models following the Zachman Framework guidance. Ultimately, SysML and UML should be integrated with the agent-based model. An example with the collaborative engineering services for the global automotive supply chain is hereby described.

Based on Capability of C4ISR Architectural Modeling and Analysis

C4ISR system is complex system. Such systems architecture and complex needs of many. Then complex system’s capability requirements are difficult to catch. Description of capability requirements are usually imprecise and do not support architecture analysis. The paper uses an extended UML modeling technique to analyzing the requirements of C4ISR capabilities. It also introduces a new model convert domain model into the Description Logic ontology. Use Description Logic ontology description the standard DoD Architecture Framework, the proposed method may populate C4ISR architectural analysis.

Non Legacy viewpoint for Department of Defense Architecture Framework architectures

The Department of Defense Architecture Framework (DoDAF) is a key tool used by the United States engineering and acquisition communities. The DoDAF provides a method to organize system engineering information into a series of architecture products, and groups them into different “views” of the system. These viewpoints represent traditional perspectives of system architecture data, such as operations or technologies. With a new release of the DoDAF, it is now possible to create viewpoints that extend the system architecture to include new types of data such as a Human Viewpoint, which includes information about the human component of the system. This “Non Legacy” viewpoint can be used to augment the standard sets of architectural products with human-centered information important to the system description. However, the methodology to include new viewpoints in the DoDAF is not defined. While the DoDAF specification indicates that new data elements can be included in unique architecture products, there is no guidance on how to instantiate these representations while adhering to the DoDAF Meta Model (DM2) data schema. The focus of this research effort was to develop a methodology to implement the Human Viewpoint by extending the DM2 constructs while preserving the integrity of the overall architecture. The proposed methodology includes augmenting the underlying data schema, identifying the format to render the output models, ensuring that the additional views remains linked to the overall architecture, and evaluating the implications of the additional viewpoint. A flexible architecting tool, the Architex Decision Support Toolset, was used as an architecture test-bed to evaluate the feasibility of implementing Non Legacy viewpoints using the prescribed process. The outcome of this work can be extended to provide a general methodology for including other Non Legacy viewpoints with the DoDAF architecture framework.

Technology Update on the Unified Architecture Framework (UAF)

AbstractArchitecture frameworks continue to evolve. The Unified Profile for the Department of Defense (DoD) Architecture Framework (DoDAF) and the UK's Ministry of Defence Architecture Framework (MODAF) (UPDM) provides a standard means of representing DoDAF, MODAF, and NATO Architecture Framework (NAF) conformant architectures using the Unified Modeling Language (UML), and Systems Modeling Language (SysML). Since the UPDM V2.0 publication, further information has emerged such as the June 2011 NATO study entitled: “Development of The AMN (Afghanistan Mission Network) Architecture In 2010 – Lessons Learned,” by Torsten Graeber of the NATO C3 Agency. This report identified the following in section 4.1‐ARCHITECTURE FRAMEWORKS, sub‐section 4.1.2 Observations (Need for a Unified Architecture Framework) and stated that:• differences in DoDAF, MODAF, and NAF make it difficult to match the metamodel one to one.• some of the concepts in the frameworks have the same name but different definitions, i.e. different semantics.• difficult to cross‐walk the concepts between the different frameworks leads to miscommunication between architects using different frameworks.Based on the above, the NATO Architecture Capability Team (Architecture CaT) meeting on Sept. 10‐11, 2012 committed to move to a single world‐wide Architecture Framework. Consequently, a new architecture framework profile supporting a unified framework is needed. It is intended that this framework bring the different architecture frameworks together. The UPDM V3.0 domain metamodel shall be derived from MODEM (the MODAF metamodel) and the DoDAF 2.0 metamodel (DM2), both of which are based upon the International Defence Enterprise Architecture Specification Foundation [IDEAS]. This paper will document the rationale behind the UPDM 3.0 as well as its new name of the Unified Architecture Framework (UAF).

A Methodology for Making Services and Systems Equal and Combinative in DoD Architecture Framework 2.0

A Methodology for Making Services and Systems Equal and Combinative in DoD Architecture Framework 2.0

Method and Application of Operational Architecture Modeling Based on Information Flow Analysis

Abstract To strengthen operational process analysis and normalize information requirements description in systemic operations based on information systems, a new operational architecture modeling method is proposed from the perspective of information flow analysis. An operational architecture modeling framework based on information flow analysis is established by referring to American department of defense architecture framework (DoDAF V2.0). Concepts of entities, relationships, attributes and mapping rules are defined. Operational activity model, operational nod model and information alternation model are constructed. Finally, aerial assault operation is taken as an example to demonstrate the modeling process. Simulation results show that operational process analysis is more refined and information requirement descriptions are more visible, normal and clear, which validate the feasibility and validity of the method and models.