Overview

Defect Management lets you create and manage defects reported against Products.

The Defect Management User's Guide is intended for users who need to become quickly familiar with the application. Defect Management requires ENOVIA Product Line Management to also be installed.

About ENOVIA Defect Management

A Defect defines what the problem is and provides a detailed description of the steps required to reproduce the defect. It also defines the severity and priority of the defect. It also defines how the problem was found (which version or release of a product) and the environment where the problem occurred (client and server operating systems, browser database, and so on).

To resolve a defect, any number of Defect Actions are created. Defect Actions could possibly include documentation, software development, and quality assurance. Each Defect Action can have a different action assignee. A Defect cannot be completed until all of the Defect Actions are completed.

Implementation Reviews can be used to describe the changes required by a Defect Action.

About Change Boards

A Change Board consists of the people responsible for reviewing Defects and either assigning them to be fixed, or rejecting them (and providing a reason). The Change Board is comprised of people who have Lead Roles within the Organization defined with Design Responsibility for a Product.

A Product can have an Organization (which can be a Company, Plant, Business Unit, or Department) defined for its Design Responsibility attribute. That Organization is called the Change Organization for that Product. That Organization also has People with roles) such as Development Manager or Quality Engineer) defined for it. If a Person is defined as having a Lead Role for any of the roles listed below, they are automatically defined as members of the Change Board for Defects submitted against the Product.

Defect Management uses these roles to define the Change Board:


  • Customer Support Manager
  • Customer Support Engineer
  • Development Manager
  • Development Engineer
  • Quality Manager
  • Quality Engineer
  • Product Manager

When a Defect is created, the creator selects a Product for the Reported Against Product field. Defect Management automatically enters the name of the organization with Design Responsibility for that product in the Change Responsibility field. If no Organization is defined with Design Responsibility, then Defect Management uses the Change Board for the Model to which the Product belongs. If no Organization is defined with Design Responsibility for the Model, then the person creating the Defect must select an Organization for the Change Responsibility field. That Organization becomes the Change Board for this Defect (but not for the Product against which the Defect is reported).

Members of the Change Board use the Defect Assessment Dashboard to triage (evaluate severity/priority, reject, return for more details, or assign to be fixed) the defects. See Managing Defects.

Once a Defect is created, the Change Board members do not change if the Change Responsibility or lead responsibilities are changed.

About the Defect Team

The Defect Team can view, edit, and be assigned tasks for a Defect or Defect Action and is comprised of the people in the Change Board for the Product plus those with the specific roles listed below.

People with these roles can be assigned as an Action Assignee for a Defect or Defect Action:


  • Development Manager
  • Development Engineer
  • Supplier Development Engineer

People with these roles can be assigned as a Quality Assignee for a Defect or Defect Action:


  • Quality Manager
  • Quality Engineer
  • Supplier Quality Engineer

Where only those people with Lead Roles are part of the Change Board, anyone with any of these roles in the Change Responsibility organization are part of the Defect Team.

About Roles

Defect Management defines specific roles that can be assigned to users.

This table lists how to use the product depending on your role:

Role Description
Customer Support Engineer Handles incoming Issues and interfaces with customers.
Customer Support Manager Customer Support team lead who manages a team of Customer Support Engineers (and possibly Customer Support Suppliers).
Supplier Customer Support Engineer Customer Support Engineers working for a Supplier to the host company. Interfaces with customers much like the Customer Support Engineer role.
Development Engineer Responsible for fixing Defect Actions. Only persons with the Development Engineer role can be assigned Defect Actions.
Development Manager Development team lead who manages a team of Development Engineers (and possibly Development Supplier Engineers). The Development Manager also delegates the responsibility of fixing Defect Actions to members of his team.
Supplier Development Engineer Development Engineers working for a Supplier to the host company. Performs similar duties as the Development Engineers of the host company, but can only access those Defects to which they are specifically assigned to as the Responsible Development Engineer.
Quality Engineer Responsible for verifying Defect fixes.
Quality Manager Quality team lead who manages a team of Quality Engineers (and possibly Supplier Quality Engineers). The Quality Manager also delegates the responsibility of verifying Defects to members of his team.
Supplier Quality Engineer Quality Engineers working for a Supplier to the host company. Performs similar duties as the Quality Engineers of the host company, but can only access Defects to which they are specifically assigned to as the Responsible Quality Engineer.
Release Engineer Generates individual product builds. Relates Defects in the Test or Closed state to an appropriate Build object.
Product Manager Manages all phases of a Product.

Before Reading this Guide

All ENOVIA products install common components that are shared, providing consistency of features across all applications. Common features allow ENOVIA products to manage information such as user and company profiles, documents, and routes, based on company roles rather than on the application used. See the Common Components User's Guide for details.

Other common features are provided by ENOVIA Business Process Services . These include IconMail, generic searching, collections, and preferences, and are described in the Application Exchange Framework User's Guide. This guide also describes how to use the ENOVIA user interface.

Common feature behaviors that are unique to Defect Management are described in this user guide.

Getting the Most Out of this Guide

The Defect Management User's Guide is organized to help you use Defect Management to perform tasks appropriate to your designated role.

Here are some suggestions for using this guide:


  • Working with Defects. This section describes Defects, and the tasks you can perform on them.
  • Working with Defect Actions. This section describes Defect Actions, and the tasks you can perform on them.
  • Searching. This section describes how to find items you need to work with.
  • Working with Implementation Reviews. This section describes how to work with Implementation Reviews for a Defect Action.
  • Techniques. This section describes the business process flow for working with a Defect or Defect Action.
  • Interface Description. This section describes the menus, toolbars, windows and Categories menus used within Defect Management.