requirements and requirements engineering

Question 1

different types of requirements

Answer 1

business; overall goals
user
functional; what the software should do
non-functional; characteristics the system should have
system; how the system should be built

Question 1

requirements

Answer 1

a statements about a product that specifies what it should do or how it should perform

Question 2

functional requirements

Answer 2

processes the system must perform and information it should provide

Question 3

non-functional requirements

Answer 3

usability performance and maintainability - more about how the system runs

Question 4

what is requirements engineering and why should we do it

Answer 4

establishing user requirements as you want to get things right from the starts as it can be expensive or difficult to fix later

Question 5

requirements gathering

Answer 5

articulating and understanding the users needs via questionnaires, focus groups, interviews, observations and the think aloud technique

Question 6

requirements analysis

Answer 6

checking over the gathered requirements for contradictions or anything missing

Question 7

requirements documentation

Answer 7

expressed in a structured numbered way that’s easy for users to understand usually categorised into functional and non-functional with importance rankings and models

Question 8

requirements verification and validation

Answer 8

checking the requirements with users and stakeholders to find out if they’re correct and if they’re what they want

Question 9

what are some challenges of requirements

Answer 9

it can be hard to find out what users need as they may not be able to articulate it or be aware of technical restraints