Skip to main content

Currently Skimming:

3 Human-System Integration and the System Development Process
Pages 55-74

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 55...
... Three general classes of human factors methods provide a robust representation of the multiple HSI concerns, and are applicable at varying levels of effort throughout the development life cycle. These broad classes include methods to: • Define opportunities and context of use: Methods for analyses that contribute to early definitions of opportunities and requirements and that attempt to characterize the context of use, including characteristics of users, their tasks, and the broader physical and organizational environment in which they operate so as to build systems that will effectively meet the needs of users and their work and will function smoothly within the broader physical and organizational context.
From page 56...
... These methods generate objective data concerning critical humansystem issues, leading to incremental growth of system definition and stakeholder commitment. In Chapter 2 we showed how system development activities of the incremental commitment model (ICM)
From page 57...
... By engaging appropriate HSI methods during the incremental development process, risks can be reduced throughout the engineering life cycle, increasing the likelihood of a system's meeting user requirements and satisficing stakeholders. Appendix Table 3-A1 lists best practices for human-system integration taken from ISO/PAS 18152 (International Organization for Standardization, 2003)
From page 58...
... with spiral approach to design activity HSI activities that reduce Define opportunities Define contexts Design Evaluate risk and facilitate & requirements of use solutions transdiciplinary teams Stakeholder Satisficing Goal of system Success-critical stakeholder satisficing: this implies that the key decision makers in system development have agreed that particular design solutions are development acceptable, if not optimal. Tradeoffs have been made that may not maximize system performance but will result in acceptable performance within the cost and schedule constraints.
From page 59...
... Instead, human factors methods can be more broadly conceived both as design-aiding techniques and as methods for progressive risk reduction during the life cycle. In this sense, human factors methods contribute to the development process in much the same way as, for example, prototyping or simulation is employed by systems engineers and can be used during the early to middle stages of development to evaluate alternatives and to narrow design choices based on various constraints.
From page 60...
... As designs become more elaborated, participatory techniques can be applied to the point of reaching stakeholder consensus for purposes of a specific increment. This linkage of HSI activities to incremental development permits the design and risk management process to serve as a way to select the most appropriate HSI methods (and their extent of application)
From page 61...
... In addition, there is a clear need to share design and process artifacts at all phases in the systems development process, especially with the software and hardware developers who are actually implementing the system, and who are not only relying on clear specifications for development, but who are also expected to contribute to the generation of those specifications at critical decision points in the process. As a consequence, the committee has pursued the concept of shared representations as a means of addressing this concern.
From page 62...
... Each subsequent artifact in the process builds on the original model and, through negotiation, points to a model of what the system should be in such a way that it can finally be prototyped. Shared representations act as mediators in the collaborative and iterative construction of knowledge in the design process.
From page 63...
... . Attributes of Good Shared Representations Nearly every activity in the system development life cycle results in some form of tangible design artifact, but it may not necessarily be a good shared representation.
From page 64...
... Documentation that focuses on activities identified from a territory map often becomes successful shared representations. They are produced in the midst of extensive task, process, or environmental research and provide a way to discuss what currently happens and what should or could happen.
From page 65...
... Personas are also often an excellent shared representation category because they are composite user archetypes based on behavioral data gathered from many actual people during discovery research (see Chapter 7)
From page 66...
... Although conventional project planning schedules or spreadsheets can support the design and development process, they can never take the place of consciously planning, producing, and seeding discussion around shared representations to improve the quality of collaboration and productive outcomes of transdisciplinary design teams (Carroll, 2002)
From page 67...
... Work context analysis –Perform research into required system Investigate required usability. system usability –Generate design options for each Usability benchmarking aspect of the system related to its use and its effect on stakeholders.
From page 68...
... –Task analysis 5. Architecting –Generate design options for each solutions aspect of the system related to its use –Work domain analysis (a)
From page 69...
... –Participatory design elements –Prototyping –Usability evaluation methods User interface guidelines and standards continued
From page 70...
... Human mitigate risks related to HS issues. Plan use of HSI data to resources –Evaluate the current severity mitigate risks of emerging threats to system Identify HSI issues and usability and other HS risks and the aspects of the system effectiveness of mitigation measures.
From page 71...
... HSI knowledge –Evaluate the current severity –Risk analysis (e) Staffing of emerging threats to system –Usability evaluation usability and other HS risks and the methods effectiveness of mitigation measures.
From page 72...
... analysis analysis –Manage the life-cycle plan to address –Risk analysis HS issues. User feedback –Take effective mitigation to address Work context analysis risks to system usability.
From page 73...
... Retirement –Produce personnel strategy. Work context analysis –Review the system for adherence to applicable human science knowledge, style guides, standards, guidelines, regulations, and legislation.
From page 74...
... Assess and improve HSI data collection, –Perform research to develop HF data capability analysis, and as required. Develop and maintain improvement –Produce coherent data standards and HSI infrastructure and (b)


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.