Software Engineering and Requirements Engineering

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/16

flashcard set

Earn XP

Description and Tags

Flashcards covering essential vocabulary and concepts in software engineering and requirements engineering.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

17 Terms

1
New cards

Team Formation - Stage 1: Forming

Introductions; consensus on purpose; best behavior; potential clique formation; emergence of team leader.

2
New cards

Team Formation - Stage 2: Storming

Painful stage of role negotiation; competition and conflicts arise; communication and goal setting are essential.

3
New cards

Team Formation - Stage 3: Norming

Members collaborate; creativity increases; leaders become facilitators; roles defined with fluid boundaries.

4
New cards

Team Formation - Stage 4: Performing

Effective behavior patterns prevail; team achieves more; capability to prevent/work through problems.

5
New cards

Requirements Engineering

A systematic and disciplined approach to specifying and managing requirements to understand stakeholders' needs.

6
New cards

Four Major Tasks of Requirements Engineering

Eliciting, analyzing/documenting, validating, and managing/evolving requirements.

7
New cards

What is the relationship between effort and risk in Requirements Engineering?

In Requirements Engineering, as effort increases in gathering and analyzing requirements, the risk of misunderstandings and project failure decreases.

8
New cards

Functional Requirements

Requirements concerning a result or behavior that a system must provide.

9
New cards

Quality Requirements

Requirements related to quality concerns; specifies criteria for judging system operation.

10
New cards

Maintainability Constraints

Requirements limiting the solution space beyond functional and quality requirements.

11
New cards

Stakeholder

A person or organization that influences or is impacted by a system's requirements.

12
New cards

Elicitation

The process of asking questions and gathering information from stakeholders to determine their goals and requirements.

13
New cards

Context Diagrams

Diagrams representing a system's environment, including external entities and data flows.

14
New cards

Onion Model

A layered model illustrating different systems and their environments, from product to wider stakeholder context.

15
New cards

Rich Picture

Graphical representation showing stakeholders and their relationships, with primary concerns illustrated.

16
New cards

Effective Elicitation Practices

Engaging in activities to discover system requirements that prioritize stakeholder satisfaction.

17
New cards

Validation of Requirements

Ensuring that each documented requirement meets the needs of stakeholders.