000 05944cam a2200925 i 4500
001 ocn928136923
003 OCoLC
005 20240523125539.0
006 m o d
007 cr |||||||||||
008 151105s2016 nju ob 001 0 eng
010 _a 2015042369
040 _aDLC
_beng
_erda
_epn
_cDLC
_dYDX
_dN$T
_dDG1
_dIDEBK
_dEBLCP
_dYDXCP
_dCOO
_dRECBK
_dDEBSZ
_dOHI
_dUPM
_dOCLCF
_dUMI
_dDEBBG
_dCCO
_dIDB
_dMERUC
_dLOA
_dTEFOD
_dK6U
_dSTF
_dOCLCQ
_dLIP
_dPIFAG
_dFVL
_dVGM
_dOCLCQ
_dZCU
_dU3W
_dD6H
_dOCLCQ
_dWRM
_dCOCUF
_dICG
_dVT2
_dUKMGB
_dOCLCQ
_dWYU
_dG3B
_dTKN
_dOCLCQ
_dDKC
_dOCLCQ
_dUKAHL
_dUX1
_dOCLCQ
_dN9V
_dOCLCO
_dOCLCQ
_dOCLCO
_dOCLCL
016 7 _a017720498
_2Uk
019 _a949043607
_a961514583
_a1055352104
_a1081226013
_a1100439419
_a1101725532
_a1148111265
_a1256673371
020 _a9781119213680
_q(electronic bk.)
020 _a1119213681
_q(electronic bk.)
020 _a9781119213697
_q(electronic bk.)
020 _a111921369X
_q(electronic bk.)
020 _z9781119117643
_q(hardback)
020 _z9781119125365
020 _z1119125367
020 _z111911764X
029 1 _aAU@
_b000059223868
029 1 _aAU@
_b000060219568
029 1 _aCHNEW
_b000894336
029 1 _aCHNEW
_b000944888
029 1 _aCHVBK
_b480251266
029 1 _aDEBBG
_bBV043628154
029 1 _aDEBBG
_bBV043738136
029 1 _aDEBSZ
_b461175428
029 1 _aDEBSZ
_b485062992
029 1 _aUKMGB
_b017720498
035 _a(OCoLC)928136923
_z(OCoLC)949043607
_z(OCoLC)961514583
_z(OCoLC)1055352104
_z(OCoLC)1081226013
_z(OCoLC)1100439419
_z(OCoLC)1101725532
_z(OCoLC)1148111265
_z(OCoLC)1256673371
037 _aCL0500000739
_bSafari Books Online
037 _a2CD212ED-D0C7-46E8-85B7-21B53396AEDF
_bOverDrive, Inc.
_nhttp://www.overdrive.com
042 _apcc
050 0 0 _aQA76.76.F34
072 7 _aCOM
_x030000
_2bisacsh
082 0 0 _a005
_223
084 _aCOM081000
_2bisacsh
049 _aMAIN
100 1 _aBell, Michael,
_d1957 June 22-
_eauthor.
245 1 0 _aIncremental software architecture :
_ba method for saving failing IT implementations /
_cMichael Bell.
264 1 _aHoboken, New Jersey :
_bJohn Wiley & Sons, Inc.,
_c2016.
300 _a1 online resource
336 _atext
_btxt
_2rdacontent
337 _acomputer
_bc
_2rdamedia
338 _aonline resource
_bcr
_2rdacarrier
500 _aIncludes index.
520 _a"This book will depict rare insights into actual failed-to-perform software systems, followed by comprehensive root-cause analyses identifying the reasons for their unsuccessful execution in production. Remedies will be provided that offer strategies to tackle the chief issues. Last, architecture and design best practices will conclude the discussion. The book will assist users to: Mitigate risks of software development projects Increase return on investments (ROI) Provide effective tools to assess technological achievability and viability Introduce software design best practices for enterprise architecture efforts Identify actual software construction value proposition Foster software assets reuse and consolidation Accelerate time-to-market "--
_cProvided by publisher.
588 0 _aPrint version record and CIP data provided by publisher.
504 _aIncludes bibliographical references and index.
505 0 _aCh. 1 The Need for Incremental Software Architecture -- pt. ONE Why Do Enterprise Systems Fail? -- ch. 2 What Is a Failing Enterprise System? Is It Management's Fault? -- ch. 3 Technological System-Level Failures -- pt. TWO End-State Architecture Discovery and Analysis -- ch. 4 System Fabric Discovery and Analysis -- ch. 5 Application Discovery -- ch. 6 Application Mapping -- pt. THREE End-State Architecture Decomposition -- ch. 7 End-State Architecture Structural Decomposition through Classification -- ch. 8 Business Analysis Drives End-State Architecture Structural Decomposition -- ch. 9 Technical Analysis Drives End-State Architecture Structural Decomposition -- ch. 10 Business Views Drive End-State Architecture Decomposition -- ch. 11 Environment Behavior Drives End-State Architecture Decomposition -- pt. FOUR End-State Architecture Verification -- ch. 12 Design Substantiation -- ch. 13 Introduction to End-State Architecture Stress Testing -- ch. 14 End-State Architecture Stress Testing Driven by Pressure Points -- ch. 15 Enterprise Capacity Planning for End-State Architecture.
590 _aJohn Wiley and Sons
_bWiley Online Library: Complete oBooks
650 0 _aSoftware failures.
650 0 _aEvolutionary programming (Computer science)
650 0 _aContinuous improvement process.
650 0 _aSoftware architecture.
650 6 _aBogues (Informatique)
650 6 _aProgrammation �evolutive.
650 6 _aAm�elioration continue.
650 6 _aArchitecture logicielle.
650 7 _aCOMPUTERS
_xDesktop Applications
_xProject Management Software.
_2bisacsh
650 7 _aContinuous improvement process
_2fast
650 7 _aEvolutionary programming (Computer science)
_2fast
650 7 _aSoftware architecture
_2fast
650 7 _aSoftware failures
_2fast
758 _ihas work:
_aIncremental software architecture (Text)
_1https://id.oclc.org/worldcat/entity/E39PCGG4HmQvtvYqKdYTM6jyFq
_4https://id.oclc.org/worldcat/ontology/hasWork
776 0 8 _iPrint version:
_aBell, Michael, 1957 June 22-
_tIncremental software architecture.
_dHoboken : John Wiley & Sons, Inc., 2016
_z9781119117643
_w(DLC) 2015040936
856 4 0 _uhttps://onlinelibrary.wiley.com/doi/book/10.1002/9781119125365
938 _aAskews and Holts Library Services
_bASKH
_nAH29522909
938 _aEBL - Ebook Library
_bEBLB
_nEBL4338180
938 _aEBSCOhost
_bEBSC
_n1157320
938 _aProQuest MyiLibrary Digital eBook Collection
_bIDEB
_ncis32291320
938 _aRecorded Books, LLC
_bRECE
_nrbeEB00659400
938 _aYBP Library Services
_bYANK
_n12813286
938 _aYBP Library Services
_bYANK
_n12816030
994 _a92
_bINLUM
999 _c12294
_d12294