Downloads & Free Reading Options - Results

Four salvage ships and four ocean-going towing ships are maintained and operated by the Military Sealift Command (MSC) for the U.S. Navy. In 2019, the first T-ATF ships will reach the end of their 40-year life expectancy. The program manager for these vessels has a set of top-level performance characteristics that are deemed as desirable requirements for a new ship class, encapsulating both legacy ship class capabilities. The DoD has shifted defense planning from the specific service requirements generated system (RGS) acquisition to the Joint Capabilities Integration and Development System (JCIDS) approach that focuses more on how adversaries fight rather than whom they are fighting. This thesis explores how to use systems architecting to incorporate the capabilities derived from strategic guidance into a Department of Defense Architecture Framework (DODAF) product. The design tool, CORE, is used to explain the architecting methodology and produce DODAF v1.5 system models for decision making and acquisition requirement generation.

Command, Control, Communications, Computers, and Intelligence (C4I) systems, each originally designed to address a single warfighting function, have been assembled into an interdependent C4I System of Systems (SoS). The C4I SoS continues to evolve, without overarching capabilities-based performance requirements. Without requirements, there is no practical, repeatable, and objective process to assess changes to the SoS. This project applied a disciplined systems engineering process to design a Joint C4I Capability Certification Measures (JC3M) system. JC3M can be used to define performance measures for a C4I SoS, determine baseline SoS performance, assess proposed SoS changes, and monitor SoS performance. Modeling and simulation tools were used to project the performance of three existing alternatives and two new alternatives. A Life Cycle Cost Estimate (LCCE) was generated for each alternative. An Analysis of Alternatives compared performance and cost. The Joint Test and Evaluation Methodology Capability Test Methodology (JTEM CTM) was projected to provide slightly better performance than other alternatives, at the median LCCE. The results were a recommendation to monitor JTEM CTM as it completes development, and employ the JTEM CTM in a C4I SoS evaluation to confirm its estimated cost and performance.

Command, Control, Communications, Computers, and Intelligence (C4I) systems, each originally designed to address a single warfighting function, have been assembled into an interdependent C4I System of Systems (SoS). The C4I SoS continues to evolve, without overarching capabilities-based performance requirements. Without requirements, there is no practical, repeatable, and objective process to assess changes to the SoS. This project applied a disciplined systems engineering process to design a Joint C4I Capability Certification Measures (JC3M) system. JC3M can be used to define performance measures for a C4I SoS, determine baseline SoS performance, assess proposed SoS changes, and monitor SoS performance. Modeling and simulation tools were used to project the performance of three existing alternatives and two new alternatives. A Life Cycle Cost Estimate (LCCE) was generated for each alternative. An Analysis of Alternatives compared performance and cost. The Joint Test and Evaluation Methodology Capability Test Methodology (JTEM CTM) was projected to provide slightly better performance than other alternatives, at the median LCCE. The results were a recommendation to monitor JTEM CTM as it completes development, and employ the JTEM CTM in a C4I SoS evaluation to confirm its estimated cost and performance.

As a Systems Engineering instructor at DAU, I have engaged in a number of discussions and debates, both in and out of the classroom, on architecture in systems acquisition. Over time, I began to see there was a real lack of consensus about the importance of architecture, how it fits in to the Defense Acquisition System (DAS), and how it relates to system engineering.

No abstract available

In 2010, the USMC changed its Marine Corps Planning Process (MCPP) to include operational design in response to direction from the Commander of United States Joint Forces Command (USJFCOM). This updated process however has proven to be misunderstood and fundamentally no different from the previous edition based upon the classical decision making model. This thesis therefore presents an alternative planning process for the United States Marine Corps. This thesis uses the foundations of systems architecting to redefine operational design as operational architecting and presents a detailed operational architecting process that translates strategic guidance into an operational design. This operational design then becomes the starting point for the traditional military planning process. The alternative planning process describes operational architecting as a distinct activity from operational planning but provides for a seamless transition between both activities and for multiple iterations if needed. The thesis recommends this process as a baseline for further refinement and experimentation as the USMC further develops its planning theory and doctrine.

