chapter 13 Flashcards

1
Q

A method to track requirements through the development lifecycle to manage changes and verify alignment with goals.

A

requirements traceability

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

Why is traceability important for scope management?

A

It ensures functional requirements are linked to business needs, prevents scope creep, and avoids gaps in fulfilling customer needs.

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

They describe the behaviors or actions a system must perform, including interactions and compliance with standards.

A

functional requirements

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

Conditions describing the system’s environmental constraints, such as performance, security, scalability, and legal compliance.

A

quality of service (non-functional) requirements

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

What are assumptions and constraints in project development?

A

Constraints
Assumptions

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

Beliefs assumed to be true but not yet confirmed.

A

Assumptions

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

Limitations or restrictions on solutions.

A

Constraints

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

A tool that links one set of elements (e.g., requirements) to another (e.g., test cases or designs).

A

traceability matrix

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

What are the key elements of quality requirements?

A

Reliability, maintainability, scalability, security, disaster recovery, and usability.

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

Requirements structured with clear elements like event/condition, subject, action verb, object, rules, and outcomes.

A

well-formed requirements

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

Name the three types of traceability information.

A

Source: Origin of the requirement.
Rationale: Business goal the requirement satisfies.
Requirements: Interrelations among requirements.

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

List the key attributes of functional requirements.

A

Behavior or operation.
Desired effects within the problem domain.
Interaction methods with the solution.

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

Constraints from external conditions, such as legal rules or cultural differences.

A

environmental requirements

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

Name three types of interface requirements.

A

Hardware interfaces.
Software interfaces.
Communication interfaces.

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

A list defining terms with specific meanings for the organization or project.

A

glossary

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

Plans for increasing the system’s capacity to accommodate growth.

A

scalability requirements.

12
Q

What is the purpose of diagrams in requirements documentation?

A

Show relationships between entities.
Depict event sequences.
Visualize physical locations of solution components.

13
Q

The ease of implementing future changes to the solution.

A

maintainability

14
Q

Guidelines to secure the system against catastrophic failures and data loss.

A

failure and disaster recovery requirements

15
Q

Specifications for preventing loss, damage, or harm resulting from system use.

A

safety requirements

16
Q

Constraints on the distribution of personal information, requiring consent from the parties involved.

A

privacy requirements

16
Q

Define how the system will function in terms of user interactions, access, and acceptable downtime.

A

operational requirements

17
Q

Specifications to restrict access, monitor sensitive data, and ensure protection of information.

A

ecurity requirements

17
Q

Define information that the system must produce for external agencies, even if not needed for daily operations.

A

audit requirements

18
Q

Address the system’s ability to operate across multiple cultures or nationalities.

A

globalization and localization requirements

19
Q

What are the main attributes of quality requirements?

A

Designability
Reliability
Usability
Scalability
Maintainability

20
Q

Describe how the system handles catastrophic failures and recovers data.

A

failure and disaster recovery requirements

21
Q

A template that combines text, tables, and diagrams to express requirements comprehensively

22
Q

matrix

A

A structured table used to convey complex, uniform sets of requirements.

23
Q

Indicate how much information the system must process within a specified timeframe.

A

performance requirements

24
Q

Specifications for interactions between the system and external hardware, software, or communication channels.

A

interface requirements

25
Q

External constraints, such as legal regulations, cultural differences, or physical conditions affecting the system.

A

environmental requirements

26
Q

Educational needs for stakeholders to effectively interact with the solution.

A

training requirements

27
Q

Unconfirmed beliefs presumed to be true during the project.

A

assumptions

28
Q

Limitations that restrict available options for solutions.

A

constraints