Project life cycle

Traditional project life cycle

For a traditional software project, it consists of the following five phases:

1. Research Stage

  • Purpose: Prepare for danger in times of peace
  • Personnel: Relevant personnel, with emphasis on product managers
  • Node: multi-angle thinking/plan, finally the leader to make a decision

2 Design Stage

  • Objective: To visualize the scheme
  • Personnel: product team leading, development, testing, operation and maintenance involved
  • Nodes: product requirements document, project odometer

3 Development Stage

  • Purpose: Scheme running
  • Personnel: development team, operation and maintenance team
  • Node: Phase The project is running properly

4 Test Phase

  • Objective: To ensure the functional perfection of the project
  • Personnel: mainly test team, operation and maintenance, development participation
  • Node: The project functions meet requirements

5 Operation Phase

  • Purpose: Project deployment + operation and maintenance
  • Personnel: operation team, development/product team
  • Nodes: project termination, function iteration, etc

New project life cycle

Deployment of software projects

  • Deployment process – Design reasonable deployment solutions based on project functions
  • Deployment projects – Smooth project deployment with deployment solutions

Deployment process

It consists of two parts: Deployment scheme and deployment environment

Deployment plan

  1. Analyze the product requirements document of the project, obtain the main idea of the project, and determine the direction of the deployment solution
  2. Analyze project development documents and design deployment nodes according to functional boundaries
  3. Analyze boundary functions, investigate functional software, make reasonable choices, and select the ones that meet the current business scenarios
  4. Sort out the deployment software implementation schemes involved in project deployment, and determine the initial deployment scheme according to the nodes determined in 2
  5. Adjust and optimize the project deployment plan according to the actual situation of the project

The deployment environment

According to our understanding of the project life cycle, a project needs to go through the work of multiple teams to finally form a finished product, that is to say, the developed project needs to be deployed in a multi-stage environment according to our deployment plan, and the environment of each stage has its special role. So let’s take a look at the five environments involved in project release:

Personal development environment

  • Staff: Myself
  • Working platform: personal laptop, company computer
  • Platform features: The environment is customized, and the individual development environment on the team can be different
  • Work content: sub-module and sub-function of the project
  • Completion criteria: Completion of the content assigned by the leader [functional sub-module development of the project]

Company development environment

  • Staff: Development team
  • Working platform: company internal server
  • Platform features: The server environment is exactly the same as the online server environment
  • Job description: Functional coordination between project sub-modules
  • Completion criteria: the project stage development and debugging are completed

Project test environment

  • Staff: Test team
  • Platform: company internal server
  • Features: The server environment is exactly the same as the online server environment
  • Content: functional/non-functional/exploratory tests of the project
  • Standard: Normal operation of project phase functions

Pre-release environment

  • Personnel: Operation and maintenance team
  • Platform: one of the company’s online servers
  • Features: The server environment is exactly the same as the online server environment
  • Content: Special functional tests (such as payments), data stress tests, other security tests, etc
  • Standard: Functional normal operation of the project phase, the last line of defense

Project Online Environment

  • Personnel: Operation and maintenance team
  • Platform: company online server group
  • Features: Standard online server environment
  • Content: Code deployment and maintenance
  • Criteria: Normal operation of the project