Requirements Flashcards
What do requirements define?
What a product is meant to do and meant to be
The product will never be right unless it conforms to
the requirements
Why should requirements be agreed in writing?
Protects both developers and client
What does the requirements specification state?
All the necessary details of what the client needs and wants in his software
What is the difference between functional and non functional requirements?
Functional: what the product will do
Non-functional: how well it will do it
What do functional requirements describe/
the actions the product must take if it is to be useful to a user
“The product shall detect when the air temperature falls below freezing” is an example of a ________________ requirement
Functional
What do non-functional requirements describe?
Properties or qualities the product must have to be acceptable
e.g. look and feel, how well it performs, legal attributes
“The product must be able to determine ‘friend or foe’ in less than 0.25 seconds” is an example of a _________________ requirement
Non functional
What are constraints?
Global requirements or limitations on the project or eventual design
The product must be available at the beginning of the next academic year is an example of a ____________
constraint
What does SMART stand for?
Specific
Measurable
Achievable
Realistic
Time-Bound
What “seven sins” should a good specification avoid?
Noise - element that does not carry relevant information
Silence - existence of a feature that is not covered
Over specification - element corresponds to a feature of the solution rather than the problem
Contradiction - two elements define a feature that contradicts each other
Ambiguity - an element can be interpreted in multiple ways
Forward reference - element uses features not defined until later in the document
Wishful thinking - element defines feature that cannot realistically be validated
