Search

At present, there exists a prioritization of identifying novel and innovative approaches to managing the small Unmanned Aircraft Systems (sUAS) threat. The near-future sUAS threat to U.S. forces and infrastructure indicates that current Counter-UAS (C-UAS) capabilities and tactics, techniques, and procedures (TTPs) need to evolve to pace the threat. An alternative approach utilizes a networked squadron of unmanned aerial vehicles (UAVs) designed for sUAS threat interdiction. This approach leverages high performance and Size, Weight, and Power (SWaP) conformance to create less expensive, but more capable, C-UAS devices to augment existing capabilities. This capstone report documents efforts to develop C-UAS technologies to reduce energy consumption and collaterally disruptive signal footprint while maintaining operational effectiveness. This project utilized Model Based System Engineering (MBSE) techniques to explore and assess these technologies within a mission context. A Concept of Operations was developed to provide the C-UAS Operational Concept. Operational analysis led to development of operational scenarios to define the System of Systems (SoS) concept, operating conditions, and required system capabilities. Resource architecture was developed to define the functional behaviors and system performance characteristics for C-UAS technologies. Lastly, a modeling and simulation (M&S) tool was developed to evaluate mission scenarios for C-UAS. Outstanding Thesis Civilian, Department of the Navy Civilian, Department of the Navy Civilian, Department of the Navy Civilian, Department of the Navy Civilian, Department of the Navy Approved for public release. Distribution is unlimited.

Purpose The 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/approach Using 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. Findings The 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/value The 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.

As one of the products in the US Department of Defense Architecture Framework version 2.0 (DoDAF 2.0), the Operational Activity to Services Traceability Matrix product (SvcV-5) links the operational viewpoint (OV) and service viewpoint (SvcV). SvcV-5 is an essential product for optimizing the design of other service view products; thus, it is necessary to study how to optimize the design of SvcV-5. This paper studies the semi-automatic design method of SvcV-5 based on the service identification method. The main idea of this paper is to extract relevant information from previous architecture design products, such as OV-6b, CV-4 and CV-6, and then to study the method of taking service identification and designing the SvcV-5 product. First, a message-based service initial identification method is used to generate the initial service set. Second, considering the measure of the cohesion and the coupling degree of the service, a service improving algorithm is used to update the initial service set. In this process, a dependency matrix between operational activities is established; this matrix includes data dependencies and capability requirement dependencies. Then, according to the mapping result of the service identification method, service-related information can be determined manually by designers. Finally, SvcV-5 can be generated through an automatic algorithm based on the service identification result and the OV-6b product. This article verifies the proposed method using the motivation example of the earthquake rescue information system (ERIS) architecture product design. Through conducting experimental analysis and comparing our method with other service identification methods, we illustrate the effectiveness of the proposed SvcV-5 optimization design method.

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&rsquo, 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 &ldquo, correct assembly&rdquo, 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.

© 2020 IEEE. Remote-controlled or autonomous multi-rotor air vehicles, or drones, have become common and commercially available even to individual consumers, mostly for imaging purposes. Drones appeal to mission architects looking to extend the toolbox provided to operators performing challenging missions such as public safety operations. However, careful analysis of the operational context and concept of operations must take place before major acquisitions. The purpose of this paper is to propose a model-based operational architecture definition framework, which is based on the Department of Defense Architecture Framework (DoDAF) ontology and uses Object Process Methodology (OPM) as its underlying modeling language. Through careful mapping of DoDAF Operational Viewpoint (OV) ontology to OPM ontology, we were able to show that the entire OV ontology can be covered by a small set of objects, processes, relations among them, and constructs comprising them. We then show how to instantiate the ontology to create a model of an actual architecture of interest (AoI) while maintaining strong typing of the model elements to ensure validity, integrity, consistency, and continuous compliance with the OV. We demonstrate our approach on the case of using drones in public safety enterprises for the purpose of crowd management in massively attended events and locations. The proposed framework allows for capturing ConOps and OpsCon in a lightweight, yet robust and consistent manner, and improve communication and concept validation between operational stakeholders and enterprise architects.

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

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.

