University of Southern California
Center for Systems and Software Engineering
Barry Boehm, Roberta Gleiter,
Gary Hafen, DeWitt Latimer,
Rich Turner
Gary Thomas, Glenn Berg
February 13, 2007 ©USC-CSSE 1

University of Southern California
Center for Systems and Software Engineering
A.
Taxonomy of software project contract efforts
B.
Study of successful contracts to find commonalities in software projects
C.
Top acquisition risk list (acquirer/contractor point of views)
D.
Inventory current acquisition practices on acquirer and contractor sides
E.
Map risks to practices to determine coverage and gaps in practice
F.
Quantify the impact/cost of the turn-over of acquisition personnel
G.
Look at acquisition risks – do a risk model of what we learn.
H.
Develop fault tree analysis of to know the probability of success of the program at a given point
I.
Tool that help you quantify s/w (or system) opportunities and risks over time and impact of missing these
J.
Do something like “100 Questions for Technical Review” for software intensive systems acquisition
K.
How often do our acquisition re-use based assumptions work out?
L.
Is amount of code a part of complexity for acquisition?
M.
Macro risk project tool – evolve and pilot
N.
How would an acquisition organization write an acquisition strategy for a development based on MBASE and incremental commitment
Blue – High Value/High Difficulty Green – High Value/Low Difficulty
February 13, 2007 ©USC-CSSE 2

Opp A
Opp B
Opp C
Opp D
Opp E
Opp F
Opp G
Opp H
Opp I
Opp J
Opp K
Opp L
Opp M
Opp N
University of Southern California
Center for Systems and Software Engineering
Research Opportunities
10
5
0
0
C
A
L
D
K
M
E
G
B
N
J
F
H
I
5
Difficulty of Research
10
February 13, 2007 ©USC-CSSE 3

University of Southern California
Center for Systems and Software Engineering
• MBASE to a standard format (for injection into standards bodies)
• Write a standard around the Incremental
Commitment Model
February 13, 2007 ©USC-CSSE 4