• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Re-engineering Legacy Software - Opportunities

 
Greenhorn
Posts: 29
1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am working since last couple of years in the scope of legacy maintenance & modernization. I have come across several options including: tool based migration, platform rehosting & reengineering. I would be typically interested in what this book from 'Chris Birchall' offers. Does this book offer an evaluation of different options available in moving away from legacy? Or a process workflow so far as reeingineering is concerned?
 
Sheriff
Posts: 17644
300
Mac Android IntelliJ IDE Eclipse IDE Spring Debian Java Ubuntu Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
There are three options I've seen given in the book: Refactor, Rewrite, or Replace. Chris gives a lot of good advice in this book about all these options. However, if you're looking for a recipe for a "reengineering process flow," there is none, not in this book nor in any other book you'll ever find out there. Any book that purports to give you such a thing should be treated with extreme suspicion.
 
Junilu Lacar
Sheriff
Posts: 17644
300
Mac Android IntelliJ IDE Eclipse IDE Spring Debian Java Ubuntu Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The book does, however, discuss several ways you can use different technologies to improve process flow. These include automated builds using Jenkins, automated tests, automating the development environment using Vagrant and Ansible, moving infrastructure to the cloud, DevOps, OpenStack, and others. I would caution against just diving in and employing these technologies without clear goals and a good understanding of how they may affect your team's ability to continue to deliver on their commitments. These are not plug-and-play technologies. Some of them have pretty steep learning curves. More importantly, your team(s) also need to adapt their way of working. DevOps and an organization's success in moving to this paradigm has been said to involve a huge cultural change, something that often gets overlooked in the rush to implement the technologies involved.
reply
    Bookmark Topic Watch Topic
  • New Topic