Goals
- Create a dashboard for collection and display of EVS Metrics
Background and strategic fit
Metrics are used for budget justification and performance review
Assumptions
- The application will have access to Sitestats and Google analytics
- The dashboard will be accessed by government clients and used to generate reports
Requirements
| # | Title | User Story | Importance | Notes |
|---|---|---|---|---|
| 1 | Pull data from Sitestats | Many legacy applications have their metrics on Sitestats. | ||
| 2 | Pull data from Google Analytics | All new web applications must included GA hooks | ||
| 3 | Pull data from AWS logs | API applications on AWS will need to have logs or other analytics available for compilation into Dashboard | ||
| 4 | User generated reports | Users will be able to generate reports using criteria such as a list of applications and time constraints | ||
| 5 | Storage mechanism | Given the variety of sources of information it is likely the Dashboard will need its own storage mechanism | ||
| 6 | CDISC/FDA reporting | Must support reporting on downloads of value set and supporting files. | ||
User interaction and design
Questions
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Outcome |
|---|---|
| How do we make different metric sources equivalent | |
| What metrics are crucial | |
| What metrics are informative but second level |
