...
Sv translation | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
A proper naming of elements in the facility library is necessary for to guarantee a user-friendly utilization of QBRX. The most important conventions that should be considered at all times are listed below.
Names are unique descriptionsA good naming immediately shows , what an element (facility type, meaning, value, etc.) is all aboutthe connotation of an element. Like this, all elements are distinguishable and usable in the best possible way. If, for example, many similar meanings are required at one facility type, they all should be given straightforward , but distinguishable names. This simplifies the assignment of data sources as well as the analysis of data.
As general as possible and as specific as necessaryA universally applicable naming makes elements fitting ensures that elements can be used for as many scopes as possible. The facility type "Room" can be used is suitable for an office and a kitchen at the same time. There is no need for a special type for any of these two. At the same time, it an element should be named as specific as necessary to allow an optimal usage. A cooling chamber, for example, requires special configurations to analyze its data in the best possible way. That's why a specific naming is necessary and also helpful to reuse it for other cooling chambersfacilities with similar requirements.
Keep it simple and technically correctNo matter if Englisch, German or another language - simple, commonly known terms should be used for the naming. Not every user is a native speaker (especially regarding the Englisch user interface) and knows all complex wordshas a wide-ranging vocabulary memorized. Exceptions to this rule are technical terms for elements that require a specific wording.
Choose consistent namesOne should abide to set conventions to ensure consistency. Consistency is the key to a problem-free workflow. Recognizable naming patterns simplify working with QBRX for all users.
Avoid abbreviationsSome abbreviations are commonly known and are understand by nearly everybody like , for example "e.g.". However, there are abbreviations that seem practical but could only cause problems due to their unfamiliarity or ambiguity. Not everybody knows the abbreviation "dp" for "data point". It could also mean"Daft Punk" or "Director of Photography". When in doubt, write it out!
|