System Engineering Management Plan (SEMP) Template



Test Case SOA_PlugIns_2.0

for the

AWIPS

Contract

DG133W-05-CQ-1067

Prepared for:

U.S. Department of Commerce

NOAA/NWS Acquisition Management Division

SSMC2, Room 11220

1325 East-West Highway

Silver Spring, MD 20910

Prepared by:

Raytheon Company

STC Office

6825 Pine Street

Omaha, NE 68106

Submitted By:

___________________________________________________________ ___________

Test Engineer Date

Approved By:

___________________________________________________________ __________

Program Manager Date

___________________________________________________________ __________

Mission Assurance Quality Date

Revision History

|Revision |Date |Affected Pages |Explanation of Change |

|1.0 |27 Jun 08 |All |Initial Release (Note: Builds on the TO8 SOA Plugin test case.) |

Table of Contents

1.0 Scope 1

2.0 APPLICABLE DOCUMENTS 2

2.1 Source Documents 2

2.2 Reference Documents 2

3.0 Test Case description 3

3.1 Assumptions, Constraints and Preconditions 3

3.2 Recommended Hardware 3

3.3 Test Inputs 3

3.4 Test Outputs 3

4.0 TEst Scenario 4

5.0 TO8 requirements verification traceability matrix (RVTM) 17

6.0 TO9 requirements verification traceability matrix (RVTM) 20

Scope

See the TO9 Software Test Plan.

APPLICABLE DOCUMENTS

1. Source Documents

TO8 Test Case SOA_PlugIns 1.0.

FCM-S2-1994 (Redbook Graphics)

2. Reference Documents

TO9 Software Test Plan for the Advanced Weather Information Processing System Project, Contract #DG133W-05-CQ-1067, 14 April 2008.

Existing AWIPS 1 and AWIPS 2 test procedures.

The AWIPS D-2D User’s Manual Build 8.1.

The Silver Spring NWS AWIPS 1 test bed application.

Release OB8.1 and OB8.2 of the Weather Event Simulator (WES).

Rational RequisitePro.

Test Case description

This test case primarily demonstrates the capability of Service Oriented Architecture (SOA) plug-ins delivered during TO9. It builds on the TO8 test case and includes the test procedures from TO8. Plug-ins to be delivered and tested during TO9 include BUFR decoders for Profiler data, model soundings and satellite soundings.

The capability to ingest, store and display Red Book Vector Products will also be tested.

3. Assumptions, Constraints and Preconditions

• TO9 software has been installed successfully.

• AWIPS test driver installed and functional.

• CAVE, EDEX and pgAdmin III are running.

• An internet connection is available.

• Live data flow containing the data types to be tested. Canned data can be substituted if the live data flow does not contain the data required to test a specific plug-in.

• The correct display of the data infers that the functionality of decode, ingest and storage is working correctly.

• Data decode, ingest, and storage validation accomplished during the Preliminary Delivery Test (PDT); results available in the PDT report.

• Localization previously set.

• TO9 testing begins at step 72. Regression testing of steps 1-71 occurred prior to DT. Therefore, capability tested and delivered during TO8 (steps 1-71) remain intact and will not be executed during the TO9 DT.

• Actions, Results, and Requirements highlighted in yellow indicate requirements and/or capabilities to be included in the scope of future task orders. They are included here for purposes of continuity and traceability with the original AWIPS I test case documents.

4. Recommended Hardware

See TO9 Software Test Plan, Section 2.2.

5. Test Inputs

Section 4.0 below contains the test procedures for this test case. Sections 2.2 – 2.9 of the Software Test Plan contain general test inputs applicable to all TO9 test cases.

6. Test Outputs

The images and data will be displayed in CAVE for redbook products. The AWIPS test driver will be used to display the ingested plugin data.

TEst Scenario

|Step |Action |Result |Pass/Fail |

| |From the test workstation open CAVE. |CAVE successfully launches. The 5-D panel (4 smaller| |

| | |panels on the left and one larger main panel) | |

| | |displays. | |

| |Zoom so that a CONUS-sized area displays centered on approximately |The main panel displays an area centered on the | |

| |Kansas City. |CONUS that includes some of Mexico and Canada. | |

|DISPLAY LIGHTNING |

| |From the CAVE menu bar click Mouse Button (MB) 1 ‘Obs’ and then |A menu displays that contains the following 5 | |

| |‘Lightning’ (located under Hazards). |options: 1hr Lgtng Plot, 15min Lgtng Plot, 15min | |

| | |Pos/Neg Lgtng Plot, 5min Lgtng Plot, and 1min Lgtng | |

| | |Seq. | |

| |Select 1hr Lgtng Plot. |A lightning plot containing the previous 1 hour | |

| | |lightning strikes displays on the main panel. | |

| |Select ‘Clear’ from the menu bar. |The loaded lightning display is removed. | |

| |Select ‘15min Lgtng Plot’. |A lightning plot containing the previous 15 minutes | |

| | |of lightning strikes displays on the main panel. | |

| |Select ‘Clear’ from the menu bar. |The loaded lightning display is removed. | |

| |Select ‘15min Pos/Neg Lgtng Plot’. |A display of positive and negative strikes for the | |

| | |past 15 minutes displays. | |

| |Select ‘Clear’ from the menu bar. |The loaded lightning display is removed. | |