NASA is planning a series of short and long duration human and robotic missions to explore the Moon and then Mars. A key objective of the missions is to grow, through a series of launches, a system of systems communication, navigation, and timing infrastructure at minimum cost while providing a network-centric infrastructure that maximizes the exploration capabilities and science return. There is a strong need to use architecting processes in the mission pre-formulation stage to describe the systems, interfaces, and interoperability needed to implement multiple space communication systems that are deployed over time, yet support interoperability with each deployment phase and with 20 years of legacy systems. In this paper we present a process for defining the architecture of the communications, navigation, and networks needed to support future space explorers with the best adaptable and evolable network-centric space exploration infrastructure. The process steps presented are: 1) Architecture decomposition, 2) Defining mission systems and their interfaces, 3) Developing the communication, navigation, networking architecture, and 4) Integrating systems, operational and technical views and viewpoints. We demonstrate the process through the architecture development of the communication network for upcoming NASA space exploration missions.

Maritime domain awareness (MDA) entails knowing what is happening in the oceans and waterways that could affect the security or environment of the United States. With a focus on potential attack vessels (PAV) as threats in the maritime domain, a multi-domain SoS is needed to exploit and integrate information from multiple sources, including sensors, databases, and intelligence, to provide reconnaissance, surveillance, and information used in the formulation of a common operational picture (COP), a tool to effect maritime domain awareness. In this thesis the best architecture of net-centric operations (NCO) multidomain system of systems (SoS) for MDA is determined, employing an integrated systems engineering methodology for analyzing and ranking systems of systems architectures. This methodology involves the use of process modeling, modeling of an SoS with the systems modeling language (SysML), and subsequent conversion of the resulting SysML diagrams into an ExtendTM executable simulation model, used in a simulative study carried out to evaluate three multi-domain awareness SoS architecture alternatives in terms of the time to establish a COP and the probability of COP accuracy. Of the three architecture alternatives, a conceptual SoS whose constituting systems are connected in a distributed network with a high degree of connectivity is found to take the least amount of time to establish a COP and to have a high probability of COP accuracy. It can thus be considered to be the best of the three MDA SoS architecture alternatives. The results indicate that, in a distributed network, which is the backbone of net-centric operations, direct links between the sensors and the coalition C2 center shorten the communications delay and hence reduce the time to establish a COP. The accuracy of the information to be combined at the coalition C2 center is necessary for having a high probability of COP accuracy. Furthermore, the integrated systems engineering methodology for analyzing SoS architectures provides an effective framework and tool for designing and analyzing complex SoS in general and NCO MDA SoS in particular.

Maritime domain awareness (MDA) entails knowing what is happening in the oceans and waterways that could affect the security or environment of the United States. With a focus on potential attack vessels (PAV) as threats in the maritime domain, a multi-domain SoS is needed to exploit and integrate information from multiple sources, including sensors, databases, and intelligence, to provide reconnaissance, surveillance, and information used in the formulation of a common operational picture (COP), a tool to effect maritime domain awareness. In this thesis the best architecture of net-centric operations (NCO) multidomain system of systems (SoS) for MDA is determined, employing an integrated systems engineering methodology for analyzing and ranking systems of systems architectures. This methodology involves the use of process modeling, modeling of an SoS with the systems modeling language (SysML), and subsequent conversion of the resulting SysML diagrams into an ExtendTM executable simulation model, used in a simulative study carried out to evaluate three multi-domain awareness SoS architecture alternatives in terms of the time to establish a COP and the probability of COP accuracy. Of the three architecture alternatives, a conceptual SoS whose constituting systems are connected in a distributed network with a high degree of connectivity is found to take the least amount of time to establish a COP and to have a high probability of COP accuracy. It can thus be considered to be the best of the three MDA SoS architecture alternatives. The results indicate that, in a distributed network, which is the backbone of net-centric operations, direct links between the sensors and the coalition C2 center shorten the communications delay and hence reduce the time to establish a COP. The accuracy of the information to be combined at the coalition C2 center is necessary for having a high probability of COP accuracy. Furthermore, the integrated systems engineering methodology for analyzing SoS architectures provides an effective framework and tool for designing and analyzing complex SoS in general and NCO MDA SoS in particular.

