It's UWAweek 42 (2nd semester, week 12)

help1402

This forum is provided to promote discussion amongst students enrolled in CITS1402 Relational Database Management Systems.

Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.

How do I ask a good question?
Displaying the 2 articles in this topic
Showing 2 of 612 articles.
Currently 79 other people reading this forum.


 UWA week 39 (2nd semester, week 9) ↓
SVG not supported

Login to reply

👍x2
helpful

Hi, I actually found some discrepacies and missing information I would like to discuss, I hope this will reach the teaching team to help me and other students to do their projects. Below I have grouped the questions according to the entity for ease of reading. CLIENT: 1. From the case study narration provided there is this sentence of "and one or two email address (S 20) are recorded along with a generated unique client identifier". However the ERD for client only have phone[1..2] and does not specify email[1..2]. Should we still add the email to the logical model (following narration) or should we ignore the email and just follow the ERD? 2. As for this "generated unique client identifier" are we free to use any data type or there are certain data types we have to adhere to? 3. Seems like the erd is wrong for client address (address as the header of composite values should not be indented right?) 4. How about company name? narration does not provide the type for it, are we allowed to assume the length on out own? VEHICLE TYPE: 5. Model data type and length is not specified for Vehicle Type, which should we use then? 6. What should we fill in Doors, Body and Trim? it is not specified in the narration. 7. As for Fuel can we fill it with S(6) since it is mentioned in narration that it can be (EV, Hybrid, Fuel)? or Fuel here refers to something like "Gasoline" and "Diesel"? VEHICLE: 8. Same with question 1, Vehicle ERD does not have phone number. Should I still follow narration and add it or just ignore it and follow ERD? INSURANCE: 9. InsuranceID and PolicyType does not have data type in narration, what data type should we use? Are we allowed to assume on our own? POLICY NUMBER: 10. Policy number does not have any data type mentioned in narration, what data type should we use? Are we allowed to assume on our own? HIRED VEHICLE: 11. If I think that Date and Days is a dangerous column name to use in SQLite (it may be used as function or method in other sql languages), are we allowed to rename it to something like startDate and hireDays for clarity? OTHER MISC QUESTION: 12. If I believe that making new single primary key field is better instead of using multiple fields for composite keys (of course it will be recorded in the assumption pdf), am I free to choose whatever data type I use for this?


SVG not supported

Login to reply

👍x2
helpful

Thanks for pointing out the issues. Let me answer these one by one. "Andre Harsono" <24*7*1*6@s*u*e*t*u*a*e*u*a*> wrote:
> Hi, I actually found some discrepacies and missing information I would like to discuss, I hope this will reach the teaching team to help me and other students to do their projects. > Below I have grouped the questions according to the entity for ease of reading. > > CLIENT: > 1. From the case study narration provided there is this sentence of "and one or two email address (S 20) are recorded along with a generated unique client identifier". However the ERD for client only have phone[1..2] and does not specify email[1..2]. Should we still add the email to the logical model (following narration) or should we ignore the email and just follow the ERD?
This was a human error. I missed it, however, just follow what is there in the ERD.
> 2. As for this "generated unique client identifier" are we free to use any data type or there are certain data types we have to adhere to?
You can use any data type.
> 3. Seems like the erd is wrong for client address (address as the header of composite values should not be indented right?)
Yes, there is an extra tab. I'll update that in a while.
> 4. How about company name? narration does not provide the type for it, are we allowed to assume the length on out own?
Sure.
> > > VEHICLE TYPE: > 5. Model data type and length is not specified for Vehicle Type, which should we use then?
You can assume it yourself.
> 6. What should we fill in Doors, Body and Trim? it is not specified in the narration.
Also, please assume yourself. We added some new info as part of the scope creep.
> 7. As for Fuel can we fill it with S(6) since it is mentioned in narration that it can be (EV, Hybrid, Fuel)? or Fuel here refers to something like "Gasoline" and "Diesel"?
S6 is fine. Even if someone keeps it an integer, that also works
> > VEHICLE: > 8. Same with question 1, Vehicle ERD does not have phone number. Should I still follow narration and add it or just ignore it and follow ERD?
Follow the ERD
> > INSURANCE: > 9. InsuranceID and PolicyType does not have data type in narration, what data type should we use? Are we allowed to assume on our own?
It can be a string of a fixed length. You can decide the length.
> > POLICY NUMBER: > 10. Policy number does not have any data type mentioned in narration, what data type should we use? Are we allowed to assume on our own?
Same as above
> > HIRED VEHICLE: > 11. If I think that Date and Days is a dangerous column name to use in SQLite (it may be used as function or method in other sql languages), are we allowed to rename it to something like startDate and hireDays for clarity?
In the SQL part of the quiz, you may need to use the same attributes as I will share with you the minimal schema.
> > OTHER MISC QUESTION: > 12. If I believe that making new single primary key field is better instead of using multiple fields for composite keys (of course it will be recorded in the assumption pdf), am I free to choose whatever data type I use for this?
Yes you can! But I suggest that you stick to what you have in the ERD as attributes. Cheers

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  8:08AM Aug 25 2024
Privacy policy