System Requirements Flashcards

1
Q

____ Capture the understanding of what is to be done (plural)

A

Requirements

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

Poor ____ are the single biggest problem for projects

A

Requirements

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

Requirements define:

A
  1. ‘What’ is to be done
  2. ‘How well’ it is to be done
  3. Under ‘what conditions’
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Requirements drive ______

A

everything

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

True or False: a requirement may be a contractually binding statements

A

True

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

True or False: a requirement can not be documentation of a problem space

A

False

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

True or False: A requirement can not be a method by which a team communicates

A

False

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

NASA Requirement Conventions:

A

Requirements are binding - SHALL
Facts or declaration - WILL
Goals/Non-Mandatory - SHOULD

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

NASA Requirement Don’ts:

A

DO NOT USE:

must, have to, ought to, etc

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

Types of Requirements: (list them)

A
  1. Functional
  2. Performance
  3. Constraints
  4. Verifications
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Define Requirement Type: Functional

A

Requirement which defines WHAT an item must do.

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

Define Requirement Type: Performance

A

Requirements which define and quantify HOW WELL an item must accomplish a task.

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

Define Requirement Type: Constraint

A

Requirements that capture operational, environmental, safety, or regulatory constraints (WHAT CONDITIONS)

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

Define Requirement Type: Verification

A

Requirements that capture how confidence will be established about the system performance in its intended environment.

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

Other types of requirements:

A
Stakeholder needs
System Reqs
Imposed Reqs (env.)
Interface Reqs
Regulation Reqs
Implementation Reqs (we can't ride flying carpets to the moon)
Verification Reqs
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Cost incurred _____ ______ over the system maturity period. (Increase/Decrease, Sharply, Gradually)

A

Increases Gradually

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

System-Specific Knowledge _____ ______ over the system maturity period. (Increase/Decrease, Sharply, Gradually)

A

Increases Gradually

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

Commitment to Technology Configuration, Performance, and Cost _____ ______ over the system maturity period. (Increase/Decrease, Sharply, Gradually)

A

Increases Sharply

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

Ease of change _____ ______ over the system maturity period. (Increase/Decrease, Sharply, Gradually)

A

Decreases Sharply

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

Design Disciplines _____ ______ over the system maturity period. (Increase/Decrease, Sharply, Gradually)

A

Increase Gradually

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

Systems Engineering _____ ______ over the system maturity period. (Increase/Decrease, Sharply, Gradually)

A

Decreases Gradually

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

True or False: requirements will not change due to understanding of difficulties.

A

False

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

True or False: reqs change when priorities change.

A

True

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

Name some places where requirements are derived:

A
Stakeholder disclosures
Goals/Objectives
Constraints/Assumptions
ConOPs
FOMs
PBS
WBS
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

System boundaries are _______ ______-

A

External interfaces

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

List the methods for decomposing requirements:

A
  1. Flow-down
  2. Allocation
  3. Derivation
27
Q

Define Requirement Decomposition Method: Flow-Down

A

Direct transfer from subsystem capabilities.

Example: power supply req of sat. system may be entirely flowed down to req of satellite’s solar power subsystem.

28
Q

Define Requirement Decomposition Method: Allocation

A

Quantitative apportionment of resources from higher to lower levels using the same unit of measure.
Example: 1000 kg spacecraft may allocate 200 kg, 500 kg, and 300 kg to its three respective subsystems.

29
Q

Define Requirement Decomposition Method: Derivation

A

Apportionment that is implementation specific.
Examples:
1. Launch vehicle propulsion will determine maximum payload mass.
2. Structural stiffness requirement (young’s mod) may be determined from natural frequency of launch vehicle.

30
Q

Once requirements are decomposed for all levels of the system, ____ is established to connect them.

A

Traceablility

31
Q

____ is used to analyse the impact of requirement/mission changes.

A

Traceability

32
Q

If the parent requirements are incomplete, incorrect, ambiguous, conflicting, or unverifiable, the children requirements will be ______ _______.

A

Progressively worse

33
Q

Define IDD:

A

Interface Definition Document: defines interfaces to existing systems

34
Q

Define IRD:

A

Interface Requirement Document: defines interfaces for two developing systems.

35
Q

What is an ICD?

A

Interface Control Document: Identifies the design solution for the physical interface (mechanical solutions & drawings)

36
Q

When a system is decomposed into smaller segments, _____ are created.

A

Interfaces

37
Q

Define a TBD Requirement:

A

To be decided req

38
Q

Define a TBR Requirement:

A

To be resolved req

39
Q

Good requirements are _ _ _ _ _

A

SMART

40
Q

SMART

A
S - Specific
M - Measurable
A - Achievable
R - Relevant
T - Traceable
41
Q

Name three mandatory characteristics of good requirements:

A
  1. Needed
  2. Verifiable
  3. Attainable
42
Q

True or False: requirements can address more than one thing.

A

False

43
Q

True or False: a specific requirement should only be understood in one particular way.

A

True

44
Q

State a good requirement format: (three words)

A

WHO SHALL WHAT

45
Q

These words are ________: flexible, lightweight, maximize, adequate, small, portable, easily

A

Unverifiable

46
Q

These words are ________: as appropriate, so on, but not limited to

A

Ambiguous

47
Q

True or False: A requirement addresses HOW to provide something.

A

False

48
Q

Why ask if a requirement is necessary?

A

To determine if we even need it.

49
Q

True or false, this is a good requirement: the lunar lander shall include an airlock.

A

False:

The lunar lander shall provide the capability to egress/ingress while maintaining pressure.

50
Q

True or false, this is a good requirement: The spacecraft shall have a lifetime of al least five years.

A

True

51
Q

True or false, this is a good requirement: The vehicle shall be safe in a minor crash.

A

False:

The vehicle shall meet all the safety requirements specified in the Safety Codes…

52
Q

True or false, this is a good requirement: The vehicle shall allow extra-vehicular activities during operations phase.

A

True

53
Q

Checklist for Requirements:

A
  1. Unambiguous?
  2. Free of unverifiable shit?
  3. Not implementation specific?
  4. Necessary?
  5. Free of operation description?
  6. Free of TBDs?
54
Q

True or False: A requirement can contain an operation description.

A

False
Ask: ‘Does the developer have control over this?’
‘is this a need the product must satisfy or an activity involving the product?’

55
Q

____ captures the motivation and assumptions of a requirement.

A

Rationale

56
Q

Rationale or Requirement?

The UAV Shall be able to hover

A

Requirement

57
Q

Rationale or Requirement?

over 99% of all US highway overpasses have a 14 foot clearance.

A

Rationale

58
Q

The ______, is the set of techniques preliminarily proposed to test system requirements.

A

Requirement Verification Plan

59
Q

True or False: When there are many operational scenarios, it is a good idea to choose the worst case scenario for your requirement verification plan.

A

True:
See DRM (ConOps and Scoping)
Design Reference Mission

60
Q

What three things does requirement VALIDATION address?

A
  1. If we have the correct problem definition
  2. Do our requirement accurately capture this problem
  3. Are our requirements SMART or stupid?
61
Q

Define SRR:

A

System Requirements Review

62
Q

True or False: Requirement validation takes place after the SRR (System Requirements Review)

A

False, it takes place before the SRR

63
Q

______ ______ is a process of ensuring that: the set of requirements is correct complete and consistent.

A

Requirement Validation

64
Q

True or False: The cost of reconciling undefined/corrupted requirements stays more or less constant as the project matures.

A

False. The cost increases dramatically.