1 / 4

Planetary Science Archive

Planetary Science Archive. PSA User Group Meeting #1. PSA User Requirements: Overview / Discussion. PSA UG #1  July 2 - 3, 2013  ESAC. PSA URD Status. Currently in V4.0 – Oct 2011 10-02-2010: internal meeting to consolidate the requirements

davina
Download Presentation

Planetary Science Archive

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. Planetary Science Archive PSA User Group Meeting #1 PSA User Requirements: Overview / Discussion PSA UG #1  July 2 - 3, 2013  ESAC

  2. PSA URD Status • Currently in V4.0 – Oct 2011 • 10-02-2010: internal meeting to consolidate the requirements • Review of the compliance of the current PSA with the requirements. Around 80% of requirements are already met • April-June 2010: Intense testing of the User Interfaces against the requirements of each mission with the Project Scientists. • Iterations within the PSA and with the MEX Project Scientist on the Map Browser have also been incorporated. • Requirements for individual missions / disciplines not defined. • Further interaction with the user community is needed. Regular interaction should be established to maintain the document.

  3. ‘E-PSA’ URD Status • Drafted requirements in 2011/2012 • Unofficial and pending further discussions between SAT and PSA-DH • Based on second generation od access systems (e.g. SOHO). • No requirements yet for third generation (e.g. Ulysses / XMM).

  4. PSA URD Discussion • URD discussion objectives: • Tighten up loosely defined requirements • Identify specific and workable requirements where needed • Questions: • Requirements missing? • Requirements poorly defined? • Are the priority and criticality of requirements correct? • How can we (and should we) start to draft requirements for a ‘thin layer’ UI? If so, how many requirements are transferable directly? • How can requirements be added to best address the needs of your discipline?

More Related