Sommerville-Software-Engineering-10ed

Recommendations

Info

538 Chapter 18 ■ Service-oriented software engineeringOperation Inputs Outputs ExceptionsMakeCatalogmcInCompany idPDF-flagmcOutURL of the catalog forthat companymcFaultInvalid company idLookuplookInCatalog URLCatalog numberlookOutURL of page with theitem informationlookFaultInvalid catalognumberSearchsearchInCatalog URLSearch stringsearchOutURL of web page withsearch resultssearchFaultBadly formed searchstringComparecompInCatalog URLEntry attribute (up to 6)Catalog number (up to 4)compOutURL of page showingcomparison tablecompFaultInvalid company idInvalid catalog numberUnknown attributeCheckDeliverycdInCompany idCatalog numberNumber of items requiredcdOutExpected deliverydatecdFaultInvalid company idNo availabilityZero items requestedMakeVirtualOrdervoInCompany idCatalog numberNumber of items requiredvoOutCatalog numberNumber of itemsrequiredPredicted delivery dateUnit price estimateTotal price estimatevoFaultInvalid company idInvalid catalognumberZero items requestedFigure 18.11 Cataloginterface designcdIncID: stringcatNum: stringnumItems: integersize (cID) = 6size (catNum) = 10numItems > 0cdOutcatNum: stringdelivDate: datesize (catNum) = 10delivDate > TodayFigure 18.12 UMLdefinition of input andoutput messagescdFaulterrCode: integerInvalid company iderrCode=1Invalid catalog numbererrCode = 2No availabilityerrCode = 3Zero items requestederrCode = 4
18.3 ■ Service engineering 539Notice how I have added detail to the description by annotating the UML diagramwith constraints. These details define the length of the strings representing the companyand the catalog item, and specify that the number of items must be greater thanzero and that delivery must be after the current date. The annotations also showwhich error codes are associated with each possible fault.The catalog service is an example of a practical service, which illustrates that it isnot always straightforward whether to choose a RESTful or a SOAP-based approachto service implementation. As an entity-based service, the catalog can be representedas a resource, which suggests that a RESTful model is the right one to use. However,operations on the catalog are not simple GET operations, and you need to maintainsome state in an interaction session with the catalog. This suggests the use of a SOAPbasedapproach. Such dilemmas are common in service engineering, and usuallylocal circumstances (e.g., availability of expertise) are a major factor in the decisionof which approach to use.To implement a set of RESTful services, you have to decide on the set of resourcesthat will be used to represent the catalog and how the fundamental GET, POST, andPUT operations will operate on these resources. Some of these design decisions arestraightforward:1. There should be a resource representing a company-specific catalog. This shouldhave a URL of the form <base catalog>/<company name> and should be createdusing a POST operation.2. Each catalog item should have its own URL of the form <base catalog>/<companyname>/<item identifier>.3. You use the GET operation to retrieve items. Lookup is implemented by using theURL of an item in a catalog as the GET parameter. Search is implemented by usingGET with the company catalog as the URL and the search string as a query parameter.This GET operation returns a list of URLs of the items matching the search.However, the Compare, CheckDelivery, and MakeVirtualOrder operations aremore complex:1. The Compare operation can be implemented as a sequence of GET operations toretrieve the individual items, followed by a POST operation to create the comparisontable and a final GET operation to return this to the user.2. The CheckDelivery and MakeVirtualOrder operations require an additionalresource, representing a virtual order. A POST operation is used to create thisresource with the number of items required. The company id is used to automaticallyfill in the order form, and the delivery date is calculated. The resourcecan then be retrieved using a GET operation.You need to think carefully about how exceptions are mapped onto the standardhttp response codes such as a 404 code, meaning that a URL cannot be retrieved.I don’t have space to go into this issue here, but it adds a further level of complexityto the service interface design.
Page 1 and 2:
GlobaleditionSoftware EngineeringTE
Page 3:
Editorial Director: Marcia HortonEd
Page 6 and 7:
4 Preface2. I write about what I kn
Page 8 and 9:
6 PrefaceIf your course has a pract
Page 10 and 11:
Contents at a glancePreface 3Part 1
Page 12 and 13:
10 ContentsChapter 4 Requirements e
Page 14 and 15:
12 ContentsChapter 13 Security engi
Page 16 and 17:
14 ContentsPart 4 Software Manageme
Page 18 and 19:
extensively changed from previous e
Page 20 and 21:
18 Chapter 1 ■ IntroductionSoftwa
Page 22 and 23:
20 Chapter 1 ■ IntroductionQuesti
Page 24 and 25:
22 Chapter 1 ■ IntroductionProduc
Page 26 and 27:
24 Chapter 1 ■ Introduction1. Het
Page 28 and 29:
26 Chapter 1 ■ IntroductionOf cou
Page 30 and 31:
28 Chapter 1 ■ Introduction1. Sof
Page 32 and 33:
30 Chapter 1 ■ IntroductionComput
Page 34 and 35:
32 Chapter 1 ■ Introductionbeing
Page 36 and 37:
34 Chapter 1 ■ IntroductionMentca
Page 38 and 39:
36 Chapter 1 ■ Introduction3. Adm
Page 40 and 41:
38 Chapter 1 ■ Introduction3. All
Page 42 and 43:
40 Chapter 1 ■ IntroductionKey Po
Page 44 and 45:
42 Chapter 1 ■ Introduction1.9. F
Page 46 and 47:
44 Chapter 2 ■ Software processes
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
3Agile softwaredevelopmentObjective
Page 76 and 77:
74 Chapter 3 ■ Agile software dev
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
100 Chapter 3 ■ Agile Software so
Page 104 and 105:
102 Chapter 4 ■ Requirements engi
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
5System modelingObjectivesThe aim o
Page 142 and 143:
140 Chapter 5 ■ System modelingTh
Page 144 and 145:
142 Chapter 5 ■ System modeling«
Page 146 and 147:
144 Chapter 5 ■ System modelingFi
Page 148 and 149:
146 Chapter 5 ■ System modelingRe
Page 150 and 151:
148 Chapter 5 ■ System modelingMe
Page 152 and 153:
Page 154 and 155:
152 Chapter 5 ■ System modelingDo
Page 156 and 157:
154 Chapter 5 ■ System modelingDa
Page 158 and 159:
156 Chapter 5 ■ System modelingFu
Page 160 and 161:
Page 162 and 163:
160 Chapter 5 ■ System modelingCo
Page 164 and 165:
162 Chapter 5 ■ System modelingEx
Page 166 and 167:
164 Chapter 5 ■ System modelingWe
Page 168 and 169:
166 Chapter 5 ■ System modelingRu
Page 170 and 171:
168 Chapter 6 ■ Architectural des
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
7Design andimplementationObjectives
Page 200 and 201:
198 Chapter 7 ■ Design and implem
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
224 Chapter 17 ■ Design and Imple
Page 228 and 229:
8Software testingObjectivesThe obje
Page 230 and 231:
228 Chapter 8 ■ Software testingI
Page 232 and 233:
230 Chapter 8 ■ Software testingT
Page 234 and 235:
232 Chapter 8 ■ Software testingD
Page 236 and 237:
234 Chapter 8 ■ Software testing2
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
242 Chapter 8 ■ Software testingI
Page 246 and 247:
244 Chapter 8 ■ Software testingt
Page 248 and 249:
246 Chapter 8 ■ Software testingF
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
252 Chapter 8 ■ Software testingK
Page 256 and 257:
254 Chapter 8 ■ Software testingR
Page 258 and 259:
256 Chapter 9 ■ Software evolutio
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
More and more systems are safety-cr
Page 288 and 289:
286 Chapter 10 ■ Dependable syste
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
11Reliability engineeringObjectives
Page 310 and 311:
308 Chapter 11 ■ Reliability engi
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
Page 318 and 319:
Page 320 and 321:
Page 322 and 323:
Page 324 and 325:
Page 326 and 327:
Page 328 and 329:
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 342 and 343:
340 Chapter 12 ■ Safety engineeri
Page 344 and 345:
Page 346 and 347:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
Page 354 and 355:
Page 356 and 357:
Page 358 and 359:
Page 360 and 361:
Page 362 and 363:
Page 364 and 365:
Page 366 and 367:
Page 368 and 369:
Page 370 and 371:
Page 372 and 373:
Page 374 and 375:
Page 376 and 377:
374 Chapter 13 ■ Security enginee
Page 378 and 379:
Page 380 and 381:
Page 382 and 383:
Page 384 and 385:
Page 386 and 387:
Page 388 and 389:
Page 390 and 391:
Page 392 and 393:
Page 394 and 395:
Page 396 and 397:
Page 398 and 399:
Page 400 and 401:
Page 402 and 403:
Page 404 and 405:
Page 406 and 407:
Page 408 and 409:
Page 410 and 411:
14Resilience engineeringObjectivesT
Page 412 and 413:
410 Chapter 14 ■ Resilience engin
Page 414 and 415:
Page 416 and 417:
Page 418 and 419:
Page 420 and 421:
Page 422 and 423:
Page 424 and 425:
Page 426 and 427:
Page 428 and 429:
Page 430 and 431:
Page 432 and 433:
Page 434 and 435:
Page 436 and 437:
Page 438 and 439:
Chapter 18 introduces the related t
Page 440 and 441:
438 Chapter 15 ■ Software reuseRe
Page 442 and 443:
440 Chapter 15 ■ Software reusePr
Page 444 and 445:
442 Chapter 15 ■ Software reuseAp
Page 446 and 447:
444 Chapter 15 ■ Software reuseUs
Page 448 and 449:
446 Chapter 15 ■ Software reuseFa
Page 450 and 451:
448 Chapter 15 ■ Software reuseco
Page 452 and 453:
450 Chapter 15 ■ Software reuseEl
Page 454 and 455:
452 Chapter 15 ■ Software reuseCo
Page 456 and 457:
454 Chapter 15 ■ Software reuseCo
Page 458 and 459:
456 Chapter 15 ■ Software reuse4.
Page 460 and 461:
458 Chapter 15 ■ Software reuseCl
Page 462 and 463:
460 Chapter 15 ■ Software reusere
Page 464 and 465:
462 Chapter 15 ■ Software reuseEx
Page 466 and 467:
16Component-basedsoftware engineeri
Page 468 and 469:
466 Chapter 16 ■ Component-based
Page 470 and 471:
Page 472 and 473:
Page 474 and 475:
Page 476 and 477:
Page 478 and 479:
Page 480 and 481:
Page 482 and 483:
Page 484 and 485:
Page 486 and 487:
Page 488 and 489:
Page 490 and 491: 488 Chapter 16 ■ Component-based
Page 492 and 493: 17Distributed softwareengineeringOb
Page 494 and 495: 492 Chapter 17 ■ Distributed soft
Page 522 and 523: 18Service-orientedsoftware engineer
Page 524 and 525: 522 Chapter 18 ■ Service-oriented
Page 554 and 555: 552 Chapter 19 ■ Systems engineer
Page 582 and 583: 20Systems of systemsObjectivesThe o
Page 584 and 585: 582 Chapter 20 ■ Systems of syste
Page 590 and 591:
588 Chapter 20 ■ Systems of syste
Page 592 and 593:
Page 594 and 595:
Page 596 and 597:
Page 598 and 599:
Page 600 and 601:
Page 602 and 603:
Page 604 and 605:
Page 606 and 607:
Page 608 and 609:
Page 610 and 611:
Page 612 and 613:
21Real-time softwareengineeringObje
Page 614 and 615:
612 Chapter 21 ■ Real-time softwa
Page 616 and 617:
Page 618 and 619:
Page 620 and 621:
Page 622 and 623:
Page 624 and 625:
Page 626 and 627:
Page 628 and 629:
Page 630 and 631:
Page 632 and 633:
Page 634 and 635:
Page 636 and 637:
Page 638 and 639:
Page 640 and 641:
This page intentionally left blank
Page 642 and 643:
Chapters 24 explains the basics of
Page 644 and 645:
642 Chapter 22 ■ Project manageme
Page 646 and 647:
Page 648 and 649:
Page 650 and 651:
Page 652 and 653:
Page 654 and 655:
Page 656 and 657:
Page 658 and 659:
Page 660 and 661:
Page 662 and 663:
Page 664 and 665:
Page 666 and 667:
Page 668 and 669:
Page 670 and 671:
668 Chapter 23 ■ Project planning
Page 672 and 673:
Page 674 and 675:
Page 676 and 677:
Page 678 and 679:
Page 680 and 681:
Page 682 and 683:
Page 684 and 685:
Page 686 and 687:
Page 688 and 689:
Page 690 and 691:
Page 692 and 693:
Page 694 and 695:
Page 696 and 697:
Page 698 and 699:
Page 700 and 701:
Page 702 and 703:
24Quality managementObjectivesThe o
Page 704 and 705:
702 Chapter 24 ■ Quality manageme
Page 706 and 707:
Page 708 and 709:
Page 710 and 711:
Page 712 and 713:
Page 714 and 715:
Page 716 and 717:
Page 718 and 719:
Page 720 and 721:
Page 722 and 723:
Page 724 and 725:
Page 726 and 727:
Page 728 and 729:
Page 730 and 731:
Page 732 and 733:
25ConfigurationmanagementObjectives
Page 734 and 735:
732 Chapter 25 ■ Configuration ma
Page 736 and 737:
Page 738 and 739:
Page 740 and 741:
Page 742 and 743:
Page 744 and 745:
Page 746 and 747:
Page 748 and 749:
Page 750 and 751:
Page 752 and 753:
Page 754 and 755:
Page 756 and 757:
Page 758 and 759:
Page 760 and 761:
758 Glossarybureaucracy are minimiz
Page 762 and 763:
760 Glossaryclient-server architect
Page 764 and 765:
762 Glossarydenial of service attac
Page 766 and 767:
764 GlossaryGitA distributed versio
Page 768 and 769:
766 Glossarymodel checkingA method
Page 770 and 771:
768 Glossaryprogram evolution dynam
Page 772 and 773:
770 GlossaryRESTREST (Representatio
Page 774 and 775:
772 Glossarysoftware processThe act
Page 776 and 777:
774 Glossaryuser interface designTh
Page 778 and 779:
Page 780 and 781:
778 Subject IndexAirbus 340 flight
Page 782 and 783:
780 Subject Indexchange anticipatio
Page 784 and 785:
782 Subject Indexdata-driven modeli
Page 786 and 787:
784 Subject Indexenvironments. See
Page 788 and 789:
786 Subject Indexhigh-availability
Page 790 and 791:
788 Subject Indexmanagement (softwa
Page 792 and 793:
790 Subject Indexoperating system l
Page 794 and 795:
792 Subject Indexprotection, 383ass
Page 796 and 797:
794 Subject Indexreuse (continued)a
Page 798 and 799:
796 Subject Indexservice-to-service
Page 800 and 801:
798 Subject Indexsystem design (con
Page 802 and 803:
800 Subject IndexUML (continued)sub
Page 804 and 805:
Author IndexAAbbott, R., 202, 224Ab
Page 806 and 807:
Author Index 805EEbert, C., 611, 63
Page 808 and 809:
Author Index 807Loeliger, J., 216,
Page 810 and 811:
Author Index 809Souyris, J., 356, 3
show all

Sommerville-Software-Engineering-10ed

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

Delete template?

Save as template?