Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Software Engineering > Requirements Engineering > Flashcards

Requirements Engineering Flashcards

1
Q

What is requirements engineering?

A

The process of understanding and defining the characteristics of a software system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What does the requirements engineering cover?

A

Must have features.
Restrictions.
Cost-benefit analysis.
Risk analysis.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are requirements?

A

Descriptions of a system’s services and constraints generated during the requirements engineering process.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Level of detail of requirements engineering.

A

Client/user: broad levels of detail.

Developers: big levels of detail.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Requirements engineering activities:

A

Feasibility study.
Requirements elicitation and analysis.
Requirements specification (document)
Requirements validation.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are functional requirements?

A

Statements about the services that will be provided, how the system responds and system behaviour.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are non-functional requirements?

A

Statements about the limitations of services/functions provided by the system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Describe domain requirements.

A

They reflect the environment in which a system works; are specific requirements according to a system’s field.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What are the metrics for non-functional requirements?

A

Speed, size, ease of use, reliability, robustness and portability.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is the software requirements document?

A

Official statement of what is required of the system developers. It is not a design document.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What must the SRD have?

A 
Preface
Introduction
Glossary
User requirements definition.
System architecture.
System requirements specification.
System models.
System evolution.
AppendiceIndex
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are some common activities between different requirements engineering process?

A

Elicitation
Analysis
Validation
Management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Describe the what iteration means on the Elicitation and analysis

A

Specification-Discovery-Classification and organisation-Priorization and negotiation.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Some key ideas of validation:

A 
Validity
Consistency: problems?
Completeness
Realism
Verifiability
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

How can you validate?

A

Through test cases or prototypes.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is the requirements management?

A

Process of managing requirements during the requirements engineering process and system development. “The understanding of the problem changes, so the requirements change as well”

17
Q

What is planning on requirements management?

A

Establishes the levels of requirements management detail that is required.

18
Q

Planning activities?

A

Requirements identification
Change management process
Traceability policies
Tool support

Software Engineering (2 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions