Welcome to Software Design Methodologies/Software Construction COMP2100/6442 for the first semester 2019.
Note that it will change from the last semester 2018 version. There is some shift in content and assesment approach.
A formal description of this course can be found via Programs and Courses:
For the first semester version of the course Dr Sid C-K Chau - Sid.Chau@anu.edu.au is the course convener and chair of examiners. For the second semester version of the course Dr Dongwoo Kim - email@example.com is the course convener and chair of examiners.
The second examiner for the course alternates between Sid and Dongwoo. So Sid is the first examiner in the first semester and Dongwoo is first examiner in second semester.
There is no set text book for this course. However if you have an old text book when you previously studied Java (such as Thinking Java, Bruce Eckel, referenced in COMP1110/1510) you may find that useful. Also I have written a introductory Java textbook which covers the basics of what I would expect students coming into this course would have covered. See:
- Eric McCreath, An Introduction to Programming and Software Development using Java aipsdjE1.pdf
The lecture content for this course is pre-recorded and will be made available as the course progresses. There will be classroom lectures provided as well, but the content will differ from the online content. The requirement is that students watch the recordings sometime during the weeks they are schedule. So lectures schedule in Week X should be should be watched before the end of Week X. Quizes and Labs in Week X+1 and following will assume you have watch all of the lectures in Week 0 to Week X. So you should watch the Week 0 lectures in O-week (or at the very latest before your workshop in week 1).
The proposed assessment is as follows:
|Lab Tests||20%||2 lab tests run during labs in weeks 6 and 11|
|Group Assignment||15%||stages due over semester, final commit due Friday Week 11, demo and marking Week 12|
|Final Exam||55%||3-hour exam at the end of semester|
So the final raw mark is calculated with: \[ raw = lecture + lab + labtest + assignment + 0.55 \times exam \]
(this assumes the exam is marked out of 100)
From the date that your assessment marks are released electronically, you have a period of two weeks in which to question your mark. After this period your mark will be final. Release of assessment marks will be announced on the course announcement Forum.
The exam mark or final raw mark may be scaled to produce the final overall mark and grade. This, if done, will use piece-wise linear scaling with adjustments made at grade boundaries. The final marks for COMP2100 and COMP6442 are scaled separately.
Students must get a minimum final overall mark of at least 50% to pass the course. Final marks are moderated at the Research School of Computer Science examiners meeting. Supplementary exams (or supplementary assessment) will be awarded to those students with an overall course mark of between 45 and 49.
The first lab test and final exam are hurdles that students must also pass in order to pass the course.
Please check the Undergraduate Handbook and the web for policy statements concerning special consideration and special, further and supplementary examinations.
Quality and integrity are expected from all students. Students should also expect this from the lecturing/tutorial staff. Please read over the ANU’s policy on this matter: http://academichonesty.anu.edu.au/. Very minor breaches of the academic integrity principle may result in a reduction of marks of up to 10% of the total marks available for the assessment.
There will be 9 supervised laboratory sessions, each of 2 hour duration. The first lab start in week 1.
Each lab will have some basic tasks which most people will be able to complete and gain full marks for. There will also be “challenge tasks” which I would expect some would not be able to complete or gain full marks for. Lab work will be presented and marked in person by your tutor during your registered lab time.
Ideally labs should be completed and marked during their designate lab week. So complete and have marked off Lab 1 during your first lab session in Week 1, have Lab 2 completed and marked during your second lab session in Week 2, etc.. However, if you don’t get a lab completed within the schedule slot then you are free have it marked off at the beginning of the next lab session (except Lab 9 which mush be marked off during lab 9). No work will be marked off after your final lab. If you miss a lab for a reason outside of your control, such as you are unwell, then we will attempt to arrange an alternative lab session for you. This will either be during another lab slot. All requests for such an additional lab session must be emailed to me the course convener before the lab session you miss (or as soon as it is practical after the lab). Please include in the email the scheduled lab slot you are missing, your tutors name, and the reason you will not be able to attend (or did not attend) your scheduled slot, along with any supporting documentation.
Lab sessions will be mainly used for individual learning tasks, however, you are encouraged to help each other and get help from your tutor during these session.
To register for a session, goto Streams.
During your lab in weeks 5 and 10 there will be a 1 hour lab test. These will be marked out of 10. So the final lab test mark, denoted , will be out of 20. And is calculated using:
\[ labtest = labtest_1 + labtest_2 \]
The first lab test is an early hurdle, for which a student must pass in order to continue this course.
This will be a group assignment (groups of 2, 3, 4 students) and will marked out of 10. It will involve making an app for Android. The basics of it will be started and done during the labs. The college git lab server will be used for developing and submitting the assignment. There will be a number of stages along the way, with the final stage due on Friday of Week 11 (5pm). The assignment will be presented by your group and marked during a scheduled slot in Week 12. We will make use of our lab slots, although your assignment group may be schedule for a different slot than your normal lab time.