III. Requirements as the Foundation of Software

Question 1

How do requirements constitute the foundation of software? (2)

Answer 1

3-4

Question 2

main goals of Requirements Definition: characterize the target system in terms of (4) –> be sufficiently (5)

Answer 2

3-6

Question 3

Typical roles involved in Requirements Definition (5)

Answer 3

3-7

Question 4

Artifacts produced during Requirement Definition (3)

Answer 4

3-8

Question 5

what is System Glossary and its goal? Guidelines (3)

Begriffslexikon / Domänenlexikon

Answer 5

3-9

Question 6

Requirements Specification: 2 types + what does it focus on? (4)

Answer 6

3-10

Question 7

• what do Requirements in Engineering define? (3)
• distinguish Functional and Non-functional requirements
• classification (3)

Answer 7

3-14

Question 8

Principles for Requirements: MuSCoW, SMART

Answer 8

3-18, 19

Question 9

• how do Requirements Specification work?

- what are typical artifacts? (4)

Answer 9

3-24

Question 10

5 properties of a (good) requirements specification

Answer 10

3-25

Question 11

Kanomodell + draw

Answer 11

3-29

Question 12

Requirements Elicitation: sources, typical methods (3)

Answer 12

3-28

Question 13

why is Modeling in Requirements Engineering important?

Answer 13

3-31

Question 14

how is the target system seen during context analysis?

Answer 14

3-32

black box

Question 15

how is modeling interfaces and data flows based on? (2)

draw

Answer 15

3-34

Question 16

how is modeling actors and use cases based on? (3)

• what can actors be?
• how to display domain function?
• how to display interaction?

Answer 16

3-35

Question 17

Characterization of Actor:

• what does an Actor represent?
• the interaction actor - actor, actor - target system

Answer 17

3-36

Question 18

• Characterization of Use Case / Business process / workflow (Anwendungsfall) –> what does it represent? What does it typically consist of?
• what is irrelevant in the set of use cases? (2)

Answer 18

3-37

Question 19

• What is Use Case scenario? What is mandatory?

- does use case need to select all in the set of events and actions associated with it?

Answer 19

3-39, 40

Question 20

• what should we do when a short description is not enough?

- Are use case description templates standardized?

Answer 20

3-41, 42

Question 21

Suggestion of Use Case Scenario Template elements (8)

Answer 21

3-42, 43

Question 22

Modeling Requirements with Use Cases –> what do we do? (4)

Answer 22

3-47

Question 23

• Main goals of UML Use Case Diagrams (3)

- what does it display? Nodes (3), Edges (3) –> Draw

Answer 23

3-49, 50

Question 24

• (Relationships between Use Cases) what is Include?
• A include B –> meaning?
• Draw

Answer 24

3-52, 55

Question 25

• (Relationships between Use Cases) what is Extend?
• B extend A –> meaning?
• Draw

Answer 25

3-53, 55

Question 26

• (Relationships between Use Cases) what is gen / spec?
• B is-a A –> meaning?
• relationship specialized use case - original use case
• substitution principle

Answer 26

3-54

Question 27

when are exceptions and particularities added?

Answer 27

3-60

Question 28

Requirements Management - Anforderungsmanagement

• why is it needed?
• managing requirements (4)

Answer 28

3-63, 64

Question 29

what does Requirements Traceability serve?

what is bidirectional traceability?

Answer 29

3-66