| |Select ‘5min Lgtng Plot’. |A lightning plot containing the previous 5 minutes | |

| | |of lightning strikes displays on the main panel. The| |

| | |DTG of the display should be within the past 5 | |

| | |minutes (depending on data receipt). | |

| |Select ‘Clear’ from the menu bar. |The loaded lightning display is removed. | |

| |Select ‘1min Lgtng Seq’. |Lightning strikes in one minute intervals for the | |

| | |past 5 minutes displays. The DTG for the display | |

| | |should be within the past 5 minutes (depending on | |

| | |data receipt). | |

| |Select ‘Clear’ from the menu bar. |The loaded lightning display is removed. | |

|DISPLAY SATELLITE |

| |From the Satellite menu use MB1 and select ‘IR Window’. |An IR image displays. IR satellite imagery can be | |

| | |displayed through the menu bar. | |

| |Select ‘Clear’ from the menu bar. |Satellite images are removed. | |

| |From the Satellite menu use MB1 and select ‘Visible’. |A visible image displays. Visible satellite imagery | |

| | |can be displayed through the menu bar. | |

| |Select ‘Clear’ from the menu bar. |Satellite images are removed. | |

| |From the Satellite menu use MB1 and select ‘Water Vapor’. |A water vapor image displays. Water vapor satellite | |

| | |imagery can be displayed through the menu bar. | |

| |Select ‘Clear’ from the menu bar. |Satellite images are removed. | |

|DISPLAY GRIB |

| |Open the Volume Browser by MB1 ‘Volume’, ‘Browser’. |The Volume Browser display GUI appears. | |

| |Display parameters from the latest ECMWF model run by selecting |Contoured 500mb level temperature and height fields | |

| |‘ECMWF-HiRes’ for the grid. For the Fields select temperature and |from the latest available ECMWF model run displays. | |

| |height. For Planes select ‘500mb’. Load the selections. Note: Other |ECMWF grib data can be displayed. | |

| |available parameters can be substituted. | | |

| |Select Clear from the menu bar. |Gridded display is removed from the main pane. | |

| |In the Volume Browser select ‘Edit’, ‘Clear All’. |Volume Browser entries are removed. | |

| |Display parameters from the latest NAM model run by selecting an |Contoured 700mb level omega fields (vertical | |

| |available NAM model for the grid. For the Fields select ‘Forcing’, |velocity) from the latest available NAM model run | |

| |‘Omega’. For Planes select ‘700mb’. Load the selection. Note: Other |displays. NAM grib data can be displayed. | |

| |available parameters can be substituted. | | |

| |Select Clear from the tool bar. |Gridded display is removed from the main pane. | |

| |In the Volume Browser select ‘Edit’, ‘Clear All’. |Volume Browser entries are removed. | |

| |Display parameters from the latest GFS model run by selecting ‘GFS40’ |Contoured fields of surface RH from the latest | |

| |for the grid. For the Fields select ‘Moist’ and ‘RH’. For Planes |available GFS-40 model run displays. GFS grib data | |

| |select ‘Surface’ (under Misc). Load the selection. Note: Other |can be displayed. | |

| |available parameters can be substituted. | | |

| | 1. Select ‘Clear’ from the menu bar. | 1. Gridded display is removed from the main | |

| |2. In the Volume Browser select ‘Edit’, ‘Clear All’. |pane. | |

| | |2. Volume Browser entries are removed. | |

| |Display parameters from the latest RUC model run by selecting an |Contoured 350mb temperature and height contours from| |

| |available RUC model for the grid. For the Fields select Temperature |the latest available RUC model display. RUC grib | |

| |and Height. For the Planes select ‘350mb’. Load the selection. |data can be displayed. | |

| | 1. Select ‘Clear’ from the menu bar. | 1. Gridded display is removed from the main | |

| |2. In the Volume Browser select ‘Edit’, ‘Clear All’. |pane. | |

| | |2. Volume Browser entries are removed. | |

| |Close the Volume Browser. Select ‘Volume’ from the menu bar. |A drop down menu labeled “Volume” appears. A listing| |

| | |of bundled (families) of grib model data displays. | |

| |From ‘Volume’ on the menu bar select ‘ECMWF’ located under Families. |A bundled set of ECMWF parameters displays. ECMWF | |

| | |grib data can be displayed from the Volume drop-down| |

| | |list. | |

| |Select ‘Clear’ from the menu bar. |Gridded display is removed from the main pane. | |

| |From ‘Volume’ select ‘NAM40’ located under Families. |A bundled set of NAM 40 parameters displays. NAM 40 | |

| | |grib data can be displayed from the Volume drop-down| |

| | |list. | |

| |Select ‘Clear’ from the menu bar. |Gridded display is removed from the main pane. | |

| |Select ‘GFS40’ located under Families. |A bundled set of GFS parameters displays. GFS grib | |

| | |data can be displayed from the Volume drop-down | |

| | |list. | |

| |Select ‘Clear’ from the menu bar. |Gridded display is removed from the main pane. | |

| |Select ‘RUC’ located under Families. |A bundled set of RUC-80 parameters displays. RUC | |

| | |grib data can be displayed from the Volume drop-down| |

| | |list. | |

| |Select ‘Clear’ from the menu bar. |Gridded display is removed from the main pane. | |

|DISPLAY RAOB |

