You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 29 Next »

The objectives of this review are to ensure that:

  • The L1 capabilities projected for delivery to Pilot Operations are ready for verification and validation.
  • That the software system to be tested is under configuration control and is available in the software test environment.
  • That any items not yet ready for test are identified with a plan to advance them to a state of completion and test prior to delivery to Pilot Operations.
  • That a suite of tests sufficient for verification and validation have been defined.

Review Plan

  • This is an internal SRDP Project Office review, the Review Plan is completely described within this Confluence page
  • The Review is scheduled for May 3, 2019

Participants

  • Project Office: Jeff, John, Mark, Bob
  • DMS: Mark Whitehead, Stephan, Kana, Morgan, Andy, David, James

Artifacts Under Review

DateItem or Event and Deadline for AvailabilityResponsible
5/3/2019




RVTM (Requirements Verification Traceability Matrix)SRDP PM

Test Environment Ready (including configuration list) to support the L1 Verification and Validation

DMS
L2 Verification/Validation CompleteDMS/SRDP Heur.

L1 Verification Plan and Test Procedures Complete for the following:

  • OUS Restores
  • VLA Calibration Pipeline
  • Archive Interface
  • Optimized Imaging

L1 Verification Plan 5.2.2019

DMS

L1 Validation Plan for Heuristics and Operations Test procedures in Jira

LI Validation Plan 5.2.2019

SRDP Heur. / SRDP Ops.
5/8/2019Outstanding Issues and incurred Risk DefinedSRDP PM
Report on Outcome of Review - Delta TRR scheduled for May 17, 2019SRDP PD

Pilot TRR Agenda

  1. SRDP Project Director: Opening Remarks
  2. DMS: Test Environment Ready (including configuration list)

  3. SRDP PM: Present Verification and Validation RVTMs; review process to track V&V against the requirements
  4. DMS:  Present L2 verification and validation completion report, based on Jira ticket status
  5. DMS:  Present L1 Verification Plan and Test Procedures, defined within the set of Jira Test Tickets
  6. SRDP Project Scientist: Present L1 Validation Plan and Test procedures defined within the set of Jira Test Tickets
  7. SRDP Operations Mgr.:  Present Operations Process Test Plan defined within the set of Jira Test Tickets: SRDP-336; SRDP-337; SRDP-338, SRDP-340
  8. SRDP Project Director: Preliminary assessment of Test Readiness, itemize any key blockers or major risk to resolve before proceeding

Outcome of Pilot Ops TRR

Report prepared by SRDP Project Director to include:

  • Outcome of review to be one of the following:

    Initial outcome May 3, was a Fail.  Significant issues were identified in both the test configuration control, and feature completion.  Delta TRR scheduled for May 17 to review progress and assess.

Pilot (Delta) TRR Agenda - May 17, 2019

  1. SRDP Project Director: Opening Remarks
  2. SRDP PM: Review Open Actions from TRR
  3. SRDP PM: Review issues since TRR:

    Issue NumberDescriptionReferencesImpactReported byDateOwner/Assigned in Jira
    1Outstanding requirement to allow selection of pre-release CASA versions within the Archive menu pull down described in SSA-5592 is not in the L1 Doc or model, should this be aded?SSA-5592Revision to Requirements and all downstream artifacts (model, V&V Test, etc), added work to DMSJeff Kern5/13/2019Richard Falardeau 
    2Spectral cutouts within a spectral window (ALMA Cube Imaging) can only be exported to a single file, unsure if additional exports are overwriting a previously generated file.  ALMA exports a single file since cutouts are not supported.PIPE-345Significant inconvenience, workarounds are in discussionJoe Masters / John Tobin5/13/2019Kana
    3The export of calibration products from the VLA pipeline run is addressed in PIPE-47 is not working as expectedPotential blocker to Pilot OpsJohn Tobin5/13/2019Kana
    4SRDP-251 (ALMA Metadata) missing EBs although the DB was reported as copied from productionSRDP-251 (ALMA), SRDP-253 (VLA) & SSA-5583Blocker to Pilot Ops due to partial validationJohn Tobin5/13/2019John Tobin
    5Permissions within archive to download to local directoriesSRDP-209, SRDP-218, SSA-5268Significant inconvenience, no progress since Dec 2018John Tobin5/13/2019John Tobin
  4. Any Other issues?


    1. Pass: All inputs are satisfactory, no additional risks found, proceed as scheduled.
    2. Risk Identified: One or more risks were identified requiring additional attention.  Risk is not deemed sufficient to affect the schedule.  Risk management plan shall be updated.
    3. Partial Pass: One or more risks are likely to impact schedule of the release.  Re-planning to address risk required.
    4. Fail: Sufficient risk identified to halt the release.  Re-planning or rescoping required.

  5. Outcome less than an unconditional "Pass" shall include recommended steps and dates to rectify all discrepancies
  6. SRDP Project Director: Closing Statement / next steps

Mid-Pilot TRR Agenda - July 9, 2019

Participants

SRDP Project Office: John Tobin, Mark lacy, Bob Treacy

DMS: Morgan Griffith, Mark Whitehead, Stephan Witz, Kana Sugimoto, Joe Masters

  1. SRDP PM: Review Open Actions required to deliver Pilot Operations Capability to Validation

    1. PIPE-389 - Template recipe: creation of 'mfs' and 'cont' images
      • Ready to validate
    2. SSA-5113 - Epic ticket: Implement ALMA optimized imaging cube capability
      • Review Issues under Epic for Blockers and completion target dates
    3. SSA-5330 Epic Ticket: Science Products, Ancillary Products and Associations
      • Review Issues under Epic for completion target dates
      • Still tagged for SRDP Pilot, No known blockers for Optimized Imaging
    4. (ML) Status of SSA-5599 Epic ticket - workaround scripts for Optimized Imaging workflow corresponding to requirements on Requirements for SSA work-around scripts for pilot, including SSA-5604, SSA-5632, SSA-5605.
    5. Identify Configuration changes (i.e. versions reflecting changes from these tickets)
    6. Any Other issues?
      1. Account permissions etc for DAs and AoD (ML) to run jobs as almapipe.
    7. Review and Assign Action Items


Issue NumberDescriptionReferencesImpactReported byDateOwner/Assigned in Jira
M1




















  • No labels