It's UWAweek 17 (1st semester, week 8)

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 selected article
Showing 1 of 95 articles.
Currently no other people reading this forum.


 UWA week 15 (1st semester, week 6) ↓
SVG not supported

Login to reply

👍?
helpful

Hi, I have been watching the forums in the past few days. Nice to see people have some questions. I clarified some questions today in the class and later by individual appointments. First of all you need to state your assumptions. After interaction with multiple students, here are some of the ways that you can approach the terms mentioned in the case study. "Each eye surgeon has one or two minor surgeries in which they work". Some of you are considering minor surgery as a service. This could work, but remember that in such clinics, surgery is often referred to as a "surgery room" as indicated in the case study "...in which they work". Just state your assumption when you are referring to this term. "a parent might be a customer without being a patient if they pay the bills for their child who is a patient." Hint: One option is to do specialisation here. For instance for a class person, you can have two subclasses, patient and customer. You need to think of how you are going to apply constraints. "the patient cannot have multiple appointments with the same surgeon on the same day" Hint: Think of how you can make a tuple unique. Treatment vs Service. Hint: Assume eyesight-check is a treatment, it may offer finding the right power for the classes and may also offer fitting contact lenses. Cheers Mehwish

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  5:07AM Sep 06 2023
Privacy policy