Unit 4 - The case study: part 1 Flashcards
What are the main differences between a use case and a user story?
A use case describes a business process or a self-contained task within a process. It is as complete as possible, lasts as a document, is agreed (by
customers and developers) and is used to generate requirements.
A user story is small enough to be implemented in a single iteration, represents an instance from a user perspective, is not complete, does not last and instead is used as a reminder for a conversation.
Consider the required characteristics of a user story as described in Unit 2: independent, negotiable, valuable to users and customers, estimable, small, testable.
Give an example of another valid user story for this case study and of a user story that would not satisfy these criteria.
Another valid user story could be:
. as a manager I can remove a room from the bookable rooms in a hotel when the room is being refurbished.
An example of a user story that does not satisfy the criteria is:
. as a guest I must find the interface friendly – this is not a good example as it is not a testable story.
In the Volere template in Section 6, we recorded some non-functional requirements. What further work is needed in order to produce the software requirements?
We need to remove any ambiguities and add clear fit criteria.
Additionally, we need to identify which functional requirements they constrain; in some instances, they will apply to whole use cases.
Often we will need to consult the system stakeholders for further details.
What else needs to be done in terms of non-functional requirements?
We should look at each use case and see whether we identify other non-functional requirements based on the use case steps.
We can do this by looking at the functional software requirements in turn (each corresponding to a use case step), and considering whether there are any non-functional requirements that apply to them but have been omitted.
