The system(adds-on) captures the employee email and inspect it if there is sensitive data. The system (adds-on) does not deal with an employee. It deals with email when it is sent. My question is: should I put employee like entity in the ER diagram?
The system(adds-on) captures the employee email and inspect it if there is sensitive data. The system (adds-on) does not deal with an employee. It deals with email when it is sent.
My question is: should I put employee like entity in the ER diagram?
ER Diagram : It is used in software engineering during the planning phase of project. It defines the different elements of the system which plays a vital role in the project. And with the relationship cardinality we defines the database scheme for the system.
For example : In the College Project where project need to maintain complete College database so here ER diagram entities will be Student, Faculty, Department, Other_Staff so this different will be considered as Object for the system and will be defined as Entity and each entity will have their Own characteristics and property, which will defined as attribute of the Entity.
Step by step
Solved in 2 steps with 1 images
