Software Development Life Cycle (SDLC)

SDLC definition

The modern Software Development Life Cycle (SDLC) consists multiple phases. It starts with chatting about an idea and ends at measuring the metrics of running it in production.

Most important organizational process

Every company is becoming a software company. Therefore the SDLC is becoming the most important organizational process. Effective software development is an essential skill to create value, attract great people, and keep applications secure. To enable this skill organizations are adopting SDLC stacks that help this workflow.

SDLC Stacks

There are a couple of organizations that are building a stack for the SDLC. Below we've listed the stages of the DevOps toolchain and the products available.

Stage Product category GitLab feature GitHub Marketplace Atlassian self hosted / SaaS Legacy Open Source
Plan Chat Mattermost n/a HipChat / Stride IRC
Plan Issue tracking GitLab Issues GitHub Issues JIRA / Trello Redmine
Plan Kanban boards GitLab Boards ZenHub JIRA / Trello Kanboards
Create Version control GitLab GitHub BitBucket Server/.org SVN
Create Code Review GitLab GitHub BitBucket Server/.org Gerrit
Verify Continuous integration. GitLab CI Travis CI Bamboo / BitBucket CI Jenkins CI
Package Container registry GitLab Container Registry n/a n/a SonarQube Nexus
Release CD/Release automation GitLab CD n/a Bamboo / BitBucket Pipelines Jenkins Pipeline
Configure Configuration management GitLab Secret variables n/a n/a / Environment variables Puppet
Monitor Monitoring GitLab Metrics Sentry n/a Nagios
Subject GitLab GitHub Atlassian
Preferred platform Kubernetes Heroku n/a
Single tenant install (self-hosted) Integrated Needs other products Separate products, CI/CD not actively developed
Multi tenant install (SaaS) Integrated Needs other products Includes CI/CD, issues in JIRA, no monitoring

Cloud Native work-flow

Cloud Native means developing applications to run in the cloud. The platform for deploying these applications is switching from Virtual Machines (AWS) to Container Schedulers (Kubernetes). Cloud native applications are split up into micro services. This means one application consists of many services that each have their own project and code base. To handle these cloud native work-flows GitLab has sub-groups, Auto DevOps, and multi-project pipelines

An integrated product brings emergent benefits

GitLab is the only integrated product for the SDLC, all others are combinations of different products. Having one product makes for a much better user experience because there is one UI, better security because of consistent permission settings, and less time spend on administration and integration. Apart from that this 'development operating system' has some emergent properties that wouldn't otherwise be possible:

These emergent properties allow the following emergent benefits:

Open source is the future of software development

GitLab is developed out in the open with most code available under an open source license. This allowed more than 1500 experts to contribute their process in the form of code. GitLab distills the greatest collection of DevOps best practices into a cloud native work-flow. Our integrated product allows you to stand on the shoulders of many experts.