250 likes | 383 Views
4-D Wx Data Cube Data Formats & Decoders. Introduction & Overview. Agenda for the Week. Monday Logistics (host) Introductions Meeting Objectives (Tom & Mark) Major Activities/Milestones Through End of FY11 FY10 IT Demonstration Objectives Participants Demonstration Plan
E N D
4-D Wx Data CubeData Formats & Decoders Introduction & Overview
Agenda for the Week • Monday • Logistics (host) • Introductions • Meeting Objectives (Tom & Mark) • Major Activities/Milestones Through End of FY11 • FY10 IT Demonstration • Objectives • Participants • Demonstration Plan • Demonstration Test Plan • Product Format & Decoders • 4-D Wx Data Cube Product Overview • 4-D Wx Data Cube Decoder Overview • Tuesday & Wednesday • Data Format & Decoder Discussions & Planning • Thursday • General Discussion
Meeting Objectives • Develop a plan for • proceeding with developing additional data formats: a prioritized list with assigned organization & completion date for each • which data sets can be published as part of the FY10 IT Demo and by whom • Discuss issues with decoders as related to the 4-D Wx Data Cube and develop a plan with dates for resolution • Gain a mutual understanding of high-level schedule of 4-D Wx Data Cube activities through the end of FY11 • Gain a mutual understanding of objectives and current planning status for the FY10 IT Demo • Gain an understanding of significant issues and concerns
Design Review • The 4-D Wx Data Cube Team has decided to schedule a Cube Design Review early in CY10 • The purpose is to conduct an in depth look at all aspects of the development efforts including: • Architecture • RIs • Reg/Rep • Service Adapters • The Design Review will be discussed this Thursday
FY10 IT Demonstration Objectives • Utilize: • NOAAnet & FTI to communicate between NOAA & FAA • presumed elements of operational architecture to the maximum extent possible • Maximize products published by NOAA & FAA • Demonstrate a SAS-like capability (manual & automatic) • Measure & report communications & processor performance • Publish NEVS data • Implement security measures • Utilize appropriate standards
FY10 IT Demonstration Other • Utilize a simulator to make requests for data in order to exercise the software • Clearly separate non-Cube functionality from Cube functionality • Develop our own front end (separate from ADDS) • Develop and exercise more rigorous testing, followed by a demonstration
Lessons Learned - 2009 IT DemoPreparation (including dry-run)
Lessons Learned - 2009 IT DemoFormal IT Demonstration (cont)
FY10 IT Demonstration Demonstration Plan • Purpose: Provide a single point of reference for all aspects of the demo • Owner: 4-D Wx Data Cube Team • Input from: all players
FY10 IT DemonstrationNotional Test Outline • Test Case 1: WFSRI version 2.0 • Test Case 2: WCSRI version 2.0 • Test Case 3: SAS • Test Case 4: NEVS • Test Case 5: Service Adapters • Test Case 6: Performance & Latency • Test Case 7: Security • Test Case 8: Standards • Regression Test: • WFSRI version 1.0 • WCSRI version 1.0 • WellFleet Registry/Repository • Standards
FY10 IT DemonstrationProcedures Format Follow FAA AMS Guidelines for test document development Will incorporate the following: Test step w/ expected results Space for to indicate step completed (or Failed) Reference requirement being tested Sign-off sheet for each Test Case noting time/date of completion, section for comments, signatures for Q/A and Test Conductor
FY10 IT Demonstration Demo Test Procedures 1.0 Introduction: Includes Purpose and Scope 2.0 Reference Documents: 3.0 Test Description 3.1 System Under Test 3.2 Interface Under Test 3.3 Test Setup 3.4 Test Equipment 3.5 Personnel 3.6 Location Schedule
FY10 IT Demonstration Demo Test Procedures (cont) 4.0 Test Conduct 4.1 Safety Considerations 4.2 Requirements Under Test 4.3 Procedures 4.4 Test Data Reduction and Analysis Appendix A – Requirement Traceability Matrix (More information and description of each section can be found in Appendix C-6 at http://fasteditapp.faa.gov/ams/do_action?do_action=ListTOC&contentUID=20 )
FY10 IT Demonstration Program Trouble Report (PTR) • Form used to identify issues that are encountered during testing • Each failed test steps will result in a PTR • PTR from will consist of: • Time and Date of PTR • Test Case / Step / Page • Who generated PTR • Issue • Explanation • Resolution
FY10 IT Demonstration Simulator / Tools • iTKO Lisa Tool • http://www.itko.com/lisa • Progress Software Actional • http://web.progress.com/actional/ • ESRI ArcGIS • Unidata Integrated Data Viewer (IDV) • http://www.unidata.ucar.edu/software/idv/ • NextGen Evaluation Weather Tool (NEWT)
FY10 IT DemonstrationMilestones (requires dates) Draft 1 of Demonstration Procedures Draft 2 of Demonstration Procedures Software baselined / frozen Dry-Runs at NOAA Draft 3 of Demonstration Procedures Dry-Runs at FAA Finalized Demonstration Procedures Test Readiness Review Formal FY10 IT Demonstration (Full Test) Formal FY10 IT Demonstration (High-Level Test) FY10 IT Demonstration Quick Look Report FY10 IT Demonstration Report
Product Format & Publishing Discussion • Formats • Some formats have been developed; others are under development • Goal is to plan, through end of FY11, for developing formats beyond those already completed or planned—including which organization is responsible for which product formats, and when they will be completed • Publishing • Goal is to decide—for the FY10 Demo—which products will be published and by whom
Decoder Discussion Wednesday, November 18 • Scope of Decoder Discussion • What Decoder-Related Problems Should Be Anticipated? • Based on experience • Based on foresight • What Standards Apply (OFCM, WMO, …)? • Differing standards versions • Dealing with overlapping standards • Legacy Systems Transition • Decoder Metadata & Need for Consistency • Example: Site Identification Inconsistency • Rules (what is allowed, not allowed?) • Example: METAR remarks field • Example: Concatenated messages
Decoder Discussion - continued Wednesday, November 18 • Local Tables • Other Decoder Challenges (Input from Group) • Governance • Definition and establishment of governance • Leveraging existing governance bodies • Authoritative (oversight) and technical (execution) layers needed • Need for ongoing interagency collaboration– a long-term activity • Next Steps • Very near term (e.g., FY10) and beyond FY10