Following my last post, I’m going to outline the the software development life cycle (SDLC).
SDLC is the phases used which create and/or alter information systems and the models and methodologies which people have used to do this.
The SDLC is an extremely structured and methodological way of developing, maintaining and replacing existing information systems.
How did SDLC come about? In 1970 Winston Boyce developed SDLC as a help to programming. It had two phases: analysis and coding. In 1974,only a few short years later, Dr. Barry Boehm listed a number of the main phases of software development.
Reasons for chosing SDLC: The reason for a SDLC process it to help produce a product that is cost-efficient, effective, and of high quality. This can be done by correcting problems in existing software, improving an existing system, change – from an outside group or competition, which also leads to change. For example a company may need a better system in order to produce products quicker, reducing the risks of not meeting demand and letting other companies take their profits.
Benefits of SDLC; SDLC helps to reduce failure, it reduces the risk of a system not meeting consumer needs and it helps ease the process of building a system. It helps to evaluate costs and completion targets, easier control and also it’s easier to maintain.
Disadvantages of SDLC; It is costly and time consuming to develop, the system has to be designed up front, it can be very rigid, it’s very hard to implement costs if the project overruns (for example you may remember Cathal telling us of a friend who has been designing a system for over two years?), user input can also be limited.
I hope this blog has given you a clearer idea of SDLC. I will describe the phases of SDLC in my next post.