Upload
emmeline-headley
View
224
Download
9
Tags:
Embed Size (px)
Citation preview
Human Views for MODAF
Dr Anne Bruseberg Systems Engineering & Assessment Ltd, UK
on behalf of the Human Factors Integration Defence Technology Centre (HFI DTC)
6 February 2008Integrated EA Conference 2008
The need for Human Views
• Ensure Human Factors Integration (HFI)
• 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– Coping with design of complex systems– Opportunity for early involvement
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
What are Human Views (HVs)?
• Capturing specific human-related components of Enterprise models to enable effective HFI
• Ensures common modelling approach
• Helps HFI to relate to SE concepts/methods
• HFI design decision areas that can generally be perceived as formal definitions. – Not:
• the ‘soft’ issues that may be observed
• Informal dependencies and behaviours (they are constraints and results)
• Functional definitions– extending traditional meaning of ‘functional’ to HFI design areas
The HFI question
• “Can this person/these people, in this job, with this training, perform these tasks, using this equipment, to these standards, under these conditions”?
The HV question?
“Can these operational and capability requirements be achieved -
• grounded in these HFI objectives and standards, • through these technological and organisational
structures, • with these human resources,• fulfilling these functions, • interacting as part of these
organisational/task/process dependencies, • in these roles/jobs, • requiring these skills and characteristics, • in these locations, • using this equipment, • over these timescales?“
MODAF developments
MODAF v. 1.1 (6 Viewpoints, 38 Views)
Architecture characteristics
• Separation of component concerns• Generic: Conceptual Data Model / Meta Model• Instantiation: Logical and Physical Data Model • View: window/snapshot onto model• Architectural products• Viewpoints• Levels of abstraction
– Complexity– Requirements-solutions
MODAF SV-1 (v 1.1)
MODAF Meta-Model: New
Capability Deployment
CapabilityConfigurationCapability
Configuration
PhysicalAsset
PhysicalAsset
OrganisationalResource
OrganisationalResource
configured with
StandardStandard
subject todoctrine
hosted on
SystemSystem
owns
configured with
deployed to
NodeNode
realised by
OperationalActivity
OperationalActivity
FunctionFunctionhas
supports
RoleRole
is assigned
operates
conducts
New MODAF v1.1 M3 definitions
• ResourceInteraction (SV-1)– An assertion that two <<FunctionalResource>>s interact.
• Examples: data exchange between systems, conversations between people, people using systems
• Function (SV-4)– An activity which is specified in context of the resource (human
or machine) that performs it.• Note1: Contrast with <<OperationalActivity>>, where the actor
performing the activity is not known (i.e. it is just a logical node). A <<Function>> is implementation-specific.
• Role (SV-1, OV-4)– An aspect of a person or organization that enables them to fulfil
a particular function.
• PostType (OV-4)– A type of point of contact or responsible person. Note that this is
the type of post - e.g. Desk Officer, Commander Land Component, etc.
SOA focus in DoDAF v 1.5
Services Ope
ratio
nal A
ctiv
ity A
Ope
ratio
nal A
ctiv
ity B
Ope
ratio
nal A
ctiv
ity C
Ope
ratio
nal A
ctiv
ity D
Ope
ratio
nal A
ctiv
ity E
Ope
ratio
nal A
ctiv
ity F
Ope
ratio
nal A
ctiv
ity G
Ope
ratio
nal A
ctiv
ity H
Ope
ratio
nal A
ctiv
ity I
Ope
ratio
nal A
ctiv
ity J
Ope
ratio
nal A
ctiv
ity K
Ope
ratio
nal A
ctiv
ity L
Ope
ratio
nal A
ctiv
ity M
Ope
ratio
nal A
ctiv
ity N
Ope
ratio
nal A
ctiv
ity O
Ope
ratio
nal A
ctiv
ity P
Ope
ratio
nal A
ctiv
ity Q
Ope
ratio
nal A
ctiv
ity R
Ope
ratio
nal A
ctiv
ity S
Ope
ratio
nal A
ctiv
ity T
Service 1 X X XService 2 X X XService 3 X X XService 4 X X X X X XService 5 X X XService 6 X X X X XService 7 X X XService 8 X X X X X X X
Capability 1 Capability 2 Capability 3 Capability 4 Capability 5
Operational Activity to Services Traceability Matrix (SV-5c)
MODAF Human Views
UK work: progress / plan
• Scoping Study
• HV concepts to IA
• Draft HV Handbook
• Input towards MODAF v1.1
• Stakeholder Review
• Revised HV Handbook
• Published HV Handbook (Issue 1)
• Applications and Updates
end Dec 06
8 Feb 07
12 March 07
30 March 07
end July 07
mid Sept 07
Jan 08
ongoing
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-2
SV-3SV-8
SV-9
SV-6
SV-5
SV-1
StV-3,5
StV-2
StV-4
SV-4
HV-A:PersonnelAvailability
HV-B: QualityObjectives and
Metrics
HV-C: HumanInteractionStructure
HV-D:Organisation
HV-E: HumanFunctions and
Tasks
HV-G: DynamicDrivers of Human
Behaviour
HV-F:Roles and
Competencies
FormalDependencies
Part-whole
Rank
Conditions
OperationalConfigurations/States 1...n
HumanFunctions/Tasks
Facilities
Detailedthrough
Human PerformanceCriteria & Metrics
Methods ofCompliance
Mappedto
TargetMeasures
Specifiedwith
Mappedto
Informationaccess,
transmissionand sharing
Systems
Locations
actual virtual
Roles/Responsibilities
Competency RequirementsSkills Attributes Knowledge
PersonnelDevelopment
Need
OrganisationalUnits
Units Teams Posts
FormalProcesses/
Procedures/Values
Enable
Relatethrough
At
At
Aredefinedthrough
Define
Define
Needs
Require
Trends/Forecasts
Fulfill
Human-computerInterface
Have
SystemFunctions
Affect
ActualPeople
Personin Post
Has
Environment
With
Use
HFI ValueLevel 1...nHFI ValueLevel 1...nHFI ValueLevel 1...nHFI ValueLevel 1...nHFI ValuedefinitionsLevel 1...n
Conduct
Require
Interactionwith
Equipment
Teamwork/Interaction
Taskwork(decom-position)
RequireRequire
Peopleavailability
Define
Numbers Characteristics
Have
Person(throughPost) in
Role
Define
Have
Ensures Have
At
Time/Epoch
Behaviours
HCITeamwork
Taskwork
Assessedthrough
Define
Affect
StateChanges
TimeUnits
Have
For
Scenario 1...n(representative)
For
Describe
Define
At
Dynamic properties
HaveInterface
with
Havestatus
of
Display
Display
DisplayDisplay
Consist of
HV-AHV-G
HV-E
HV-D
HV-F
HV-C
HV-B
FormalTask-BasedOrganisationAffect
Affect
HV-A: Personnel Availability (example)
0
10
20
30
40
50
60
totalavailable
now
totalavailablein future
futureneed
HV-A: Personnel Availability
Opportunities given
Personnel-relateddevelopment processes
Roles
Posts/Positions Define
Constrain
Actual People
Time:(Development
Phase,Epoch)
Forecast
Characteristics
Numbers
At
Of
Captures
WithWithExperienceGathering
Organisational Structures
Affect
Require
Require
Skills/Expertise/Knowledge
Attributes
Experience/Values/Attitudes
Uniquely humanCharacteristics
Affect
BehaviourWorkload/Error
Assessment
WorkloadAssessment
Availability
FluctuationTrends
OrganisationalProcesses & Policies
Cause
Task/Roledemands
Affect
Career structure &Rank progression
On-the-job learning(exposure)
Social Learning
Affect
Affect
Affect
Affects
Affects
CapturesCaptures
DemographyTrends
Trainingneeds
analysis
Belong to
EvolvingStructures and
Processes
Have
Qualifications/Grade
With
HV-A
Have
FilledPosts
In
Formal Training
Recruitment/Retention Process
Health & SafetyProvision
Personnel Policy
HV-B: Quality Objectives and Metrics (example)
HV-B: Quality Objectives and Metrics
HumanFunctions/Tasks
Detailedthrough
Human PerformanceCriteria & Metrics
Methods ofCompliance
Mappedto
TargetMeasures
Specifiedwith
Mapped to
Behaviours
HCITeamwork
Taskwork
Assessedthrough
HFI ValueLevel 1...nHFI ValueLevel 1...nHFI ValueLevel 1...nHFI ValueLevel 1...nHFI ValuedefinitionsLevel 1...n
HV-B
At
Define
Time/Epoch
Role
System
Physical Location 1
Role
RoleSystem
VirtualLocationthroughdatasharing
Physical Location 2
Role Role
System
Requires physic alinfrastruc ture
Physic alremoteness
Role
Physical Location 3
Role System
System Materia l flow
Role
HV-C: Human Interaction Structure (examples)
Role RoleUnit Unit
Role
System
UnitUnit
Role
Communic ationthrough system
Task A lloc ationTransmiss ion/ Reporting
SupervisoryInstruc tions/Reporting
Command /Reporting
Deploymentinstruc tions/rec eivefeedbac k
Datasharingforc oordi-nation
Unit
Role1
Interaction Types within and between Roles/Units
Role2
Role3
Role5
Role4
Unit 1 Unit 2 Role9
Role6
Unit 3
Role7
Collaborate
Coordinate
Cooperate
Supervise
Working Group
Unit 4
Unit 5
Command
Role9
Role8
Role11
Role10
FLEXIBLE DUTY ALLOCATION
Organisation 2
Organisation 1Role
1
Interaction Types within and between Roles/Units
Role2
Role3
Role5
Role4
Unit 1 Unit 2 Role9
Role6
Unit 3
Role7
Collaborate
Coordinate
Cooperate
Supervise
Working Group
Unit 4
Unit 5
Command
Role9
Role8
Role11
Role10
FLEXIBLE DUTY ALLOCATION
Organisation 2
Organisation 1
HV-C: Human Interaction Structure
Organisational Units
Units Teams Posts
HumanFunctions/Tasks
Interactionwith
EquipmentTeamwork/Interaction
Taskwork(decom-position)
FormalDependencies
Facilities
Informationaccess,
transmissionand sharing
Consistof
Systems
Locations
actual virtual
Roles/Responsibilities
Enable
Relatethrough
At
At
Fulfill
Human-computerInterface Have
SystemFunctions
Environment
With
Conduct
Require
RequireRequire
HV-C
Interface with
Aredefinedthrough
InteractionPurpose
OperationalFunctions
Nodes
Perform
Structure
Have
Affect
Affect
Determine
Require
Moving
HV-D: Organisation (examples)
HV-D: Organisation
FormalDependencies
Part-whole Rank
OperationalConfigurations/States 1...n
Informationaccess,
transmissionand sharing
Consist of
Roles/Responsibilities
Organisational Units
Units Teams Posts
FormalProcesses/
Procedures/Values
Relatethrough
Aredefinedthrough
Affect
Has
Use
Person(throughPost) in
RoleDefine
HV-D
Interactiontypes
FormalTask-BasedOrganisation
Affect
Affect
Cause
Affect
Defines
e.g.
InteractionPurpose
Have
Personnel
Require
HV-E: Human Functions and Tasks (example)
Human Task Flow for Human Function 1
Hum
an
Sys
tem
Hum
an
Task 1.1
Task 1.2
Task 1.3 Task 1.4
SystemFunction X
Note: ‘system’ is used here for hardware/technology (in line with MODAF terminology)
HV-E: Human Functions and Tasks
Information access,transmission and
sharing
Systems
Enable
Fulfill
Human-computerInterface
Have
System Functions
Behaviours
HCI Team work Task work
HV-ERoles/
Responsibilities
OperationalFunctions
Human Functions/Tasks
Interaction withEquipment
Teamwork/InteractionTaskwork
(decomposition)
Require
Interfacewith
Require
Conduct
Define
NodesPerform
Structure
HV-F: Roles and Competencies (examples)
Human Task Flow for Human Function 2
Role
2R
ole
3R
ole
1
Task 2.1
Task 2.2
Task 2.4 Task 2.5
Task 2.3
IndividualRole 8.1.2
Skill 1
Knowledge 1
Attribute 1
Note: The ‘A’ in KSA (Knowledge, Skills & Attributes) is sometimes also referred to as Aptitudes, or Abilities.
HV-F: Roles and Competencies
HumanFunctions/Tasks
Information access,transmission and sharing
Roles/Responsibilities
RelatethroughConduct
Interactionwith
Equipment
Teamwork/Interaction
Taskwork(decom-position)
HV-F
Consistof
Competency Requirements
Skills Attributes Knowledge
PersonnelDevelopment
Need
Organisational Units
Units Teams Posts
Require
Define Personin Post
Have
Require
Needs
Peopleavailability
HV-G: Dynamic Drivers of Human Behaviour (example)
(1) Commander
CMD
KM/IM JISE
COPS
JOC
FOPSIO
(2) Rep to KM/IM
(3) Director InfoManagement
(5) OPT Team
Intel
(4) OPT Team
Intel
JFMCC -> JTF
(6) INTEL - IPE
(7) Red Cell Analyst
(8) Red Cell Analyst
(9) Director
(10) JIAWG Director
(11) OPT Team
Leader
(12) OPT
Team Intel
(13) IO Planner
FOPS
JIB(14) PAO
Assistant
(15) OPT Team
SUW
(16) OPT Team
USW
JLRC
(17) OPT Team
JOPES
(18) Director
(19) Battle Watch
Captain
JICO
(20) JICO
JICO
(20) JICO
(21) Maritime Ops
(22) Maritime Ops
Cell
Role
Cell Change
Role (Cell) Change
As the JFMCC morphs to the JTF, the FOPS cell gains OPT Planning Members from their JFMCC “home” cells (4,5,12,17) and the Planning Roles become more specialized (15, 16). The IPAC and PAO cells change names (JISE and JIB), reflecting a different focus.
Role (Specific) Change
HV-G: Dynamic Drivers of Human Behaviour
OperationalConfigurations/States 1...n
Dependencies
Role assigments
Procedures
Locations/Environment
HumanFunctions/
Tasks
Human PerformanceCriteria & Metrics
TargetMeasures
Specifiedwith
Mappedto
Roles/Responsibilities
Behaviours
HCITeamwork
Taskwork
InformationFlows
(OV-6/SV10-c)
Assessedthrough
StateChanges
(OV-6/SV10-b)
HasDefine
Require
Person(through Post)
in Role
Includes
Affect
StateChanges
Time Units
Timeline
Mission phases
ConditionsOperationalconstraintsEvents/situationsTimeconditionsTask Rules
Have
For
At
Organisationalstructure
In
Includes
Scenario 1...n(representative)
evolving
critical
typical
For
Locations
At
HV-G
Include
Define
Describe
DynamicpropertiesHave
Summary
• The need to model an entire Enterprise as a socio-technical system is well recognised. – Enterprise Architectures are being conceived to specify
requirements and solutions for all DLOD. – MODAF version 1.1 has significantly modified many of its
underlying definitions. – The HVs further expand on this development.
• The complementary HVs for MODAF aim to bring together SE and HFI as two related disciplines. – Whilst SE and HFI depend on each other, each is grounded in a
set of approaches and philosophies not immediately compatible. – By choosing a SE approach to express HFI design decision
areas, HFI professionals are provided with means to communicate to Systems Engineers.
– HV elements have the potential of changing traditional SE approaches that can be overly technology focused.