|Course Title||The Art of Computing|
: Monday 10:00-12:00 and 14:00-16:00, Tuesday 10:00-12:00, Wednesday 10:00-12:00
Timetable for all classes
|Consultations||TBD - available by appointment|
|Units of Credit||6|
Before commencing this course, students should:
In order to do this course, students are expected to have:
After completing this course, students will:
This course contributes to the development of the following graduate capabilities:
|Graduate Capability||Acquired in|
|Scholars capable of independent and collaborative enquiry, rigorous in their analysis, critique and reflection, and able to innovate by applying their knowledge and skills to the solution of novel as well as routine problems||Labs & Project|
|Entrepreneurial leaders capable of initiating and embracing innovation and change, as well as engaging and enabling others to contribute to change||Project|
|Professionals capable of ethical, self- directed practice and independent lifelong learning||Labs & Project|
|Global citizens who are culturally adept and capable of respecting diversity and acting in a socially just and responsible way||All work|
Some students find learning to program challenging, at least at first. Here are some guidelines
The Student Code of Conduct ( Information , Policy ) sets out what the University expects from students as members of the UNSW community. As well as the learning, teaching and research environment, the University aims to provide an environment that enables students to achieve their full potential and to provide an experience consistent with the University's values and guiding principles. A condition of enrolment is that students inform themselves of the University's rules and policies affecting them, and conduct themselves accordingly.
In particular, students have the responsibility to observe standards of equity and respect in dealing with every member of the University community. This applies to all activities on UNSW premises and all external activities related to study and research. This includes behaviour in person as well as behaviour on social media, for example Facebook groups set up for the purpose of discussing UNSW courses or course work. Behaviour that is considered in breach of the Student Code Policy as discriminatory, sexually inappropriate, bullying, harassing, invading another's privacy or causing any person to fear for their personal safety is serious misconduct and can lead to severe penalties, including suspension or exclusion from UNSW.
If you have any concerns, you may raise them with your lecturer, or approach the School Ethics Officer , Grievance Officer , or one of the student representatives.
Plagiarism is defined as using the words or ideas of others and presenting them as your own. UNSW and CSE treat plagiarism as academic misconduct, which means that it carries penalties as severe as being excluded from further study at UNSW. There are several on-line sources to help you understand what plagiarism is and how it is dealt with at UNSW:
Make sure that you read and understand these. Ignorance is not accepted as an excuse for plagiarism. In particular, you are also responsible that your assignment files are not accessible by anyone but you by setting the correct permissions in your CSE directory and code repository, if using. Note also that plagiarism includes paying or asking another person to do a piece of work for you and then submitting it as your own work.
UNSW has an ongoing commitment to fostering a culture of learning informed by academic integrity. All UNSW staff and students have a responsibility to adhere to this principle of academic integrity. Plagiarism undermines academic integrity and is not tolerated at UNSW. Plagiarism at UNSW is defined as using the words or ideas of others and passing them off as your own.
If you haven't done so yet, please take the time to read the full text of
The pages below describe the policies and procedures in more detail:
You should also read the following page which describes your rights and responsibilities in the CSE context:
|Project - Proposal||Week 3||10%||2,3,4|
|Project - Implementation||HCI, Python Programming||Week 5||20%||2,3,4|
|Project - Demonstration||
|Project - Feedback||HCI, Python Programming||Week 5||5%||2,3,4|
|Labs||All topics||Weeks 1-5||20%||1,2,3,4|
|Final Exam||All topics||Exam period||45%||1,2,3,4|
** While the project demonstration is not assessed in itself, failure to attend, demonstrate and respond to questions about one's project may impact the mark awarded for the implementation.
In weeks 1-5 you will need to complete a series of lab exercises. These will typically be programming exercises asking you to solve a particular problem in python. [This may change: To receive marks for these labs you will need to get them marked by your lab coordinator in your allocated lab time in the week after the lab is released. For example, you will need to get the week 1 lab exercises marked in your week 2 lab. If you finish your exercises early, you can, of course, get them marked in the week they were assigned.]
Note: It is likely that the total number of marks for labs for the term will be somewhere between 20 and 30. This will only be confirmed in week 10. You can expect each lab mark to be worth between 0.66% of your course grade and 1% of your course grade.
In the project, you will implement an application in Python solving a problem of your choice. You will be assessed on how well you were able to write the code for this app as well as the design of its interface. While available time and skills are limitations that will need to be taken into account, the problem you choose to solve is up to you. Your project idea will need to be approved by your tutor. You are encouraged to work with a partner on your project, especially if you're new to programming, but you are not required to and can complete the project on your own if you wish.
The final exam will be open book and online. You will have 3 hours to complete it. It will involve programming exercises, but may also include multiple choice and short answer. You will NOT be remotely monitored while taking the exam.
The exam mark is subject to scaling.
There is a competency requirement for COMP1010. This is automatically satisfied by achieving 22.5/45 on the final exam. Students with good attempts at other coursework who do not achieve competency on the final exam may be offered an additional opportunity to demonstrate competency.
|Lab + Project||Exam||Total (Lab + Project + Exam)||Passing Grade|
|>50%||>50%||>50% (given based on previous grades)||Pass the course|
|<50%||>50%||>50% (not given)||Pass the course|
|>50%||<50%||>50% (not given)||Not necessarily pass. Students may be offered an additional opportunity to demonstrate competency. If a student demonstrates competency on their second attempt and their overall grade is at least 50 PS, they will be awarded the a final grade of at least 50 PS. In the situation where their course grade calculated using the exam mark from their first attempt is above 50 PS, they will be assigned the grade half-way between 50 and their initial final grade.|
|<50%||<50%||<50% (given)||Does not pass the course|
This schedule is HIGHLY subject to change based on student feedback throughout the term.
|1||Course intro, Python and Programming Fundamentals (PPF)||PPF||PPF||-||-|
|2||Python and Programming Fundamentals, User Interface Design, Web Apps||PPF||PPF||-||-|
|3||Web Apps||Web Apps||Web Apps||
Project proposal due (10%)
|4||Data Structure Design, Project support||Web Apps||Web Apps||-||-|
|5||Revision, Review, Exam information, Exam Preparation, Project Demos||Exam Preparation||Project reflection||
Project application due (20%)
Project feedback due (5%)
There are no formal textbooks for this course, but students may find the following FREE book helpful for learning and practicing python programming
Other FREE resources which have been discovered and recommended by past students of this course include:
This course is evaluated each session using the myExperience system as well as feedback from students and tutors throughout each term.
Students are also encouraged to provide informal feedback during the session, and to let course staff know of any problems as soon as they arise. Suggestions will be listened to openly, positively, constructively, and thankfully, and every reasonable effort will be made to address them.
Resource created Sunday 18 December 2022, 06:34:49 PM, last modified Monday 02 January 2023, 11:47:03 AM.