| |Select ‘Upper Air’ from the menu bar. Under the RAOB section select |The latest RAOB for Omaha, NE, displays. A hodograph| |

| |Omaha, NE (KOAX). |and 24 hour temperature change graph also appear | |

| | |(the latter not active). Note: Derived parameters | |

| | |will not display. | |

| |Close the skew-T tab. Under ‘Upper Air’ select ‘UA Plots’, and |A plot display over the US for 700hPa from the |DR #823 |

| |‘700hPa’ located under RAOB. |latest RAOB data appears. | |

| |Clear the display. Select the ‘Points’ icon from the menu bar. |A pre-determined set of points appear, normally | |

| |Approximately center point A over Chicago, IL. |lettered beginning with A. Point A is moved and | |

| | |centered over Chicago. | |

| |Open the Volume Browser by MB1 ‘Volume’, ‘Browser’. |The Volume Browser display GUI appears. | |

| |Select ‘Sounding’ from the Volume Browser tool bar. |Volume Browser is set to sounding mode. | |

| |From the volume browser select the following: Grid-GFS40; Sounding |A sounding based on gridded data for Point A | |

| |(under Thermo); Points-A. Select ‘Load’. |displays. It contains a hodograph and 24-hr | |

| | |temperature change (both not active). Values for | |

| | |various parameters available in the data base also | |

| | |display. Finally, the asterisk in the map is | |

| | |centered over Chicago, where point A was moved. | |

|DISPLAY AIRCRAFT |

|Since the display of aircraft data has not been incorporated into CAVE, a test driver will be used to demonstrate the aircraft | |

|plug-in exists. | |

| |Close the Skew-T display. Bring up the test driver in a web browser by|Test driver displays. | |

| |going to: | | |

| | . | | |

| |Select ‘ASCII Data’. Open Request/Response Message. Edit the Request |The last 10 PIREP reports are returned. Aircraft | |

| |window entry to display the following script: |plug-in exists and is operational. | |

| | | | |

| |include(“PIREPRequest.js”); | | |

| |var dataRequest = new PIREPRequest(); | | |

| |dataRequest.setCount(10); | | |

| |dataRequest.enableAsciiResponse(); | | |

| |dataRequest.execute(); | | |

| | | | |

| |Select ‘Request Product’. | | |

| |Rerun the above step with data from the following script: |The last 10 AIREP reports are returned. Aircraft | |

| |Include(“AIREPrequest.js”); |plug-in exists and is operational. | |

| |var dataRequest = new AIREPRequest(); | | |

| |dataRequest.setCount(10); | | |

| |dataRequest.enableAsciiResponse(); | | |

| |dataRequest.execute(); | | |

|MDCRS plots will be delivered in TO 9. Therefore, the next two steps can not be executed. | |

| |Next, Under ‘Aircraft’ select ‘MDCRS plots’. |A display by flight levels in 5000 feet increments | |

| | |appears for available MDCRS plots. | |

| |Select ‘250-300 hft’. |A display of available MDCRS plots between FL 250 – | |

| | |300 appear. | |

|DISPLAY MARITIME |

| |Ensure a cleared, CONUS map is selected as the display area. From the |The latest observations from fixed buoys displays. | |

| |menu bar select ‘Obs’. Under the Maritime category select ‘Fixed | | |

| |Buoys’. | | |

| |Clear the display. Under ‘Obs’ select ‘Moving Maritime’. |The latest observations from ships and floating | |

| | |buoys displays. | |

| |Clear the display. Under ‘Obs’ select ‘MAROB’. |The latest MAROB data displays | |

|DISPLAY RADAR |

| |Clear the display. From the tool bar select ‘Radar’, ‘kdvn’, ‘kdvn 4 |A listing of available four panel radar displays | |

| |Bit Products’, ‘kdvn 4 bit four panel’. |appears. | |

| |Select the 0.5/1.5/2.4/3.4 Z/SRM panels. |A four panel radar display appears in the main | |

| | |panel. The displays are for 0.5, 1.5, 2.4, and 3.4 | |

| | |tilts. Note: not all panels may load if data is not | |

| | |available. Another station may be selected. | |

| |Close the 4-panel display. Select ‘kmpx’ under Radar. Select ‘kmpx 4 |A composite reflectivity radar image for Minneapolis| |

| |Bit Products’, ‘Comp Ref 4bit (CZ), |displays. | |

| |Clear the display and repeat above step for ‘Storm Total Precip’. |A display of storm total precip displays. | |

| |Note: STP may not be available, depending on the weather occurring at | | |

| |the site. | | |

| |Clear the display and select under Radar ‘kfsd’, ‘kfsd Derived’, ‘Echo|A display of the echo tops for Sioux Falls displays.| |

| |Tops (ET)’. | | |

| |Clear the display and under the koax localization select ‘koax 4 Bit |The latest radar image, 1.5 tilt, for koax | |

| |Products’, ‘koax 4bit Reflectivity’, ‘1.5 Refl’. |localization displays. | |

| |Repeat for ‘2.4 Refl’. |The latest radar image, 2.4 tilt, for koax | |

| | |localization displays. | |

| |Repeat for ‘3.4 Refl’. |The latest radar image, 3.4 tilt, for koax | |

| | |localization displays. | |

|DISPLAY TAF and TEXT |

| |From the menu bar select ‘Tools’, ‘Text Window’. |A text display window opens. | |

