Entity-relationship Model and Database Naming Conventions

Database naming Conventions are standards when naming database components. I find Pascal Case notation naming convention to be one of the less rigorous ones. Pascal is straight forward, with a few rules which make it easy for development and understanding. There are several rules to Pascal notation however; the rules are simple and straight forward. The guidelines go as follow; limiting the characters in name, restricting underscores, numbers, the use of a letter as first character of the name, limit the use of acronyms, simple names that can be understood, and avoid using spaces even if the system permits its. Pascal by far is the most sensible of the naming conventions because it’s clear concise and easy to read.
Entity Relation Diagram structures and notations are different at least five features. Some allow attributes in a relationship, how they represent cardinality and participation constraints, the place where they specify constraints, or they portray overlapping and split subclass entity-types, or they show total or partial narrowing down, and whether they model the foreign key at the ERD level.
Bachman Notation also known as data structure diagram is used to design the data with a network or relational logical model. It divides the data from model. This is how the data is stored in the system.
Barker's Notation signifies the properties of relationships including cardinality and optionality, exclusion, recursion and the use of abstraction.
EXPRESS is a data modeling language, the EXPRESS Language Reference Manual. Data models strictly define data objects and relationships amongst data objects for the domain of interest.
Data modeling language for the development of semantic data models is the structure and semantics of material within an environment or system is characterized by a graphical information model.
Unified Modeling Language A type of static structure diagram that describes the structure of a system by showing the system's classes,