Presentation is loading. Please wait.

Presentation is loading. Please wait.

Slide # 1 January 07, 2008 SW CTR TO9 Kickoff: Agenda / Meeting Objective Objective of Today’s Meeting Review Comments/Response to TO9 Proposal Describe.

Similar presentations


Presentation on theme: "Slide # 1 January 07, 2008 SW CTR TO9 Kickoff: Agenda / Meeting Objective Objective of Today’s Meeting Review Comments/Response to TO9 Proposal Describe."— Presentation transcript:

1 Slide # 1 January 07, 2008 SW CTR TO9 Kickoff: Agenda / Meeting Objective Objective of Today’s Meeting Review Comments/Response to TO9 Proposal Describe Task Order Finalize Milestone Dates Agenda Prop Comments/Response Summary10 min TO9 Deliverables20 min Schedule Adjustments15 min

2 Slide # 2 January 07, 2008 SW CTR TO9 Kickoff: NWS Proposal Comments RTS and NWS discussed the comments on 12/13/07: no award issues GFE Closure List is addressed via the GFE Test Procedures. –Raytheon will provide a matrix and indicate TO9 completions as was done with TO8 for D2D  (NWS) assumes that marked-up “in-process” versions of the SMM and SSDD that reflect the changes for the migrated applications will be available for government review. (correct)  Which “Smart Tool” will be the conversion example? (All 50 Smart Tools in baseline will be converted) Have now designed a viable Java to Python Bridge. Most smart tools will remain unchanged, a few may require some conversion, just the smart tools in the national baseline will be tested  Who will set the agenda for 4/30/08 TIM? (jointly set)  Test Plan and Procedures should identify and address the testing of any TO 8 DRs assigned to this TO. (agree) Milestone specific suggested acceptance criteria (See Figure 1 in PECP) This kick-off meeting with the NWS (pulled in from PECP date) The current date for the GFE TIM (2/19/08) (Set date in this meeting) Is 1 day between the TO9 Out-brief and the ADE Programmers Briefing realistic? (Yes, unless it presents problems for NWS. If so, we can adjust. We pulled in because of the “late delivery”) Current date for the delivery of TO9 software and out-brief follows a Federal Holiday (9/1/08). (We can move to 9/3/08 or 9/4.)  It is suggested that a Technical Interchange Meeting (TIM) with NCEP be add to discuss and support the NAWIPS migration activities. (Even though NAWIPS Migration is out of scope for TO9, Raytheon can accommodate a TIM with NCEP if no material preparation is required.)

3 Slide # 3 January 07, 2008 SW CTR TO9 Kickoff: NWS Proposal Comments  SW Delivery Date is later than NWS expected based on TO7 outbrief. 1.Do start and end dates overlap so that TO10 starts sooner? (yes) 2.Later delivery reduces test time available to NWS. (noted) Only 4 trips (items 6, 12, 16, and 17) identified in milestone table. Please identify the 5th trip. (Unscheduled “site” visit; site = HQ or Field)  During Delivery Testing, there are 2 people scheduled to conduct the test, 1 person for 1 week, the other for 2 weeks, please expound on the need for the second person for the additional week. (Risk reduction to ensure DT readiness) What is the naming convention for the delivery? (TO9 SWD p#) What are the Raytheon suggested acceptance criteria for the government milestones? From Table 4: –Item 4 has been addressed. (GFE Closure list) –Item 8: On-time and identifying missing tests that are critical to acceptance of the TO delivery. Submitted as a list of named tests and accompanied by a brief description. –Item 9: Standard UML use case that unambiguously defines the test case. –Item 14: On-time and identifying test procedure issues that are critical to acceptance of the TO delivery. Issues can be missing procedures or issues with included procedures. Submitted as a list of declarative statements such test procedure “xyz” should…(include specific data or test step).

4 Slide # 4 January 07, 2008 SW CTR TO9 Kickoff: Acceptance Figure 1, page 6

5 Slide # 5 January 07, 2008 SW CTR TO9 Kickoff: Task Order Summary Work ItemDescription/Activity Work Station Capabilities Implement the following:  GFE Perspective: GFE Menus, tool bar, GFE edit preferences, Legend Pop Ups, Status Bar, Intersite coordinate GUI. (ISC is GUI only, background processing depends on communication and is planned for T011. Climate data interfaces planned for T011 when CLIMATE is planned)  Spatial Editor: Animation (e.g. looping), Edit Areas, Pencil Tool, Sample Tool, Move/Copy Tool and Contour Tools.  Grid Manager: Primary Widget, Select Wx Element and Time range, Copy/Paste/Stretch/Compress, and Interpolate Grids Dialog. (Temporal Editor is in T010.)  Graphical Hazards: GHG Viewer, GHG Monitor, and first cut at VTEC interface.  Text Formatter Launcher + Data Interface.  Smart Tool Widgets + Interface (create a set of GUI widgets that are accessible from a Smart Tool script). GUI widgets not necessary since design approach is using Java to Python Bridge; however, extensive testing still required  AvnFPS for TAFs.  Redbook Vector Rendering. (Support only currently used SBN product formats)