| |In the AFOS Cmd: enter ‘OMATAFOMA’. Return. |A terminal area forecast (TAF) for the selected | |

| | |station displays. AWIPS II contains a TAF plug-in | |

| | |that allows for the storage and retrieval of TAF | |

| | |data. | |

| |Clear the display. In the text window, AFOS Cmd: enter ‘OMAAFDOMA’. |A text bulletin displays. Text products can be | |

| |Return. |displayed; a text plug-in exists. | |

|DISPLAY METAR |

| |Clear the display. In the AFOS Cmd: enter ‘OMAMTROMA’. |A series of raw metar observations for Nebraska | |

| | |displays. Raw METAR observations can be retrieved | |

| | |and displayed. | |

| |Close the text window. Ensure a “clear” map centered on the CONUS is |A drop down menu bar displays providing a list of | |

| |displayed in the main panel. Select ‘Obs’ from the CAVE menu bar. |observation types that can be displayed. | |

| |Select ‘Surface Plot’. |The latest available decoded and ingested | |

| | |observations are displayed over the CONUS. | |

| |Clear the display. Under ‘Obs’, select ‘Other Plots’, ‘Surface |The latest available surface plots from synoptic | |

| |Synoptic Plots’. Note: Loop and/or zoom as necessary. |formatted observations displays. CAVE contains a | |

| | |synoptic plug-in. | |

| |Open a pgAdmin III session. Select the int1 DB. Under metadata open |A listing of the database tables displays. | |

| |‘Schemas’, ‘awips’, ‘Tables’. | | |

| |Using MB3 click on ‘obs’. |The DB Property and associated Value for obs | |

| | |displays. | |

| |Perform a SQL query by selecting the ‘View the data in the selected |A display of the metadata stored in the observation | |

| |object.’ Icon located in the menu bar containing icons. |database displays. | |

| |Examine the column headers. Look for the following headers: |These are all examples of columns that contain | |

| |autostationtype, sealevelpress, mintemp24hr, maxtemp24hr, precip1hour,|values found in the remarks section of METAR | |

| |precip6hour, and presschange3hour. |observations. | |

| |Scroll down through the columns. When remarks are reported, values |METAR remarks are decoded and stored in the AWIPS | |

| |will be found in these columns. Open the observation in the “message” |database. | |

| |column to confirm the value is found in the remarks section, RMK. | | |

|End of TO8 Test |

|Begin TO9 Test |

|DISPLAY PROFILER DATA DECODED FROM BUFR |

| |To determine if profiler data is being ingested and stored open |A listing of ingested profiler data appears. | |

| |pgAdmin. Run the following SQL query: | | |

| |select * from prodata; | | |

| |Select and annotate two stations from the stationed character column. |Profiler station id selected. | |

| |Selected Station ids: __________________ | | |

| |Open the AWIPS test driver. This will be used to query the database |The AWIPS Test Driver Interface Connected to | |

| |and view the selected two profiler data. |AWIPS-int1 opens. | |

| | | | |

| |Open the Request/Response Message and enter the following query (first|A Request/Response message is entered. | |

| |delete the request in the “Request:” window). Replace the XXXXX with | | |

| |one of the two station numbers selected above. | | |

| | | | |

| |include("ProfilerRequest.js"); | | |

| |var dataRequest = new ProfilerRequest(); | | |

| |dataRequest.setCount(1); | | |

| |dataRequest.addParameter("stationId","XXXXX"); | | |

| |dataRequest.enableAsciiResponse(); | | |

| |dataRequest.execute(); | | |

| |Select “Request Product”. |Data for the profiler station entered for the | |

| | |stationed displays. It will be the oldest data (or | |

| | |the first entry in the DB). Profiler data is being | |

| | |decoded and ingested into the AWIPS II database. | |

| |Repeat steps 75 and 76 for the second point selected. |Data for the profiler station entered for the | |

| | |stationed displays. It will be the oldest data (or | |

| | |the first entry in the DB). Profiler data is being | |

| | |decoded and ingested into the AWIPS II database. | |

|DISPLAY MODEL SOUNDING DATA DECODED FROM BUFR |

| |To determine if model sounding data are being ingested and stored open|A listing of all model sounding data that has been | |

| |pgAdmin run the following SQL query: |ingested appears. | |

| |select * from modelsounding; | | |

| |Scroll down. Under “GFS” reporttype select and record two sets of |Two data points are chosen from the GFS model that | |

| |latitudes and longitudes. |will be used to retrieve data. | |

| |Selected Lat/Longs: __________________ | | |

| |If not already displayed, open the AWIPS test driver. This will be |The AWIPS Test Driver Interface Connected to | |

| |used to query the database and view the selected two profiler data. |AWIPS-int1 opens. | |

| | | | |

| |Open the Request/Response Message and enter the following query (first|A Request/Response message is entered. | |

| |delete the request in the “Request:” window). Replace the XX.XX and | | |

| |YYY.YY with one of the two data points selected above. | | |

| | | | |

| |include("ModelSoundingRequest.js"); | | |

| |var dataRequest = new ModelSoundingRequest(); | | |

| |dataRequest.setCount(1); | | |

| |dataRequest.addParameter("reportType","GFS"); | | |

| |dataRequest.addParameter ("latitude","XX.XX"); | | |