Maritime domain awareness (MDA) entails knowing what is happening in the oceans and waterways that could affect the security or environment of the United States. With a focus on potential attack vessels (PAV) as threats in the maritime domain, a multi-domain SoS is needed to exploit and integrate information from multiple sources, including sensors, databases, and intelligence, to provide reconnaissance, surveillance, and information used in the formulation of a common operational picture (COP), a tool to effect maritime domain awareness. In this thesis the best architecture of net-centric operations (NCO) multidomain system of systems (SoS) for MDA is determined, employing an integrated systems engineering methodology for analyzing and ranking systems of systems architectures. This methodology involves the use of process modeling, modeling of an SoS with the systems modeling language (SysML), and subsequent conversion of the resulting SysML diagrams into an ExtendTM executable simulation model, used in a simulative study carried out to evaluate three multi-domain awareness SoS architecture alternatives in terms of the time to establish a COP and the probability of COP accuracy. Of the three architecture alternatives, a conceptual SoS whose constituting systems are connected in a distributed network with a high degree of connectivity is found to take the least amount of time to establish a COP and to have a high probability of COP accuracy. It can thus be considered to be the best of the three MDA SoS architecture alternatives. The results indicate that, in a distributed network, which is the backbone of net-centric operations, direct links between the sensors and the coalition C2 center shorten the communications delay and hence reduce the time to establish a COP. The accuracy of the information to be combined at the coalition C2 center is necessary for having a high probability of COP accuracy. Furthermore, the integrated systems engineering methodology for analyzing SoS architectures provides an effective framework and tool for designing and analyzing complex SoS in general and NCO MDA SoS in particular.

Human-system interactions have been largely overlooked in the traditional systems engineering process. Awareness of human factors (HF) has increased in the past few years, but the involvement of HF specialists is still often too little and too late. In systems involving long-duration human space flight, it is essential that the human component be properly considered in the initial architectural definition phase, as well as throughout the system design process. HF analysis must include not only the strengths and limitations of humans in general, but the variability between individuals and within an individual over time, and the dynamics of group interactions.

No abstract available

The National Aeronautics and Space Administration (NASA) and the Department of Defense (DoD) are planning Space System of Systems (SoS) to address the new challenges of space exploration, defense, communications, navigation, Earth observation, and science. In addition, these complex systems must provide interoperability, enhanced reliability, common interfaces, dynamic operations, and autonomy in system management. Both NASA and the DoD have chosen to meet the new demands with high data rate communication systems and space Internet technologies that bring Internet Protocols (IP), routers, servers, software, and interfaces to space networks to enable as much autonomous operation of those networks as possible. These technologies reduce the cost of operations and, with higher bandwidths, support the expected voice, video, and data needed to coordinate activities at each stage of an exploration mission. In this paper, we discuss, in a generic fashion, how the architectural approaches and processes are being developed and used for defining a hypothetical communication and navigation networks infrastructure to support lunar exploration. Examples are given of the products generated by the architecture development process.

The European Telecommunications Standards Institute (ETSI) released a set of specifications to define a restful architecture for enabling seamless service provisioning across heterogeneous Machine-to-Machine (M2M) systems. The current version of this architecture is strongly centralized, thus requiring new enhancements to its scalability, fault tolerance, and flexibility. To bridge this gap, herein it is presented an Overlay Service Capability Layer, based on Information Centric Networking design. Key features, example use cases and preliminary performance assessments are also discussed to highlight the potential of our approach.

The European Telecommunications Standards Institute (ETSI) released a set of specifications to define a restful architecture for enabling seamless service provisioning across heterogeneous Machine-to-Machine (M2M) systems. The current version of this architecture is strongly centralized, thus requiring new enhancements to its scalability, fault tolerance, and flexibility. To bridge this gap, herein it is presented an Overlay Service Capability Layer, based on Information Centric Networking design. Key features, example use cases and preliminary performance assessments are also discussed to highlight the potential of our approach.

