Using the grid in Part 1 of the ‘CW1 templates’ document, elicit functional requirements via four user stories.For the “As a…” part of the user story template, choose primary stakeholders that you identify from the case study (see Section 1 of this document). One stakeholder could have more than one requirement to demonstrate what they need the system for. The user stories you choose should be considered critical to the success of the prototype and non-trivial.  For each of your user stories, you should also document acceptance criteria as a means of ensuring each requirement (via the user story) can be tested. Tip: if the acceptance criteria for a user story is difficult to write, check your user story is singular and not an ‘epic’ (see lecture notes). The user stories, and acceptance criteria, templates will give you experience of how requirements can be elicited, and documented, in Agile methodologies (often they are written on post-it notes!).
Part 2: Volere Template Shells Using the blank Volere requirements shell in Part 2 of ‘CW1 templates’, document two requirements as follows:
One functional requirement
One non-functional requirement
For your functional requirement, choose one of your user stories in Part 1 to describe the requirement in more detail in the Volere template. For your non-functional requirement, consult the case study, Volere template (see supporting resources in Section 3 of this document) and potentially other standard good practice/design you find from research as necessary.
You are expected to justify where you have derived each requirement from. Whether this is from the case study or other research, use the “supporting materials” section of the Volere shell to indicate this and keep you’re your source as specific as possible, e.g. section of case study.
Note that a specification of this kind could be used with a range of stakeholders, some of whom may be unfamiliar with the Volere Template, so you should use the “comments” section of the Volere shell as a key for any numbered ratings/codes so that its meaning is clear. The Volere template will give you experience of how requirements can be elicited, and documented, into a more formal specification, typical for some plan-driven methodologies
Analyse your user stories by completing a ‘pairwise’ comparison, deciding which is the ‘winning requirement’ using the following Likert scale devised by Saaty (2008).

Read less