Software Engineering - Requirements Engineering

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

1/17

flashcard set

Earn XP

Description and Tags

Flashcards for reviewing software engineering requirements.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

18 Terms

1
New cards

Software Requirement

Specifies the business functions that the user will be able to perform using the system-to-be in different situations or contexts.

2
New cards

User requirements

High-level goals or business goals, rather than software requirements needed by the developer.

3
New cards

Requirements gathering

Helps the customer define what is required: what is to be accomplished, how the system will fit into the needs of the business, and how the system will be used on a day-to-day basis.

4
New cards

Requirements analysis

Refining and modifying the gathered requirements.

5
New cards

Requirements specification

Documenting the system requirements in a semiformal or formal manner to ensure clarity, consistency, and completeness.

6
New cards

User Stories

Used in agile methods and stated in terms of user’s goals and capabilities instead of system features; written by the customer or user, not by the developer.

7
New cards

Business Policies

Explicit identification of these is important for involving stakeholders in decision making and anticipating future changes.

8
New cards

Tools for Requirements Engineering (e.g., user stories, use cases)

Used for determining what the user needs and writing a description of what system will do.

9
New cards

Specification

Describe what the software-to-be will do at the interface.

10
New cards

Acceptance Tests

Assess the project success criteria and determine if requirements are met as expected; conducted by the customer throughout the project.

11
New cards

Size Points

Assigned to each user story in agile methods.

12
New cards

Velocity (Productivity)

Estimated from experience to help estimate work duration in agile methods.

13
New cards

To-Do List

A list of user stories prioritized by the customer in agile development.

14
New cards

Requirement Engineering Activities

Activities involved in a software project, including elicitation, documentation, specification, prototyping, analysis, review, agreement, and acceptance.

15
New cards

Requirement Analysis Tasks

The analysis of requirements consists of categorizing/clustering and prioritizing requirements.

16
New cards

VORD

Viewpoint-oriented requirements definition

17
New cards

Analytical Hierarchy Process (AHP)

Used for prioritizing requirements, involving pairwise comparisons.

18
New cards

Requirement Traceability

Important to track back after development and verify all requirements have been developed, tested, packaged, and delivered.