Page History

• Date: //date
• Time: 9:00 ET
• Location: nraozoom04 
• Sprint Calendar

Attendance:

• Jeff Kern
• Dana Balser
• Mark Whitehead 
• Allison Costa
• Mark Ferguson 

Agenda:

• 11/10, 11 am EST (next Thursday)
  • planned TTAT discussion at TTA meeting
• TTAT User's Guide (Allie)
  • Allie is going to update the quick start guide with Dana's suggestions and send out to Dev team too
• Sprint 40 feedback
  • Allie is going to move the consensus comments into a Jira ticket.
• Following  Following up on Dev discussions:
  
  • Feasibility Justification hook deferred.
  • Do we want versioning on Consensus Reviews (requirement in Sys Desc). See 

    Jira
    server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-1055

    • Jeff is going to ask Tony R about the extent of this requirement. Mark F says that they have this in their implementation plan such that in the future, it could be supported.
  • Science Categories to Panels
    
    • Section 3.4.2 in Sys Desc says
      
      • There shall be a many-to-one mapping between SRPs andSCIENCE CATEGORIES. In the case where multiple SRPs are connected to the sameSCIENCE CATEGORY, we implicitly assume that a given proposal is only reviewed by one SRP; that is, the proposals are divided between the SRPs.
    •  Conceptual Architecture 2.1.2.3.1.2 Element Catalog says
      • There is a many-to-many relationship between Science Categories and SRPs.

    • Jira
      server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-870

    • The domain model should reflect 1 SC to 1 SRP panel, 2 SCs to 1 SRP panel, 1 SC to 2 SRP panels, but currently the scope is just 1 to 1 and 2 SC to 1, as the 1 SC to 2 requires more work (e.g., sorting proposals)
      • Dana will update System Description
      • Mark will update text in Conceptual Architecture

Open Actions: