System Requirements Flashcards
What are Requirements?
- Determine the required functionality of the system
- Produce specifications that describe the system
- Key to producing a successful system
What are some difficulties with Requirements?
- Small mistakes, big impact later
- Users don’t know what they want
- Hard to get right the first time
What is the order for defining requirements?
Should be done systematically
- Stakeholder analysis and involvement
- Assess, combine, prioritise
- Iterate, get feedback, prototype
What are 3 things the Requirements Gathering process should be?
- Organised
- Iterative
- Easy to understand
What are 3 ways requirements can be gathered?
- Interviews
- Questionnaires
- Existing systems
What are some 4 stakeholder examples?
- Managers
- Employees
- Suppliers
- Customers
What are some issues that can arise with stakeholders and what approach can be used?
- Not all stakeholders are equal
- Cannot please all people all of the time
- Perform Stakeholder Analysis to choose the best approach
What is some issues with Requirements?
- Missing
- Poor quality: incoherent, imprecise, impossible, open to interpretation
- Irrelevant: not needed, too early, obvious
- Need to identify and correct in early stages through iteration
What is Functional Requirements?
Define what a product must do and what its features and functions are
What is Non-functional Requirements?
Describe the general properties of a system
What is MoSCoW analysis?
- Must have: critical, essential to the system
- Should have: ideally have these
- Could have: optional extras
- Won’t have: not to be implemented this time
What are some features of Requirements in Iterative Development?
- Continuous refinement
- Constant checking/rechecking for suitability
- Easier/earlier identification of mistakes
- More flexibility for requirements change
- Ability to prototype requirements, system parts, whole system
- Better visibility
