SWSI Development Meeting Notes

Meeting Date: February 27, 2001

Time: 9:30 AM

Place: GSFC, Building 12, Room E222

[Attendees:]{.underline} Steve Blackwell, Cathy Chang, John Gasch, Gerry
Klitsch, Jerry Rauser, Scott Robinson, Tom Sardella, Lydia Smirnova, and
Alan Zinkgraf

**[Action Items Responses:]{.underline}**

1.  Action Item #s 9, 37, 42, 43, 47, and 56 -- nothing reported

2.  Action Item #5 response -- Jerry noted to the group that Danh has
    made significant progress on his total rewrite to the SWSI System
    Requirements Document (SRD) Matrix (which reflects the newest
    version of the SRD). Tom noted that there is a meeting scheduled for
    this Thursday to review his comments to the SRD.

3.  Action Item #11 response -- (Investigate NCC activities for the
    proposed move and how this will effect SWSI development and testing
    in the future) -- Jerry reported that he has sent the new schedule
    (which includes the new Build schedule) to DSMC representatives for
    their incorporation to the DSMC Master Schedule.

4.  Action Items 18, 32, and 41 -- Scott reported that he plans on
    running some tests on Harshna's W/S this week, and also plans on
    setting up Secure CRT on Gerry W/S.

5.  Action Item #53 response -- \[Set up a demo of the Comprehensive
    Discrepancy System (CDS)\] -- Jerry questioned when the developers
    would like to have the demo on the CDS. Tom noted that he would like
    to discuss this further with Harshna.

6.  Action Item #54 response -- (Check what parameters have null as
    default values for SSC codes) -- Alan reported that he has been
    working on loading the parameters to the database. He has also
    changed NULL values in required parameters to a single space so that
    he could load those onto the database. Alan is to provide a list of
    parameters that have NULL values associated with them.

7.  Action Item #55 response -- (Provide an impact on Client, on how
    much work would be involved to detect only one (I or Q) channel is
    reported in MAR UPD stream and display blanks for the other channel)
    -- Gerry reported that he has provided some information on this
    subject to Harshna; but has not heard back from her. Gerry noted to
    the group that this will impact the Database, Client and Common
    Classes, and the Isolator. He noted that the Client and Common
    Classes may take a couple weeks of additional work; but he doesn't
    know how much time it would take on updates to the Database and
    Isolator.

**[Build 1 Status:]{.underline}**

Respecifiables -- John and Alan have implemented the Service_Param table
changes. Gerry is to test this.

Active Schedule Table -- Alan and John have updated scripts to populate
to the Active Schedule.

Updates

-   Schedule Delete Requests -- nothing reported

-   SAR -- interface with the Isolator

-   Alert Panel -- completed, Cathy is to insert some dummy code to demo
    the alerts

-   Active Schedule Panel -- draft

-   Service Display Panel -- draft, test data

-   Schedule Request Panel - draft

-   Clone SAR -- draft with Build 0, Steve noted that this needs to be
    revisited for Build 1.

-   Isolator -- Cathy putting in code for mnemonics request information
    and will retest.

Tom asked if tests could be run on Build 1 at this time. Gerry replied
that this may be possible in a couple weeks.

**[DAS CDR (RFAs):]{.underline}**

Tom noted that SWSI has been assigned some issues from the CDR, e.g.,
playback request (multiple period selection), Active Schedule (ability
to save displays to files, common separated values or CSV), and logging
UPDs at the Client W/S. Tom would like to see how the RFAs are worded
first before we start any actions. Tom suggested that a meeting be held
(Harshna, Gerry, and himself) to discuss what additional funding may be
required to implement this additional work.

**[Status Reports:]{.underline}**

Scott is to investigate JDK 1.3 **(see AI #57).**

John reported that things are stabilizing with the database. He did
note, however, that the playback issue may require some additional work.