cesg-1

CSS Area Report -- Super BOF Background

• E-mail From A. Hooke to CESG: (CSS AD emphasis )

Date: Fri 02 Oct 2009To: CESGcc: CMCSubject: Proposed way-forward for a "Service Oriented Architecture (SOA) for Space Missions."

“…. . The IOAG also asks the CCSDS to study whether the current CCSDS work could be expanded to embrace the production of a “Service Oriented Architecture (SOA) for Space Missions…

…In response to the IOAG resolution, it is proposed that the CESG will convene a BOF at the October meeting with a view towards chartering a Working Group to create some kind of “SOA for Space Mission Operations” – probably more of a “SOA-like” service architecture framework for CCSDS services on ground and in space. This would essentially be the top-level CCSDS framework for space mission operations into which all of the other CCSDS work would be referenced…

…If acceptable to the CESG then the CSS Area Director should convene the BOF during the upcoming CCSDS meeting at ESTEC. It has been suggested that in view of the importance of this activity, the BOF should meet on the morning of Tuesday 27 October…”

cesg-2

CSS Area Report -- Super BOF Meeting Summary

SOA for Space was only hinted at; need for CCSDS Model, guidance information at CCSDS-wide level was the primary output of the BOF

Discussed only briefly:• Formation of SOA for Space WG – really SOA for CCSDS – to address all

IT infrastructure issues at CCSDS level• Produce recommendations on SOA for CCSDS• Re-programming of existing WG

• How long will does it take to produce the recommendation(s)• What do we do with current efforts?

Goals for NEW WG as indicated at conclusion of Super-BOF: 1. Exhaustive list of services identifying cross-support services 2. Cross-Support & Interoperability Use cases / Operational scenarios, 3. overlap and gap analysis (identify redundant and missing services) 4. Business cases (based on existing and in-work services), 5. Architecture of existing and in-work services including an information model, 6. Abstract service definitions: rational for a service, content of service specifications, taxonomy 7. CCSDS Reference architecture. Identify impact on existing architecture.

cesg-3

CSS Area Report -- Super BOF Plan of Attack

CESG/CMC: Form BOF ASAP•Nominees 07 Nov 09•BOF Ground Rules, Initiation 20 Nov 09

BOF: Rapid Identifications re Items 1 + 2•(List of Services)•(List of Scenarios)•15 Dec 2009

CESG: Vote on Identifications •Feedback to BOF•10 Jan 2010

BOF: Draft Concept Paper•Points 3 – 7, WG approach, WG Deliverables•Identification of Key Trades, fitting SOA to CCSDS•31 January 2010

CESG: Review Draft, Feedback to BOF•15 Feb 2009

BOF: Final Concept Paper• 28 Feb 2010

Let’s call this the CCSDS Reference Architecture BOF

cesg-4

CSS Area Report -- Additional Recommendations (Post Super BOF)

• Initiate parallel activity (in addition to CCSDS Reference Architecture) with goal of producing concept paper for SOA aspect of CCSDS• Focused exclusively on information infrastructure

services• Aligned with current industry SOA approach• Identify deliverables relative to related CCSDS activities

on information architecture, registries/SANA, directories• Due date of 28 Feb 2010 (same as reference architecture

BOF concept paper)• CESG/CMC makes informed decision for WG initiation at

Spring meetings

• Going forward…Need to seriously consider that CCSDS reference architecture be visited in a structured formal manner at every CCSDS technical meetings (vs. MOUs)

cesg-5

CSS Area Report -- Super BOF Conclusion

• Agreement that overall CCSDS technical framework (reference architecture) in much need of (re-)definition

• That SOA for CCSDS itself was not directly addressed (but suggested to draft two concept papers in parallel)

• Need to seriously consider that CCSDS framework be visited in a structured formal manner at every CCSDS technical meeting (CESG standing action)

• Concern:• BOF members need both excellent domain knowledge and

available time

cesg-6

Systems Engineering Area Report

• Super BoF• Reviewed visions of what a “SOA for Space” might be, as presented by

CESG chair and MOIMS, SEA and CSS ADs• Identified at least four different variants on how “SOA for Space” and

“Services” were being interpreted across CCSDS• Agreed to initiate a BoF to develop a charter for a CCSDS Reference

Architecture (or Model) that would map all CCSDS services and their relationships (see CSS presentation for details)

• SEA view is that a Space Information Services Architecture (e.g. SOA for Space) is different than the CCSDS Reference Architecture:- Define a reference end-to-end space information service architecture for

interoperability and cross support - Common framework and elements- Both flight and ground data system operations

- Define standard components and services, including their specifications- Define secure deployment and federation models for information services- Define and leverage common methods for representing information models - Develop best practices for the design of standard data definitions, including

XML schemas, data dictionaries, and common registries

04 November 2009

D. Cross Area Meetings, contd

cesg-7

• CESG strongly advocates that CCSDS needs an overall reference architectural framework into which all of its work can be aligned in terms of services and standards, and that it also needs a consistent way to express how those services should be defined and specified. CESG recommends that the CMC should endorse the “way forward” proposal made by the CSS Area:

• CESG notes that this activity is likely to need temporary redirection of resources from several information architecture-related activities in MOIMS and SEA, including SM&C• Current work cannot totally stop• Question of where eventual WG would be located?• CESG Chair files a “friend of court” brief that – as the major stakeholder in the outcome –

SM&C should be given this job

CESG General Issues/Concerns [3] (CESG Report CMC)

Team-1: Services, Scenarios, Framework

Team-2: Service Definition Technology28 Feb 10

WG ConceptWG

FormedMay 09