How to retire (respectfully) legacy systems

Posted by: Natty Gur, on 11 Sep 2009 | View original | Bookmarked: 0 time(s)

They served us for a long period of time, but (for different reasons that I wont cover in this post) now the time to say good bye and to retire them.  Legacy systems exist in each and every enterprise and we all have the experience of retire them. The question is whether your enterprise have a predefine process to retire legacy systems or is just process that happened?   In this post I'll try to share a retirement process for legacy systems. From what I've seen so far in most enterprises, legacy...

Advertisement
Free Agile Project Management Tool from Telerik
TeamPulse Community Edition helps your team effectively capture requirements, manage project plans, assign and track work, and most importantly, be continually connected with each other.
Category: Software | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 830 | Hits: 25

Similar Posts

  • Related EA posts of mine more
  • Silverlight SVC Web Service problems on IIS more
  • WSDL-First in WCF, versus WSDL-First in ASMX more
  • A simple config-less IIS-hosted WCF service more
  • A Brief Aside: WebServiceHostFactory more
  • ServiceHostFactory vs ServiceHostFactoryBase more
  • LU2 Connectivity with Host Integration Server more
  • LogDump: CLRProfiler Log analysis tool more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD