Term
| user requirements and system requirements |
|
Definition
User requirements: are statements, in a natural language plus diagrams of what services the system is expected to provide to system users.
System Requirements: are more detailed descriptions of the software system's functions, services and operational constraints. |
|
|
Term
| What is the distinction between functional and non-functional requirements? |
|
Definition
Functional- specifies what the system or application should DO.
Non-functional- specifies how the system or app should BE. |
|
|
Term
| Give two or three examples of non-functional requirements |
|
Definition
Portability- the effort required to move software to a diff target platform.
Legal- there may be legal issues involving privacy of information
Performance requirements- about resources required, response time etc.
ease of use
reliability |
|
|
Term
| What is a software requirements document? |
|
Definition
| Is an official statement of what the system developers should implement. Should include both user reqs and detailed specs of the system requirements. |
|
|
Term
| What are the stages of the requirements engineering process? |
|
Definition
1. Feasibility study
2. Requirements Analysis
3. Requirements Specification
4. Requirements validation |
|
|
Term
| Give several reasons why it is difficult to elicit requirements? |
|
Definition
1. Stakeholders often do not know exactly what kind of system/services they want.
2. Stakeholders naturally express requirements in their own terms and therefore, requirement engineers should be able to understand these requirements.
3. Different stakeholders have different requirements. Requirement engineers have to consider all potential sources of requirements and discover commonalities and conflicts.
4. Political factors may affect the requirements of the system.eg: managers may demand specific system requirements.
5. The economic and business environment is very dynamic where analysis takes place, therefore, new requirements may be required in the future. |
|
|
Term
|
Definition
| A scenario is a description of example interaction sessions. (No more than a few.) Includes what user and system expect at the start, the normal event flow, what can go wrong, what other activities can be happening, and the system state at the end. |
|
|
Term
|
Definition
| A requirements discovery technique that identifies the actors involved in an interaction, names the type, and describes the interaction with the system p106 |
|
|
Term
| What is ethnography and how is it used in the requirements engineering process? |
|
Definition
Deriving requirements by observing operational processes, how people work alone and together. It’s used to complement other approaches, like use case analysis or prototyping, by revealing 2 critical requirements that other elicitation techniques miss:
those derived from the way people actually work (one type of process detail)
those derived from how people cooperate (another type of process detail) |
|
|
Term
| What are three requirements validation techniques? |
|
Definition
1. Requirements reviews
2. Prototyping
3. test-case generation |
|
|
Term
| What are the stages of the requirement change management process? |
|
Definition
(a) Problem analysis and change specification
(b) Change analysis and costing
(c) Change implementation |
|
|
