<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:"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;}
/* 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;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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:1627421346;
mso-list-template-ids:-477737170;}
@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:1799034837;
mso-list-template-ids:411206938;}
@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:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@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:Symbol;}
@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:2012945338;
mso-list-template-ids:-582051018;}
@list l2: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 l2: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 l2: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 l2: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 l2: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 l2: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 l2: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 l2: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 l2: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"><b><span style="color:black">SEA-SA </span></b><b><span style="color:#070706;background:#FFEE94">RASDS</span></b><b><span style="color:black"> working meeting on 14 Feb 22</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: Krosley, Radulescu, Shames, Slane, Stangl<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 open issues from 10 Jan 22 meeting – Peter Shames & team</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:l0 level1 lfo1">Fred mentioned that the SC14, as part of their considerations of how to leverage the SANA registry of terms, is now starting to more seriously consider the architecture aspects of their work
and to find value in the RASDS++ work as a viable framework. That is excellent.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1">We spent some time at the beginning of the session exploring the relationships between a purely “Enterprise” viewpoint (pg 15) and the relationships to the Functional and Connectivity viewpoints
(pg 53). We all agreed that including these diagrams was a real value, as will be the explanation of the relationships. An updated pg 53, showing the “home viewpoints” of all these objects is included in the (slightly) revised 14 Feb 22 version, attached
here.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1">Ramon pointed out that there are solid correspondence relationships among these primary objects that we should leverage and describe.
<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1">Reviewed the notes from 10 Jan relating to file “SEA SAWG <span style="color:#070706;background:#FFEE94">RASDS</span> Update Views 13Dec21” that was edited following the 10 Jan 22 meeting.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1">We discussed the relationships between the “abstract” Enterprise views of “application” and “service” elements and the “realized” Functional and Connectivity views of “service”, “function”, and
“system” elements. And then we discussed the truly recursive nature of these relationships where the “abstract functions” from the Functional viewpoint are “realized” by the more concrete Connectivity and Physical views, and then, again, where these abstract
component design views are turned into real, concrete, Components by the implementation processes.
<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1">We also, briefly, discussed how this can be thought of as a recursive descent down the left hand side of the “Systems Engineering V”, followed by an ascent up the right hand side of the V as
components are created, tested, assembled into modules, elements, integrated, tested and eventually launched and operated. We
<u>may</u> <u>mention</u> that in the RASDS, but will not be exploring it in any depth since it is a whole subject on its own.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1">Touched upon, again, the need for a consistent set of terms that we can all agree upon and that have good provenance and alignment with common usage in our space operations domain.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1">Fred asked “what does system mean”, relative to pg 51 and 53, and we used that to springboard into a look through the definitions of “system”, “Capability”, “Role”, “Actor”, and “Resource”.
Most of these terms are already defined in RASDS, but were not carried into this slide deck. After review we determined that the RASDS definitions are fine as they are, so we will just reference them as they are in the future.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo1">We discussed the casual use of terms, as in “resource” or “actor” as opposed to a formalized definition. On 10 Jan 22 we discussed capturing this distinction using bold or italics when it is
a formal use as opposed to a casual one.<o:p></o:p></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo1">
Christian asked about adding some additional examples, in addition to the abstract object, definition, and representation aspects. Peter pointed out that we did already have these for all of the viewpoints, but that they need to be reviewed.<o:p></o:p></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo1">
Fred asked about On Orbit Servicing (OOS) as an example. Peter suggested that this might be a bit esoteric as a general example, since it is essentially a very important, but quite specialized, systems of systems example. Ramon suggested we could treat this
kind of “worked example” as a CCSDS Orange Book. We could consider doing that, or find a way to create a “testimonial folder” containing info on worked examples using RASDS++.<o:p></o:p></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo1">
We then reviewed the items left from the 10 Jan 22 meeting<o:p></o:p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level2 lfo1">
Pg 17: Element may be used recursively, it may be a whole or a part of a larger whole. “Element” is defined in RASDS, find it in the SANA Registry
<a href="https://sanaregistry.org/r/terms">https://sanaregistry.org/r/terms</a>. Any definition from Doc 311.0-M-1 is RASDS.<o:p></o:p></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level2 lfo1">
Pg 50: the term “Capability” may be defined as an “enterprise capability” in an Enterprise view or a “system capability” in a system view (Functional or Connectivity view).<o:p></o:p></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level2 lfo1">
Pg 51: Christian asked if we should consider adding the term “Role” to this diagram. The term “Role” is used as a few points in this deck, particularly in relationship to Enterprise VP, but it is not defined within this deck. It is, however, defined in the
existing RASDS terms as: “The way in which an entity participates in a relationship; an object’s set of behaviors and actions associated with the relationship of that object with other objects.”<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1"><span style="color:black">Pg 54: This list of viewpoints changes for SC14 uses the term(s) “space domain (physical, hardware, software) objects” and in this context the term “space
domain”, with whatever qualifiers, means different aspects of some class of elements that are part of space enterprises, writ large. The term “Space domain” is not in wide use, but space domain awareness is: “</span>Space domain awareness is the study and
monitoring of satellites orbiting the earth. It involves the detection, tracking, cataloging and identification of artificial objects, i.e. active/inactive satellites, spent rocket bodies, or fragmentation debris.” We may want to find a different term, or
to define it ourselves. The current RASDS definition of “domain” is strictly in the Enterprise viewpoint and may be too narrow for current purposes. Other CCSDS uses are more narrowly focused down in “protocol land”. Should we retain this term, and define
it, or drop it in terms of <o:p></o:p></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level2 lfo1">
Pg 60: The term Role needs to be defined in the realm of Enterprise and “resources”, in the general sense of the word. The definition identified in notes for pg 51 may suffice.<o:p></o:p></li></ul>
</li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level1 lfo1">
Not discussed today, also from the 10 Jan 22 meeting:<o:p></o:p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level2 lfo1">
We agreed to be careful to distinguish examples from class definitions<o:p></o:p></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level2 lfo1">
We agreed to carefully include ontology and representational diagrams for each viewpoint, but not to make this be a more dominant feature than that, such as including more formalized ontological definitions in OWL or some other representation<o:p></o:p></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level2 lfo1">
We agreed to define, early in the doc, what we were doing and how we were doing it vis-à-vis ontologies<o:p></o:p></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level2 lfo1">
Pg 64 & 65: The operational view terms that were provided, derived largely from NIST, need to be carefully reviewed. For instance, do we really need all three of “activity”, “task”, and “work”? Would two of the three be enough? What is the relationship
of these operational / behavioral terms to Role and Resource?<o:p></o:p></li><li class="MsoListParagraph" style="color:black;margin-left:0in;mso-list:l0 level2 lfo1">
Pg 84: Are all “Connectors” in these Physical / Structural viewpoints really physical components, as opposed to the more abstract connections as in the Connectivity viewpoint?<o:p></o:p></li></ul>
</li></ul>
<p class="MsoNormal" style="margin-left:.25in"><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"><u><span style="color:black">Next Steps Discussion – Shames</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:l2 level1 lfo2">Peter made minor changes to the slides from 10 Jan 22<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2">That updated file is attached here. Look specifically at pg 53, which was edited and re-colored to reflect the viewpoints where these various object types are defined. Note: pg 63 still needs
to be updated.<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l2 level1 lfo2">Review assignments. Each member of the team agreed to take responsibility for reviewing one viewpoint, and also one closely related viewpoint, for clarity, wording, definitions, and representational
consistency<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="color:black">Next Working Meeting, 14 Mar 2022 @ 0700 AM PDT</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Agenda:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo3">Briefly review these notes <o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo3"><b><i>Christian</i></b>: review updated diagrams, ontology, and representation approaches for Enterprise viewpoint and secondarily Functional viewpoint<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo3"><b><i>Fred</i></b>: Review updated diagrams, ontology, and representation approaches for Operational viewpoint and secondarily Enterprise viewpoint<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo3"><b><i>Ramon</i></b>: Review updated diagrams, ontology, and representation approaches for Physical viewpoint and secondarily Connectivity viewpoint<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo3"><b><i>Costin</i></b>: Review updated diagrams, ontology, and representation approaches for Functional viewpoint and secondarily Operational viewpoint<o:p></o:p></li><li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo3"><b><i>Peter:</i></b> Review the entire package for consistency of topic coverage and presentation across all of the <span style="color:#070706;background:#FFEE94">RASDS</span>++ viewpoints <o:p></o:p></li></ul>
<p class="MsoNormal"><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"> <o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>