With the deterioration of battlefield environment, joint combat will become an important mode of operation in the future. In this paper, the Department of Defense Architecture Framework (DoDAF) is studied, the architecture framework design ideas and specific architecture design steps of DoDAF are given, the architecture views involved are described. This paper presents a DoDAF-based modeling method for air-sea joint combat system architecture, which can better describe the operational tasks, information relations among constituent nodes and sub-systems of the complex integrated air-sea joint operation system. This method is often used in the early development stage of complex systems, and enhances consistency understanding between application personnel and system designers and developers.

The method of architecture is an effective way to analyze the requirements of weapons and equipment. DODAF (U.S. Department of Defense Architecture Framework) is a standard specification issued by the U.S. Department of Defense in 2004 to guide the generation of military equipment requirements. DODAF has been widely recognized as the standard of weapon equipment requirement description. This paper introduces the concepts of DODAF, analyze DoDAF function, structure and problems of DoDAF, and discusses the basic process of weapon loading requirement analysis based on DODAF method, providing a new scientific method for the analysis and research of weapons and equipment requirements.

The Human Views were developed to collect and categorize human-focused information to ensure that the human component is considered in system architecture development. While the Human Views are not an integrated viewpoint with the Department of Defense Architecture Framework DoDAF, they can be implemented as a set of Fit-for-Purpose views. Fit-for-Purpose views are custom views created to address specific stakeholder questions and to display custom sets of data. However, very little guidance exists for the creation of Fit-for-Purpose views or their use in architecture analysis. To help address this, a six-step methodology was developed to design Fit-for-Purpose Human Views for the DoDAF. The methodology is illustrated using a mobile communication system; the resulting Human Views can be used to evaluate the impact of assigning different types of personnel to complete mission tasks using the system. By including custom data in the output products, such as simulation outcomes, the Fit-for-Purpose views support resolution of specific stakeholder concerns. The six-step design methodology is domain agnostic and may be generalizable to the design of Fit-for-Purpose views for other areas of concern.

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.

This chapter details the overall system architecting process that aligns with the Department of Defense Architecture Framework. It also describes in detail the Human Viewpoint methodology. This five stage methodology includes understanding the context, collecting the data, designing the models and performing analyses. It also describes the Fit for Purpose concept and its use in rendering Human Views to address specific stakeholder concerns at the last stage. The methodology is aligned with a sequenced development of the individual views and results in a complete Human Viewpoint.

By analyzing the department of defense architecture framework (DoDAF), the architecture modeling process for C2 System of Joint anti-ship combat (C2JAC) based on DoDAF2.0 is proposed. Combining with 0perational requirements of joint anti-ship combat and specific operational process, key model of operational and system perspective for C2JAC is designed by using the method of combining structured and object-oriented. Finally, the behavior logic of the architecture dynamic model is verified by the Rational Rhapsody architecture verification tool. The results express the rationality of the designed architecture model.

In this paper, the aircraft scenario modeling and requirement capture method are studied under the framework of the Department of Defense Architecture Framework (DoDAF) based on Model-Based System Engineering (MBSE). First, the description method is presented based on the DoDAF, basic elements, and the model levels of the aircraft operational scenario respectively. Second, the aircraft requirement capture process and analysis steps are determined based on the aforementioned scenario. Operational requirements can be captured by the interaction between aircraft and various stakeholders in different operational scenarios. Then, the scenario model of a certain civil aircraft, including the flight phase level, the task cell level, and the behavior unit level, is constructed based on the DoDAF. The process of operational requirement capture based on the above model is elaborated in detail. Finally, the results of this paper can be applied to capture the operational requirements of aircraft. More importantly, the results can also be used to connect the market needs with the development process of aircraft. The traceability between market needs and development requirements can be identified effectively.

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.