| |dataRequest.addParameter ("longitude","-YYY.YY"); | | |

| |dataRequest.enableAsciiResponse(); | | |

| |dataRequest.execute(); | | |

| |Select “Request Product”. |GFS data for the entered datapoint displays. It will| |

| | |be the oldest data (or the first entry in the DB). | |

| | |GFS model sounding data are being decoded and | |

| | |ingested into the AWIPS II database. | |

| |Repeat steps 81 and 82 for the second point selected. |GFS data for the entered datapoint displays. It will| |

| | |be the oldest data (or the first entry in the DB). | |

| | |GFS model sounding data are being decoded and | |

| | |ingested into the AWIPS II database. | |

| |The next several steps repeat the above model sounding test steps but |A listing of all model sounding data that has been | |

| |use the ETA model. To determine if model sounding data for the ETA |ingested appears. | |

| |model are being ingested and stored open pgAdmin, run the following | | |

| |SQL query: | | |

| |select * from modelsounding; | | |

| |Scroll down. Under “ETA” reporttype select and record two sets of |Two data points are chosen from the ETA model that | |

| |latitudes and longitudes. |will be used to retrieve data. | |

| |Selected Lat/Longs: __________________ | | |

| |In the test browser, open the Request/Response Message and enter the |A Request/Response message for ETA data is entered. | |

| |following query (first delete the request in the “Request:” window). | | |

| |Replace the XX.XX and YYY.YY with one of the two data points selected | | |

| |above. | | |

| | | | |

| |include("ModelSoundingRequest.js"); | | |

| |var dataRequest = new ModelSoundingRequest(); | | |

| |dataRequest.setCount(1); | | |

| |dataRequest.addParameter("reportType","ETA"); | | |

| |dataRequest.addParameter ("latitude","XX.XX"); | | |

| |dataRequest.addParameter ("longitude","-YYY.YY"); | | |

| |dataRequest.enableAsciiResponse(); | | |

| |dataRequest.execute(); | | |

| |Select “Request Product”. |ETA data for the entered datapoint displays. It will| |

| | |be the oldest data (or the first entry in the DB). | |

| | |ETA model sounding data are being decoded and | |

| | |ingested into the AWIPS II database. | |

| |Repeat steps 86 and 87 for the second point selected. |ETA data for the entered datapoint displays. It will| |

| | |be the oldest data (or the first entry in the DB). | |

| | |ETA model sounding data are being decoded and | |

| | |ingested into the AWIPS II database. | |

|DISPLAY SATELLITE SOUNDING DATA (GOES and POES) DECODED FROM BUFR |

| |To determine if satellite sounding data from GOES satellites are being|A listing of all satellite sounding data from GOES | |

| |ingested and stored open pgAdmin, run the following SQL query: |satellites that has been ingested appears. | |

| |select * from goessounding; | | |

| |Scroll down. Select and record two sets of latitudes and longitudes. |Two data points are chosen from the GOES satellite | |

| |Selected Lat/Longs: __________________ |soundings that will be used to retrieve data. Note | |

| | |the wmoheader column and that GOES file headers fall| |

| | |under the JUTX* WMO header. | |

| |If not already displayed, open the AWIPS test driver. This will be |The AWIPS Test Driver Interface Connected to | |

| |used to query the database and view the satellite sounding data. |AWIPS-int1 opens. | |

| | | | |

| |Open the Request/Response Message and enter the following query (first|A Request/Response message for GOES Satellite data | |

| |delete the request in the “Request:” window). Replace the XX.XX and |is entered. | |

| |YYY.YY with one of the two data points selected above. | | |

| | | | |

| |include("GOESSoundingRequest.js"); | | |

| |var dataRequest = new GOESSoundingRequest(); | | |

| |dataRequest.setCount(1); | | |

| |dataRequest.addParameter ("latitude","XX.XX"); | | |

| |dataRequest.addParameter ("longitude","-YYY.YY"); | | |

| |dataRequest.enableAsciiResponse(); | | |

| |dataRequest.execute(); | | |

| |Select “Request Product”. |GOES Satellite sounding data for the entered | |

| | |datapoint displays. It will be the oldest data (or | |

| | |the first entry in the DB). GOES Satellite sounding | |

| | |data are being decoded and ingested into the AWIPS | |

| | |II database. | |

| |Repeat steps 92 and 93 for the second point selected. |GOES Satellite sounding data for the entered | |

| | |datapoint displays. It will be the oldest data (or | |

| | |the first entry in the DB). GOES Satellite sounding | |

| | |data are being decoded and ingested into the AWIPS | |

| | |II database. | |

| |To determine if satellite sounding data from POES satellites are being|A listing of all satellite sounding data from POES | |

| |ingested and stored open pgAdmin, run the following SQL query: |satellites that has been ingested appears. | |

| |select * from poessounding; | | |

| |Scroll down. Select and record two sets of latitudes and longitudes. |Two data points are chosen from the POES satellite | |

| |Selected Lat/Longs: __________________ |soundings that will be used to retrieve data. Note | |

| | |the wmoheader column and that POES file headers fall| |

| | |under the IUTX* WMO header. | |

| |If not already displayed, open the AWIPS test driver. This will be |The AWIPS Test Driver Interface Connected to | |

| |used to query the database and view the satellite sounding data. |AWIPS-int1 opens. | |

| | | | |

