1 / 13

Systems Architecture WG: Report of the Spring 2005 Meeting

Systems Architecture WG: Report of the Spring 2005 Meeting. April 14, 2005 Takahiro Yamada, JAXA/ISAS. Summary Technical Status. Systems Architecture WG Goal: Develop a reference architecture and a formal representation method Working Group Status: Active _X_ Idle ____

efia
Download Presentation

Systems Architecture WG: Report of the Spring 2005 Meeting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Systems Architecture WG:Report of the Spring 2005 Meeting April 14, 2005 Takahiro Yamada, JAXA/ISAS

  2. Summary Technical Status • Systems Architecture WG • Goal: Develop a reference architecture and a formal representation method • Working Group Status: Active _X_ Idle ____ • Working Group Summary Situation: • Working Group Summary progress: • Updated the RASDS document (near BCP), • Developing a formal model (before WB) • Problems and Issues: • Not enough resources, Propriety issue (XASTRO profile)

  3. Executive Summary • Review of RASDS was made by experts on RM-ODP and a discrepancy between RASDS and RM-ODP in the use of the concept of Viewpoints was discovered. • It was agreed to revise the RASDS document so that it is aligned better with RM-ODP. • It was also agreed that the RASDS formal model should be developed based on the ISO standard on “UML for ODP.”

  4. Summary of Goals and Deliverables • Define a reference architecture that provides a framework for generation of space data systems standards and development of space data systems. • Document the reference architecture identifying basic elements. • Develop a document that provides to the other Working Groups and BoFs guidelines on how to apply the reference architecture. • Develop formal methods for representing space data systems architectures that will enable sharing of architectural information among engineers. • Develop tools that will facilitate design, modeling, and simulation of system architectural designs. • Develop a cross support service architecture (TBC)

  5. Progress Achieved • With regard to items 1 and 2 (see the previous page), a review of RASDS was made by experts on RM-ODP and a discrepancy between RASDS and RM-ODP in the use of the concept of Viewpoints was discovered. • It was agreed to revise the RASDS document so that it is aligned better with RM-ODP. The document will explain the types of entities and how each type is represented in the Viewpoints. • With regard to item 4, it was agreed that the RASDS formal model should be developed based on the ISO standard on “UML for ODP.” • The progress of the XASTRO2 project was reviewed but there is still a propriety issue that CCSDS cannot use it. There was a misalignment between XASTRO2 and RASDS.

  6. Near-Term Schedule

  7. Open Issues • It was agreed that the RASDS formal model should be developed based on the ISO standard on “UML for ODP,” but we need to work out how it should be adapted so that it can be usable by space system experts without reading a big text book on UML. • It was verbally stated by CMC that the development of RASDS must be terminated and the resources must be transferred to development of a cross support service architecture. • Requirements will be provided by IOAG but resources necessary to do the work must also be provided by Agencies. • Some Agencies (NASA, ESA, CNES, JAXA) are still interested in developing a formal model and some of them (at least JAXA) are willing to provide necessary resources,

  8. Action Items • Revise the RASDS document based on the discussion at the meeting (so that it is more compatible with RM-ODP) • Actionee Shames • Due date 30 June 2005 • Edit a Green Book (informational) that explains the concept of RASDS • Actionee Yamada • Due date 30 June 2005 • Review the “UML for ODP” document and propose how we can use it as the formal model of RASDS • Actionee All • Due date 30 June 2005 • Establish a liaison relationship with ISO/IEC JTC 1/SC 7/WG 19 • Actionee Hooke, Shames and Wood • Due date 30 June 2005

  9. Resource Problems • There may not be enough resources to perform items 4 through 6 of the Goals and Deliverables.

  10. Risk Management Update • It is still unclear if enough resources are available from the Agencies to perform the necessary jobs.

  11. Cross Area WG / BOF Issues • We need a CCSDS-wide standard on a method for describing objects (services, data, devices, etc.) with templates for describing some basic objects. • There are several ways of describing services within CCSDS (Space Link Protocols, SLE Services, SM&C Services). • We need a CCSDS-wide standard on a method for managing objects (services, data, devices, etc.). • There are several activities for developing management methods within CCSDS (Onboard network management, SLE Service Management, SM&C Service Management).

  12. Resolutions to be Sent to CESG and Then to CMC • The Systems Engineering Area resolves to establish a liaison relationship with ISO/IEC JTC 1/SC 7/WG 19 for cooperating in development of RASDS and its formal model, and notify the CMC of the establishment of the liaison.

  13. New Working Items, New BOFs, etc. • It was verbally stated by CMC that a cross support service architecture must be developed by SAWG.

More Related