<html xmlns:v="urn:schemas-microsoft-com:vml" 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=iso-8859-1">
<meta name="Generator" content="Microsoft Word 14 (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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Dear Karen,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">See our mails below regarding test cases for Planning Book. The respective presentation for the telecon (with more or less the same information as below) I uploaded to CWE:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Planning%20Information%20Book/Prototyping/ActionItem2015-0327-13_Planning_Book_Test_Cases.pptx">http://cwe.ccsds.org/css/docs/CSS-SM/CWE%20Private/Planning%20Information%20Book/Prototyping/ActionItem2015-0327-13_Planning_Book_Test_Cases.pptx</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I allowed myself to create a subfolder “Prototyping” in Planning Book folder.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Btw. I will try to call in on Thursday, but currently it’s 50/50 chance I will make it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best Regards<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Marcin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Barkley, Erik J (3970) [mailto:erik.j.barkley@jpl.nasa.gov]
<br>
<b>Sent:</b> Freitag, 29. Mai 2015 03:12<br>
<b>To:</b> Gnat, Marcin<br>
<b>Subject:</b> RE: SMWG: Planning Format Book - Test cases<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Marcin,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks for the inputs and thoughts. I think
</span><span style="font-family:Wingdings;color:#1F497D">J</span><span style="color:#1F497D">.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I think the first thing to keep in mind is that we are not yet writing any kind of service specification but really just a data format specification. There is a strong tendency of course to make sure we support
any eventual service. So if we keep that in mind then I think then the request part of it is definitely a phase 3 type activity. And I think this is perhaps going to be an activity that comes quite a bit later than the main prototyping of the output format.
The reason I say that is that we have to first agree on the abstract engineering and then get down to specifics. I know that in the case of the DSN there are a lot of details and options that can be put in the request but those probably don't look very much
like what ESA may come up with for more of the "standing orders" type approach. Therefore I think this is going to require some sorting out before we can get into what the prototyping for the request aspect looks like. With any luck, perhaps you can join us
on the June 2 teleconference and we can at least touch upon this a bit. I will note that the agenda is getting to be rather “explosive” in that it will very unlikely be able to fit within the two hour window as there are lots of requests for various topics
of discussion and developments to go over in CCSDS. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">-Erik<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> <a href="mailto:Marcin.Gnat@dlr.de">Marcin.Gnat@dlr.de</a> [<a href="mailto:Marcin.Gnat@dlr.de">mailto:Marcin.Gnat@dlr.de</a>]
<br>
<b>Sent:</b> Wednesday, May 20, 2015 11:26 PM<br>
<b>To:</b> Barkley, Erik J (3970)<br>
<b>Subject:</b> SMWG: Planning Format Book - Test cases<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a name="Gruß"></a>Hi Erik,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Next week is the due date for the test cases for the Planning Book. As you probably noticed due to my absence in last telecons, I am currently pretty busy with projects and other work here, so no time for CCSDS stuff. Next week also I’m
on a vacation, so I will not be able to really work on that. Starting back in June (I hope) I can spend some time for CCSDS finally.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Anyway, just as a starting point for the considerations:<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt">-<span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span>For the Simple Schedule Book we’ve had three phases of testing, manual, tool-supported and “special use” (meaning in this case the unallocated time).<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt">-<span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span>Assuming we do testing only of the planning events use case, we may try to go for something similar like above:<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt"><span style="font-family:"Courier New"">o</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span>Phase 1: Manual phase (with creation of the event file manually, either with Notepad or XMLSpy or so) just to give the testing parties the “first feeling”. This phase may be keept short, something like two test cases per prototyping side.<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt"><span style="font-family:"Courier New"">o</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span>Phase2: Tool-Supported phase (with some more or less automated conversion tools which convert between internal and CCSDS file formats). This we may elaborate into several test cases and maybe even use cases for the events:<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-18.0pt"><span style="font-family:Wingdings">§</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span>Small number of events vs. large number<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-18.0pt"><span style="font-family:Wingdings">§</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span>Specific time frame<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-18.0pt"><span style="font-family:Wingdings">§</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span>Deeps Space, LEO, GEO events<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-18.0pt"><span style="font-family:Wingdings">§</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span>Routine events vs. LEOP events<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:108.0pt;text-indent:-18.0pt"><span style="font-family:Wingdings">§</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span>Usage for scheduling, mission planning, etc…<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt">-<span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span>How do we want to handle the request? Should it be integral part of the above tests? I would actually go for that, in such a case we may introduce an intermediate test phase where we “just” check the compatibility (I do not know if I use here really
the word I want to use ;-), I hope you get what I mean) between the request and the planning information (events). Other possibility would be to test the request as a separate test phase (would be the phase 3 in my above list) where we say “Tool-supported
request-reply”.<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt">-<span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span>Important thing to decide (by us, but maybe by the prototyping parties) is the handling of the request -> means do I just get the request, process it manually (human eyes) and then produce the planning information or explicitly have a prototype software
which receives a request file and respectively generates a planning information according to request? The second case is definitely more elegant, but involves definitely some more effort (and for me also would mean involving our Flight Dynamics). On the other
hand, we have to test only the interface, so as long the reply fits to the request, prototyping should not care much how one got there? Or?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="punctuation-wrap:simple;text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif"">Best regards<o:p></o:p></span></p>
<p class="MsoNormal" style="punctuation-wrap:simple;text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal" style="punctuation-wrap:simple;text-autospace:none"><a name="Absender"></a><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif"">Marcin<o:p></o:p></span></p>
<p class="MsoNormal" style="punctuation-wrap:simple;text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal" style="punctuation-wrap:simple;text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">——————————————————————————<o:p></o:p></span></p>
<p class="MsoNormal" style="punctuation-wrap:simple;text-autospace:none"><b><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">Deutsches Zentrum für Luft- und Raumfahrt</span></b><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">
e.V. (DLR)<o:p></o:p></span></p>
<p class="MsoNormal" style="punctuation-wrap:simple;text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">German
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">Aerospace Center</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:16.0pt;punctuation-wrap:simple;text-autospace:none">
<a name="Institut"></a><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:dimgray">Space Operations and Astronaut Training | German Space Operations Center (GSOC) | Communications and Ground Stations | Oberpfaffenhofen | 82234 Wessling | Germany<o:p></o:p></span></p>
<p class="MsoNormal" style="punctuation-wrap:simple;text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal" style="punctuation-wrap:simple;text-autospace:none"><a name="Funktion"></a><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">Marcin Gnat</span></b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">
| </span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:dimgray">Ground Data System Manager</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:16.0pt;punctuation-wrap:simple;text-autospace:none">
<a name="Telefon"></a><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:dimgray">Telephone +49 (8153) 28 3201 | Telefax +49 (8153) 28 1456 |
</span><a href="mailto:marcin.gnat@dlr.de"><span style="font-size:8.5pt;font-family:"Arial","sans-serif"">marcin.gnat@dlr.de</span></a><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:dimgray"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:16.0pt;punctuation-wrap:simple;text-autospace:none">
<a href="http://www.dlr.de/"><span lang="DE" style="font-size:8.5pt;font-family:"Arial","sans-serif"">www.DLR.de</span></a><u><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:blue"><o:p></o:p></span></u></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>