| |Open the Request/Response Message and enter the following query (first|A Request/Response message for POES Satellite data | |

| |delete the request in the “Request:” window). Replace the XX.XX and |is entered. | |

| |YYY.YY with one of the two data points selected above. | | |

| | | | |

| |include("POESSoundingRequest.js"); | | |

| |var dataRequest = new POESSoundingRequest(); | | |

| |dataRequest.setCount(1); | | |

| |dataRequest.addParameter ("latitude","XX.XX"); | | |

| |dataRequest.addParameter ("longitude","-YYY.YY"); | | |

| |dataRequest.enableAsciiResponse(); | | |

| |dataRequest.execute(); | | |

| |Select “Request Product”. |POES Satellite sounding data for the entered | |

| | |datapoint displays. It will be the oldest data (or | |

| | |the first entry in the DB). POES Satellite sounding | |

| | |data are being decoded and ingested into the AWIPS | |

| | |II database. | |

| |Repeat steps 98 and 99 for the second point selected. |POES Satellite sounding data for the entered | |

| | |datapoint displays. It will be the oldest data (or | |

| | |the first entry in the DB). POES Satellite sounding | |

| | |data are being decoded and ingested into the AWIPS | |

| | |II database. | |

|DISPLAY MODEL OUTPUT STATISTICS (MOS) DECODED FROM BUFR |

| |To determine if profiler data is being ingested and stored open |A listing of ingested mos data appears. | |

| |pgAdmin. Run the following SQL query: | | |

| |select * from mosdata; | | |

| |Select and annotate two stations from the stationid character column. |MOS station id selected. | |

| |Selected Station ids: __________________ | | |

| |Open the AWIPS test driver. This will be used to query the database |The AWIPS Test Driver Interface Connected to | |

| |and view the selected two profiler data. |AWIPS-int1 opens. | |

| | | | |

| |Open the Request/Response Message and enter the following query (first|A Request/Response message is entered. | |

| |delete the request in the “Request:” window). Replace the XXXXX with | | |

| |one of the two station numbers selected above. | | |

| | | | |

| |include("BUFRMOSRequest.js"); | | |

| |var dataRequest = new BUFRMOSRequest(); | | |

| |dataRequest.setCount(1); | | |

| |dataRequest.addParameter("stationId","XXXXX"); | | |

| |dataRequest.enableAsciiResponse(); | | |

| |dataRequest.execute(); | | |

| |Select “Request Product”. |Data for the MOS station entered for the stationed | |

| | |displays. It will be the oldest data (or the first | |

| | |entry in the DB). BUFR formatted MOS data are being | |

| | |decoded and ingested into the AWIPS II database. | |

| |Repeat steps 104 and 105 for the second point selected. |Data for the MOS station entered for the stationed | |

| | |displays. It will be the oldest data (or the first | |

| | |entry in the DB). BUFR formatted MOS data are being | |

| | |decoded and ingested into the AWIPS II database. | |

|RED BOOK PRODUCTS. THE NCEP/HYDRO DROPDOWN MENU IN CAVE CONTAINS SELECTIONS TO DISPLAY RED BOOK PRODUCTS. A RANDOM SAMPLING WILL BE TESTED. |

| |Open CAVE. Under the NCEP/HYDRO menu drop down select “SPC Convective |The Day 1 Convective Outlook displays. Compare to | |

| |Outlooks”, “Day 1 Convective Outlook”. |SPC, . Areal coverage should| |

| | |be approximately the same for both areas. | |

| |Repeat for the Day 3 Convective Outlook. |The Day 3 Convective Outlook displays. Compare to | |

| | |SPC, . Areal coverage should| |

| | |be approximately the same for both areas. | |

| |Still in CAVE, under the NCEP/HYDRO menu drop down select “Fire |The Day 2 Fire Weather Outlook displays. Compare to | |

| |Weather”, “Fire Wx Outlook – Day 2”. |SPC, , Fire Wx Forecasts. | |

| | |Areal coverage should be approximately the same for | |

| | |both areas. | |

| |Still in CAVE, under the NCEP/HYDRO menu drop down select “Precip & |The latest available radar contours of intensity | |

| |Stability”, “Radar Summary”. |displays. Compare to same display on AWIPS I. | |

| |Still in CAVE, under the NCEP/HYDRO menu drop down select “Temps and |The latest available surface geostrophic wind plot | |

| |Weather” located under NCO and then “Sfc Geo Wind Plot”. |displays. Compare to same display on AWIPS I. | |

| |Still in CAVE, under the NCEP/HYDRO menu drop down select “Threat |The Weekly Drought Monitor displays. Compare to same| |

| |Chart”, “Weekly Drought Monitor”. |display on AWIPS I. | |

|RISK REDUCTION. As a risk reduction for TO10, preliminary development work for hydrology will be demonstrated. A formal risk reduction demonstration|

|will be presented at a later time. |

| |To show that SHEF plug-in has been created and data are being stored, |pgAdmin III application opens. | |

| |Open pgAdmin III. | | |

| |Select “awips-db”, “hd_ob81oax”, “Schemas”, “public” and ‘Functions”. |The properties for the obs_pe table displays. In the| |

| |Under Functions select “obs_pe”. |SQL pane a listing of the SHEF tables being | |

| | |populated | |

| | |appears. | |

