1. 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 anne.bruseberg@sea.co.uk

2. What is MODAF?

3. MoD Architectural Framework –Based on DoDAF (US) –Approach for the design of complex systems (NEC) –Enables Interoperability –Models Enterprises

5. 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

6. MODAF: 6 Viewpoints, 38 Views

8. What is HFI?

9. HFI domains Human Factors Engineering System Safety Manpower Training Personnel Health Hazards HFI Organisational & Social

10. 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

11. HFI Value Chain

14. HFI support for MODAF

15. 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

16. 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.

17. OV-5: Operational Activity Model

18. SV-4: (Systems) Functionality Description

19. SV-4 may assign functions to roles

20. HVs between OV and SV level

21. HV Comparison

22. The Human View Handbook

23. Provides ‘meta-model’ for each HV (example: HV-E)

24. Includes illustrations (example: HV-F)

25. Building up examples to support HVs (HV-C)

26. Questions?