Process of Sofware Development 2/2

Please click here for Process of Software Development Part 1

5.0 Testing

This becomes part of the software development process because testing is all about the Build, Test, Fix cycle. Essentially Development build it, Test check it works, and if it doesn't, then pass it back to Development to fix.

This then becomes an iterative cycle consisting of fixes being packaged into builds by development which are then released into test for the bugs to be checked.

6.0 Deployment

Once the software code base has passed test the development team need to deploy it into the live or production environment. Once done this deployment task ends the active part of the process of software development.

7.0 Maintenance or Warranty

On a project, once the code goes live it will usually have a warranty period of 2-4 weeks in which the code needs to be maintained by the project team.

If it is simply a piece of software which has been bought from an external supplier then it will usually be the subject of a maintenance agreement which will probably included a number of upgrade build deployments during the year. This would include things such as CRM systems (Siebel , Chordiant), CMS systems (Vignette, Blue Martini) and SAP (Finance and HR).

Even if it is a bespoke piece of software specifically development by an external supplier there should be a warranty period as well as maintenance contract in place to support it.

Process of Software Development - Tip

The software development process is relatively straightforward in theory and doesn't really change in practice no matter which software development model you are using. Just remember in your project plan, that there is a great deal of prep work which needs to take place before actual coding can start.

Further getting formal approval of high level designs and software design definitions is vital to negate any problems or disagreements later on. It is not something any good software architect will be keen on doing, because they are usually more interested in techie stuff not paperwork, but you need to push them to get through the approval process to make both their and your lives easier further into the project management life cycle.

Lastly the quality of the code will make or break a software development project. There is no guarantee it will be good quality should this process and paperwork be followed, but it is a much more likely conclusion if it is followed.

---