Are there mnemonics in the database design space that you find helpful when communicating database design concerns?

A popular and useful mnemonic in the software development space is SOLID. - **S**ingle responsibility - **O**pen–closed - **L**iskov substitution - **I**nterface segregation - **D**ependency inversion Are there **mnemonics** in the database design space that you find helpful when communicating database design concerns with software developers? Normalization forms is the first to come to mind: - UNF: Unnormalized form - 1NF: First normal form - 2NF: Second normal form - 3NF: Third normal form - BCNF: Boyce–Codd normal form - Don't think I have ever made it past BCNF :-) However, the forms are often perceived as 'academic' by a development team in the public sector/banking/insurance space. Often teams will 'discover' an EAV solution - **E**ntity **A**ttribute **V**alue schema and think they have solved all peristence problems - and they code a *small* perisstence framework around their EAV "innovation". I find EAV schemas very probablematic and I am looking for something like SOLID - or anything more approachable than "Boyce Codd Third Normal Form" to help communicate concerns and ideas about what 'good' database design.