30 likes | 110 Views
Summary of the Joint Meeting on M&C (1). M&C Architecture There is already an architecture in the MOIMS books. But it should be reviewed by others Areas. Boundary between MOIMS and SOIS
E N D
Summary of the Joint Meeting on M&C (1) • M&C Architecture • There is already an architecture in the MOIMS books. But it should be reviewed by others Areas. • Boundary between MOIMS and SOIS • SOIS is not developing M&C services. It is only developing device access services and has given to MOIMS the responsibility of developing services related to M&C. • Device Description and Modeling • There are multiple activities on modeling (SOIS, MOIMS, CSS) • Who should be responsible? • Messaging • There are multiple activities on messaging (SOIS, MOIMS, CSS) • Who should be responsible?
Summary of the Joint Meeting on M&C (2) • RASDS • The contents are OK, but they are presented in an uncomfortable way. • It shows concepts but they are too abstract. We need a formal template for specifying services.
Tasks of Systems Engineering Area • Collect all the architectures developed by the CCSDS Areas and assess whether they are all compatible with each other • MOIMS, SOIS, CSS, Security, Information, OAIS, … • Collect all the services developed by the CCSDS Areas and assess whether they are all compatible with each other • Synthesize the results