test readiness review nasa/gsfc code 452 june 6, 2008 space network access system (snas) test...

Test Readiness ReviewNASA/GSFC Code 452

June 6, 2008

Space Network Access System (SNAS) Space Network Access System (SNAS) Test Readiness ReviewTest Readiness Review

June 6, 2008

NASA Code 452

Space Network (SN) Project


June 6, 20082

TRR AgendaTRR Agenda

• Purpose of Review Rose Pajerski

• System Overview

• Requirements Overview Chii-der Luo

• Software Readiness

• Hardware Readiness Merri Benjamin

• Security Status Joe Clark

• Acceptance Test Readiness Merri Benjamin

• Transition and Training David Warren

• Wrap Up and Next Steps Rose Pajerski


June 6, 20083

Purpose of ReviewPurpose of Review

• The objectives of the review are to provide a comprehensive briefing to– Review SNAS requirements and testing activities to date– Present acceptance test plans and activities– Brief of the system, personnel and documentation readiness for acceptance testing– Demonstrate the system’s readiness to support acceptance testing at WSC

• Readiness criteria– All applicable functional, unit, subsystem testing, etc. has been successfully

completed.– Test objectives clear, system and environment configured and all test documentation

complete– All RFAs / issues from previous reviews have been satisfied according to plan.– All known significant system discrepancies have been identified and dispositioned– Interfaces under configuration management or as specified in test plan

– Testers identified, trained and ready

• Upon completion of the review, the SNAS team seeks approval to proceed with acceptance testing


June 6, 20084

Review BoardReview Board

• Lynn Myers, (chair), NASA Code 450

• Markland Benson, NASA Code 583

• David Campbell, NASA Code 584, HST

• Gregory Coombs, HTSI Mission Integration & Operations

• Bryan Batson, LM/JSC/MSOC Engineering


June 6, 2008

Project OverviewProject Overview

Rose Pajerski


June 6, 20086

OrganizationOrganization

NASA Contractor

SN Project ManagerCode 452

Keiji Tasaki

SN Project ManagerCode 452

Keiji Tasaki

SNAS Product Development Lead

Rose Pajerski

SNAS Product Development Lead

Rose Pajerski Resource/Business ManagerPaula Tidwell

Resource/Business ManagerPaula Tidwell

IT Security

Curtis Emerson

IT Security

Curtis Emerson

Implementation Contractor

NENS

Implementation Contractor

NENS

Systems Engineering Contractor

ITT

Systems Engineering Contractor

ITT

Product ManagementContractor

PAAC-II

Product ManagementContractor

PAAC-II

Code 451Network Integration Management Office

Scott Greatorex / NENS


June 6, 20087

Prior MilestonesPrior Milestones

• Project Milestones– System Requirements Review 7/08/03– NENS Task #20 SNAS PREP 4/04 - 10/04– NENS Task #60 SNAS start 3/04/05– Delta-System Requirements Design Review 4/28/05– Preliminary Design Review 9/12/05– Critical Design Review 5/04/06– Implementation 6/5/06 - 7/20/07– Integration/System Testing 8/07 - 05/08– Beta Testing 8/07 - 8/08– Server Shipment to WSC 5/06-12/08– System Installation and Checkout 5/14-30/08


June 6, 20088

Moving Forward ScheduleMoving Forward Schedule

Scheduled Completion

• Test Readiness Review today• Acceptance Testing 7/25/08• CIM #8 July• Beta Testing 8/15/08• Transition to WSC Operations July - September

– Training August– User’s Guide August– Server Operator’s Guide August

• ORR (date tba) ~ 8/28/08• Operational Availability (NCCDS) 9/02/08


June 6, 20089

Customer Community MilestonesCustomer Community Milestones

• Group Customer Interface Meetings– CIM #1, April 13, 2005 Pre-SRR

– CIM #2, June 14, 2005 Pre-PDR

– CIM #3, August 25, 2005 Post-PDR

– CIM #4, January 26, 2006 Pre-CDR

– CIM #5, November 11, 2006 Build 1 demo

– CIM #6, March 28, 2007 Build 2 demo

– CIM #7, July 26, 2007 Build 3/4 demo

• Beta Releases & Participants– 1st beta: 4/07 - 7/16/07 (Build 2 – NOMs, WSC)

