CodeArts Req Best Practices

Managing Raw Requirements of an IPD-System Device Project (Smart Watch R&D)

A hallmark of a successful product lies in its ability to meet customer requirements. Unlike traditional requirement management tools that only play a role in the R&D phase, CodeArts Req covers both customer and market requirements by providing a complete process from customer requirement collection, high-value requirement decision-making, to delivery and acceptance. It makes real-time requirement progress transparent and improves market requirement flow by 70%.

In CodeArts Req's raw requirement (RR) management, you can submit customer requirements to the target organization. This organization can then make decisions, conduct analysis, and manage delivery and acceptance of these requirements in real time. This process accelerates the delivery of customer requirements and enhances the market competitiveness of your products.

Managing Defects of an IPD-System Device Project (Smart Watch R&D)

Defect management is a critical part in product lifecycle management. Both hardware and software development will encounter countless defects. Poor defect management will affect the product quality. Based on years of experience in quality and operation management, Huawei has developed a set of effective defect best practices. It provides a unified, efficient, and visualized defect tracking platform to ensure that each defect can be closed with high quality and efficiency.

A company plans to launch a smart watch. However, the R&D will take a long period, and requires collaboration of multiple departments and teams. How can the company transfer defects among organizations and ensure that the defects can be finally closed? Now, let's look at some defect lifecycle management practices.

Baseline Management for an IPD-System Device Project (Smart Watch R&D)

A product goes through a complex R&D process from planning to release. CodeArts Req helps to manage these processes by requirement baselines, change requests of controlled fields, change reviews, and change management. Baseline changes must reach specified gate thresholds before going to the next stage to keep teams on the right track.

A company plans to launch a smart watch, which requires collaboration across departments and teams. R&D requirements have been assigned to each production and research team after rounds of communication and clarification on requirements. To ensure that products are delivered on time and with high quality, all R&D and production teams need to devotedly carry out tasks based on specified requirements. Therefore, baseline control for requirements is necessary and baselined requirements cannot be modified randomly. The following uses this company as an example to describe how to implement requirement baseline control.

Feature Tree Management for an IPD-System Device Project (Smart Watch R&D)

System features (SFs) are the core assets of a product and are always iterating. Full management provided by CodeArts Req includes a feature tree to better manage SFs, prevent asset loss, and enable fast cross-generation feature inheritance and development.

Using an IPD-System Device Project to Review Changes to a Smart Watch R&D Project

Bringing a product from planning to market involves a complex development cycle. CodeArts Req provides baseline control and change management for work items, streamlining the entire process from change request and review to implementation. It enforces strict change controls, maintains baseline integrity, and enables full auditability of approvals, decisions, and accountability.

Best Practices of CodeArts Req Permission Management

CodeArts Req provides role-based access control (RBAC) and attribute-based access control (ABAC). This document describes how to configure permissions based on roles and how to implement refined permission control in a custom workflow for an IPD-system device project.