This paper proposes an approach to construct effectiveness evaluation model semi-automatically based on system architecture such as Department of Defense Architecture Framework (DoDAF). The effectiveness evaluation index system is firstly generated based on architecture models including Capability Dependencies (CV-4), Capability to Operational Activities Mapping (CV-6), Operational Activity to Systems Traceability Matrix (SV-5b) and System Measures Matrix (SV-7) in the DoDAF, using the transformation technology QVT. Then the effectiveness calculation model, which is based on analytic hierarchy process (AHP), is semi-automatically generated based on the evaluation tool developed by the authors' team. Based on the effectiveness evaluation index system and the calculation model, the effectiveness of the system described in the architecture can be evaluated in the supporting of the corresponding data, which can be from simulation results or experts. Because the effectiveness evaluation model is constructed based on the system architecture, The proposed approach can ensure that the constructed effectiveness evaluation model including the index system and the calculation model has its source and is objective, distinguishing from experience or emotion. Besides, the proposed approach can improve the efficiency and decrease the mistakes during the process of constructing effectiveness model.

The System of System (SoS) supportability assessment problem has become more and more complicated and lacks of efficient means because there are multiple combatant tasks and numerous weapons and systems. In this study, the Department of Defense Architecture Framework (DoDAF) is used as a top-down perspective to analyze the SoS supportability problem. Moreover, the fundamental elements which are related to SoS supportability are categorized from a down-top perspective. With the two perspectives integrated, the SoS supportability assessment model is constructed which is comprised of the supportability composite parameters, the supportability design parameters and the supportability resource parameters.

A novel executable modeling approach is proposed for system-of-systems architecture by taking full advantage of the Department of Defense Architecture Framework (DoDAF) Meta-model (DM2) and defining the common model transformation specification at the metamodel level. This methodology provides more flexibility and adaptability for the automated construction of executable models directly from the architectural data rather than from static models. More specifically, the architectural data metamodel is first established to guide architectural data modeling of core data elements and associations in DM2 as the common and consistent data dictionary for architecture modeling, while the executable formalism metamodel is designed to formally define executable models. Then, the mapping rules between both metamodels are presented as the common transformation specification regardless of which modeling language or methodology is employed in developing architectural descriptions. Finally, eXtensible Markup Language (XML) technology, like XML schema languages and eXtensible Stylesheet Language specifications, is discussed to facilitate the automated transformation of executable models from architectural instance data. The feasibility of the proposed approach is illustrated using a published example where colored Petri net (CPN) is used as the executable formalism.

The capture of system structure, behavior, configuration, interaction, and compliance is common practice in architectures. These are largely static views showing a specific configuration or behavior. IEEE Std 610.12–1990 defines architecture as “the fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution.” (IEEE, 1990) Modeling this evolution or the temporal aspects in architecture frameworks such as the Department of Defense Architecture Framework (DoDAF) was previously problematic. With the release of DoDAF version 2.0, architectures can now take the fourth dimension (Time) into account. The challenge is to identify areas of architecture where time can be modeled and how to take best advantage of it. Also problematic is how to express these concepts without having to expose all the internal ontological relationships upon which DoDAF is built. The Unified Profile for DoDAF and MODAF (UPDM) delivers an implementation of DoDAF 2.0 that provides a clear and concise way of expressing these concepts without requiring the user to become an expert in the DoDAF 2.0 “internal wiring” and detailed ontological concepts. This paper will examine the temporal concepts defined in DoDAF 2.0 and show how time can be effectively integrated into a model to express essential temporal concepts.

With the continuous emergence of all kinds of complex systems and the increasing complexity of complex systems, standards architecture becomes more and more important for its guidance and support in the life cycle of complex systems. First, this paper makes a comparative study on several architectures and architecture frameworks, and the comparative study shows that Standards Viewpoint is a better way of modeling of standards architecture; then by using and improving Department of Defense Architecture Framework, this paper puts forward a Standards Viewpoint development methodology; finally, by making secondary development of commercial architecture software platform, this paper realizes software development of Standards Viewpoint and modeling of standards architecture.

