000			04326cam a2200661 i 4500
001			ocn928136923
005			20250919141835.0
006			m o d
007			cr |||||||||||
008			151105s2016 nju o 001 0 eng
010			_a 2015042369
020			_a9781119213680 (pdf)
020			_a1119213681 (pdf)
020			_a9781119213697 (epub)
020			_a111921369X (epub)
020			_z9781119117643 (hardback)
020			_a9781119125365
020			_a1119125367
020			_a111911764X
020			_a9781119117643
029	1		_aDEBSZ _b461175428
029	1		_aDEBBG _bBV043628154
029	1		_aDEBBG _bBV043738136
029	1		_aCHNEW _b000894336
029	1		_aAU@ _b000059223868
035			_a(OCoLC)928136923 _z(OCoLC)949043607 _z(OCoLC)961514583
037			_aCL0500000739 _bSafari Books Online
040			_aDLC _beng _erda _cDLC _dYDX _dNST _dDG1 _dIDEBK _dEBLCP _dYDXCP _dCOO _dRECBK _dDEBSZ _dOHI _dUPM _dOCLCF _dUMI _dDEBBG _dCCO
042			_apcc
049			_aMAIN
050	0	0	_aQA76.76.F34
072		7	_aCOM _x030000 _2bisacsh
082	0	0	_a005 _223
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			_aDescription based on print version record and CIP data provided by publisher.
504			_aIncludes bibliographical references and index.
505	0		_aMachine generated contents note: ch. 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.
650		0	_aSoftware failures.
650		0	_aEvolutionary programming (Computer science)
650		0	_aContinuous improvement process.
650		0	_aSoftware architecture.
655		4	_aElectronic books.
776	0	8	_iPrint version: _aBell, Michael, 1957 June 22- author. _tIncremental software architecture _dHoboken : John Wiley & Sons, Inc., 2016 _z9781119117643 _w(DLC) 2015040936
856	4	0	_uhttps://eresourcesptsl.ukm.remotexs.co/user/login?url=https://doi.org/10.1002/9781119125365 _zWiley Online Library
907			_a.b16815415 _b2022-10-06 _c2020-07-17
942			_n0
998			_ae _b2020-07-17 _cm _dz _feng _gnju _y0 _z.b16815415
999			_c648951 _d648951