Help Center/ CodeArts Req/ Best Practices/ Huawei E2E DevOps Practice: Managing Requirements/ Overview
Updated on 2026-09-15 GMT+08:00
View PDF
Share

Overview

HE2E DevOps Framework

This framework is an operable and implementable agile development methodology proposed by CodeArts using both our experience and advanced industry practices.

Figure 1 HE2E DevOps implementation framework
Table 1 HE2E DevOps implementation framework

Stage

Description

Planning and Design
The first two steps in the diagram depict the product planning process where service personnel (or customers) collaborate with technical personnel to establish the product's overall logic, plan and design the product, and break down requirements at a specific granularity.
  • Software development solves issues and delivers value, not just simply provides functions. Impact mapping identifies user requirements and root causes.
  • User stories convey objectives and requirements in specific scenarios, facilitating communication between customers, service personnel, and developers. If you only view separate requirement items, you cannot consider them from the entire solution's perspective. User stories focus on scenarios, sorting out and displaying stages and activities in a tree structure. In this way, you will view both requirement items and overall requirement scenarios.

Planning and Tracking

Steps 3 to 10 belong to the Scrum framework and are also the main management practices.

  • Scrum defines a relatively complete framework for agile process management. In CodeArts, the Scrum framework is integrated with your team's daily development activities. Main process deliverables include the product backlog, sprint backlog, potential deliverable product increments, and issue list. Core team activities include sprint planning meetings, daily Scrums, sprint reviews, sprint retrospective meetings, and daily updates.
  • In addition, your team can learn from the lean thinking in Kanban, visualize value streams, and identify and resolve blockage and bottlenecks. These actions help to accelerate value stream delivery and feedback loop for continuous improvement.

Iteration

Continuous Delivery
Starting from step 11 is the engineering practice, that is, the CI/CD process.
  • Continuous delivery is based on code repositories. It not only covers traditional security control of code assets, concurrent development, and version and baseline management, but also reflects team collaboration and communication.
  • The pipeline connects code check (or static scanning), automated build, automated testing in all stages, and automated deployment.
  • In addition to dynamic stages and activities like code check, build, testing, and deployment, continuous delivery also involves artifact and environment (development, test, quasi-production, and production) management.
  • The continuous delivery pipeline manages stages, environments, stage activities, entry and pass quality gates, and input and output artifacts in each stage.

Application Scenario

We will use the sample code for an auto part e-mall named "Phoenix Mall" and the "DevOps Full-Process" sample project to describe how to use CodeArts to implement the HE2E DevOps framework. This solution is applicable to Scrum R&D projects.

Solution Architecture

  • Composition of the DevOps Full-Process Sample Project

    This project uses Scrum and presets some service templates. Products and services involved in this project.

    Table 2 List of involved products/services

    Service

    Description

    CodeArts

    Req

    Presets three planned and completed Sprints, project module settings, and several statistical reports.

    Repo

    Presets the code repository phoenix-sample to store project sample code.

    Check

    Presets four tasks.

    Build

    Presets five tasks.

    Artifact

    Stores software packages generated by build tasks.

    Deploy

    Presets three applications.

    TestPlan

    Presets more than 10 test cases in a function test case library.

    Pipeline

    Presets five pipelines.

    Other components and services

    Identity and Access Management (IAM)

    Manages accounts.

    SoftWare Repository for Container (SWR)

    Stores Docker images generated by build tasks.

    Cloud Container Engine (CCE)

    Deploys software packages, which is different from ECS-based deployment.

    Elastic Cloud Server (ECS)

    Deploys software packages, which is different from CCE-based deployment.