PLANNING: Planning focuses on the Scope of the Project. The output of the planning phase include: Projects Plan, Schedules, Cost Estimations & Procurement Requirements
REQUIREMENTS: The IT Team gathers requirements from Business Stakeholders and subject matter experts (SMEs). The Output of these phases in a waterfall project is usually a document that lists these requirements. Agile methods, by contrast, may produce a backlog of tasks to be performed.
DESIGNS AND PROTOTYPING: Once requirements are understood, the design process takes place. It makes the use of established patterns for application architecture and software development. Architecture frameworks like TOGAF may be used here. Outputs Include Designs Documents that list the patterns and components selected for the project, code produced by Spikes, used as a starting point for development.
SOFTWARE DEVELOPMENT: This phase produces the software under development. This could be in “Sprints” (Agile). Or a single block effort (Waterfall). The output of this phase is testable, functional software.
TESTING: This testing phases of the SDLC is arguably one of the most important. It is impossible to deliver quality software without testing methods for testing can include: Code quantity, unit testing (functional Tests), Integration testing, performance testing, security testing. The output of the testing is functional software, ready for deployment to a production environment.
DEPLOYMENT: The deployment phase is, Ideally a highly automated phase. In high-maturity enterprises, this phases is almost invisible; software has deployed the instant it is ready. Enterprises with the lower maturity, or in some highly regulated industries, the process involves some manual approvals. The output of this phase is the release to production of working software.
OPERATIONS & MAINTENANCE: The operations and maintenance phase is the end of the beginning. through the SDLC doesn’t end here. The software must be monitored constantly to ensure proper operations. Bugs and defects discovered in production must be reported and responded to, which often feeds work back into the process. Bugs fixes may not flow through the entire cycle, however at least an abbreviated process is necessary to ensure that fix does not introduce other problems.