I do understand the concept of Software Development Cycle. I wanted to know if there is any other software development cycle. As I answer the question during interviews I was told that I was missing a step.
There's a lot more before the time when you get the requirements and a lot after the product gets to testing. I don't think anyone can give you *the* answer to this question as many different organizations tailor the lifecycle to their needs. I'd go with JA's approach and do a google search or browse around through SEI's CMM documentation. There are probably also some documents in the downloads and links section of this site.
Pick one tell the name and add there are others.
Like RUP "Short for Rational Unified Process, a software development methodology from Rational. Based on UML, RUP organizes the development of software into four phases, each consisting of one or more executable iterations of the software at that stage of development.
inception -- In this stage, the projectís business case is stated and the team decides if the project is worth doing or if it is even possible. It is important to the process to first formulate the scope of the project and also determine what resources will be needed.
elaboration -- In this stage, the developers take a closer look at the project to determine its architecture foundation and to evaluate the architecture in relation to the project. This stage is important to the RUP because it is here that developers analyze the risks associated with changing the scope of the project or adding new technologies along the way.
construction -- In this stage, the development of the project is completed. The application design is finished and the source code is written. It is in this stage that the software is tested to determine if the project has met its goal laid out in the inception phase.
transition -- In this stage, any fine-tuning is performed. Any final adjustments can be based on user feedback, usability or installation issues." straight from www.webopedia.com