Brainscape's Knowledge GenomeTM

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


See full index

Business Sarfaraz > Chapter 11 - Documenting and Managing Requirements > Flashcards

Chapter 11 - Documenting and Managing Requirements Flashcards

1
Q

What are three reasons for keeping good requirement documentation?

A

Communication

Validation

Further testing

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

What sections are included in a Requirements document?

A

Intro and Background

Business process models

Function models

Data model

Requirements catalogue

Glossary

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

What are the four types of requirement in a Requirements Catalogue?

A

General

Technical

Functional

Non-functional

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

What categories would fall into General in a Requirements Catalogue?

A

Business constraints

Business policies

Legal

Branding

Cultural

Language

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

What categories would fall under Technical in a Requirements Catalogue?

A

Hardware

Software

Interoperability

Internet

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

What categories would fall under Functional in a Requirements Catalogue?

A

Data entry

Data maintenance

Procedural

Retrieval

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

What type of categories would fall under Non-Functional in a Requirements Catalogue?

A

Performance

Security

Access

Backup and Recovery

Archiving and retention

Maintainability

Business Continuity

Availability

Usability

Accessibility

Capacity

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

What needs to be documented for a requirement?

A

Requirement Identifier

Requirement Name

Requirement Description
(User verb object)

Source

Owner

Author

Type of requirement

Priority

Business Area

Stakeholders

Associated non-functional requirements

Acceptance Criteria

Related requirements

Related documents

Comments

Rationale

Resolution

Version History

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

What is “Backwards from” traceability?

A

Origins of the requirement.

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

What is “Forwards to” traceability?

A

What happened to the requirement

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

What is vertical traceability?

A

Alignment with business values, strategy and objectives.

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

What are the six components of Requirements Management?

A

Requirements identification

Requirements cross-referencing

Requirements origin and ownership

Software support

Change control

Configuration management

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

What is Requirements identification?

A

Each requirement needs to be identified uniquely

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

What is Requirements cross-referencing?

A

Related requirements and documents should be cross-referenced to allow analyst to identify whether changing a requirement will impact other requirements.

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

What is Requirements origin and ownership?

A

Origin of the requirement.

The owner will need to make decisions about the requirement.

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

What is Configuration Management?

A

Controlling changes made to project deliverables such as documents.

17
Q

What sort of problems can occur without effective Configuration Management?

A

Difficulty in identifying latest version

Re-introduction of out of date requirements

Using wrong set of requirements for testing

18
Q

What is Configuration identification concerned with?

A

Defining which deliverables will be brought under configuration control

Identifier and version numbering scheme to be applied.

19
Q

What is Configuration control?

A

The version control process

20
Q

What possibilities are the for baselining during Agile development?

A

Baselining every prototype before demonstration

Baselining daily

Baselining at the end of a timebox

21
Q

What are the stages for Change Control?

A

Documenting the proposed change

Consulting the stakeholders

Deciding on the change

22
Q

What features can software support give to Requirements Management?

A

Documentation creation and storage

Secure storage and access

Documents linkage

Version numbering

Business Sarfaraz (14 decks)

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