I need to draw an ER (entity relation) diagram for the following situation:
there different types of loan available to employees which they may choose to take or not. They can take only 1 type of loan, or many types of loan, or even not take any. If they take a loan, then thay will start submitting payments after some time.
so i have made the ER diagram as following
(1) student <-----> (n) loan
(1) loan <-----> (n) payment
now i argue that a relation between "student" and "payment" is not necessary because given a payment we can uniqly identify the loan, and from a unique loan we then can uniqly identify the student.
anyway, some argue that on ER diagram i have to have also "student" <---> "payment" relation because the ER diagram is a business model and should not include programming logic ..
any opinions ? should i explicitly have that "student"<--->"payment" relation or not ? wouldn't it become just unnecessary data ?
thanks
2006-11-10
20:19:46
·
5 answers
·
asked by
Zettag
2
in
Computers & Internet
➔ Programming & Design
at the begining, the loan is available to students
sorry .. wrong typing
2006-11-10
20:25:02 ·
update #1