“COSYSMO for Human Systems Integration”
COSYSMO Workshop
Kevin Liu
MIT Graduate Research Assistant
Advisors: R. Valerdi and D. Rhodes
Center of Systems and Software Engineering Annual Research Review
March 8-11 2010
Motivation-What is HSI?
HSI requirements include, but
are not limited to, any
requirement pertaining to one or
more domains of HSI, or the
integration of those domains.
Broadly, the term encompasses
any requirement that contributes
to the integration of human
considerations into the system
being developed.
seari.mit.edu
© 2009 Massachusetts Institute of Technology
2
Motivation-Economics of HSI
Human factors. Human factors engineering principles
Shall's+Will's+Must's
Shall’s + Will’s + Must’s
450
400
350
300
250
200
150
100
50
0
H
S
I
such as specified in MIL-STD-1472 shall be employed
in each XXX system solution (Threshold = Objective).
} <-“hard”
} <-“nominal”
}
MQ-1 Orig
seari.mit.edu
MQ-1
Update
<-“easy”
C-130J
RQ-4
© 2009 Massachusetts Institute of Technology
3
Motivation-Early Cost
Estimation
refinements
Inputs:
# of Requirements
Outputs:
(1) cost estimate
(2) requirements analysis
Adapted from Air Force HSI
Office (2009). Human Systems
Integration Requirements
Pocket Guide.
seari.mit.edu
© 2009 Massachusetts Institute of Technology
4
Workshop Overview
Research Question: What is the impact of HSI requirements on
Systems Engineering effort?
seari.mit.edu
© 2009 Massachusetts Institute of Technology
5
Workshop Overview
Research Question: What is the impact of HSI requirements on
Systems Engineering effort?
Methodology:
-10 Requirements from HSI Requirements Pocket Guide, Air
Force HSI Office
- Comparison to a “nominal” or “1x” requirement
- 3-round Delphi method
seari.mit.edu
© 2009 Massachusetts Institute of Technology
6
Workshop Overview
Research Question: What is the impact of HSI requirements on
Systems Engineering effort?
Methodology:
-10 Requirements from HSI Requirements Pocket Guide, Air
Force HSI Office
- Comparison to a “nominal” or “1x” requirement
- 3-round Delphi method
Contributions:
-Share information about perception of HSI
- Validation of estimation methodology
- Initial quantifiable estimate of HSI’s impact on Systems Engineering
seari.mit.edu
© 2009 Massachusetts Institute of Technology
7
Methodology
Example of a nominal requirement
Threshold: Operators shall be able to read the XX display (where XX is the
system being designed) during day and night, with no visible signature at night
from 10-50m. Device must enable operators to keep head up while reading data
on computer.
1x
2x
4x
8x
- JROC-approved requirements
- CDD/CPD – level requirements
- System information redacted
- Assumptions about system addressed during discussion
seari.mit.edu
© 2009 Massachusetts Institute of Technology
8
Methodology
Round 1: Individual ratings
Round 2: Discuss individual results anonymously
Adjust ratings as necessary
Round 3: Discuss Round 2 results anonymously
Adjust ratings as necessary
seari.mit.edu
© 2009 Massachusetts Institute of Technology
9
Methodology
Round 1: Individual ratings
Round 2: Discuss individual results anonymously
Adjust ratings as necessary
Round 3: Discuss Round 2 results anonymously
Adjust ratings as necessary
During discussion, consider:
-Assumptions
-Interpretation of language
-Interpretation of effort units
-Individual expertise
seari.mit.edu
© 2009 Massachusetts Institute of Technology
10