<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:inherit;
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:4790449;
mso-list-template-ids:-550978186;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:438182192;
mso-list-template-ids:-1441352260;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2
{mso-list-id:788551513;
mso-list-type:hybrid;
mso-list-template-ids:-535652976 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l3
{mso-list-id:1048458644;
mso-list-template-ids:1580650496;}
@list l3:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Dear SEA-SA RASDS enthusiasts,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We have a working meeting scheduled for this coming Monday, 8 Nov. The attached presentation includes the latest set of updates that I have at hand. I have been making a “consistency” pass over the materials, intended to bring the various
views up to a common level of details and perspectives. To that end there are several new pages added and some changes to others for consistency. These changes deal with several, but not all, of the “Forward Plan” issues identified in the notes from the
last meeting, which are appended here.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I draw your attention, in particular, to the following pages: 21-23, 27-28, 34-35, 39-42, 45-48, 52, 58-59, 69, and 90-101 (SysML annex).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’d also like to draw your attention to the Operations Viewpoint, pgs 61 – 66. In looking at these diagrams, and trying to create a one page “this is how to represent this” diagram (mocked up on pg 63), like pgs 20, 26, 34, etc I felt
like we had not yet really come to closure on just what this viewpoint was. Please see pg 62 for the questions I think we need answers for.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I think we still have similar questions re the Physical Viewpoint. We have stated some concepts of how these components tie to the other physical components (Nodes & Links) in the Connectivity Viewpoint, but these ideas are not yet “crisp”
in my mind. I’d like the aspects of this view to be more concrete. For one possible approach to that see below where I talk about openCAESAR and OML.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The other area that still feels “soggy” to me, i.e. “not crisp” is how we model the terminology / ontology. In these updates I have adopted treating these ontological representations as info models (which is what they are). Felt nicely
recursive, see if you agree. It does still mean that we create all of these ontologies “by hand”, which in this day and age seems rather retro. We’ve tried some different tools that use OWL and other approaches, but none has, as yet “sparked”. I have just
loaded Eclipse, and I think Ramon has too. There are a variety of modeling plug-ins that may give us the traction we need, and the platform is a) free, b) works on Mac and PC, and c) has a substantial international community. It’s being used to good effect
by the CSS SM WG for their Functional Resource Models (FRM). Perhaps someone will take on the task of digging into this and providing some consistent ontology models. There is also a SysML plugin for Eclipse.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I also learned of a different, but related, body of work called Ontological Modeling Language (OML). There are TLA several variations on “OML” so search for the full name. And there is an open source project called openCAESAR. To quote
from one of the leads:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">OML is also “free”. It’s provided by the open source project “openCAESAR” (<a href="http://www.opencaesar.io/" title="http://www.opencaesar.io/"><span style="color:#0563C1">http://www.opencaesar.io/</span></a>)
with a specification at<span class="apple-converted-space"> </span><a href="http://www.opencaesar.io/oml/"><span style="color:#0563C1">http://www.opencaesar.io/oml/</span></a>.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">OML (Ontological Modeling Language) is a language that allows you to model ontologies. OML ontologies are of 4 types:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black"> <o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo3">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:black">Vocabularies: defines your domain’s concepts, aspects, relations, properties, rules (inference rules) with open-world semantics<o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo3">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:black">Vocabulary bundles: combines several inter-related ontologies and closes the world for them to permit “description logic” reasoning<o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo3">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:black">Description: defines your systems as instances using terms from some vocabulures above<o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo3">
<![if !supportLists]><span style="font-size:10.0pt;font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:black">Description bundle: combines your descriptions in a dataset that can be reasoned on<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">OML is a higher level syntax around OWL2-DL (which supports DL reasoning) and SWRL (ability to extend DL semantics with more logical inference rules).<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<u><span style="color:black">We can give you a demo if you’re interested.<o:p></o:p></span></u></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Full disclosure: This has been developed at JPL as part of the Integrated Model Centric Engineering (IMCE) project, and OML and CAESAR and parts of the underpinnings for this project. They are using this whole
framework in three different ways:<o:p></o:p></span></p>
<ol start="1" type="1">
<li class="MsoListParagraph" style="color:black;mso-list:l2 level1 lfo4">Framework for formally modeling (and checking for consistency) ontologies<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level1 lfo4">The IMCE modeling framework, which is an ontology<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l2 level1 lfo4">Using the IMCE framework and ontology for modeling mission systems and components, and checking
<u>those</u> “realized” models for consistency with the ontologies (variation of pg 5 in the attached)<o:p></o:p></li></ol>
<p class="MsoNormal"><span style="color:black">On the one hand, this is a higher level of rigor than we are attempting to achieve, and they have a team of people working on this. On the other hand, one of the specific things they are modeling is all the spacecraft
physical elements and creating a Mass Element List (MEL) and a Power Element List (PEL). Anyone familiar with space missions knows that these are key gate products, and here they are being created from checked and validated models.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">If anyone has an interest in looking more deeply into this and exploring the possibility of using this framework to assist our work I would support getting a demo and digging more deeply. Don’t be shy, speak up.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">See you all on Monday.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Cheers, Peter<o:p></o:p></span></p>
<div style="mso-element:para-border-div;border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal" style="border:none;padding:0in"><span style="color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-family:"inherit",serif;color:#070706;background:#FFEE94"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-family:"inherit",serif;color:black">RASDS++ working meeting on 18 October 21</span></b><span style="font-family:"inherit",serif;color:#070706;background:#FFEE94"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Attendees: Huang, Krosley, Radulescu, Rovetto, Sanchez – Aguillar, Shames, Stangl, Vaden<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><u><span style="color:black">Review of revised RASDS++ Powerpoint Materials (Function, Connectivity, Operation) – led by Shames & Radulescu</span></u><span style="color:black"><o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo1">Reviewed the 16 Oct 21 version of the RASDS++ PPT materials, with focus on overall coverage, consistency of presentation, terminology<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo1">Stangl made the point that the ECSS has a separate working effort to define a set of Euro-centric terms in a Glossary. He was requested to review those terms, and the RASDS proposed ones, and
identify any overlaps or disconnects. The point was also made that RASDS has chosen to align terminology to widely adopted and respected sources such as ISO 42010, NIST, TOGAF, DoDAF, and others. The point was made in a later discussion (during the 20 Oct
meeting) that in general there seldom is any single source that provides all of the desired terms and that some “detective work” and revising has been needed to create a single self-consistent, set of terms.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo1">Agreed during review to retain the viewpoint main object diagrams that show the main objects, input, output and management interfaces, main attributes, and concerns.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo1">During discussion of the Communications Viewpoint (protocols) agreed that we needed a simpler diagram in addition to the rather complicated one that was included as an example. This later led
to adoption of this same general approach for all viewpoints.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo1">In the complicated protocol example that had been included we agreed (during 20 Oct discussion) to retain some of the security features, but to eliminate at least one of the three security approaches
that were included. All agreed that security is a very important topic, and that it had to be treated adequately.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo1">We spent some time on the Operations Viewpoint and reviewed the Activity Diagram that had been provided as an example. This brought up a discussion of consistency in the use of object representations
across different views. This UML-derived Activity diagram adopted the UML style, which used rounded rectangles for Functions and rectangles for data. But the RASDS unified “Legend”, pg 10, uses ovals to represent Functions and rounded rectangles to represent
Data / Information objects.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo1">A separate working session was held by Radulsecu, Rovetto, and Shames, on 19 Oct, to explore ways to improve this Activity Diagram. The result is in the 20 Oct PPT set, and it uses ovals, rounded
rectangles, and dashed arrows, to align with the common practice documented in the Legend.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo1">Rovetto showed an ontology diagram produced with a tools called VUE and suggested that we explore use of it for the RASDS ontology diagrams. Rovetto, Radulescu, and Shames explored this during
their side meeting and concluded that this tool had some nice presentation features, but that it did not appear to have the ability to handle the OWL formulations that we have created. It also only works on PCs and not on the more current Mac OS’s, so it
is unlikely to meet our needs for an interoperable format / approach.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo1">=> A common and agreed method for producing these ontologies is still desired, other options are solicited<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo1">For the Operations Viewpoint we will also need a less complicated example diagram than the one provided<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo1">The Activity Diagram, which is an example of use showing what is, in effect, a deep space style mission operations flow, was the subject of a lot of discussion. There was a stated concern that
it was not really accurate, that it did not include comm network activities nor science activities, and that it was missing some typical data flows. All of these observations are likely accurate, but we have to remember that this is just an example of how
this method may be used, it is not intended to accurately depict any given configuration or deployment.<o:p></o:p></li></ul>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-family:"inherit",serif;color:#070706;background:#FFEE94">SEA-SA</span></b><b><span style="font-family:"inherit",serif;color:black"> RASDS working meeting on 20 October 21</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Attendees: Huang, Krosley, Radulescu, Shames, Slane, Stangl, Vaden<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><u><span style="color:black">Review of revised RASDS++ Powerpoint Materials (Enterprise, Connectivity, Operations, Service) – led by Shames & Slane</span></u><span style="color:black"><o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo2">Reviewed the 18 Oct 21 updated version of the RASDS++ PPT materials, with a continuing focus on overall coverage, consistency of presentation, terminology<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo2">Reviewed the consistency in the package across different viewpoints, seeking to ensure a consistent presentation of different views and levels of detail<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo2">Agreed on the following pattern for each viewpoint<o:p></o:p>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">Each viewpoint will have a main object diagram that shows the primary object defined in the viewpoint, input, output and management interfaces, main attributes, and concerns.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">Each viewpoint will have a “drawing template” diagram showing two (or more) of the objects, the elements that they may include or directly reference, and how the usual relationships between them
are depicted. These are all in the abstract.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">Each viewpoint will have a constrained ontological diagram showing the main object, close “neighbor” objects, and closely related support objects in context, with relationships<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">Each viewpoint will have a simple example diagram showing the use of the drawing template to create a relatively simple model<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">Each viewpoint will have a more complex example view, probably drawn from one of the SCCS-ARD or ASL documents, showing use of the viewpoint methods to create a more complicated, realistic, view
of some typical real elements, in context<o:p></o:p></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo2">Motivated by the complicated protocol stack diagram, which includes a number of security protocols (data encryption, BP network layer security, and IPSEC IP layer security) we discussed removing
the IPSEC, but also how to handle security in more general terms<o:p></o:p>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">Agreed to do a pass across the whole document with “security eyes” on, to ensure that we have adequately supported cybersecurity modeling needs in the model methods & views that are provided<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">Ensure that security topics were included in each complicated example where that made sense<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">Keeping in mind that we are producing an architecture method and not an architecture, per se<o:p></o:p></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo2">Reviewed the Enterprise Viewpoint with Fred Slane’s guidance since this is a specific SC14 concern<o:p></o:p>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">Agreed to adopt many of the “enterprise architecture” terms that were provided, but to ensure that the term “Enterprise” was used in every case instead of “Business”<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">Agreed that the term “Enterprise” was suitably broad enough to cover agencies, projects, multi-mission consortia, government organizations, businesses, and other commercial entities<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">Reviewed the combines Enterprise / System ontology and agreed that this was a useful way of describing the relations ships (really correspondences) between objects in two different viewpoints<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">This triggered a discussion of how these ontologies, classes, and relationships among classes relate to math, knowledge graphs, first order logic, and graph theory. This is not a rabbit hole
we will explore, but it does have relevance.<o:p></o:p></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo2">Reviewed the Operations Viewpoint and Ontology<o:p></o:p>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">Agreed that we need to provide the same sorts of intro diagrams for this VP as for the others in this set<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">Agreed that the revised example provided by Rovetto, Radulsecu, and Shames aligns better with the rest of the RASDS++ style<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">Agreed that we need a cleaner ontology diagram than either of the ones that we now have<o:p></o:p></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo2">Reviewed the Services Viewpoint<o:p></o:p>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">Agreed that the prototype service diagram was acceptable, but that it needed some clean-up (in draft form)<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">Agreed that we should focus the Services viewpoint not just on SOA-style service paradigms, but also include options like on-board message bus, AMS, and web/cloud deployments<o:p></o:p></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo2"><b><span style="background:yellow">Forward plan</span></b><o:p></o:p>
<ul style="margin-top:0in" type="circle">
<li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">Add / update diagrams to meet agreed contents from this meeting<o:p></o:p>
<ul style="margin-top:0in" type="square">
<li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo2">Main object diagrams (all) – Shames<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo2">Drawing template diagrams (all) – Shames<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo2">Ontology models: Enterprise – Shames/Slane; Functional – Shames; Connectivity & Structural – Krosley/Slane; Operations – Radulescu; Information & Service - Shames<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo2">Enterprise Examples – Slane<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo2">Functional Examples – Shames<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo2">Connectivity Examples – Shames/Krosley<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo2">Structural Examples – Krosely<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo2">Operations Examples – Radulsecu<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo2">Information Examples – Krosley<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level3 lfo2">Service Examples – Shames/Slane<o:p></o:p></li></ul>
</li><li class="MsoNormal" style="color:black;mso-list:l1 level2 lfo2">Security “eyes” review – Shames/Radulescu/Sanchez-Aguillar<o:p></o:p></li></ul>
</li></ul>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Next meeting – 2’nd Monday of the month, 8 Nov 2021<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>