Introduction & Foundation Flashcards

1
Q

Define requirement (3)

A
  1. A condition or capability needed by a user to solve a problem or achieve an objective.
  2. A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed documents.
  3. A documented representation of a condition or capability as in 1 or 2.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Define stakeholder

A

A stakeholder of a system is a person or an organization that has an (direct or indirect) influence on the requirements of the system.

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

Define requirements engineering

A

Requirements engineering is a systematic and discplined approach to the specification and management of requirements.

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

Goals of requirements engineering (2)

A
  1. Knowing the relevant requirements, achieving a consensus among the stakeholders about these requirements, documenting them according to given standards, and managing them systematically.
  2. Understanding and documenting the stakeholders’ desires and needs, they specifying and managing requirements to minimize the risk of delivering a system that does not meet the stakeholders’ desires and needs.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

4 core activities of requirements engineering

A
  1. Elicitation
  2. Documentation
  3. Validation and negotiation
  4. Management
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Elicitation

A

During requirements elicitation, different technique are used to obtain requirements from stakeholders and other sources and to refine the requirements in greater detail.

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

Documentation

A

During documentation, the elicited requirements are described adequately. Different techniques are used to document the requirements by using natural language or conceptual models.

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

Validation and negotiation

A

In order to guarantee that the predefined quality criteria are met, documented requirements must be validated and negotiated early on.

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

Management

A

Requirements management is orthogonal to all other activities and comprises any measures that are necessary to structure requirements, to prepare them so that the can be used by different roles, to maintain consistency after changes, and to ensure their implementation.

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

Necessary capabilities requirements engineer (7)

A
  1. Analytic thinking
  2. Empathy
  3. Communication skills
  4. Conflict resolution skills
  5. Moderation skills
  6. Self-confidence
  7. Persuasiveness
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Functional requirement

A

A requirement concerning a result of behavior that shall be provided by a function of the system.

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

Quality requirements

A

A requirement that pertains to a quality concern that is not covered by functional requirements.

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

Examples functional requirements (3)

A
  1. functional
  2. behavioral
  3. data requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Examples quility requirements (5)

A
  1. Performance,
  2. availability,
  3. dependability,
  4. scalability or
  5. portability
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Constraint

A

A requirement that limits the solution spcae beyond what is necessary for meeting the given functional requirements and quality requirements.

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

System context

A

The part of the system environment that is relevant for the definition as well as the understanding of the requirements of a system to be developed.

17
Q

System boundary

A

Seperates the system to be developed from its environment; i.e. it separates the part of the reality that can be modified or altered by the development process from aspects of the environment that cannot e changed or modified by the development process.

18
Q

Requirement sources (3)

A
  1. Stakeholders
  2. Documents
  3. Systems in operation
19
Q

Categories Kano model (3)

A
  1. Dissatisfiers
  2. Satisfiers
  3. Delighters
20
Q

Disadvantage survey technique

A

Requirements engineer is in the lead. This might resultat in the fact that stakeholder concerns are forgotten, siperseded, or disregarded

21
Q

Survey techniques

A
  1. Interview

2. Questionnaire

22
Q

Disadvantage interview

A

Very time-consuming

23
Q

Advantage interview

A

Uncover subconsious requirements