Sommerville-Software-Engineering-10ed

786 Subject Index
high-availability systems, 172, 218
honesty (people management), 653
host-target development, 213, 216–18, 222
HTML5 programming, 28, 445
http and https protocols, 530–31
human error, 307, 351–52, 418–21
human needs hierarchy, 653–54
I
IDEs (Interactive Development Environments),
53, 217
ECLIPSE environment and, 218
general-purpose, 218
host-target development and, 216, 217–18, 222
repository architecture for, 180
iLearn, 38–39, 567. See also digital learning
environment
implementation (system implementation), 28, 47,
56–58, 69, 196–225
components, 465, 466, 471–72, 475, 487
configuration management, 212, 215–16
design and, 56–58, 69, 196–225
interface specification, 208–09
life-cycle phase, 47
host-target development, 213, 216–18
open-source development, 219–21
reuse and, 212, 213–215
service deployment and, 540–41
service-oriented software for, 28
UML documentation, 197, 198–209
unit testing and, 47
in-car information system, 522–24
inception phase (RUP), 46
inclusion (people management), 653, 657
incompatibility, component composition
and, 481–83
incremental delivery, 46, 51, 62, 64–65,
76, 91
incremental development, 46, 50–51, 73–74, 77
incremental testing, 59, 242
incremental integration, 242
incremental planning, 78
information loss, 286
information systems, 32, 185–86, 187–89, 522–24
infrastructure security, 374, 375–76
inheritance, 152, 204, 209, 233, 722. See also
generalization
input/output mapping, 310–11
inputs, validity checks of, 326–27, 399
inspections, 229–30, 239, 710–714. See
also reviews
insulin pump control system, 32–34
activity model of, 33, 155
data-flow model (DMD) for, 155
dependability properties for, 288–89
failure in, 316–17
functional reliability requirements, 317
hardware components (diagram), 33
hazards in, 346
natural language specification for, 122
non-functional reliability requirements, 316–17
permanent software failure, 316
risk classification for, 347–49
risk reduction for, 351–52
safety-critical system control, 341
safety requirements for, 346–349, 351–52
safe state, 351
sequence diagrams for, 155
software control of, 341
software failure solutions, 351–52
structured language specification for, 123–24
tabular specification for, 124
transient software failure, 316
issue-tracking systems, 746–47
integrated application systems, 442, 454
integration
configuration and, 46, 52–54
continuous, 78, 742–43
system development and, 570
system testing and, 48
systems of systems (SoS), 595, 597–99
integrity, security and, 374, 413
intellectual property rights, 28
interacting workflows, 545–46
interaction models, 144–49, 163, 199–200,
496–97
distributed systems, 496–97
object-oriented design and, 199–200
sequence diagrams, 146–49, 163
use cases, 144–46, 163, 200
interactive applications, 25
interface design, 57, 208–09
interface misunderstanding, 238
interface misuse, 238