Although SDLC has different forms and models, it follows certain steps. These steps could have the same name in one methodology but they are treated in a different manner or could lead to something different. We will take a look at some of the common steps that you will find in most methodologies in SDLC.
There are SDLC models that have been created by different developers. Some of them follow the standard steps in a model however; there are those that prefer to create their own type of model. But whatever their model is, they should go through these stages as these determine the outcome of the any SDLC model.
1. Planning – Everything starts with a concept. It could be a concept of someone, or everyone. However, there are those that do not start out with a concept but with a question, “What do you want?” they ask thousands of people in a certain community or age group to know what they want and decide to create an answer. But it all goes back to planning and conceptualization. It is also essential for developers to know that this stage deals a lot with upper management so if you are not the owner of the software development company; you have to deal with them a lot in this stage.
2. Design – Once planning and arguing with the manager or the owner about the plan and somehow convincing them, it is time to design or create a rough plan regarding the software. Developers will work together and decide the initial specifics of the software to be created. They will decide what platform or programming language to use, which will take care the coding of a certain part of the software and even the time frame.
This could be conducted by a project manager along with the developers. The workflow about the project is also laid out. Some will also treat this stage as planning for the back-end operations in developing the software. It is not only important that developers should have a solid plan; they should at least know that something will help them achieve to finish the program faster.
3. Implementation – The first two stages are quite common in all SDLC models. However, things change starting on this stage. When the design and all the things that you need have been laid out, it is time to work on the plan. Some developers, especially those that follow the standard plan of developing software will work on the plan and present them for approval.
However, there are those that follow the iterative plan in SDLC. Iterative SDLC is something revolutionary compared to traditional stages in developing software. Instead of finishing everything and presenting them to the general users or testers, Iterative SDLC will develop the software slowly and each change should be presented to the intended users are at least in a focus group when they are about to be implemented in public. Implementation in some SDLC models is a combination of implementation and testing to a focus group.
4. Testing – This could mean two things depending on an SDLC model. The first type of testing is the actual testing by users. This is usually done in models wherein implementation does not go with pre-testing with users. On the other hand, there are also testing that uses professionals in the field. This testing is aimed in cleaning the software of all the bugs altogether. For software that are set for public release, the software is first tested by other developers who were not in charge in creating the software.
They will weed out the bugs and suggest fixes if every they find one. Once this stage is completed, it is time to test the software not just to the developers but to actual users. Some have been bold enough to offer the software openly to the public but best practices will suggest that you have to invite limited number of people before actually offering the software as a open beta version.
That way, the software and even the hardware that backs up the operation is actually tested. A gradual increase in the number of users will test the power of the server. Some servers, even though created to withstand heat and continuous data processing, could not just handle the pressure when thousands of users all over the world starts to creep in the server.
5. Acceptance – When the software is released to be used by a certain company, acceptance means the software is implemented as an added tool or could be replacing another software that has been found too wanting after years of use. On the other hand, when the software is implemented to the public a new software could be an added software for use. It is difficult to change public software but they are not closing their ears to new software. So developers will always have a fighting chance in the market as long as they implement good software for public use.
6. Maintenance – When the software is implemented, it does not mean that the software is good as it is. All SDLC models include maintenance since there are absolutely no way that a software will be working perfectly. Someone has to stay in the present software to take a look and ensure the program works perfectly. When the software is implemented in public.
Software companies either set up a call center or an e-mail service to address the concerns of the consumer. As we have indicated in previous chapters, Maintenance is quiet an easy task as long as the right food and product is serve in an expected time frame. However, it is always a challenge when something goes wrong. The whole team might not be there to help the developer so addressing a major concern could never be answered.
7. Disposal – Last but not the least, when a software is being outmoded, it is not just all deletion of files. Project managers should take a look at all the affected files of the software and determine which file to protect and dispose. Disposal will also require an efficient purging of documents so that no traces of information could be retrieved from memory devices inside the computer.
If the company is planning to re-use the company computers that is ok but it is an entirely different story when the computer and other related equipments is sold. If you have not deleted the files with a powerful software, the information inside the hard disk could be read through a simple information retrieval software that could open up a lot of possible hacking opportunity. There might be very important information that can be retrieved and be used by the enemy. Transfer of information is also being thought of in this stage since the new software or an update will affect a small number of people or even documents.
These are the common steps in SDLC. Although they might have different versions, they all end up with one thing: creating a software to make the world a better place. These seven steps could be even bigger or expanded depending on the SDLC model that has been followed by different developers. These strategies were created by the same programmers and they sure know that something is needed to be done to create better software.