Tools Survey Results Engineering Node July 18, 2005 pds.nasa.gov

Tools Survey Results Engineering Node July 18, 2005 http://pds.nasa.gov

Topics Objective Tools Survey Summary Developing a Tool Plan and Approach Schedule/Plan Sample Requirements 2

Objective Start to address current tool deficiencies – – – – Mismatch between current functionality and current needs Lack of correlation with PDS Standards Current tool set is poorly integrated Too many bugs, difficult to use, etc. Goal is to create a more integrated, modern, and better designed toolkit, by recasting the tools as a framework, based on the PDS Model, and implemented as a set of re-usable components 3

Tools Survey Summary Existing Tools – Popular tools – Not so popular tools – Popular Functions – In general, functions associated with Label Validation and Product Validation. Interesting Notes The rest of the functions were given a lukewarm response, half for and half against for the most part. Issues – Each tool had at least 2 nodes that voted for “should still be supported” or “critical to do job”. New Tool Functions – DDICT, KWVTool, Tab2Lab, Table checker, tbtool Interesting Notes Perl Validation Toolkit and the accompanying LVTool as well as NASAView. Some comments indicated confusion on the respondents part with regard to the survey and how to answer the questions. Regardless of functionality, many respondents desire a component based tool set/library with more emphasis on command-line and common API’s than on GUI front-ends. 4

Developing a Tool Plan and Approach Determine existing functionality – – Determine desired functionality – – – New development driven by reviewed requirements Maintenance development driven by SCR’s Enhanced testing (unit tests and standard set of test data) Configuration management Start with highest rated capabilities first and follow and phasing approach – Start with Tools Survey results Correlate with Level 1/2 requirements Hold appropriate reviews and get Node buy in Follow a structured Software Development Lifecycle – – – – Evaluate existing tools for current capabilities Offer a training session on existing tools Phase I: Label and product validation Develop a plan for phasing out obsolete tools – – Provide consistent functionality and interfaces, if possible, in the new tools set Offer conversion support 5

Schedule/Plan - Phase I Conduct tool survey – Brief MC (Jul 2005) Phase I (scoped to Label and Product Validation) – Identify tool plan and approach (Jul 2005) – Develop tool requirements (Jul 2005 - Sep 2005) – Requirements review (w/ node tech staff) Present results to MC Develop tool design (Sep 2005 - Oct 2005) – – – Discuss with MC Design review (w/ node tech staff) Present results to MC Implement (Oct 2005 - Dec 2005) Beta test (Dec 2005 - Feb 2006) Software release (February 2006) Phase II – – Label generation Plan for phasing out obsolete tools 6

Sample Requirements - Phase I (Derived from Tools Survey) Label Validation – Validate the PDS label or catalog against a specified version of the data dictionary – Ensure all required keywords are present – Ensure there is a data pointer for each data object – Ensure keywords in the PDS label are in the psdd and the values are valid according to the psdd – The PDS label has valid syntax according to ODL Product Validation – Label validation as described above – Validate a table against it's label Others – Download latest or selected dictionary version upon customer demand 7