This research identifies the information/data required to perform a safety assessment for large-scale systems integration. From these required safety-related information/data, and the utilization of system engineering processes and practices, a safety assessment architecture is developed. As a result, the risk of known hazards is mitigated to as low as reasonably practical (ALARP) and the system health of these large-scale system integrations is improved throughout the system's life cycle. The thesis first identifies the current gap in system safety assessment for large-scale system integrations, especially in the area of Commercial of the Shelf (COTS) and Non-Developmental Item (NDI) systems integration. Next, with reference to the DoD system life cycle process, a COTS/NDI system integration life cycle process model is proposed. In addition, in line with the DoD policy to have a joint weapon system safety review board, a system safety functional hierarchy is then created. Using the functional hierarchy created, more detailed sub-functions and measures of effectiveness for system safety assessment are then analyzed. Finally, a hazard list table is proposed as a tool to be used in relation to the system safety assessment functional hierarchy so as to achieve the objective to identify, mitigate, trace and accept all residual risks associated with the large-scale system integration throughout its life cycle. A case example of the Harpoon Weapon System (HWS) safety assessment on a ship platform is used to further explain the usage and process of generating, maintaining and tracking the hazard list table.

The aviation literature gives relatively little guidance to practitioners about the specifics of architecting systems for safety, particularly the impact of architecture on allocating safety requirements, or the relative ease of system assurance resulting from system or subsystem level architectural choices. As an exemplar, this paper considers common architectural patterns used within traditional aviation systems and explores their safety and safety assurance implications when applied in the context of integrating artificial intelligence (AI) and machine learning (ML) based functionality. Considering safety as an architectural property, we discuss both the allocation of safety requirements and the architectural trade-offs involved early in the design lifecycle. This approach could be extended to other assured properties, similar to safety, such as security. We conclude with a discussion of the safety considerations that emerge in the context of candidate architectural patterns that have been proposed in the recent literature for enabling autonomy capabilities by integrating AI and ML. A recommendation is made for the generation of a property-driven architectural pattern catalogue.

The United States Navy andMarine Corps have identified capability gaps in the areas of collecting Intelligence, Surveillance, Reconnaissance, and Targeting (ISR&T) data and employing fires during amphibious operations. The Littoral Combat Ship (LCS) presents an opportunity to deploy specific mission capabilities in the amphibious theater. This paper identifies the operational, functional, and physical architecture of an LCS Amphibious Warfare Mission Package (LAMP) necessary to provide capabilities associated with ISR&T data collect and fires employment. Physical architecture configurations are evaluated using a discrete-event model. Cost estimates for each alternative are presented in order to identify the LAMP architecture that provides the most cost-effective solution for providing capabilities associated with ISR&T data collection and fires employment. This paper concludes by identifying potential LAMP assets that would provide cost-effective support of amphibious operations. Four feasible alternatives are ultimately identified as cost-effective solutions, with LCCEs ranging from $105.49M and $188.22M and providing varying levels of effectiveness in terms of average engagement time and percentage of threats successfully affected.

A major challenge to the successful planning and evolution of an acknowledged System of Systems (SoS) is the current lack of understanding of the impact that the presence or absence of a set of constituent systems has on the overall SoS capability. Since the candidate elements of an SoS are fully functioning, stand-alone Systems in their own right, they have goals and objectives of their own to satisfy, some of which may compete with those of the overarching SoS. These system-level concerns drive decisions to participate (or not) in the SoS. Individual systems typically must be requested to join the SoS construct, and persuaded to interface and cooperate with other Systems to create the new capability of the proposed SoS. Current SoS evolution strategies lack a means for modeling the impact of decisions concerning participation. The goal of this research is to model the evolution of the architecture of an acknowledged SoS that accounts for the ability and willingness of constituent systems to support the SoS capability development. Since DoD Systems of Systems (SoS) development efforts do not typically follow the normal program acquisition process described in DoDI 5000.02, the Wave Model proposed by Dahmann and Rebovich is used as the basis for this research on SoS capability evolution. The Wave Process Model provides a framework for an agent-based modeling methodology, which is used to abstract the non-utopian behavioral aspects of the constituent systems and their interactions with the SoS. In particular, the research focuses on the impact of individual system behavior on the SoS capability and architecture evolution processes. A proof of concept agent-based model (ABM) of the system interactions is developed and integrated with a genetic algorithm (GA) to explore the potential architectural design space, using a fuzzy associative memory (FAM) to evaluate candidate architectures for simulating SoS creation and evolution.

