SDLC Phases?

The systems development life cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project, from an initial feasibility study through maintenance of the completed application .

 SDLC Phases:-

• 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.

• Requirement

In engineering, a requirement is a singular documented need of what a particular product or service should be or perform. It is most commonly used in a formal sense in systems engineering or software engineering. It is a statement that identifies a necessary attribute, capability, characteristic, or quality of a system in order for it to have value and utility to a user.

• 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.

• Implemantion

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.

• 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.

• 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.

• Maintinance

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.