COSYSMO Workshop
Outbrief
CSSE Annual Research Review
Los Angeles, CA
Mon March 16 & Tues March 17, 2009
Ricardo Valerdi
Attendees (11)
•
•
•
•
•
•
•
•
•
•
•
Mauricio Aguiar, TI Metricas
Barry Boehm, USC
Jared Fortune, USC
Peter Hantos, Aerospace Corp
Dan Ligett, SoftStar Systems
Ray Madachy, Naval Postgraduate School
Miles Nesman, Boeing
Beth O’Donnell, Boeing
Stan Rifkin, Master Systems
Garry Roedler, LMCO
Ricardo Valerdi, MIT
Agenda
• Leading Indicators update (Roedler)
• COSYSMO reuse (Fortune)
• COSYSMO for Human Systems Integration
(Valerdi)
• Expert COSYSMO (Madachy)
Deferred
• Harmonization of SysE and SwE
Take-aways (1 of 4)
Leading Indicators (Roedler)
Sources of
ignition
Smoke
detectors
Fire
alarms
Fires
Engineering
Capability
Engineering
Performance
Engineering
Status
Financial
Indicators
Estimate with uncertainty
£
*
Mar
Apr
May
Jun
Jul
Aug
Sep
S
W
BC P
W
AC WP
BC
Oct
Time
Causes
Need to monitor
drivers and pull
control levers
Consequences
Performance
not meeting
plans
Product not
maturing fast
enough
Behind
schedule,
unpredictable
Take-aways (2 of 4)
COSYSMO Reuse (Fortune)
Identify reuse strategy
Identify reuse artifacts
Reuse
intangibles
Define classes of reuse
Size
drivers
Cost
drivers
Risk assessment
Document future reuse
opportunities
Populate reuse
repository
Will be discussed
in detail
Take-aways (3 of 4)
COSYSMO for Human Systems Integration (Valerdi)
Environment—the conditions in and around the system and
the concepts of operation that affect the human’s ability to
function as a part of the system as well as the requirements
necessary to protect the system from the environment.
Manpower—the number and mix of
personnel (military, civilian, and
contractor) authorized and available to
train, operate, maintain, and support each
system.
Survivability—the ability of a system, including
its operators, maintainers and sustainers to
withstand the risk of damage, injury, loss
of mission capability or destruction.
Habitability—factors of living and working
conditions that are necessary to sustain the
morale, safety, health, and comfort of the user
population that contribute directly to personnel
effectiveness and mission accomplishment, and
often preclude recruitment and retention
problems.
Occupational Health—the consideration of design
features that minimize risk of injury, acute and/or
chronic illness, or disability, and/or reduce job
performance of personnel who operate, maintain, or
support the system.
Personnel—the human aptitudes, skills, and
knowledge, experience levels, and abilities
required to operate, maintain, and support a
system at the time it is fielded.
Training—the instruction and resources
required providing personnel with
requisite knowledge, skills, and abilities
to properly operate, maintain, and
support a system.
Human Factors Engineering—the comprehensive
integration of human capabilities and limitations into
systems design, to optimize human interfaces to
facilitate human performance in training operation,
maintenance, support and sustainment of a system.
Safety—hazard, safety and risk analysis in system design and
development to ensure that all systems, subsystems, and their
interfaces operate effectively, without sustaining failures or
jeopardizing the safety and health of operators, maintainers and
the system mission.
Take-aways (4 of 4)
•
•
•
•
•
Expert COSYSMO (Madachy)
Program size may not be a predictor of risk
• Possible proxy: cost driver ratings that demonstrate
relative complexity
“Dominance” effect introduces show-stoppers
• High Level of Service Requirements paired with
anything is a risk
Low Documentation may be worse than high
documentation from a risk standpoint
Risk prioritization is difficult to generalize
Some mitigation strategies can address multiple risks
(risk prioritization criteria?)
• Hiring the right expertise
• Investing in knowledge management