ECS Verification Database - Ticket Reports

ECS Verification Databse - Ticket Reports

NASA Logo

VDB Home Page
- VDB Tickets
- VDB Data Search
- VDB Reports
  - Standard Reports
  - Status Reports
  - ITP Reports
  - Delta Reports
  - Orphan Reports
  - Special Reports
- VDB Database
- VDB Support


Earth Science Enterprise

EOS Projects

ESDIS Home Page
-ESDIS CM System
-ESDIS Requirements
-ESDIS Docs

EDHS Home Page
- EDHS CM Page
- EDF/CSDV CCB

NASA Home Page

Developed by
Raytheon Logo

VDB Support

IT Security Warning

  

Tickets are an ECS development concept that draws together information from various database tables into a single, cohesive description of each ECS Release Capability as identified in the ECS System Science Release Plans. These data sets are created in real-time from numerous VDB tables.

Tickets
Select By:
Ticket Name:
OR:
NCR No:

Show L4 Mappings?:



L4 Traceability Report
 
The VDB supports L4 to Component traceability for certain subsystems. Tickets that contain L4 requirements for any of the supported subsystems are considered "supported tickets." Supported tickets may include some L4 requirements from subsystems for which traceability is not supported, in which case the CI link is designated "N/A". See the selection window "Select by Ticket ID" for the list of currently supported tickets.
 
Master Report:

This report includes a record for every L4 requirement that appears on any ticket that is supported for traceability, whether or not any traceability data has already been mapped to the requirement.


Report Name:
 
Select By Ticket ID:

This report is simply an excerpt of the Master L4 Traceabiliy Report for a single ticket. It includes a record for every L4 requirement that appears on the selected ticket. This report identifies records for which traceability data is missing and should be a review item in the requirements review for a ticket. It can also be used as the basis for creating traceability documentation for design reviews.

 
Ticket ID:
 
Select By CI Subsystem:

This report only shows L4 records that already contain L4 to CI traceability data. It is useful for research to survey a particular subsystem, but is not suitable for use as a review item because it may not be complete.

 
CI Subsystem:

   
       

 
  Why are Tickets important?
 
   
  What does a Ticket contain?
   
  What's the meaning of "Latest CCR Affecting this Ticket" and "Latest CCR Date Affecting this Ticket?"
   
  What is the "Number of Tracked Ticket Changes?"