Introduction
An important part of the requirements gathering process is to engage end users and stakeholders. In an infrastructure project of this nature, a good way to relay the types of functionality that will be supported is through user stories. These stories demonstrate the types of functionality that will be directly supported by the infrastructure, as well as the types of tooling that will be enabled by the infrastructure.
Stories
# |
Story |
Priority |
Status |
|---|---|---|---|
1 |
|
|
|
2 |
|
|
|
3 |
|
|
|
4 |
|
|
|
5 |
|
|
|
6 |
|
|
|
7 |
|
|
|
8 |
|
|
|
9 |
|
|
|
10 |
|
|
|
Terminology
Priority
- Must: this story must absolutely be supported by the semantic infrastructure in order to meet the core needs of the community
- Should: this story should be supported by the semantic infrastructure because it represents important functionality without which many user needs will not be met
- Could: this story is not critical to the needs of the community but is "nice to have"
Status
- Draft: the story is still under development by the semantic infrastructure analysts
- Review: the story has completed the analysis process and is under a period of community review and comment
- Confirmed: the story has been reviewed and confirmed by the community
