systems development life cycle

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:

1. The existing system is evaluated. Deficiencies are identified. This can be done by interviewing users of the system and consulting with support personnel.
2. The new system requirements are defined. In particular, the deficiencies in the existing system must be addressed with specific proposals for improvement.
3. The proposed system is designed. Plans are laid out concerning the physical construction, hardware, operating systems, programming, communications, and security issues.
4. 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.
5. 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.
6. 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.

Read more about systems development life cycle: - The Center for Technology in Government at the State University of New York in Albany provides a survey of systems development models. - SearchVB.com provides links to more information about program development. - Learn IT: Software Development has more information about development methods.

Do you have something to add to this definition? Let us know. Send your comments to techterms@whatis.com

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT How to choose a software testing methodology Choosing the right testing methodology, be it agile, waterfall, V-model or spiral model, depends on the software project, explains expert John... Implementing the IBM Rational Unified Process and Solutions: A Guide to Improving Your Software Development Capability and Maturity -- Chapter 2, Your First Steps The Rational Unified Process (RUP), a software development methodology, may be a good fit for your needs. This free chapter outlines how to promote... 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...

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary Capability Maturity Model  (SearchSoftwareQuality.com) collaboration diagram  (SearchSoftwareQuality.com) A collaboration diagram, also called a communication diagram or interaction diagram, is an illustration of the relationships and interactions among...