Hello Friends,
I am trying to gather information on what sort of rules can be made for various VC component nomenclature.
We have so many objects setup for VC,
Classes
Characteristic
Characteristic Value
Configuration Profile’s
Dependencies
So what do you suggest, do all this objects needs some rules to maintain nomenclature or not?
Let’s take example of product as CAR.
Broadly there are 3 types based upon pricing range.
Economy, Middle segment & Luxury
3 KMAT’s, ECO_CAR, MID_CAR, LUX_CAR
Consider CAR’s have just 4 assemblies, COLOUR, ENGINE, TRANSMISSION, TYRES
So should I go ahead and create this 4 Characteristic presenting these assemblies or each assembly of specific model needs a new Characteristic.
ENGINE
ENGINE_ECO
ENGINE_MID
ENGINE_LUX
How many classes do I need?
Just one per model to hold all characteristic for that Model or more?
Classes
CL_ECO
CL_MID
CL_LUX
I am starting this discussion and I am sure as each organizatipn has its own nomenclature for various objects, but there could be best practices in naming these objects.
Implementing a naming convention greatly helps. looking forward more additions in product attributes and introduction of new products.
So please reply with your thoughts.
Thanks
Ritesh
