IPO Stuff Flashcards

1
Q

What do all the org project enabling processes take as an input?

A

All the organizational project-enabling processes take the organization strategic plan as an input

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

What is something important that LCMM’s activities include that you might forget?

A

Actually establishing a LCMM process

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

What are inputs and outputs for LCMM you might forget?

A

It gets a couple inputs from QM and the organization tailoring strategy from TLR. Its outputs go to MEAS (org process performance measures needs/data), and to Control (basically OPAs)

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

What inputs and outputs for INFRAM are ones you’d forget?

A

IFRAM gets infrastructure needs from both PM and PP. Its outputs (org. infrastructure and project infrastructure) to the organization and the project(s) are enablers to both.

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

What inputs and outputs of PM might you miss?

A

PM gets supply strategy from SUP (note there is no similar input from ACQ). It also gets project status reports from PAC. Distinct outputs are project direction to PP and PAC, org lessons learned to KM, project portfolio to PP/HRM.

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

What I/Os of KM might you miss?

A

KM has pretty predictable inputs and outputs. Key inputs are both org lessons learned from PM and project lessons learned from PAC; the key output is the KM system which is then an enabler.

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

What Tailoring IPOs might I miss?

A

Tailoring primarily takes the life cycle models from LCMM, and outputs both org and project tailoring strategies (LCMM and PP). The activity I’m most likely to forget is “Take due account of the life cycle structures recommended or mandated by standards.”

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

What ACQ actvities might I miss?

A
  • Establish and maintain an agreement
  • Monitor the agreement
  • Accept the product or service
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What ACQ I/Os might I miss?

A
  • Inputs : Acquisition need from PP and Enabling System Requirements from all the process on the bottom and right half of the V. You also get acquisition replies and acquired systems from SUP.
  • Outputs :
    • ​Acq strategy [PP]
    • Request for supply [SUP]
    • Acquisition agreement [Control]
    • Accepted System or system element [INT]
    • Acquisition payment [SUP]
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What SUP activities might I miss?

A
  • Establish and maintain an agreement
  • Execute the agreement
  • Deliver and support the product or service
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What SUP inputs might I miss?

A
  • Request for supply [ACQ]
  • Supply Payment [ACQ]
  • Validated system [VAL]
  • Disposed system [DISP]
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Which SUP outputs might I miss?

A
  • Supply strategy [PM]
  • Supply response [ACQ - Acquisition reply] and [PP]
  • Supply agreement [Control]
  • Supplied system [ACQ – Acquired system]
  • Supply report [PAC]
  • Supply record [KM]
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is a RM activity I may miss?

A

Manage the Risk Profile

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

What is it from all the the other life cycle processes that could be inputs into CM?

A

CIs generated by any other life cycle process

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

Where do major, specific outputs of the TM processes almost always go?

A

PAC

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

What might I miss about QA’s inputs?

A

None of them come from the technical processes, not even from verification or validation.

17
Q

Where do CRs from PAC go?

A

Into CM and INFOM

18
Q

What about life cycle concepts/constraints could I miss?

A
  • Life cycle concepts (i.e. operations concept, disposal concept, support concept) get developed in BMA (preliminary) and SNRD, and then serve as inputs to all technical processes thereafter.
  • Life cycle constraints are generated by technical processes on the bottom and right side of the V, and they are inputs to everything in the V “left” of the processes that generate them. They are worded in the outputs as X constraints where X is the name of the TP
19
Q

How does the RVTM trace through the life cycle?

A
  • Initial version gets created in SNRD
  • Updated in SRD
  • Then is an input to VER, where the final version of it comes back as an input to SRD
  • Final RVTM is an input into VAL
20
Q

Trace MOEs/MOPs/TPMs through the life cycle

A
  • Preliminary MOE needs/data get generated in BMA and finalized in SNRD
  • MOP needs and data are generated in SRD. Note: there are no preliminary MOPs
  • TPM needs and data are generated in a preliminary version in AD, finalized in DD.
  • MOE/MOP/TPM needs and data are all inputs into MEAS
21
Q

What are source documents?

A

Source documents are external documents relevant to the particular stage of procurement activity for the system of interest. Inputs into PP, BMA, and SNRD.

22
Q

What’s the trace for Project Constraints through the life cycle?

A

Project Constraints get generated by Project Planning, but are only inputs into BMA and SNRD

23
Q

How do the various traceabiities (e.g. design traceability, implementation traceability) evolve through the V?

A

In the left side and bottom of the V, traceabilities are bi-directional and generally from/to before/after. E.g. for IMPL: Design traceability (from the predecessor process) is an input to IMPL. Implementation traceability flow both back to DD and forward to INT.

24
Q

What is a key input from ACQ to INT?

A

Accepted system

25
Q

Where do all the strategy doc outputs from ACQ, SUP, and everything in the V go?

A

PP

26
Q

What else gets validated in Validation besides the system?

A

It includes validating the actual requirements, not just the system. Validated requirements is them an input to PAC and SNRD

27
Q

What are the standard controls?

A
  • Applicable laws/regulations
  • Project direction
  • Project control requests
  • Standards
  • Agreements
28
Q

What are the standard enablers?

A
  • Organizational policies, procedures, and standards
  • Organization infrastructure
  • Project infrastructure
  • Knowledge management system
29
Q

Where do project change requests come from and where do they go?

A

They may originate in any life cycle process, but they are outputted from PAC, thence to CM and INFOM

30
Q

What are PP I/Os I could miss?

A
  • Input : Supply response [SUP]
  • Input : QM corrective actions [QM]
  • Input : QA Plan [QA]
  • Input: Strategy docs from other TM and T processes. The exam questions may use something like “X Strategy” where X refers to a process
  • Output : SEMP
  • Output : Project constraints [BMA] and [SNRD]
  • Output : Acquisition need [ACQ]
31
Q

What is the trace of system functions through the life cycle?

A
  • They are identified in SNRD and defined (fleshed out) in SRD
  • They are then used by AD and DD
32
Q

What is the trace of interfaces through the life cycle?

A
  • System functional interfaces are identified in SRD.
  • They are then inputted into AD and AD outputs the preliminary definitions of these interfaces.
  • Then the preliminary interface definitions go to DD, where, they are completed/updated and then outputted as interface definitions
  • They are inputs into IMPL, INT, and VER
  • INT then will, potentially, flow back interface update identification to AD and DD.
33
Q

When are procedures generated by the technical processes and where are they used?

A
  • They are generated by the TPs on the right side of the V (excluding Operation)
  • They are inputs into PAC
34
Q

What do most (but not all) of the TPs do in their “manage” activity?

A

Provide baseline information for configuration management.