| |Record the names of at least three tables (e.g., height, temperature, |Table names are recorded. | |

| |lake) for use in the next step. | | |

| |In pgAdmin III under Databases select “awips-db”, “hd_ob81oax”, |A listing of the SHEF tables contained in the | |

| |“Schemas”, “public”, and “Tables”. |database appears. | |

| |Using the right mouse buttion highlight one of the tables recorded |A listing of the SHEF data for the table selected | |

| |above. Select “View Data” and “View All Roles”. |displays and is current. SHEF data is being stored. | |

| |Repeat the above two steps for the remaining two tables. |SHEF data is being stored. | |

|End of TO9 Test |

TO8 requirements verification traceability matrix (RVTM)

|Number |Description |Test Step(s) |

|CAVE_TO8_18.22 |CAVE shall display the Fixed Buoys plot product |49 |

|CAVE_TO8_18.23 |CAVE shall display the Moving Maritime plot product |50 |

|CAVE_TO8_18.24 |CAVE shall display the MAROB station plot product |51 |

|ADE_TO8_024 |AWIPS shall contain Plug-Ins that decode and store data and metadata |3-46 |

| | |49-72 |

|ADE_TO8_024.1 |AWIPS shall contain a bin Lightning Plug-in |3-13 |

|ADE_TO8_024.1.1 |The bin-Lightning Plug-in shall decode lightning metadata |3-13 |

|ADE_TO8_024.1.2 |The bin-Lightning Plug-in shall store lightning metadata in the metadata repository |3-13 |

|ADE_TO8_024.1.3 |CAVE shall display lightning data |3-13 |

|CAVE_TO8_016.1 |CAVE shall display 1 hour binary lightning plots |4 |

|CAVE_TO8_016.2 |CAVE shall display 15 minute binary lightning plots |6 |

|CAVE_TO8_016.3 |CAVE shall display 15 minute positive/negative binary lightning plots |8 |

|CAVE_TO8_016.4 |CAVE shall display 5 minute binary lightning plots |10 |

|CAVE_TO8_016.5 |CAVE shall display 1 minute binary lightning sequence |12 |

|ADE_TO8_024.2 |AWIPS shall contain a GINI Satellite Plug-in |14-19 |

|ADE_TO8_024.2.1 |The GINI Satellite Plug-in shall decode GINI Satellite metadata |14-19 |

|ADE_TO8_024.2.2 |The GINI Satellite Plug-in shall store GINI Satellite metadata in the metadata repository |14-19 |

|ADE_TO8_024.2.3 |CAVE shall display GINI Satellite data |14-19 |

|ADE_TO8_024.3 |AWIPS shall contain a Grib Plug-in |20-37 |

|ADE_TO8_024.3.1 |The Grib Plug-in shall decode Grib metadata |20-37 |

|ADE_TO8_024.3.2 |The Grib Plug-in shall store Grib metadata in the metadata repository |20-37 |

|ADE_TO8_024.3.3 |CAVE shall display decoded Grib data |20-37 |

|ADE_TO8_024.4 |The Grib Plug-in shall decode grib data necessary for the correct operation of the AWIPS II |20-37 |

| |system | |

|ADE_TO8_024.4.1 |The Grib Plug-in shall decode ECMWF data |20-37 |

|ADE_TO8_024.4.2 |The Grib Plug-in shall decode NAM data |20-37 |

|ADE_TO8_024.4.3 |The Grib Plug-in shall decode GFS data |20-37 |

|ADE_TO8_024.4.4 |The Grib Plug-in shall decode RUC data |20-37 |

|ADE_TO8_024.5 |AWIPS shall contain a RAOB (BUFR) Plug-in |38-43 |

|ADE_TO8_024.5.1 |The RAOB (BUFR) Plug-in shall decode RAOB metadata |38-43 |

|ADE_TO8_024.5.2 |The RAOB (BUFR) Plug-in shall store RAOB metadata in the metadata repository |38-43 |

|ADE_TO8_024.5.3 |CAVE shall display RAOB data |38-43 |

|ADE_TO8_024.6 |AWIPS shall contain a Text Plug-in |62 |

|ADE_TO8_024.6.1 |The Text Plug-in shall decode text data |62 |

|ADE_TO8_024.7 |AWIPS shall contain an Aircraft Plug-in |44-46 |

|ADE_TO8_024.7.1 |The Aircraft Plug-in shall decode Aircraft metadata |44-46 |

|ADE_TO8_024.7.1.1 |The Aircraft Plug-in shall decode AIREP Aircraft metadata |44-46 |

|ADE_TO8_024.7.1.2 |The Aircraft Plug-in shall decode RECCO Aircraft metadata |47-48 |

|ADE_TO8_024.7.1.3 |The Aircraft Plug-in shall decode PIREP Aircraft metadata |44-46 |

|ADE_TO8_024.7.2 |The Aircraft Plug-in shall store Aircraft metadata in the metadata repository |44-46 |

|ADE_TO8_024.7.2.1 |The Aircraft Plug-in shall store AIREP Aircraft metadata in the metadata repository |44-46 |

|ADE_TO8_024.7.2.2 |The Aircraft Plug-in shall store RECCO Aircraft metadata in the metadata repository |47-48 |

|ADE_TO8_024.7.2.3 |The Aircraft Plug-in shall store PIREP Aircraft metadata in the metadata repository |44-46 |

