Docstoc

SNAS Release Delivery Readiness the CLASS Server

Document Sample
SNAS Release Delivery Readiness the CLASS Server Powered By Docstoc
					                         SNAS Release 3 (10.1)

                       Delivery Readiness Review

                                     March 2, 2010




SNAS Release 3 DRR – March 2, 2010                   1
                                     Agenda

• Purpose:
     • Content of Release 3
     • Operational acceptance testing and results
     • Readiness to promote Release 10.1 candidate.5 to Release 3 Operations.

• Agenda
     • Release 3 Overview                               Dave Warren
     • Acceptance Testing                               Mike Miller
     • Acceptance Testing Open IDRs                     Mike Miller
     • 10.1 Delivery Plan                               Mike Miller
     • Customers Ready for Transition                   Ame Fox
     • Summary and Recommendation                       Mike Miller
     • Follow-on Activities                             Mike Miller


SNAS Release 3 DRR – March 2, 2010                                              2
                               Release 3 Overview        (1 of 3)


• Release 3 software resolves:

      – 12 Wishlist items: 8 general, 4 from JSC

      – 23 Discrepancy Reports (DR) from Operational Releases 1 and 2

      – 14 Interim DRs (IDR) uncovered during acceptance testing

      – 83 Bugs opened during development, system or user testing



      Note: Release 3 Content slides at end of presentation




SNAS Release 3 DRR – March 2, 2010                                      3
                               Release 3 Overview (2 of 3)
• Functionality Added
      – Streamlined MOC Client Menu
            • Reduced duplication on Main Control menu and submenu options, especially
              in generating reports and queries

      – Enhanced Recurrent Scheduling

      – Added DAS scheduling to Graphical Timeline
            • Added RAR, RAMR, and DASMAR objects and functionality similar to SAR,
              RR and USM

      – Localization of individual client.prop properties
            • Alternative way of pointing to local, user specified properties instead of
              central, system-wide client properties

      – Improved O&M Client control
            • Send messages to specific Users
            • Tracking mission changes through review history
            • Notifying Users when Mission changes submission fail

SNAS Release 3 DRR – March 2, 2010                                                         4
                               Release 3 Overview                  (3 of 3)


      – Enhanced EPS TCP/IP capability
            •   Message causes exception
            •   Fixed UPD configuration inhibiting displays in the GUI
            •   Client did not listen after disconnect/reconnect
            •   Handles SARs with zero keywords for SSCs

      – Upgraded COTS on system servers
            • Linux OS, Oracle driver, JDK and JRE, and Eclipse development tool
            • Clients will require JRE update to 1.6.0_15


• Documentation
      – MOC Client Users Guide updated to reflect changes
      – SNAS/EPS ICD reflecting new message changes




SNAS Release 3 DRR – March 2, 2010                                                 5
                                     Acceptance Testing
• Acceptance Test Plan
      – Sixteen test scripts developed by SNAS from their System Testing
      – Test cases were developed for specific Wishlist items, DRs and Bugs,
        and addressed functional regression testing
• Testers
      – WSC Tech Ops
      – HST and JSC personnel
      – Beta testers from SN community (FGST and Swift)
• Environment
      – ANCC
      – DAS HMD
• Results
      – For Candidate.4 baseline, 15 of 16 test cases were passed
            • Remaining High Availability test case to be performed on WSC OPS servers
              when servers return to redundant SN configuration

SNAS Release 3 DRR – March 2, 2010                                                       6
                      Acceptance Testing Open IDRs                       (1 of 2)


• Open IDRs will be converted to Release 3 (10.1) DRs
      – No significant impacts to Customer Operations
      – MOC/WSC workarounds documented (customer perspective)
      – Open IDRs turned into OPS DRs, and will be addressed in the next
        release
            • 27478      Directory Warning for TCP/IP Node
            • 27463      TCP/IP Node stopped receiving SRMs when sFTP node forward flag
                         set to false
            •   27460    Unexpected Decline of RR though SA time available in TUT
            •   27455    Events marked Completed prior to execution time
            •   27444    Bulk Modify time slip processes events incompletely
            •   27396    IP GUI doesn't show all IPs
            •   27356    Shift Change Does not always take effect




SNAS Release 3 DRR – March 2, 2010                                                    7
                     Acceptance Testing Open IDRs                          (2 of 2)


• 27478 Directory Warning for TCP/IP Node
           • Opened by JSC, an annoyance
• 27463 TCP/IP Node stopped receiving SRMs when sFTP node
        forward flag set to false
           • Opened by JSC, configuring both TCP/IP and SFTP nodes for the same
             messages causes duplicate messages, turning one off affects other (MOC
             operations has a workaround)
• 27460 Unexpected Decline of RR though SA time available in TUT
           • Opened by HST; for Release 3, adjusted TUT retrieval mechanism – watch
• 27455 Events marked Completed prior to execution time
           • Opened by HST, first time noticed – watch (workaround is to call NCC
             scheduler for event modifications if needed)
• 27444 Bulk Modify time slip processes events incompletely
           • Opened by HST; may be related when multiple connections for the same
             connection ID is enabled; contact SN OPS for assistance (see SN Alert notice)
• 27396 IP GUI doesn't show all IPs
           • Opened by WSC O&M, first time noticed – watch
• 27356 Shift Change Does not always take effect
           • Opened by JSC, first time noticed – watch

SNAS Release 3 DRR – March 2, 2010                                                       8
                                     10.1 Delivery Plan
• Go/No Go at DRR (March 2nd)                                        Marty Antholzner
      – Release NAM (no DAS availability, move to legacy,            Mike Miller
        customers will be supported by OPS schedulers)
• March 9 Delivery
      – Mike Miller – Delivery Lead
      – T-0 to T+6 hours
            • Perform cold database backups on OPS DB instance
                 – Shut-down and restart for single DBA user         Juan Gonzalez
                 – Run Purge scripts to remove dynamic data          Mike Goen
            • Run scripts to reformat Oracle DB files on OPS         Juan Gonzalez
              instance                                               Mike Shih
            • Perform cold backup of Ops database                    Juan Gonzalez
            • Activate Release 3 (10.1) OPS on EIF servers           Scott Robinson
            • Validate successful delivery switch                    Mike Miller /
                                                                       Manny Rios
            • “Back to operations” NAM (with Release 3 MOC Client)   Mike Miller
      – Delivery Complete, SNAS users back to operations using Release 3

SNAS Release 3 DRR – March 2, 2010                                                    9
                        Customers Ready for Transition
• MCEs and NOMs contacted each MOC using SNAS operationally by
  email and/or phone
                                               Status
     Misson                          User of   for Rel 3
•    ALOS                            NCC       unknown
•    CNOFS (Hanson, Kirkland)        NCC/DAS   unknown
•    EO-1                            NCC       testing
•    FGST                            NCC/DAS   Ready
•    GALEX                           NCC       unknown
•    ISS                             NCC       Ready* expecting a 3/8 transition
•    LDBP/ULDBP                      NCC/DAS   Will be Ready by next mission
•    SPTR-2                          NCC       Ready
•    Swift                           NCC/DAS   Ready
•    THEMIS                          NCC       Ready
•    TIMED                           NCC       unknown
•    WISE                            NCC       Ready


SNAS Release 3 DRR – March 2, 2010                                             10
                          Summary and Recommendation
• All testing was completed and successful
      – HA to be performed once OPS mode is up

• All IDRs addressed
      – Non-impacting to SN Customer operations
      – Workarounds documented – via Alert notice

• Back-out plans in place
      – Both system and database will be copied for back-out
      – Backups to be reapplied for back-out, if needed

• Final verification of customer readiness feedback

• Recommend Delivery – baseline SNAS 10.1 (candidate.5)

• “Back to Operations” NAM ready to be issued to SN Community
SNAS Release 3 DRR – March 2, 2010                              11
                                     Follow-on Activities
• Training of TOCC and MOC personnel available
      – via WSC personnel in the ANCC
      – via NOM phone/email support


• Upgrade of OPS mode servers to COTS versions
      – Return to server redundancy


• High Availability count verification

• Formal Delivery package – to be checked into WSC CM
      – Media and release letter shipped from GCP




