What is Software development life cycle?

I would like to know the different stages, if possible.

What is Software development life cycle?
The software development lifecycle consists of the following stages:





Requirements Analysis


Specification


Software architecture


Implementation (or Coding)


Testing (including beta releases)


Documentation


Software Training and Support


Maintenance





There are several processes for completing these stages with the oldest being the waterfall model, where developers follow these steps in order.





Iterative development calls for construction of small portions of a project so all steps are at least started early on to catch problems and faulty assumptions. This type of development relies heavily on feedback.





I just completed a help file for a company that used the extreme programming process which, is the best-known agile process. In XP, the phases are carried out in extremely small, continuous steps compared to the older, "batch" processes. The company developed software in this way because the powers that be believed that being able to adapt to changing requirements at any point is a more realistic and better approach than trying to define everything at the beginning and then spending time controlling changes to the requirements. The downside to the XP method is the increased likelihood of scope creep.
Reply:I would add support/bug fixes to the other guy's list.
Reply:Software development life cycle.


Request / Inquiry: a need for a software solution


Analysis : Detail discussion with end user to find out all nessasary requirement. And you never know what they may come up next.


Design: as implied all layout intput/output GUI are considered


Development: buy required equipments hardwares to meet analysis REQ


Deployment: use software develop on multiple PC configuration to make sure the software work.


Maintainance: most important meet requirement changes includes Gasp! Debugging


Refinement: make it better.
Reply:Well then you get the'beta' stage and we all become 'lab rats' if it is Microsoft - Internet Explorer 7 smashed my computer - honestly but this 'road testing ' on the public is plain wrong.
Reply:The answer from scmduplessis is excellent, apart from one thing. He puts documentation after testing. But if the system isn't documented, the testers won't know what it's supposed to do!





So before testing can be completed, you need enough documentation that the testers will know what the various screens should look like, what options they allow, what each button should do, and so on.





This is just one example of how the different phases of the life cycle impact on each other. I bet that every phase actually has some impact on the one before it and the one after it.
Reply:It used to be called 'waterfall' methodology because you didnt' start one stage before the other one was done. Now, you can kinda blend the ending / starts together.





Requirements (from user)


Analysis (from development team of level of effort)


Design (of proposed system


Build


Test


Implementation (delivering application to user)