The Human View Handbook for MODAF: Part V â Appendices

More documents

Recommendations

Info

The Human View Handbook Part 5: Appendices DOCUMENT INFORMATION Purpose of the Human View Handbook The Human View Handbook for MODAF describes a set of Human Views (HVs) to be used as complementary elements to MODAF – the Ministry of Defence Architectural Framework. It aims to clarify the role of Human Factors (HF) when creating Enterprise Architectures in support of acquisition – in order to facilitate both Human Factors Integration (HFI) and Systems Engineering (SE). HVs aim to enable better integration across all the Defence Lines of Development (DLOD) and to aid Through-Life Capability Management (TLCM). Enterprise Architectures such as MODAF produce conceptual models of current and future systems. By modelling an enterprise as a whole, MODAF provides an overview perspective that aids acquisition management and collaboration between diverse disciplines. Therefore, it is an important tool for helping to fulfil the prime objectives of HFI – those of integrating the different HFI domains, integrating with other engineering disciplines, managing the need for HFI activities, and informing trade-off analyses. HVs clarify the scope of enterprises as socio-technical systems. HVs capture specific human-related components of enterprise models to enable effective HFI. By explicitly modelling the human elements that are being shaped in the process of capability design, they can be considered early and related closely to the design and implementation of technology. This supports a change of focus from technologycentred functional requirements only to broader capability-based requirements. The HVs aim to support any practitioner who needs to consider the human elements of Enterprise Architectures. The role of applying HVs may fall to experts with either Human Factors or Engineering backgrounds who plan and design future technologies and/or infrastructure, human networks, organisations, operations, or personnel processes, including the relationships between these aspects. Contents The HV Handbook is broken up into five separate documents: Part 1 provides a high-level introduction to concepts, benefits and use; Part 2 provides an in-depth technical description and justification of HVs; Part 3 provides guidance on the underlying processes and methods needed to support planning and generating HVs; Part 4 provides example applications to illustrate HV use, based on experiences from realistic projects, including a collection of HV example instantiations; Part 5 provides additional useful resources through several appendices. Table 1 provides an overview of the document structure. Note that the four main sections partition the document. However, the main headings run through these sections with continuous numbering (to avoid too many levels). Complementary to the HV Handbook, the ‘Human View Quick Start Guide’ provides a condensed technical overview of the HVs that can function as a quick reference guide. page 2
The Human View Handbook Part 5: Appendices Table 1: The contents of the HV Handbook, with a brief outline of each section. Part I: Introduction Section Description Part I: Overview & Short Introduction 1 Introduction to Human Views Provides a high-level introduction to the Human Views covering the most essential aspects on purpose, benefits, use and technical content. It provides a condensed summary to help judge whether the implementation of HVs is appropriate, and what for. Part II: Technical Description Part III: Process Guidance Part II: Technical Background and Detailed Human View Descriptions 2 HVs to support MODAF as an Enterprise Architecture 3 The Role of HFI 4 Joining HFI and MODAF perspectives 5 Overview of Human Views 6 Detailed descriptions To introduce the role of MODAF as an Enterprise Architecture, its purpose, structure, principles and use are explained, and to justify the need for modelling people-related elements explicitly. The HVs were tailored to the main characteristics of an architectural model. To introduce the role of HFI in relation to enterprise design as part of acquisition processes, the HFI process, HFI benefits, and HFI functions are expanded on. Some example cases are given to illustrate the problems that may occur when not involving HFI sufficiently. Approaches and terminology differ between HFI and SE. The HVs need to bring together perspectives from both HFI methodologies and architectural modelling approaches. The differences are discussed to be able to bridge them better. Potential relationships of the HVs with MODAF are discussed. The HVs are introduced, including their purpose and benefit, and definitions of what HVs are (and are not). The relationship with MODAF layers and technical themes is clarified. The HV meta-model is introduced, which specifies the HV data elements and their dependencies. The function of HVs in filling gaps in the MODAF meta-model and view descriptions is introduced. Each HV (HV-A through to HV-G) is described in depth, including its • Function (providing a summary of its focus and purpose) • Benefits and use (including justifications for using the View) • Data elements (defining the meta-model elements, and listing relationships with relevant MODAF Views and MODAF meta-model definitions) • Visualisation options (describing or illustrating ways in which the HV can be presented), including examples to show how the HV may be applied for its different instantiations). Part III: Applying Human Views: Process and Methods 7 Aims of the process guidance The purpose and content of sections 8 to 10 are outlined, in providing guidance on how to plan, use and implement HVs, and how to progress creating the Views. Section III is organised in line with the generic MODAF Architecting Process. It describes decision variables for scoping and detailing project-specific use by a wide range of potential stakeholders, rather than narrowly tailored answers. 8 The Purpose The section puts HVs in the context of the processes that it needs to support, and responds to the questions: • Why consider HVs (i.e. deciding whether to use MODAF and HVs in principle) • What to use HVs for (i.e. deciding on purpose and focus of HV use, when establishing architecting project boundaries in line with the envisaged benefits). This includes generic principles for architecture generation and use, which are important for understanding the role of HVs and their application. page 3
Page 1 and 2: The Human View Handbook for MODAF:
Page 3: The Human View Handbook Part 5: App
Page 7 and 8: The Human View Handbook Part 5: App
Page 55:
HFIDTCPIII_T02_02e Version 2/ 11 Au
show all

The Human View Handbook for MODAF: Part V â Appendices

Create successful ePaper yourself

Delete template?

Save as template?

The Human View Handbook for MODAF: Part V â Appendices