SNAS Release 3 DRR – March 2, 2010                          12
 Backup Slides

Release 3 Contents
 Release 3 RTVM
                       Release 3 Content - Wishlist items
•    W/L 13             Combine NCC and DAS scheduling.
•    W/L 25             Provide tools to support log management
•    W/L 41             COTS upgrades (Linux 5.3, JRE 1.6.0_15, Eclipse, etc.)
•    W/L 42             Streamline MOC main menu
•    W/L 46             Allow O&M to select a user to send message to
•    W/L 47             Localization of client.prop file
•    W/L 53             Provide O&M review history
•    W/L 59             Add Event ID to Confirmed Events Reports
•    W/L 61-13          Pattern display drops, until configuration is saved.
•    W/L 61-14          Display doesn't index back to where user's last input
                        was made.
• W/L J/L11             It's preferable to provide the capability for user to select
                        colors of Alert panel text and background.
• W/L J/L16             The default start time of Active Events Summary
                        should be the current time

SNAS Release 3 DRR – March 2, 2010                                                14
                       Release 3 Content – Ops Discrepancies
                                                 (1 of 2)

•    52475      SNAS/Server - High Availability - failed counts not incrementing
•    56443      A large number of requests disappeared from the EIF database
•    56490      KASAR normal SSC GUI will not except values
•    56491      Continuous red alerts when DAS is disconnected
•    56493      O&M Client must warn user when manual SNIF restart is required
•    56494      SNIF sends SARs for unassigned SIC on another SIC's
                connection
•    56495      NumberFormatExceptions in SNIF log files
•    56499      TCP UPD Configuration inhibits display in GUI
•    56500      TCP/IP Message causes exception
•    56501      Intermittent display update issue on Active Events Summary
•    56524      SNIF transmitter thread queue overstock when connection is
                down
•    56526      SNAS O&M Client Cannot Delete Obsolete User Accounts


SNAS Release 3 DRR – March 2, 2010                                                 15
                      Release 3 Content – Ops Discrepancies
                                      (2 of 2)


• 56786 Lost Connectivity with DAS and SDIF On SNAS
• 56879 SNIF exception when Acq Failure Notification message
        received
• 57068 LDBP Unable to Schedule or GCMR DAS events via SNAS
• 57069 SWIFT SNAS Client Drops UPD Logging
• 57143 WISE Unable to Schedule events receiving constant alarms
• 57239 FGST not receiving data since DASCON reboot
• 57251 SNAS SSC Parameters incorrect read back
• 57293 TDRS 10 / SGLT 2 LDBP GCMR Processing
• 57303 TDRS 10 / SGLT 2 LDBP GCMR Processing
• 57311 TDRS-6 / SGLT-1 SSA2 and MAR LDBP were unable to send
        GCMRs
• 57318 TDRS 6 / SGLT 1 LDBP GCMR Processing

SNAS Release 3 DRR – March 2, 2010                            16
                      Release 3 Content – Interim DRs (AT)
•       SNAS delivery 3 isn't generating UPD selects on AT
     27382
•       Bulk Replace is losing TSW constraining
     27384
•       EPS file Type Entry fields complain even when not needed
     27385
•       TSW message on TCP/IP Interface alert message missing data
     27386
•       TSW transmission is intermittent
     27393
•       Reports include events outside of requested time frame
     27413
•       Modification of Schedule (RAMR) Using Graphic Timeline
     27419
•       USMs created from SNAS GUI not forward to TCP/IP clients
     27420
•       DAS Schedule Clone Feature Using Graphic Timeline
     27423
•       Error processing reconfig GCMR from TCP EPS
     27425
•       Schedule Request Summary Request Message doesn't
     27430
              conform to the ICD
• 27446 Make minimum duration default to specified duration
• 27462 Problems adding new DAS SSCs
• 27480 Resetting TSW flag on RR against Confirmed SARs
SNAS Release 3 DRR – March 2, 2010                             17
                                Release 3 Content – Bugs (1 of 3)
