A software life-cycle is a methodology (blue print) in which certain predefined steps are taken to guarantee a successful outcome of a project. Here is a ordered list of the steps: requirements definition, design document, rapid prototype, application coding / network building, system testing, and user testing / acceptance.

The first step of any project is defining what needs to be done, the business problem to be solved.  The requirements definition document is used to write down the needs of the client.

The second step of any project is defining how a computer program or network configuration will solve the clients needs. The design document lists out the technologies that will be used in the solution. 

The third step of any project is a rapid prototype of the program to show proof of concept to the client.  Many times, this program contains a mockup of screens and reports with no real coding being accomplished.  This prototype allows the client to view the final layout and make changes before a significant coding effort has taken place.

The forth step is the actual coding of the application or the building of the network. All of the work is done by the consultant on-site or off-site.

The fifth step is to perform a test of the application or system.  Any bugs or problems can be ironed out before presenting the technical solution to the client.

The sixth and last step is user testing and final acceptance.  The client reviews each decision in the design document to make sure the solution solves the business problem.

[Home] [Services] [Products] [Partners] [Contact Us]

Last Updated 12.29.04