- What's New
- Function Overview
-
Service Overview
- What Is CodeArts Req?
- Advantages
- Use Cases
-
Features
- Multiple Built-in IPD Requirement Models
- E2E Traceability
- Baseline Management and Change Review
- Efficient Cross-Project Requirement Collaboration
- System Feature Management
- Customers' Raw Requirements Management
- Bug Full Lifecycle Management
- Efficient Cross-Organization Collaboration for Bug Tracking and Management
- Bug Trend Analysis and Quality Measurement
- Traceable Fixing Process
- Customizable Fixing Process
- Security
- Permission Management
- Constraints
- Getting Started
-
User Guide
- CodeArts Req Usage Process
- Purchasing and Authorizing CodeArts Req
- Accessing the CodeArts Req Homepage
- Creating a CodeArts Project
- Managing Scrum Project Requirements
-
Managing IPD-System Device Project Requirements
- Requirement Management Process
-
Configuring Common Settings
- Configuring Common Work Item Fields
- Configuring Common Work Item Statuses
- Configuring Work Item Templates
- Configuring Work Item Status Flows
- Configuring Work Item Tags
- Creating Work Item Modules
- Creating Work Types
- Configuring Work Item Status Roll-up Rules
- Configuring Notification Rules
- Viewing Work Item Import/Export Records
- Creating and Managing RRs
- Creating and Managing a Feature Tree and System Features
- Configuring Project Plans
- Creating and Managing R&D Requirements
- Creating and Managing Tasks
- Creating and Managing Bugs
- Reviewing Work Items
- Tracking the Project Progress
-
Managing IPD-Standalone Software Project Requirements
- Requirement Management Process
-
Common Configuration Management
- Configuring Common Work Item Fields
- Configuring Common Work Item Statuses
- Configuring Work Item Templates
- Configuring Work Item Status Flows
- Configuring Work Item Tags
- Creating Work Item Modules
- Creating Work Types
- Configuring Automatic Roll-up Rules
- Configuring Notifications
- Viewing Work Item Import/Export Records
- Creating and Managing RRs
- Creating and Managing a Feature Tree and System Features
- Configuring a Plan
- Creating and Managing R&D Requirements
- Creating and Managing Tasks
- Creating and Managing Bugs
- Reviewing Work Items
- Tracking the Project Progress
- (Optional) Checking Audit Logs
-
Best Practices
- CodeArts Req Best Practices
- Best Practices of Scrum Projects
- Using IPD-System Device Projects to Manage RRs of a Smart Watch R&D Project
- Using IPD-System Device Projects to Manage Defects of a Smart Watch R&D Project
- Using IPD-System Device Projects to Perform a Baseline Review (BR) on a Smart Watch R&D Project
- Using IPD-System Device Projects to Manage Feature Trees of a Smart Watch R&D Project
- Huawei E2E DevOps Practice: Managing Requirements
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
APIs
-
Work Items of the Scrum Project
- Creating a Customized Field for a Work Item Type
- Uploading an image
- Obtaining Work Item Completion Rate
- Obtaining Comments on a Specified Work Item
- Querying Labor Hours by User (Single Project)
- Querying Labor Hours by User (Multi-Project)
- Obtaining the Work Item History
- Create work items.
- Querying Work Items of a Project
- Advanced Query Work Item
- Deleting Work Items in Batches
- Querying Work Item Details
- Updating a Work Item
- Deleting a Work Item
- Obtains sub-work items.
- Querying Historical Records of All Work Items in a Project
- Querying the Work Item Transfer Configuration of a Scrum Project
- Creating a Work Item as a Fine-grained Permission User
- Queries the work items associated with the current work item.
- Queries the associated Wikis associated with the current work item.
- Queries the code submission records or branch creation records associated with the current work item.
- Querying Associated Wikis
- Querying Customized Fields of Scrum Work Items
- Downloading an Image
- Uploading an Attachment to a Work Item
- Iteration of the Scrum Project
- User Information
- Project members
- Project Information
- Project Indicators
- Project Statistics
- Modules of the Scrum Project
- Domain of the Scrum Project
- Scrum Project Statuses
-
Work Items of the Scrum Project
- Application Examples
- Appendixes
- Change History
-
FAQs
-
Work Items
- How Can I Assign One Scrum Project Work Item to Multiple Members?
- Why Is a Message Reporting Duplicate File Name Displayed During File Association in a Scrum Project?
- How Do I Handle the Verification Exceptions in the Number of Work Items Imported to an IPD Project?
- How Do I Modify the Recipient After an IPD Project Requirement Is Assigned?
- Member Management
-
Troubleshooting
- Why Is the Message "You have been invited to run projects with another account. Accept invitation" Displayed When Inviting Other Users to Join My Project in CodeArts Req?
- Why Can't I Create a Project Using "DevOps Full-Process"?
- Why Is a Message Indicating the Field Name Already Exists Displayed When Setting a Work Item Field in a Scrum Project?
-
Work Items
- Videos
- General Reference
Copied.
What Is CodeArts Req?
Product Overview
CodeArts Req is a requirement management and team collaboration service. Built on Huawei's years of practical R&D, it has multiple out-of-the-box requirement models and object types (requirements, bugs, and tasks) for any scenario. It supports multiple R&D modes such as IPD and DevOps. Functions include cross-project collaboration, baseline and change management, and custom reports.
- Req seamlessly integrates with other CodeArts services to provide full lifecycle software management and team collaboration.
- CodeArts Req presets multiple templates for Scrum, IPD-system device, IPD-standalone software projects.
- Scrum projects are a fit for agile software development teams who uphold Scrum methodologies and practices.
- IPD-system device projects manage large-scale product development with high-quality and efficiency based on structured processes and powerful cross-project collaboration.
- IPD-standalone software projects manage large-scale software development with high quality and efficiency based on structured processes and powerful cross-project collaboration.
- Efficient, transparent, and visualized end-to-end project management is made possible due to the multiple basic features provided. These features include requirement planning and management, bug management, sprint planning and management, custom workflows, progress tracking, statistical reports, and project document hosting.
NOTE:
IPD project templates are available only in the AP-Singapore region.
Features
- Requirement Planning and Breakdown
Raw requirements are usually abstract and vague. They need to be analyzed and broken down into minimum-level units that can be delivered in each sprint.
In Scrum projects of CodeArts Req, requirements can be broken down in the four-layer hierarchy: Epic > Feature > Story > Task.
An abstract and vague epic is divided into multiple features which are further broken down into stories. A story, also called user story, is a minimum deliverable unit that is written from the customers' perspective and complies with the INVEST principle, which means that a story should be independent, negotiable, valuable, estimable, small, and testable. After the breakdown, stories are scheduled into one or more sprints based on the manpower of the development team and the estimated finished time of the epic requirement.
This method leads to continuous delivery and ensures runnable software is produced in every sprint and offered to users for testing. The development team can then collect user feedback, apply changes accordingly in the next sprint, and finally deliver a product that meets the requirements of users and promise business success.
Requirements can be planned and broken down using a mind map in CodeArts Req.
- Sprint
A sprint-based agile software development process is composed of several repetitive cycles. It features continuous delivery and feedback collection, against the linear process of waterfall software development, where a product is delivered only at the end of the process.
A product is released after each sprint. The feedback collected in a sprint will be used as references in the next sprint for the development team to continuously improve the software. Adopting the sprint model reduces risks and change costs and improves development efficiency.
You can plan and manage sprints in CodeArts Req.
NOTE:
Although both "iteration" and "sprint" refer to a repetitive process, there are some slight differences between them. "Iteration" is a common term used in different agile methodologies, whereas "sprint" is a Scrum term.
- Custom Statistics Report
Data statistics and analysis are the basis for transparent and visualized software project management. However, time-consuming manual data collection and analysis are a real pain to many project managers.
CodeArts Req supports online data collection and analysis. You can use preset reports or create custom reports as required.
- Document Hosting
Document hosting supports uploading documents in different formats. You can upload project summaries, architecture documents, and product requirement documents to the cloud, so that project members can access and obtain documents via a unified access address at any time. This facilitates information sharing throughout the team and the building of project experience.
Scrum Development Process
- Scrum is a popular agile development method. It enables continuous delivery through repetitive sprints, which are cycles of closed-loop software development from user requirement planning to user feedback collection.
- Sprint planning meetings, daily Scrum meetings, sprint retrospective meetings, and sprint review meetings are keys to simple but efficient project management.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot