Overview

This practice demonstrates an e-mall project to show how a product R&D team uses the HE2E DevOps framework with CodeArts to develop software from end to end.

This document defines a virtual team and the roles involved in software R&D. It explains how different roles utilize CodeArts' tools—work items, code repositories, tests, artifact repositories, and pipelines—alongside other cloud services, for analysis, design, development, and testing. It serves as a reference for E2E continuous software delivery.

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
Click to enlarge

**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 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.

Background

Company A is an automobile parts dealer. Company A develops "Phoenix Mall", an online store for automobile parts, to boost sales.

The mall manages members, parts, and orders, meeting company A's management requirements and allowing customers to query and purchase products.

The Scrum mode is used for iterative development. Each iteration period is two weeks.

Solution Architecture

This automobile parts e-mall consists of five microservice components.

Figure 2 Technical architecture of Phoenix Mall
Click to enlarge

**Table 2** Architecture
Microservice Component	Description
Web client server (corresponding to the Vote function in the sample code)	Service logic: Users can use a browser to access the web UI of this service. When a user clicks Like on a specific offering, the service saves the record of the selected offering in the Redis cache. Technology stack: Python and Flask frameworks Application server: Gunicorn
Web management server (corresponding to the Result function in the sample code)	Service logic: Users can use a browser to access the web UI of this service. The statistics about Like clicked by users on the UI are dynamically displayed. The data is obtained from the PostgreSQL database. Technology stack: Node.js and Express frameworks Application server: server.js
Background order batch processing program (corresponding to the Worker function in the sample code)	Service logic: This service is a background process. It monitors item records in the Redis cache, obtains new records, and saves them in the PostgreSQL database so that the management UI can extract data for statistics display. Technology stack: .NET Core or Java (This service provides two technology stacks to implement the same function. You can modify the configuration and select one of the technology stacks as the runtime process.)
Order cache	Service logic: Persists data for the client UI. Technology stack: Redis
Order database	Service logic: Serves as the data source of the management UI. Technology stack: PostgreSQL

The following members are involved in the project R&D.

**Table 3** Project role list
Project Member	Project Role	Responsibility
Sarah	Project admin	Plans the project and sets up a team.
Maggie	Project manager	Manages project delivery plans.
Chris	Developer	Develops, compiles, deploys, and verifies project code.
Billy	Tester	Writes and executes test cases.