Download - Swsi Bse Transitionrr1
-
7/29/2019 Swsi Bse Transitionrr1
1/19
SWSI Bulk Scheduling Transition Readiness Review 12/02/2004
SWSI Bulk SchedulingEnhancement (BSE)
Release 04.2
Transition Readiness Review
Merri Benjamin
David Warren
-
7/29/2019 Swsi Bse Transitionrr1
2/19
SWSI Bulk Scheduling Transition Readiness Review 12/02/20042
Agenda
Introduction/Background
BSE Requirements
Software Changes
Acceptance Testing
Customer Evaluation
SWSI Users Guide
Training Status Current SWSI Software Status
Delivery Plan
Summary-Checklist
Recommendation
Wrap up
-
7/29/2019 Swsi Bse Transitionrr1
3/19
SWSI Bulk Scheduling Transition Readiness Review 12/02/20043
Introduction/Background
The purpose of the meeting is the SWSI Bulk SchedulingEnhancement (BSE) Transition Readiness Review (TRR).
The objective of this TRR is to obtain SN Operations andCustomer agreement that the SWSI BSE can transition fromdevelopment to operations as SWSI Release 04.2.
RFA forms are provided and will be accepted until December 9.
With the current SWSI baseline, Release 04.1, SWSI customersmust submit their schedules or changes to their schedules,one at a time through their SWSI Client.
SWSI Release 04.2 contains the BSE which enablessubmission of multiple schedule requests [SARs, SDRs, andRRs] from files.
-
7/29/2019 Swsi Bse Transitionrr1
4/19
SWSI Bulk Scheduling Transition Readiness Review 12/02/20044
BSE Requirements
At the start of this software development task, severalmeetings were held to discuss the functional requirements
and desires of the SWSI for the BSE functionality. Bulkschedule input file formats were defined.
On July 7, 2004 a Requirements/Design Concept Review(R/DCR) was held.
10 RFAs were submitted and all dispositioned.
Action: Verify save function in submit path is identical to savefunction in save path Response: Data flow diagram was modified to better clarify save
function
Action: Confirm unknown fields in input file are indeed dontcares Response: A table was provided which listed the fields that are
ignored by the parser.
-
7/29/2019 Swsi Bse Transitionrr1
5/19
SWSI Bulk Scheduling Transition Readiness Review 12/02/20045
BSE Requirements (cont)
Action: Eliminate Filter For button if its functionality remainsstrictly associated with the save function.
Response: button was renamed to Filter and will serve as the real filterfor the requests in the window.
Action: Consider changing labels to Start Creation Time andStop Creation Time
Response: The labels remain as Minimum Creation Time and MaximumCreation Time to maintain uniformity of the SN systems (e.g. SPSR).
Action: Add name of parsed file to tabular display of validationresults.
Response: File name added to display
Action: Change the format of the date and time in the Start Timefield.
Response: Date and time fields are displayed as DOY/HH:MM:SS.
Action: Re-address the minimum requirement for Client,specifically, amount of RAM and hard disk required.
Response: BSE performance testing results indicate no changes toclient requirements are necessary as a result of the client modifications.
-
7/29/2019 Swsi Bse Transitionrr1
6/19
SWSI Bulk Scheduling Transition Readiness Review 12/02/20046
BSE Requirements (cont)
Action: Modify Tabular Display of Validation window to include thename of the parsed file and provide number of valid/invalid
requests. Response: Window was updated to include file name and provides
number of valid/invalid requests.
Action: Add additional filter criteria to filter functions.
Response: Additional filter criteria added (e.g., SIC, TDRS, Status).
Action: Monitor performance problems recently reported in thebaseline SWSI and characterize impacts to BSE and developworkarounds
Response: The SWSI development team aggressively investigated theperformance problems being reported in Operations and determined a
database purge script was not in the baseline. An automated purgescript was delivered and subsequently, no performance problems havebeen reported. Additionally, a system performance and loading test wasexecuted against the BSE delivery and no performance problems werenoted.
-
7/29/2019 Swsi Bse Transitionrr1
7/19
-
7/29/2019 Swsi Bse Transitionrr1
8/19SWSI Bulk Scheduling Transition Readiness Review 12/02/20048
BSE Requirements (cont)
Design derived functional requirements
Bulk Schedule File Input Characteristics
An input bulk schedule file shall be able to contain a mixture of SARs,SDRs, and RRs.
Each SAR, SDR, or RR embedded in the input file will be separated by anew line character.
Comments lines shall be able to be inserted by starting the line with thespecial delimiter %%%.
The input file shall be limited to 300Kbytes and shall be supplied by the
client. File Processing
Users shall be able to select the input bulk data file via a standard filechooser.
File validation shall be performed on the Client and validation resultsshall be available for user review and or saved for editing.
User shall have the option to submit to Server the SARs, SDR, or RR
which successfully passed Client validation or user shall have theoption to abort bulk schedule request.
Summary Filtering User shall be able to filter Schedule Request Summary window by
creation time.
User shall be able to save filtered Schedule Request Summary to a file.
-
7/29/2019 Swsi Bse Transitionrr1
9/19SWSI Bulk Scheduling Transition Readiness Review 12/02/20049
Software Changes
Application Server No modifications to Server applications or database schema
Baseline system PR 4045 fix is implemented with the BSE. This fixadjusts the data value of the display length of some serviceparameters from 4 to 3 and is needed to accommodate the validationchecks that are implemented in the BSE Client enhancement. The fixhas no impact to any user.
Client Displays New Bulk Schedule Requests option on menu under NCC Scheduling
New displays under NCC Select Bulk Schedule Request Data File pop-up
Summary of Bulk Schedule Request File window
Schedule Add Summary Request Detail for Entry # xx window
Schedule Delete Summary Request Detail for Entry # xx window
Replace Summary Request Detail for Entry # xx window
Service Detail window New Schedule Request Filter window for Schedule Request
Summary
New Active Schedule Filter window for Active Schedule Summary
Client Software Bulk [SAR / SDR / RR] file parsing and validation routines
Peer Code Walkthroughs were performed.
-
7/29/2019 Swsi Bse Transitionrr1
10/19SWSI Bulk Scheduling Transition Readiness Review 12/02/200410
Acceptance Testing
Since the system is hosted at WSC, client-side environment isdefined as desktop PCs (Windows and Unix) with internetaccess.
Client tested on platforms with
Windows 98, NT, 2000, XP
Solaris 7, 8
Linux (Red Hat 7.3)
The Open IONet client-side test environment for the systemlocated at GSFC, Building 13 and WSC.
The Closed IONet client-side test environment for the systemlocated only at WSC.
-
7/29/2019 Swsi Bse Transitionrr1
11/19SWSI Bulk Scheduling Transition Readiness Review 12/02/200411
Acceptance Testing (cont)
Acceptance Test Plan generated and contained two test suites BSE specific functionality and performance testing.
SWSI Regression Test (SWSI Regression Test 001)
BSE specific tests contained 4 groups of testing with severaltest cases within each group. Each test case designed toverify the high-level and derived functional requirements. AVerification Case Requirements Matrix (VCRM) is provided in
the Acceptance Test Plan. Group 1 Verify Client download and installation
Group 2 Verify new GUI screens and Bulk Schedule Submissionand Request ID extraction function.
Group 3 Verify validation functions for Bulk Schedule SARs,SDR, and SRR .
Group 4 Performance and Loading tests
All run for the record test cases were executed with Beta04.
All tests cases executed against Beta04 passed. A final TestReport was completed on 11/19/04.
-
7/29/2019 Swsi Bse Transitionrr1
12/19SWSI Bulk Scheduling Transition Readiness Review 12/02/200412
Customer Evaluation
Early versions (Beta02 and Beta03) provided to SWSIcustomers for evaluation.
Operations
Made suggestion to improve validation corrections by asking for anedit-on-the-fly capability
Suggested Deselect All button for filter screens
GP-B Scheduler and NOM
SWIFT NOM
SP&M
"Overall, the SWSI terminal has done an excellent job of verifying thecontent of our requests and has given very useful error messageswhich helped us fix our data. After adjusting the values to meet the
expected values, the message parsed successfully and has beentransmitted."
-
7/29/2019 Swsi Bse Transitionrr1
13/19SWSI Bulk Scheduling Transition Readiness Review 12/02/200413
SWSI Users Guide
The Users Guide was updated and reviewed, and used by theTest Team during Acceptance Testing.
DCN 002 to the Users Guide is complete and submitted to SNCCB for review and approval. CCB review is scheduled forDecember 7, 2004.
-
7/29/2019 Swsi Bse Transitionrr1
14/19SWSI Bulk Scheduling Transition Readiness Review 12/02/200414
Training Status
Some SN Operations staff provided initial Beta evaluationsand supported BSE Acceptance Testing.
Test Team will initiate training with appropriate OperationsSupport Personnel
Initial instructions and sample test files provided to interestedSWSI customers during testing phase. Test support andOperations support personnel will provide technicalassistance to all SWSI customers, as needed.
Updated SWSI Users Guide provides detailed instructionswith screen snaps of the operation of the BSE function. BSEscheduling is provided in Section 8.
-
7/29/2019 Swsi Bse Transitionrr1
15/19SWSI Bulk Scheduling Transition Readiness Review 12/02/200415
Current SWSI Software Status
All problems noted in earlier Beta versions were fixed andthere are no open BSE PRs against Beta04.
If accepted for transition to Operations, Beta04 will bedelivered as SWSI Release 04.2 and replace Release 04.1.
-
7/29/2019 Swsi Bse Transitionrr1
16/19SWSI Bulk Scheduling Transition Readiness Review 12/02/200416
Delivery Plan BSE Release Delivery
Highlights
Issue Network Advisory Message (NAM) Upon transition approval, the Release 04.2 client will be made
available for download from the website
Customers will upgrade client at own downtime but expect all usersto download and use new client by 1/31/05.
Zero SWSI server downtime but Operations will restartSNIF and Isolator to activate PR change
04.1 client is compatible for users not urgently needingBSE functionality
WSC OPS will provide support
No Failover testing necessary since no server changes
No back out of delivery has to happen as 04.1 and 04.2 SW can co-exist on client
Sustaining Engineering Status Quo
SWSI I&T environment will remain at GSFC.
SWSI falls under the purview of the SERB.
CDS used as the discrepancy management system.
Next release (05.1) to correct 04.1 PRs prioritized by SERB
-
7/29/2019 Swsi Bse Transitionrr1
17/19
-
7/29/2019 Swsi Bse Transitionrr1
18/19
SWSI Bulk Scheduling Transition Readiness Review 12/02/200418
Recommendation
We recommend that the
04.2 SWSI Bulk Scheduling Enhancements
be accepted and transitioned into SN Operations.
-
7/29/2019 Swsi Bse Transitionrr1
19/19
SWSI Bulk Scheduling Transition Readiness Review 12/02/200419
Wrap up
Review and assignment of Action Items RFA Form available on Documentation page at
http://swsi.gsfc.nasa.gov/
Submit RFAs to the TRR Chairperson only.
RFAs due by December 9th
Closing remarks