Cloud Project Development Workflow Linking Requirements, Code, and IDEs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloud services for software development are independent and require manual cross-service process coordination and information tracing, leading to low development efficiency.

Innovation Solution

A cloud service-based project development system with a requirement management node, code hosting node, and IDE management node that automates cross-service process coordination and information tracing by associating project phases through requirement information, creating code and IDE instances, and performing function testing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If cloud services are used independently for project development, then each service can provide its specialized function, but cross-service process coordination and information tracing require manual operations, resulting in low development efficiency

Engineering Contradiction:
Improvecross-service process coordinationVSAvoiddevelopment efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent merges multiple independent cloud services (requirement management service, code hosting service, IDE service, testing service) into an integrated development system where services communicate automatically through standardized interfaces. The requirement management service acts as a central coordinator that triggers subsequent services, eliminating manual coordination between independent services and enabling seamless cross-service workflow automation.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The requirement management service functions as an intermediary that receives requirement information, generates task instructions, and automatically transmits them to code hosting service, IDE service, and testing service. This intermediary mechanism enables automatic information tracing and process coordination across services without requiring manual user intervention at each service boundary.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of time

If manual information filling and feedback between services is required, then each service maintains its independence, but the development process becomes time-consuming and inefficient

Engineering Contradiction:
Improvetime for information coordinationVSAvoidproject development efficiency
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

The requirement management service performs preliminary actions by pre-defining task templates and instruction formats for subsequent development activities. When a requirement is submitted, the system automatically generates structured task instructions in advance, preparing all necessary information for code hosting, IDE configuration, and testing services before actual development begins, thereby eliminating time-consuming manual information gathering.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system establishes continuous automated information flow between services through the requirement management service. Once a requirement is submitted, the system continuously automates the generation, transmission, and tracing of task information across all development services without interruption, maintaining uninterrupted useful action throughout the entire development process from requirement to deployment.

Inventive Principle:
Principle #20Continuity of useful action

3Ease of operation

If users manually coordinate processes across multiple cloud services, then service independence is maintained, but user operations increase and development efficiency decreases

Engineering Contradiction:
Improveuser operations requiredVSAvoiddevelopment efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The development system implements self-service through automated service-to-service communication. The requirement management service automatically generates task instructions and triggers subsequent services without user intervention. Each service receives structured instructions and executes its function autonomously, with the system self-coordinating the entire development workflow from requirement submission through code hosting, IDE provisioning, and testing, thereby eliminating manual user operations while maintaining service independence.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20250335191A1Cloud Service-Based Project Development System and Method, and Computing Device Cluster
Publication Date: 2025.10.30 HUAWEI CLOUD COMPUTING TECHNOLOGIES CO LTD
  • US20250335191A1 patent drawing
  • US20250335191A1 patent drawing
  • US20250335191A1 patent drawing

AI summary

A requirement management node obtains requirement information of a project, sends a branch creation instruction to a code hosting node in the system based on the requirement information, and sends an instance creation instruction to an integrated development environment (IDE) management node. The code hosting node creates, in response to the branch creation instruction, a code branch corresponding to the project. The IDE management node creates, in response to the instance creation instruction, an IDE instance corresponding to the project, and obtains and runs a code file of the project from the code branch based on the IDE instance. Therefore, the requirement information of the project is used to associate each process phase in a project development process in a standard manner.