•   159    SNAS log files must not contain binary data
•   203    Unnecessary pull down options
•   207    OAM Client cannot approve/reject a request
•   369    Allow O&M to select a user to send message to
•   405    Recurrent scheduling generates SARs with incorrect times
•   407    Localization of client.prop file
•   417    Alias missing from Available SSC panel
•   419    Uncaught exception when user's certificate files not found
•   428    Incorrect Services displayed on Active Schedule Request Summary
•   469    Provide O&M review history
•   519    Add Event ID to Confirmed Events Reports
•   523    Duplicate active events have incorrect "Service Type Antenna" info
•   536    Various StreamCorruptionExceptions
•   544    MOC Client log file using local timezone on SAR data details
•   545    Return receipts being lost between SAM and MOC Client
•   606    Purge of UPD data failed on WSC EIF2 database
•   608    Various StreamCorruptionExceptions
•   610    SAM-Sve connections lost due to timeouts
•   641    Bulk import does not validate the reference Id against the SIC
•   649    intf check's on Orbital Parameter panel can't be modified
•   653    Schedule Request Summary Filters : upper/lower bounds fields need numeric validation
•   655    EnumExtStatusExpCode enum error
•   658    Need DB commit/ rollback capability when saving / deleting from RS
•   659    Active Events Summary Filters: Event ID Criteria upper/lower bounds fields need numeric validation
•   660    SAM is triggering a "Full" garbage collection every 11 seconds
•   661    MOC Client disconnect from SAM - digit count range invalid; Various StreamCorruptionExceptions
•   667    SAR Panel doesn't stop one of its threads when it closes
•   668    Duplicate calls to addWindowListener in SnasFrame subclasses should be removed
SNAS Release 3 DRR – March 2, 2010                                                                              18
                               Release 3 Content – Bugs (2 of 3)
•   669   String values should be compared using .equals, not ==
•   672   Need a Recurrent Scheduling Request Message for the EPS ICD
•   673   Cannot print fully detailed Active Events Summary
•   675   Active Event Summary panel is pulsing
•   676   Active Schedule please wait notification panel not always closed when data is received
•   677   AlertProcessor receipt timer should be cancelled on Logout
•   679   Define Orbital Constraints panel has multiple bugs (including many NullPointerException)
•   681   SRM files from EPS interface contain multiple SRMs
•   682   Cleanup code causes multiple MOC Client windows to get NullPointerException when user logs out
•   688   Not All EPS response messages using EPSTmpDir variable
•   689   Request auto refresh active schedule data from DAS at only a third of the NCC auto refresh rate
•   690   The bulkSar panel needs a relative time option
•   691   Need to be able to configure SvE for a single SAM
•   695   Need a Schedule Request Summary message for EPS
•   696   RS Edit superprototype panel - OPS locking up
•   697   SAM encounters "ArrayIndexOutOfBoundsException"s
•   699   TSW Transmit Occurs with Null Input
•   700   After MOC Client logout/login without exiting, hourly TUT stops
•   701   Exception when modifying RS pattern
•   702   Panels locked by under popping Critical popup panel
•   703   Rejected RR can't be corrected and resubmitted
•   704   USMs periodically disappear and reappear on Graphic Timeline
•   705   KASARIF panels store UI Channel ID I Channel wrong;
•   706   RS Pattern editor loses panel focus
•   708   Functionality discrepancy for MOC Controller position
•   709   Issues with User-Defined TDRS Constraint Setup
•   710   Deactivation of Save to Timeline Button for Graphical Timeline Replace Requests
•   712   EPS native USM file transfer duplicated
SNAS Release 3 DRR – March 2, 2010                                                                          19
                               Release 3 Content – Bugs (3 of 3)
