Kevin MacG. Adams

Systems Theory as the Foundation for Understanding Systems

As currently used, systems theory is lacking a universally agreed upon definition. The purpose of this paper is to offer a resolution by articulating a formal definition of systems theory. This definition is presented as a unified group of specific propositions which are brought together by way of an axiom set to form a system construct: systems theory. This construct affords systems practitioners and theoreticians with a prescriptive set of axioms by which a system must operate; conversely, any set of entities identified as a system may be characterized by this set of axioms. Given its multidisciplinary theoretical foundation and discipline-agnostic framework, systems theory, as it is presented here, is posited as a general approach to understanding system behavior.

Managing risk in software maintenance

Software risk management in maintenance differs in major ways from risk management in development. Risk opportunities are more frequent, risks come from more diverse sources, and projects have less freedom to act on them. The authors describe how they dealt with these differences in a large US Navy software maintenance organization.

System of Systems Engineering Requirements: Challenges and Guidelines

Abstract: Traditional systems engineering (SE) has been successful in developing requirements that are objective, verifiable, and definitive. These requirements are chiefly related to technical or technological issues necessary to achieve a desired level of system performance. In contrast, System of Systems Engineering (SoSE) engages a more complex and holistic problem space, including organizational, managerial, policy, human/social, and political dimensions that exist in conditions of emergence, ambiguity, and uncertainty; therefore, the traditional SE requirements paradigm must be called into question. At present, the SoSE requirements paradigm has not reached the level of maturity or sophistication experienced by traditional SE. It is a miscalculation to expect successful approaches for SE requirements development to enjoy the same level of success when applied directly to the SoSE problem domain. The purpose of this article is to explore the nature of requirements from an SoSE perspective. First, the article establishes a foundation for differences between the SE and SoSE problem domains. Second, the traditional SE paradigm governing requirements is developed. Third, the specific nature of the SoSE problem domain implications for requirements is established. Fourth, guidelines for requirements within SoSE efforts are provided. The article concludes with key implications for the development and use of requirements in the SoSE field by practitioners.

Systems principles: foundation for the SoSE methodology

The application of systems theory and systems thinking to the design and management of complex systems of systems and their associated life cycles can provide a valuable lens for the emerging methods in system of systems engineering (SoSE). This paper is organised to show how the valuable concepts of systems theory and systems thinking as related to SoSE, can provide the formalism and framework for the inclusion of systems concepts, fundamentals, and language as the foundation for a SoSE methodology.

The RQ-Tech methodology: a new paradigm for conceptualizing strategic enterprise architectures

The purpose of this paper is to report on a new system-theoretic based methodology and corresponding model for Enterprise Architecture development. This model captures the essence of the strategic, conceptual, doctrinal layer of the organization. Reusable Quality Technical Architectures (RQ-Tech) graphically reveals a comprehensive array of enterprise decision alternatives in easily understandable views; all while maintaining the hyperlinks to its provenance in strategic authoritative documentation. The RQ-Tech method has combined the practice of Enterprise Architectures with a modern perspective grounded in Systems Theory and the theory regarding the computer science-oriented Semantic Web. This recombination results in a distinctive methodology for developing models. This new methodology supports the conclusion that system-specific solutions produce islands of technology and can be prevented by employing better enterprise change planning. A review of the literature in three major areas illustrates the ov...

Overview of the systems of systems engineering methodology

There is no widely accepted approach to conducting system of systems engineering (SoSE) efforts. The SoSE methodology is a rigorous engineering analysis that invests heavily in the understanding and framing of the problem under study. By conducting a rigorous engineering analysis of the problem and its associated context, the SoSE methodology minimises the chance that a Type III error may be committed early on in a SoSE analysis. The SoSE methodology is a guide to be adapted to the particular circumstances that define its application. The theoretical and philosophical grounding for the SoSE methodology derives from systems theory. The systems principles, laws, and concepts are central to everything that follows in application of the SoSE methodology to a specific problem domain. The SoSE methodology contains seven perspectives and 23 constituent elements that serve to structure the application of the perspectives during methodology application. Each perspective is essential to a holistic treatment of the problem, with all perspectives iteratively applied and existing in relationship to every other, informing and informed by each.

Towards Intelligence-Based Systems Engineering and System of Systems Engineering

This introductory chapter defines intelligence-based systems with focus on semantic systems, simulation systems, and intelligent agents. Semantic systems define the foundation to communicate systems engineering challenges using logic, simulation systems introduce the dynamic component, and intelli- gent agents can introduce alternatives roles. It then gives an overview of tradi- tional systems engineering as well as system of systems engineering showing the need to emphasize the system of systems perspective in modern engineering approaches. Finally, both views are aligned, providing a scope for intelligence- based systems engineering and the contributions of the following book chapters are summarized in relationship to this scope.

Perspective 1 of the SoSE methodology: framing the system under study

The first perspective in the system of systems engineering (SoSE) methodology is to ensure that the engineering analysis is supported by an explicit understanding and framing of the problem under study. By explicitly framing the problem and its associated context, the SoSE methodology minimises the chance of a Type III error (i.e., correctly rejects the null hypothesis for the wrong reason) committed at study’s outset. This paper addresses the methodology’s Perspective 1, framing the system under study, and the nine component execution elements serving to operationalise it. The paper will illustrate those elements as tools with which SoS problems may be framed in terms of their most prominent contextual and environmental influences.

The US Navy carrier strike group as a system of systems

A US Navy carrier strike group (CSG) is an important element of US policy projection through military assets. The CSG is a system of systems (SoS) representing both an organisation of people and a collection of ships, aircraft, and support equipment designed to support US global interests. The CSG is a metasystem composed of a number of separate subsystems (vessels, air wing, and staffs), and it fits the classic definition of a SoS proposed by Maier (1999). Command, control, communications, computers, intelligence, surveillance, and reconnaissance (C4ISR) subsystems in a carrier strike group (CSG) are a SoS supporting the larger CSG. This paper will introduce the reader to the US Navy CSG. It will include a summary of components in the CSG SoS, the SoSs mission, a description of the component systems, how the SoS is organised, and how the metasystem is purposefully directed by its command, control, communications, computers, intelligence, surveillance, and reconnaissance (C4ISR) subsystems. The paper serves as an introduction to this issues following papers that will use emerging system of systems engineering (SoSE) principles and methods to provide a more holistic frame of reference for understanding CSG C4ISR as a SoS.

Stakeholders in systems problems

Stakeholders exist at the centre of all systems problems and are the principal contributors to the solution of these problems. We provide an approach for classifying stakeholders and determining an appropriate level of action to take with respect to these stakeholders that combines the power, legitimacy and urgency typology with a stakeholder attitude classification schema. The newly developed stakeholder strategy is a matrix that combines stakeholder attitude and classification. This matrix serves as a guide for the application of resources in support of stakeholder involvement. This technique provides systems practitioners with a means to deal with stakeholders effectively.