choose any organization—a bank, a hospital, a store, or a coffee bar, for exampl

Question

choose any organization—a bank, a hospital, a store, or a coffee bar, for example—and describe how to uniquely define the customer. Assume that this is a relational model and that you are not creating a single numeric or alphanumeric unique identifier for the customer, such as a customer number.

With these thoughts in mind, analyze ways to ensure uniqueness and the existence of data. Consider the attributes you will store, and discuss each of the following:

*What happens if one of the fields is unknown?
*Are all the required fields always recorded for a customer?
*How can you prevent duplicate records?
*Are “William Jones,” “Bill Jones,” and “W. J. Jones” the same customer? If they are, how could you connect them?
*Do any of the defined attributes have more than one value?
*How can you ensure that all types of customers fit your definition?

Discuss whether there really is a unique definition for a customer and whether your definition works equally well for all businesses. With some reference

Explanation / Answer

if you can take a example of hospital then Pateint will be customer

  
PATIENT.
PATNAME required primary
PATADDRESS required  
PAT-PHONE   required primary

MEDICALREPORTS

PatBirthdate required
DATEADMIT required
PREVIOUSRECORD
PREVIOUSHOSPITAL   
PREVIOUSDATE  
PREVIOUSREASONFORADMIT   

REASONFORADMIT required

1)What happens if one of the fields is unknown?

if one of the field is unknown then there will be insert anomaly if the primary key is not avivlable

it will throw exception dml cause unknown or null not allowed in the primary field

2) are alll the required field always recorded for customer

yes all required field always recorded for customer as patient name . address phonenumber admit date and reasonfor admit is required to process any patient record and further assistance

3) to prevent duplicate record by providing the primary key and candidate keys like patientname,patientphone number can be unique

4)   *Are “William Jones,” “Bill Jones,” and “W. J. Jones” the same customer? If they are, how could you connect them?

5) the below attribute are multivalued attribute

PREVIOUSRECORD
PREVIOUSHOSPITAL   
MEDICALREPORTS
PREVIOUSREASONFORADMIT   

as a Patient can have many previous medcal history he might have visited many hospital before and he might be admited for diffrent reason he admitted yesterdat

5) yes with this schema all the types of customer will be covered

s we have identified the potenstial reason and attribute that can be a part of pateint history we can assured that we can cover almost all the customer

if you want to improve you can define two type of pateint admit patient and outpatient

5) if you can define the patient then what you want to have that each and every patient should have include

PATNAME
PATADDRESS   
PAT-PHONE   

PatBirthdate   
DATEADMIT
PREVIOUSRECORD
PREVIOUSHOSPITAL   
PREVIOUSDATE  
PREVIOUSREASONFORADMIT   

REASONFORADMIT

this will cover almost all the bussiness requirement

1) like how many hospitals patient previously visited?

2) what are the reason for admit?

3) what are the previous reason for admit

4) privious medical reason for admit

5) privious date he was admitted

6) and medical reports he is undergoes throught his life and according to that define recovery plan for patient

Related Questions

Navigate

• Browse (All)
• Browse C
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.