This article is part of an Essential Guide, our editor-selected collection of our best articles, videos and other content on this topic. Explore more in this guide:
4. - Project prioritization terms to review: Read more in this section
Explore other sections in this guide:
- 1. - Don't sacrifice IT project timelines with your virtual teams
- 2. - Videos for better project prioritization
- 3. - Project management for improving mobile app turnaround time
What is systems development life cycle (SDLC)?
(SDLC is also an abbreviation for Synchronous Data Link Control.)
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.
Various SDLC methodologies have been developed to guide the processes involved, including the waterfall model (which was the original SDLC method); rapid application development (RAD); joint application development (JAD); the fountain model; the spiral model; build and fix; and synchronize-and-stabilize. Frequently, several models are combined into some sort of hybrid methodology. Documentation is crucial regardless of the type of model chosen or devised for any application, and is usually done in parallel with the development process. Some methods work better for specific types of projects, but in the final analysis, the most important factor for the success of a project may be how closely the particular plan was followed.
In general, an SDLC methodology follows the following steps:
- The existing system is evaluated. Deficiencies are identified. This can be done by interviewing users of the system and consulting with support personnel.
- The new system requirements are defined. In particular, the deficiencies in the existing system must be addressed with specific proposals for improvement.
- The proposed system is designed. Plans are laid out concerning the physical construction, hardware, operating systems, programming, communications, and security issues.
- The new system is developed. The new components and programs must be obtained and installed. Users of the system must be trained in its use, and all aspects of performance must be tested. If necessary, adjustments must be made at this stage.
- The system is put into use. This can be done in various ways. The new system can phased in, according to application or location, and the old system gradually replaced. In some cases, it may be more cost-effective to shut down the old system and implement the new system all at once.
- Once the new system is up and running for a while, it should be exhaustively evaluated. Maintenance must be kept up rigorously at all times. Users of the system should be kept up-to-date concerning the latest modifications and procedures.
|Getting started with the systems development life cycle|
|To explore how the systems development life cycle is used in the enterprise, here are some additional resources:|
|Varying SDLC methodologies among development teams: Software development life cycle (SDLC) methodologies have their own advantages, tools and so forth. Expert David Christiansen explains why development groups should be allowed to embrace a variety of methodologies.|
|How use cases facilitate the SDLC: Why incorporate use case techniques into your software development lifecycle? Requirements expert Betty Luedke explains how use cases benefit the SDLC and how practitioners can get the most out of them|
|When to begin testing in the SDLC: Testing is one of the most important components of the software development lifecycle, but when to begin testing depends on a number of factors. Expert Mike Kelly discusses how certain issues affect the timing of testing in the SDLC.|