Operational Scenarios Identification and Prioritization in Systems of Systems: A Method and an Experience Report in the Defense Domain

  • Carlos Eduardo de Barros PaesEmail author
  • Valdemar Vicente Graciano Neto
Conference paper
Part of the Smart Innovation, Systems and Technologies book series (SIST, volume 152)


Military systems play a crucial role in the defense of a country. They are often interconnected to monitor the frontiers, increase the national sovereignty, and interoperate to offer a unified control of the entire territory. These alliances of systems are currently known as systems of systems (SoS). During the last years, software has been increasingly embedded in those systems to increase their precision. Besides, multiple cyber-physical systems have also been associated to interoperate in the context of SoS, bringing novel challenges related to the conception of those systems, in particular (i) how to elicit systems’ requirements and make them coexist in the same large-scale system, (ii) how to coexist competing requirements, (iii) how to support the distributed development of constituent systems and interoperability links, (iv) how to capture their conceptual operation in a unified document to exploit their functionalities in a fruitful manner, and (v) how to make the SoS cohesive, exploiting their functionalities and creating emergent behaviors to foster the national security. Given those gaps and challenges, this paper reports an experience of a real project carried out in a real Department of Defense, particularly in the navy’s context, besides externalizing a method called OSW to support the ConOps documents in SoS engineering projects. We report the conception of a SoS for defense and maritime surveillance, focusing on the concept of operations (ConOps) of that systems, the challenges faced, and the method established. We claim that this report contributes to the engineering of defense SoS since it provides a panorama of SoS conception, besides presenting solutions that can be replicated in other projects to be carried out worldwide, contributing thus for the advance of SoS research in that domain .


Systems-of-systems engineering Experience report National defense and security 


  1. 1.
    ISO/IEC/IEEE Systems and Software Engineering—Architecture Description: ISO/IEC/IEEE 42010:2011(E) (Revision of ISO/IEC 42010:2007 and IEEE Std 1471-2000), pp. 1–46 (2011)Google Scholar
  2. 2.
    Department of Defense (DoD): Systems Engineering Guide for Systems of Systems, V 1.0. (2008)Google Scholar
  3. 3.
    Walden, D.D., Roedler, G.J., Forsberg, K., Hamelin, R.D., Shortell, T.M.: International Council on Systems Engineering: Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities. Wiley, Hoboken, NJGoogle Scholar
  4. 4.
    Paes, C.E.B., Graciano Neto, V.V., Oquendo, F., Nakagawa, E.Y.: Experience report and challenges for systems-of-systems engineering: a real case in the Brazilian defense domain. In: Proceedings of Workshop on Distributed Development, Software Ecosystems and Systems of Systems, pp. 41–50 (2016)Google Scholar
  5. 5.
    de Barros Paes, C.E., Neto, V.V.G., Moreira, T., Nakagawa, E.Y.: Conceptualization of a system-of-systems in the defense domain: an experience report in the Brazilian Scenario. IEEE Syst. J., 1–10 (2018)Google Scholar
  6. 6.
    de A. Chaves, S.F.: Sistema de Gerenciamento da Amazônia Azul (SisGAAz): o passo inicial para o efetivo controle da área marítima brasileira. Monografia apresentada ao Departamento de Estudos da Escola Superior de Guerra como requisito à obtenção do diploma do Curso de Altos Estudos de Política e Estratégia (CAEPE), Rio de Janeiro (2013)Google Scholar
  7. 7.
    Silva, E., Cavalcante, E., Batista, T., Oquendo, F., Delicato, F.C., Pires, P.F.: On the characterization of missions of systems-of-systems. In: Proceedings of the 2014 European Conference on Software Architecture Workshops—ECSAW’14, pp. 1–8. ACM Press, New York, NY, USA (2007)Google Scholar
  8. 8.
    Oquendo, F.: Architecturally describing the emergent behavior of software-intensive system-of-systems with SosADL. In: 2017 12th System of Systems Engineering Conference (SoSE), pp. 1–6. IEEE (2017)Google Scholar
  9. 9.
    Maier, M.W.: Architecting principles for systems-of-systems. Syst. Engin. 1, 267–284 (1998)CrossRefGoogle Scholar
  10. 10.
    Department of Defense (DoD): Software Development and Documentation—Military Standard MIL-STD-498 (1994)Google Scholar
  11. 11.
    Hamelin, R.D., Walden, D.C., Krueger, M.E.: INCOSE Systems Engineering Handbook v3. 2: Improving the Process for SE Practitioners. INCOSE International 11 (2010)Google Scholar
  12. 12.
    ISO:IEC 15288: 2008 Systems and software engineering-System life cycle processes. In: 2nd International Organization for Standardization/International Electrotechnical Commission, 18th March. (2008)Google Scholar
  13. 13.
    Dahmann, J., Rebovich, G., Lane, J.A., Lowry, R.: System engineering artifacts for SoS. In: 2010 IEEE International Systems Conference, pp. 13–17. IEEE (2010)Google Scholar
  14. 14.
    Dahmann, J.S., Baldwin, K.J.: Understanding the current state of US defense systems of systems and the implications for systems engineering. In: 2008 2nd Annual IEEE Systems Conference, pp. 1–7. IEEE (2008)Google Scholar
  15. 15.
    IEEE Computer Society. Software Engineering Standards Committee., Institute of Electrical and Electronics Engineers., IEEE-SA Standards Board.: IEEE guide for information technology– : system definition– concept of operations (ConOps) document. Institute of Electrical and Electronics Engineers (1998)Google Scholar

Copyright information

© Springer Nature Singapore Pte Ltd. 2020

Authors and Affiliations

  1. 1.Pontifical Catholic University of São PauloSão PauloBrazil
  2. 2.Federal University of GoiásGoiâniaBrazil

Personalised recommendations