| | | 1 | The objective of the Systems Engineering Area (SEA) is to address system-wide architectural and engineering topics that are so pervasive that they span over all, or several, other CCSDS areas. This work includes development of specific standards and guidelines, development of system architectures and models, coordination/collaboration with other areas, and otherwise supporting CCSDS and CMC engineering and operational goals.
The SEA system architecture tasks include end-to-end reference architecture, architecture analysis and description methods, and related cross cutting terminology topics. The SEA security architecture and standards are to be used by other CCSDS areas requiring security guidance and services. The Delta-DOR services touch upon the Cross Support Services (CSS) and Space Link Services (SLS) areas, and Mission Operations and Information Management Services (MOIMS) may be involved in planning for use of these services. The information architecture and registry services also cross cut MOIMS, CSS, Space Internetworking (SIS), and other Services. Extensible Markup Language (XML) standards and guidelines and other special cross-cutting topics that are guided by SEA affect all of the other areas. As system or information architecture standards are developed, SEA will coordinate with the other CCSDS areas and working groups to develop approaches that align with CCSDS goals for interoperability and cross support. The strategic goals of the SEA are listed below.
|
| | | 2 | Complete a security architecture and the framework, infrastructure mechanisms, and techniques to protect system elements, communication links, networks, and information as it flows through the end-to-end space mission system.
|
| | | 3 | Define the mechanisms for performing Delta-DOR spacecraft ranging operations and the exchange and processing of observational data. Ensure that operational planning (service management and DOR tones) and ancillary tasks (Quasar reference sources) are well specified.
|
| | | 4 | Complete a reference information architecture, information infrastructure services including service-oriented architecture (SOA) and interfaces, and frameworks for handling operational data flows and supporting multi-agency federated data systems.
|
| | | 5 | Define the XML standards and guidelines to be used across all CCSDS areas.
|
| | | 6 | Define an extensible timeline data standard for exchange of linear and activity timelines to be used across all CCSDS areas.
|
| | | 7 | Define an overall time services architecture for time correlation, synchronization, and distribution, for end-to-end mission operations and cross support throughout the mission lifecycle. |
| | | 8 | Produce documents that will provide an architectureal description of the CCSDS
work, understanding of the links/interactions between the different standards, identification of gaps, and provide the means to describe these architectures, information models, and policies in a consistent way. Produce a CCSDS Application Layer Architecture showing the relationships among all of the application layer standards and services and their relationships to supporting standards for space communication and cross support. This is a companion document to the Space Communication Cross Support architecture (SCCS-ADD) that documents SLS, SIS, CSS, and SEA standards relationships. Work with MOIMS and SOIS to document the relationships between the standards in these two areas and with those already documented in the SCCS-ADD. Revise the CCSDS Reference Architecture for Space Data Systems (RASDS) to accomplish its 5-year review and, in a second phase, augment the existing document with methods using Model-Based System Engineering (MBSE) and SysML. Working with the other areas, update the CCSDS Glossary to provide a self consistent and unambiguous set of terms. Create a Registry Management Policy and related procedures and information models for managing the sets of registry information created by the other CCSDS areas. |
