• Requirements Management

Question 1

Requirements Management: Core Tasks

Answer 1

▪ Rationale Management and Traceability:
* Justification of requirements
* Linking requirements to each other and to development artifacts
▪ Requirements Management:
* Structuring, documentation and archiving
* Attribution
▪ Interactions with other management tasks:
* Validation and verification
* Change management including impact analysis
* Version management
* Configuration Management
* Claim Management
* Support for distributed RE

Question 2

Elementary Attributes: Priority and Acceptance Criterion

Answer 2

Priority:
▪ Not always all requirements can be implemented and usually not all requirements are equally
important
→ Prioritization of requirements

Acceptance Criterion:
▪ It is not always possible to clearly evaluate and check all requirements, or to decide during
acceptance when the implementation of the requirement was appropriate from the perspective of
the stakeholders
→ Acceptance criterion defines criteria under which the implementation of the requirements is
considered valid

Question 3

Procedure for handling corrections regarding requirements according to their specification:

Answer 3

Apply -> Rate -> Decide -> Realize

Question 4

Objectives of change management for requirements

Answer 4

▪ Systematic and controlled recording of change requests
▪ Evaluation of change requests (sense and effort, risks etc.)
▪ Decision on the implementation of the changes
▪ Implementation of the changes

Question 5

Establishment of Change Management

Answer 5

Define a change process
Create responsibilities and a change control board
Creation of a change database that supports the change process

Question 6

what are Quality Gates

Answer 6

Quality Gates are quality measurement points

Question 7

Constructive Quality Assurance

Answer 7

Elicitation Techniques, Specification Techniques
(Standards, Processes), Prototyping

Question 8

Analytical Quality Assurance

Answer 8

Dynamic Techniques, Static Techniques

Question 9

Smells in Requirements

Answer 9

Smell detection is used for manual and automatic quality assurance
▪ Problem: Issues in requirements, such as ambiguities or incomplete requirements specifications,
can lead to time and cost over-run

Question 10

Why NLP? Common errors in specifications

Answer 10

Textual specifications are fundamental for SW development processes
Yet (remember user stories as an invite to converse)
* Often bad quality due to using natural language
* Problems: Inherent ambiguities, inconsistencies, etc.

Question 11

Quality model for specifications

Answer 11

atomicity
unambiguity
conciseness
testability
traceability
consistency
formal correctness