Target release1.0
Epic Link to related JIRA epic or feature
Document status
Document owner
DesignerLead designer
DevelopersLead developer
QALead tester

Goals

Background and strategic fit

Metrics are used for budget justification and performance review

Assumptions

Requirements

#TitleUser StoryImportanceNotes
1Pull data from SitestatsMany legacy applications have their metrics on Sitestats. Must Have
  • Additional considerations or noteworthy references (links, issues)
2Pull data from Google AnalyticsAll new web applications must included GA hooks

3Pull data from AWS logsAPI applications on AWS will need to have logs or other analytics available for compilation into Dashboard

4User generated reportsUsers will be able to generate reports using criteria such as a list of applications and time constraints

5Storage mechanism

Given the variety of sources of information it is likely the Dashboard will need its own storage mechanism



6CDISC/FDA reportingMust support reporting on downloads of value set and supporting files.






User interaction and design

Include any mockups, diagrams or visual designs relating to these requirements.

Questions

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

QuestionOutcome
How do we make different metric sources equivalentCommunicate the decision reached
What metrics are crucial
What metrics are informative but second level

Not Doing