Target release | Release name or number |
---|
Epic | Link to related JIRA epic or feature |
---|
Source Code | Link to GitHub Repository |
---|
Project Status | |
---|
Document status | |
---|
Document owner | Mohit Kumar Bajoria |
---|
Designer | Lead designer |
---|
Developers | Lead developer |
---|
QA | Lead tester |
---|
|
Project Summary
Goals
- Add offline support in community-app then we can have same application working on all browsers with offline support and need of a desktop app will not be needed.
Background, Impact, and User Need
Why are you doing this? How does this relate to your overall product strategy?
Deliverables
Insert list of project deliverables here including documentation, etc.
Project Implementation Plan
Detailed implementation plan
Schedule/Timeline
High level schedule for implementation based on GSOC calendar
Additional Resources
Link to background, wiki pages, other similar work, research related to the project.
Requirements
Assumptions
- List the assumptions you have such as user, technical or other business assumptions. (e.g. users will primarily access this feature from a tablet).
User Stories
# | Title | User Story | Importance | Notes |
---|
1 | Short identifier for the story | Describe the user and what they are trying to achieve | Must Have | - Additional considerations or noteworthy references (links, issues)
|
| | | | |
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:
Question | Outcome |
---|
(e.g. How we make users more aware of this feature?) | Communicate the decision reached |
Not Doing
- List the features discussed which are out of scope or might be revisited in a later release.