requirements (week 2) Flashcards
what is a requirement
–> a software capability needed by the user to solve a problem or to achieve an objective
requirement activities are linked to other development activities such as
- -> design
- -> implementation
- -> testing
what are the 2 types of requirements
- -> functional requirements
- -> non functional requirements
what are functional requirements
–> capabilities that the system must have
–> functions that the system must perform for each of the users of the system
what are non functional requirements
–> these are constraints that the new system must meet
–> eg saving orders must be completed in less than 5 seconds
what are the properties of the requirements
–> consistent
–> unambiguous
–> comprehensive
- -> prioritised
- -> more important features first and implement in a way that achieves the best outcome - -> verifiable
- -> documentation must be verifiable on how the features that are developed satisfy the requirements
what are the activities in requirement analysis
- -> eliciting requirements
- -> analysing requirements
- -> requirements modelling
- -> review and retrospective
what is the objective of eliciting requirements
- -> the task of communicating with customers and users to determine what their requirements are
- -> also called requirement gathering
what is the objective of analysing requirements
- -> determine whether the stated requirements are incomplete ambiguous or contradictory
- -> resolve these issues
what is the objective of requirements modelling
–> requirements may be documented in various forms such as use cases and user stories and natural lang docs
what is the objective of the review and retrospective
- -> team members reflect on what happened in the iteration
- -> identify actions for improvement going forward
