Software Development Life Cycle

sdlc

The result of a well-coordinated team effort is a product or software:

  • pizza delivery website
  • mobile banking app
  • web browser

Software Development Life Cycle (SDLC) describes the key stages of the software creation process. The earlier a QA engineer detects bugs, the cheaper they are to fix.

Stages of the Software Development Life Cycle

1. Planning

The planning stage involves allocating resources for project implementation, assessing risks, and defining expected outcomes.

2. Analysis

Analysts gather information from stakeholders, prepare documentation, and describe the product requirements.

3. Design

At this stage, requirements are further detailed, interaction diagrams and screen mockups are created.

4. Development

Developers study the requirements described by analysts and write the application’s source code.

5. Testing

Testers come into play — the product must not be released for production use without full confidence in its correct behavior.

6. Maintenance

After a successful release, the product may need functional improvements or bug fixes reported by real users.

Software Development Models

The most popular development models based on SDLC stages: Waterfall Model and Agile Model.


Waterfall Model
waterfall-sdlc-model

Waterfall Model is a classic development model. Each stage depends on the successful completion of the previous one. Suitable for projects with clear requirements and rare changes.

  • Requirements are defined at early stages
  • Strict control over the development process
  • Facilitates time and cost estimation for each stage
  • Changing requirements is difficult and costly
  • Lack of quick feedback can lead to unmet customer expectations
Agile Model
agile-sdlc-model

Agile Model focuses on iterative development, rapid delivery of working product versions, and constant customer collaboration. The previously discussed Scrum follows the Agile model.

  • Adaptation to changing requirements
  • High speed of delivering a working product
  • Quick feedback
  • Often lacks sufficient attention to documentation
  • Customer’s active involvement may slow down development
After which stage does the product become available to the end user?
Sidebar arrow