Maritime domain awareness (MDA) entails knowing what is happening in the oceans and waterways that could affect the security or environment of the United States. With a focus on potential attack vessels (PAV) as threats in the maritime domain, a multidomain system of systems (SoS) is needed to exploit and integrate information from multiple sources, including sensors, databases, and intelligence, to provide reconnaissance, surveillance, and information used in the formulation of a common operational picture (COP), which is a tool to effect maritime domain awareness. In this thesis, the best architecture of net-centric operations (NCO) multidomain SoS for MDA is determined, employing an integrated systems engineering methodology for analyzing and ranking system of systems architectures. This methodology involves the use of process modeling, modeling of an SoS with the systems modeling language (SysML), and subsequent conversion of the resulting SysML diagrams into an Extend (trademark) executable simulation model used in a simulative study conducted to evaluate three multidomain awareness SoS architecture alternatives in terms of the time to establish a COP and the probability of COP accuracy. Of the three architecture alternatives, a conceptual SoS whose constituent systems are connected in a distributed network with a high degree of connectivity is found to take the least amount of time to establish a COP and to have a high probability of COP accuracy. It can thus be considered to be the best of the three MDA SoS architecture alternatives. The results indicate that, in a distributed network, which is the backbone of net-centric operations, direct links between the sensors and the coalition C2 center reduce the time to establish a COP. The integrated systems engineering methodology for analyzing SoS architectures provides an effective framework and tool for designing and analyzing complex SoS in general and NCO MDA SoS in particular.

This research identifies the information/data required to perform a safety assessment for large-scale systems integration. From these required safety-related information/data, and the utilization of system engineering processes and practices, a safety assessment architecture is developed. As a result, the risk of known hazards is mitigated to as low as reasonably practical (ALARP) and the system health of these large-scale system integrations is improved throughout the system's life cycle. The thesis first identifies the current gap in system safety assessment for large-scale system integrations, especially in the area of Commercial of the Shelf (COTS) and Non-Developmental Item (NDI) systems integration. Next, with reference to the DoD system life cycle process, a COTS/NDI system integration life cycle process model is proposed. In addition, in line with the DoD policy to have a joint weapon system safety review board, a system safety functional hierarchy is then created. Using the functional hierarchy created, more detailed sub-functions and measures of effectiveness for system safety assessment are then analyzed. Finally, a hazard list table is proposed as a tool to be used in relation to the system safety assessment functional hierarchy so as to achieve the objective to identify, mitigate, trace and accept all residual risks associated with the large-scale system integration throughout its life cycle. A case example of the Harpoon Weapon System (HWS) safety assessment on a ship platform is used to further explain the usage and process of generating, maintaining and tracking the hazard list table.

The goal of this research is to model the evolution of the architecture of an acknowledged SoS that accounts for the ability and willingness of constituent systems to support the SoS capability development. Since DoD Systems of Systems (SoS) development efforts do not typically follow the normal program acquisition process described in DoDI 5000.02, the Wave Model proposed by Dahmann and Rebovich is used as the basis for this research on SoS capability evolution. The Wave Process Model provides a framework for an agent-based modeling methodology, which is used to abstract the non-utopian behavioral aspects of the constituent systems and their interactions with the SoS. In particular, the research focuses on the impact of individual system behavior on the SoS capability and architecture evolution processes.

