foo site: Website Coding

Life Cycle of Software for Custom Software Development

Lifecycle of software basically depicts the various important phases or activities, which happens in the 'life' of the software starting from its conception and ending with its retirement. The development of software is a fairly long process which includes various stages like (a) requirement (b) design (c) integration (d) testing (e) operations and (f) maintenance.

Development of software cycle describes the various inter-relationships which now have become a norm followed in the custom software programming circles. This life cycle includes:

The waterfall method: This is by far the most rigid of all the custom software programming life cycles. However, it's well suited for projects that follow a well defined structural design have a strong performance requirements hierarchy. It is also the chosen method for custom software development services in which developers already well aware of requirements expected of the software, which are unlikely to drastically change during the course of its development.

The Extreme Programming Method: It's the latest manifestation of the Waterfall model, thereby making it the current fad of developers working on custom software programming. Given the fact that it retains quite a few eccentricities of the waterfall model it too doesn't work all that well on development of software projects which have shifting or complex requirements. The XP (extreme programming) model basically believes in starting the coding as soon as possible without creating an actual prototype of the software, which can be shown to the client for his/her approval.

Throwaway prototyping: Advocated by Brooks, the Throwaway prototyping model for development of software is useful in situations the client has been unable to clearly define his requirements. Custom software development services follows this approach by constructing partial but workable prototype of the system thereby giving the client the liberty to work on this incomplete software, identify the grey areas which can then filled in by the programmers.

Most professional programmers prefer to use the software life-cycle because it's helps them avoid the problems of a 'wild hacker' or a 'government bureaucrat', thus helping developers follow a flexible middle path.

About the Author:

I am the webmaster at www.synapseindia.com ' A web development company offering custom software development services to businesses in India and abroad.