000 | 11060cam a22003734a 4500 | ||
---|---|---|---|
001 | 43641345 | ||
003 | OCoLC | ||
005 | 20250704144558.0 | ||
008 | 000308s2000 enka b 001 0 eng | ||
010 | _a00028992 | ||
015 |
_aGB99U6626 _2bnb |
||
015 |
_aGBA229755 _2bnb |
||
020 |
_a0471975087 _q(alk. paper) |
||
020 |
_a9780471975083 _q(alk. paper) |
||
035 |
_a(OCoLC)43641345 _z(OCoLC)42954495 _z(OCoLC)48498087 _z(OCoLC)992281833 |
||
040 |
_aDLC _beng _cDLC _dUKM _dMUQ _dBAKER _dNLGGC _dXVF _dBTCTA _dYDXCP _dDEBBG _dVA@ _dOCLCQ _dIG# _dOCLCF _dOCLCO _dBEDGE _dOCLCQ _dTHHCU _dCNUTO _dVGM _dTHHCU _dOCLCQ _dOCLCO _dUKMGB _dNAG _dOCLCQ _dOCLCO |
||
042 | _apcc | ||
050 | 0 | 0 |
_aQA76.758 _b.V54 2000 |
082 | 0 | 0 |
_a005.1 _221 |
100 | 1 | _aVliet, Hans van | |
245 | 1 | 0 |
_aSoftware engineering : _bprinciples and practice / _cHans van Vliet |
250 | _a2nd ed | ||
260 |
_aChichester [England] ; _aNew York : _bJohn Wiley, _c2000 |
||
300 |
_axxii, 726 pages : _billustrations ; _c24 cm |
||
336 |
_atext _btxt _2rdacontent |
||
337 |
_aunmediated _bn _2rdamedia |
||
338 |
_avolume _bnc _2rdacarrier |
||
504 | _aIncludes bibliographical references (pages 673-716) and index | ||
505 | 0 | 0 |
_g1.1 _tWhat is Software Engineering? _g6 -- _g1.2 _tPhases in the Development of Software _g10 -- _g1.3 _tMaintenance or Evolution _g16 -- _g1.4 _tFrom the Trenches _g17 -- _g1.4.1 _tAriane 5, Flight 501 _g18 -- _g1.4.2 _tTherac-25 _g19 -- _g1.4.3 _tLondon Ambulance Service _g21 -- _g1.5 _tSoftware Engineering Ethics _g24 -- _g1.6 _tQuo Vadis? _g26 -- _gPart I _tSoftware Management _g33 -- _g2 _tIntroduction to Software Engineering Management _g35 -- _g2.1 _tPlanning a Software Development Project _g38 -- _g2.2 _tControlling a Software Development Project _g41 -- _g3 _tSoftware Life Cycle Revisited _g47 -- _g3.1 _tWaterfall Model _g49 -- _g3.2 _tPrototyping _g51 -- _g3.3 _tIncremental Development _g56 -- _g3.4 _tRapid Application Development _g57 -- _g3.5 _tIntermezzo: Maintenance or Evolution _g59 -- _g3.6 _tSpiral Model _g62 -- _g3.7 _tTowards a Software Factory _g64 -- _g3.8 _tProcess Modeling _g65 -- _g4 _tConfiguration Management _g73 -- _g4.1 _tTasks and Responsibilities _g75 -- _g4.2 _tConfiguration Management Plan _g80 -- _g5 _tPeople Management and Team Organization _g85 -- _g5.1 _tPeople Management _g87 -- _g5.1.1 _tCoordination Mechanisms _g88 -- _g5.1.2 _tManagement Styles _g90 -- _g5.2 _tTeam Organization _g92 -- _g5.2.1 _tHierarchical Organization _g92 -- _g5.2.2 _tMatrix Organization _g94 -- _g5.2.3 _tChief Programmer Team _g95 -- _g5.2.4 _tSWAT Team _g96 -- _g5.2.5 _tOpen Structured Team _g96 -- _g5.2.6 _tGeneral Principles for Organizing a Team _g97 -- _g6 _tOn Managing Software Quality _g101 -- _g6.1 _tOn Measures and Numbers _g104 -- _g6.2 _tA Taxonomy of Quality Attributes _g110 -- _g6.3 _tPerspectives on Quality _g120 -- _g6.4 _tQuality System _g123 -- _g6.5 _tSoftware Quality Assurance _g125 -- _g6.6 _tCapability Maturity Model (CMM) _g126 -- _g6.7 _tSome Critical Notes _g134 -- _g7 _tCost Estimation _g143 -- _g7.1 _tHow Not to Estimate Cost _g149 -- _g7.2 _tEarly Algorithmic Models _g151 -- _g7.3 _tLater Algorithmic Models _g154 -- _g7.3.1 _tWalston--Felix _g156 -- _g7.3.2 _tCOCOMO _g158 -- _g7.3.3 _tPutnam _g160 -- _g7.3.4 _tDeMarco _g162 -- _g7.3.5 _tFunction Point Analysis _g163 -- _g7.3.6 _tCOCOMO 2: Variations on a Theme _g166 -- _g7.4 _tDistribution of Manpower over Time _g172 -- _g8 _tProject Planning and Control _g181 -- _g8.1 _tA Systems View of Project Control _g182 -- _g8.2 _tA Taxonomy of Software Development Projects _g185 -- _g8.3 _tRisk Management _g189 -- _g8.4 _tTechniques for Project Planning and Control _g192 -- _gPart II _tSoftware Life Cycle _g201 -- _g9 _tRequirements Engineering _g203 -- _g9.1 _tRequirements Elicitation _g210 -- _g9.1.1 _tRequirements Elicitation Techniques _g217 -- _g9.2 _tRequirements Specification Document _g224 -- _g9.3 _tRequirements Specification Techniques _g231 -- _g9.3.1 _tEntity--Relationship Modeling _g233 -- _g9.3.2 _tFinite State Machines _g236 -- _g9.3.3 _tSADT _g237 -- _g9.3.4 _tSpecifying Non-Functional Requirements _g241 -- _g9.4 _tA Modeling Framework _g242 -- _g9.5 _tVerification and Validation _g246 -- _g10 _tSoftware Architecture _g253 -- _g10.1 _tAn Example: Producing a KWIC-Index _g258 -- _g10.1.1 _tMain Program and Subroutines with Shared Data _g260 -- _g10.1.2 _tAbstract Data Types _g261 -- _g10.1.3 _tImplicit Invocation _g264 -- _g10.1.4 _tPipes and Filters _g266 -- _g10.1.5 _tEvaluation of the Architectures _g267 -- _g10.2 _tArchitectural Styles _g270 -- _g10.3 _tDesign Patterns _g282 -- _g10.4 _tVerification and Validation _g285 -- _g11 _tSoftware Design _g291 -- _g11.1 _tDesign Considerations _g295 -- _g11.1.1 _tAbstraction _g296 -- _g11.1.2 _tModularity _g299 -- _g11.1.3 _tInformation Hiding _g303 -- _g11.1.4 _tComplexity _g303 -- _g11.1.5 _tSystem Structure _g311 -- _g11.2 _tDesign Methods _g315 -- _g11.2.1 _tFunctional Decomposition _g317 -- _g11.2.2 _tData Flow Design (SA/SD) _g321 -- _g11.2.3 _tDesign based on Data Structures _g326 -- _g11.2.4 _tHow to Select a Design Method _g334 -- _g11.3 _tNotations that Support the Design Process _g337 -- _g11.4 _tDesign Documentation _g339 -- _g11.5 _tVerification and Validation _g342 -- _g12 _tObject-Oriented Analysis and Design _g351 -- _g12.1 _tOn Objects and Related Stuff _g353 -- _g12.2 _tObject-Oriented Analysis and Design Notations _g359 -- _g12.2.1 _tClass Diagram _g360 --c _g12.2.2 _tState Diagram _g363 -- _g12.2.3 _tSequence Diagram _g367 -- _g12.2.4 _tCollaboration Diagram _g368 -- _g12.2.5 _tUse Case Diagram _g369 -- _g12.2.6 _tCRC Cards _g370 -- _g12.3 _tObject-Oriented Analysis and Design Methods _g371 -- _g12.3.1 _tBooch Method _g378 -- _g12.3.2 _tObject Modeling Technique (OMT) _g379 -- _g12.3.3 _tFusion _g381 -- _g12.3.4 _tObject Orientation: Hype or the Answer? _g383 -- _g12.4 _tObject-Oriented Metrics _g385 -- _g13 _tSoftware Testing _g395 -- _g13.1 _tTest Objectives _g399 -- _g13.1.1 _tTest Adequacy Criteria _g402 -- _g13.1.2 _tFault Detection Versus Confidence Building _g403 -- _g13.1.3 _tFrom Fault Detection to Fault Prevention _g405 -- _g13.2 _tTesting and the Software Life Cycle _g407 -- _g13.2.1 _tRequirements Engineering _g407 -- _g13.2.2 _tDesign _g409 -- _g13.2.3 _tImplementation _g410 -- _g13.2.4 _tMaintenance _g411 -- _g13.3 _tVerification and Validation Planning and Documentation _g411 -- _g13.4 _tManual Test Techniques _g413 -- _g13.4.1 _tReading _g414 -- _g13.4.2 _tWalkthroughs and Inspections _g415 -- _g13.4.3 _tScenario-Based Evaluation _g417 -- _g13.4.4 _tCorrectness Proofs _g418 -- _g13.4.5 _tStepwise Abstraction _g419 -- _g13.5 _tCoverage-Based Test Techniques _g420 -- _g13.5.1 _tControl-Flow Coverage _g421 -- _g13.5.2 _tData Flow Coverage _g424 -- _g13.5.3 _tCoverage-Based Testing of Requirements Specifications _g425 -- _g13.6 _tFault-Based Test Techniques _g427 -- _g13.6.1 _tFault Seeding _g427 -- _g13.6.2 _tMutation Testing _g428 -- _g13.7 _tError-Based Test Techniques _g429 -- _g13.8 _tComparison of Test Techniques _g431 -- _g13.8.1 _tComparison of Test Adequacy Criteria _g432 -- _g13.8.2 _tProperties of Test Adequacy Criteria _g433 -- _g13.8.3 _tExperimental Results _g436 -- _g13.9 _tDifferent Test Stages _g438 -- _g14 _tSoftware Maintenance _g447 -- _g14.1 _tMajor Causes of Maintenance Problems _g451 -- _g14.2 _tReverse Engineering and Restructuring _g455 -- _g14.2.1 _tInherent Limitations _g458 -- _g14.2.2 _tTools _g462 -- _g14.3 _tOrganizational and Managerial Issues _g463 -- _g14.3.1 _tOrganization of Maintenance Activities _g464 -- _g14.3.2 _tSoftware Maintenance from a Service Perspective _g467 -- _g14.3.3 _tControl of Maintenance Tasks _g473 -- _g14.3.4 _tQuality Issues _g476 -- _gPart III _tSupporting Technology _g481 -- _g15 _tFormal Specification _g483 -- _g15.1 _tInformal Specification Techniques _g487 -- _g15.2 _tModel-Oriented Specifications _g489 -- _g15.2.1 _tConcepts of VDM _g493 -- _g15.2.2 _tA Sample VDM Specification _g496 -- _g15.2.3 _tValidation of a VDM Specification _g504 -- _g15.3 _tAlgebraic Specifications _g505 -- _g15.3.1 _tInitial and Final Semantics _g507 -- _g15.3.2 _tSome Difficulties _g510 -- _g15.3.3 _tHow to Construct an Algebraic Specification _g511 -- _g15.3.4 _tSome Example Algebraic Specifications _g514 -- _g15.3.5 _tLarge Specifications _g518 -- _g15.4 _tSpecification by Pre- and Postconditions _g519 -- _g15.5 _tThou Shalt Formalize _g521 -- _g16 _tUser Interface Design _g531 -- _g16.1 _tWhere Is the User Interface? _g534 -- _g16.2 _tWhat Is the User Interface? _g538 -- _g16.3 _tHuman Factors in Human--Computer Interaction _g539 -- _g16.3.1 _tHumanities _g539 -- _g16.3.2 _tArtistic Design _g540 -- _g16.3.3 _tErgonomics _g541 -- _g16.4 _tRole of Models in Human--Computer Interaction _g543 -- _g16.4.1 _tA Model of Human Information Processing _g544 -- _g16.4.2 _tMental Models of Information Systems _g547 -- _g16.4.3 _tConceptual Models in User Interface Design _g549 -- _g16.5 _tDesign of Interactive Systems _g552 -- _g16.5.1 _tDesign as an Activity Structure _g553 -- _g16.5.2 _tDesign as Multi-Disciplinary Collaboration _g555 -- _g16.6 _tTask Analysis _g557 -- _g16.6.1 _tTask Analysis in HCI Design _g557 -- _g16.6.2 _tAnalysis Approaches for Collaborative Work _g559 -- _g16.6.3 _tSources of Knowledge and Collection Methods _g560 -- _g16.6.4 _tAn Integrated Approach to Task Analysis: GTA _g561 -- _g16.7 _tSpecification of the User Interface Details _g563 -- _g16.7.1 _tDialog _g564 -- _g16.7.2 _tRepresentation _g565 -- _g16.8 _tEvaluation _g565 -- _g16.8.1 _tEvaluation of Analysis Decisions _g566 -- _g16.8.2 _tEvaluation of UVM Specifications _g567 -- _g16.8.3 _tEvaluation of Prototypes _g570 -- _g17 _tSoftware Reusability _g575 -- _g17.1 _tReuse Dimensions _g578 -- _g17.2 _tReuse of Intermediate Products _g580 -- _g17.2.1 _tLibraries of Software Components _g580 -- _g17.2.2 _tTemplates _g585 -- _g17.2.3 _tDesign Reuse _g585 -- _g17.2.4 _tReuse of Architecture _g586 -- _g17.2.5 _tTransformation Systems _g586 -- _g17.2.6 _tApplication Generators and Fourth-Generation Languages _g588 -- _g17.3 _tReuse and the Software Life Cycle _g589 -- _g17.4 _tReuse Tools and Techniques _g591 -- _g17.4.1 _tFrom Module Interconnection |
505 | 0 | 0 |
_tLanguage to Architecture Description Language _g591 -- _g17.4.2 _tMiddleware _g596 -- _g17.4.3 _tObject-Oriented Programming _g597 -- _g17.4.4 _tSoftware Development Environments _g598 -- _g17.5 _tPerspectives of Software Reuse _g600 -- _g17.6 _tNon-Technical Aspects of Software Reuse _g604 -- _g17.6.1 _tEconomics _g605 -- _g17.6.2 _tManagement _g607 -- _g17.6.3 _tPsychology of Programmers _g608 -- _g18 _tSoftware Reliability _g615 -- _g18.1 _tAn Example: Fault-Tolerant Disks _g617 -- _g18.2 _tEstimating Software Reliability _g621 -- _g19 _tSoftware Tools _g631 -- _g19.1 _tToolkits _g636 -- _g19.2 _tLanguage-Centered Environments _g638 -- _g19.3 _tIntegrated Environments and Workbenches _g641 -- _g19.3.1 _tAnalyst WorkBenches _g642 -- _g19.3.2 _tProgrammer Workbenches _g643 -- _g19.3.3 _tManagement Workbenches _g647 -- _g19.3.4 _tIntegrated Project Support Environments _g648 -- _g19.4 _tProcess-Centered Environments _g650 -- _gAppendix _tA ISO 9001: Quality Systems _g655 -- _gAppendix B _tIEEE Standard 730: Software Quality Assurance Plans _g659 -- _gAppendix C _tIEEE Standard 830: Software Requirements Specifications _g663 -- _gAppendix D _tIEEE Standard 1012: Software Verification and Verification Plans _g667 |
650 | 0 | _aSoftware engineering | |
776 | 0 | 8 |
_iOnline version: _aVliet, Hans van. _tSoftware engineering. _b2nd ed. _dChichester [England] ; New York : John Wiley, 2000 _w(OCoLC)649583613 |
942 |
_2lcc _cBOOKS _n0 |
||
999 |
_c1848 _d1848 |