Design elements - ER diagram (Chen notation)

"Chen's notation for entity–relationship modeling uses rectangles to represent entity sets, and diamonds to represent relationships appropriate for first-class objects: they can have attributes and relationships of their own. If an entity set participates in a relationship set, they are connected with a line.
Attributes are drawn as ovals and are connected with a line to exactly one entity or relationship set.
Cardinality constraints are expressed as follows:
- a double line indicates a participation constraint, totality or surjectivity: all entities in the entity set must participate in at least one relationship in the relationship set;
- an arrow from entity set to relationship set indicates a key constraint, i.e. injectivity: each entity of the entity set can participate in at most one relationship in the relationship set;
- a thick line indicates both, i.e. bijectivity: each entity in the entity set is involved in exactly one relationship.
- an underlined name of an attribute indicates that it is a key: two different entities or relationships with this attribute always have different values for this attribute.
Attributes are often omitted as they can clutter up a diagram; other diagram techniques often list entity attributes within the rectangles drawn for entity sets." [Entity–relationship model. Wikipedia]
The vector stencils library ERD, Chen's notation contains 13 symbols for drawing entity-relatinship diagrams using the ConceptDraw PRO diagramming and vector drawing software.
The example "Design elements - ER diagram (Chen notation)" is included in the Entity-Relationship Diagram (ERD) solution from the Software Development area of ConceptDraw Solution Park.

"An ER model is an abstract way of describing a database. In the case of a relational database, which stores data in tables, some of the data in these tables point to data in other tables - for instance, your entry in the database could point to several entries for each of the phone numbers that are yours. The ER model would say that you are an entity, and each phone number is an entity, and the relationship between you and the phone numbers is 'has a phone number'. Diagrams created to design these entities and relationships are called entity–relationship diagrams or ER diagrams.
Using the three schema approach to software engineering, there are three levels of ER models that may be developed. ...
Conceptual data model ... is the highest level ER model in that it contains the least granular detail but establishes the overall scope of what is to be included within the model set.
Logical ER model ... contains more detail than the conceptual ER model. In addition to master data entities, operational and transactional data entities are now defined.
The physical ER model is normally developed to be instantiated as a database. Therefore, each physical ER model must contain enough detail to produce a database and each physical ER model is technology dependent since each database management system is somewhat different.
Physical model ... is normally forward engineered to instantiate the structural metadata into a database management system as relational database objects such as database tables, database indexes such as unique key indexes, and database constraints such as a foreign key constraint or a commonality constraint." [Entity–relationship model. Wikipedia]
This crow's foot entity-relationship diagram (ERD) example "Educational data base" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Entity-Relationship Diagram (ERD) solution from the Software Development area of ConceptDraw Solution Park.