1 / 21

Build 9b Status and Plans

Build 9b Status and Plans. PDS Management Council F2F Towson, Maryland March 28, 2019. Overall Plan for Build 9B. Build 9b is the next planned build and release of PDS4 which will include model, documents, and software (system and tools).

joehanson
Download Presentation

Build 9b Status and Plans

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. Build 9b Status and Plans PDS Management Council F2F Towson, Maryland March 28, 2019

  2. Overall Plan for Build 9B Build 9b is the next planned build and release of PDS4 which will include model, documents, and software (system and tools). IM and Tools will be tested by Nodes and IPDA in March. Delivery to I&T is planned for March 29, 2019. Integration and Test is planned for April 2019. Deployment to start in early May 2019.

  3. Information Model and Standards Components Information Model Specification (HTML) Release Notes Data Dictionary (HTML and PDF) XML Schema and Schematron

  4. Summary of Information Model Changes • Common dictionary – Implemented 14 approved SCRs • Notable Changes (detailed list in backup) • CCB-202 - Amend the Instrument class context product • CCB-235 - Add data type ASCII_BibCode • CCB-238 - Associate Thumbnail to other products • CCB-243 - Consolidate Context Target for Samples • CCB-245 - Deprecate 'Airborne' as host type • CCB-246 - Deprecate 'Sun' as a separate context target • Local Data Dictionary (LDD) • Tested LDD Ingestion Process; under review • Updated LDDTool significantly • CCB-203 - enforce constraints on pds namespace attributes • Removed obsolete entities – e.g., Telemetry Parameters

  5. Discipline and Mission LDDs

  6. Information Model Build 9bTesting and Release Plan • Feb 15, 2019 – Friday – All SCRs to be implemented have been identified • Feb 15 - 28, 2019 – Finish SCR implementation • Release IM to development directory • Internal testing • Fix bugs • Mar 1 – 14, 2019 – EN, DN, and IPDA testing • Release IM to development directory • Perform regression testing at EN • Mar 15 - 28, 2019 – Prepare IM for release to System I&T • Mar 29, 2019 – Friday – Release IM to release directory • “Start of Build” and System I&T • IM is frozen • System I&T - System Testing • System Release Build

  7. Build 9b Software Components Tools Services Registry/Search Includes support for Tool and Data Dictionary content Transport Backward compatible with the PDS-D Product Server Report Generating monthly HQ reports • Ingest • Harvest Tool • Catalog Tool • Preparation • Generate Tool • Transform Tool • Validate Tool • Inspect Tool • Core and PDS4 Tools Libraries

  8. Major Software Changes(Tools) • Validate Tool • Added spot checking of data content • Added additional checks that address more of the Validate Tool requirements • Per TWG request, added validation of Context Product references in labels • Transform Tool • Added additional support for transforming to FITS • Inspect Tool • Added initial support for visualizing PDS3 products • Harvest Tool • Updated to interface with the new Registry/Search Service • Updated to ingest full product labels into new Registry/Search Service

  9. Major Software Changes(Services) • Registry/Search • Integrated Registry and Search Services together under one technology (Solr 7.7) • Provide capability to deploy Service within Docker Container • Tracking • Added additional service interfaces (insert/update) for the following: • Product, Archive, Certification, and NSSDCA statuses • Delivery, Role and Users • Instrument, Investigation (mission), and Node References

  10. Registry/Search Upgrade • Full product labels will get stored under a Registry Index in Solr • Old registry only stored product metadata • Harvest Tool was updated to support this feature • Will improve re-indexing performance • Improved performance over the old Registry • Initial Metrics ingesting 1 million products • Ingest took about 14 hours (old version ~= several days) • Data Footprint • Harvest Intermediate Data: ~4.1 GB • Registry Index (where the product labels reside): ~3.3 GB • Search Index (where search product metadata resides): ~445 MB • Total Footprint: 7.8 GB

  11. Changes to Standards Reference and Documents • Documents now part of build process • Document Authoring Team (DAT) • S.Slavney; R.Simpson & R.Joyner • Document Review Team (DRT) • S.McLaughlin; S.LaVoie; E.Guinness; T.King • Document update plans • 2/24 – Distribute Data Author Team (DAT) updates to the Data Review Team (DRT) • 4/5 – Data Review Team (DRT) responses due • 4/19 – Document updates completed and posted

  12. Schedule forSoftware Delivery March 4, 2019 – March 15, 2019 – TWG Beta Test March 18 – 22, 2019 – Address issues, final component-level testing March 25 – 29, 2019 – Compile and package components March 29, 2019 – Deliver Software to System I&T April 8 – May 17, 2019– System Integration & Test May 20 – June 14, 2019 – System Deployment June 14, 2019 – Software made publicly available on the EN Site

  13. I&T Plan • System I&T is an iterative process. • Test cases are derived from requirements. • Regression testing is mandatory for each build. • Test cases are used to exercise software and services with example data products delivered with each build. • All issues found are recorded in the tracking system JIRA. • Prior to completion of a system build, all show stopper issues must be corrected and the fix must be verified, follow by regression testing. • Only when I&T is completed without major anomaly, then system can be deployed. • Full details are captured in test report which identifies result of each test case, and their traceability to requirements.

  14. QA Process IM Beta Test Data Tools Beta Plan/Data I&T Plan/Data EN & Node Beta Test Beta IM Build Software EN System I&T I&T Results Beta Software CCB Approved SCRs S/W JIRA Issues Ops Software Draft Std Ref, DPH, Concepts Doc Review Ops Std Ref, DPH, Concepts

  15. I&T Input/Output • Input • IM V1.12.0.0 as a result of Node testing of candidate IM based on approved SCRs by CCB • Build 9b system software including upgrades and fixes of issues captured in JIRA • Build 9b test plan including new test cases of any new features and regression test cases • Build 9b test data • Output • Any new issues found will be added to JIRA • Any fixed issues will be closed in JIRA • Test result will be documented (including requirement traceability matrix)

  16. Questions/Comments

  17. Backup

  18. Approved and Implemented SCRs

More Related