21.01.2022 Views

Sommerville-Software-Engineering-10ed

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

796 Subject Index

service-to-service communication, see

integrated services

services, 521

business, 534, 541–47, 548

classification of, 534, 548

communication and, 524–29

components, 521, 526–29

composition (construction) of, 541–47

coordination, 534, 548

incremental delivery and, 64–65

operation and maintenance for, 48

process models for, 544–46

reusable Web components, 52, 526–29

reuse of, 542

software development and, 541–47, 548

testing, 543, 546–47

utility, 534, 548

web-based, 27–28, 521

RESTful approach, 524, 529–33, 544

service information exchange (SOAP), 525–26,

531, 544

workflow, 542, 543, 544–46, 548

servicing, evolution v., 257–58

shared memory interfaces, 238

signatures, 744–45

simple design, 78

simplicity (agile methods), 76, 78, 91

simulation systems, 25

simulators, 217

size checks, 327

SLAM model checker, 358

small releases, 78

social change, business and, 24

social layer, 292

sociotechnical systems, 552, 577

complexity of, 556, 558–59

defensive layers, 419–20

emergent properties 544, 559–61, 577

environment and software interaction,

293–94

failure propagation, 560–61

human error and, 418–21

layers of, 292–93, 557

management, 421–24, 432

nested technical systems, 416–17

non-deterministic properties, 561–62

operational processes, 421–24, 432

organizational elements, 557–58

regulation and compliance, 294–95

resilience and, 416–24

success criteria, 562–63

systems engineering for, 556–59

software, 19, 20, 228

attributes, 20, 22

customized (bespoke), 21

efficiency, 22

engineering ethics, 28–31

failures, 18

generic products, 20–21

issues affecting, 24

lifetime, 256–57

product types, 20–21, 24–26

professional development, 19–28

regulation and compliance of, 294–95

system boundaries and characteristics, 26

software architecture catalog, Booch’s, 170

software as service (SaS), 512–16, 517

configuration of, 514–15

multi-tenancy, 514, 515, 516

scalability, 514, 515–16

server overload and, 512–13

service-oriented architectures (SOAs) v.,

513–14, 522

‘software crisis’, 19

Software Development Life Cycle (SDLC) model, 45

software development tools, 53

software diversity, 318, 322, 323–25, 336

software engineering, 19–23, 40, 92

activities for software process, 20, 23, 44

computer science v., 20, 23

diversity, 24–27

engineering discipline, 21–22

ethical responsibility and, 28–31, 40

formal verification, 356–58

fundamental notions in, 26, 40

Internet effect on, 20, 27–28

licensing for, 356

model checking, 358–59, 368

model-driven engineering (MDE), 158–59

product development and, 20–21

reuse-based, 53–54, 438

safety processes, 352–61

static program analysis, 359–61, 368

systems engineering v., 20, 23, 40, 554

web-based systems, 27–28

Software Engineering Institute (SEI), 67

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!