<font size=2 face="sans-serif">Hi Sam,</font>
<br>
<br><font size=2 face="sans-serif">I believe that we should define a concrete
set of terminology and use it consistently throughout the documents. </font>
<br><font size=2 face="sans-serif">Nowadays we just use "MO services"
for everything which makes things harder to read/explain.</font>
<br>
<br><font size=2 face="sans-serif">My initial suggestion is to coin the
following terms: (feel free to make changes or include
other suggestions)</font>
<br>
<br><font size=2 face="sans-serif"><b>MO Architecture</b>: A stratified
service-oriented architecture that abstracts the service layer from the
transport layer.</font>
<br><font size=2 face="sans-serif"><b>MO Technology</b>: The technology
for mission operations of space assets developed on top of the MO Architecture.</font>
<br><font size=2 face="sans-serif"><b>MO service</b>: A service defined
using the MO Technology.</font>
<br><font size=2 face="sans-serif"><b> MO
standard service</b>: An MO service standardized by the CCSDS Agency.</font>
<br><font size=2 face="sans-serif"><b> MO
bespoke service</b>: An MO service defined for a dedicated use case, typically
a mission-specific service.</font>
<br>
<br><font size=2 face="sans-serif"><b>MO Application</b>: An application
that uses the MO Technology.</font>
<br><font size=2 face="sans-serif"><b>MO Core</b>: The combination of the
elements: MAL, COM services, and Common services. These elements are expected
to be present in a typical deployment of an MO Application.</font>
<br><font size=2 face="sans-serif"><b>MO System</b>: A system composed
of MO Applications.</font>
<br>
<br><font size=2 face="sans-serif">(Others that I can think of: MO Provider,
MO binding, MO standard binding, MO bespoke binding, MO encoding, MO standard
encoding, MO bespoke encoding)</font>
<br><font size=2 face="sans-serif">Adding one page at the beginning of
the document with consistent terminology will make the reading/writing
much simpler.</font>
<br>
<br><font size=2 face="sans-serif">Best regards,</font>
<br><font size=2 face="sans-serif">César Coelho</font>
<br>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Sam Cooper <sam@brightascension.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">MOIMS-SC@mailman.ccsds.org</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">06/04/2017 10:19</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[Moims-sc] CCSDS
MO Green Book update</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">"MOIMS-SC"
<moims-sc-bounces@mailman.ccsds.org></font>
<br>
<hr noshade>
<br>
<br>
<br><font size=3>Dear All,<br>
<br>
As discussed during the last teleconference, please find below the outline
we are proposing for the Green Book update for your comments.<br>
</font>
<br><font size=4 color=#4f4f4f face="Trebuchet MS"><b>Green Book Skeleton</b></font>
<p><font size=1 color=#2f2f2f face="Verdana">Introduction (2-3 pages)</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Aim of this Green Book</font>
<li><font size=1 color=#2f2f2f face="Verdana">Structure of this Green Book</font>
<li><font size=1 color=#2f2f2f face="Verdana">How to read and use this
Green Book</font></ul><font size=1 color=#2f2f2f face="Verdana">Mission
Operations Motivation and Rationale (6-8 pages)</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Background and context</font>
<li><font size=1 color=#2f2f2f face="Verdana">Scope under consideration</font>
<li><font size=1 color=#2f2f2f face="Verdana">Challenges facing operations
and space systems development</font>
<li><font size=1 color=#2f2f2f face="Verdana">Stakeholder identification</font>
<li><font size=1 color=#2f2f2f face="Verdana">User needs</font>
<li><font size=1 color=#2f2f2f face="Verdana">Role of software, and mission
operations services, in addressing the user needs</font>
<li><font size=1 color=#2f2f2f face="Verdana">Requirements on MO</font></ul><font size=1 color=#2f2f2f face="Verdana">Mission
Operations Design (4-6 pages)</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Terminology</font>
<li><font size=1 color=#2f2f2f face="Verdana">Design principles (e.g. SOA,
messaging, at a high-level)</font>
<li><font size=1 color=#2f2f2f face="Verdana">The MO service model (non-technical
description)</font>
<li><font size=1 color=#2f2f2f face="Verdana">Providing and consuming services
(non-technical description)</font>
<li><font size=1 color=#2f2f2f face="Verdana">Applications and services</font>
<li><font size=1 color=#2f2f2f face="Verdana">Standard services</font>
<li><font size=1 color=#2f2f2f face="Verdana">MO in practice - some example
case studies</font></ul><font size=1 color=#2f2f2f face="Verdana">Mission
Operations Technology (4-6 pages)</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">The MO service model in more
detail</font>
<li><font size=1 color=#2f2f2f face="Verdana">Layering in MO</font>
<li><font size=1 color=#2f2f2f face="Verdana">Common services</font>
<li><font size=1 color=#2f2f2f face="Verdana">The role of the common object
model</font>
<li><font size=1 color=#2f2f2f face="Verdana">The Message Abstraction Layer</font></ul><font size=1 color=#2f2f2f face="Verdana">Developing
MO Applications (4-6 pages)</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Typical MO applications</font>
<li><font size=1 color=#2f2f2f face="Verdana">Relationship between applications
and services</font>
<li><font size=1 color=#2f2f2f face="Verdana">Standard vs application-specific
services</font>
<li><font size=1 color=#2f2f2f face="Verdana">MO application development
tools</font>
<li><font size=1 color=#2f2f2f face="Verdana">...</font></ul><font size=1 color=#2f2f2f face="Verdana">Integrating
MO Systems (4-6 pages)</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Essential services</font>
<li><font size=1 color=#2f2f2f face="Verdana">Detailed description of common
services and COM services</font>
<li><font size=1 color=#2f2f2f face="Verdana">The role of the MAL and communications
protocols</font>
<li><font size=1 color=#2f2f2f face="Verdana">Reference implementations</font>
<li><font size=1 color=#2f2f2f face="Verdana">Implementing an MO system
using the reference tools</font>
<li><font size=1 color=#2f2f2f face="Verdana">...</font></ul><font size=1 color=#2f2f2f face="Verdana">Managing
and Administering MO Systems (4-6 pages)</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">The role of the common services</font>
<li><font size=1 color=#2f2f2f face="Verdana">Audit trail</font>
<li><font size=1 color=#2f2f2f face="Verdana">Archiving</font>
<li><font size=1 color=#2f2f2f face="Verdana">Security</font>
<li><font size=1 color=#2f2f2f face="Verdana">...</font></ul><font size=1 color=#2f2f2f face="Verdana">MO
Communications (4-6 pages)</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Detailed look at the architecture
and the way communications works</font>
<li><font size=1 color=#2f2f2f face="Verdana">Overview of different communications
bindings</font>
<li><font size=1 color=#2f2f2f face="Verdana">...</font></ul><font size=1 color=#2f2f2f face="Verdana">Overview
of the Standards (2-3 pages)</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Top level view of the standards/books</font>
<li><font size=1 color=#2f2f2f face="Verdana">Mapping of the standards
onto topics and stakeholders</font>
<li><font size=1 color=#2f2f2f face="Verdana">Mapping of the standards/topics/stakeholders
onto the following chapters</font></ul><font size=3><br>
Stakeholders </font>
<p><font size=1 color=#2f2f2f face="Verdana">Preliminary list of stakeholders:</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Managers </font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Mission level</font>
<li><font size=1 color=#2f2f2f face="Verdana">Infrastructure</font>
<li><font size=1 color=#2f2f2f face="Verdana">Programme managers</font></ul>
<li><font size=1 color=#2f2f2f face="Verdana">Operators (Ops)</font>
<li><font size=1 color=#2f2f2f face="Verdana">System Integrators (EGSE
and AIT)</font>
<li><font size=1 color=#2f2f2f face="Verdana">Software Developers </font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Infrastructure</font>
<li><font size=1 color=#2f2f2f face="Verdana">Applications</font></ul></ul><a href="https://issues.brightascension.com/projects/ccsds-mo-support/wiki/Green_Book_Revisions/edit?section=3"><font size=1 color=#0060a0 face="Verdana">Edit
this section</font></a>
<br>
<br><font size=3 color=#4f4f4f face="Trebuchet MS"><b>Stakeholder to Section
Mapping</b></font>
<p><font size=1 color=#2f2f2f face="Verdana">For <b>Managers</b>:</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Read first three sections</font>
<li><font size=1 color=#2f2f2f face="Verdana">Read Managing and Administering
MO Systems</font>
<li><font size=1 color=#2f2f2f face="Verdana">If further detail required,
read Mission Operations Technology</font></ul><font size=1 color=#2f2f2f face="Verdana">For <b>Operators</b>:</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Read first three sections</font>
<li><font size=1 color=#2f2f2f face="Verdana">Read Mission Operations Technology</font>
<li><font size=1 color=#2f2f2f face="Verdana">If further detail required
on management, read Managing and Administering MO Systems</font>
<li><font size=1 color=#2f2f2f face="Verdana">If further detail required
on development, read Developing MO Applications</font></ul><font size=1 color=#2f2f2f face="Verdana">For <b>System
Integrators</b>:</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Read first three sections</font>
<li><font size=1 color=#2f2f2f face="Verdana">Read Mission Operations Technology</font>
<li><font size=1 color=#2f2f2f face="Verdana">Read Integrating MO Systems</font>
<li><font size=1 color=#2f2f2f face="Verdana">If further detail required
on management, read Managing and Administering MO Systems</font>
<li><font size=1 color=#2f2f2f face="Verdana">If further detail required
on development, read Developing MO Applications</font></ul><font size=1 color=#2f2f2f face="Verdana">For <b>Application
Software Developers</b>:</font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Read first three sections</font>
<li><font size=1 color=#2f2f2f face="Verdana">Read Mission Operations Technology</font>
<li><font size=1 color=#2f2f2f face="Verdana">Read Developing MO Applications</font>
<li><font size=1 color=#2f2f2f face="Verdana">If further detail required
on integration, read Integrating MO Systems</font>
<li><font size=1 color=#2f2f2f face="Verdana">If further detail required
on management, read Managing and Administering MO Systems</font></ul><font size=1 color=#2f2f2f face="Verdana">For <b>Infrastructure
Software Developers</b></font>
<ul>
<li><font size=1 color=#2f2f2f face="Verdana">Read first three sections</font>
<li><font size=1 color=#2f2f2f face="Verdana">Read Mission Operations Technology</font>
<li><font size=1 color=#2f2f2f face="Verdana">Read Integrating MO Systems</font>
<li><font size=1 color=#2f2f2f face="Verdana">Read MO Communications</font>
<li><font size=1 color=#2f2f2f face="Verdana">If further detail required
on management, read Managing and Administering MO Systems</font>
<li><font size=1 color=#2f2f2f face="Verdana">If further detail required
on development, read Developing MO Applications</font></ul><font size=3><br>
<br>
<br>
The idea of the book is that it has some general overview sections at the
beginning and then, depending on your interest, you have a set of sections
that are applicable to you that you should read. The hope is that these
later sections can be more focussed and relevant that trying to cover everything
for everybody which I think the previous document suffered from. Also,
we are trying to emphasise the goals and uses of MO rather than the technology,
so putting the horse back in front of the cart.....<br>
<br>
So, please, any comments you have on anything, but ideally other stakeholders
and the sections they would want. If you could send those to me by Monday
the 24th of April that would be brilliant.<br>
<br>
We hope to release a first draft of the document in time for us to discuss
in San Antonio. It will not be complete and will most likely only cover
a few sections but should give us an idea of direction and style.<br>
<br>
Thanks,<br>
Sam.<br>
<br>
<br>
<br>
<br>
<br>
</font>
<br><tt><font size=3>This message and any attachments are intended for
the use of the addressee or addressees only.<br>
The unauthorised disclosure, use, dissemination or copying (either in whole
or in part) of its<br>
content is not permitted.<br>
If you received this message in error, please notify the sender and delete
it from your system.<br>
Emails can be altered and their integrity cannot be guaranteed by the sender.<br>
<br>
Please consider the environment before printing this email.<br>
<br>
</font></tt><tt><font size=2>_______________________________________________<br>
MOIMS-SC mailing list<br>
MOIMS-SC@mailman.ccsds.org<br>
</font></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-sc"><tt><font size=2>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-sc</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br><PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE>