All life on earth fulfills the cycle of life; born, grow, reproduce and, finally, die. In software it’s sort of the same process. It begins with the “born” process, except, unlike many of us, it’s not an accident.
The first step, as in all things, it’s to plan. You cannot go straight to the computer and start typing whatever comes into your mind and hope for the best. It’s never like that. You have to communicate to the stakeholers of the project and they have to communicate with you to make clear what the software can do, how will it do it, when will it do it, etc. This is the foundation for the whole project, so it is very important to make everything clear and that you understand the requirements of the problem.
Then we analyze the requirements set by the previous step. In this step facts are gathered and interpreted in order to make decision about changes in the software, what will be the scope of the program, what problems will be faced and how are they going to be solved.
The design. At this level, the architecture of the software will be define as best as posible, as well as the documentation of the project. The architecture must containe how the data will be handle, if a third party software will be used, and all the internal details of the program. and then FINALLY we get to code. On to the implementation.
This is the dream stage, the actual coding, the beginning of the development. The coder writes with the help of the guidelines set before this stage, all the data flow charts, the architecture, the 3rd party software, everything in the documentation is applied here, the coder reads these requirements and choose the correct language for the implementation. The the software goes to production, at this point we can safely asume that the program is a young adult, ready for action.
First the software is tested for bugs, malfunctions, “features”, errors and mistakes, then is reported, checked, fixed, and test again. Testing is only for the code itself, it’s a good practice to ask yourself if the product met the clients expectations, what part of the plan change, what was the most difficult part of working on it.
And the last stage is a iteration of taking care of the final product, ensuring that it remains relevant and functional aswell as with the highest standars of quality.
Tricia Hussung. (2016). What Is the Software Development Life Cycle?. 21/1/2019, de Husson University Sitio web: https://online.husson.edu/software-development-cycle/
Joachin's Singularity 