•   713    MOC does not get notified of SSC changes for a DAS SSC
•   714    Specify the start time property to look for active events
•   715    Add checkbox to reverse the background of the Alert Summary display from blank to white
•   717    PurgeDatabase utility does not purge UPD_LOG
•   720    Title of ActiveEventsSummary printout should not read 'Active Schedule’
•   722    Add an OAM Delete User option
•   725    RS pattern names longer than 15 characters cause exceptions
•   726    Bulk Modify Uses Database Defaults for Replace Requests
•   729    NullPointerException for Erroneous Passphrase at Login
•   730    Objects sent to SAM after a MOC Client reconnect may be invalid due to "cleanup" code
•   732    ClassCastException in SNIF during startup
•   737    Incorrect msg class used for report responses generated by EPS
•   738    ConcurrentModificationException causes SNIF to stop working
•   739    Incorrect Active Events Summary Details Filtered Set Report
•   741    Toggling between Relative and Absolute time on RR Panel Changes Service Stop/Duration
•   742    SNIF doesn't set start/stop time correctly for some TSW Messages.
•   743    ConcurrentModificationException in ActiveScheduleRequestingThread of SDIF
•   747    MOC client freezes during Re-create USM actions
•   749    Older SNAS application log files should be compressed
•   751    Reports include events outside of requested time frame
•   754    Stray lock file for Active Schedule Upload causes MOC Client to freeze
•   757    Query Active Schedule Upload Not Working
•   759    Service Time Format Switch When Cloning a Replace Request in Graphical Scheduling
•   761    Replace Request transmitted with Invalid Minimum Duration
•   767    SAM's "Force Logoff" of MOC/OAM Client doesn't always work
•   768    Cannot add new DAS SSC--get NullPointerException
•   769    Protocol strings from DAS SSC Panel not interpreted properly


SNAS Release 3 DRR – March 2, 2010                                                                   20
                                                   Release 3 RTVM (1 of 4)
ID       Req ID                                                      Requirement                                                         Test Case
1     3.2.2.3   Range of values for each field.                                                                                         G2.1
2     3.3.1.2   SNAS Database Administrator (DBA), an SN O&M client user role, to control the SNAS system database.                     G2.1
3     3.3.1.3   Mission Manager, a SNAS MOC client user role, to control all of the SNAS functionality for that Customer (i.e., a       G1.2, G2.1
4     3.3.1.4   superuser).
                Mission Scheduler/Planner, a SNAS MOC client user role, to perform forecast and active period scheduling as well as the G1.2
                capability of accessing and reviewing orbital data.
5 3.3.1.5       Mission Controller, a SNAS MOC client user role, to support real-time monitor and control operations as well as the     G1.2
                capability of accessing and reviewing orbital data.
6 3.3.1.6       Mission Support, a SNAS MOC client user role, to support logging, delogging and reporting.                              G1.2
7 3.4.1.1       The SNAS shall comply with the 452 ICD SN/CSM.                                                                          G2.1
8 3.4.1.2.1     The SNAS shall provide an interface with the NCCDS to perform the following functions related to SN NCCDS services:     G2.1
                Service Scheduling
9 3.4.1.2.2     The SNAS shall provide an interface with the NCCDS to perform the following functions related to SN NCCDS services:     G2.1
                Service Planning
10 3.4.1.2.6    Receipt of NCCDS Alerts.                                                                                                G1.2, G1.11
11 3.4.2.1.1    Schedule Add Request (SAR), Message Type 99, Class 10,                                                                  G1.5, G2.2
12 3.4.2.1.3    Schedule Replace Request (RR), Message Type 99, Class 12,                                                               G1.5
13 3.4.2.17     The SNAS shall provide the capability to regenerate TSWs based on user-entered time interval parameters.                G1.3
14 3.4.2.17.1.a PSAT,                                                                                                                   G1.3
15 3.4.2.17.1.b UAV,                                                                                                                    G1.3
16 3.4.2.2      SNAS shall accept and process externally generated batch (bulk) schedule requests consisting of the message types       G1.10
                SNAS shall 3.4.2.1.
17 3.4.2.20.3 identified in save the most recent TUT to logged on MOC Clients hourly.                                                   G1.3
18 3.4.2.23.1 Notify the user the SRM has been received, and                                                                            G2.2
19 3.4.2.24.1 Notify the user the USM has been received, and                                                                            G2.2
20 3.4.2.3      The SNAS shall allow SARs to be created at any time without regard to any previous schedule request.                    G1.5


     SNAS Release 3 DRR – March 2, 2010                                                                                                          21
                                                      Release 3 RTVM (2 of 4)
ID       Req ID                                                             Requirement                                                               Test Case
21    3.5.1.2.7   Receipt of DAS Alerts.                                                                                                             G1.2, G1.11
22    3.5.3.3     The SNAS shall be capable of receiving one (1) UPD message every sixty (60) seconds for each active event.                         G1.11
23    3.5.5.1.1   Alert the user implied by the SIC specified in the DAS alert message, and                                                          G1.11
24    3.5.5.1.2   Make the text of the DAS alert message available for review by the user.                                                           G1.11
25    3.6.1.1     Latitude, longitude, altitude, and time for a spacecraft in Earth-Centered Fixed (ECEF) True of Date coordinate system             G1.3
                  referenced to World Geodetic System 1984 (WGS-84) reference ellipsoid, or
26 3.6.1.2        Cartesian position and velocity and time data for a spacecraft in ECEF True of Date coordinate system referenced to WGS- G1.3
                  84 reference ellipsoid.
27    3.6.2.1     Into a type 8 (stationary) Improved Interrange Vector (IIRV) for that spacecraft, or                                               G1.3
28    3.6.2.2     Into a type 1 (orbital) IIRV for that spacecraft.                                                                                  G1.3
29    3.6.3.1     Into a type 2 (Forced) IIRV for that spacecraft, or                                                                                G1.3
30    3.6.3.2     Into a type 4 (Maneuver Ignition) IIRV for that spacecraft, or                                                                     G1.3
31    3.6.3.3     Into a type 5 (Maneuver Cutoff) IIRV for that spacecraft, or                                                                       G1.3
32    3.6.3.4     Into a type 6 (Reentry) IIRV for that spacecraft, or                                                                               G1.3
33    3.6.3.5     Into a type 7 (Powered Flight) IIRV for that spacecraft.                                                                           G1.3
34    3.7.1.7     Records pertaining to successful SNAS login and logout,                                                                            G1.1
35    3.7.1.8     Records pertaining to failed SNAS login attempts, and                                                                              G1.1
36    3.7.2.1     For SNAS MOC clients,                                                                                                              G2.1
37    3.8.1.2     The SNAS MOC Client shall support an interface to a Customer supplied external processing system (EPS).                            G1.8, G1.9
38    3.8.1.2.4   The SNAS shall provide a mechanism for the MOC client user to communicate changes to the SN O&M personnel.                         G2.1
39    3.8.1.5     The O&M Client shall support the O&M roles defined in Section 3.3 and only those roles.                                            G2.1, G2.2
40    3.8.2.2     The user shall have the ability to perform the following for their individual user interface configuration settings: Display, edit G1.1
                  and save.
41 3.8.2.3.2      The SNAS MOC Client shall have the ability to set applicable thresholds in the configuration settings for Alerts.                  G1.2
42 3.8.3.3        The displays shall be able to depict information about NCCDS scheduled service(s) as well as DAS service(s).                       G1.3, G1.4,
                                                                                                                                                     G1.7

     SNAS Release 3 DRR – March 2, 2010                                                                                                                       22
                                                       Release 3 RTVM (3 of 4)
ID    Req ID                                                                 Requirement                                                             Test Case
44 3.8.3.6.1       Graphical timelines shall be able to depict Schedule requests.                                                                   G1.7
45 3.8.3.7         Timelines shall be configurable such that related information (e.g., SARs and TSWs) are shown together in a single               G1.7
                   display.
46    3.8.3.10.1   The user shall have the capability to print from each display.                                                                   G1.5
47    3.8.3.10.2   The user shall have the capability to print from the screen.                                                                     G1.5
48    3.8.3.12.2   SNAS shall provide dynamic updates as new NCCDS and DAS UPD messages are received.                                               G1.11
49    3.8.4.1.3    The SNAS shall provide a status on the communication links with DAS.                                                             G1.11
50    3.8.4.13     SNAS shall provide the capability of generating recurring schedules (RS) based on a combination of predefined patterns,          G1.4, G1.3
                   selected TDRSs, TSWs and TUT.
51 3.8.4.13.1      A pattern shall consist of a properly formatted list of one or more prototypes and/or superprototypes.                           G1.3
52 3.8.4.13.2      SNAS shall provide mechanisms for the user Recuurent Scheduling interactions.                                                    G1.3
53 3.8.4.13.3      If RS generation of SARs/ASARs is aborted, any SARs and/or ASARs that have been generated shall be saved in a file               G1.3
                   that can be submitted to the NCCDS.
