human factors integration for modaf: needs and solution approaches anne bruseberg systems...
TRANSCRIPT
Human Factors Integration for MODAF:
Needs and Solution Approaches
Anne Bruseberg Systems Engineering & Assessment Ltd, UK
(HFI DTC)
Gavan Lintern General Dynamics, US
INCOSE 2007 Symposium, San Diego, 27 June 2007
What is MODAF?
What is MODAF?
• MoD Architectural Framework– Based on DoDAF (US)– Approach for the design of complex systems (NEC)– Enables Interoperability
– Models Enterprises
Coping with complexity
• Models future systems – Aids requirements specification– Produces interlinked conceptual models– Provides overview– Provides operational focus
• Uses– Abstraction / Decomposition / Categorisation– Separation of issues into Views– Standardised representations: Structure/UML
• Supports collaboration between different disciplines– Provide common reference– Aids design management and trace
MODAF
MODAF: 6 Viewpoints, 38 Views
What is HFI?
HFI domains
Human FactorsEngineering
System Safety
Manpower
Training
Personnel
Health Hazards
HFI
Organisational & Social
HFI Functions
• HFI creates value through: – Raising potential issues and preventing risks– Establishing validated insight– Providing methods, processes, data, standards, expertise– Enabling user involvement– Undertaking a design mediation and communication role
Design activities
(activity cost)
Design features
(savings potential)
Problem prevention
(impact cost saving)
Lack of design activities (activity cost saving)
Design flaws(cost potential)
Problem occurrence(impact cost)
Risk preventionactivity
Likelihood ofrisk prevention
Risk causeLikelihood of
risk occurrenceProblemeffects
HFI Value Chain
HFI Process
Design activities
(activity cost)
Design features
(savings potential)
Problem prevention
(impact cost saving)
Lack of design activities (activity cost saving)
Design flaws(cost potential)
Problem occurrence(impact cost)
Risk preventionactivity
Likelihood ofrisk prevention
Risk causeLikelihood of
risk occurrenceProblemeffects
HFI Value Chain
VALUE
COST(efficiency)
PERFOR-MANCE
(effectiveness)SAFETY
(legislation)
Design activities
(activity cost)
Design features
(savings potential)
Problem prevention
(impact cost saving)
Lack of design activities (activity cost saving)
Design flaws(cost potential)
Problem occurrence(impact cost)
Risk preventionactivity
Likelihood ofrisk prevention
Risk causeLikelihood of
risk occurrenceProblemeffects
HFI Value Chain
DLODs
Concepts/Doctrine
OrganisationLogistics
Equipment
HFI support for MODAF
Why and How
• Why integrate HFI with MODAF? – SE needs HFI
• Enable socio-technical systems design• Need to specify people-related design decision areas
– Explicitly; Correctly; Early
– MODAF (version 1.0) has shortfalls in that
– HFI needs SE• MODAF is now mandated • Coping with design of complex systems• Opportunity for early involvement
• How? – Human Views (HVs):• Model human-related elements of Enterprises
• Ensures common modelling approach• Helps HFI to relate to SE concepts/methods
MODAF (version 1.0) shortfalls
• HFI trends and standards • are not captured.
• Human performance metrics, targets, and limitations • are not specified.
• Human role/job/organisational design • is insufficiently captured.
• Allocation of function decisions/ information requirements specifications
• may be technology-lead. • Team activity and team requirements
• are insufficiently captured.
OV-5: Operational Activity Model
SV-4: (Systems) Functionality Description
SV-4 may assign functions to roles
HVs between OV and SV level
OV-4
OV-2OV-3
OV-6
SV-10
OV-1a,b
SV-7
OV-5
OV-1c
SV-2SV-11
SV-3
SV-8
SV-9
SV-6
SV-5
SV-1
StV-5
HV-A:Capability
Constraints
HV-B: QualityObjectivesand Metrics
HV-C: SocialNetwork
Structure &Exchanges
HV-D a, b, c:OrganisationalDependencies
HV-E: HumanFunction
Definitions
HV-G: HumanPerformance
Dynamics
HV-F a, b, c:Roles and
Competencies
StV-2
StV-4
SV-4
HV Comparison
OV-5
OV-4
OV-2
HV-A
HV-C
HV-B HV-G
HV-Da, b, c
HV-Fa, b, c
HV-ESV-4
OV-6
Roles inLayout
Rolegroupings
Humanactivities/HCI
Human-HumanCommunication
Manningneeds
Roles andCompetencies
mapped toSystems
HV-A1:Activity to
UNTL
HV-1:Personnel
Policy
Paul Hicks(BAE Systems)
Holly Handley (US)
Kevin Baker(Canada) HV-F1:
Locations/Reach-back
HV-F2:Organizational
Structures
HV-A:Responsibility
Matrix
(OV-5decomposition)
HV-B: KSAper Activity
HV-C: RoleRequirements
HV-D: RoleTraining
HV-E:Workload
HV-G:Doctrine
MODAFHV-5: Humansystem level
functions
HV-4: Roles/Responsibilities
HV-3: taskdata elements
HOV-6a:HR relatedconstraints
HV-7: HumanPerformanceRequirementsHV-8: Personnel/
Training change
OV-1c
SV-10
HOV-6c:event activity
Capability Constraints Quality Objectives/Metrics
Social Network Structure& Exchanges
OrganisationalDependencies
Human FunctionDefinitions
Human Functions to Roleand Competency Mapping
HumanPerformanceDynamics
MODAFHVs
SV-7
SV-1
OV-3
The Human View Handbook
Provides ‘meta-model’ for each HV (example: HV-E)
Includes illustrations (example: HV-F)
Building up examples to support HVs (HV-C)
Questions?