|ADE_TO8_024.7.3 |CAVE shall display Aircraft data |44-46 |

|ADE_TO8_024.7.3.1 |CAVE shall display AIREP Aircraft data |44-46 |

|ADE_TO8_024.7.3.2 |CAVE shall display RECCO Aircraft data |47-48 |

|ADE_TO8_024.7.3.3 |CAVE shall display PIREP Aircraft data |44-46 |

|ADE_TO8_024.8 |AWIPS shall contain a Synoptic Plug-in |66 |

|ADE_TO8_024.8.1 |The Synoptic Plug-in shall decode Synoptic metadata |66 |

|ADE_TO8_024.9 |AWIPS shall contain a Maritime Plug-in |49-51 |

|ADE_TO8_024.9.1 |The Maritime Plug-in shall decode Maritime metadata |49-51 |

|ADE_TO8_024.9.1.1 |The Maritime Plug-in shall decode ship synoptic Maritime metadata |49-51 |

|ADE_TO8_024.9.1.2 |The Maritime Plug-in shall decode buoy synoptic Maritime metadata |49-51 |

|ADE_TO8_024.9.1.3 |The Maritime Plug-in shall decode CMAN synoptic Maritime metadata |49-51 |

|ADE_TO8_024.9.1.4 |The Maritime Plug-in shall decode MAROB Maritime metadata |49-51 |

|ADE_TO8_024.9.2 |The Maritime Plug-in shall store Maritime metadata in the metadata repository |49-51 |

|ADE_TO8_024.9.2.1 |The Maritime Plug-in shall store ship synoptic Maritime metadata in the metadata repository |49-51 |

|ADE_TO8_024.9.2.2 |The Maritime Plug-in shall store buoy synoptic Maritime metadata in the metadata repository |49-51 |

|ADE_TO8_024.9.2.3 |The Maritime Plug-in shall store CMAN synoptic Maritime metadata in the metadata repository |49-51 |

|ADE_TO8_024.9.2.4 |The Maritime Plug-in shall store MAROB Maritime metadata in the metadata repository |49-51 |

|ADE_TO8_024.9.3 |CAVE shall display Maritime data |49-51 |

|ADE_TO8_024.9.3.1 |CAVE shall display ship synoptic Maritime data |49-51 |

|ADE_TO8_024.9.3.2 |CAVE shall display buoy synoptic Maritime data |49-51 |

|ADE_TO8_024.9.3.3 |CAVE shall display CMAN synoptic Maritime data |49-51 |

|ADE_TO8_024.9.3.4 |CAVE shall display MAROB Maritime data |49-51 |

|ADE_TO8_024.10 |AWIPS shall contain a Radar Plug-in |52-59 |

|ADE_TO8_024.10.1 |The Radar Plug-in shall decode Radar metadata |52-59 |

|ADE_TO8_024.10.2 |The Radar Plug-in shall store Radar metadata in the metadata repository |52-59 |

|ADE_TO8_024.10.3 |CAVE shall display Radar data |52-59 |

|ADE_TO8_024.11 |AWIPS shall contain a TAF Plug-in |60-61 |

|ADE_TO8_024.11.1 |The TAF Plug-in shall decode TAF metadata |60-61 |

|ADE_TO8_024.11.2 |The TAF Plug-in shall store TAF metadata in the metadata repository |60-61 |

|ADE_TO8_024.12 |AWIPS shall contain a METAR Plug-in |63-65, 67-71 |

|ADE_TO8_024.12.1 |The METAR Plug-in shall decode METAR metadata |63-65, 67-71 |

|ADE_TO8_024.12.2 |The METAR Plug-in shall store METAR metadata in the metadata repository |63-65, 67-71 |

|ADE_TO8_024.12.3 |CAVE shall display METAR data |63-65, 67-71 |

|AWIPS_T08_030.4 |The AWIPS system shall ingest METAR (WMO FM-15) observation data |63-65, 67-71 |

|AWIPS_T08_030.5 |The AWIPS system shall ingest SPECI (WMO FM-16) observation data |63-65, 67-71 |

|AWIPS_T08_030.6 |Refine the ADE 1.0 Metar plug-in by extending decoding into the remarks |63-65, 67-71 |

|AWIPS_T08_031.1 |AWIPS shall ingest binary lightning data |3-13 |

|AWIPS_T08_031.2 |AWIPS shall decode binary lightning data |3-13 |

|AWIPS_T08_031.3 |AWIPS shall store binary lightning data |3-13 |

TO9 requirements verification traceability matrix (RVTM)

|Number |Description |Test Step(s) |

|SYSR2074 |The AWIPS system shall implement Redbook Vector Rendering. |107-112 |

|SYSR2087 |The AWIPS system shall implement the BUFR Decoder for Profiler Data. |72-77 |

|SYSR2088 |The AWIPS system shall implement the BUFR Decoder for Model Soundings. |78-88 |

|SYSR2089 |The AWIPS system shall implement the BUFR Decoder for Satellite Soundings. |89-100 |

|SYSR2090 |The AWIPS system shall implement (ingest and storage) the Red Book Vector Products for |107-112 |

| |products viewable from D2D menus. | |

|SYSR2091 |The AWIPS system shall implement the ASOS parser for TextWS support. |N/A |

|SYSR2092 |The AWIPS system shall implement the ASOS formatter for TextWS support. |N/A |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download