More on Legacy Systems
Join the DZone community and get the full member experience.Join For Free
that's not a legacy system, this is a legacy system.in my last blog on legacy systems i talked about what they were and weren't. in this one i'm going to expand on this and how they fit into the business process lifecycle.
like most developers the centre of my work life is the software development process. this might involve a business analysis phase before and some support afterwards but this is a relatively small percentage of my time.
the 'software development centric' view of the world is below (this is the 'sdlc diagram' and your own process may differ but will share elements). there are two parts that interact with the outside world - requirements and deploy (which may be lightweight and frequent) and the external interactions are wrapped in that.
for some businesses (e.g. public facing web sites) the software is the business and there is no significant period before or after the software development - it occurs constantly. these businesses are very interesting to us developers for this very reason (and therefore the projects often discussed at conferences) but are actually the exception. for the majority of organisations their individual it systems perform a function that constitute only a small part of what they do.
therefore users of our software view the world differently. the software development phase is a very small part of their business processes lifecycle and lifespan. they view the world a little more like this:
most of the processes they execute will originally have been done ‘manually’ (i include generic software tools such as spreadsheets) and may been done this way from 6 months to 100 years. (if you think i'm exaggerating with '100 years' then you should speak to someone who's worked with an old insurance company!)
eventually it will be decided that it is cost effective to develop bespoke software (or spend a lot of effort configuring bpm/crm etc software). this process may be iterative and deliver value quickly but will be mostly complete after a relatively short period of time (compared to the organisation’s lifespan).
it is now fully live and a software team will consider it to now be in its maintenance phase. from the organisation's point-of-view this is where the real value is extracted from the system. very little money is being spent on it but it is being used and either helping to generate revenue or increasing the efficiency of a process.
as time goes on there will be a decreasing number of changes made to it. eventually it will be considered ‘legacy’. ultimately the system will reach end-of-life and replaced when no longer fit for purpose.
if we were going to scale the diagram to indicate time then it might look like this:
these are kind of lifecycle times that i've experienced and yours may differ - this will depend largely on the industries you work within.
therefore 'legacy' should be viewed as a phase in the lifecycle of the process. note that i have a small arrow going back to software development from the maintenance/legacy phase as it may have upgrades or additions made many years after being deployed.
a comment on my previous blog post said that they refer to 'legacy' systems as 'mature' as this has more positive connotations. i think it also accurately reflects legacy as being a stage of a lifecycle rather than any particular indication of quality.
lastly i'm just going to quickly plug my talk at qcon again ( modern legacy systems ) which explores some legacy issues, makes suggestions about approaching them and how to leave a good legacy rather than a bad one. if you haven't booked your place at qcon yet then you can use code anne100 to get £100 off.
Published at DZone with permission of Robert Annett, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.