2006-08-22 07:13:30 · 4 answers · asked by phil460cc 1 in Computers & Internet ➔ Programming & Design
Life cycle models describe the interrelationships between software development phases. There are many life cycle models (waterfall model, spiral model, throwaway prototyping model, evolutionary prototyping model, incremental/iterative development model, reusable software model, etc.), so there is no such thing as "the" life cycle model...
2006-08-22 07:27:38 · answer #1 · answered by NC 7 · 0⤊ 0⤋
The Lifecycle model of a software can be interpreted in two fashions:
a) The Development Life Cycle model: This model determines the way the software is developed, and includes Requirement gathering, designing, developing, testing and deploying the software. Additional points of interest in this model is documentation and support of the software.
b) The Life of the software: This model visualizes a larger view of software and includes the actual "life" of the software, from its inception to its "death" i.e. when it is replaced by a better software. Each software follows the same life plan, there is the need to build a software to solve a certain problem, to develop it, to maintain and enhance it and to deprecate it and replace it with a newer software.
While the first model is more abt how the software is built and is limited/extensive in that arena only, for the second model the first is just a part of its entirety.
Hope this helps !
2006-08-22 14:33:45 · answer #2 · answered by bostoncity_guy 2 · 0⤊ 0⤋
Read the very good tutorial given below on SDLC iterative model
http://qafriend.com/sdlc-models/iterative-model
2014-04-28 04:59:46 · answer #3 · answered by Anonymous · 0⤊ 0⤋
depends on who you ask, there are many different methods to developing software.. basically though, its first determining the requirements of the software, then laying out a high-level design and interfaces. Following this, you start filling in details in a detailed design phase, pseudocode, etc. Then you begin the coding/implementation phase. During that, or once its done, you unit test each part of the code, or function, individually. You can backtrack to other steps if problems are found. Then.. system testing/integration if necessary, and when thats done you are set for deployment. Then theres just maintenance, upkeep, additional testing etc. During all this, review mechanisms should be in place at the end of each phase
2006-08-22 14:24:43 · answer #4 · answered by fuzzhead 2 · 0⤊ 0⤋