It is important for a project to establish a common understanding the terms of its core domain. It may also be helpful to compile definitions, designations, and rough sketches for terms of secondary domains. This provides the basis for preventing misunderstanding or misuse of terms in the documentation, code or communication. Teams must not be scared to describe terms. In project it is usually not necessary and often impracticable to define with water-proofed clarity. Keep in mind that the goal is a common understanding which typically evolves during the course of the project. This is especially true for glossaries that are used within the project by the team and associated experts. It may call for a different approach if the glossary is publicly available. | 
