Sommerville-Software-Engineering-10ed

Subject Index 795
safety-critical systems, 287, 340–44, 368
certification of, 294, 302, 355–56
control systems, 341–42
dependability and, 294, 302
development process and, 352–53
error-prone constructs and, 329
hazard-driven techniques, 342
primary safety-critical software, 341
process assurance and, 355–56
regulation and compliance for, 294, 353
risk triangle for, 347–48
secondary safety-critical software, 341–42
system failure and, 340–41
safety reviews, 355
SAP, 21
Sarbanes Oxley accounting regulations, 51
scalability, 491, 492, 494, 514, 515–16
scale, software development and, 24
scaling agile methods, 88–97, 98
scenarios
elicitation of requirements from, 118–20
testing, 246–47, 252
use cases, 125–26
scheduling, 675–80, 696
activity charts for, 678–80
project planning and, 675–80, 696
plan-driven projects, 675–76
presentation (visualizing), 676–80
Scrum, 73, 78, 85–88, 96, 98
secure systems, 561
security, 24, 26, 373–407
application, 374–375
architectural design and, 172, 388,
392–95
assurance, 402–04
availability, 374, 375, 379
checklist, 403
confidentiality, 374
controls, 377, 378–79
dependability and, 22, 26, 288, 376–79
design for, 374, 388–402, 405
engineering, 373–407
failure, 397
guidelines, 396–401, 404
infrastructure, 374, 375–76
logging user actions, 398
operational, 374, 376
organizations and, 380–82
policies, 396–97
programming guidelines, 401–02
protection, 380, 384, 390, 393–94, 395
regulation and compliance for, 294–95
reliability and, 379
requirements, 382–88
resilience and, 288, 379
risk assessment, 381–82, 405
safety and, 379
system layers, 374–75
terminology, 377–378
testing, 402–04
threats, 377, 378, 404
trust and, 22, 24
usability guideline, 397–98
validation, 405
vulnerability and, 377, 378, 391, 401
self-monitoring architecture, 320–22
SEMAT (software engineering methods and tools)
initiative, 24
semicentralized P2P architecture, 511, 512
sensor-based data collection systems, 32
separation of concerns, 486
sequence diagrams, 141, 144, 146–49, 155, 163, 205,
206–07, 241
sequential composition, 480
server overload, 512–13
service engineering, 533–41
candidate identification, 533–36
implementation and deployment, 540–41
interface design, 533, 536–40
legacy systems and, 540
service information exchange (SOAP), 525–26,
531, 544
service-oriented architectures (SOAs), 513–14,
520–50
approach, 522, 524
components, 526–29
message exchange, 526–29
service interface, 528
service protocols, 525
software as service (SaS) v.,
513–14, 522
standards, 525–26
web applications, 524–29
WSDL and, 526, 527–29
service-oriented software engineering, see service
engineering; service-oriented architectures
(SOAs); services
service-oriented systems, 442, 466–67, 526–33