Software life cycle includes feasibility study phase, requirement analysis phase, design phase, realization phase, testing phase, and maintenance phase.
Expanded:
Software Life Cycle (SLC) is a life cycle in which software is created until it is scrapped or discontinued. There are phases within the software life cycle such as problem definition, feasibility analysis, general description, system design, coding, debugging and testing, acceptance and operation, maintenance and upgrading to obsolescence, and there are also iterative phases that combine the activities of the above phases, i.e., iteration as a phase of the life cycle.
The software life cycle, also known as the software life cycle or system development life cycle, is the generation of software until the end of the life cycle, the cycle has a problem definition, feasibility analysis, general description, system design, coding, debugging and testing, acceptance and operation, maintenance and upgrading to abandonment and other stages,
This time-phased approach to thinking is a principle of thinking in software engineering, that is, step-by-step, step-by-step, each stage should be defined, worked on, reviewed, and documented for communication or for review, in order to improve the quality of software. However, with the maturity of new object-oriented design methods and technologies, the guiding significance of the software life cycle design approach is gradually diminishing.
Each cycle of the life cycle has a defined task and produces documentation (information) of a certain specification, which is submitted to the next cycle as a basis for continued work. According to the software life cycle, the development of software no longer only emphasizes "coding", but outlines the entire process of software development.
Software engineering requires that the beginning of each cycle of work can only be established in the previous cycle of results "correct" on the premise of the continuation of the cycle; therefore, each cycle is according to the "activity-results-audit-activity-until the result is correct". Therefore, each cycle progresses in a "activity-result-review-activity-until-result-is-correct" cycle.