Object oriented & classical software engineering:
Saved in:
| Main Author: | |
|---|---|
| Format: | Book |
| Language: | English |
| Published: |
Boston [u.a.]
McGraw-Hill
2007
|
| Edition: | 7. ed. |
| Subjects: | |
| Online Access: | Inhaltsverzeichnis |
| Physical Description: | XX, 618 S. graph. Darst. |
| ISBN: | 0073191264 9780073191263 |
Staff View
MARC
| LEADER | 00000nam a2200000 c 4500 | ||
|---|---|---|---|
| 001 | BV021403844 | ||
| 003 | DE-604 | ||
| 005 | 20070109 | ||
| 007 | t| | ||
| 008 | 060214s2007 xx d||| |||| 00||| eng d | ||
| 020 | |a 0073191264 |9 0-07-319126-4 | ||
| 020 | |a 9780073191263 |9 978-0-07-319126-3 | ||
| 035 | |a (OCoLC)255940791 | ||
| 035 | |a (DE-599)BVBBV021403844 | ||
| 040 | |a DE-604 |b ger |e rakwb | ||
| 041 | 0 | |a eng | |
| 050 | 0 | |a QA76.758 | |
| 082 | 0 | |a 005.1 |2 22 | |
| 084 | |a ST 230 |0 (DE-625)143617: |2 rvk | ||
| 100 | 1 | |a Schach, Stephen R. |e Verfasser |4 aut | |
| 245 | 1 | 0 | |a Object oriented & classical software engineering |c Stephen R. Schach |
| 246 | 1 | 3 | |a Object-oriented & classical software engineering |
| 246 | 1 | 3 | |a Object-oriented and classical software engineering |
| 246 | 1 | 3 | |a Object oriented and classical software engineering |
| 250 | |a 7. ed. | ||
| 264 | 1 | |a Boston [u.a.] |b McGraw-Hill |c 2007 | |
| 300 | |a XX, 618 S. |b graph. Darst. | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b n |2 rdamedia | ||
| 338 | |b nc |2 rdacarrier | ||
| 650 | 4 | |a C++ (Computer program language) | |
| 650 | 4 | |a Object-oriented programming (Computer science) | |
| 650 | 4 | |a Software engineering | |
| 650 | 4 | |a UML (Computer science) | |
| 650 | 0 | 7 | |a Objektorientierte Analyse |0 (DE-588)4504809-5 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Software Engineering |0 (DE-588)4116521-4 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Objektorientierte Programmierung |0 (DE-588)4233947-9 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Objektorientierung |0 (DE-588)4346172-4 |2 gnd |9 rswk-swf |
| 655 | 7 | |8 1\p |0 (DE-588)4123623-3 |a Lehrbuch |2 gnd-content | |
| 689 | 0 | 0 | |a Software Engineering |0 (DE-588)4116521-4 |D s |
| 689 | 0 | 1 | |a Objektorientierung |0 (DE-588)4346172-4 |D s |
| 689 | 0 | |8 2\p |5 DE-604 | |
| 689 | 1 | 0 | |a Software Engineering |0 (DE-588)4116521-4 |D s |
| 689 | 1 | 1 | |a Objektorientierte Analyse |0 (DE-588)4504809-5 |D s |
| 689 | 1 | |8 3\p |5 DE-604 | |
| 689 | 2 | 0 | |a Objektorientierte Programmierung |0 (DE-588)4233947-9 |D s |
| 689 | 2 | |8 4\p |5 DE-604 | |
| 856 | 4 | 2 | |m GBV Datenaustausch |q application/pdf |u http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=014655432&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |3 Inhaltsverzeichnis |
| 883 | 1 | |8 1\p |a cgwrk |d 20201028 |q DE-101 |u https://d-nb.info/provenance/plan#cgwrk | |
| 883 | 1 | |8 2\p |a cgwrk |d 20201028 |q DE-101 |u https://d-nb.info/provenance/plan#cgwrk | |
| 883 | 1 | |8 3\p |a cgwrk |d 20201028 |q DE-101 |u https://d-nb.info/provenance/plan#cgwrk | |
| 883 | 1 | |8 4\p |a cgwrk |d 20201028 |q DE-101 |u https://d-nb.info/provenance/plan#cgwrk | |
| 943 | 1 | |a oai:aleph.bib-bvb.de:BVB01-014655432 | |
Record in the Search Index
| _version_ | 1828141358728085504 |
|---|---|
| adam_text |
OBJECT-ORIENTED & CLASSICAL SOFT ENGINEERING SEVENTH EDITION STEPHEN R.
SCHACH VANDERBILT UNIVERSITY HIGHER EDUCATION BOSTON BURR RIDGE, IL
DUBUQUE, IA NEW YORK SAN FRANCISCO ST. LOUIS BANGKOK BOGOTA CARACAS
KUALA LUMPUR LISBON LONDON MADRID MEXICO CITY MILAN MONTREAL NEW DELHI
SANTIAGO SEOUL SINGAPORE SYDNEY TAIPEI TORONTO CONTENTS PREFACE V PART
ONE INTRODUCTION TO SOFTWARE ENGINEERING 1 CHAPTER 1 THE SCOPE OF
SOFTWARE ENGINEERING 3 LEARNING OBJECTIVES 3 1.1 HISTORICAL ASPECTS 4
1.2 ECONOMIC ASPECTS 7 1.3 MAINTENANCE ASPECTS 8 1.3.1 CLASSICAL AND
MODERN VIEWS OF MAINTENANCE 9 1.3.2 THE IMPORTANCE OF POSTDELIVERY
MAINTENANCE 11 1.4 REQUIREMENTS, ANALYSIS, AND DESIGN ASPECTS 13 1.5
TEAM DEVELOPMENT ASPECTS 16 1.6 WHY THERE 1S NO PLANNING PHASE 17 1.7
WHY THERE IS NO TESTING PHASE 17 1.8 WHY THERE IS NO DOCUMENTATION PHASE
18 1.9 THE OBJECT-ORIENTED PARADIGM 19 1.10 THE OBJECT-ORIENTED PARADIGM
IN PERSPECTIVE 23 1.11 TERMINOLOGY 24 1.12 ETHICAL ISSUES 27 CHAPTER
REVIEW 28 FOR FURTHER READING 28 KEY TERMS 29 PROBLEMS 30 REFERENCES 31
CHAPTER 2 SOFTWARE LIFE-CYCLE MODELS 35 LEARNING OBJECTIVES 35 2.1
SOFTWARE DEVELOPMENT IN THEORY 35 2.2 WINBURG MINI CASE STUDY 36 2.3
LESSONS OF THE WINBURG MINI CASE STUDY 40 2.4 TEAL TRACTORS MINI CASE
STUDY 40 2.5 ITERATION AND INCREMENTATION 41 2.6 WINBURG MINI CASE STUDY
REVISITED 45 2.7 RISKS AND OTHER ASPECTS OF ITERATION AND INCREMENTATION
46 2.8 MANAGING ITERATION AND INCREMENTATION 49 2.9 OTHER LIFE-CYCLE
MODELS 50 2.9.1 CODE-AND-FIX LIFE-CYCLE MODEL 50 2.9.2 WATERFALL
LIFE-CYCLE MODEL 51 2.9.3 RAPID-PROTOTYPING LIFE-CYCLE MODEL 53 2.9.4
OPEN-SOURCE LIFE-CYCLE MODEL 54 2.9.5 AGILE PROCESSES 57 2.9.6
SYNCHRONIZE-AND-STABILIZE LIFE-CYCLE MODEL 60 2.9.7 SPIRAL LIFE-CYCLE
MODEL 60 2.10 COMPARISON OF LIFE-CYCLE MODELS 64 CHAPTER REVIEW 65 FOR
FURTHER READING 66 KEY TERMS 67 PROBLEMS 67 REFERENCES 68 CHAPTER 3 THE
SOFTWARE PROCESS 71 LEARNING OBJECTIVES 71 3.1 THE UNIFIED PROCESS 73
3.2 ITERATION AND INCREMENTATION WITHIN THE OBJECT-ORIENTED PARADIGM 73
3.3 THE REQUIREMENTS WORKFLOW 75 3.4 THE ANALYSIS WORKFLOW 77 3.5 THE
DESIGN WORKFLOW 79 3.6 THE IMPLEMENTATION WORKFLOW 80 3.7 THE TEST
WORKFLOW 81 3.7.1 REQUIREMENTS ARTIFACTS 81 3.7.2 ANALYSIS ARTIFACTS 81
3.7.3 DESIGN ARTIFACTS 82 3.7.4 IMPLEMENTATION ARTIFACTS 82 XIII XIV
CONTENTS 3.8 POSTDELIVERY MAINTENANCE 84 3.9 RETIREMENT 85 3.10 THE
PHASES OF THE UNIFIED PROCESS 85 3.10.1 THE INCEPTION PHASE 86 3.10.2
THE ELABORATION PHASE 88 3.10.3 THE CONSTRUCTION PHASE 89 3.10.4 THE
TRANSITION PHASE 89 3.11 ONE- VERSUS TWO-DIMENSIONAL LIFE-CYCLE MODELS
90 3.12 IMPROVING THE SOFTWARE PROCESS 92 3.13 CAPABILITY MATURITY
MODELS 92 3.14 OTHER SOFTWARE PROCESS IMPROVEMENT INITIATIVES 95 3.15
COSTS AND BENEFITS OF SOFTWARE PROCESS IMPROVEMENT 96 CHAPTER REVIEW 98
FOR FURTHER READING 98 KEY TERMS 99 PROBLEMS 100 REFERENCES 100 CHAPTER
4 TEAMS 104 LEARNING OBJECTIVES 104 4.1 TEAM ORGANIZATION 104 4.2
DEMOCRATIC TEAM APPROACH 106 4.2.1 ANALYSIS OFTHE DEMOCRATIC TEAM
APPROACH 107 4.3 CLASSICAL CHIEF PROGRAMMER TEAM APPROACH 107 4.3.1 THE
NEW YORK TIMES PROJECT 109 4.3.2 LMPRACTICALITY OFTHE CLASSICAL CHIEF
PROGRAMMER TEAM APPROACH 110 4.4 BEYOND CHIEF PROGRAMMER AND DEMOCRATIC
TEAMS 110 4.5 SYNCHRONIZE-AND-STABILIZE TEAMS 114 4.6 TEAMS FOR AGILE
PROCESSES 115 4.7 OPEN-SOURCE PROGRAMMING TEAMS 115 4.8 PEOPLE
CAPABILITY MATURITY MODEL 116 4.9 CHOOSING AN APPROPRIATE TEAM
ORGANIZATION 117 CHAPTER REVIEW 118 FOR FURTHER READING 118 KEY TERMS
118 PROBLEMS 119 REFERENCES 119 CHAPTER 5 THE TOOLS OF THE TRADE 121
LEARNING OBJECTIVES 121 5.1 STEPWISE REFINEMENT 121 5.1.1 STEPWISE
REFINEMENT MINI CASE STUDY 122 5.2 COST-BENEFIT ANALYSIS 127 5.3
SOFTWARE METRICS 129 5.4 CASE 130 5.5 TAXONOMYOFCASE 131 5.6 SCOPEOFCASE
133 5.7 SOFTWARE VERSIONS 136 5.7.1 REVISIONS 137 5.7.2 VARIATIONS 137
5.8 CONFIGURATION CONTROL 138 5.8.1 CONFIGURATION CONTROL DURING
POSTDELIVERY MAINTENANCE 140 5.8.2 BASELINES 140 5.8.3 CONFIGURATION
CONTROL DURING DEVELOPMENT 141 5.9 BUILD TOOLS 141 5.10 PRODUCTIVITY
GAINS WITH CASE TECHNOLOGY 142 CHAPTER REVIEW 144 FOR FURTHER READING
144 KEY TERMS 144 PROBLEMS 145 REFERENCES 146 CHAPTER 6 TESTING 149
LEARNING OBJECTIVES 149 6.1 QUALITY ISSUES 150 6.1.1 SOFTWARE QUALITY
ASSURANCE 151 6.1.2 MANAGERIAL INDEPENDENCE 151 6.2 NON-EXECUTION-BASED
TESTING 152 6.2.1 WALKTHROUGHS 153 6.2.2 MANAGING WALKTHROUGHS 153 6.2.3
INSPECTIONS 154 CONTENTS XV 6.2.4 COMPARISON OF INSPECTIONS AND
WALKTHROUGHS 156 6.2.5 STRENGTHS AND WEAKNESSES OF REVIEWS 157 6.2.6
METRICS FBR INSPECTIONS 157 6.3 EXECUTION-BASED TESTING 157 6.4 WHAT
SHOULD BE TESTED? 158 6.4.1 UTILITY 159 6.4.2 RELIABILITY 159 6.4.3
ROBUSTNESS 160 6.4.4 PERFORMANCE 160 6.4.5 CORRECTNESS 161 6.5 TESTING
VERSUS CORRECTNESS PROOFS 162 6.5.1 EXAMPLE OF A CORRECTNESS PROOF 162
6.5.2 CORRECTNESS PROOF MINI CASE STUDY 166 6.5.3 CORRECTNESS PROOFS AND
SOFTWARE ENGINEERING 167 6.6 WHO SHOULD PERFORM EXECUTION-BASED TESTING?
170 6.7 WHEN TESTING STOPS 171 CHAPTER REVIEW 171 FOR FURTHER READING
172 KEY TERMS 172 PROBLEMS 173 REFERENCES 174 CHAPTER 7 FROM MODULES TO
OBJECTS 177 LEARNING OBJECTIVES 177 7.1 WHAT IS A MODULE? 177 7.2
COHESION 181 7.2.1 COINCIDENTAL COHESION 181 7.2.2 LOGICAL COHESION 182
7.2.3 TEMPORAL COHESION 183 7.2.4 PROCEDURAL COHESION 183 7.2.5
COMMUNICATIONAL COHESION 184 7.2.6 FUNCTIONAL COHESION 184 7.2.7
INFORMATIONAL COHESION 185 7.2.8 COHESION EXAMPLE 185 7.3 COUPLING 186
7.3.1 CONTENT COUPLING 186 7.3.2 COMMON COUPLING 187 7.3.3 CONTROL
COUPLING 189 7.3.4 STAMP COUPLING 190 7.3.5 DATA COUPLING 191 7.3.6
COUPLING EXAMPLE 191 7.3.7 THE IMPORTANCE OF COUPLING 192 7.4 DATA
ENCAPSULATION 193 7.4.1 DATA ENCAPSULATION AND DEVELOPMENT 196 7.4.2
DATA ENCAPSULATION AND MAINTENANCE 197 7.5 ABSTRACT DATA TYPES 202 7.6
INFORMATION HIDING 203 7.7 OBJECTS 205 7.8 INHERITANCE, POLYMORPHISM,
AND DYNAMIC BINDING 209 7.9 THE OBJECT-ORIENTED PARADIGM 212 CHAPTER
REVIEW 214 FOR FURTHER READING 215 KEY TERMS 215 PROBLEMS 216 REFERENCES
217 CHAPTER 8 REUSABILITY AND PORTABILITY 219 LEARNING OBJECTIVES 219
8.1 REUSE CONCEPTS 220 8.2 IMPEDIMENTS TO REUSE 222 8.3 REUSE CASE
STUDIES 223 8.3.1 RAYTHEON MISSILE SYSTEMS DIVISION 224 8.3.2 EUROPEAN
SPACE AGENCY 225 8.4 OBJECTS AND REUSE 226 8.5 REUSE DURING DESIGN AND
IMPLEMENTATION 226 8.5.1 DESIGN REUSE 226 8.5.2 APPLIKATION FRAMEWORKS
228 8.5.3 DESIGN PATTERNS 229 8.5.4 SOFTWARE ARCHITECTURE 233 8.5.5
COMPONENT-BASED SOFTWARE ENGINEERING 233 8.6 REUSE AND POSTDELIVERY
MAINTENANCE 234 8.7 PORTABILITY 235 8.7.1 HARDWARE INCOMPATIBILITIES 235
8.7.2 OPERATING SYSTEM INCOMPATIBILITIES 236 8.7.3 NUMERICAL SOFTWARE
INCOMPATIBILITIES 236 8.7.4 COMPILER INCOMPATIBILITIES 237 XVI CONTENTS
8.8 WHY PORTABILITY? 241 8.9 TECHNIQUES FOR ACHIEVING PORTABILITY 241
8.9.1 PORTABLE SYSTEM SOFTWARE 242 8.9.2 PORTABLE APPLICATION SOFTWARE
242 8.9.3 PORTABLE DATA 243 CHAPTER REVIEW 244 FOR FURTHER READING 245
KEY TERMS 246 PROBLEMS 246 , REFERENCES 247 , CHAPTER 9 PLANNING AND
ESTIMATING 252 LEARNING OBJECTIVES 252 9.1 PLANNING AND THE SOFTWARE
PROCESS 253 9.2 ESTIMATING DURATION AND COST 254 9.2.1 METRICSFOR THE
SIZE OFA PRODUCT 256 9.2.2 TECHNIQUES OF COST ESTIMATION 259 9.2.3
INTERMEDIATE COCOMO 262 9.2.4 COCOMO II 265 9.2.5 TRACKING DURATION AND
COST ESTIMATES 266 9.3 COMPONENTS OF A SOFTWARE PROJECT MANAGEMENT PLAN
266 9.4 SOFTWARE PROJECT MANAGEMENT PLAN FRAMEWORK 268 9.5 IEEE SOFTWARE
PROJECT MANAGEMENT PLAN 270 9.6 PLANNING TESTING 273 9.7 PLANNING
OBJECT-ORIENTED PROJECTS 274 9.8 TRAINING REQUIREMENTS 274 9.9
DOCUMENTATION STANDARDS 275 9.10 CASE TOOLS FOR PLANNING AND ESTIMATING
276 9.1 1 TESTING THE SOFTWARE PROJECT MANAGEMENT PLAN 276 CHAPTER
REVIEW 276 FOR FURTHER READING 277 KEY TERMS 277 PROBLEMS 278 REFERENCES
279 PART TWO THE WORKFLOWS OF THE SOFTWARE LIFE CYCLE 283 CHAPTER 10
REQUIREMENTS 285 LEARNING OBJECTIVES 285 10.1 DETERMINING WHAT THE
CLIENT NEEDS 285 10.2 OVERVIEW OF THE REQUIREMENTS WORKFLOW 286 10.3
UNDERSTANDING THE DOMAIN 287 10.4 THE BUSINESS MODEL 288 10.4.1
INTERVIEWING 288 10.4.2 OTHER TECHNIQUES 289 10.4.3 USE CASES 290 10.5
INITIAL REQUIREMENTS 291 10.6 INITIAL UNDERSTANDING OF THE DOMAIN: THE
MSG FOUNDATION CASE STUDY 292 10.7 INITIAL BUSINESS MODEL: THE MSG
FOUNDATION CASE STUDY 294 1 0.8 INITIAL REQUIREMENTS: THE MSG FOUNDATION
CASE STUDY 298 1 0.9 CONTINUING THE REQUIREMENTS WORKFLOW: THE MSG
FOUNDATION CASE STUDY 300 10.10 REVISING THE REQUIREMENTS: THE MSG
FOUNDATION CASE STUDY 302 10.11 THE TEST WORKFLOW: THE MSG FOUNDATION
CASE STUDY 310 10.12 THE CLASSICAL REQUIREMENTS PHASE 319 10.13 RAPID
PROTOTYPING 320 10.14 HUMAN FACTORS 321 10.15 REUSING THE RAPID
PROTOTYPE 323 10.16 CASE TOOLS FOR THE REQUIREMENTS WORKFLOW 324 10.17
METRICS FOR THE REQUIREMENTS WORKFLOW 325 10.18 CHALLENGES OF THE
REQUIREMENTS WORKFLOW 325 CHAPTER REVIEW 327 FOR FURTHER READING 327 KEY
TERMS 327 CASE STUDY KEY TERMS 328 PROBLEMS 328 REFERENCES 329 CONTENTS
XVII CHAPTER 11 CLASSICAL ANALYSIS 331 LEARNING OBJECTIVES 331 11.1 THE
SPECIFICATION DOCUMENT 331 11.2 INFORMAL SPECIFICATIONS 333 11.2.1
CORRECTNESS PROOFMINI CASE STUDY REDUX 334 11.3 STRUCTURED SYSTEMS
ANALYSI S 335 11.3.1 SALFY 'S SOFTWARE SHOP MINI CASE STUDY 335 1T.4
STRUCTURED SYSTEMS ANALYSIS: THE MSG FOUNDATION CASE STUDY 343 11.5
OTHER SEMIFORMAL TECHNIQUES 344 11.6 ENTITY-RELATIONSHIP MODELING 345
11.7 FINITE STATE MACHINES 347 11.7.1 FINITE STATE MACHINES: THE
ELEVATOR PROBLEM CASE STUDY 349 11.8 PETRINETS 353 11.8.1 PETRI NETS:
THE ELEVATOR PROBLEM CASE STUDY 356 11.9 Z 358 11.9.1 Z: THE ELEVATOR
PROBLEM CASE STUDY 359 11.9.2 ANALYSIS OFZ 361 11.10 OTHER FORMAL
TECHNIQUES 363 11.11 COMPARISON OF CLASSICAL ANALYSIS TECHNIQUES 363
11.12 TESTING DURING CLASSICAL ANALYSIS 365 11.13 CASE TOOLS FOR
CLASSICAL ANALYSIS 365 11.14 METRICS FOR CLASSICAL ANALYSIS 366 11.15
SOFTWARE PROJECT MANAGEMENT PLAN: THE MSG FOUNDATION CASE STUDY 366
11.16 CHALLENGES OF CLASSICAL ANALYSIS 367 CHAPTER REVIEW 367 FOR
FURTHER READING 368 KEY TERMS 368 CASE STUDY KEY TERMS 369 PROBLEMS 369
REFERENCES 371 CHAPTER12 OBJECT-ORIENTED ANALYSIS 375 LEARNING
OBJECTIVES 375 12.1 THE ANALYSIS WORKFLOW 376 12.2 EXTRACTING THE ENTITY
CLASSES 377 1 2.3 OBJECT-ORIENTED ANALYSIS: THE ELEVATOR PROBLEM CASE
STUDY 378 1 2.4 FUNCTIONAL MODELING: THE ELEVATOR PROBLEM CASE STUDY 378
1 2.5 ENTITY CLASS MODELING: THE ELEVATOR PROBLEM CASE STUDY 380 12.5.1
NOUN EXTRACTION 381 12.5.2 CRC CARDS 383 1 2.6 DYNAMIC MODELING: THE
ELEVATOR PROBLEM CASE STUDY 384 1 2.7 THE TEST WORKFLOW: OBJECT-ORIENTED
ANALYSIS 387 1 2.8 EXTRACTIN G THE BOUNDARY AND CONTROL CLASSES 391 1
2.9 THE INITIAL FUNCTIONAL MODEL: THE MSG FOUNDATION CASE STUDY 392 1
2.1 0 THE INITIAL CLASS DIAGRAM: THE MSG FOUNDATION CASE STUDY 395 12.11
THE INITIAL DYNAMIC MODEL: THE MSG FOUNDATION CASE STUDY 397 1 2.1 2
REVISING THE ENTITY CLASSES: THE MSG FOUNDATION CASE STUDY 399 12.13
EXTRACTING THE BOUNDARY CLASSES: THE MSG FOUNDATION CASE STUDY 401 12.14
EXTRACTING THE CONTROL CLASSES: THE MSG FOUNDATION CASE STUDY 401 12.15
USE-CASE REALIZATION: THE MSG FOUNDATION CASE STUDY 402 12.15.1 ESTIMATE
FUNDS AVAILABLE FOR WEEK USE CASE 402 12.15.2 MANAGE AN ASSET USE CASE
409 12.15.3 UPDATE ESTIMATED ANNUAL OPERATING EXPENSES USE CASE 413
12.15.4 PRODUCE A REPORT USE CASE 416 12.16 INCREMENTING THE CLASS
DIAGRAM: THE MSG FOUNDATION CASE STUDY 421 12.17 THE TEST WORKFLOW: THE
MSG FOUNDATION CASE STUDY 423 12.18 THE SPECIFICATION DOCUMENT IN THE
UNIFIED PROCESS 423 12.19 MORE ON ACTORS AND USE CASES 424 1 2.20 CASE
TOOLS FOR THE OBJECT-ORIENTED ANALYSIS WORKFLOW 425 XVIII CONTENTS 1
2.21 CHALLENGES OF THE OBJECT-ORIENTED ANALYSIS WORKFLOW 425 CHAPTER
REVIEW 426 FOR FURTHER READING 427 KEY TERMS 427 PROBLEMS 428 REFERENCES
429 CHAPTER 13 DESIGN 431 , LEARNING OBJECTIVES 431 13.1 DESIGN AND
ABSTRACTION 432 13.2 OPERATION-ORIENTED DESIGN 432 13.3 DATA FLOW
ANALYSIS 433 13.3.1 MINI CASE STUDY: WORD COUNTING 434 13.3.2 DATA FLOW
ANALYSIS EXTENSIONS 439 13.4 TRANSACTION ANALYSIS 439 13.5 DATA-ORIENTED
DESIGN 441 13.6 OBJECT-ORIENTED DESIGN 442 13.7 OBJECT-ORIENTED DESIGN:
THE ELEVATOR PROBLEM CASE STUDY 443 13.8 OBJECT-ORIENTED DESIGN: THE MSG
FOUNDATION CASE STUDY 446 13.9 THE DESIGN WORKFLOW 451 13.10 THE TEST
WORKFLOW: DESIGN 453 13.11 THE TEST WORKFLOW: THE MSG FOUNDATION CASE
STUDY 453 13.12 FORMAL TECHNIQUES FOR DETAILED DESIGN 454 13.13
REAL-TIME DESIGN TECHNIQUES 454 13.14 CASE TOOLS FOR DESIGN 455 13.15
METRICS FOR DESIGN 456 13.16 CHALLENGES OF THE DESIGN WORKFLOW 457
CHAPTER REVIEW 458 FOR FURTHER READING 458 KEY TERMS 459 PROBLEMS 459
REFERENCES 460 CHAPTER 14 IMPLEMENTATION 463 LEARNING OBJECTIVES 463
14.1 CHOICE OF PROGRAMMING LANGUAGE 463 1 4.2 FOURTH-GENERATION
LANGUAGES 466 14.3 GOOD PROGRAMMING PRACTICE 469 14.3.1 USE OF
CONSISTENT AND MEANINGFUL VARIABLE NAMES 469 14.3.2 THE ISSUE OF
SELF-DOCUMENTING CODE 470 14.3.3 USE OF PARAMETERS 472 14.3.4 CODE
LAYOUT FOR INCREASED READABILITY 472 14.3.5 NESTED IF STATEMENTS 472
14.4 CODING STANDARDS 474 14.5 CODE REUSE 475 1 4.6 INTEGRATION 475
14.6.1 TOP-DOWN INTEGRATION 476 14.6.2 BOTTOM-UP INTEGRATION 478 14.6.3
SANDWICH INTEGRATION 478 14.6.4 INTEGRATION OF OBJECT-ORIENTED PRODUCTS
479 14.6.5 MANAGEMENT OF INTEGRATION 480 14.7 THE IMPLEMENTATION
WORKFLOW 481 14.8 THE IMPLEMENTATION WORKFLOW: THE MSG FOUNDATION CASE
STUDY 481 14.9 THE TEST WORKFLOW: IMPLEMENTATION 481 14.10 TEST CASE
SELECTION 482 14.10.1 TESTING TO SPECIFICATIONS VERSUS TESTING TO CODE
482 14.10.2 FEASIBILITY OF TESTING TO SPECIFICATIONS 482 14.10.3
FEASIBILITY OF TESTING TO CODE 483 14.11 BLACK-BOX UNIT-TESTING
TECHNIQUES 485 14.11.1 EQUIVALENCE TESTING AND BOUNDARY VALUE ANALYSIS
486 14.11.2 FUNCTIONAL TESTING 487 14.12 BLACK-BOX TEST CASES: THE MSG
FOUNDATION CASE STUDY 488 14.13 GLASS-BOX UNIT-TESTING TECHNIQUES 490
14.13.1 STRUCTURAL TESTING: STATEMENT, BRANCH, AND PATH COVERAGE 491
14.13.2 COMPLEXITY METRICS 492 14.14 CODE WALKTHROUGHS AND INSPECTIONS
493 14.15 COMPARISON OF UNIT-TESTING TECHNIQUES 493 14.16 CLEANROOM 494
14.17 POTENTIAL PROBLEMS WHEN TESTING OBJECTS 495 14.18 MANAGEMENT
ASPECTS OF UNIT TESTING 498 CONTENTS XIX 14.19 WHEN TO REWRITE RATHER
THAN DEBUG A CODE ARTIFACT 498 14.20 INTEGRATION TESTING 499 14.21
PRODUCT TESTING 500 14.22 ACCEPTANCE TESTING 501 1 4.23 THE TEST
WORKFLOW: THE MSG FOUNDATION CASE STUDY 502 14.24 CASE TOOLS FOR
IMPLEMENTATION 502 14.24.1 CASE TOOLS FOR THE COMPLETE SOFTWARE PROCESS
503 14.24.2 INTEGRATED DEVELOPMENT ENVIRONMENTS 503 14.24.3 ENVIRONMENTS
FOR BUSINESS APPLICATIONS 504 14.24.4 PUBLIC TOOL INFRASTRUCTURES 505
14.24.5 POTENTIAL PROBLEMS WITH ENVIRONMENTS 505 1 4.25 CASE TOOLS FOR
THE TEST WORKFLOW 505 1 4.26 METRICS FOR THE IMPLEMENTATION WORKFLOW 506
14.27 CHALLENGES OF THE IMPLEMENTATION WORKFLOW 507 CHAPTER REVIEW 507
FOR FURTHER READING 508 KEY TERMS 509 PROBLEMS 509 REFERENCES 511
CHAPTER15 POSTDELIVERY MAINTENANCE 515 LEARNING OBJ ECTIVES 515 15.1
DEVELOPMENT AND MAINTENANCE 515 1 5.2 WHY POSTDELIVERY MAINTENANCE
ISNECESSARY 517 15.3 WHAT IS REQUIRED OF POSTDELIVERY MAINTENANCE
PROGRAMMERS? 517 15.4 POSTDELIVER Y MAINTENANCE MINI CASE STUDY 520 15.5
MANAGEMENT OF POSTDELIVERY MAINTENANCE 521 15.5.1 DEFECT REPORTS 521
15.5.2 AUTHORIZING CHANGES TO THE PRODUCT 522 15.5.3 ENSURING
MAINTAINABILITY 523 15.5.4 PROBLEM OF REPEATED MAINTENANCE 523 15.6
MAINTENANCE OF OBJ ECT-ORIENTED SOFTWARE 524 1 5.7 POSTDELIVERY
MAINTENANCE SKILLS VERSUS DEVELOPMENT SKILLS 527 15.8 REVERSE
ENGINEERING 527 15.9 TESTING DURING POSTDELIVERY MAINTENANCE 528 15.10
CASE TOOLS FOR POSTDELIVERY MAINTENANCE 529 1 5.1 1 METRICS FOR
POSTDELIVERY MAINTENANCE 530 1 5.1 2 POSTDELIVERY MAINTENANCE: THE MSG
FOUNDATION CASE STUDY 530 15.13 CHALLENGES OF POSTDELIVERY MAINTENANCE
530 CHAPTER REVIEW 531 FOR FURTHER READING 531 KEY TERMS 532 PROBLEMS
532 REFERENCES 533 CHAPTER 16 MORE ON UML 535 LEARNING OBJECTIVES 535
16.1 UML IS NOT A METHODOLOGY 535 16.2 CLASS DIAGRAMS 536 16.2.1
AGGREGATION 537 16.2.2 MULTIPLICITY 538 16.2.3 COMPOSITION 539 16.2.4
GENERALIZATION 540 16.2.5 ASSOCIATION 540 16.3 NOTES 541 16.4 USE-CASE
DIAGRAMS 541 16.5 STEREOTYPES 541 16.6 INTERACTION DIAGRAMS 543 16.7
STATECHARTS 545 1 6.8 ACTIVITY DIAGRAMS 547 16.9 PACKAGES 549 16.10
COMPONENT DIAGRAMS 550 16.11 DEPLOYMENT DIAGRAMS 550 16.12 REVIEW OF UML
DIAGRAMS 551 16.13 UML AND ITERATION 5 51 CHAPTER REVIEW 551 XX CONTENTS
FOR FURTHER READING 552 KEY TERMS 552 PROBLEMS 552 REFERENCES 553
BIBLIOGRAPHY 554 APPENDIX A TERM PROJECT: OSRIC'S OFFICE APPLIANCES AND
DECOR 579 APPENDIX B SOFTWARE ENGINEERING RESOURCES 583 APPENDIX C *
REQUIREMENTS WORKFLOW: THE MSG FOUNDATION CASE STUDY 585 APPENDIX D
STRUCTURED SYSTEMS ANALYSIS: THE MSG FOUNDATION CASE STUDY 586 APPENDIX
E ANALYSIS WORKFLOW: THE MSG FOUNDATION CASE STUDY 589 APPENDIX F
SOFTWARE PROJECT MANAGEMENT PLAN: THE MSG FOUNDATION CASE STUDY 590
APPENDIX G DESIGN WORKFLOW: THE MSG FOUNDATION CASE STUDY 595 APPENDIX H
IMPLEMENTATION WORKFLOW: THE MSG FOUNDATION CASE STUDY (C++ VERSION) 600
APPENDIX I IMPLEMENTATION WORKFLOW: THE MSG FOUNDATION CASE STUDY (JAVA
VERSION) 601 APPENDIX J TEST WORKFLOW: THE MSG FOUNDATION CASE STUDY 602
AUTHOR INDEX 603 SUBJECT INDEX 606 |
| adam_txt |
OBJECT-ORIENTED & CLASSICAL SOFT ENGINEERING SEVENTH EDITION STEPHEN R.
SCHACH VANDERBILT UNIVERSITY HIGHER EDUCATION BOSTON BURR RIDGE, IL
DUBUQUE, IA NEW YORK SAN FRANCISCO ST. LOUIS BANGKOK BOGOTA CARACAS
KUALA LUMPUR LISBON LONDON MADRID MEXICO CITY MILAN MONTREAL NEW DELHI
SANTIAGO SEOUL SINGAPORE SYDNEY TAIPEI TORONTO CONTENTS PREFACE V PART
ONE INTRODUCTION TO SOFTWARE ENGINEERING 1 CHAPTER 1 THE SCOPE OF
SOFTWARE ENGINEERING 3 LEARNING OBJECTIVES 3 1.1 HISTORICAL ASPECTS 4
1.2 ECONOMIC ASPECTS 7 1.3 MAINTENANCE ASPECTS 8 1.3.1 CLASSICAL AND
MODERN VIEWS OF MAINTENANCE 9 1.3.2 THE IMPORTANCE OF POSTDELIVERY
MAINTENANCE 11 1.4 REQUIREMENTS, ANALYSIS, AND DESIGN ASPECTS 13 1.5
TEAM DEVELOPMENT ASPECTS 16 1.6 WHY THERE 1S NO PLANNING PHASE 17 1.7
WHY THERE IS NO TESTING PHASE 17 1.8 WHY THERE IS NO DOCUMENTATION PHASE
18 1.9 THE OBJECT-ORIENTED PARADIGM 19 1.10 THE OBJECT-ORIENTED PARADIGM
IN PERSPECTIVE 23 1.11 TERMINOLOGY 24 1.12 ETHICAL ISSUES 27 CHAPTER
REVIEW 28 FOR FURTHER READING 28 KEY TERMS 29 PROBLEMS 30 REFERENCES 31
CHAPTER 2 SOFTWARE LIFE-CYCLE MODELS 35 LEARNING OBJECTIVES 35 2.1
SOFTWARE DEVELOPMENT IN THEORY 35 2.2 WINBURG MINI CASE STUDY 36 2.3
LESSONS OF THE WINBURG MINI CASE STUDY 40 2.4 TEAL TRACTORS MINI CASE
STUDY 40 2.5 ITERATION AND INCREMENTATION 41 2.6 WINBURG MINI CASE STUDY
REVISITED 45 2.7 RISKS AND OTHER ASPECTS OF ITERATION AND INCREMENTATION
46 2.8 MANAGING ITERATION AND INCREMENTATION 49 2.9 OTHER LIFE-CYCLE
MODELS 50 2.9.1 CODE-AND-FIX LIFE-CYCLE MODEL 50 2.9.2 WATERFALL
LIFE-CYCLE MODEL 51 2.9.3 RAPID-PROTOTYPING LIFE-CYCLE MODEL 53 2.9.4
OPEN-SOURCE LIFE-CYCLE MODEL 54 2.9.5 AGILE PROCESSES 57 2.9.6
SYNCHRONIZE-AND-STABILIZE LIFE-CYCLE MODEL 60 2.9.7 SPIRAL LIFE-CYCLE
MODEL 60 2.10 COMPARISON OF LIFE-CYCLE MODELS 64 CHAPTER REVIEW 65 FOR
FURTHER READING 66 KEY TERMS 67 PROBLEMS 67 REFERENCES 68 CHAPTER 3 THE
SOFTWARE PROCESS 71 LEARNING OBJECTIVES 71 3.1 THE UNIFIED PROCESS 73
3.2 ITERATION AND INCREMENTATION WITHIN THE OBJECT-ORIENTED PARADIGM 73
3.3 THE REQUIREMENTS WORKFLOW 75 3.4 THE ANALYSIS WORKFLOW 77 3.5 THE
DESIGN WORKFLOW 79 3.6 THE IMPLEMENTATION WORKFLOW 80 3.7 THE TEST
WORKFLOW 81 3.7.1 REQUIREMENTS ARTIFACTS 81 3.7.2 ANALYSIS ARTIFACTS 81
3.7.3 DESIGN ARTIFACTS 82 3.7.4 IMPLEMENTATION ARTIFACTS 82 XIII XIV
CONTENTS 3.8 POSTDELIVERY MAINTENANCE 84 3.9 RETIREMENT 85 3.10 THE
PHASES OF THE UNIFIED PROCESS 85 3.10.1 THE INCEPTION PHASE 86 3.10.2
THE ELABORATION PHASE 88 3.10.3 THE CONSTRUCTION PHASE 89 3.10.4 THE
TRANSITION PHASE 89 3.11 ONE- VERSUS TWO-DIMENSIONAL LIFE-CYCLE MODELS
90 3.12 IMPROVING THE SOFTWARE PROCESS 92 3.13 CAPABILITY MATURITY
MODELS 92 3.14 OTHER SOFTWARE PROCESS IMPROVEMENT INITIATIVES 95 3.15
COSTS AND BENEFITS OF SOFTWARE PROCESS IMPROVEMENT 96 CHAPTER REVIEW 98
FOR FURTHER READING 98 KEY TERMS 99 PROBLEMS 100 REFERENCES 100 CHAPTER
4 TEAMS 104 LEARNING OBJECTIVES 104 4.1 TEAM ORGANIZATION 104 4.2
DEMOCRATIC TEAM APPROACH 106 4.2.1 ANALYSIS OFTHE DEMOCRATIC TEAM
APPROACH 107 4.3 CLASSICAL CHIEF PROGRAMMER TEAM APPROACH 107 4.3.1 THE
NEW YORK TIMES PROJECT 109 4.3.2 LMPRACTICALITY OFTHE CLASSICAL CHIEF
PROGRAMMER TEAM APPROACH 110 4.4 BEYOND CHIEF PROGRAMMER AND DEMOCRATIC
TEAMS 110 4.5 SYNCHRONIZE-AND-STABILIZE TEAMS 114 4.6 TEAMS FOR AGILE
PROCESSES 115 4.7 OPEN-SOURCE PROGRAMMING TEAMS 115 4.8 PEOPLE
CAPABILITY MATURITY MODEL 116 4.9 CHOOSING AN APPROPRIATE TEAM
ORGANIZATION 117 CHAPTER REVIEW 118 FOR FURTHER READING 118 KEY TERMS
118 PROBLEMS 119 REFERENCES 119 CHAPTER 5 THE TOOLS OF THE TRADE 121
LEARNING OBJECTIVES 121 5.1 STEPWISE REFINEMENT 121 5.1.1 STEPWISE
REFINEMENT MINI CASE STUDY 122 5.2 COST-BENEFIT ANALYSIS 127 5.3
SOFTWARE METRICS 129 5.4 CASE 130 5.5 TAXONOMYOFCASE 131 5.6 SCOPEOFCASE
133 5.7 SOFTWARE VERSIONS 136 5.7.1 REVISIONS 137 5.7.2 VARIATIONS 137
5.8 CONFIGURATION CONTROL 138 5.8.1 CONFIGURATION CONTROL DURING
POSTDELIVERY MAINTENANCE 140 5.8.2 BASELINES 140 5.8.3 CONFIGURATION
CONTROL DURING DEVELOPMENT 141 5.9 BUILD TOOLS 141 5.10 PRODUCTIVITY
GAINS WITH CASE TECHNOLOGY 142 CHAPTER REVIEW 144 FOR FURTHER READING
144 KEY TERMS 144 PROBLEMS 145 REFERENCES 146 CHAPTER 6 TESTING 149
LEARNING OBJECTIVES 149 6.1 QUALITY ISSUES 150 6.1.1 SOFTWARE QUALITY
ASSURANCE 151 6.1.2 MANAGERIAL INDEPENDENCE 151 6.2 NON-EXECUTION-BASED
TESTING 152 6.2.1 WALKTHROUGHS 153 6.2.2 MANAGING WALKTHROUGHS 153 6.2.3
INSPECTIONS 154 CONTENTS XV 6.2.4 COMPARISON OF INSPECTIONS AND
WALKTHROUGHS 156 6.2.5 STRENGTHS AND WEAKNESSES OF REVIEWS 157 6.2.6
METRICS FBR INSPECTIONS 157 6.3 EXECUTION-BASED TESTING 157 6.4 WHAT
SHOULD BE TESTED? 158 6.4.1 UTILITY 159 6.4.2 RELIABILITY 159 6.4.3
ROBUSTNESS 160 6.4.4 PERFORMANCE 160 6.4.5 CORRECTNESS 161 6.5 TESTING
VERSUS CORRECTNESS PROOFS 162 6.5.1 EXAMPLE OF A CORRECTNESS PROOF 162
6.5.2 CORRECTNESS PROOF MINI CASE STUDY 166 6.5.3 CORRECTNESS PROOFS AND
SOFTWARE ENGINEERING 167 6.6 WHO SHOULD PERFORM EXECUTION-BASED TESTING?
170 6.7 WHEN TESTING STOPS 171 CHAPTER REVIEW 171 FOR FURTHER READING
172 KEY TERMS 172 PROBLEMS 173 REFERENCES 174 CHAPTER 7 FROM MODULES TO
OBJECTS 177 LEARNING OBJECTIVES 177 7.1 WHAT IS A MODULE? 177 7.2
COHESION 181 7.2.1 COINCIDENTAL COHESION 181 7.2.2 LOGICAL COHESION 182
7.2.3 TEMPORAL COHESION 183 7.2.4 PROCEDURAL COHESION 183 7.2.5
COMMUNICATIONAL COHESION 184 7.2.6 FUNCTIONAL COHESION 184 7.2.7
INFORMATIONAL COHESION 185 7.2.8 COHESION EXAMPLE 185 7.3 COUPLING 186
7.3.1 CONTENT COUPLING 186 7.3.2 COMMON COUPLING 187 7.3.3 CONTROL
COUPLING 189 7.3.4 STAMP COUPLING 190 7.3.5 DATA COUPLING 191 7.3.6
COUPLING EXAMPLE 191 7.3.7 THE IMPORTANCE OF COUPLING 192 7.4 DATA
ENCAPSULATION 193 7.4.1 DATA ENCAPSULATION AND DEVELOPMENT 196 7.4.2
DATA ENCAPSULATION AND MAINTENANCE 197 7.5 ABSTRACT DATA TYPES 202 7.6
INFORMATION HIDING 203 7.7 OBJECTS 205 7.8 INHERITANCE, POLYMORPHISM,
AND DYNAMIC BINDING 209 7.9 THE OBJECT-ORIENTED PARADIGM 212 CHAPTER
REVIEW 214 FOR FURTHER READING 215 KEY TERMS 215 PROBLEMS 216 REFERENCES
217 CHAPTER 8 REUSABILITY AND PORTABILITY 219 LEARNING OBJECTIVES 219
8.1 REUSE CONCEPTS 220 8.2 IMPEDIMENTS TO REUSE 222 8.3 REUSE CASE
STUDIES 223 8.3.1 RAYTHEON MISSILE SYSTEMS DIVISION 224 8.3.2 EUROPEAN
SPACE AGENCY 225 8.4 OBJECTS AND REUSE 226 8.5 REUSE DURING DESIGN AND
IMPLEMENTATION 226 8.5.1 DESIGN REUSE 226 8.5.2 APPLIKATION FRAMEWORKS
228 8.5.3 DESIGN PATTERNS 229 8.5.4 SOFTWARE ARCHITECTURE 233 8.5.5
COMPONENT-BASED SOFTWARE ENGINEERING 233 8.6 REUSE AND POSTDELIVERY
MAINTENANCE 234 8.7 PORTABILITY 235 8.7.1 HARDWARE INCOMPATIBILITIES 235
8.7.2 OPERATING SYSTEM INCOMPATIBILITIES 236 8.7.3 NUMERICAL SOFTWARE
INCOMPATIBILITIES 236 8.7.4 COMPILER INCOMPATIBILITIES 237 XVI CONTENTS
8.8 WHY PORTABILITY? 241 8.9 TECHNIQUES FOR ACHIEVING PORTABILITY 241
8.9.1 PORTABLE SYSTEM SOFTWARE 242 8.9.2 PORTABLE APPLICATION SOFTWARE
242 8.9.3 PORTABLE DATA 243 CHAPTER REVIEW 244 FOR FURTHER READING 245
KEY TERMS 246 PROBLEMS 246 , REFERENCES 247 , CHAPTER 9 PLANNING AND
ESTIMATING 252 LEARNING OBJECTIVES 252 9.1 PLANNING AND THE SOFTWARE
PROCESS 253 9.2 ESTIMATING DURATION AND COST 254 9.2.1 METRICSFOR THE
SIZE OFA PRODUCT 256 9.2.2 TECHNIQUES OF COST ESTIMATION 259 9.2.3
INTERMEDIATE COCOMO 262 9.2.4 COCOMO II 265 9.2.5 TRACKING DURATION AND
COST ESTIMATES 266 9.3 COMPONENTS OF A SOFTWARE PROJECT MANAGEMENT PLAN
266 9.4 SOFTWARE PROJECT MANAGEMENT PLAN FRAMEWORK 268 9.5 IEEE SOFTWARE
PROJECT MANAGEMENT PLAN 270 9.6 PLANNING TESTING 273 9.7 PLANNING
OBJECT-ORIENTED PROJECTS 274 9.8 TRAINING REQUIREMENTS 274 9.9
DOCUMENTATION STANDARDS 275 9.10 CASE TOOLS FOR PLANNING AND ESTIMATING
276 9.1 1 TESTING THE SOFTWARE PROJECT MANAGEMENT PLAN 276 CHAPTER
REVIEW 276 FOR FURTHER READING 277 KEY TERMS 277 PROBLEMS 278 REFERENCES
279 PART TWO THE WORKFLOWS OF THE SOFTWARE LIFE CYCLE 283 CHAPTER 10
REQUIREMENTS 285 LEARNING OBJECTIVES 285 10.1 DETERMINING WHAT THE
CLIENT NEEDS 285 10.2 OVERVIEW OF THE REQUIREMENTS WORKFLOW 286 10.3
UNDERSTANDING THE DOMAIN 287 10.4 THE BUSINESS MODEL 288 10.4.1
INTERVIEWING 288 10.4.2 OTHER TECHNIQUES 289 10.4.3 USE CASES 290 10.5
INITIAL REQUIREMENTS 291 10.6 INITIAL UNDERSTANDING OF THE DOMAIN: THE
MSG FOUNDATION CASE STUDY 292 10.7 INITIAL BUSINESS MODEL: THE MSG
FOUNDATION CASE STUDY 294 1 0.8 INITIAL REQUIREMENTS: THE MSG FOUNDATION
CASE STUDY 298 1 0.9 CONTINUING THE REQUIREMENTS WORKFLOW: THE MSG
FOUNDATION CASE STUDY 300 10.10 REVISING THE REQUIREMENTS: THE MSG
FOUNDATION CASE STUDY 302 10.11 THE TEST WORKFLOW: THE MSG FOUNDATION
CASE STUDY 310 10.12 THE CLASSICAL REQUIREMENTS PHASE 319 10.13 RAPID
PROTOTYPING 320 10.14 HUMAN FACTORS 321 10.15 REUSING THE RAPID
PROTOTYPE 323 10.16 CASE TOOLS FOR THE REQUIREMENTS WORKFLOW 324 10.17
METRICS FOR THE REQUIREMENTS WORKFLOW 325 10.18 CHALLENGES OF THE
REQUIREMENTS WORKFLOW 325 CHAPTER REVIEW 327 FOR FURTHER READING 327 KEY
TERMS 327 CASE STUDY KEY TERMS 328 PROBLEMS 328 REFERENCES 329 CONTENTS
XVII CHAPTER 11 CLASSICAL ANALYSIS 331 LEARNING OBJECTIVES 331 11.1 THE
SPECIFICATION DOCUMENT 331 11.2 INFORMAL SPECIFICATIONS 333 11.2.1
CORRECTNESS PROOFMINI CASE STUDY REDUX 334 11.3 STRUCTURED SYSTEMS
ANALYSI S 335 11.3.1 SALFY 'S SOFTWARE SHOP MINI CASE STUDY 335 1T.4
STRUCTURED SYSTEMS ANALYSIS: THE MSG FOUNDATION CASE STUDY 343 11.5
OTHER SEMIFORMAL TECHNIQUES 344 11.6 ENTITY-RELATIONSHIP MODELING 345
11.7 FINITE STATE MACHINES 347 11.7.1 FINITE STATE MACHINES: THE
ELEVATOR PROBLEM CASE STUDY 349 11.8 PETRINETS 353 11.8.1 PETRI NETS:
THE ELEVATOR PROBLEM CASE STUDY 356 11.9 Z 358 11.9.1 Z: THE ELEVATOR
PROBLEM CASE STUDY 359 11.9.2 ANALYSIS OFZ 361 11.10 OTHER FORMAL
TECHNIQUES 363 11.11 COMPARISON OF CLASSICAL ANALYSIS TECHNIQUES 363
11.12 TESTING DURING CLASSICAL ANALYSIS 365 11.13 CASE TOOLS FOR
CLASSICAL ANALYSIS 365 11.14 METRICS FOR CLASSICAL ANALYSIS 366 11.15
SOFTWARE PROJECT MANAGEMENT PLAN: THE MSG FOUNDATION CASE STUDY 366
11.16 CHALLENGES OF CLASSICAL ANALYSIS 367 CHAPTER REVIEW 367 FOR
FURTHER READING 368 KEY TERMS 368 CASE STUDY KEY TERMS 369 PROBLEMS 369
REFERENCES 371 CHAPTER12 OBJECT-ORIENTED ANALYSIS 375 LEARNING
OBJECTIVES 375 12.1 THE ANALYSIS WORKFLOW 376 12.2 EXTRACTING THE ENTITY
CLASSES 377 1 2.3 OBJECT-ORIENTED ANALYSIS: THE ELEVATOR PROBLEM CASE
STUDY 378 1 2.4 FUNCTIONAL MODELING: THE ELEVATOR PROBLEM CASE STUDY 378
1 2.5 ENTITY CLASS MODELING: THE ELEVATOR PROBLEM CASE STUDY 380 12.5.1
NOUN EXTRACTION 381 12.5.2 CRC CARDS 383 1 2.6 DYNAMIC MODELING: THE
ELEVATOR PROBLEM CASE STUDY 384 1 2.7 THE TEST WORKFLOW: OBJECT-ORIENTED
ANALYSIS 387 1 2.8 EXTRACTIN G THE BOUNDARY AND CONTROL CLASSES 391 1
2.9 THE INITIAL FUNCTIONAL MODEL: THE MSG FOUNDATION CASE STUDY 392 1
2.1 0 THE INITIAL CLASS DIAGRAM: THE MSG FOUNDATION CASE STUDY 395 12.11
THE INITIAL DYNAMIC MODEL: THE MSG FOUNDATION CASE STUDY 397 1 2.1 2
REVISING THE ENTITY CLASSES: THE MSG FOUNDATION CASE STUDY 399 12.13
EXTRACTING THE BOUNDARY CLASSES: THE MSG FOUNDATION CASE STUDY 401 12.14
EXTRACTING THE CONTROL CLASSES: THE MSG FOUNDATION CASE STUDY 401 12.15
USE-CASE REALIZATION: THE MSG FOUNDATION CASE STUDY 402 12.15.1 ESTIMATE
FUNDS AVAILABLE FOR WEEK USE CASE 402 12.15.2 MANAGE AN ASSET USE CASE
409 12.15.3 UPDATE ESTIMATED ANNUAL OPERATING EXPENSES USE CASE 413
12.15.4 PRODUCE A REPORT USE CASE 416 12.16 INCREMENTING THE CLASS
DIAGRAM: THE MSG FOUNDATION CASE STUDY 421 12.17 THE TEST WORKFLOW: THE
MSG FOUNDATION CASE STUDY 423 12.18 THE SPECIFICATION DOCUMENT IN THE
UNIFIED PROCESS 423 12.19 MORE ON ACTORS AND USE CASES 424 1 2.20 CASE
TOOLS FOR THE OBJECT-ORIENTED ANALYSIS WORKFLOW 425 XVIII CONTENTS 1
2.21 CHALLENGES OF THE OBJECT-ORIENTED ANALYSIS WORKFLOW 425 CHAPTER
REVIEW 426 FOR FURTHER READING 427 KEY TERMS 427 PROBLEMS 428 REFERENCES
429 CHAPTER 13 DESIGN 431 , LEARNING OBJECTIVES 431 13.1 DESIGN AND
ABSTRACTION 432 13.2 OPERATION-ORIENTED DESIGN 432 13.3 DATA FLOW
ANALYSIS 433 13.3.1 MINI CASE STUDY: WORD COUNTING 434 13.3.2 DATA FLOW
ANALYSIS EXTENSIONS 439 13.4 TRANSACTION ANALYSIS 439 13.5 DATA-ORIENTED
DESIGN 441 13.6 OBJECT-ORIENTED DESIGN 442 13.7 OBJECT-ORIENTED DESIGN:
THE ELEVATOR PROBLEM CASE STUDY 443 13.8 OBJECT-ORIENTED DESIGN: THE MSG
FOUNDATION CASE STUDY 446 13.9 THE DESIGN WORKFLOW 451 13.10 THE TEST
WORKFLOW: DESIGN 453 13.11 THE TEST WORKFLOW: THE MSG FOUNDATION CASE
STUDY 453 13.12 FORMAL TECHNIQUES FOR DETAILED DESIGN 454 13.13
REAL-TIME DESIGN TECHNIQUES 454 13.14 CASE TOOLS FOR DESIGN 455 13.15
METRICS FOR DESIGN 456 13.16 CHALLENGES OF THE DESIGN WORKFLOW 457
CHAPTER REVIEW 458 FOR FURTHER READING 458 KEY TERMS 459 PROBLEMS 459
REFERENCES 460 CHAPTER 14 IMPLEMENTATION 463 LEARNING OBJECTIVES 463
14.1 CHOICE OF PROGRAMMING LANGUAGE 463 1 4.2 FOURTH-GENERATION
LANGUAGES 466 14.3 GOOD PROGRAMMING PRACTICE 469 14.3.1 USE OF
CONSISTENT AND MEANINGFUL VARIABLE NAMES 469 14.3.2 THE ISSUE OF
SELF-DOCUMENTING CODE 470 14.3.3 USE OF PARAMETERS 472 14.3.4 CODE
LAYOUT FOR INCREASED READABILITY 472 14.3.5 NESTED IF STATEMENTS 472
14.4 CODING STANDARDS 474 14.5 CODE REUSE 475 1 4.6 INTEGRATION 475
14.6.1 TOP-DOWN INTEGRATION 476 14.6.2 BOTTOM-UP INTEGRATION 478 14.6.3
SANDWICH INTEGRATION 478 14.6.4 INTEGRATION OF OBJECT-ORIENTED PRODUCTS
479 14.6.5 MANAGEMENT OF INTEGRATION 480 14.7 THE IMPLEMENTATION
WORKFLOW 481 14.8 THE IMPLEMENTATION WORKFLOW: THE MSG FOUNDATION CASE
STUDY 481 14.9 THE TEST WORKFLOW: IMPLEMENTATION 481 14.10 TEST CASE
SELECTION 482 14.10.1 TESTING TO SPECIFICATIONS VERSUS TESTING TO CODE
482 14.10.2 FEASIBILITY OF TESTING TO SPECIFICATIONS 482 14.10.3
FEASIBILITY OF TESTING TO CODE 483 14.11 BLACK-BOX UNIT-TESTING
TECHNIQUES 485 14.11.1 EQUIVALENCE TESTING AND BOUNDARY VALUE ANALYSIS
486 14.11.2 FUNCTIONAL TESTING 487 14.12 BLACK-BOX TEST CASES: THE MSG
FOUNDATION CASE STUDY 488 14.13 GLASS-BOX UNIT-TESTING TECHNIQUES 490
14.13.1 STRUCTURAL TESTING: STATEMENT, BRANCH, AND PATH COVERAGE 491
14.13.2 COMPLEXITY METRICS 492 14.14 CODE WALKTHROUGHS AND INSPECTIONS
493 14.15 COMPARISON OF UNIT-TESTING TECHNIQUES 493 14.16 CLEANROOM 494
14.17 POTENTIAL PROBLEMS WHEN TESTING OBJECTS 495 14.18 MANAGEMENT
ASPECTS OF UNIT TESTING 498 CONTENTS XIX 14.19 WHEN TO REWRITE RATHER
THAN DEBUG A CODE ARTIFACT 498 14.20 INTEGRATION TESTING 499 14.21
PRODUCT TESTING 500 14.22 ACCEPTANCE TESTING 501 1 4.23 THE TEST
WORKFLOW: THE MSG FOUNDATION CASE STUDY 502 14.24 CASE TOOLS FOR
IMPLEMENTATION 502 14.24.1 CASE TOOLS FOR THE COMPLETE SOFTWARE PROCESS
503 14.24.2 INTEGRATED DEVELOPMENT ENVIRONMENTS 503 14.24.3 ENVIRONMENTS
FOR BUSINESS APPLICATIONS 504 14.24.4 PUBLIC TOOL INFRASTRUCTURES 505
14.24.5 POTENTIAL PROBLEMS WITH ENVIRONMENTS 505 1 4.25 CASE TOOLS FOR
THE TEST WORKFLOW 505 1 4.26 METRICS FOR THE IMPLEMENTATION WORKFLOW 506
14.27 CHALLENGES OF THE IMPLEMENTATION WORKFLOW 507 CHAPTER REVIEW 507
FOR FURTHER READING 508 KEY TERMS 509 PROBLEMS 509 REFERENCES 511
CHAPTER15 POSTDELIVERY MAINTENANCE 515 LEARNING OBJ ECTIVES 515 15.1
DEVELOPMENT AND MAINTENANCE 515 1 5.2 WHY POSTDELIVERY MAINTENANCE
ISNECESSARY 517 15.3 WHAT IS REQUIRED OF POSTDELIVERY MAINTENANCE
PROGRAMMERS? 517 15.4 POSTDELIVER Y MAINTENANCE MINI CASE STUDY 520 15.5
MANAGEMENT OF POSTDELIVERY MAINTENANCE 521 15.5.1 DEFECT REPORTS 521
15.5.2 AUTHORIZING CHANGES TO THE PRODUCT 522 15.5.3 ENSURING
MAINTAINABILITY 523 15.5.4 PROBLEM OF REPEATED MAINTENANCE 523 15.6
MAINTENANCE OF OBJ ECT-ORIENTED SOFTWARE 524 1 5.7 POSTDELIVERY
MAINTENANCE SKILLS VERSUS DEVELOPMENT SKILLS 527 15.8 REVERSE
ENGINEERING 527 15.9 TESTING DURING POSTDELIVERY MAINTENANCE 528 15.10
CASE TOOLS FOR POSTDELIVERY MAINTENANCE 529 1 5.1 1 METRICS FOR
POSTDELIVERY MAINTENANCE 530 1 5.1 2 POSTDELIVERY MAINTENANCE: THE MSG
FOUNDATION CASE STUDY 530 15.13 CHALLENGES OF POSTDELIVERY MAINTENANCE
530 CHAPTER REVIEW 531 FOR FURTHER READING 531 KEY TERMS 532 PROBLEMS
532 REFERENCES 533 CHAPTER 16 MORE ON UML 535 LEARNING OBJECTIVES 535
16.1 UML IS NOT A METHODOLOGY 535 16.2 CLASS DIAGRAMS 536 16.2.1
AGGREGATION 537 16.2.2 MULTIPLICITY 538 16.2.3 COMPOSITION 539 16.2.4
GENERALIZATION 540 16.2.5 ASSOCIATION 540 16.3 NOTES 541 16.4 USE-CASE
DIAGRAMS 541 16.5 STEREOTYPES 541 16.6 INTERACTION DIAGRAMS 543 16.7
STATECHARTS 545 1 6.8 ACTIVITY DIAGRAMS 547 16.9 PACKAGES 549 16.10
COMPONENT DIAGRAMS 550 16.11 DEPLOYMENT DIAGRAMS 550 16.12 REVIEW OF UML
DIAGRAMS 551 16.13 UML AND ITERATION 5 51 CHAPTER REVIEW 551 XX CONTENTS
FOR FURTHER READING 552 KEY TERMS 552 PROBLEMS 552 REFERENCES 553
BIBLIOGRAPHY 554 APPENDIX A TERM PROJECT: OSRIC'S OFFICE APPLIANCES AND
DECOR 579 APPENDIX B SOFTWARE ENGINEERING RESOURCES 583 APPENDIX C *
REQUIREMENTS WORKFLOW: THE MSG FOUNDATION CASE STUDY 585 APPENDIX D
STRUCTURED SYSTEMS ANALYSIS: THE MSG FOUNDATION CASE STUDY 586 APPENDIX
E ANALYSIS WORKFLOW: THE MSG FOUNDATION CASE STUDY 589 APPENDIX F
SOFTWARE PROJECT MANAGEMENT PLAN: THE MSG FOUNDATION CASE STUDY 590
APPENDIX G DESIGN WORKFLOW: THE MSG FOUNDATION CASE STUDY 595 APPENDIX H
IMPLEMENTATION WORKFLOW: THE MSG FOUNDATION CASE STUDY (C++ VERSION) 600
APPENDIX I IMPLEMENTATION WORKFLOW: THE MSG FOUNDATION CASE STUDY (JAVA
VERSION) 601 APPENDIX J TEST WORKFLOW: THE MSG FOUNDATION CASE STUDY 602
AUTHOR INDEX 603 SUBJECT INDEX 606 |
| any_adam_object | 1 |
| any_adam_object_boolean | 1 |
| author | Schach, Stephen R. |
| author_facet | Schach, Stephen R. |
| author_role | aut |
| author_sort | Schach, Stephen R. |
| author_variant | s r s sr srs |
| building | Verbundindex |
| bvnumber | BV021403844 |
| callnumber-first | Q - Science |
| callnumber-label | QA76 |
| callnumber-raw | QA76.758 |
| callnumber-search | QA76.758 |
| callnumber-sort | QA 276.758 |
| callnumber-subject | QA - Mathematics |
| classification_rvk | ST 230 |
| ctrlnum | (OCoLC)255940791 (DE-599)BVBBV021403844 |
| dewey-full | 005.1 |
| dewey-hundreds | 000 - Computer science, information, general works |
| dewey-ones | 005 - Computer programming, programs, data, security |
| dewey-raw | 005.1 |
| dewey-search | 005.1 |
| dewey-sort | 15.1 |
| dewey-tens | 000 - Computer science, information, general works |
| discipline | Informatik |
| discipline_str_mv | Informatik |
| edition | 7. ed. |
| format | Book |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>00000nam a2200000 c 4500</leader><controlfield tag="001">BV021403844</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20070109</controlfield><controlfield tag="007">t|</controlfield><controlfield tag="008">060214s2007 xx d||| |||| 00||| eng d</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">0073191264</subfield><subfield code="9">0-07-319126-4</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9780073191263</subfield><subfield code="9">978-0-07-319126-3</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)255940791</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV021403844</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">rakwb</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="050" ind1=" " ind2="0"><subfield code="a">QA76.758</subfield></datafield><datafield tag="082" ind1="0" ind2=" "><subfield code="a">005.1</subfield><subfield code="2">22</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">ST 230</subfield><subfield code="0">(DE-625)143617:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Schach, Stephen R.</subfield><subfield code="e">Verfasser</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Object oriented & classical software engineering</subfield><subfield code="c">Stephen R. Schach</subfield></datafield><datafield tag="246" ind1="1" ind2="3"><subfield code="a">Object-oriented & classical software engineering</subfield></datafield><datafield tag="246" ind1="1" ind2="3"><subfield code="a">Object-oriented and classical software engineering</subfield></datafield><datafield tag="246" ind1="1" ind2="3"><subfield code="a">Object oriented and classical software engineering</subfield></datafield><datafield tag="250" ind1=" " ind2=" "><subfield code="a">7. ed.</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Boston [u.a.]</subfield><subfield code="b">McGraw-Hill</subfield><subfield code="c">2007</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">XX, 618 S.</subfield><subfield code="b">graph. Darst.</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">n</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">nc</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">C++ (Computer program language)</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Object-oriented programming (Computer science)</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Software engineering</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">UML (Computer science)</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Objektorientierte Analyse</subfield><subfield code="0">(DE-588)4504809-5</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Software Engineering</subfield><subfield code="0">(DE-588)4116521-4</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Objektorientierte Programmierung</subfield><subfield code="0">(DE-588)4233947-9</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Objektorientierung</subfield><subfield code="0">(DE-588)4346172-4</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="655" ind1=" " ind2="7"><subfield code="8">1\p</subfield><subfield code="0">(DE-588)4123623-3</subfield><subfield code="a">Lehrbuch</subfield><subfield code="2">gnd-content</subfield></datafield><datafield tag="689" ind1="0" ind2="0"><subfield code="a">Software Engineering</subfield><subfield code="0">(DE-588)4116521-4</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2="1"><subfield code="a">Objektorientierung</subfield><subfield code="0">(DE-588)4346172-4</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2=" "><subfield code="8">2\p</subfield><subfield code="5">DE-604</subfield></datafield><datafield tag="689" ind1="1" ind2="0"><subfield code="a">Software Engineering</subfield><subfield code="0">(DE-588)4116521-4</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="1" ind2="1"><subfield code="a">Objektorientierte Analyse</subfield><subfield code="0">(DE-588)4504809-5</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="1" ind2=" "><subfield code="8">3\p</subfield><subfield code="5">DE-604</subfield></datafield><datafield tag="689" ind1="2" ind2="0"><subfield code="a">Objektorientierte Programmierung</subfield><subfield code="0">(DE-588)4233947-9</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="2" ind2=" "><subfield code="8">4\p</subfield><subfield code="5">DE-604</subfield></datafield><datafield tag="856" ind1="4" ind2="2"><subfield code="m">GBV Datenaustausch</subfield><subfield code="q">application/pdf</subfield><subfield code="u">http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=014655432&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA</subfield><subfield code="3">Inhaltsverzeichnis</subfield></datafield><datafield tag="883" ind1="1" ind2=" "><subfield code="8">1\p</subfield><subfield code="a">cgwrk</subfield><subfield code="d">20201028</subfield><subfield code="q">DE-101</subfield><subfield code="u">https://d-nb.info/provenance/plan#cgwrk</subfield></datafield><datafield tag="883" ind1="1" ind2=" "><subfield code="8">2\p</subfield><subfield code="a">cgwrk</subfield><subfield code="d">20201028</subfield><subfield code="q">DE-101</subfield><subfield code="u">https://d-nb.info/provenance/plan#cgwrk</subfield></datafield><datafield tag="883" ind1="1" ind2=" "><subfield code="8">3\p</subfield><subfield code="a">cgwrk</subfield><subfield code="d">20201028</subfield><subfield code="q">DE-101</subfield><subfield code="u">https://d-nb.info/provenance/plan#cgwrk</subfield></datafield><datafield tag="883" ind1="1" ind2=" "><subfield code="8">4\p</subfield><subfield code="a">cgwrk</subfield><subfield code="d">20201028</subfield><subfield code="q">DE-101</subfield><subfield code="u">https://d-nb.info/provenance/plan#cgwrk</subfield></datafield><datafield tag="943" ind1="1" ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-014655432</subfield></datafield></record></collection> |
| genre | 1\p (DE-588)4123623-3 Lehrbuch gnd-content |
| genre_facet | Lehrbuch |
| id | DE-604.BV021403844 |
| illustrated | Illustrated |
| index_date | 2024-07-02T14:02:35Z |
| indexdate | 2025-03-31T20:04:19Z |
| institution | BVB |
| isbn | 0073191264 9780073191263 |
| language | English |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-014655432 |
| oclc_num | 255940791 |
| open_access_boolean | |
| owner | DE-703 |
| owner_facet | DE-703 |
| physical | XX, 618 S. graph. Darst. |
| publishDate | 2007 |
| publishDateSearch | 2007 |
| publishDateSort | 2007 |
| publisher | McGraw-Hill |
| record_format | marc |
| spelling | Schach, Stephen R. Verfasser aut Object oriented & classical software engineering Stephen R. Schach Object-oriented & classical software engineering Object-oriented and classical software engineering Object oriented and classical software engineering 7. ed. Boston [u.a.] McGraw-Hill 2007 XX, 618 S. graph. Darst. txt rdacontent n rdamedia nc rdacarrier C++ (Computer program language) Object-oriented programming (Computer science) Software engineering UML (Computer science) Objektorientierte Analyse (DE-588)4504809-5 gnd rswk-swf Software Engineering (DE-588)4116521-4 gnd rswk-swf Objektorientierte Programmierung (DE-588)4233947-9 gnd rswk-swf Objektorientierung (DE-588)4346172-4 gnd rswk-swf 1\p (DE-588)4123623-3 Lehrbuch gnd-content Software Engineering (DE-588)4116521-4 s Objektorientierung (DE-588)4346172-4 s 2\p DE-604 Objektorientierte Analyse (DE-588)4504809-5 s 3\p DE-604 Objektorientierte Programmierung (DE-588)4233947-9 s 4\p DE-604 GBV Datenaustausch application/pdf http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=014655432&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA Inhaltsverzeichnis 1\p cgwrk 20201028 DE-101 https://d-nb.info/provenance/plan#cgwrk 2\p cgwrk 20201028 DE-101 https://d-nb.info/provenance/plan#cgwrk 3\p cgwrk 20201028 DE-101 https://d-nb.info/provenance/plan#cgwrk 4\p cgwrk 20201028 DE-101 https://d-nb.info/provenance/plan#cgwrk |
| spellingShingle | Schach, Stephen R. Object oriented & classical software engineering C++ (Computer program language) Object-oriented programming (Computer science) Software engineering UML (Computer science) Objektorientierte Analyse (DE-588)4504809-5 gnd Software Engineering (DE-588)4116521-4 gnd Objektorientierte Programmierung (DE-588)4233947-9 gnd Objektorientierung (DE-588)4346172-4 gnd |
| subject_GND | (DE-588)4504809-5 (DE-588)4116521-4 (DE-588)4233947-9 (DE-588)4346172-4 (DE-588)4123623-3 |
| title | Object oriented & classical software engineering |
| title_alt | Object-oriented & classical software engineering Object-oriented and classical software engineering Object oriented and classical software engineering |
| title_auth | Object oriented & classical software engineering |
| title_exact_search | Object oriented & classical software engineering |
| title_exact_search_txtP | Object oriented & classical software engineering |
| title_full | Object oriented & classical software engineering Stephen R. Schach |
| title_fullStr | Object oriented & classical software engineering Stephen R. Schach |
| title_full_unstemmed | Object oriented & classical software engineering Stephen R. Schach |
| title_short | Object oriented & classical software engineering |
| title_sort | object oriented classical software engineering |
| topic | C++ (Computer program language) Object-oriented programming (Computer science) Software engineering UML (Computer science) Objektorientierte Analyse (DE-588)4504809-5 gnd Software Engineering (DE-588)4116521-4 gnd Objektorientierte Programmierung (DE-588)4233947-9 gnd Objektorientierung (DE-588)4346172-4 gnd |
| topic_facet | C++ (Computer program language) Object-oriented programming (Computer science) Software engineering UML (Computer science) Objektorientierte Analyse Software Engineering Objektorientierte Programmierung Objektorientierung Lehrbuch |
| url | http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=014655432&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |
| work_keys_str_mv | AT schachstephenr objectorientedclassicalsoftwareengineering AT schachstephenr objectorientedandclassicalsoftwareengineering |