LDR | | 05379cmm u2200565Ki 4500 |
001 | | 000000316278 |
003 | | OCoLC |
005 | | 20230525180119 |
006 | | m d |
007 | | cr cnu---unuuu |
008 | | 190622s2019 enk o 000 0 eng d |
019 | |
▼a 1103987016 |
020 | |
▼a 1838988572 |
020 | |
▼a 9781838988579
▼q (electronic bk.) |
035 | |
▼a 2153720
▼b (N$T) |
035 | |
▼a (OCoLC)1104089495
▼z (OCoLC)1103987016 |
037 | |
▼a 10E90570-F728-4E71-9BEE-C19F54FC15D2
▼b OverDrive, Inc.
▼n http://www.overdrive.com |
040 | |
▼a EBLCP
▼b eng
▼e pn
▼c EBLCP
▼d TEFOD
▼d OCLCF
▼d OCLCQ
▼d YDX
▼d UKAHL
▼d OCLCQ
▼d N$T
▼d 248032 |
049 | |
▼a MAIN |
050 | 4 |
▼a QA76.758 |
082 | 04 |
▼a 005.16 |
100 | 1 |
▼a Annett, Robert. |
245 | 10 |
▼a Working with Legacy Systems :
▼b a Practical Guide to Looking after and Maintaining the Systems We Inherit. |
260 | |
▼a Birmingham :
▼b Packt Publishing, Limited,
▼c 2019. |
300 | |
▼a 1 online resource (152 pages) |
336 | |
▼a text
▼b txt
▼2 rdacontent |
337 | |
▼a computer
▼b c
▼2 rdamedia |
338 | |
▼a online resource
▼b cr
▼2 rdacarrier |
505 | 0 |
▼a Cover; FM; Table of Contents; Preface; Chapter 1: Definition, Issues, and Strategy; What is Legacy?; An IT-Centric View of the World; Systems Development in Context; Systems Development Scaled with Time; Examples of Real Legacy Systems; Common Issues; No Documentation; Lost Knowledge; Hidden Knowledge; Unused Functionality; No Coherent Design/Inconsistent Implementation; Fragility (versus Stability); Tight Coupling; Loose Coupling; Zombie Technologies; Licensing; Regulation; Politics; Organization Constraints and Change are Reflected in the System |
505 | 8 |
▼a External Processes Have Evolved to Fit around the SystemExternal Systems Have Evolved to Fit around the System; Decaying Data; Now What?; Reasons to be Cheerful; A Legacy System is a Successful System; You Have Real Users You Can Talk To; You Can Learn a Lot about the Business; You Can Have a Large Impact Quickly; It's Important, But Not Trendy, So You'll Get Paid Well!; Strategies; Ignore It; What is it?; Investigation; Maintenance; Upgrade; Migration; Incremental Improvements; Replacement; A Special Note on Decommissioning; Conclusion; Chapter 2: Investigation and System Review |
505 | 8 |
▼a Architectural Description and ReviewStakeholders; Locate the stakeholders; End Users; Support Staff; System's Infrastructure Staff; Audit and Compliance; Budget Holders; Third-Party Suppliers; Developers/Software Engineers/Database Analysts; Document the Stakeholders; Architectural Sketches; Why Sketch?; Context Diagram; Container Diagram; Component Diagram; C4 -- Classes; Further Analysis; What Else Can Be Done?; Further Static Analysis; Further Dynamic Analysis; Security Considerations; Passwords; Account Maintenance and Life cycle; Cryptographic Keys; Certificates |
505 | 8 |
▼a Third-Party Passwords and KeysLack of Patching; Moving from Closed to Open Networks; Modernizing Data Formats; New Development and Copied Data; Server and Infrastructure Consolidation; Improved Backup Processes; Checklist of Questions and Actions; Chapter 3: Making Changes; Safely Making Changes; Virtualization Is Your Friend; 50,000-Foot View of the Virtualization Process; Actions to Make a System Safe to Change; Preparation Issues; External Dependencies Required for Testing; Duplicate Test System Data Becomes Stale Quickly; Internal Coupling Stops You Swapping Components |
505 | 8 |
▼a Changes Cause Unexpected ErrorsLicensing and Regulation Issues Running Multiple Copies; Structural Changes for Disaster Recovery/High Availability; Stabilization; Why Stability?; What Have We Achieved Already?; Bad Data; Removing Unwanted Data; Data Cleansing; Removing Unneeded Components; Removing Unneeded Tasks; Process Cleansing; Removing Unused User Options; Don't Underestimate a Resource Boost; Re-Examine your Application Settings; Optimize the Users' Actions; Leaving a Good Legacy; Why Bother Leaving a Good Legacy?; Documentation; Tests; Design Considerations; Appendix A: Example Legacy Scenario. |
520 | |
▼a The IT industry is obsessed with new technologies. Courses, books, and magazines mostly focus on what is new. Starting with what a legacy system looks like to applying various techniques for maintaining and securing these systems, this book gives you all the knowledge you need to maintain a legacy system. |
588 | 0 |
▼a Print version record. |
590 | |
▼a Added to collection customer.56279.3 |
650 | 0 |
▼a Software reengineering. |
650 | 0 |
▼a Software maintenance
▼x Management. |
650 | 0 |
▼a Computer architecture. |
650 | 7 |
▼a Computer architecture.
▼2 fast
▼0 (OCoLC)fst00872026 |
650 | 7 |
▼a Software maintenance
▼x Management.
▼2 fast
▼0 (OCoLC)fst01124205 |
650 | 7 |
▼a Software reengineering.
▼2 fast
▼0 (OCoLC)fst01124215 |
655 | 4 |
▼a Electronic books. |
776 | 08 |
▼i Print version:
▼a Annett, Robert.
▼t Working with Legacy Systems : A Practical Guide to Looking after and Maintaining the Systems We Inherit.
▼d Birmingham : Packt Publishing, Limited, 짤2019
▼z 9781838982560 |
856 | 40 |
▼3 EBSCOhost
▼u http://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&db=nlabk&AN=2153720 |
938 | |
▼a Askews and Holts Library Services
▼b ASKH
▼n AH36368529 |
938 | |
▼a ProQuest Ebook Central
▼b EBLB
▼n EBL5784242 |
938 | |
▼a YBP Library Services
▼b YANK
▼n 300576896 |
938 | |
▼a EBSCOhost
▼b EBSC
▼n 2153720 |
990 | |
▼a 관리자 |
994 | |
▼a 92
▼b N$T |