The United States Navy and Marine Corps have identified capability gaps in the areas of collecting Intelligence, Surveillance, Reconnaissance, and Targeting (ISR&T) data and employing fires during amphibious operations. The Littoral Combat Ship (LCS) presents an opportunity to deploy specific mission capabilities in the amphibious theater. This paper identifies the operational, functional, and physical architecture of an LCS Amphibious Warfare Mission Package (LAMP) necessary to provide capabilities associated with ISR&T data collect and fires employment. Physical architecture configurations are evaluated using a discrete-event model. Cost estimates for each alternative are presented in order to identify the LAMP architecture that provides the most cost-effective solution for providing capabilities associated with ISR&T data collection and fires employment. This paper concludes by identifying potential LAMP assets that would provide cost-effective support of amphibious operations. Four feasible alternatives are ultimately identified as cost-effective solutions, with LCCEs ranging from $105.49M and $188.22M and providing varying levels of effectiveness in terms of average engagement time and percentage of threats successfully affected.

Four salvage ships and four ocean-going towing ships are maintained and operated by the Military Sealift Command (MSC) for the U.S. Navy. In 2019, the first T-ATF ships will reach the end of their 40-year life expectancy. The program manager for these vessels has a set of top-level performance characteristics that are deemed as desirable requirements for a new ship class, encapsulating both legacy ship class capabilities. The DoD has shifted defense planning from the specific service requirements generated system (RGS) acquisition to the Joint Capabilities Integration and Development System (JCIDS) approach that focuses more on how adversaries fight rather than whom they are fighting. This thesis explores how to use systems architecting to incorporate the capabilities derived from strategic guidance into a Department of Defense Architecture Framework (DODAF) product. The design tool, CORE, is used to explain the architecting methodology and produce DODAF v1.5 system models for decision making and acquisition requirement generation.

Four salvage ships and four ocean-going towing ships are maintained and operated by the Military Sealift Command (MSC) for the U.S. Navy. In 2019, the first T-ATF ships will reach the end of their 40-year life expectancy. The program manager for these vessels has a set of top-level performance characteristics that are deemed as desirable requirements for a new ship class, encapsulating both legacy ship class capabilities. The DoD has shifted defense planning from the specific service requirements generated system (RGS) acquisition to the Joint Capabilities Integration and Development System (JCIDS) approach that focuses more on how adversaries fight rather than whom they are fighting. This thesis explores how to use systems architecting to incorporate the capabilities derived from strategic guidance into a Department of Defense Architecture Framework (DODAF) product. The design tool, CORE, is used to explain the architecting methodology and produce DODAF v1.5 system models for decision making and acquisition requirement generation.

Three areas of architecting science were investigated: (1) Tradespace exploration is a conceptual design tool used to compare thousands of designs. Flexibility, the ability to dynamically change systems to mitigate risk or leverage opportunity, is difficult to assess within static tradespaces. A metric to identify valuably flexible designs in a tradespace, Value Weighted Filtered Outdegree, was developed and applied to a satellite radar and ORS case, and shown to identify designs that would not have been identified with existing tradespace metrics. (2) One cited mechanism for accommodating uncertainty in design is to embed flexibility. A new framework was developed in the research to aid the design of a flexible system. Change propagation analysis was extended for analysis of systems with heterogeneous relationships between components, using filtered outdegree analysis to quantify flexibility. (3) Decision makers utilize multiple criteria and many levels of reasoning to understand complex multivariate data. They can be aided by direct-perception decision-support systems of configural rather than separable displays. An experiment compared performance across different levels of reasoning, finding that configural display promoted better performance and more efficient eye fixation patterns at the highest level of reasoning than the separable display, and was the subjective tool of choice.

