| The majority of requirements are derived and traced from user stories. The stories are scenarios that describe, in the users language, what they want to do with the DfR software. At the most detailed level, developers should be able to implement the story within a single iteration. Anything more complex than that is called an "epic" and must be subdivided into stories for development. I most cases the story should be written defining the actor and what they want the software to do. Actors are roles, they may be people or processes. The story should include who (the actor), what (needs to be done) and why (it needs to be done). It should be clear how to test the story for acceptance. |