3 - Requirements Engineering

Question 1

Requirements Analysis

Answer 1

Negotiation + Evaluation + Prioritization + Consolidation of requirements

Question 2

Reasons to change Requirements

Answer 2

Internal Reasons (defects in requirements/insights/economic frameworks) + External Reasons (change requests/technical infrastructure/COTS)

Question 3

Tracing of Requirements is important for …

Answer 3

efficient and effective management of requirements and part of Requirements Management

Question 4

Change Management

Answer 4

Collect goals and requirements and decide later on final requirements

Question 5

Requirement Source

Answer 5

Source of the real world object justifying the requirement’s existence

Question 6

Use Case

Answer 6

describes (sub)function from a user perspective; illustrated with story boards or scenarios

Question 7

Requirements Artifact

Answer 7

Requirements in documented form

Question 8

Stakeholder

Answer 8

Person that is interested in System Under Development (SUD)

Question 9

Solution Oriented RE

Answer 9

system specification and description of the required (non-)functional requirements

Question 10

Time Boxing

Answer 10

realize as many requirements as possible with given budget and time frame

Question 11

Problem Oriented RE

Answer 11

specification and description of the intention that is related with the development // detailed requirement specification

Question 12

Product Requirements Document

Answer 12

contains all requirements from customer perspective with respect to delivery and service (vague/implicit/conflicting)

Question 13

Architectural Design

Answer 13

determines controllability of a system from a developers point of view (derived from requirements)

Question 14

Use Case Specification

Answer 14

general description; define primary users; specification of objectives/postconditions/assumptions/preconditions

Question 15

Functional View

Answer 15

functional specification for each function (interface/dependency)

Question 16

Success Principles

Answer 16

detect failure (prevent cost explosion) - avoid unstable/wrong requirements - clear requirements

Question 17

Functional Specifications Document

Answer 17

detailed requirements for devs. Requirements are complete/unambiguous and testable (detailed/consistent/measurable)

Question 18

Requirements Engineering

Answer 18

Iterative and systematic approach to create requirements and system specification together with stakeholders + basis for development

Question 19

Rational

Answer 19

explains and justifies the need of a requirement

Question 20

Types Of Requirements

Answer 20

Traditional System Analysis: Structured System Analysis // Phase-Related Requirements Engineering: RE as development process phase // Continuous Requirements Engineering: RE as a task over different projects

Question 21

We distinguish between _______________ and _______________ form.

Answer 21

external (syntax) and internal form (semantic)

Question 22

V&V

Answer 22

Checking of the quality of requirements together with stakeholders

Question 23

Requirements Specification

Answer 23

Documentation + Modeling + Structuring

Question 24

Specification Documents are the basis for …

Answer 24

contract design + coordination between stakeholders + implementation and integration + future extensions

Question 25

Process Of Requirements Engineering

Answer 25

Include relevant informations - collect and structure goals - derive requirements - work out alternatives - document requirements & capture details

Question 26

Requirements Elicitation

Answer 26

Defining goals and collecting requirements