A data-centric, capability-focused approach is proposed to facilitate the architecture modeling and analysis of challenging system-of-systems (SoS). This approach abstracts essential information from the underlying complexity with the architecture modeling in a data-centric and semantically consistent fashion, and allows early understanding and exploration of the logical, behavioral, and performance characteristics to achieve the desired capabilities. More specifically, a high-level data meta-model, depicting the semantic relationships of constituent architectural data elements, is first presented to guide the architectural data modeling, which is aligned well with the US Department of Defense Architecture Framework (DoDAF) Meta-model (DM2). Then, the development of architectural descriptions and the construction of executable models are studied based on the core architectural data elements. Additionally, architecture analysis using static and executable models are discussed, including static analysis, dynamic analysis, and experimental analysis. The feasibility of the foregoing approach is demonstrated with an illustrative example. ©2013 Wiley Periodicals, Inc. Syst Eng 16

The target audiences for this paper are systems engineers and architects involved in the design of complex systems such as program organizations. This is the first in a series exploring how the design of program organizations developed for the purpose of designing and developing aerospace and defense systems can be optimized. The objective of this paper is to lay the groundwork for an architecture framework for the development of a program organization. The draft standard ISO/IEC 42010 is used to define the structural requirements of the architecture framework. In addition, we use the Zachman Architecture FrameworkTM to organize the framework and the Department of Defense Architecture Framework Version 2.0 DoDAF 2.0 to create the model environment for the Program Organizational Architecture Framework POAF. This approach to defining the POAF ensured that we would have the data needed to support our objective to optimize the design of the program organization and hopefully reduce the number of defects inherent in the design. We also believe that we have sufficiently defined the characteristics of a POAF to spur more research in this area. © 2012 Wiley Periodicals, Inc. Syst Eng

The capability requirements of the command, control, communication, computing, intelligence, surveillance, reconnaissance (C4ISR) systems are full of uncertain and vague information, which makes it difficult to model the C4ISR architecture. The paper presents an approach to modeling the capability requirements with the fuzzy unified modeling language (UML) and building domain ontologies with fuzzy description logic (DL). The UML modeling constructs are extended according to the meta model of Department of Defense Architecture Framework to improve their domain applicability, the fuzzy modeling mechanism is introduced to model the fuzzy efficiency features of capabilities, and the capability requirement models are converted into ontologies formalized in fuzzy DL so that the model consistency and reasonability can be checked with a DL reasoning system. Finally, a case study of C4ISR capability requirements model checking is provided to demonstrate the availability and applicability of the method.

The NATO Human View is an additional viewpoint for an architecture framework that provides information on the human in the system. This paper represents the last of three papers describing the NATO Human View. The first paper described the development of the Human View by a multinational NATO panel [Handley and Smillie, Syst Eng 11(2) (2008), 156–164]. The second paper described a methodology to use the Human View data in a simulation model in order to demonstrate the impact of the human on system performance [Handley and Smillie, Syst Eng 13(1) (2010), 72–79]. This final paper describes a methodology to align the NATO Human View with the Department of Defense Architecture Framework (DoDAF) 2.0 Meta Model (DM2) in order to produce “Fit for Purpose” views. These views can be used to augment the standard sets of architectural products with human-centered information important to the system description. The alignment of the Human View with the DM2 also facilitates reconciliation of different interpretations of the Human View construct. © 2011 Wiley Periodicals, Inc. Syst Eng © 2012 Wiley Periodicals, Inc.

This paper presents a development of the US Department of Defense Architecture Framework (DoDAF) based on life-cycle concept of the Generalized Enterprise Reference Architecture and Methodology (GERAM) framework/ISO 15704:2000 requirements. Previous research has identified areas of concern within DoDAF by analyzing and evaluating DoDAF against GERAM and potentially assisting in its future development. This paper aims to extend existing architecture description process and artifacts within DoDAF that match the scope of the GERAM life-cycle phases. For this development we use life-cycle aspect of three well-known reference architectures (including PERA, CIMOSA, and GRAI-GIM) that were the basis in formation of GERAM.

