Information Lost Redundancy Questions

There is no redundancy, in
fact we are losing lot of data More than one Cusomter Own Techncn prfrm the
like dates for job. technician perform More than One Who must pay pay Repair for specific same repair at diff When the job
on a specific job? Car for the Car? Job time on a diff car was done
Technician ID is
not present to link
with the jobs. It is There is no
not possible to Customer technician ID in
identify who must information will be repair and the
pay for the par Bridging is absent, Customer id is lost as it not tables cannot be
because repair hence same unique which bridged to a job; so bridged. One
cannot be bridged There is no redundancy in technician cannot means customers we cannot see technician cannot
to the customer fact lots of bridging is perform on cannot own more which job is for perform more than
missing. different job. than one car so which customer. one job.
a that is a problem.

Customer
information will be
lost, we have no
tables at all.
Moreover we
cannot find out
who should be for
the job because
we lost information
for the customer.
Moreover we
cannot identify
which job was
There is no redundancy, in done for which
Date is also fact a lot of information is customer to bill the
missing. lost customer.
b
 Although we can
identify which Customer ID is
technician missing / wrongly
performed the job. used (at one place
The naming is it is customerid
confusing, job and and at other
job_refair is a bad custid), so we furthermore there
naming Things are bridged cannot map the job could two job ids
convention. In Fact Job and Repair are the in the job&repair a customer. If we for the same
we could same thing and hence hence there can assume the names customer and
condense job, redundant. This seems to be be more than A customer having would be same same for the Yes you can
repairds, be on the better design but customer and different car will then we are not technician. So both identify when
job&repair into two has one redundancy which more than one have different job missing customer this features the job was
tables. is job&repair. technician due to jobs table. information. provides greater done.
c flexibility of data.

Wherever car is
hardcoded with the
customer we
cannot have more
than one cars
hence it is a
problem in d, the
design in c is much
better where car is
in the jobs so there
There is no redundancy, in could be more
Technician details fact we are losing lot of data than one jobs for a Customer is not Date is also
will be lost like dates for job. car. linked to a job. missing for a job.
d

Mapping between
Technician data is Task and Job has customer job and
missing. redundant information technician missing.
e
 Information of car
is also missing, we
have never used
the carVIN; which
Job should be means we cannot
central theme Job id is not used have the car
which should link anywhere. bridged. Customer
repair, customer Technician_reapir and ID is missing,
and technician. But repair are redundant, also hence we cannot
neither job, nor the job. Technical_repair is bridge details of
repair addresses a redundant design. customer to a job.
this problem.
f