The Air Force Life Cycle Management Center (AFLCMC) Hanscom Operating Location (Hanscom-OL) implemented a methodology called Domain Systems Engineering, Architecting and Analysis (DSEA&A) to enable the identification and resolution of domain-level problems or opportunities related to affordability, efficiency, and effectiveness (AE&E). The goal of DSEA&A, also referred to as domain analytics (DA), is to consider and assess a set of potential solutions to resolve problems identified by one or more domain stakeholders. The scope of a DSEA&A effort can be wholly contained within a Program Executive Officer's (PEO) portfolio or can span multiple PEOs portfolios. DSEA&A was developed in response to AF higher headquarters desires to identify and deliver cross-cutting, affordable solutions in a timely manner. This document provides a high-level introduction to DSEA&A. It highlights one way to do DSEA&A based on lessons learned in applying these concepts to acquisitions at the Hanscom Operating Location (Hanscom-OL) of the AF LCMC. This is a set of guidelines and not a prescription. DSEA&A builds on traditional systems engineering, architecture, and analysis methodologies. Individual DSEA&A activities must be considered relative to the domain and problem at hand and should be tailored as needed. This document is targeted primarily to DSEA&A practitioners aka domain engineers. It is also suitable as background information for a wide range of audiences including leadership, policy makers, users, and acquisition personnel. This document addresses only the additional effort required to do DSEA&A. It does not address how to do traditional systems engineering, basic architecting and analysis, system implementation, program management, etc. The reader is presumed to have a basic understanding of these related areas.

The goal of this research is to model the evolution of the architecture of an acknowledged Systems of Systems (SoS) that accounts for the ability and willingness of constituent systems to support the SoS capability development. Since DoD SoS development efforts do not typically follow the program of record acquisition process described in DoDI 5000.02, the Wave Model proposed by Dahmann and Rebovich is used as the basis for this research on SoS capability evolution. The Wave Process Model provides a framework for an agent-based modeling methodology, which is used to abstract the non-utopian behavioral aspects of the constituent systems and their interactions with the SoS. In particular, the research focuses on the impact of individual system behavior on the SoS capability and architecture evolution processes.

This paper will attempt to find out whether the fundamentals of systems architecture are beneficial to a better understanding of the elements and goals of operational design as understood throughout the Department of Defense, and to provide a sound basis for its inclusion in the Marine Corps Planning Process (MCPP). On 24 August 2010, the United States Marine Corps published an update to Marine Corps Warfighting Publication (MCWP) 5-1, Marine Corps Planning Process (MCPP). This publication replaced and superseded the original MCWP 5-1, which was published on 5 January 2000 and was an attempt to incorporate operational design into the first step of MCPP. The major change renamed the first step to problem framing, attempting to emphasis a greater awareness and understanding of the background and environment in which a military operation would occur. This paper will first outline the fundamental USMC doctrine related to the development of the MCPP, describe the changes and emphasis to the MCPP from January 2000 to August 2010, evaluate the current MCPP in light of literature published on operational design, and compare and contrast the MCPP and operational design with the civilian discipline of systems architecting. The author argues that the discipline of' systems architecture will offer a gateway to a better understandinq of operational design and a possible foundation for its incorporation into the MCPP.

Service orientation is an approach to software systems development that has become a popular way to implement distributed, loosely coupled systems, because it offers such features as standardization, platform independence, well-defined interfaces, and tool support that enables legacy system integration. From a quality attribute point of view, the primary drivers for service orientation adoption are interoperability and modifiability. However, a common misconception is that an architecture that uses a service-oriented approach can achieve these qualities by simply putting together a set of vendor products that provide an infrastructure and then using this infrastructure to expose a set of reusable services to build systems. In reality, there are many architectural decisions that need to be made. An architectural decision that promotes interoperability or modifiability can negatively impact other qualities, such as availability, reliability, security and performance. The goal of this report is to present general guidelines for architecting service-oriented systems, how common service-oriented system components support these principles, and the effect that these principles and their implementation have on system quality attributes.

In 2010, the USMC changed its Marine Corps Planning Process (MCPP) to include operational design in response to direction from the Commander of United States Joint Forces Command (USJFCOM). This updated process however has proven to be misunderstood and fundamentally no different from the previous edition based upon the classical decision making model. This thesis therefore presents an alternative planning process for the United States Marine Corps. This thesis uses the foundations of systems architecting to redefine operational design as operational architecting and presents a detailed operational architecting process that translates strategic guidance into an operational design. This operational design then becomes the starting point for the traditional military planning process. The alternative planning process describes operational architecting as a distinct activity from operational planning but provides for a seamless transition between both activities and for multiple iterations if needed. The thesis recommends this process as a baseline for further refinement and experimentation as the USMC further develops its planning theory and doctrine.