Human-System Integration in the System Development Process A New Look (2007) / Chapter Skim
Currently Skimming:
1 Introduction
1 Introduction
Pages 9-28
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 9... ...
This volume provides a vision for integrating an understanding of human capabilities and needs into system design using an incremental model of systems engineering development that continually assesses risks, including risks associated with the human element, at each phase of the system development effort. The chapters present a large variety of methods (1)
|
From page 10... ...
Additional methods and approaches are needed to complement the existing methodology as systems become more complex and the focus shifts from the design and operation of individual systems to systems of systems. A brief history of key events in the development of human factors appears in Box 1-1.
|
From page 11... ...
In this report we use the term "human-system integration" to refer to the design activities associated with ensuring that the human-system domains described above are considered in concert with all the other design activities associated with the systems engineering process, so that the resulting designs are truly responsive to the needs, capacities, and limitations of the ultimate users of the systems. Although human factors engineering is but one of the HSI domains, the one concerned with providing the methods and expertise to take account of human performance capacities and limitations in formulating effective system designs, it receives particular emphasis in this report because the methods appropriate to it are often the same methods needed for the other domains.
|
From page 12... ...
. There is an urgent need for improved HSI methods and tools that will enable system designers to anticipate and head off potential problems earlier in the design process (Woods, 2002)
|
From page 13... ...
Another outstanding example of success is the Army Comanche Helicopter program. By modifying the acquisition program specifically to recognize human-system interaction as an integral part and by introducing HSI requirements early and throughout the acquisition program, the government-industry team substantially improved overall human-system performance while realizing a cost saving of 40 times the cost of the HSI investment.
|
From page 14... ...
In addition to obtaining the labor savings that were promised by the technology, the redesign also improved the customer responses, leading to the voice recognition technology that is part of nearly all U.S. directory assistance calls today.
|
From page 15... ...
INTRODUCTION • Failure to assign resources as a result of lack of awareness that specific resources are needed to address HSI concerns. • Conflicting requirements of various stakeholders in the system development process.
|
From page 16... ...
An example of a system of systems under development is the Air Force Falconer Air Operations Center in Arizona; in Central Command, Air Operations Center is described in The Integrator (Mayer, 2005) as follows: The Electronic Systems Center developed Falconer AOC "system of sys tems" is the Combined Forces Air Component Commander's weapon system for commanding air and space forces.
|
From page 17... ...
These are the issues we address in this report. Specifically, the charge to the committee is to • provide a comprehensive review of issues involved in design throughout the system life cycle that need to be addressed by a consideration of human cognitive and physical performance characteristics.
|
From page 18... ...
Both programs are compatible with the seven HSI domains listed in the defining DoD Instruction 5000.2 Operation of the Defense Acquisition System (U.S. Department of Defense, 2003a)
|
From page 19... ...
, a modeling tool developed by the Army Human Engineering Directorate and used by the Army and the Navy for manpower planning and to inform human-system design decisions (Allender et al., 2005)
|
From page 20... ...
An important input to effective training is a task analysis that identifies the skills and knowledge needed for acceptable performance -- this analysis requires updating as the system configuration changes or as new automation is introduced. Although there may be some task analysis requirements that are unique to the training domain, the methods for creating this task analysis are substantially the same as those used for other system development purposes discussed in this report.
|
From page 21... ...
for which training is critical but manpower and personnel issues are less relevant. Many commercial products are released for which user training is impractical, so they need to have self-evident, intuitive user interfaces to be successful; indeed, for web-based commercial services, user training is impossible, and ease of use becomes a significant, make-or-break attribute.
|
From page 22... ...
4. Sharing of dynamically updated personal information through person-centric shared databases.
|
From page 23... ...
Adopting a Risk-Driven Approach A central focus of the incremental commitment model is the progressive reduction of risk throughout the system development life cycle with the goal of producing a cost-effective system in which all stakeholders are considered winners. Risk reduction is accomplished through the application of all relevant disciplines.
|
From page 24... ...
For the manufacturer of commercial products, loss of sales, product liability lawsuits, and product recalls are major potential results of failure to adequately consider HSI risks. These operational stage risks are traceable to failures to fully integrate user needs and capabilities at earlier phases of the development cycle.
|
From page 25... ...
By predicting and highlighting potential performance limitations, computer simulations of the human-machine system are another form of model that can support shared understanding by the development stakeholders. The committee thinks that a current impediment to effective identification of HSI issues and risks and utilization of the resultant recommendations is the often vague nature of the products of HSI analysis.
|
From page 26... ...
For a system to remain work-centered over time, it must not only support the elements of work identified at the design stage, but it must also be able to accommodate elements that the initial design did not appropriately capture and be adaptable to meet the changing nature of the work. Systems need to be designed in ways to enable users to adapt the system to evolving requirements.
|
From page 27... ...
They are used throughout the report to highlight different approaches, methods, and tools. Part II: Human-System Integration Methods in System Development contains three chapters characterizing HSI methods and tools.
|
From page 28... ...
8 HUMAN-SYSTEM INTEGRATION IN SYSTEM DEVELOPMENT identified as central contributors of information to the system development process about topics relating to people. Part III: Scenarios, Conclusions, and Recommendations provides the committee's vision for the future and our conclusions and recommendations.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.