Programming is just programming. Software has a life cycle: it is conceived, is born, matures, dies and is replaced by newer, younger software. Understanding each of these steps is key in developing maintainable software on budget.

• Conception

  One of the most exciting steps. Everything is easy and makes sense at the beginning of this phase. Usually chalked full of phases such as '....all we have to do is....' and '....really stick to the KISS mentality....' or '....it is so simple it is elegant....' this is also the step where naivety and inexperience will lead the enthusiastic to failure. Software should be a sharp tool with a narrow application. Although this approach at first sounds limited and limiting one only need design applications correctly using modern day methodologies and tool sets to be able to reuse code efficiently. By limiting the concept of software a more clear ( and followable ) path can be charted through the software life cycle.

• Birth

  If you're lucky enough to get here congratulations. Most software stays vapour ware and usually because poor planning and unrealistic expectations. Now you're a proud parent and if it's your first piece of software you will no doubt dote over it needlessly. Now the rest of the world can comment on your baby. How will you react when the first person calls your baby ugly? Eventually that will lead you in the next, and longest, phase.

• Maturation

  This one may be the most poorly named step as it really does encompass the largest time component of most production software. This is the phase during which either the business requirements change or the unplanned for scenarios occur. It is during the maturation phase that the true metal of the programming and planning team is tested. A more properly planned solution will live a longer ( and provide the support staff a more enjoyable ) existance.

• Death

• do while { }