Rules and Standards

CAA V5 Naming Rules

Standard names for CAA V5 brands, solutions, applications, products, and configurations
Technical Article

Abstract

As CAA V5 introduces a number of different programming entities, naming rules and conventions have been developed in order to avoid name collisions inside and outside the CAA environment, and to make things clearer for its developers. This article describes the basics of these naming rules.

Why Naming Rules?

These naming rules apply to both the Dassault Systèmes group, to the CAA Partners and Members, and to CAA customers that keep their in-house developments. They are aimed at avoiding naming conflicts between the entities that can be found together in the same repository at run time [1] [2]. They are also intended to make any CAA application or solution belongs to the CAA application or solution family.

The CAA naming conventions are based on a brand name, usually a trigram. This brand name is used to start the name of every entity in products or solutions for this brand. The Dassault Systèmes brand names are:

Brand Trigrams Brand Names
CAT CATIA
ENOV ENOVIA
VPM ENOVIA
DNB DELMIA

[Top]

Naming Rules for CAA V5 Applications

For Products [Partner BRAND] V5 - [Product Name] <1,2,3>

Partner Name : DCS, MDI, CSC, ...

Rational:

  1. [Partner BRAND] will avoid naming conflicts between partners
  2. V5 is the foundation of CAA and is used as a label
  3. No direct mention of Dassault Systèmes hosting Brand (CATIA/DELMIA/ENOVIA): can be done through partner portfolio structuration
  4. No need for PRODUCT specification (implicit)

Here are two examples of product names from CSC:

[Top]

Naming Rules for CAA V5 Solutions

For Products [Partner BRAND] V5 - [Product Name]
For Configurations [Partner BRAND] V5 - [Product Name] CONFIGURATION

Rational:

[Top]

References

[1] CAA V5 C++ Naming Rules
[2] CAA V5 Java Naming Rules

[Top]

History

Version: 1.0 [Sep 2000] Document created
[Top]

Copyright © 2000, Dassault Systèmes. All rights reserved.