Software Development Life Cycle main phases

Development life cycle of a product

The development life cycle of a product or a feature is a wide process that includes specifications, development, and testing, deployment into QA and Production environments, maintenance as well as migration.

Specifications, which is the conceptual part of the process (technical requirements, task assignments and so on.). For more information, see Specifications.
Development, testing, and deployment, which are the designing and publishing parts of the process. For more information, see Developing and Testing and Building and Deploying.
Deployment into QA and Production environments. For more information, see Deploying to QA and Production environments.
Maintenance which is mainly achieved through GIT branching and tags. For more information, see Maintaining.
Migration.

Continuous Integration (CI) is a development practice where members of a team integrate their work frequently, each integration being verified by an automated build to detect integration errors as quickly as possible.
Continuous Deployment (CD) is a practice where the code changes that passed automated testing can be rapidly and safely deployed to production.
Build automation is a best practice used during the software development life cycle to compile and package source code with an automation build script.
For example, Talend users can export the sources of a Job they created in Talend Studio as a zip file using Maven and they can re-use this generated archive file in Talend Management Console to schedule the next executions of this Job.
Version control and Source Code Management (SCM) allow you to manage and track the changes made to the software by assigning revisions to these changes. Talend achieves this thanks to its shared Repository and branching system based on Git. For example, Talend users can use the Repository that is shared between Talend Studio and other applications, as well as its branching system to version changes.

Profiles

Example set of the main persona that are involved in the phases of a product life cycle.

Alan the Project Manager (Analysis and Requirements / Specifications Phase): Alan drives the project architecture and picks technologies to be used. He is in charge of designing the specifications along with business managers and developers.
Jim the developer (Development and Tests + Maintenance Phases): Jim designs and implements Jobs and components in the Development environment. They also create and run tests for the Jobs they designed, then pass these Jobs to Thomas. If needed, they can handle maintenance by fixing errors or improving the software to meet new technical requirements.
Thomas the Quality Assurance engineer (QA Tests Phase): Thomas creates and executes test suites on features and products using manual (based on user scenarios) and automated build tests (using Test Cases) in the QA environment. He also sends regular result reports to Megan.
Megan the Operation/Release Manager (Go Live Phase): Megan approves the release candidate build (RC) and deploys it to Production when she is sure all tests have passed.

Development life cycle of a product

SDLC-related concepts

Profiles

Did this page help you?