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

Compare with Current View Page History

« Previous Version 41 Next »

Action items listed here were captured during the CoDR meeting sessions held April 15-16, 2020

OVERVIEW

  • SRDP-522  Add to risk register the insufficient details of the review variants at this stage, potential for cross talk and confusion in process details  that may be outside of current architecture Updated, marked done
  •  SRDP-496 & 475 clarify diagrams taking the technical nature of notation, generalize the diagram, and add a legend where needed  Added comment to both tickets, Assigned to Jeff as Post Review Action
  •  SRDP-493 clarify need for filtering and flexible project creation in System Description document, perhaps capture nature of observations at submission (DDT, RSRO, etc.) Added comment to ticket, assigned to Dana for Post Review Action
    • Add risk that we have not missed any other parts of the process  Updated Risk Register, see comment in ticket
  • SRDP-532 Done, solution discussed in meeting accepted - Closed
  • SRDP-461&531 Clarify requirement, compile a quantified list of things people like about the ALMA OT and what they don't like about the PST.  Mine Science Helpdesk tickets to identify what is tripping people up about the PST.
    Added above comment to ticket, assigned to Jeff as Post Review Action
  • SRDP-515 Add discussion of what needs to be captured to allocate subarrays to System Description under capabilities, perhaps also in Sec 2 Added comments to ticket, assigned to Dana as Post Action Review
    • Also add discussion on the ability for observers to request commensal systems to be on/off, does PI get to request data from commensal system?

REVIEWS

  • SRDP-522 Also discussed under OVERVIEW, no additional action from this discussion
  • SRDP-507 Clarify the wording that the tool does not automatically assign reviewers, Added Comment to ticket, assigned to Dana as post Review Action
  • SRDP-537 & 541 Point to current guidelines as the policy for defining conflicts Added Comment to ticket, assigned to Dana as post Review Action
  • SRDP-505 Although automated seems simple on the surface, too many edge cases drive this to a manual review for conflict, recommended solution accepted- Closed
  • SRDP-487 Committee recommends that the project should consider changing the Technical Justification from being tied to an Allocation Request to instead be tied to a Facility.  The project should perform an evaluation including stakeholders to evaluate the impact and necessity of this change. Added Comment to ticket, assigned to Jeff as post Review Action
  • SRDP-477 Change the wording to clarify that DDT proposals are not necessarily executed in the current semester  Added Comment to ticket, assigned to Dana as post Review Action

ARCHITECTURE

  • SRDP-521 & 514 Clarify either in the Preface or Sec 2 the definition of capabilities and resources, how they are associated with each other and relate to Allocation Requests, recognizing which apply to proposal submission and which to scheduling Added Comment to tickets, assigned SRDP-514 to Dana, SRDP-521 to Mark as post Review Actions
  •  
  • SRDP-513 Mark to clarify the placement of generators (internal vs. external) within the model added comment from slide to ticket, assigned to Mark. W. for Post Action Review
  • SRDP-520 Add sentence near figure that proposals may link to many projects added comment from slide and assigned as Post Action Review to Mark W.
  • SRDP-431 Close w/o action Closed
  • SRDP-516 Suggested action in Architecture slide is accepted, added comment from slide to ticket, assigned to Mark. W. for Post Action Review
  • SRDP-430 & 483 These are also related to the addition of reliability as a Quality Attribute, Develop and conduct several user driven Quality Attribute Scenarios, adding the plan and strategy to the document; potential scenarios include use of tutorials and the STSCI videos are a tool to shed light on how users use S/W to submit.  Deadline? Added Comment to tickets, assigned to Dana as post Review Action, although they are in the Architecture Review.

WORKFLOW

  • SRDP-501 Clarify as discussed in the Jira Ticket.
  • SRDP-519 & SRDP-540: Clarify Standard and nonstandard processing in the Document as discussed on the ticket. 
  • SRDP-489: Clarify in the document that the DDT case this is internal software view, but the "User View" will consist of a single screen for entry of information from all phases.
  • SRDP-480 Clarify the language and perhaps structure regarding reviews and approvals currently defined as Super TACs (especially as relates to HSA)
  • SRDP-440 Update System Description to reflect the requirement in the System Concept to capture to database approved Allocation Requests and Allocation Dispositions as well as the metrics to track these items
  • SRDP-495 The particular items to be edited should be done in the OPT,  add comment to ticket and close
  • SRDP-494
  • No labels