54 3.8.4.2         Based on the user’s login information, the SNAS shall provide the user with the capability to select from a list of SICs, for    G1.1, G2.2
                   which the user is authorized, the SIC or any combination of the listed SICs, including all of the SICs in the list, to be used
55 3.8.4.3         The user shall be capable of selecting either operational or test mode during login.                                             G1.1
56 3.8.4.5         The SNAS shall provide a means to view alerts or messages when operational abnormalities are detected in SN                      G2.2
                   Scheduling Function resources.
57 3.8.4.7.1       The SNAS shall provide the user with displays of the following with updated status: Current active events.                       G1.4, G1.5
58 3.8.4.7.2       The SNAS shall provide the user with displays of the following with updated status: Previously transmitted schedule              G1.4, G1.5
                   requests.
59 3.8.4.8.2       SNAS shall provide the MOC Client with the capability of displaying SSCs.                                                        G2.1
60 3.8.4.8.7       SNAS shall provide the MOC Client with the capability of displaying TSW(s).                                                      G1.3
61 3.8.8.2.1       The following reports, in the structure and format as defined in 452-ICDSNAS/                                                    G1.6
                   EPS, shall be provided upon request for NCCDS services: Confirmed Schedule Report
62 3.8.8.2.2       The following reports, in the structure and format as defined in 452-ICDSNAS/                                                    G1.6
                   EPS, shall be provided upon request for NCCDS services: Confirmed Events Listing.
     SNAS Release 3 DRR – March 2, 2010                                                                                                                      23
                                                  Release 3 RTVM (4 of 4)
ID    Req ID                                                           Requirement                                                              Test Case
63 3.8.8.2.3   The following reports, in the structure and format as defined in 452-ICDSNAS/                                                   G1.6
               EPS, shall be provided upon request for NCCDS services: Rejected/Declined Events,.
64 3.8.8.2.4   The following reports, in the structure and format as defined in 452-ICDSNAS/                                                   G1.6
               EPS, shall be provided upon request for NCCDS services: Confirmed Events Report.
65 3.9.2       SNAS shall allow SN O&M personnel full/direct control to SNAS data via the SN O&M client software.                              G2.3

66 3.9.3.1.2   Data deletion,                                                                                                                  G2.3
67 3.9.6       SN O&M personnel shall be able to create and maintain all user data necessary to schedule, monitor and control SN               G2.1, G2.2
               services.
68 3.9.6.9     A record of all changes to user data shall be saved in the database log file for routine monitoring and audits.                 G2.2, G2.3

69 5.1.2       The SNAS servers shall be designed and configured such that routine system maintenance operations and routine system            G3.1
               administrative functions can be executed without rendering the capabilities of the servers operationally unavailable to the
70 7.2.2.3     The SNAS shall allow a new user to log in to a Client application replacing the user that is currently logged onto the SNAS     G1.3
               system.
71 7.2.2.3.1   This logon switch shall log in the new user without closing the connection or changing the state of the current user’s client   G1.3
               application.
72 7.2.2.3.2   Upon successful log in of the new user the switch login shall logout the previous user.                                         G1.3
73 7.2.2.3.3   All user initiated actions shall be prevented during the switch login process.                                                  G1.3
74 7.2.2.3.4   For SNAS user roles, SNAS shall not switch users unless the new user has the same SNAS Client role as the current user          G1.3
               or is a Mission Manager.
75 7.2.2.3.6   If the switch user is unsuccessful, the SNAS shall send out an alert and shall ensure that the original login remains active.   G1.3

76 7.2.2.4     The SNAS shall restrict the number of failed login attempts.                                                       G1.1
77 7.2.2.6     The SNAS shall provide for secure message exchange using encryption between the server and the MOC clients on both G1.1
               the Open IONet and the Closed IONet.
  SNAS Release 3 DRR – March 2, 2010                                                                                                                    24

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:0
posted:9/29/2012
language:Unknown
pages:24