user requirements (week 3) Flashcards
what are user requirements
–> it is the tasks that the user can accomplish with the product or what the product can do for the user.
what are the methods for expressing user requirements
- -> user stories
- -> use cases
- -> prototypes
- -> storyboards
what are user stories
–> user stories are expressed in everyday language and describe a specific goal from the perspective of the user along with the reason as to why they want it.
what is the format of the user story
- -> who = it is a stakeholder role for whom the requirement is being formed
- -> what = functionality that the stakeholder wants to achieve by using the product
- -> why = highlights the goals/visions of the product and provides insight into the value or benefit of the requirement
what is the role of the product owner in regards to the user stories
- -> write the user stories
- -> prioritise the user stories
what is acceptance criteria
user stories must be accompanied by the acceptance criteria
these are the conditions that the product must satisfy to be accepted by a user, stakeholders, or a product owner.
each user story must have at least 1 acceptance criteria
who introduced use cases
Ivar Jacobson
when were use cases introduced
1986
what is use case
it describes the interaction between the system and the external users that leads to achieving particular goals
what are the 3 main elements of use case
actors = these are the users outside the system that interact with the system
system = it is described by functional requirements that define an intended behaviour of the product
goals = the purposes of the interaction between users and the system are outlined as goals
what are the 2 formats to represent the use case specification documents
use case diagrams
use case description
what are the 4 elements in use case diagrams
use cases = drawn with ovals and represent the different scenarios that actors might have with the system
system boundaries = box that groups various use cases in a system
actors = figures that depict external users (people or systems) that interact with the system
associations = drawn with lines and show the different types of realtions between actors and use cases
what is use case description
represents the sequence of events along with other information that relates to this use case.
the template typically includes
- -> description
- -> actors
- -> pre and post conditions
- -> main flow
- -> alternative flow
what are 2 difference between use case and user stories
–> user stories are about needs whereas use cases are about the behaviour you will build into the system to perform those needs
–> user stories are easy for users to read whereas use cases describe interaction between the software and the users
what are the 3 types of prototypes
wireframes
mockups
design prototypes
