Feature Template
Note
describe the feature and general details across teams here
Implementation
If you are interested in the implementation, lets dive into it with following quicklinks:
<Android>
<Backend>
<iOS>
Requirement Template
A requirement should consists of following content:
Priority |
{low, med, high } |
Status |
{idea, discussed, determined} |
Involved stakeholders |
|
Implemented in |
{back end VERSIONnr. , android VERSIONnr. , ios VERSIONnr.} |
Dependency |
Is this requirement somehow related to another one? |
Motivation/Reason |
Describe the default use case from user perspective As <Persona>, I want to <do something>, so that I <why?>. |
Description |
You should write a detailed requirement description here |
Functional Requirements
Example: News and Event-Feature
NE-1 News Priority
high
Status
determined
Involved stakeholders
Development Team
Implemented in
backend 1.0.0 , android 1.0.0, ios 1.0.0
Dependency
Description
A news shall consists of a timestamp, an adequate picture, a headline and a description.
NE-2 Events Priority
high
Status
determined
Involved stakeholders
Development Team
Implemented in
backend 1.0.0 , android 1.0.0, ios 1.0.0
Dependency
Description
An event shall consists of a timestamp, a location, an adequate picture, a headline, a description and an organizer.
NE-3 Listing of news and events Priority
high
Status
determined
Involved stakeholders
Development Team
Implemented in
backend 1.0.0 , android 1.0.0, ios 1.0.0
Dependency
NE-1, NE-2
Description
Users can switch between the news and events view via tab bar and the system shall provide a list of the last (most recent) 10 news and events. If the end of the list is reached while scrolling, 5 more events are reloaded and added to the end of the list. By default the latest events and news should be displayed.