Spiraling vehicle complexity requires an overall architectural concept that provides a total vehicle perspective across all functional domains. Here we summarize the concept and some basic elements of an architecture framework for the automotive industry. We intend to drive the thought process within the automotive industry toward a standardized architectural foundation that builds upon successful examples of similar efforts, such as the Department of Defense Architecture Framework (DoDAF).

Problem statement: The Command, Control, Communications, Computers and Intelligence (C4I) Systems provided situational awareness about operational environment and supported in decision making and directed to operative environment. These systems had been used by various agencies like defense, police, investigation, road, rail, airports, oil and gas related department. However, the increase use of C4I system had made it more important and attractive. Consequently interest in design and development of C4I system had increased among the researchers. Many defense industry frameworks were available but the problem was a suitable selection of a framework in design and development of C4I system. Approach: This study described the concepts, tool and methodology being used for evaluation analysis of different frameworks by Analytic Hierarchy Process (AHP). Results: We had compared different defense industry frameworks like Department of Defense Architecture Framework (DODAF), Ministry of Defense Architecture Framework (MODAF) and NATO Architecture Framework (NAF) and found that AHP is fairly good tool in terms of analysis. Conclusion: Different defense industry frameworks such as DODAF, MODAF and NAF had been evaluated and compared using AHP.

This paper presents an approach to work with the process life-cycle of the U.S. Department of Defense Architecture Framework (DoDAF), and extend existing architecture description process and artifacts within DoDAF that match the scope of the ADD life-cycle phases to enhanced system life-cycle development process that includes process-iteration based development and determination in an integral manner.

This research examines the underlying rationale of architecture frameworks and their use in acquisition with the goal of identifying best practices to improve system development. Three key questions are addressed: (1) What is the role of artifacts in system design? (2) What are the benefits provided by architecture frameworks? And (3) what are the best measures-of-effectiveness for assessing the value of architecture frameworks? To address the first question, we review relevant literature on collaborative design and propose a rationale for using artifacts as communicative and illustrative tools. Second, we enumerate the motivations for their use in system design and acquisition. Third, eight measures-of-effectiveness of architecture frameworks are derived from the literature and our experience with the Department of Defense Architecture Framework.

We address the problem of lean staffing with a review of the Department of Defense Architecture Framework and conclude that the human system aspects of the relevant Organizational and Systems Views need to be informed by special analytic methods from Cognitive Systems Engineering. We describe a systematic framework for Human Views in a companion paper. In this paper, we illustrate how selected knowledge acquisition methods of cognitive engineering can be used to generate supplemental information for the Human Views needed to resolve the issue of lean staffing.

The Department of Defense (DOD) has struggled with the systems development, integration and interoperability for more than 30 years. Despite the Department of Defense Architecture Framework (DODAF) compliance requirement initiated 20 years ago to address these concerns, DOD agencies continue to struggle to deliver interoperable systems required for operations. The Monterey Phoenix (MP) approach shifts the paradigm underlying these DODAF views to focus on system behaviors and interactions rather than component functionality and the data flows between them. Although robust DODAF tools are available for model documentation, the MP Analyzer tool enables the system architect to reduce design complexity while quickly and easily exposing architectural flaws prior to implementation. This research defines DODAF models that can be generated using the MP approach to realize MP benefits such as automatic scenario generation and comply with DOD guidance. Using criteria established in this research, 16 of the 51 total DODAF models from five of the eight viewpoints are produced using data available in the MP approach. The value proposition to DOD programs is the ability to intercept design errors before they become costly system failures or rework requirements. Future research can validate the DODAF model generation from MP as it matures. http://archive.org/details/generationofdepa1094547314 Civilian, Space and Naval Warfare Systems Center Pacific Approved for public release; distribution is unlimited.

