000 03854nam a2200529 i 4500
001 UMUN-OA-20261005-SE-006
003 local
005 20261005174819.0
006 m o d s
007 cr
008 180929s2008 mnu o 0 0 eng d
035 _a(MnU)OTLid0000618
040 _aMnU
_beng
_cMnU
050 4 _aQA76
100 1 _aDemeyer, Serge
_eauthor
245 0 0 _aObject-Oriented Reengineering Patterns
_cSerge Demeyer
264 2 _aMinneapolis, MN
_bOpen Textbook Library
264 1 _aLille, France
_bStéphane Ducasse
_c[2008]
264 4 _c©2008.
300 _a1 online resource
336 _atext
_btxt
_2rdacontent
337 _acomputer
_bc
_2rdamedia
338 _aonline resource
_bcr
_2rdacarrier
341 0 _atextual
_bunknown
_2sapdv
490 0 _aOpen textbook library.
500 _aPublication type: Open textbook.
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
506 0 _aOpen access; no subscription required for the linked open-access version.
_fUnrestricted online access
_2star
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.
540 _aAttribution-ShareAlike (licence family recorded by the source; version not supplied in metadata).
_uhttps://open.umn.edu/opentextbooks/textbooks/618
542 1 _fAttribution-ShareAlike
546 _aIn English.
588 0 _aDescription based on print resource
590 _aCourse allocation: B. Sc. Software Engineering.
650 0 _aComputer Science
_vTextbooks
653 _aB. Sc. Software Engineering
653 _aUMUN open access collection
653 _aFoundational textbook
655 4 _aElectronic textbooks.
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
_yRead open-access publication
_zOpen access.
_70
856 4 2 _uhttps://open.umn.edu/opentextbooks/textbooks/618
_yOpen Textbook Library catalogue and formats
_70
884 _aCourse selection and automated MARC21 enrichment from Open Textbook Library metadata.
_g20261005
_khttps://open.umn.edu/opentextbooks/textbooks/618
_qlocal
942 _n0
999 _c498
_d498