Glossary

Category

A category is way to classify a requirement. You define requirement categories for your organization specific to your enterprise needs. Examples of categories include: Market Requirements, Technical Requirements, Functional Requirements and Nonfunctional Requirements.

Competitor

When you create a product, you can indicate that the product is a competitor product. You can store the same detailed information for a competitor product as for a product you are developing. You can use the competing product as a source of requirements.

Epic

An epic acts as a parent container for multiple child user stories that span multiple releases and sprints in a product. You can link epics to requirements to provide traceability and to help with the planning process.

Feature

A feature is part of a product. A feature can be independent and standalone, or it can work with other parts of a product.

Persona

A persona can be a person or a composite of many people. The description of a user, customer, buyer, or other individual who can cause you to create a requirement. You can link requirements to personas and sources to provide traceability and to help with the planning process.

Product

Something of value produced by your company for sale or internal company use. A product can be merchandise or wares, software, a building project, or any other consumable. Products also represent services, applications, or systems in an IT environment.

Product Owner

The scrum team member listed as the product owner in the properties of a product.

The product owner has privileges over all objects that are associated with the product, such a requirements, releases, sprints, and backlog items. The product owner does not need to be a scrum team member to work with user stories associated with the product.

Release

A release is similar to a project, an effort that ends with the delivery of value. The release usually entails a number of features and requirements.

Requirement

A requirement is a documented specification that describes what a particular product or service can be or do. A statement that defines a necessary attribute, capability, characteristic, or quality of a product or service so that it provides value to a user.

Source

A source can be a company or organization. You can collect information about sources and include contact information and other market information. A source can be linked to a requirement to provide traceability and context.

Traceability

The ability to trace a requirement from its origin to the lowest levels of implementation, typically a test case, or work item.

User Story

A user story is a way to define requirements in CA Agile Vision. If these products are used together, a requirement in CA Product Vision can be linked to its associated user story in CA Agile Vision.