Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

« Previous Version 5 Next »

Goals

  • Develop the Recommendation page for the reviewers of the application
  • JIRA FT-19

Requirements

RequirementImportanceNotes

The Reviewers need access to this page.

Must Have

Option to select "Recommend" or "Not Recommend"

Must HaveThe DPC is the only committee not required to select an option; all others are
Chair of the committee is required to upload a recommendation report.Must Have 
Chair of the committee pushes the document to the next committee
via a "Done with Review" button
Must Have

See Workflow transitions screen

Committees must be able to view the recommendation
and recommendation report of the previous committees
Must HaveRecommendation report can be downloaded; doesn't have to be viewed in the online viewer

User interaction and design

 

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome

How long is the typical recommendation report that's uploaded by a committee chair?

  • Does it require certain elements/information?
    • Yes/No votes
    • Justification

Better to upload the file because they work on it together, sometimes on google doc.

There's no required information for a recommendation report.

Can the current committee see the recommendation file of the previous committees?

Yes, they want to see the recommendation file and "Recommended" or "Not Recommended".

Only at DPC level they're not required to do a recommend/not recommend; they will upload a
file that could be strengths and weaknesses

  • No labels