Gamma-ray Large Area Space Telescope
Download
1 / 10

GLAST Large Area Telescope - PowerPoint PPT Presentation


  • 82 Views
  • Uploaded on

Gamma-ray Large Area Space Telescope. GLAST Large Area Telescope. LAT Level Verification LAT Level Requirement Review Kickoff Rich Baun Systems Engineering. Agenda. Requirement and verification flowdown overview Test Case review process overview Requirements responsibilities

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' GLAST Large Area Telescope' - hedwig-hubbard


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

Gamma-ray Large Area Space Telescope

GLAST Large Area Telescope

LAT Level Verification

LAT Level

Requirement Review Kickoff

Rich Baun

Systems Engineering


Agenda
Agenda

  • Requirement and verification flowdown overview

  • Test Case review process overview

  • Requirements responsibilities

  • Test case review

    Test & Verification Website

    http://www-glast.slac.stanford.edu/systemengineering/Verification%20&%20Test/Verification%20and%20Test.htm




Requirement owner responsibilities
Requirement Owner Responsibilities

  • Know which requirements you are responsible to buy-off

  • Know where and how your requirements are sold

  • Determine your requirement type

    • Functional – Function not impacted by environments, i.e. Commanding

    • Environmental – Specific to an environment, usually requires analysis of environmental test data (Thermal, Dynamics, EMI)

    • Performance – Requires trending, not sold until after TV

  • Determine what sells your requirement

    • Successful completion of a test? Data collected and checked by a test? Post test analysis of test data? Analysis only?

      • There are test reports, test logs, configuration files, digi files (if applicable), and recon files (if applicable) available for review

    • The VCRM identifies what tests sell what reqts

    • Test case outlines show where and how each test sells reqts

  • Write an NCR if you find an anomaly

  • Provide objective evidence that a requirement is sold

    • You must certify the LAT complies to the requirement

      • Is analysis and a formal report required to document compliance?


How to report a requirement sell off
How to Report a Requirement sell-off

  • Report the requirement sell-off to Systems

    • For reqts not needing a formal report (most requirements)

      • Send an e-mail with the following information

        • Requirement number (REQID) or Verification Plan number (VERID)

        • Date, time, and run number when supporting test case(s) were run

          • If data was collected from multiple runs, each run must be noted

        • Worse case test data that supports the reqt was sold (if applicable)

        • Compliance statement, i.e. the report must state definitively the LAT complies with the requirement

          • Margin to the requirement must be stated where appropriate

        • Any NCRs or JIRAs associated with the requirement must be listed

    • For requirements needing a formal report

      • Write a Requirements Verification Report (RVR)

        • See next slide for details

        • You will be notified if a requirement needs an RVR


Requirements verification reports
Requirements Verification Reports

  • For an agreed to subset of LAT requirements only, not all reqts

  • Must have an assigned LAT Docs number

  • Minimum RVR contents

    • Requirement owner’s name

    • Requirement source, text, and number

    • Verification Plan text and number

    • Supporting test case name and number (if applicable)

    • Script name(s) used to run test

    • Date, time, and run number when supporting test case(s) were run

      • If data was collected from multiple runs, each run must be noted

    • Compliance statement, i.e. the report must state definitively the LAT complies with the requirement

      • Margin to the requirement must be stated where appropriate

    • Supporting documentation of test data, analysis, and results

    • Deviations from the verification plan and the reasons for the deviations must be stated

    • Any NCRs or JIRAs associated with the requirement must be listed





ad