SOS Architecture Design and Analysis

**References**

15(3):36-45

2013

VA, US; 2003

**50**

[1] David ES, Michael B, Obaid Y. Systems Engineering and Program Management-Trends and Costs for Aircraft and Guided Weapons Programs. United States Air Force;

*Systems-of-Systems Perspectives and Applications - Design, Modeling, Simulation…*

[9] Rebovich G Jr. Volume 2: Systems Thinking for the Enterprise: New and Emerging Perspectives. MITRE

[10] Nielsen BC, Larsen GP, Fitzgerald J, Woodcock J, Peleska J. Systems of systems engineering: basic concepts, model-based techniques, and research directions. ACM Computing Surveys.

[11] Systems and Software Engineering Director, Systems Engineering Guide for Systems of Systems, Deputy Under Secretary of Defense (Acquisition and Technology Office of the Under Secretary of Defense (Acquisition, Technology and Logistics)), Version 1;

[12] Saenz AO, Ronald EG, Centeno M.

engineering. International Journal of Industrial and Systems Engineering. 2009. DOI: 10.1504/IJISE.2009.024155

[13] DeRosa JK. Enterprise Systems Engineering. Presented at Air Force Association, Industry Day, Day 1, August 4, 2005; Danvers, MA, USA;

Defining enterprise systems

Corporation; 2005

2015;**48**(2):18

2008

2005

2006. ISBN: 0-8330-3872-9

[2] Keating C, Rogers R, Unal R, Dryer D, Poza SA, Safford R, et al. Systems of systems engineering. Journal Engineering Management Journal. 2003;

[3] Carlock P, Lane AJ. System of Systems Enterprise Systems Engineering, the Enterprise

SoS, USCCSE; 2006. Article 618

[4] INCOSE, Guide to the Systems Engineering Body of Knowledge (SEBoK), The Trustees of the Stevens Institute of Technology, Stevens, Part-4,

[5] Cardoso J, Schmitz B, Kieninger A. Service Design - Service Research. New York, US: Springer International Publishing; 2015. pp. 325-357

[6] Lane JA. What Is System of Systems and Why Should I Care? Daniel J. Epstein Department of Industrial and systems Engineering, University of Southern California, USC, CSSE-2013;

[7] ANSI/EIA. EIA-632, Processes for Engineering a System. Philadelphia, PA, USA: American National Standards Institute (ANSI)/Electronic Industries Association (EIA); Government

Electronics and Information Technology Association Engineering Department.

[8] NASA. Systems Engineering Handbook, NASA/SP-2007-6105 Rev1.

Washington DC, US: NASA

Headquarters; 2007

INCOSE BKCASE, v1.7 2016

Architecture Management Framework and System of Systems Cost Estimation.

**53**

**Chapter 4**

*Tien M. Nguyen*

**Abstract**

**1. Introduction**

WIS, and FOS-DVACS

SOS Enterprise, SOSE CONOPS,

Approach: A Perspective on Space

The objective of this chapter is to (i) define System-of-Systems Enterprise (SOSE), SOSE Concept of Operations (CONOPS), and SOSE Architecture (SOSEA)

**Keywords:** SOS Enterprise (SOSE), SOSE CONOPS, SOSE Architecture (SOSEA) design, SOSE integration, compatibility matrix, SOSEA evaluation metrics, SOSE capability component, capability gap analysis framework, capability management framework, requirements-based, capability-based, integration analysis framework

Currently, from a combined space and airborne perspective, one can categorize

• A set of connections among satellites within each FOS, namely, FOS-BS, FOS-

• A set of connections among FOS-BS, FOS-WIS, and FOS-DVACS.

existing "enterprises" as: (i) military enterprise, (ii) civilian enterprise, and (iii) commercial enterprise for space and airborne applications. This chapter uses existing U.S. Department of Defense (DOD) and The International Council on Systems Engineering (INCOSE) definitions on System-of-Systems (SOS) and Family-of-Systems (FOS) [1–3] to define these enterprises through the use of practical examples and design scenarios. **Figure 1** illustrates the space SOSE concept in general. As an example, current commercial space enterprise consists of (i) FOS of Broadcasting Satellites (FOS-BS), (ii) FOS of Wideband Internet Satellites (FOS-WIS), and (iii) FOS of Data, Video, Audio Communications Satellites (FOS-DVACS). For commercial space enterprise, the SOS environment can be defined as:

CONOPS assessment, and (ii) discuss their differences using examples from existing space and airborne systems. The chapter also describes the SOS design challenges and presents an SOSE Architecture design approach addressing these challenges. In addition, DOD Architecture Framework Version 2.02 (DODAF-v2.02) views will be discussed along with a recommendation for a set of key DODAF views to capture system architecture artifacts with practical examples involving SOS Enterprise architectures for notional space-based communications system and manned airborne Intelligence, Surveillance, and Reconnaissance (ISR) platform.

SOSE Architecture Design

and Airborne Systems

## **Chapter 4**