Integrated Sensor Architecture (ISA) is designed in response to stovepiped integration approaches. The design, based on the principles of Service Oriented Architectures (SOA) and Open Architectures, addresses the problem of integration, and is not designed for specific sensors or systems. The use of SOA and Open Architecture approaches has led to a flexible, extensible architecture. Using these approaches, and supported with common data formats, open protocol specifications, and Department of Defense Architecture Framework (DoDAF) system architecture documents, an integration-focused architecture has been developed. ISA can help move the Department of Defense (DoD) from costly stovepipe solutions to a more cost-effective plug-and-play design to support interoperability.

The Department of Defense Architecture Framework's (DoDAF) [1]data-centric development paradigm offers the potential for depth in architecture data and flexibility in presentation styles aimed at decision support. However the architecture development methodology advocated in versions 2.0 and upwards is a significant shift in approach, compared to prior versions. The framework specification, supporting literature and exemplar implementations fail to offer enough detail on a number of pertinent issues, among them executable modeling and architecture analysis, and the technology or tooling requirements which will facilitate their implementation. As part of ongoing research efforts aimed at addressing this gap this paper offers an overview of the literature on architecture modeling methodologies specifically tailored to the DoDAF, and propose the Modeling and Simulation Systems Development Framework (MS-SDF) [2] as a coherent and comprehensive approach for modeling within the DoDAF.

This paper presents the approach developed for the partial MASPS level document DO-344 “Operational and Functional Requirements and Safety Objectives” for the UAS standards. Previous RTCA1 work led to the production of an Operational Services Environment Description document, from which operational requirements were extracted and refined. Following the principles described in the Department of Defense Architecture Framework, the overall UAS architecture and major interfaces were defined. Interacting elements included the unmanned aircraft (airborne component), the ground control station (ground component), the Air Traffic Control (ATC), the Air Traffic Service besides ATC, other traffic in the NAS, and the UAS ground support. Furthering the level of details, a functional decomposition was produced prior to the allocation onto the UAS architecture. These functions cover domains including communication, control, navigation, surveillance, and health monitoring. The communication function addressed all elements in the UAS connected with external interfaces: the airborne component, the ground component, the ATC, the other traffic and the ground support. The control function addressed the interface between the ground control station and the unmanned aircraft for the purpose of flying in the NAS. The navigation function covered the capability to determine and fly a trajectory using conventional and satellite based navigation means. The surveillance function addressed the capability to detect and avoid collisions with hazards, including other traffic, terrain and obstacles, and weather. Finally, the health monitoring function addressed the capability to oversee UAS systems, probe for their status and feedback issues related to degradation or loss of performance. An additional function denoted ‘manage’ was added to the functional decomposition to complement the heath monitoring coverage and included manual modes for the operation of the UAS.

The SEAS ISR Architect maps Department of Defense Architecture Framework (DoDAF) views to military outcome and demonstrates a quick turnaround tool for the Initial Capabilities Document (ICD) phase of the Joint Capabilities Integration and Development System (JCIDS) process. The SEAS ISR Architect allows the user to reconfigure intelligence, surveillance, and reconnaissance (ISR) architectures within the DoD Architecture Framework, to parameterize a Systems Effectiveness and Analysis Simulation (SEAS) with a pre-loaded scenario and present a comparison of the warfighting effectiveness of a range of architectural alternatives based on multiple simultaneous theater simulations.

The System Entity Structure (SES) Enterprise Alternative Evaluator (SEAE) provides a “next step” to government mandated architecture frameworks by augmenting pictorial views into structured system representations for making design decisions. The Department of Defense Architecture Framework (DoDAF), a documentation tool used to portray operational concepts and supporting system details, is presently void of a malleable design description that structures processes and technologies for automatic enumeration of alternatives. DoDAF architecture views contain entity-like nodes; each representing documented processes and technologies. The SEAE leverages both DoDAF view nodes and computer science–based operations research to provide an evaluation technique that generates an operational concept's alternative architectures for future evaluation.

