CCSDS System Engineering Area (SEA) System Architecture Working Group (SAWG) Meeting Agenda

Slide Note
Embed
Share

The CCSDS System Engineering Area (SEA) System Architecture Working Group (SAWG) meeting agenda outlines discussions on Green Book status updates, RASDS revisions, SCCS-ARD/ADD revisions, joint publication processes, and more for Fall 2020. It also covers plans for Reference Architecture revisions, collaboration with SC14, glossary and terminology discussions, and integration of CSS documents into SEA.


Uploaded on Sep 28, 2024 | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

E N D

Presentation Transcript


  1. CCSDS System Engineering Area (SEA): System Architecture WG (SAWG) Meeting Agenda Peter Shames, SEA AD 8 Nov 2020 8 Nov 2020 SEA-1

  2. SAWG Fall 2020 Working Meeting Agenda Meeting 1, Monday, 9 Nov 2020 Agenda review, Peter, 20 minutes Application and Support Layer (ASL) Green Book status update (it has been approved by CMC for publication), Peter, 10 minutes Review of proposed set of core RASDS revisions, including ASL and MBSE extensions, Peter, 60 minutes RASDS discussion, 30 minutes Meeting 2, Tuesday 10 Nov 2020 Review of SC14 related RASDS revisions, including new viewpoints, Fred, 30 minutes Discussion of integration and (joint or parallel) publication process, Peter & Fred, 45 minutes Rough work plan for RASDS revisions, Peter, 30 minutes Brief discussion of SANA / Terminology issues, Daniel, 15 minutes Meeting 3, Wednesday 11 Nov 2020 Review of needed revisions to SCCS-ARD/ADD, John, 45 minutes Coordination between SCCS-ARD/ADD and RASDS revisions, Peter & John, 30 minutes Rough work plan for SCCS-ARD/ADD revisions, John & Peter, 30 minutes Closing discussions, All, 15 minutes 8 Nov 2020 SEA-2

  3. SAWG Reference Architecture Plan Publish SAWG Applications and Support Layer(ASL) reference architecture Covers MOIMS and SOIS, uses RASDS methodology Approved for publication, in CMC poll CMC-P-2020-10-003 Authorization to publish CCSDS 371.0-G-1, Application and Support Layer Architecture (Green Book, Issue 1) Initiate revisions to the Reference Architecture for Space Data Systems (RASDS) document Extend existing framework with new and updated viewpoints Work jointly with TC20/SC14 on new viewpoints Collaborate with SC14 (and ECSS?) on glossary & terminology (see separate discussion) Bring the CSS Space Communication Cross Support Architecture (SCCS) documents into SEA for updates These are already architectural in nature and use RASDS The CSS would have to re-start their Cross Support Architecture WG, which is now dormant Given necessary resources, the CSS Area and CESG have agreed that the project could better be handled in SEA SAWG 8 Nov 2020 SEA-3

  4. Other Related Activities SC14 would like to have an ontology and already uses RASDS This is proposed as a joint / collaborative effort with them SC14 also has an information management and control issue, similar to what the CMC has identified A formal liaison relationship between CCSDS and SC14, that covers terminology, has been approved ECSS / ES is moving toward a data repository for their requirements ECSS data repository provides a representation of the current library of documents Repository provides for presentation in a number of forms, i.e. output to Word, database, other tools The ECSS glossary will be recreated from the repository, and the relationships among terms will be defined, but there are no plans to rationalize the contents of the library 8 Nov 2020 SEA-4

  5. Terminology, Ontology, Reference Architecture Definitions Terminology: a set of terms and their descriptions, most often rendered in some narrative form. From Wikipedia: a general word for the group of specialized words or meanings relating to a particular field . Ontology: a formalized naming and definition of terms, categories, properties, and their relationship to other terms. From Wikipedia: a representation, formal naming and definition of the categories, properties and relations between the concepts, data and entities that substantiate one, many or all domains of discourse . Reference Architecture: a formalized definition of viewpoints, views, the objects they describe, and their relationships suitable for use in creating and describing specific systems architectures. From Wikipedia: A software reference architecture is a software architecture where the structures and respective elements and relations provide templates for concrete architectures in a particular domain or in a family of software systems. System can, obviously, be substituted for software . The elements and relations required for a reference architecture are best formalized in an ontology, but a set (or sets) of terminology may have to suffice. 8 Nov 2020 SEA-5

  6. BACKUP 8 Nov 2020 SEA-6

  7. SAWG Observations on Terminology Some of the terms used in CCSDS documents are not even in the CCSDS Glossary We only have accurate information models and schema for a small sub-set of the terms in use Some terminology is defined in multiple different standards, and this is where issues arise Lack of consistent terminology makes automation and cross use of terms much more difficult Some terminology is in isolated domains and not an issue Multiple inconsistencies in use of terminology Collisions of usage (same word, two different meanings) Specializations (same word, on analysis one derived from another) Multiple terms used for the same things Internal inconsistencies in usage or definitions Inconsistent use of representations (lack of class diagrams) Inconsistent references to external standards (ISO BRM and other) Some differences appear to be easy to resolve (reference the document/namespace), others will require more work 8 Nov 2020 SEA-7

  8. Connectivity (& Physical) Viewpoint - Component / Connector (Node / Link) Examples Data System Components (CPU, instruments, SSR) Connectors (network, data bus, serial lines, backplane) Telecomm Components (transmitter, receiver, antenna) Connectors (RF link, optical link, waveguide) Structural Components (S/C bus, physical link, arm/articulation, structural attributes of other components) Connectors (joint, bolt (incl explosive), weld) Power Components (solar panel, battery, RTG, switches, power attrib of other components) Connectors (power bus, rotational power connectors) Thermal Components (cooler, heater, thermal attributes of other components) Connectors (heat pipe, duct, free space radiation) Propulsion Components (motor, wheel, thruster, gyro) Connectors (contact patch, gravity, radiation pressure) 2 Mar 2015 8 Nov 2020 SEA-8 PS 8

Related


More Related Content