Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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:
    • Need Stories for
      Technical Feasibility Justification hook deferred.
    • do Do we want versioning on Consensus Reviews (requirement in Sys Desc). See 
      Jira
      serverDMS JIRA
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
      keySTT-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. if so, need story to view them and to do versioning
    • Science Categories to Panels - Source of Truth and updating STT-870
      • 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
        serverDMS JIRA
        columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
        keySTT-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:

Task report
pages68321335