The Software Development Life Cycle - Conclusion

I am very excited to be concluding this series on the software development life cycle.

I would like to specially appreciate the writers of the IEEE Guide to the Software Engineering Body of Knowledge 1 and the Wikipedia entry on Systems development life cycle 2, materials heavily referenced and upon which this series is built upon.

To conclude this series, I will go through the key concepts and terms we have discussed in the software development life cycle.

Overview

As we discussed earlier, the Software Development Life Cycle are the (what) phases involved in creating (why) high-quality software in (where) controlled environments during a (when) software design and development project through the (how) agile, iterative, or sequential methodologies

There are five (5) SDLC phases 1 i.e. - The planning phase is concerned with (what) making plans to develop a software product or service. This may involve defining a minimum viable product or an ideal software version, creating project documents, and/or carrying out product-to-market fit. The planning phase ends with a decision for or against continued work or development of the intended software. - The design phase is concerned with (what) transforming software requirements, success factors, properties and functions into a detailed software design document which can be used to deliver the proposed software - The development phase is concerned with creating a working software prototype as defined in the software design document (how) through writing programming code, no code solutions, reuse/modification of existing software or software components - The testing phase is concerned with ensuring that the current software version conforms to the requirements defined in the software planning and/or design document by (how) rectifying defects and validating fixes - The operations/maintenance phase is concerned with ensuring that the software version is reasonably up-to-date, secure, and improved in the face of environmental changes, new user requirements, discovery of faults, and newer techniques/software/solutions

Design and Development refers to a project session been carried out by one or more individuals.

High quality software is software that meets and/or exceeds customer expectations and is delivered within scheduled time frames and cost estimates.

A SDLC methodology is a unique method, order, and purpose of using the SDLC phases e.g. agile, iterative, or sequential methodologies.

An environment is a controlled area where software developers build, distribute, install, configure, test, and execute systems that move through the SDLC.

Take care!

On giants shoulder’s (References):