...
-
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 conflictsAdded 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 semesterAdded 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
- SRDP-513 Mark to clarify the placement of generators (internal vs. external) within the model
- SRDP-520 Add sentence near figure that proposals may link to many projects
- SRDP-431 Close w/o action
- SRDP-516 Suggested action in Architecture slide is accepted
- 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?