lesson 8 Flashcards

1
Q

describe the characteristics of the final deliverable in ordinary non-technical language.

A

Functional requirements

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

specify criteria that can be used to judge the final product or service that your project delivers.

A

Non-functional requirements

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

restrictions or constraints to be placed on the deliverable and how to build it.

A

Non-functional requirements

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

Their purpose is to restrict the number of solutions that will meet a set of requirements.

A

Non-functional requirements

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

Three types of general non-functional development constraints?

A
  1. Time
  2. Resource
  3. Quality
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

When a deliverable should be delivered

A

time

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

How much money is available to develop the deliverable

A

Resource

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

Any standards that are used to develop the deliverable, development methods, etc.

A

Quality

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

emerge from the functional requirements to answer the
questions: how will the problem be solved this time and will it be solved technologically and/or procedurally?

A

Technical Requirements

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

are the needs of the sponsoring organization, always from a management perspective.

A

Business requirements

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

are usually expressed in broad outcomes, satisfying the business needs, rather than specific functions the system must perform.

A

Business requirements

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

These requirements grow out of the vision for the product that, in turn, is driven by mission (or business) goals and objectives

A

Business requirements

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

requirements describe what the users need to do with the system or product.

A

User Requirements

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

can be internal or external and are usually non-negotiable.

A

Regulatory requirements

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

They are the restrictions, licenses, and laws applicable to a product or business that are imposed by the government.

A

Regulatory requirements

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

is a property that must be exhibited by software developed or adapted to solve a particular problem.

A

software requirement

16
Q

As a practical matter, it is typically useful to have some concept of the volume of the requirements for a particular software product.

A

Measuring Requirements

17
Q

The project manager gathers initial project facts from the project charter.

A

Scope Inputs

18
Q

is part of scope definition, and it can be done using one or
more of following techniques

A

Gathering requirements

19
Q

Attributes associated with each requirement can be recorded in the requirements traceability matrix.

A

Requirements Traceability Matrix

20
Q

describes the products or services to be delivered by the project and how they are decomposed and related. It is a deliverable-oriented decomposition of a project
into smaller components. It defines and groups a project’s discrete work elements in a
way that helps organize and define the total work scope of the project.

A

Work Breakdown Structure (WBS)

21
Q

details the project deliverables and describes the major objectives.

A

Scope Statement