– 2nd beta: 7/07 - 11/29/07 (Build 3/4 - NOMs, WSC, HST)

– 3rd beta: 11/07 - 3/03/08 (NOMs, WSC, HST, JSC, TRMM)

– 4th beta: 3/08 - 4/18/08 (NOMs, WSC, HST, JSC, TRMM, SP&M, SPTR)

– 5th beta: 4/08 - 5/30/08

– Release 0.1 06/04/08


June 6, 200810

Project DocumentationProject Documentation

• System Requirements Doc. (DCN 002) CCB approved (4/30/08)

• Operations Concept Doc. (DCN 002) CCB approved (11/15/06)

• ICD between DAS/SNAS CCB approved (5/03/06)

• ICD between EPS/SNAS CCB approved (11/15/06)

• ICD between SN/CSM (DCN 002) CCB approved (10/29/07)

• Security Documentation 452 Approved (10/29/07)

• System Test Document Final, 5/16/08

• Acceptance Test Plan Final, 6/04/08

• MOC & O&M Client Users Guides Review drafts

• Server Operators Guide Review draft


June 6, 2008

Requirements OverviewRequirements Overview

Chii-der Luo


June 6, 200812

RequirementsRequirements

• Current version: SRD DCN 002 (4/08)– 860 baseline requirements

– Security requirements for 2810.1A compliance added• Internet Security Service Officer and System Administrator Roles• System Logging changes• Auditing

– Updates: Clarification of State Vectors required by JSC; clarification of requirements on orbital data processing and recurrent scheduling

• SRD DCN 001 (4/06)– External interface requirements added

• User Planning System processes Recurrent Scheduling Orbital Data Processing External Processing Interface

• Report Transfers Additional Bulk File Type


June 6, 200813

Requirements Verification & Test CasesRequirements Verification & Test Cases

• Requirement verification disposition– Verification methods

• 689 Test (covered by 70 test cases)• 33 Demonstration• 4 Analysis (RMA)• 44 Inspection (including s/w standards – 6)• 28 Security • 62 Recommended for removal in DCN003

– Test case development process• Development team generated drafts during Development Testing• Reviewed by ITT• Updated based on comments• Reviewed by ITT and WSC• Finalized by WSC


June 6, 200814

Requirements Traceability Verification MatrixRequirements Traceability Verification Matrix

ID Req ID Requirement Method SAT Ver Case IDVerification

StatusRequirement

StatusApproval

StatusComments

1 3.1.1 The SNAS shall provide an interactive interface for planning, scheduling, and real-time monitoring and control of SN services.

Test SNAS-MOC-MSNSETUP-NCCSSC,SNAS-OM-MSNADMIN-NCCSSC,SNAS-OM-SYSMON-NCC

2 3.2.1.1 For all imported f iles, the message structure for each message type shall be validated as defined in 452-ICD-SN/CSM, ICD betw een the SN and Customers for Service Management.

Test SNAS-MOC-MSNSETUP-NCCSSC,SNAS-MOC-SCHED-TUT,SNAS-MOC-SCHEDNCC-SAR,SNAS-MOC-SCHEDNCC-RR,SNAS-MOC-SCHEDNCC-SDR,SNAS-MOC-SCHEDNCC-ASAR,SNAS-MOC-SCHEDNCC-WLR,SNAS-MOC-SCHEDTOOLS-REQUESTSNAS-OM-MSNADMIN-NCCSSC,SNAS-OM-SYSMON-NCC,SNAS-MOC-EPS-AUTONCC

3 3.2.1.2 For all imported f iles, the message structure for each message type shall be validated as defined in 452-ICD-SNAS/DAS, ICD betw een the SNAS and DAS, or

Test SNAS-MOC-SCHEDDAS-TVR,SNAS-MOC-SCHEDTOOLS-REQUEST,SNAS-MOC-EPS-AUTODAS

4 3.2.1.3 For all imported f iles, the message structure for each message type shall be validated as defined in 452-ICD-SNAS/EPS, Interface Control Document betw een the Space Netw ork Access System (SNAS) and the External Processing System (EPS).

Test SNAS-MOC-OVV-UAVPSAT,SNAS-MOC-OVV-TCWTSW

5 3.2.2.1 For all messages to be transmitted to the NCCDS or DAS, the Syntax shall be validated.

Test SNAS-MOC-MSNSETUP-NCCSSC,SNAS-MOC-SCHEDDAS-RAR,SNAS-MOC-SCHEDDAS-PBKS,SNAS-OM-MSNADMIN-NCCSSC

6 3.2.2.2 For all messages to be transmitted to the NCCDS or DAS, the Data type for each f ield shall be validated.


7 3.2.2.3 For all messages to be transmitted to the NCCDS or DAS, the Range of values for each f ield shall be validated.


8 3.2.2.4 For all messages to be transmitted to the NCCDS or DAS, it shall be validated that All required f ields have been entered.



June 6, 2008

Software ReadinessSoftware Readiness

Chii-der Luo


June 6, 200816

Servers and ComponentsServers and Components

• Open IONet Server– Services Access Manager (SAM) provides MOC & O&M Client

connection

• Closed IONet Server– Services Enabler (SvE) controls all message processing

• Client messaging to and from servers• Control and Monitoring of all internal connections• Data collector and transfer activator

Forwards NCC and DAS messages to the appropriate Clients

– SNAS-NCC Interface (SNIF) & SNAS-DAS Interface (SDIF)• Monitors DB for outgoing Client messages ready for transmission• Transmits all ICD formatted messages to NCC/DAS• Receives all NCC/DAS responses and alerts, and updates DB

– SAM for Client connections via Closed IONet

• Data Server– Oracle RDBMS

– Data Server Data Manager (DSDM) for heavy-duty DB interactions


June 6, 200817

Configuration ControlConfiguration Control

• Development Environment– Changes controlled using CM tool

• Concurrent Versioning System (CVS) setup on development server• Eclipse IDE environment established on developer workstations

connected to CVS• Code checked into CVS after successfully compiled/linked and unit

tested by developers • Version can be tagged at specific Build milestones

– Build scripts were developed and executed on development server to create new server processes and client executables

– Clients are copied to remote computers and tested


June 6, 200818

Development TestingDevelopment Testing

• Peer code reviews– Recorded issues in Jupiter plug-in to Eclipse development tool

– Use of freeware Findbugs in streamlining code reviews

• Unit testing– Used JTest and JProbe

• Integration & tests– Testing updated functionality

– Used to develop and validate test cases

– Exercised all subsystems using MOC and O&M Clients

• System tests– Used developed test cases

– Regression tests

– Recorded and tracked problems in Bugzilla

– Open discrepancies to be transferred to Comprehensive Discrepancy System (CDS) Internal Discrepancy Reports (IDR)r3eviews


June 6, 200819

Development EnvironmentDevelopment Environment

Proxy

Closed IONETOpen IONET

Secure Gateway

Client

Data / Closed Server

Router

Hub

Open Server

HMD DAS

ANCC

SNAS Boundary

SNAS-architecture-2008-0417


June 6, 200820

Beta TestingBeta Testing

• User Planning System (UPS) and Space Web Services Interface (SWSI) engineers applying operational experiences

• Beta testers– SWSI users: WSC NCCDS & DAS Ops, SWIFT/GLAST/AIM

NOMs, SP&M

– UPS users: HST, TRMM, JSC, SP&M

– ITT

• Major functionality tested– Request generation capability

– DAS / NCC File transfers

– EPS message transfers

– Orbital data processing

– Recurrent scheduling

• Four Beta versions since 8/07• Continue use of Bugzilla for problem reporting and tracking


June 6, 200821

Beta TestingBeta TestingUser CommunityUser Community

• GSFC Network Operations Managers– Gamma-ray Large Area Space Telescope (GLAST) – DAS/NCCDS

scheduling

– Astronomy of Ice in the Mesosphere (AIM) – NCCDS scheduling

– Wide-field Infrared Survey Explorer (WISE) – DAS/NCCDS scheduling

• Hubble Space Telescope (HST)– STScI (Baltimore) - Forecast period scheduling

– STOCC (GSFC) - Active period scheduling

• Johnson Space Center (JSC)– User Planning System (UPS) Engineering – Forecast/Active

scheduling and Recurrent scheduling

• Tropical Rain Monitoring Mission (TRMM)– Recurrent scheduling & orbital data processing

• White Sands Complex– Demand Access System (DAS) engineering

– Network Control Center Data System (NCCDS) engineering


June 6, 200822

Beta Testing Beta Testing ConfigurationConfiguration

• Remote Client communication to server access via– GSFC’s Central Network Environment (CNE)

– NASA’s Open IONet

• Connected to WSC’s ANCC and DAS HMD• Data populated from O&M

– Official mission data• TDRS IDs/Groups, SICs, SSCs, PEs (from ANCC)• Service and UPD definitions (from SWSI)

– O&M-approved data (from Mission Manager)• User accounts and roles, SSC changes, PE changes

• User generated (realistic Beta testing)– All mission defaults and characteristics, and EPS node data

– DAS schedule & playback requests

– NCC schedule requests

– Orbital and vector data via file imports


June 6, 200823

Beta (I&T) EnvironmentBeta (I&T) Environment


RAID

Secure Gateway

Client

Router

Client

Closed Server

Router

Hub

Open Server

HMD DAS

ANCC

SNAS Boundary SNAS Boundary

Switch

Data Server


June 6, 200824

Development/Beta Testing ResultsDevelopment/Beta Testing Results

• Discrepancy status: 81 I&T 373 Resolved

36 Beta (HST) 21 Wishlist/Enhancement

6 Beta (ITT) 5 Open Discrepancy

8 Beta (JSC) ======================

23 Beta (NOM) 399 Total

22 Beta (WSC)

223 System Testing

================

399 Total

• No open priority 1 or 2 discrepancies– 5 Open discrepancies of priority 3, 4 or 5


June 6, 200825

Continued Use of Beta SystemContinued Use of Beta System

• Beta version will be kept in step with AT version• Continued UPS user familiarization

– MOC Operation capabilities• NCCDS request processing• Bulk schedule request ingest• Orbital data processing• TSW transmission• Recurrent scheduling• Auto-forwarding• Report generation• Graphics timeline

– Comments and bug reports will be accepted

• Continued SWSI user familiarization– MOC Operational capabilities

• DAS and NCCDS request processing• Bulk schedule request ingest• UPD and GCMR processing• Vector transfer • TUT access and retrieval• Request summaries• O&M Client functionality

– Comments and bug reports will be accepted


June 6, 2008

Hardware ReadinessHardware Readiness

Merri Benjamin


June 6, 200827

Operational (AT) EnvironmentOperational (AT) Environment


RAID

Secure Gateway

Client

Router Router

Client

Closed Server Closed Server

Data Server

Router Router

Hub Hub

Open Server Open Server

NCCDAS

HMD DAS

ANCC

Heartbeat

SNAS Boundary

SNAS Boundary

Switch Switch

Data ServerHeartbeat

Heartbeat

Client

Internet


June 6, 200828

Operational String - StatusOperational String - Status

• Systems Configuration – SNAS Servers

• Installed under EC –TO60-1• Two racks in WSC CDCN (Open Servers and Closed Servers)• Connected to NISN Open and Closed IONet equipment racks in the

WSC GCE• Software and Database configured on system • Remote System Admin access from GSFC via IONet verified• End-to-end connections from Client to Servers to ANCC and DAS HMD

verified

– NISN IONet modifications• Bandwidth increased on Closed IONet routers to accommodate SNAS

data• Modifications to WSC Open IONet interface to accommodate SNAS

system and increased bandwidth allocations


June 6, 2008

Security OverviewSecurity Overview

Joe Clark


June 6, 200830

SNAS Security BoundarySNAS Security Boundary

Internet Closed IONETOpen IONET

RAID

Secure Gateway

Router Router


Data Server

Router Router

Hub Hub


NCCDAS

HMD DAS

ANCC

Heartbeat

SNAS Boundary

SNAS Boundary

Switch Switch


Heartbeat

SNAS-architecture-2008-0417

Client ClientClient

SNAS Accreditation Boundary

NISN


June 6, 200831

SNAS Security Categorization SNAS Security Categorization (1 of 2)(1 of 2)

• Guidance taken from– NIST 800-60

– NPR 2810.1A

– Discussions with representatives from Code 731 and Code 453

• SNAS has been determined to be a low impact system following FIPS 199 Guidelines because– the loss of confidentiality, integrity, or availability might:

• cause a significant degradation in mission capability to an extent and duration that the organization is able to perform its primary functions, but the effectiveness of the functions is noticeably reduced;

• result in minor damage to organizational assets; • result in minor financial loss; or • result in minor harm to individuals


June 6, 200832

SNAS Security Categorization SNAS Security Categorization (2 of 2)(2 of 2)

System/Application Name

Description Applicable Locations

InfoType Security Categorization

Space Network service scheduling web application for customers

This system provides scheduling, monitoring and control for TDRSS services to Customer platforms.

New Mexico D.22.4 Information Infrastructure Management Information LLL

Low

C3.5.4 Information and Technology ManagementLLL

Low

Confidentiality Integrity Availability

Overall High Water Mark Low Low Low

Questioner Template Responses

On scale of 0-10 what is the impact to NASA’s reputation if the information is compromised? 3

What are the effects of system failure to NASA? Upset customers, loss of scheduling data

What is the significance of failure for each of the identified effects on the system from question # 2 above?

Low, Low

What is the highest sensitivity level of the information processed, handled or stored in the information system?

SBU

What is the official (NASA System Owner) Criticality Designation for the information system? Not Officially Designated

In the opinion of the system and information owner (two answers) what is the restoration period of the information system in the case of a total catastrophe with respect to the agency?

Restore in 30 days

System & Data/Information Owners Comments: Based on the Space Network Web Services Interface (SWSI) system in use for 2 years without problems.

Crosschecked Security Categorization Low


June 6, 200833

SNAS Security Documentation StatusSNAS Security Documentation Status

• Risk Assessment Report– Approved 29 October 2007

• SNAS Security Plan– Approved 29 October 2007– Contingency Plan has been incorporated in the Security Plan

• Self-Assessment Checklist– Approved 29 October 2007

• SNAS will become a subsystem of WSC– The SNAS Security Plan will be incorporated into the WSC

Security Plan


June 6, 2008

Acceptance Test Readiness

Merri Benjamin


June 6, 200835

Test Environment – Test Environment – Systems Resources for ATSystems Resources for AT

• SNAS Servers – Operational String– Connections to ANCC and DAS HMD verified

• Connection to NCCDS and DAS Ops blocked

– Software Release 0.1 loaded– SNAS Database configured - populated with required pre-test

configurations (i.e., test SICs and SSCs)


RAID

Secure Gateway

Client

Router Router

Client


Data Server

Router Router

Hub Hub


NCCDAS

HMD DAS

ANCC

Heartbeat

SNAS Boundary

SNAS Boundary

Switch Switch


Heartbeat

Client

Internet


June 6, 200836

Test Environment – Test Environment – Systems Resources for ATSystems Resources for AT (con’t)(con’t)

– ANCC configuration – shared SN resource• Pre-test database configurations completed• No interactive UPD updates – not a concern for AT

– DAS HMD – shared SN resource• TO-83, DASE Task Order, activities concurrent with SNAS AT – not a

concern for test integrity – modifications to DAS HMD not related to DAS functionality

– Client Platforms – multiple platforms available to AT testers• MOC Client on test platforms• O&M Client on test platforms


June 6, 200837

Test PlanTest Plan

• AT Objectives– Verification of MOC Client functionality– Verification of O&M Client functionality– Verification of data flows between Client, Open Server system, and

Closed Server system– Verification of data flows between Closed Server system and ANCC

and DAS HMD– Verification of Data Server functions for data storage and retrieval

• ATP Completed - testing to requirements – RTVM in ATP– Functional Requirements

• User interface• Interactions with NCCDS• Interactions with DAS

– Operational Requirements• Operational procedures• Maintenance• Security


June 6, 200838

Test Plan Test Plan (con’t)(con’t)

• Test Cases - Five Test Groups– System Configuration for Mission and Users

• Logins, Mission Setups, etc.

– MOC Client Functionality• Orbital data processing, NCCDS and DAS scheduling, Real-time

monitoring, Reports and Queries, etc.

– O&M Client Functionality• System monitoring, customer configuration update requests, etc.

– Security tests

– System Performance tests


June 6, 200839

ATP Test Case Groups ATP Test Case Groups (1 of 6)(1 of 6)

• System Configuration for Mission and Users– User Configuration Test Group

