Overview
Dependency Diagram visually represents all predecessor and successor artifacts within the system. It allows you to view and establish dependencies between artifacts, specifically, to designate which artifacts precede and succeed an artifact.
Version Information: The Dependency Diagram module described in this article is available starting from TopTeam version 21.50.
In this article, you’ll learn these topics:
- Opening Dependency Diagram
- Changing the Query Scope for the Dependency Diagram
- Adding and Removing Dependencies
- Viewing, Adding and Deleting Dependencies via Non-Trace Link Widget
Who should read this?
- TopTeam Administrators
- TopTeam Users
Prerequisites
‘Predecessor/Successor’ linking rules are defined for required record types. To learn more about defining linking rules, see Configuring Traceability Schema/Rules for Record Types.
Opening Dependency Diagram
Changing the Query Scope for the Dependency Diagram
A scope is required to generate a Dependency Diagram that determines the query’s initial location, i.e., you can select the artifacts for which the diagram will be displayed. The scope could be any of these: project, package, group, or artifact.
Adding and Removing Dependencies
Viewing, Adding and Deleting Dependencies via Non-Trace Links Widget
The Non-Trace Links Widget in an artifact detail editor provides another interface for managing dependencies. Here, you can view existing dependencies as well as add or delete dependencies.
Revised: February 15th, 2024