https://www.google.ie/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0CB8QFjAAahUKEwiY_6eenb_IAhUE2hoKHZbnB6U&url=http%3A%2F%2Fwww.mesh-ip.eu%2Fupload%2Fmesh-wp6-D6.3-20061116-User%2520Requirements-v4b.pdf&usg=AFQjCNFOaWxMjrwgIQGTUJ9bLG_wN0K_IQ&sig2=zkOpodsXyu2SYyPKZWdMpQ&bvm=bv.104819420,d.d24
The contents include:
- The methodology for gathering requirements: Focus Group, Questionnaires, ...
- Requirements are formatted using Use Cases, Functional and Non-Functional Requirements (what the system should do vs how the system works)
This is a good example of one style of requirements document, including interpretive research methods, using personas to make the scenarios more realistic and personal etc.
ReplyDelete