Basic Concepts

Project

A project consists of a series of coordinated and controlled activities in a certain process. The objective of a project is to meet specific requirements and is restricted by time and resources. CodeArts Req manages the project process and results to achieve the objective.

Scrum

Scrum is iterative and incremental, and often used for agile software development. Scrum is a process framework that includes a series of practices and predefined roles.

A Scrum project team includes three roles: Product Owner, Development Team, and Scrum Master. They are responsible for advancing the project progress and delivering the project. The product owner represents the interest owner, and the development team includes all developers.

Scrum helps manage software development projects and maintenance teams. It can also be used as the plan management technique: Scrum of Scrums.

Backlog

Backlogs can be regarded as different to-be-developed work item pools in different software development scenarios. For example, a product backlog indicates a work item pool that contains products to be developed and a sprint backlog indicates a to-do work item pool that contains sprints to be developed.

• Product backlog: High-priority requirements based on user value.
• Sprint backlog: List of tasks to be completed in the sprint.

Release

In IPD-system device and IPD-standalone software projects, a release specifically refers to a release plan. This is a logical version concept that includes multiple IRs to be delivered. Child requirements under an IR in a release can be released in batches through different iteration plans.

Iteration

Iteration is an incremental and iterative development process. It steps up R&D productivity and product success rate by compensating deficiencies of traditional waterfall development.

Feature Tree

Feature tree is a summary of all features of a product. It focuses on product value and connects customer markets and R&D. The feature tree consists of feature sets (collections of system feature capabilities) and individual system features.

System Feature (SF)

SFs describe the main selling points and highlights of a product. It keeps iterating as the product evolves.

• IPD system device projects: SFs can have different types of sub-requirements in this hierarchy: SF > IR > SR > AR.
• IPD standalone software projects: SFs can have different types of sub-requirements in this hierarchy: SF > IR > US.

Epic

During agile development, epic is a work item type, which is usually used to define a series of macro scenarios or plans. In addition, the development workload is heavy, and epic needs to be broken down into fine-grained work items to arrange iterative development and delivery.

Feature (FE)

FEs, available only in IPD-self-operated software/cloud service and Scrum projects, describe product functions that deliver value to customers. FEs are derived from epics and broken into stories. An FE typically spans several weeks and requires multiple iterations for delivery.

User Story (US)

A user story is a work item type, an explanation of functionalities written from a user's perspective. A good user story includes:

• Role: Who will use this function.
• Activity: What functions need to be implemented.
• Value: Why the functions are required. What value the user hopes to obtain. A user story is usually recommended to be delivered within a single iteration. User stories are sometimes referred to as stories.

Raw Requirement (RR)

RRs are raw problems or requirements described from the perspective of internal and external customers. Customer requirements are a type of RRs. This type of requirement needs to be analyzed and reviewed by the RMT/RAT.

Initial Requirement (IR)

IRs are re-described accurately, with complete background, in standard format, and from the perspective of customers/markets. IRs can be generated in either of the following ways:

• RRs after analysis and decision-making by the RMT/RAT
• Product planning (including system feature breakdown)

During the incremental version development, system features have become stable, and therefore IRs are used to carry incremental requirements of the version.

System Requirement (SR)

SRs are functional and non-functional requirements that are presented externally, can be tested, and are described from the perspective of R&D. Functional requirements are scenario-specific requirements for functions provided by the system. Non-functional requirements include requirements for system costs, global quality attributes (mainly DFX), and technical restrictions.

Assigned Requirement (AR)

ARs are functional or non-functional requirements broken down to sub-systems/modules by SRs from the perspective of deliverability based on the division of responsibilities of entry-level organizations.

Bug

In project management, particularly in agile development and software project management, a bug is an error, fault, or issue in a product or system that causes it to malfunction or produce unexpected results.

Task

A task is an activity undertaken to achieve a specific goal. It is typically process-oriented and represents the minimum work unit in R&D and production.