• SNAS-MOC-USER-LOGIN• SNAS-MOC-USER-PREF• SNAS-MOC-VIEW-STAT• SNAS-MOC-VIEW-SYS• SNAS-MOC-USER-WORKSPACE

– Mission Configuration Test Group• SNAS-MOC-MSNSETUP-USERACCT• SNAS-MOC-MSNSETUP-SPCCHRS • SNAS-MOC-MSNSETUP-EPSCFG• SNAS-MOC-MSNSETUP-NCCSSC• SNAS-MOC-MSNSETUP-DSCHPARM• SNAS-MOC-MSNSETUP-PE• SNAS-MOC-MSNSETUP-EDITSUPER• SNAS-MOC-MSNSETUP-ORBITAL


June 6, 200840


• MOC Client Functions – Import Data Test Group

• SNAS-MOC-OVV-GEOC• SNAS-MOC-OVV-GEOD• SNAS-MOC-OVV-IMPVEC• SNAS-MOC-OVV-TCWTSW• SNAS-MOC-OVV-TRANSTSW• SNAS-MOC-OVV-UAVPSAT

– NCC Scheduling Test Group• SNAS-MOC-SCHED-TUT• SNAS-MOC-SCHEDNCC-SAR• SNAS-MOC-SCHEDNCC-SDR• SNAS-MOC-SCHEDNCC-RR• SNAS-MOC-SCHEDNCC-ASAR• SNAS-MOC-SCHEDNCC-WLR• SNAS-MOC-SCHED-IMPORT-NCC• SNAS-MOC-EPS-AUTONCC• SNAS-MOC-SCHEDNCC-RECURRENT


June 6, 200841


• MOC Client Functions (con’t)– DAS Scheduling Test Group

• SNAS-MOC-SCHEDDAS-TVR• SNAS-MOC-SCHEDDAS-RAR• SNAS-MOC-SCHEDDAS-RAMR• SNAS-MOC-SCHEDDAS-RADR• SNAS-MOC-SCHEDDAS-PBKS• SNAS-MOC-SCHEDDAS-PBKMR• SNAS-MOC-SCHEDDAS-PBKDR• SNAS-MOC-SCHED-IMPORT-DAS• SNAS-MOC-EPS-AUTODAS

– Scheduling Tool Test Case (NCC & DAS) • SNAS-MOC-SCHEDTOOLS-ACTIVE• SNAS-MOC-SCHEDTOOLS-BULKMOD• SNAS-MOC-SCHEDTOOLS-REQUEST• SNAS-MOC-SCHEDTOOLS-TIMELINE• SNAS-MOC-SCHEDTOOLS-TIMESHIFT• SNAS-MOC-SCHED-TSWSUM


June 6, 200842


• MOC Client Functions (con’t)– Real-time Monitoring Test Group (NCC & DAS)

• SNAS-MOC-CONTMON-REALTIME• SNAS-MOC-USER-SWITCHUSER

– Report and Query Test Group • SNAS-MOC-RPTS&QRYS-RPTS• SNAS-MOC-RPTS&QRYS-USERENV• SNAS-MOC-RPTS&QRYS-QUERIES


June 6, 200843


• O&M Client Functions – User Configuration Test Group

• SNAS-OM-USER-LOGIN• SNAS-OM-SYSMON-STAT• SNAS-OM-SYSMON-SYS

– SNAS and Mission Configuration Test Group • SNAS-OM-MSNMAINT-TDRS• SNAS-OM-MSNMAINT-NCCCONN• SNAS-OM-MSNADMIN-SIC • SNAS-OM-MSNADMIN-DASSSC• SNAS-OM-MSNADMIN-NCCSSC• SNAS-OM-MSNADMIN-MISC• SNAS-OM-MSNADMIN-PURGE• SNAS-OM-USERADM-ACCT• SNAS-OM-SYSMSG-BCAST

– SNAS Monitoring Test Group • SNAS-OM-SYSMON-MOC• SNAS-OM-SYSMON-NCC


June 6, 200844


• Security Test Group– Roles and Responsibilities– NIST Controls – General– NASA Wide Common Security Controls– Computer Support and Operations– Network Security Operations– Routine Monitoring– Periodic Testing and Security Controls Requirements– Incident Handling and Reporting– Awareness and Training– Account Management– Logical Access Requirements– Audit Trails and Accountability– Goddard Procedures and Guidelines