The Department of Defense Architecture Framework (DoDAF) provides architectural artifact examples for modeling complex system of systems within the information-centric and hardware-centric global battlespace theater. This framework is utilized by all U.S. government agencies and military branches that procure military hardware and plan for tomorrow's strategic evolution in the armed forces. This framework must be adopted by those business organizations who wish to market their products to the U.S. military. The models mandated by the DoDAF do not always align with the software development methods and production processes utilized in the commercial enterprises who position their products for acquisition into the network centric military markets. This is especially true for software industries where object oriented analysis and design methods have become entrenched as an industry standard. This paper analyzes object oriented development of complex systems and compares the artifacts produced through this method with artifacts produced through the structured architecture techniques described by the DoDAF. The comparison provides an evaluation of the commonality and gaps between both ideologies.

No industry is more demanding than aerospace-defense when it concerns the complete integration of software and hardware architectures. Tasked with defending our nascent Information Age economy, the aerospace-defense industry must be capable of waging Information Age warfare, whose key concepts include information superiority and network-centric warfare. By most quantitative metrics, aerospace-defense systems are among the largest and most complex ever constructed. The complexity of individual aerospace-defense systems (e.g., an aircraft) is frequently compounded when we integrate many of them together to form a system-of-systems (e.g., an air traffic control system) that satisfies more global requirements. This white paper describes a technical approach for improving how we specify system and system-of-systems architectures using frameworks in general, and the Department of Defense Architecture Framework (DoDAF) in particular. The model-driven approach to architectural frameworks explained here, which is based on UML™ 2.0, Telelogic TAU® Generation2™, and Telelogic DOORS®, can substantially improve productivity and quality. The information contained in this White Paper represents the current view of Telelogic on the issues discussed as of the date of publication. Because Telelogic must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Telelogic, and Telelogic cannot guarantee the accuracy of any information presented after the date of publication. This White Paper is for informational purposes only. Telelogic makes no warranties, express or implied, as to the information in this document. The example companies, organizations, products, people and events depicted herein are fictitious. No association with any real company, organization, product, person or event is intended or should be inferred. 2003–2004 Telelogic AB and PivotPoint Technology Corporation TAU, TAU Generation, TAUG2, TAU/Developer, TAU/Architect, TAU/Tester, TAU SDL Suite, DOORS, SYNERGY and DocExpress are either registered trademarks or trademarks of Telelogic. Unified Modeling Language, UML, Model Driven Architecture, and MDA are either registered trademarks or trademarks of Object Management Group. All other product and service names mentioned are the trademarks of their respective companies.

Since SOS (system-of-systems) has properties of independence, connectivity, attribution, diversity, and em ergent etc., traditional reliability modeling and assessment approaches are not fully suitable to SOS. Typically, SOS is task-oriented and a specified task of SOS will generate a particular logic process. Therefore, the reliability of a SOS can be evaluated by assessing the SOS tasks process. First, this paper uses ABM (Activity Based Methodology) method, which is based on DODAF (Department of Defense Architecture Framework), to decompose a SOS task into activity models. Second, a GERT (Graphical Evaluation and Re view Technique) hierarchical stochastic network is used to describe task process of SOS, which is dynamic and stochastic. Third, a reliability assessment method of SOS based on the SOS task process DES (Discrete Event Simulation) is presented. At last, a case study is given to illustrate the method.

This report was developed under a SBIR contract for topic AF103-165. This report describes the results a security assessment conducted on the Search and Rescue (SAR) enterprise. The purpose of the security assessment is to identify the operational risks to the SAR enterprise. In particular, those resulting from cyber attacks, identify the corresponding vulnerabilities, assess the criticality of the components, and recommend mitigations. SAR case study is a comprehensive illustration to the Department of Defense Architecture Framework (DoDAF) published as part of the international standard UML Profile for DoDAF and MoDAF (UPDM) by the Object Management Group (OMG). For the purposes of this assessment, the SAR is defined by International Aeronautical and Maritime Search and Rescue Manual (IAMSAR) and Canadian National Search and Rescue Manual. The security assessment described herein was one part of an overall project to develop a generic methodology and technology framework for computing a trustworthiness index (TI). A TI is a measure of confidence that risk is low in a claim about a system component supporting mission objectives

