Unit 2 Flashcards
The process of reaching and documenting an agreed set of requirements is known as ____________ ___________ .
requirements engineering
____________ are individuals and/or organisations affected by the success or failure of a software system
stakeholders
The requirements for a system effectively form a ________ between the client and the developers
contract
________ are specific sequences of actions that illustrate how a task can be performed. They can be used to investigate dependencies between requirements.
scenarios
There are four activities that can be identified as common to many requirements engineering processes. They are:
requirements elicitation
requirements analysis and negotiation
requirements documentation
requirements validation
Requirements ___________ is the activity concerned with identifying the requirements
elicitation
Requirements ________ and ___________ is the activity where requirements are categorised, prioritised and examined for their properties of consistency, completeness and ambiguity
analysis and negotiation
Requirements _____________ is usually done through a template document
documentation
Requirements __________ consists of a careful check of the overall requirements documentation, usually following a checklist of questions
validation
Where and when does the requirements engineering process take place in an iterative and incremental development process?
The main output of a requirements engineering process is the contract, therefore it has to take place early in the development process, however, iterative and incremental processes recognise that requirements may be revisited in parallel with other phases of development
How do requirements and stakeholders related to each other?
Requirements arise from stakeholders’ needs
What are the benefits of documenting requirements within a project?
Requirements record decisions
They are the main reference for what should be built
They are the basis for validation of the built system
What is an agile approach to requirements engineering documentation?
Requirements documentation should serve as a vehicle for common understanding, communication and future traceability.
What is a functional requirements?
A functional requirement describes an action that the product must take if it is to carry out the work it is intended to do
What is a non-functional requirement
A non-functional requirement is a requirement about a quality that the product must have