U.S. ATLAS HL-LHC Upgrade LAr Level 2 and Level 3 Managers Mailing List

[John Parsons <parsons AT nevis.columbia.edu>]

Hello all,

	Another task for the NSF L3s: please fill out the attached table for 
your deliverables.  We are already late, so please do asap and send back 
to me.
        Thanks,
                John

-------- Forwarded Message --------
Subject:        Fwd: Requirements Verification Matrix
Date:   Wed, 4 Mar 2020 14:52:18 -0500
From:   Hal Evans <hgevans AT indiana.edu>
To: 	John Parsons <parsons AT nevis.columbia.edu>, Ma, Hong <hma AT bnl.gov>, 
Mark Oreglia <oreglia AT uchicago.edu>, David Miller 
<David.W.Miller AT uchicago.edu>
CC: 	usatlas-hllhc-pomgmt-l AT lists.bnl.gov 
<usatlas-hllhc-pomgmt-l AT lists.bnl.gov>



Hi John, Hong, Mark, and David,

Where do you stand on getting a first draft of RVMs for your L3 systems 
ready? We should really try to have something before the end of the week.

Thanks  -  Hal



-------- Forwarded Message --------
Subject:        Requirements Verification Matrix
Date:   Fri, 7 Feb 2020 11:31:03 -0500
From:   Hal Evans <hgevans AT indiana.edu>
To: 	Usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov 
<Usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov>



Dear NSF L2Ms and DL2Ms,

As one of the recommendations from the NSF FDR we were asked to prepare 
Requirements Verification Matrices for our QA/QC work. The information 
to construct these RVMs is already available in the QA/QC documents for 
the individual deliverables (WBS L3 items) and in the US ATLAS 
Specifications Document (docdb #216 
<https://atlas-hllhc.docdb.bnl.gov/cgi-bin/public/ShowDocument?docid=216>, 
user-review, pwd=p2-lhc). Since the RVM is a summary of existing 
information, we'd like to keep it compact and not too difficult for the 
L3 managers to construct.

I'm attaching an example of what we have in mind here, based on the LAr 
FE electronics - WBS 6.4.1. Explanations of the individual fields are 
appended below.

Could you forward this to your L3 managers and ask them to start working 
on an RVM for their system? It would be good to have first drafts of 
these available by the end of February. I will be away from Feb.10-27, 
but Gustaaf can answer any questions you might have on this (sorry 
Gustaaf!).

Thanks  -  Hal

RVM Entry Explanations

  * One spreadsheet per L3 system
      o Post in same docdb entry as QA/QC document
  * Requirement No.
      o Each requirement from the specs spreadsheet gets a separate
        number, referenced at WBS L4: e.g./R-6.4.1.1-001/
  * Requirement
      o Extract individual requirements from specs spreadsheet
        (docdb-216) text - one requirement per row
      o First requirement should be a brief description of the deliverable
      o Need to ensure synchronization with US ATLAS Specs spreadsheet
  * Specifications Document
      o Link to ATLAS Specifications (or other) document in which this
        requirement is stated - specify where the requirement is stated
        (section, table, etc.)
  * Verification Method. Possible options are
      o /Test:/this is the normal verification method to be done at the
        QA or QC step
      o /Review:/use this for the architectural requirements (like the
        deliverable description)
  * Where Verified
      o where will the requirement be verified: institute test stand,
        CERN test facility,...
  * Responsible Institute(s)
      o list all institutes testing this requirement
  * Quality Assurance
      o Documented: QA results will usually be documented in the FDR
      o Sign-Off: usually this will be the FDR committee report
  * Quality Control
      o Documented: indicate where the results of QC testing will be
        stored, i.e. a link to a database, a document, etc. "---" if not
        a QC requirement
      o Sign-Off: this represents where the QC criteria are approved.
        Normally it will be the PRR committee report
  * Comments
      o Anything of relevance not covered in the other entries

--
^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v
  Hal Evanshgevans AT indiana.edu
            https://urldefense.com/v3/__http://pages.iu.edu/*hgevans/__;fg!!P4SdNyxKAPE!XgH-pzglzkIpjMke3bpD-Xu87oLZAbkjQCfg-iAfWfUEg7VykOxOYAeZ9sYi_dGoQ99uLwKgdu1FFnXcevkK$ 
  Tel: (812)856-3828                Fax: (812)855-5533
  253 Swain Hall West               Indiana University
  727 E. Third St.               Bloomington, IN 47405
v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^

--
^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v
  Hal Evanshgevans AT indiana.edu
            https://urldefense.com/v3/__http://pages.iu.edu/*hgevans/__;fg!!P4SdNyxKAPE!XgH-pzglzkIpjMke3bpD-Xu87oLZAbkjQCfg-iAfWfUEg7VykOxOYAeZ9sYi_dGoQ99uLwKgdu1FFnXcevkK$ 
  Tel: (812)856-3828                Fax: (812)855-5533
  253 Swain Hall West               Indiana University
  727 E. Third St.               Bloomington, IN 47405
v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^

Attachment: RVM_6.4.1_v02.xlsx
Description: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet