It's UWAweek 47

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 684 articles.
Currently 122 other people reading this forum.


 UWA week 37 (2nd semester, week 7) ↓
SVG not supported

Login to reply

👍x1
helpful
6:31pm Thu 12th Sep, ANONYMOUS

I've had a look at the unit outline and theres a discrepancy with the weighting, in 1 part it says the project is worth 15% and in another part (further down) it says 20%. Anyway, my main question is, as there are 2 parts to the project, and a follow up test, can someone please give us a break down of how much weighting % are within each component of the project so we know where to put our focus? Eg. if the score comprises entirely of just the test at the end, that info would affect my workflow/study method. Or, if all parts of the project are marked, that will also affect my mindset. Sorry if this has been covered in lectures. Thank you :)


SVG not supported

Login to reply

👍x1
helpful
10:12am Fri 13th Sep, Mehwish N.

The first part of the unit outline show indicative weights that are in the handbook and do not change. From semester to semester, we change the weights slightly depending upon various factors (student feedback, performance of students, chatGPT etc.). The right percentage has been communicated under "Required Assessments". Under the same heading it shows that the project will be graded via the take home test. This information has been communicated in other ways too, e.g., in the introductory lecture, in the project-specs and several times in the class. The project has been broken down into parts to improve the learning of the students. It would have been much easier for us to give a big project which was due toward the end of the semester, but breaking down the project into parts has a lot of bnefits. Here is how the current method is useful: 1. Part 1 of the project is about conceptual modeling. Students are encouraged to work in pairs. Research has shown that learning improves when students work in pairs. Since this part is not graded, students will be discouraged to use chatGPT/AI, rather, a number of students have told me that they are at ease and do not have the pressure to solve the assessment for marks. 2. Following the submission a solution as well as a rubric will be provided so that students can grade themselves and find out where they went wrong. 3. Part 2 will be based on our solution. This is to ensure students are not getting penalised for making mistakes in part 1. 4. Submission of part 2 will also not be graded but essential for being eligible to do the take-home test. 5. By the time there will be a take home test, students should have a very good understanding of the project without feeling the need to use AI based method or copying from each other. 6. Finally, we will call about 10% students for interviews (aka. demo), based on the following criteria: - randomly pick someone - we suspect the student has either used AI or colluded with another student - the student has performed very well and we just want to meet them :) - the student has shown poor performance and we want to help the student I am happy to get feedback post take-home test submission. It is the students' feedback that help us improve the unit. 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