Baselines Flashcards

1
Q

True or false: System Changes are inevitable.

A

True

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

Define a system baseline:

A

A complete system description including all update requirements, designs, constraints, assumptions, interfaces, resource allocations, and general team member responsibilities.

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

True or False: This class is really boring.

A

True :D

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

True or False: the following are milestone reviews - SDR, PDR, CDR, ORR

A

True

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

True or False: A baseline is not typically established at a milestone review.

A

False

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

____ Ensure that a project matures at an approximate constant rate.

A

Baselines

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

True or False: If one subsystem matures faster than others, less rework will have to be done than if all subsystems mature together.

A

False, subsystems should mature together.

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

True or False: Integrated program management synchronizes affordability, schedule, risk management, and others.

A
True:
Synthesizes-
Reqs
Design
Affordability
Schedule
Risk
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Name the 5 Aspects of a baseline:

A
  1. Reqs
  2. Design
  3. Affordability
  4. Schedule
  5. Risk
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

True or False: configuration management is the tracking of all requirements while hardware is built/coded.

A

True

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

Name some reasons for requirements to change:

A
  1. System design maturing causes reallocation
  2. New requirements displace others
  3. Stakeholders are bitching about stuff
  4. Performance is lacking
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Name some reasons for configurations to change:

A
  1. Build not equal to design

2. Something breaks during test ==> redesign/reallocation

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

True or False: Lower level requirement changes are taken care of first.

A

False, Higher level reqs must be taken care of first

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

ECR

A

Engineering Change Request

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

_ _ _ Review and assess the impact of ECRs( Engineering Change Requests)

A

CCB

Change Control Boards (fukxing bureaucrats right?)

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

True or False: the earlier a change is proposed, the more expensive the total cost will be.

A

False.

The later the worse

17
Q

True or False: system baselines are updated at FIVE major milestone reviews.

A

True

SDR, PDR, CDR, FRR, ORR

18
Q

SDR

A

System Definition Review

19
Q

PDR

A

Preliminary Design Review

20
Q

CDR

A

Critical Design Review

21
Q

FRR

A

Flight Readiness Review

22
Q

ORR

A

Operational Readiness Review

23
Q

True or False: A baseline will be established at the PFAR (post-flight assesment review)

A

False
Baselines established at:
SDR, PDR, CDR, FRR, ORR

24
Q

True or False: A baseline will be established at the ASM (Aquisition strategy meeting)

A

False
Baselines established at:
SDR, PDR, CDR, FRR, ORR

25
Q

True or False: A system baseline will be established at the MCR (Mission Concept Review)

A

False
Baselines established at:
SDR, PDR, CDR, FRR, ORR