COSYSMO Workshop

1. Kevin LiuMIT Graduate Research AssistantAdvisors: R. Valerdi and D. RhodesCenter of Systems and Software Engineering Annual Research Review March 8-11 2010 “COSYSMO for Human Systems Integration” COSYSMO Workshop

2. 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. © 2009 Massachusetts Institute of Technology

3. Motivation-Economics of HSI Human factors. Human factors engineering principles such as specified in MIL-STD-1472 shall be employed in each XXX system solution (Threshold = Objective). Shall’s + Will’s + Must’s } HS I <-“hard” } <-“nominal” } <-“easy” © 2009 Massachusetts Institute of Technology

4. Motivation-Early Cost Estimation refinements • Outputs: • cost estimate • requirements analysis Inputs: # of Requirements Adapted from Air Force HSI Office (2009). Human Systems Integration Requirements Pocket Guide. © 2009 Massachusetts Institute of Technology

5. Workshop Overview Research Question: What is the impact of HSI requirements on Systems Engineering effort? © 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 © 2009 Massachusetts Institute of Technology

7. 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 © 2009 Massachusetts Institute of Technology

8. 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 © 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 © 2009 Massachusetts Institute of Technology

10. 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 © 2009 Massachusetts Institute of Technology