6 Slide # 6 January 07, 2008 SW CTR TO9 Kickoff: Task Order Summary Work ItemDescription/Activity SOA Service Capabilities (EDEX) Implement the following:  GFE Plug-In and Server Messages for : grid management, grid lock management, reference data management, and control.  GFE access (not necessarily UtilitySrv Messages) for color tables, maps, topo, and VTEC. (reuse T08 common design approaches where practical)  Web Based Forecast Products Interface. (Will span TO9 - TO11)  Text Product Generation Interface including the data sampler and histogram. SOA Plug-ins Implement the following:  BUFR Decoder {Profiler, Model Soundings, Satellite Soundings, MOS.}  Red Book Vector Products Plug-In to support products viewable from D2D menus.  AFOS parser and formatter for TextWX (e.g. textdb) support.  LDAR Lighting plug-in with decoder.  Text Product Decoder for warnings. EDEX Common Library Implement the following:  Meteo Library Extension for access by uEngine Tasks.  Derived Parameters for grid and point data.  GFE Interpolation Functions for scalar, vector, and discrete(Wx) data types.  Smart Init Interface to enable initializing from model data and create the desired parameters.  Smart Tool Interface with a library of functions for use by smart tools.

7 Slide # 7 January 07, 2008 SW CTR TO9 Kickoff: Task Order Summary Work ItemDescription/Activity Data Management Implement the following:  GFE Data Model for scalar, vector, discrete(Wx), with interpolation.  Text QC and Business Rules. Advanced Development Prototype the following:  Hydro Visualizations.  Hydro Ingest: DPA Decoder. Test  Develop and document Test Plan, Test Procedure, and Test Report.  Update Regression Test Procedures.  Perform combined Delivery Test on Silver Spring or NWSHQ Test Bed.  Support User Functional Test as described in Sections 3.

8 Slide # 8 January 07, 2008 SW CTR TO9 Kickoff: Task Order Summary Work ItemDescription/Activity Documentation  Update JavaDoc.  Update Architecture Briefing.  Redline appropriate sections of the D2D and GFE user manuals, SMM, and SSDD for later incorporation into production documentation. Training  Update existing training materials for currency.  Provide a technical briefing for previous trainees, highlighting ADE changes (includes Example of Smart Tool Porting (Smart Tools/Init will have very limited changes). [Note: Developer training and training support are addressed in a separate Task Order.] Support  Provide DR support for UFE and IV&V as described in the description of the Support Work Item in this Section.  Conduct one face-to-face and two remote TIMs. Briefings  Provide delivery briefing (Architecture Updates, delivered end-user functions).  Provide Technical ADE update briefing package for previous ADE trainees.  Provide Risk Reduction Demonstration of Advanced Development items.

9 Slide # 9 January 07, 2008 SW CTR TO9 Kickoff: Schedule Milestones ItemDescriptionDate 1Start Technical Activity 01/04/08 done 2Task Order Award 01/11/08 done 3Kickoff With NWS 02/26/08 02/07/08 (today) 4 NWS delivery of GFE closure list (NWS milestone) 02/26/08 done (SyAT procedures) 5AELC Status Updatesmonthly 6GFE TIM * 02/19/08 03/05/08 7Draft Test Plan to NWS04/14/08 8 NWS comments delivered to Raytheon (NWS milestone ) 04/28/08 9 Use Cases to Raytheon for new tests (NWS milestone) 05/12/08 10Remote Customer TIM04/30/08 * Travel required for Raytheon Team

10 Slide # 10 January 07, 2008 SW CTR TO9 Kickoff: Schedule Milestones (Cont’d) ItemDescriptionDate 11TO10 Proposal05/30/08 12Face-to-Face Customer TIM; Location TBD * (CONUS) TBD (June) 13Draft Test Procedures to NWS6/27/08 14 NWS comments provided to Raytheon (NWS milestone) 7/11/08 15Remote Customer TIM TBD (mid-July) 16TO9 Software Delivery Test *08/08/ /15/08 17TO9 Software Delivery, Out Brief, and RRD * 09/02/08 (09/04/08) 18ADE Programmers Briefing (Remote) 09/03/08 (09/09/09) 19 All DRs screened, consolidated, and delivered to Raytheon (NWS milestone) TBD (9/30/08) 20DR Disposition Report TBD (# weeks  10/14/08) * Travel required for Raytheon Team


Download ppt "Slide # 1 January 07, 2008 SW CTR TO9 Kickoff: Agenda / Meeting Objective Objective of Today’s Meeting Review Comments/Response to TO9 Proposal Describe."

Similar presentations


Ads by Google