SW CTR TO9 Kickoff: Agenda / Meeting Objective

1. 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 Summary 10 min • TO9 Deliverables 20 min • Schedule Adjustments 15 min

2. 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. SW CTR TO9 Kickoff: NWS Proposal Comments • SW Delivery Date is later than NWS expected based on TO7 outbrief. • Do start and end dates overlap so that TO10 starts sooner? (yes) • 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. SW CTR TO9 Kickoff: Acceptance Figure 1, page 6

5. SW CTR TO9 Kickoff: Task Order Summary

6. SW CTR TO9 Kickoff: Task Order Summary

7. SW CTR TO9 Kickoff: Task Order Summary

8. SW CTR TO9 Kickoff: Task Order Summary

9. SW CTR TO9 Kickoff: Schedule Milestones

10. SW CTR TO9 Kickoff: Schedule Milestones (Cont’d)