The U.S. Department of Defense Architecture Framework (DoDAF) provides a standard framework for transforming systems concepts into a consistent set of products containing the elements and relationships required to represent a complex operational system. However, without a human perspective, the current DoDAF does not account for the human performance aspects needed to calculate the human contribution to system effectiveness and cost. The Human Viewpoint gives systems engineers additional tools to integrate human considerations into systems development by facilitating identification and collection of human-focused data. It provides a way to include Human Systems Integration (HSI) constructs into mainstream acquisition and systems engineering processes by promoting early, frequent coordination of analysis efforts by both the systems engineering and HSI communities.

Long-term preservation of product data is imperative for many organizations. A product data archive should be designed to ensure information accessibility and understanding over time. Approaches, such as the Open Archival Information System Reference Model (OAIS RM) and the Audit and Certification of Trustworthy Digital Repositories (ACTDR), provide a framework for conceptually describing and evaluating archives. These approaches are generic and do not focus on particular contexts or content types such as product data. Moreover, these approaches offer no guidance on how to formally and comprehensively describe archival systems. Such descriptions should include the business activities that a product data archive has to support and the systems that interact with the archive. Enterprise architecture provides a means to describe systems in their potentially complex environments. This paper proposes a holistic approach to formally describe the architecture and the environment of archival systems. This approach relies on the formal representation of the preservation terminology, including OAIS concepts, using the Department of Defense Architecture Framework (DoDAF). The approach covers the various interactions of other business functions with the archive and the information models necessary to ensure preservation and accessibility of product data. This approach is a step towards a reference architecture for the formal description of archival systems. To demonstrate the approach, we formally describe the ingest of product data related to a ship. The resulting description uses the preservation terminology defined in the OAIS Reference Model. It facilitates the understanding of how the preservation solution is actually implemented and provides evidence that the solution is able to preserve product data and make it accessible.

C4I (command, control, communication, computer and intelligence) are complex information systems designed to achieve mission objectives through better situational awareness and information superiority. C4I systems are system of systems (SOS), SOS comprised of independent constituent systems that interoperate with other systems to achieve specific mission objectives. In this paper we propose a framework for the interoperability of C4I Systems that covers key issues and challenges related to interoperability of heterogeneous C4I systems such as complexity, criticality and Information Exchanges Requirements (IER). The frameworks make use of department of defense architecture framework (DOAF) to describe data exchange requirements, source adapters, message translation, routing and destination adapters.

The C4ISR Architecture Framework document issued by the Department of Defense specifies three views of an information architecture and defines a set of products that describe each view. These architecture views are to serve as the basis for C4ISR system development and acquisition. The Framework does not provide a process for architecture design. In this paper, information architectures are described in the context of Structured Analysis, and then the architecture views of the Framework and the related products are interpreted in that context. A methodology for architecture design is developed that is then implemented using Structured Analysis and object orientation in two companion papers. © 2000 John Wiley & Sons, Inc. Syst Eng 3: 225‐247, 2000

Currently, Department of Defense Architecture Framework (DoDAF) 2.0 is widely used in many aspects of the architecture-related modeling fields. Due to the highly complex structure of architecture, its reliability became a pivotal issue. However, DoDAF 2.0 is lack of a specific viewpoint to model the reliability of the architecture. This paper introduces an approach to deal with reliability modeling method related missions posed by Equipment System (ES), which is an obvious characterized architecture. OV-1, OV-5a and OV-6c of DoDAF 2.0's operational viewpoint are extracted and extended as the modeling framework. Use case diagram, class diagram and sequence diagram of Unified Modeling Language (UML) are picked to present the products mentioned. The study also regulates a series of standards for each extended product in detail, in order to collect requisite reliability-related parameters for further analysis and calculation. Later, the proposed model is applied to an ES as an example to verify its availability. Keywords-reliability modeling; equipment system; mission reliability; equipment system; operational viewpoint; DoDAF 2.0