1 / 7

External Subsetter System OSS Process Jeanne Behnke July 11, 2002

External Subsetter System OSS Process Jeanne Behnke July 11, 2002. OSS - ECS Operations Support. HEW/HSA proposed to be a Type III Component

rosemaryvaldez
Download Presentation

External Subsetter System OSS Process Jeanne Behnke July 11, 2002

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. External Subsetter SystemOSS ProcessJeanne BehnkeJuly 11, 2002

  2. OSS - ECS Operations Support • HEW/HSA proposed to be a Type III Component • Definition: extend ECS requirements (e.g., EDGRS, QA MUT). ECS or non-ECS organizations may develop these components, however, ECS involvement in the development or operation of these components would require a CCR. Either ESDIS or Raytheon may identify a CCR as an OSS candidate and if both parties concur, the reduced costs associated with OSS development and maintenance will be reflected in the ECS ROM for the CCR. EDG is NOT an OSS, it is external to ECS.

  3. Criteria for Implementation • HSA/HEW (and other subsetters) was developed with ECS supported languages and be able to be built with ECS baseline development tools • HSA/HEW (and other subsetters) must be executed with baseline versions of ECS COTS • HSA/HEW, etc… must be mode aware • Documentation will be sent to ECS

  4. Delivery to ECS • HSA/HEW components will be delivered to ECS in a specified directory structure to facilitate incorporation into the ECS baseline. • UAH has experience with this from the SYNERGY II integration phase. • UAH needs to deliver as part of the component the scripts needed to build, install, and deliver ESS. • Have experience with this

  5. Delivery (continued) • Process starts with a CCR initiated by an ECS architect/advocate and UAH for review by M&O CCB • Review and approval by the ERB • At this point, it is available to the DAACS from ECS • New release delivered as part of an ECS release • Updates to HSA/HEW are available through the ECS Test Executable Process

  6. Delivery (continued) • Deliver includes HSA/HEW tar file including scripts and build instructions • Timeframe for ECS process for review, approval, incorporation and delivery is 30 days • HSA/HEW will be available as an OSS component in Fall 2002

  7. OSS Testing Policies • ECS will not do any test or integration of HSA/HEW • HSA/HEW will not be formally verified through ECS • HSA/HEW defects and enhancements managed by the ECS Trouble Ticket, NCR, and Deployment process • UAH will maintain HSA/HEW

More Related