<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;
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;}
@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:380599757;
mso-list-template-ids:-501477854;}
@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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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:569578318;
mso-list-template-ids:-1681102430;}
@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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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-start-at:0;
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"><span style="color:black">Dear RASDS group,<o:p></o:p></span></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" 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">As scheduled we had a meeting of the SAWG today, 13 May, to discuss the<span class="apple-converted-space"> RASDS</span> edits. Attendees were: Ramon Krosley, Fred Slane, Costin Radulescu, Karl Vader, Peter Shames.<o:p></o:p></span></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" 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">Discussion points:<o:p></o:p></span></p>
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l1 level1 lfo1">Peter reviewed the draft ToC outline for the RASDS++ revision. Revisions to that based on today’s discussions are attached (<u>along with writing assignments</u>).<o:p></o:p>
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">The change to the<span class="apple-converted-space"> RASDS</span> document outline to better accommodate the primacy of the Physical Viewpoint has been accepted, modulo the following
issues that were noted.<o:p></o:p></li></ul>
</li><li class="MsoListParagraph" style="color:black;mso-list:l1 level1 lfo1">Fred identified some issues that will be of particular relevance to SC14: naming of Physical Viewpoint objects and support for certain SC14 work items<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level1 lfo1">In Physical Viewpoint SC14 would prefer the terms Component and Connector to Node and Link.
<o:p></o:p>
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">This led to a discussion of the importance of adopting a consistent terminology and that while RASDS adopts a certain set of terms and representation this is not the “mandated” one, just
a self-consistent one.<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">Observation is that two sets of terms have variously been used, sometimes is a rather “fluid” fashion (blame the editor)<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">Agreement was to include both Component / Connector and Node/Link terminology and to clarify where each might be best applied<o:p></o:p></li></ul>
</li><li class="MsoListParagraph" style="color:black;mso-list:l1 level1 lfo1">Fred raised an issue, based in part on the SC14 program of work, that verification and design engineering are important topics to be able to address.<o:p></o:p>
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">Observation is that these activities are usually carried out as part of Enterprise behavior<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">Agreement is to include reference to standards like ISO 15288 and other agency process/requirements and to assert that these engineering and SE-V processes are already well documented<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">Further observation is that what most of these SE document do is to state “you need to have an architecture”, but then to be silent on just what an architecture is or what it should look
like. This recommended practice provides that guidance.<o:p></o:p></li></ul>
</li><li class="MsoListParagraph" style="color:black;mso-list:l1 level1 lfo1">Peter presented two revised RASDS++ ontology views made using the MindMapper tool.<o:p></o:p>
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">A Physical Viewpoint that riffed off a diagram that Ramon had produced a while ago.<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">The RASDS overall info model showing terms like viewpoint, view, and the selected RASDS++ viewpoints.<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">The team liked these diagrams and their easy of understanding.
<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">That said, it is not clear that we will want to expend the energy to create figures like these for all of the viewpoints. TBD.<o:p></o:p></li></ul>
</li><li class="MsoListParagraph" style="color:black;mso-list:l1 level1 lfo1">Fred brought up an example of an SC14 use of RASDS the Quality of Life (QoL) materials provided by Koki Asari of Japan. We studied the materials he provided (attached).<o:p></o:p>
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">Everyone was impressed by the adaptation of RASDS to this problem. We were particularly interested in pg 6 which showed the RASDS viewpoints, some relationships among them (correspondence,
but not named as such), a timeline axis, and a scope axis. <o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">Fred is going to ask if we can include this figure, or a variant of it, in the revision to Sec 9, “DERIVING OTHER VIEWS FROM THE BASIC VIEWPOINTS ”<o:p></o:p></li></ul>
</li><li class="MsoListParagraph" style="color:black;mso-list:l1 level1 lfo1">Ramon Krosley presented the additional work he has done to use the Ontology Markup Language (OML) to model the ISO 42010 baseline systems architecture ontology and also the Functional
Viewpoint.<o:p></o:p>
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">The OML language and tools are described at<span class="apple-converted-space"> </span><a href="https://urldefense.us/v3/__https:/www.opencaesar.io__;!!PvBDto6Hs4WbVuu7!diOB9wlne_EGleAEcsVuLNs4GeRzIJvd5jmUhR3Ag0Es2WltUftxjXNKaFy8PSL0JpKoyljW$" title="https://urldefense.us/v3/__https://www.opencaesar.io__;!!PvBDto6Hs4WbVuu7!diOB9wlne_EGleAEcsVuLNs4GeRzIJvd5jmUhR3Ag0Es2WltUftxjXNKaFy8PSL0JpKoyljW$"><span style="color:#0563C1">https://www.opencaesar.io</span></a>.
There is a downloadable spec and also a set of tools that will plug into the Eclipse framework.<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">Ramon showed a representation of the Functional Viewpoint and related it to the various Attributes and terms included on pg 4 (42010 framework), pg 14 (top level ontology),and then pg
19 (Functional Viewpoint).<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">This cross-checking and analysis pointed out some inconsistencies in these different separate views. Blame the editor (me) and the choice of “SE Tools” (PPT) which provide no inherent
consistency checks across the model.<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">This is an indication of the challenges inherent in this sort of modeling and a pointer to the need for a further careful reading and cross checking of the document and figures.<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">Doing this sort of analysis, backed up by use of the more formal OML restatement, will help ensure consistency.<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">The inclusion of these OML mappings in an Annex is another option that has been proposed. This would be especially valuable if they can be imported into a tool that will provide OWL output.<o:p></o:p></li></ul>
</li><li class="MsoListParagraph" style="color:black;mso-list:l1 level1 lfo1">Ramon plans to continue to elaborate these OML descriptions, to check them against the documented figures, and to explore the Eclipse tooling for OML and OWL export.<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level1 lfo1">We discussed just what sorts of diagrams / figures and supporting materials we might include.<o:p></o:p>
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">Fred argued for pragmatism and getting a working document out sooner, not delaying for added figures.<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">Peter suggested at least including something like Ramon’s OML files, in an annex, because that would provide a useful, machine readable, artifact in the document.<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l1 level2 lfo1">SysML diagrams have also been proposed as a separate representation in an Annex. TBD.<o:p></o:p></li></ul>
</li></ul>
<p class="MsoNormal"><span style="color:black">Action items:<o:p></o:p></span></p>
<ul type="disc">
<li class="MsoListParagraph" style="color:black;mso-list:l0 level1 lfo2">Ramon to continue to revise / extend the OML representations and to explore the Eclipse plug-in for visibility<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level1 lfo2">Fred to see if Koki will allow his diagram, or a modification of it, to be included in the RASDS++ document in Chap 9 (examples)<o:p></o:p></li><li class="MsoListParagraph" style="color:black;mso-list:l0 level1 lfo2"><u>Writing Assignments for the next meeting:</u> Produce a paragraph, as assigned (see updated ToC), for the Concept sections of the document. These may draw from existing RASDS text
or replace it as needed.<o:p></o:p></li></ul>
<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">
<b><span style="color:black">Next Working Session: 19 May 2022.</span></b><span style="color:black"><o:p></o:p></span></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" 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">Thanks, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>