Req:template
From FOSSWiki
Contents |
[edit]
Module/Requirements Title
[edit]
Current Status
- Latest Stable version: v0.1
- Release date: DD-MM-YYYY
- Latest Beta version: v0.2
- Implementation [done]
- Requirements validations [done]
- Code convention checks [done]
- Beta testing [in progress]
- Release
[edit]
Objective, Scope
The purpose of this module is to:
- objective 1
- objective 2
The scope of this module is constrained to ....
[edit]
Target Audience + Roles
The expect target audience for this module is ...
The typical roles and respective benefits are:
- role1 - will use the system to ...
- role2 - will benefit by ..
[edit]
Describing Entity/Attribute/Relationships
In relation to the module that you are designing, please describe them here. Think carefully of how you intend to name things, as your choices will have to be referenced consistently across the system and ask experts and users in your group to comment and give you feedback on your proposed choice:
- entity1 - Name (explanation?)
- attribute 1.1 - Name - definition -
- attribute 1.2 - Name - definition
- entity2 - Name (explanation?)
- attribute 2.1 - Name - definition -
- attribute 2.2 - Name - definition
- relationship Name - (explanation)
- relationship type: ie Cardinality (one to one, one to many, between which entities is this relationship taking place)
- Optional relationship (can or cannot happen) or Mandatory (must happen?)
other info about this relationship
other information:
- invoking/referencing what other data/function?
- triggering which process? events? states
- others (e.g constraints, etc)
[edit]
Functional requirements in Stories
1.1 Don [done v0.2] "we should have x feature as referenced in the mail thread <url>"
1.2 Paul lets use the following standards when doing data exchnage * url1, url2
Administration
2.1 [done v0.1] Chamindra "We should have y feature.. in the " 2.1.1 [done v0.2] Gavin "however a problem with feature.."
2.2 Paola "A bio metrics.."
Reporting
3.1 fff
[edit]
Non-functional requirements in Stories
Expect load and concurrency
4.1 Gavin "we need about 20 concurrent users"
Information security
5.1 .....
Data backup, disaster recovery, fault tolerance
6.1
[edit]
User Interface Prototypes
Picture 1 Image:Example.jpg

