{"id":343,"date":"2018-11-06T00:57:02","date_gmt":"2018-11-06T00:57:02","guid":{"rendered":"http:\/\/se.kaist.ac.kr\/starlab\/?page_id=343"},"modified":"2018-11-13T13:52:01","modified_gmt":"2018-11-13T13:52:01","slug":"dictionary","status":"publish","type":"page","link":"https:\/\/se.kaist.ac.kr\/starlab\/publications-2\/dictionary\/","title":{"rendered":"Dictionary"},"content":{"rendered":"<h2><strong>Definition of SoS<\/strong><\/h2>\n<ul>\n<li>Two or more systems\u00a0that are separately defined but <b>operate together to perform a common goal<\/b>. \u00a0 \u00a0&#8211;\u00a0Checkland 1999, \u201c<i>Systems Thinking, Systems <\/i><i>Practice\u201d (citation: 9099)<\/i><\/li>\n<\/ul>\n<ul>\n<li>SoS applies to a system of interest whose system elements are themselves systems; typically these entail <b>large scale inter\u2010disciplinary problems <\/b>with multiple, heterogeneous, distributed systems.\u00a0 \u00a0 \u00a0 &#8211;\u00a0INCOSE 2012, \u201c<i>Systems <\/i><i>Engineering Handbook: A Guide for System Life <\/i><i>Cycle Processes <\/i><i>and <\/i><i>Activities\u201d (citation: 160)<\/i><\/li>\n<\/ul>\n<ul>\n<li>SoS is an assemblage of components which individually may be regarded as systems and which possesses two additional properties. <u><b>operational independence <\/b><\/u>of the components and <u><b>managerial Independence <\/b><\/u>of the components. \u00a0 \u00a0 &#8211;\u00a0Maier 1998, \u201c<i>Architecting Principles for Systems-of-Systems<\/i>\u201d <em>(citation: 1091)<\/em><\/li>\n<\/ul>\n<ul>\n<li><i>Not <\/i><i>all SoS will exhibit all of the characteristics, but it is generally assumed that a SoS is <\/i><i>characterized <\/i><i>by exhibiting a majority of the Maier Criteria<\/i><i>. \u00a0 \u00a0<\/i><i>&#8211;<\/i>SEBok wiki<i> (\u201cGuide to the System Engineering Body of Knowledge\u201d, <\/i>INCOSE project<i>)<\/i><\/li>\n<\/ul>\n<ul>\n<li>Maier&#8217;s two criteria\n<ul>\n<li>Operational independence of the CSs<\/li>\n<li>Managerial\u00a0independence of the CSs<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<ul>\n<li>Maier&#8217;s five characteristics for SoS\n<ul>\n<li>Operational independence of the CSs<\/li>\n<li>Managerial\u00a0independence of the CSs<\/li>\n<li>Geographical distribution<\/li>\n<li>Emergent behavior<\/li>\n<li>Evolutionary development processes<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><img src=\"http:\/\/se.kaist.ac.kr\/starlab\/wp-content\/uploads\/2015\/12\/SoSdef.png\" alt=\"\" align=\"center\" \/><\/p>\n<h2><strong>Classification of SoS<\/strong><\/h2>\n<ul>\n<li>Maier defined three types of SoS in 1998. \u00a0 \u00a0 -&#8220;Architecting principles for System of Systems&#8221;\n<ol>\n<li>Virtual SoS<\/li>\n<li>Collaborative SoS<\/li>\n<li>Directed SoS<\/li>\n<\/ol>\n<\/li>\n<\/ul>\n<ul>\n<li>In Dahmanns &amp; Baldwins book &#8220;Understanding the current state of US defense system of systems and the implications for systems engineering(2008)&#8221;, they additionally defines 1 category. So, four types of SoS are\n<ol>\n<li>Virtual SoS\n<ul>\n<li>The SoS is without either managerial control or a common purpose. This makes the behavior and the fulfilled goals highly emergent, but also entails that the exact means and structures producing the system functionality are difficult to discern and distinguish.<\/li>\n<\/ul>\n<\/li>\n<li><span style=\"line-height: 1.5;\">Collaborative SoS<\/span>\n<ul>\n<li>The SoS recognizes a common purpose and goal, while the constituent systems retain independent control and objectives. Evolution of the common purpose is based on collaboration between the SoS and the constituent systems.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Acknowledged SoS (between Collaborative SoS and directed SoS)<\/strong>\n<ul>\n<li>The constituent systems are not compelled to follow a central management, but voluntarily participate in a collaboration to fulfil the goal.<\/li>\n<\/ul>\n<\/li>\n<li>Directed SoS\n<ul>\n<li>The SoS is built to fulfil specific purposes. Constituent systems have the ability to operate independently, but are managed to satisfy a concrete purpose.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<\/li>\n<\/ul>\n<p><img src=\"http:\/\/se.kaist.ac.kr\/starlab\/wp-content\/uploads\/2015\/12\/category.png\" align=\"center\" \/><\/p>\n<h2><strong>Taxonomy of SoS<\/strong><\/h2>\n","protected":false},"excerpt":{"rendered":"<p>Definition of SoS Two or more systems\u00a0that are separately defined but operate together to perform a common goal. \u00a0 \u00a0&#8211;\u00a0Checkland 1999, \u201cSystems Thinking, Systems Practice\u201d (citation: 9099) SoS applies to a system of interest whose system elements are themselves systems; typically these entail large scale inter\u2010disciplinary problems with multiple, heterogeneous, distributed systems.\u00a0 \u00a0 \u00a0 &#8211;\u00a0INCOSE [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":334,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/se.kaist.ac.kr\/starlab\/wp-json\/wp\/v2\/pages\/343"}],"collection":[{"href":"https:\/\/se.kaist.ac.kr\/starlab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/se.kaist.ac.kr\/starlab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/se.kaist.ac.kr\/starlab\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/se.kaist.ac.kr\/starlab\/wp-json\/wp\/v2\/comments?post=343"}],"version-history":[{"count":6,"href":"https:\/\/se.kaist.ac.kr\/starlab\/wp-json\/wp\/v2\/pages\/343\/revisions"}],"predecessor-version":[{"id":549,"href":"https:\/\/se.kaist.ac.kr\/starlab\/wp-json\/wp\/v2\/pages\/343\/revisions\/549"}],"up":[{"embeddable":true,"href":"https:\/\/se.kaist.ac.kr\/starlab\/wp-json\/wp\/v2\/pages\/334"}],"wp:attachment":[{"href":"https:\/\/se.kaist.ac.kr\/starlab\/wp-json\/wp\/v2\/media?parent=343"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}