The National Academies Press

Currently Skimming:

Index
Pages 365-384

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 365... ... , 44 AFQT. See Armed Forces Qualification Test procedures, 46 Aggregation, of features, 26 Architectures, back-end, 238 Agile methods, 35, 37 Armed Forces Aptitude Test Battery Air Force Falconer Air Operations Center, (ASVAB) Read the entire page →
From page 366... ... See Boeing Engineering Aerospace Cognitive task analysis (CTA) , 161–169 Simulation Tool program a bootstrap process, 165–166 Behavioral patterns, 186 contributions to system design phases, Bell Laboratories, 10 167 Best-effort definitions, 49 overview, 161–166 Best practices relationship to task analysis, 165 for HSI, 57 representative methods, 162–165 for risk mitigation, 67–74 shared representations, 166–167 tables of, 44 strengths, limitations, and gaps, Bhopal accident, 328 168–169 "Bifocal tools," 212 in the unmanned aerial systems case Big design up front (BDUF) Read the entire page →
From page 367... ... See also Shared interpretation, 175 representations for communication overview, 175–176 among members of the development shared representations, 176 team, 195 strengths, limitations, and gaps, 177 creating shared representations for, 25 Control, of information, 22 between customers and suppliers, 195 Control rooms, 157 of risk, improving, 329–330 for power plants, 139 Compatibility, evidence of, 45 Cornell Musculoskeletal Discomfort Complexity of systems, 1, 144–145, 308 Survey, 219 Composite stories, 231 Cost as an independent variable (CAIV) , Composite user archetypes, 65 76 Computational tools, paucity of, 206 Cost-competitive contracts, 33 Computer simulations, 25, 106, 240, 267 Cost-effective systems, 23 Concept mapping, 163 Costs, providing a basis for controlling, of the role of cold fronts in the Gulf 195 Coast, 164 Cougaar, 311 Concurrent engineering process models, 34, Crisis response systems, 15 37, 48, 51 Critical decision method (CDM) Read the entire page →
From page 368... ... models and simulations, 240–252 See also Human-system integration, participatory design, 210–216 developing as a discipline personas, 233–235 opportunities for, 14 physical ergonomics, 217–223 Electronic models, 25 prototyping, 235–239 Electronic Systems Center, 16 scenarios, 230–233 Emergency Care Research Institute, 110 situation awareness, 223–226 Emergency medical missions, 15 usability requirements, 191–197 Emergent behavior, 15, 53 work domain analysis, 197–207 Emergent requirements, 33 workload assessment, 207–210 Emotional models, 251–252 Delphi group decision-making technique, Encyclopedias. See also Wikipedia 262 online, user-constructed, 22 Descriptive methods, in ethnography, 151 End-state operational system risks, 57 Design Energy systems, 255 as an innovative process, 189 Engineering development risk, management as a socially constructed process, 61 of, 59 Design cycle time, pressure to reduce, 12 Enterprise resource planning (ERP) Read the entire page →
From page 369... ... , 253 analysis advantages and disadvantages of, 265 Ethical considerations, 6, 316–320 and other technique variations, Ethnographic inquiry, 231 260–262 contributions to the system design steps in performing, 264 process, 154–156 FDA. See Food and Drug Administration interviews, 153 Feasibility methods, 213 evidence of, 45 observations, 153–154 rationale for, 50 practices, 152–154 Feature needs principles, 150–152 large color touch screens, 111 shared representations, 155 medication libraries with hard and soft strengths, limitations, and gaps, dosage limits, 110–111 155–157 semiautomatic cassette loading, European Union, 319 112–113 Evaluation, 56, 247–248, 281–282 special alarms with melodies, 111–112 heuristic, 271–272 special pole mounting hardware, 113 of remaining plan activities, 90 stacking requirements, 113–114 of success accomplishments, 90 and their rationales, 110–114 system-level, 14 tubing management, 114 Event data analysis (EDA) Read the entire page →
From page 370... ... See Hierarchical task analysis G Human capabilities and needs, considering early, 1 Gantt charts, 209, 279–281 Human cognitive characteristics, 2 Global context, 16 Human-computer interaction, 10 Goal/task decompositions, 279–280 Human digital modeling, 221, 223 GOMS (goals, operators, methods, and Human error analysis, 255–265 selection rules) method, 167, contributions to system design phases, 242–243, 249–250, 281, 321 262 Google, 178 general model of, for security screening, Government organizations, 4–5 100 Graphic user interface (GUI) Read the entire page →
From page 371... ... in the life-cycle process elaboration, 36, 45 system development process, 55–74, milestone reviews, 37, 46–47 127–274 phases of, 44 best practices for risk mitigation, 67–74 principles, 33 case studies, 91–125 process model generator view, 39–40 conclusion, 66 project experience with, 50–53 defining opportunities and context of spiral view of, 47–49 use, 55, 129, 135–188 top-5 projects explicitly using, 51, 51n. defining requirements and design, 56, 1 129, 189–252 Incremental growth, of system definition evaluating, 56 and stakeholder commitment, 32, function allocation, 131 103–104 managing risks, 75–90 Individual stories, 231 methods for evaluation, 129, 253–274 Information, sharing across domains, 7 performance measurement, 131–133 Input/output system diagrams, 142 shared representations, 61–66 Institute for Human and Machine the system development process, 31–54 Cognition, 315 Human-system integration methods Institute for Safe Medical Practices, 110 tailored to time and budget Institutionalization, of a system constraints, 99–100 development process based on the Human-system model development, success factors, 302 320–322 Insurgency suppression missions, 15 Integrated product team (IPT) Read the entire page →
From page 372... ... 2, 313 Life-cycle architecture (LCA) International Journal of Human-Computer development phases, 3 Studies, 131 of the ICM and EDA, 185 International Journal of Human System operational stage risk of high costs, 59 Integration, 313 package, 44, 50 International Organization for planning, 124 Standardization. Read the entire page →
From page 373... ... theatrical approaches, 213 domains, 18 workshop methods, 213–214 Manpower considerations, 1, 5, 11 Methods based on expert assessment of the in the military sector, 18–19 characteristics of a system, 271–272 MANPRINT (Manpower Personnel cognitive walkthrough, 272 Integration) program, 10, 17, 24, guidelines and style guides, 271 296, 298, 307–308 heuristic evaluation, 271–272 Manufacturing sector, 17, 21 usability walkthrough, 272 Maps, territory, 64 Methods based on observing users of a real Market capture goals, 4 or simulated system, 268–270 Marketing Requirement Document, 110 formative methods, 268 Markov modeling, 184 summative methods, 268–269 "Mash-up" technologies, 26, 289, 291 Methods for defining opportunities and Matrix organization, 146 context of use, 314–320 Maximizing the cost-effectiveness of tools to support capture and usability evaluation, 326–327 dissemination of results of context Medical equipment of use analyses, 315–316 possible harms and hazards from the user participation in systems use of, 258 engineering and event data analysis standards for, 114 and their ethical implications, use of an automatic external 316–320 defibrillator, 258 Methods for defining requirements and use of an automatic needle injection design, 320–324 device, 258 human-system model development, Medical Research Council Laboratory, 10 320–322 Medication libraries, with hard and soft prototyping training and organizational dosage limits, 110–111 design, 322–324 Mental workload, 207–208 Methods for evaluation, 129, 253–274, Meta-design approaches, 293 324–330 Method acting, 234 analysis of human error, 256–265 Methods. Read the entire page →
From page 374... ... See also Hardware models; Human Customer observations digital modeling; Human-system resulting from HSI faults, 259 model development; Incremental Negotiation commitment model; Network facilitating, 64 models; Physical models; Sequence terms oriented to, 34 models; Software models; Team Nested techniques, 144 models Network management, 21 contributions to system design phases, Network models, of human-system 246–248 performance, 241–242 derived from human cognitive New technologies, 26 operations, 242–243 feasibility of inserting, 4 overview, 240 governmental and commercial uses of, strengths, limitations, and gaps, 248–252 22 that mimic human cognitive and "Next-generation" intravenous infusion perceptual-motor behavior, 244–246 pump, 105–125 types and uses of, 240–246 motivation behind the design, 106 ModSAF model, 244 Read the entire page →
From page 375... ... See Occupational repetitive action Participatory analysis, 5, 95, 169–175, methods 210–216, 230 Operation of the Defense Acquisition contributions to the system design System, 2, 4–5, 14 process, 173, 214 Operational requirements, of HSI, 4 fitting into the system development Operational return on investment, 31 process, 174 Operational stage, 3, 248 methods, 211–214 Operational stage risks, 59 overview, 169–173, 210–211 use-error-induced, 92 scenarios in, 172 Operations commitment review (OCR) , 47 shared representations, 173–174, Operator fatigue, 226 211–215 Opportunity-driven approach, to strengths, limitations, and gaps, determining needs for HSI activity, 174–175, 215–216 adopting, 298 workshops in, 170–172 "Opt-in" and "opt-out" approaches, 320, Participatory workshops, 170–172 320n. Read the entire page →
From page 376... ... 2, Private sector context, 4–5, 12, 20–22 218–223 Process control, 17, 21 assessing, 207 Process model generator view, 39–40 contributions to system design phases, Process tracing, 183 222 Product design methodologies, 2 overview, 217–218 Product failures, reducing risk of, 195 shared representations, 218–219 Product introduction, 124 strengths, limitations, and gaps, Product requirements document (PDR) , 222–223 119, 121 uses of methods, 219–221 Product usability characteristics evaluation Physical models, 25, 176 methods, 271–272 Physical performance characteristics, 2 automated methods based on rules and Physical prototypes, foam model of a blood guidelines, 272 analyzer prototype, 237 methods based on expert assessment Physical simulations, digital human, of the characteristics of a system, 243–244 271–272 PLIBEL, 219 Product variation, 145 Point-solution architecture, 33 Program award fee criteria, 4 Pole mounting hardware, 113 Program impacts, assessing, 83–84 Policy recommendations, 4, 301–330 Program management risks, 57 methods for defining opportunities and Program managers, lack of commitment to context of use, 314–320 HSI by, 2 methods for defining requirements and Program schedules, 89–90 design, 320–324 Progress monitoring, 14 methods for evaluation, 324–330 Project Ernestine, 243 realizing the full integration of human Protocols systems and systems engineering, analysis of, 182 301–314 RSS, 289 Polyvinyl toluene sensors, 105 think-aloud, 225 Port security, 97–105. Read the entire page →
From page 377... ... See Research and development preliminary, 108–109 Real options theory, 38 shared representations, 5 Reason's error classification, 257 Research and development (R&D) , 86 Rebaselining, 32 support for, 13 Recommendations, 2, 4, 296–330 Research recommendations, 301–330 adopting a risk- and opportunity-driven methods for defining opportunities and approach to determining needs for context of use, 314–320 HSI activity, 298 methods for defining requirements and beginning HSI contributions to design, 320–324 development early and continuing methods for evaluation, 324–330 them throughout the development realizing the full integration of human life cycle, 297 systems and systems engineering, designing to accommodate changing 301–314 conditions and requirements in the Residual risk, 259 workplace, 300–301 Resilience, 6, 14, 309, 328, 330 ensuring communication among Resources stakeholders of HSI outputs, 299 failure to assign, 14, 24 integrating across human-system suboptimal, 84, 145 domains as well as across the system Reusable components, 7, 33 life cycle, 298 Risk tailoring methods to time and budget assuming, 87 constraints, 299 Read the entire page →
From page 378... ... 1 Risk management, 48, 75–90, 104–105 "Say-do-make" approach, 214 e-commerce web sites, 255 Scalable methods, 24, 102–103 early, 115–119 multidimensional, 184 energy systems, 255 Scenarios, 7, 211, 230–233, 280 executing risk mitigation, 88–90 contributions to system design phases, handling options assessment, 85 232 identification of hazards when overview, 230 conducting, 257–259 in participatory analysis, 172 risk-driven activity levels and anchor shared representations, 231–232 point milestones, 32–33 strengths, limitations, and gaps, 233 techniques for, 255 uses of methods, 230–231 transportation systems, 255 Scenarios for the future, 277–295 weapons systems, 255 integrated methodology, 278–286 Risk mitigation, 87–88 knowledge-based planning for HSI, best practices for, 67–74 286–287 developing a plan, 88–89 user participation, 288–295 evaluating plan activities, 90 Schematic representations, for a compact evaluating success accomplishments, 90 power plant control room, 204 executing, 88–90 Screening. See Security screening identifying fallback plans, 89 Seaports. Read the entire page →
From page 379... ... See Service-oriented architectures in the design process, 64–66 Social network analysis, 185 for evaluation, 254 "Social software" services, 22, 289 flow model, 176 "Social tagging," 22 and FMEA, 259–260 Socially constructed processes, design as, and FTA, 260–262 61, 63 future-vision stories, 232 Sociotechnical systems approach, 141, futures table, 144 148–149 individual stories, 231 Software models, with integrated usability input/output system diagram, 142 tests, 119–120 organization charts, 141–142 Software Technology Risk Advisor, 311 physical model, 176 "Sourcing," of information, 22 providing a basis for controlling costs, Space program, 248. See also National 195 Aeronautics and Space reducing risk of product failure, 195 Administration reducing the development effort, 195 Special causes, 141 and role networks, 142–144 Spimes, 294 sequence model, 176 Spiral models, 34, 37, 39, 47–49 for specification of requirements, 195 development of, 35 table of organizational variances, 142 simplified view of the ICM, 48 tracking evolving requirements by win-win, 51 providing a format to document Spreadsheets, 5, 25 usability requirements, 195 Stacking requirements, 113–114 usefulness of, 62–63 "Staged world" techniques, 163–164 Shared representations for communication, Stakeholders, 2, 5, 11 5, 100–101 analyzing, 148–149 among members of the development concurrence of, 40 team, 195 conflicting requirements of, 15 Read the entire page →
From page 380... ... , 120–121 emergent, 33 Synergy between research and practice evolving nature of, 33–34 fostering more, 7, 314 rapid change, 33 lack of, 14 reusable components, 33 System design phases, 11 System resilience. See Resilience architecting and design, 247 System safety, in the military sector, 18 contributions to, 149, 160, 167, System scoping, 3 185–186, 196, 205–206, 209, 222, System simulations. Read the entire page →
From page 381... ... See also Themes, 23–27 Methods; Uses of methods adopting a risk-driven approach, 23–24 expert-based evaluation, 272 creating shared representations for product usability characteristics communication, 25 evaluation, 271–272 designing to accommodate changing user behavior evaluation, 268–270 conditions and requirements in the Types of models and simulations, 240–246 workplace, 26 digital human physical simulations, integrating HSI contributions across 243–244 life-cycle phases and human-system human-in-the-loop simulation, 240–241 domains, 27 models derived from human cognitive tailoring methods to time and budget operations, 242–243 constraints, 24 models that mimic human cognitive and Theory-based analysis, 99 perceptual-motor behavior, 244–246 Theory W approach, 38 network models of human-system THERP. See Technique for human error performance, 241–242 rate prediction signal detection theory, 242 Think-aloud protocols, 225 Read the entire page →
From page 382... ... Navy, 18–19, 250 an existing system, 270 U.S. Rehabilitation Act, 245 User-centered design process in the ICM US WEST, 13 context, 106–124 Usability activities for stakeholder requirements, approaches to ensuring, 266 196 contributions to system design phases, contextual inquiry, 114–115 196, 273 design decisions, 109 evaluation methods, 5, 232, 265–274 early risk management, 115–119 of an existing system, measuring, 193 feature needs and their rationales, improving the use of objectives, 110–114 324–326 field studies, 123 overview, 191–192, 265–266 focus groups, 122 practitioners of, 274 instructions for use development and quantifying, 325 testing, 123 setting objectives, 115 integrated hardware and software shared representations, 194–195, 273 models, 119–120 strengths, limitations, and gaps, 197, iterative usability tests, 122 273–274 life-cycle planning, 124 tools to support capture and preliminary research, 108–109 dissemination of results, 315–316 product introduction, 124 uses and types of methods, 193–194, prototypes, 119 266–272 revised risk analysis, 124 walkthrough, 272 setting usability objectives, 115 Usability requirements, 191–197 tests of alarm criticality and alerting, specifying for new systems, 193–194 120–122 USC COCOMO/COSYSMO, 311 tests of display readability, 122 Use-error faults, 254 validation usability tests, 123–124 defining, 255–256 User-created dynamic pages, 22 risk analysis, 159, 255 Read the entire page →
From page 383... ... See Cognitive walkthroughs human digital modeling, 221 Warfare, limited or full-scale, 15 interpretation, 231 Waterfall models, 34 methods for assessing discomfort, 219 sequential, 34, 39 methods for assessing fatigue, 220–221 "Weak links," 330 methods for assessing injury risk, 221 Weapons systems, 255 methods for assessing posture, 220 Wearable technologies, 292 organizational system scan, 144–147 Web 2.0, 22, 26, 288, 290–291, 294, 305, other example applications, 203–205 316, 318 problem scenarios and claims, 231 Web metrics, 270 root concept, 231 Web sites, designing, 157 stakeholder analysis, 148–149 "Weblogs," 22, 289. See also "Blogs" strengths, limitations, and gaps, WebSAT, 272 187–188 Whole-systems approach, 139 use of work domain analysis in the port Wikipedia, 290 security case study, 202 Win-lose situations, 38 Uses of models and simulations, 240–246 Win-win spiral process, 51 digital human physical simulations, Wireframes, 119 243–244 Work-arounds, 26 human-in-the-loop simulation, 240–241 Work-centered design approaches, 139 models derived from human cognitive Work domain analysis, 197–207 operations, 242–243 contributions to system design phases, models that mimic human cognitive and 205–206 perceptual-motor behavior, 244–246 overview, 197–200 network models of human-system representation for a pressurized water performance, 241–242 reactor nuclear power plant, 200 signal detection theory, 242 shared representations, 201 USS Vincennes, Iranian Air Bus downed by, strengths, limitations, and gaps, 13, 328 206–207 UTOPIA project, 65, 239 use in the port security case study, 202 uses of methods, 201–205 Work flow V graphical representation of, 101 V-model, 37, 39 problems with, 187 updates, 34 Workload, managing, 19 Read the entire page →
From page 384... ... 8 HUMAN-SYSTEM INTEGRATION IN SYSTEM DEVELOPMENT Workload assessment, 207–210 Workshop methods, 213–214, 280. contributions to system design phases, See also Drawing workshops; 209 Future workshops; Participatory overview, 207–208 workshops; Strategic design shared representations, 209 workshops; Visual workshops strengths, limitations, and gaps, Workstations, 12 209–210 World War II, 10 use of method, 208 Workplace investigations, 175 X Workplace requirements, accommodation to, 101–102 XML interface, 22, 289 Y Yahoo! Read the entire page →

From page 365...

... , 44 AFQT. See Armed Forces Qualification Test procedures, 46 Aggregation, of features, 26 Architectures, back-end, 238 Agile methods, 35, 37 Armed Forces Aptitude Test Battery Air Force Falconer Air Operations Center, (ASVAB)

Index Pages 365-384

Index
Pages 365-384