In objected-oriented design, "smells" are symptoms of code violating design principles. When a deadline is looming, decisions can affect the long-term quality of a code or CAD. Given this and the similarities between object-oriented code and CAD models, this paper introduces a set of CAD smells. These smells are derived from a top-down review of potential CAD smells mapped against the reported code smells that violate abstraction, modularity, encapsulation, and hierarchy principles. This list was further reviewed considering CAD systems and specific examples (some illustrated in the paper).
