Keep all the stakeholders in synch with real-time data<\/li>\n<\/ul>\nIn this writing, we will discuss the unique features of Kovair in allowing users to define relationships between artifacts as per their specific needs.<\/p>\n
Defining Relationships<\/h2>\n
Traceability capabilities are available in almost all ALM-based tools, but it is very important to select the right one. Frequently the \u2018out of the box\u2019 defined relationships do not cater to all business needs of the organization. Worse yet, many provide limited options for configuration. To respond to this shortfall, the Kovair platform provides the unique capability to define relationships between any artifacts along with sophisticated features such as user-defined relation types, impacts, and relationship attributes. In Kovair, users can define relationships between different artifacts by simple mouse click configuration with no coding required and no configuration files to edit.<\/p>\n
Select Artifacts<\/h2>\n
The ability to define relationships is available in any entity or artifact type in Kovair, including any custom entity you have created. Simply create a relation field, give it a name, and select the artifact with which the relationship needs to be established. In the screenshot below are some of the options available when creating a relationship.<\/p>\n
![\"define](\"https:\/\/www.kovair.com\/blog\/wp-content\/uploads\/sites\/2\/2014\/02\/define-relationships-.jpg\")
<\/p>\n
Define Cardinality<\/h2>\n
User can specify the cardinality that will be permitted when establishing relationships between artifacts. Kovair supports all possible cardinalities:<\/p>\n
\n- One to One: One Business Requirement can relate to One Use Case<\/li>\n
- One to Many: One Business Requirement can relate to multiple Use Cases<\/li>\n
- Many to One: Multiple Business Requirements can relate to one Use Case<\/li>\n
- Many to Many: Multiple Business Requirements can relate to multiple Use Cases<\/li>\n<\/ul>\n
These can be set to ensure the relationships make logical sense and disallow a relation that should not be permitted.<\/p>\n
Defining Impact Scenario<\/h2>\n
Kovair allows users to specify not only in which direction (parent, child, bidirectional) the impacts are raised, but also provides fine-grained controls over what particular changes will create an impact. In addition, notifications may be sent to relevant users.<\/p>\n
![\"Defining](\"https:\/\/www.kovair.com\/blog\/wp-content\/uploads\/sites\/2\/2014\/02\/Defining-Impact-Scenario.jpg\")
<\/p>\n
Allow linking of same items multiple times<\/h2>\n
In certain scenarios, same set of records may need to be related multiple times with each other. Kovair supports this scenario with the option of \u201cAllow Multiple Links\u201d.<\/p>\n
Relational Attributes<\/h2>\n
In certain cases, there are attributes that are specific to the relationship between two artifacts e.g. when a Test Case gets executed then a Test Run record is created. The status of the test steps related to that run is neither associated to test step nor associated to test run. It is an attribute of the relationship between Test Run and Test Step. To cater to this situation Kovair allows users to define attributes specific to the relationship through this option.<\/p>\n
![\"Relational](\"https:\/\/www.kovair.com\/blog\/wp-content\/uploads\/sites\/2\/2014\/02\/Relational-Attributes.jpg\")
\n<\/span><\/b><\/p>\nVisibility from Other Entities<\/span><\/p>\nKovair allows users to control the exposure of a related field. Through the option of \u201cVisible from <<Other Entity>>\u201d users can specify whether the relationship field should be visible from both entities involved in the relationship or not.<\/p>\n
Snapshot Fields<\/h2>\n
Values of the attributes of a record keep changing over a period of time. It is very important, especially in the context of relationships to capture or maintain a snapshot of the values of certain attributes of the artifacts involved in a relationship. Kovair allows users to do this by selecting snapshot fields during the relationship definition.<\/p>\n
![\"Snapshot](\"https:\/\/www.kovair.com\/blog\/wp-content\/uploads\/sites\/2\/2014\/02\/Snapshot-Fields.jpg\")
<\/span><\/p>\nThus Kovair enables users to build traceability relationships between artifacts from scratch as per their specific needs and that too without writing any code. Organizations using different methodologies such as Waterfall, Agile can use Kovair to customize traceability relationships<\/a> as per their project needs and gain in both productivity and product quality.<\/p>\n
![\"Traceability](\"https:\/\/www.kovair.com\/blog\/wp-content\/uploads\/sites\/2\/2014\/02\/blog-graphics-90.jpg\")
![\"Agentic](\"https:\/\/www.kovair.com\/blogs\/wp-content\/uploads\/sites\/2\/2026\/04\/blog-graphics-1120-800x500.jpg\")
\r\n\r\n <\/a>\r\n <\/div>\r\n\r\n ![\"App](\"https:\/\/www.kovair.com\/blogs\/wp-content\/uploads\/sites\/2\/2026\/04\/blog-graphics-1119-800x500.jpg\")
\r\n\r\n <\/a>\r\n <\/div>\r\n\r\n ![\"Generative](\"https:\/\/www.kovair.com\/blogs\/wp-content\/uploads\/sites\/2\/2026\/03\/blog-graphics-1118-800x500.jpg\")
\r\n\r\n <\/a>\r\n <\/div>\r\n\r\n