1 / 9

The End User in the NASA Data System Reference Architecture

The End User in the NASA Data System Reference Architecture. Christopher Lynnes Goddard Earth Sciences Data and Information Services Center. Goal: Convince you to include the End User Domain as part of the Data System in the Reference Architecture. Learning from the Past

arion
Download Presentation

The End User in the NASA Data System Reference Architecture

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. The End User in the NASA Data System Reference Architecture Christopher Lynnes Goddard Earth Sciences Data and Information Services Center

  2. Goal: Convince you to include the End User Domain as part of the Data System in the Reference Architecture • Learning from the Past • What About the End User?

  3. HDF-EOS EOSDIS Architecture

  4. A Lesson Learned (You think I would put it in writing???)

  5. A Lesson about the Upside of Including the User Domain

  6. What About the End User? • The User • Human-Computer Interface (Usability) • Machine user needs • User workflow • Adoption psychology and sociology • The User’s Platform • Client-server integration • Especially the ones the user already has • Client-client integration • E.g., discovery client with analysis client

  7. What Could We Do in the User Domain? • Promote user-centric data formats and structures • Develop services tuned to the client base • e.g., Data Nodes for the Earth System Grid • Infiltrate the client • Distribute plug-ins, extensions, add-ons, skins • e.g., IDV-GEON • Extend the client into data system • Deploy data system capabilities to the user side • e.g., SeaDAS • Help client developers • e.g., API’s, example/reference implementations, widgets/scriptlets, etc.

  8. A Cautionary Tale...

  9. Guidelines for Data System Architects Working in the User Domain • Develop a User Model and Use Cases • See the system through the eyes of the user. • Understand the user environment. • Platforms, tools, firewall rules... • Emphasize enabling, not controlling. • Play Nicely! You’re on their turf.

More Related