Systems, Man & Cybernetics - July 2017 - 12
modeling approaches, languages, and methods. It also provides a vehicle for SMCS collaboration with the MBSE Initiative on topics of mutual interest.
Moving from a Single-System Perspective
to a System-of-Systems Perspective
SoSE has become an increasingly important area for systems engineers, and this is reflected in the activities of the
INCOSE SoS WG. Created in 2013, the group has as its purpose to advance and promote the application of SE to systems of systems (SoSs) and to serve as a forum to share
understanding of SoS and SoSE issues, good practice, and
background, and to contribute to maturing the SoSE state
of the art. On behalf of INCOSE, the WG sponsors a series
of monthly open community webinars on SoS, where presenters share their ideas concerning and experiences with
the application of SoSE.
Working in partnership with both the National Defense
Industry Association (NDIA) SE Division and the IEEE,
INCOSE cosponsors the IEEE Annual SoSE Conference,
sponsors sessions at the IEEE Systems Conference, and
works in cooperation with NDIA on a range of special initiatives, most recently developing an industry perspective
on application of SoSE in defense mission engineering.
The SoS WG has developed a set of SoS Pain Points
that provide an introduction to the challenges that SoS
pose for SE and a SoSE-themed issue of INCOSE's Insight,
the INCOSE practitioner's magazine, to share the current
SoSE state of the practice for addressing these challenges
with the broader SE community. Finally, ISO/IEC JTC 1/SC 7
commissioned a study on the state of SoSE and the need
for SoSE standards in which INCOSE has a leadership role
and is a key contributor. As a result, there are now ISO/
IEC/IEEE standards in development addressing SoS considerations in engineering systems and the application of
SE processes to SoSE.
Transforming the View of System Security
The INCOSE Systems Security Engineering WG was
formed in 2007. This was motivated by a widening gap
between the costs spent on security and the losses due to
insecurity. This gap is thought to be the result of treating
security as something that could be dealt with in isolation
rather than as part of the system. The mission of the WG is
to eventually enable agile security concepts as an integral
part of SE.
The WG has established a system security engineering
guidance, case studies, and other information for the
INCOSE Systems Engineering Handbook and securitythemed issues of INCOSE Insight. The WG actively participates, collaborates, and advises on standards-including
NIST 800-160, ISO/IEC JTC 1/SC 27 standards activity in IT
security techniques, and US TAG for ISO/IEC JTC 1/SC 27-
with NDIA's Cyber Division and its Systems Security Engineering Committee within the SE Division, and with other
INCOSE WGs, such as the Critical Infrastructure Protec12
IEEE SYSTEMS, MAN, & CYBERNETICS MAGAZINE Ju ly 2017
tion and Recovery WG. The WG has also contributed to the
IEEE Smart Grid Vision for Computing and to the IEEE
Carnahan Conferences with a plenary session and papers
on agile security.
Learn More
To learn more about INCOSE and state-of-the-art practice
in SE, please visit www.incose.org.
About the Authors
Garry J. Roedler (garry.j.roedler@lmco.com) is a senior
fellow and the Engineering Outreach program manager for
Lockheed Martin and the president-elect for the International Council on Systems Engineering (INCOSE). He has more
than 32 years of systems engineering experience that spans
the full life cycle, which includes technical leadership roles
in both programs and business functions. He is also an
INCOSE fellow, holds systems engineering certification at
the Expert Systems Engineering Professional level, and
received the INCOSE Founders Award.
Alan D. Harding (president@incose.org) earned his
B.Sc. (Hons) degree in physics from the University of Durham, United Kingdom. He is the head of the Information
Systems Engineering Discipline with the BAE Systems Military Air and Information business in the United Kingdom.
He is the president of the International Council On Systems
Engineering (INCOSE), the global professional society for
systems engineering. He is a BAE Systems Global Engineering fellow, professionally registered as a Chartered Engineer
via INCOSE in the United Kingdom, and a fellow of the
Institution of Engineering and Technology.
Rachel I. LeBlanc (marcom@incose.org) earned B.S.
and M.S. degrees in the life sciences as well as an M.B.A.
degree. She is the assistant vice president of Academic
and Corporate Engagement at Worcester Polytechnic
Institute. She leads the workforce development and strategic engagement efforts for the university. She has more
than 14 years of experience working with faculty to create
education solutions to meet business needs. Throughout
her career, she and her team have provided education
solutions for several industries including robotics. She
currently serves as the director of marketing and communications on the board of directors for the International
Council on Systems Engineering and as a director of
AUVSI New England.
References
[1] J. Dahmann, "Systems of systems: Characterization and type," NATO Lecture
Series on Systems of Systems Engineering, 2015.
[2] INCOSE, Insight, "Systems of systems" theme, vol. 19, no. 3, Oct. 2016.
[3] ISO/IES. (2016). Directives, part 1: procedures for the technical work (subclause
1.17.2.1). [Online]. Available:http://www.iec.ch/members_experts/refdocs/iec/isoiecdir-1iecsup%7Bed12.0%7Den.pdf
[4] International Council on Systems Engineering. (2014, 13 Oct.) A world in motion:
systems engineering vision 2025. [Online]. Available: http://www.incose.org/AboutSE/
sevision
http://www.incose.org
http://www.B.Sc
http://www.incose.org/AboutSE/
Table of Contents for the Digital Edition of Systems, Man & Cybernetics - July 2017
Systems, Man & Cybernetics - July 2017 - Cover1
Systems, Man & Cybernetics - July 2017 - Cover2
Systems, Man & Cybernetics - July 2017 - 1
Systems, Man & Cybernetics - July 2017 - 2
Systems, Man & Cybernetics - July 2017 - 3
Systems, Man & Cybernetics - July 2017 - 4
Systems, Man & Cybernetics - July 2017 - 5
Systems, Man & Cybernetics - July 2017 - 6
Systems, Man & Cybernetics - July 2017 - 7
Systems, Man & Cybernetics - July 2017 - 8
Systems, Man & Cybernetics - July 2017 - 9
Systems, Man & Cybernetics - July 2017 - 10
Systems, Man & Cybernetics - July 2017 - 11
Systems, Man & Cybernetics - July 2017 - 12
Systems, Man & Cybernetics - July 2017 - 13
Systems, Man & Cybernetics - July 2017 - 14
Systems, Man & Cybernetics - July 2017 - 15
Systems, Man & Cybernetics - July 2017 - 16
Systems, Man & Cybernetics - July 2017 - 17
Systems, Man & Cybernetics - July 2017 - 18
Systems, Man & Cybernetics - July 2017 - 19
Systems, Man & Cybernetics - July 2017 - 20
Systems, Man & Cybernetics - July 2017 - 21
Systems, Man & Cybernetics - July 2017 - 22
Systems, Man & Cybernetics - July 2017 - 23
Systems, Man & Cybernetics - July 2017 - 24
Systems, Man & Cybernetics - July 2017 - 25
Systems, Man & Cybernetics - July 2017 - 26
Systems, Man & Cybernetics - July 2017 - 27
Systems, Man & Cybernetics - July 2017 - 28
Systems, Man & Cybernetics - July 2017 - 29
Systems, Man & Cybernetics - July 2017 - 30
Systems, Man & Cybernetics - July 2017 - 31
Systems, Man & Cybernetics - July 2017 - 32
Systems, Man & Cybernetics - July 2017 - 33
Systems, Man & Cybernetics - July 2017 - 34
Systems, Man & Cybernetics - July 2017 - 35
Systems, Man & Cybernetics - July 2017 - 36
Systems, Man & Cybernetics - July 2017 - 37
Systems, Man & Cybernetics - July 2017 - 38
Systems, Man & Cybernetics - July 2017 - 39
Systems, Man & Cybernetics - July 2017 - 40
Systems, Man & Cybernetics - July 2017 - 41
Systems, Man & Cybernetics - July 2017 - 42
Systems, Man & Cybernetics - July 2017 - 43
Systems, Man & Cybernetics - July 2017 - 44
Systems, Man & Cybernetics - July 2017 - 45
Systems, Man & Cybernetics - July 2017 - 46
Systems, Man & Cybernetics - July 2017 - 47
Systems, Man & Cybernetics - July 2017 - 48
Systems, Man & Cybernetics - July 2017 - Cover3
Systems, Man & Cybernetics - July 2017 - Cover4
https://www.nxtbook.com/nxtbooks/ieee/smc_202310
https://www.nxtbook.com/nxtbooks/ieee/smc_202307
https://www.nxtbook.com/nxtbooks/ieee/smc_202304
https://www.nxtbook.com/nxtbooks/ieee/smc_202301
https://www.nxtbook.com/nxtbooks/ieee/smc_202210
https://www.nxtbook.com/nxtbooks/ieee/smc_202207
https://www.nxtbook.com/nxtbooks/ieee/smc_202204
https://www.nxtbook.com/nxtbooks/ieee/smc_202201
https://www.nxtbook.com/nxtbooks/ieee/smc_202110
https://www.nxtbook.com/nxtbooks/ieee/smc_202107
https://www.nxtbook.com/nxtbooks/ieee/smc_202104
https://www.nxtbook.com/nxtbooks/ieee/smc_202101
https://www.nxtbook.com/nxtbooks/ieee/smc_202010
https://www.nxtbook.com/nxtbooks/ieee/smc_202007
https://www.nxtbook.com/nxtbooks/ieee/smc_202004
https://www.nxtbook.com/nxtbooks/ieee/smc_202001
https://www.nxtbook.com/nxtbooks/ieee/smc_201910
https://www.nxtbook.com/nxtbooks/ieee/smc_201907
https://www.nxtbook.com/nxtbooks/ieee/smc_201904
https://www.nxtbook.com/nxtbooks/ieee/smc_201901
https://www.nxtbook.com/nxtbooks/ieee/smc_201810
https://www.nxtbook.com/nxtbooks/ieee/smc_201807
https://www.nxtbook.com/nxtbooks/ieee/smc_201804
https://www.nxtbook.com/nxtbooks/ieee/smc_201801
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_1017
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_0717
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_0417
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_0117
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_1016
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_0716
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_0416
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_0116
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_1015
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_0715
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_0415
https://www.nxtbook.com/nxtbooks/ieee/systems_man_cybernetics_0115
https://www.nxtbookmedia.com