Architecture Telecon Report

Architecture Telecon Report

<p> Report of the Fourth Teleconference of the CCSDS TSG Architecture Working Group</p><p> held on July 18, 2002</p><p>Takahiro Yamada, ISAS, Rapporteur</p><p>1. DATE AND TIME</p><p>The fourth teleconference of the Ad Hoc TSG Working Group on Architecture (hereafter called the Architecture Working Group or AWG) was held from 15:30 to 17:00 on July 18, 2002 (UTC).</p><p>2. PARTICIPANTS</p><p>Takahiro Yamada ISAS [email protected] Peter Shames NASA/JPL [email protected] Adrian Hooke NASA/JPL [email protected] Fred Brosi NASA/GST [email protected] Donald Sawyer NASA/GSFC [email protected] Lou Reich NASA/CSC [email protected]</p><p>3. DISCUSSION SUMMARY</p><p>Brosi reported on the result of the action item 3-1, which was jointly prepared by Brosi and Reich. Their conclusions were that the Reference Model for Open Distributed Processing (RM-ODP) is a flexible model that can be adapted to different needs and that we should use it as guidance against which the CCSDS architecture is to be checked. </p><p>There may be redundancy in the CCSDS models (e.g., in the connectivity, functional and physical models), but these models may be uniformly expressed as locations of entities if the RM-ODP is used.</p><p>Quality of service (reliability etc.) can be elegantly dealt with by the RM-ODP.</p><p>The RM-ODP has been used in some of the work of OMG.</p><p>There was a question on whether an architecture description language is used in the RM- ODP, and the answer was that some languages can be applied (including ADL, ACME, IDL, and OCL=Object Constraint Language).</p><p>However, a concern was raised about using a complicated standard like ODP, in view of the time and resources that we can use between now and the next CCSDS meeting in October. We should rather focus on a simple, high-level description to be presented to project managers.</p><p>The CCSDS architecture should be used as a framework for the reorganization of CCSDS, which is being discussed by the Management Council right now.</p><p>The consensus among the participants was that we should continue working on the current CCSDS model, which will be reviewed from the viewpoint of the RM-ODP at a later time.</p><p>4. ACTION ITEMS</p><p>No. Action Assigned Due date Status to 1-1 Distribute material on what should be All June 7, 2002 Closed contained in each of the seven models. 1-2 Submit comments on the first input and All June 14, 2002 Closed distribute additional material if necessary. 1-3 Contact TC20/SC14 and find out the JPL June 18, 2002 Open status of "ISO/DIS 14711 Unmanned mission operations concepts -- Guidelines" 2-1 Generate a document that describes key Yamada June 19, 2002 Closed concepts of the architecture. 2-2 Provide definitions of key concepts. Shames June 27, 2002 Closed 2-3 Provide information on registry model. Reich June 27, 2002 Open 2-4 Contact ESA for possible participants Yamada June 19, 2002 Closed 3-1 Investigate whether ODP-RM can be Brosi and July 18, 2002 Closed applied to the CCSDS architecture Reich 3-2 Provide FAX number to Reich All July 18, 2002 Closed 4-1 Provide a copy of the mapping exercise Shames July 26, 2002 Open slides to Reich 4-2 Provide information on RM-ODP which Brosi July 26, 2002 Open CCSDS should look at</p><p>5. NEXT TELECONFERENCE</p><p>The fifth AWG teleconference is scheduled for 15:00 Friday, July 26, 2002 (UTC). </p><p>The sixth AWG teleconference is scheduled for 15:00 Thursday, August 8, 2002 (UTC). </p>

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    2 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us