• Server System and System Performance Test – SNAS-SYSTEM-PERFORM– SNAS-SYSTEM-ETE– SNAS-SYSTEM-HA


June 6, 200845

RTVM Test CompletionRTVM Test Completion

• RTVM fields to be populated during AT

– Verification Status• Pass • Passed conditionally - test passed with some reservation• Failed• Blocked - the test was not performed for some reason

– Requirement Status• Fully Met• Partially Met• Not Met

– Approval Status• Approved • Disapproved

ID Req ID Requirement Method SAT Ver Case IDVerification

StatusRequirement

StatusApproval

StatusComments

1 3.1.1 The SNAS shall provide an interactive interface for planning, scheduling, and real-time monitoring and control of SN services.

Test SNAS-MOC-MSNSETUP-NCCSSC,SNAS-OM-MSNADMIN-NCCSSC,SNAS-OM-SYSMON-NCC

2 3.2.1.1 For all imported f iles, the message structure for each message type shall be validated as defined in 452-ICD-SN/CSM, ICD betw een the SN and Customers for Service Management.

Test SNAS-MOC-MSNSETUP-NCCSSC,SNAS-MOC-SCHED-TUT,SNAS-MOC-SCHEDNCC-SAR,SNAS-MOC-SCHEDNCC-RR,SNAS-MOC-SCHEDNCC-SDR,SNAS-MOC-SCHEDNCC-ASAR,SNAS-MOC-SCHEDNCC-WLR,SNAS-MOC-SCHEDTOOLS-REQUESTSNAS-OM-MSNADMIN-NCCSSC,SNAS-OM-SYSMON-NCC,SNAS-MOC-EPS-AUTONCC

3 3.2.1.2 For all imported f iles, the message structure for each message type shall be validated as defined in 452-ICD-SNAS/DAS, ICD betw een the SNAS and DAS, or

Test SNAS-MOC-SCHEDDAS-TVR,SNAS-MOC-SCHEDTOOLS-REQUEST,SNAS-MOC-EPS-AUTODAS

4 3.2.1.3 For all imported f iles, the message structure for each message type shall be validated as defined in 452-ICD-SNAS/EPS, Interface Control Document betw een the Space Netw ork Access System (SNAS) and the External Processing System (EPS).

Test SNAS-MOC-OVV-UAVPSAT,SNAS-MOC-OVV-TCWTSW

5 3.2.2.1 For all messages to be transmitted to the NCCDS or DAS, the Syntax shall be validated.


6 3.2.2.2 For all messages to be transmitted to the NCCDS or DAS, the Data type for each f ield shall be validated.


7 3.2.2.3 For all messages to be transmitted to the NCCDS or DAS, the Range of values for each f ield shall be validated.


8 3.2.2.4 For all messages to be transmitted to the NCCDS or DAS, it shall be validated that All required f ields have been entered.



June 6, 200846

Test Reporting Test Reporting

• AT Discrepancy Reporting– SN Comprehensive Discrepancy System (CDS)

• Internal Discrepancy Report (IDR) Database

• Test Status Meetings– Testers, System Developers, and Task Monitor– Review all open discrepancies and determine plan for resolution– Identify shared resource contentions and coordinate resource

availability with WSC management (DAS HMD)– Review valid discrepancies against concurrent on-going Beta

testing • Determine plan for resolution• No patches delivered unless required to continue AT or minimal impact

to testing (I.e., minimal regression test, no impacts to integrity of test results)

– Plan for meeting two times per week

• Final Test Report and PVM will be delivered following completion of AT


June 6, 200847

Test Resources Test Resources

• Testers Identified – WSC engineers with NCC and DAS experience

• NCC & DAS engineers trained in July 2007 at GSFC• Participated in Beta testing

• Supporting resources– Customer MOC

• Input of project unique configuration and data Orbital Data Processing Recurrent Scheduling EPS-Client message exchanges with legacy systems

– WSC DBA and SNAS SA• Maintain system configuration• Update database configurations


June 6, 200848

AT Risks and MitigationAT Risks and Mitigation

• If the test system connects to either NCC or DAS OPS during testing, there could be impacts to on-going SN mission operations.

• Rated: likelihood is LOW; consequence is HIGH• Mitigation:

