000			02858nam a2200361 4500
001			OTLid0000618
003			MnU
005			20201105133347.0
006			m o d s
008			180929s2008 mnu o 0 0 eng d
040			_aMnU _beng _cMnU
050		4	_aQA76
100	1		_aDemeyer, Serge _eauthor
245	0	0	_aObject-Oriented Reengineering Patterns _cSerge Demeyer
264		2	_bOpen Textbook Library
264		1	_bStéphane Ducasse
300			_a1 online resource
490	0		_aOpen textbook library.
505	0		_aI Introduction -- Chapter 1: Reengineering Patterns -- II Reverse Engineering -- Chapter 2: Setting Direction -- Chapter 3: First Contact -- Chapter 4: Initial Understanding -- Chapter 5: Detailed Model Capture -- III Reengineering -- Chapter 6: Tests: Your Life Insurance! -- Chapter 7: Migration Strategies -- Chapter 8: Detecting Duplicated Code -- Chapter 9: Redistribute Responsibilities -- Chapter 10: Transform Conditionals to Polymorphism
520	0		_aThe documentation is missing or obsolete, and the original developers have departed. Your team has limited understanding of the system, and unit tests are missing for many, if not all, of the components. When you fix a bug in one place, another bug pops up somewhere else in the system. Long rebuild times make any change difficult. All of these are signs of software that is close to the breaking point. Many systems can be upgraded or simply thrown away if they no longer serve their purpose. Legacy software, however, is crucial for operations and needs to be continually available and upgraded. How can you reduce the complexity of a legacy system sufficiently so that it can continue to be used and adapted at acceptable cost? Based on the authors' industrial experiences, this book is a guide on how to reverse engineer legacy systems to understand their problems, and then reengineer those systems to meet new demands. Patterns are used to clarify and explain the process of understanding large code bases, hence transforming them to meet new requirements. The key insight is that the right design and organization of your system is not something that can be evident from the initial requirements alone, but rather as a consequence of understanding how these requirements evolve.
542	1		_fAttribution-ShareAlike
546			_aIn English.
588	0		_aDescription based on print resource
650		0	_aComputer Science _vTextbooks
700	1		_aDucasse, Stéphane _eauthor
700	1		_aNierstrasz, Oscar _eauthor
710	2		_aOpen Textbook Library _edistributor
856	4	0	_uhttps://open.umn.edu/opentextbooks/textbooks/618 _zAccess online version
999			_c19983 _d19983