Feature Overview (aka. Goal Summary)

An elevator pitch (value statement) that describes the Feature in a clear,
concise way.

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving
this feature. Include the anticipated primary user type/persona and which
existing features, if any, will be expanded.

The goal is to allow an admin to be able to determine the usage of RHDH based on users accessing the system.

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order
to be considered complete. If the feature spans across releases then good
to have scope for each release with acceptance criteria. Be sure to
include nonfunctional requirements such as security, reliability,
performance, maintainability, scalability, usability, etc.

Here are the key requirements for this feature

• Need # of unique users (P1)
• Username of the users above (P1)
• First-time login of the user (p1)
• Last time login of the user (P1)
• Frequency of login of the user (total times or weekly etc)
• Downloadable report (P1)
• UI for the above