Test SICs will be AT unique Property files will be adjusted to limit access

• Reduced risk to LOW

• With on-going Beta testers and AT testers sharing the same database (i.e., ANCC and DAS HMD) then there could be impacts to testing.

• Rated: likelihood is MEDIUM; consequence is HIGH• Mitigation:

Test SICS and/or SUPIDENS will be AT unique.

• Reduced risk to LOW


June 6, 200849

Open AT issuesOpen AT issues

• Version of DAS HMD to be used for SNAS AT. Continuing discussions with DASE project.

• Contention for DAS HMD resources during time planned for SNAS testing. Activities for DAS Enhancement Project (TO-83) will be on-going during SNAS AT. Work with WSC scheduling to optimize use of resources.


June 6, 2008

Transition and Training

David Warren


June 6, 200851

Releases and TransitioningReleases and Transitioning

• Release 0.1 06/4/08 Version for Acceptance Testing

(and ongoing Beta testing on I&T)

– Test team to determine need for updates to complete AT• Release 0.2, Release 0.3, etc. until testing completed

• Release 1.0 08/22/08 Version to go to Operations

• Release 2.0 10/08/08 Added Wishlist functionality– AT testers to repeat functional and regression testing

• MOC transitioning can start after 9/02/08 using Release 1.0– Follow WSC registration and approval process

– Work with O&M DBA for mission data (SIC, SSC, PE, etc,)

– Capability for NCCDS connectivity only, as DAS users must transition all at one time (DAS port limitation)


June 6, 200852

User TrainingUser Training

• E-Training– Successfully used to introduce functionality at three group

Customer Interface Meetings for Builds 1 – 4

– Live MOC Client interaction with Beta servers interfaced to DAS HMD and ANCC

• Training materials– Powerpoint Presentation

– MOC Client Users Guide – included with downloaded Client

– O&M Client Users Guide

• Beta System availability

• Network Operation Manager site-visits

• WSC Operations demonstrations


June 6, 200853

Follow-up

Rose Pajerski


June 6, 200854

Remaining ScheduleRemaining Schedule

• Acceptance Testing through 7/25/08• Beta Testing through 8/15/08• CIM #8 July• Transition to Operations July - September

– Training July & August– User’s Guide August– Server Operator’s Guide August

• ORR (date tba) 8/28/08• Operational Availability (NCCDS) starting September 2, 2008• Operational Availability (DAS) TBD


June 6, 200855

Post-TRR ActivitiesPost-TRR Activities

• Start Testing Immediately

• Respond to RFAs– Previous from earlier reviews (all closed)

– New one from today’s review

• Prepare Training materials

• Finalize project documentation– Security Plan

– Configuration Management Plan

– MOC and O&M User’s Guides

– Server Operators Guide

– Detailed Design Specification


June 6, 200856

Operational Documents Needed By ORROperational Documents Needed By ORR

• Information System Security Officer Functions new • System Administrator Functions

– Account Management new– Daily Floor Check update

• Security Audits– LOP for Security Audit process update

• Server Operations and Maintenance– Server Operators Guide update

• Database Management and Control Procedures– New Customer integration update

• Account management – including deletion of stale accounts• SIC, SSC, PE, etc. updates

• Sparing/Logistics plan update

• DSMC Operations Interface Procedures update

• Training – SNAS Overview for new users new– O&M Client, HA, and Server Operations new– MOC Client new


June 6, 200857

Next StepsNext Steps

• Plan for CIM #8 for July as 1st E-Training for Release 1

• Send documentation to CCB Review for final approvals– MOC and O&M Users Guides

– Server Operators Guide


June 6, 200858

In ClosingIn Closing

• Closing remarks from review board

• Thank you for your attendance

• RFA due date: Weds., 6/11/08 (Neil Dissinger, PAAC II)


June 6, 200859

Backup Slides


June 6, 200860

SRD DCN003 SRD DCN003 (1 of 6)(1 of 6)


June 6, 200861



June 6, 200862



June 6, 200863



June 6, 200864



June 6, 200865


test readiness review nasa/gsfc code 452 june 6, 2008 space network access system (snas) test...

Documents

systems readiness

nasa code

documentation readiness

test documentation

acceptance testing slide

wsc readiness criteria

test objectives clear

test plan testers