Ch 4. Requirements Engineering Flashcards

1
Q

What is a requirement?

A

May range from a high level abstract statement of a service or of a system constraint to a detailed mathematical functional specification

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the types of requirements?

A
  • User requirements
  • System requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are user requirements?

A

Statements in natural language plus diagrams of services the system provides and its operation constraints

Written for customers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are system requirements?

A

A structured document setting out detailed descriptions of the system’s functions, services and operational constraints.

Defines what should be implemented so may be part of a contract between client and contractor

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Agile methods usually use __ requirements engineering and may express requirements as __

A
  • Incremental
  • User stories
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are functional requirements?

A

Statements of services the system should provide

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are nonfunction requirements?

A

Constraints on the services or functions offered by the system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What are domain requirements?

A

Constraints on the system from the domain of operation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

In principle requirements should be both __ and __

A
  • Complete
  • Consistent
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

In practice, because of system and environmental complexity, it’s impossible to produce a ___

A

complete and consistent requirements document

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

___ requirements may be more critical then __ reequipments

A
  • Non-functional
  • Functional
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are the nonfunctional classifications?

A
  • Product requirements
  • Organizational requirements
  • External requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are product requirements?

A

Specify the delivered product must behave in a particular way

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What are organizational requirements?

A

A consequence of organizationla policies and procedures

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What are external requirements?

A

Arise from factors external to the system and it’s development process

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is a goal?

A

A general intention of the user such as ease of use

17
Q

The process used for requirements engineering processes vary widely depending on?

A
  • The application domain
  • The people involved
  • The organization developing the requirements
18
Q

What are the generic activites common to all requirements engineering process?

A
  • Requirements elicitation
  • Requirements analysis
  • Requirements validation
  • Requirements managementq
19
Q

Requirements engineering is an __ activity

20
Q

What are the stages of requirements elicitation?

A
  • Requirements discovery
  • Requirements classification and organization
  • Requirements prioritization and negotiation
  • Requirements specification
21
Q

What is requirements discovery?

A

The process of gathering info about the required and existing systems and distilling the user and system requirements from this info

22
Q

What is ethnography?

A

A social scientist spends a considerable time observing and analyzing how people actually work

23
Q

What are scenarios and user stories?

A

Real life examples of how a system can be used

24
Q

What is a scenario?

A

A structured form of a user story

25
What is requirements specification?
The process of writing down the user and system requirements in a requirements document
26
What are structure specifications?
An approach to writing requirements where the freedom of the requirements writer is limited and requirements are written in a standard way
27
What is tabular specification?
Used to supplement natural language
28
When is using tabular specification useful?
When you have to define a number of possible alternative courses of action
29
What is the software requirements document?
The official statement of what is required of the system developers
30
What are requirements validation?
Concerned with demonstrating that the requirements define the system that the customer really wants
31
What do you need to check for in requirements checking?
- Validity - Consistency - Completeness - Realism - Verifiability
32
What are the requirements validation techniques?
- Requirements reviews - Prototyping - Test case generation
33
What are the requirement management decisions?
- Requirements identification - A change management process - Traceability policies - Tool support
34
What are the stages of deciding if a requirements change should be accepted?
- Problem analysis and change specification - Change analysis and costing - Change implementation