COMP103-13 (NET) now offered in T Semester! (4 November to 13 December 2013). Click for the paper outline.
This paper introduces computer programming in C# – the exciting challenge of creating software and designing artificial worlds within the computer. It also covers concepts such as the internals of the home computer, the history and future of computers, how computers are changing society, and current research and challenges in computing.
In addition to the three hours of lectures each week, two tutorials and two hours of supervised laboratory sessions are also scheduled. Each week, students may work in pairs or individually in the lab sessions to develop new programs, and will be given tutorial exercises so that they can gauge their progress as they come to terms with the various aspects of computer science and programming. No previous computing experience is expected.
Students who pass this paper will be able to create programs in C#, using the common graphical controls such as buttons, picture boxes and text fields. They will understand the basic concepts of event-driven and object-oriented programming. They will be able to use conditional statements to react to user input and process errors. They will be able to use iterative statements, arrays, lists and structs to process large amounts of data. The student will understand a broad range of significant Computer Science concepts.
COMP106 General Programming
Official Timetable Information
Two tutorials per week, held in various rooms around campus. The places and times for the tutorials are available
Two one-hour supervised labs each week in labs 3 and 4 in R-block. The times for the lab sessions are not yet available.
There are three lectures a week. They provide a medium for presenting the background, theoretical material, and general information for the paper.
There are two programming tutorials scheduled each week, where you will meet in a small group with your tutor, to discuss concepts covered in lectures and work on exercises in small groups.
The practicals for this paper give you the crucial 'hands-on' experience that is necessary to learn computer programming. Each week in the labs we will practice important skills dealing with various aspects of programming and the C# language. You may work with a partner or individually to create a new program, experiment with different ways of making it work better, and discuss your solutions with your demonstrator or tutor.
Students should expect to spend about 10 hours per week on this paper, in the following proportions:
'Starting out with Visual C# 2010 (Second Edition)'
by Tony Gaddis.
You must purchase the Laboratory and Tutorial Manual from Campus Copy
The laboratories for this paper are RG.10 and RG.11 (Labs 3 & 4). They are equipped with 85 Windows Personal Computers. The programming environment will be C# using Microsoft Visual Studio 2010. If you want to use C# at home, you can download Microsoft Visual C# 2010 Express Edition for free from http://www.microsoft.com/visualstudio/eng/downloads#d-2010-express. Printing, email and web access is available but will be charged for via the Unicash system.
The Part I Computer Laboratories are available to enrolled students Monday to Friday 8am to 9pm. A schedule of supervised and 'free' time will be posted on the lab doors. Prior to 8am, after 9pm, and at weekends, your (cardax activated) student ID card will be required for access. Students found in the lab at these times without a card will be removed.
The practical programme must be completed to the satisfaction of the coordinator for the paper.
The in-class test will test the material covered up to that point. Details about the test will be given out in lectures prior to the test.
Each week you will be asked to design or modify a simple program in your laboratory sessions. This may be done using pair programming, with each person taking 10 minute turns on the keyboard. You can also complete the exercises individually if you wish. After you have implemented a program, you will discuss it with your demonstrator in the lab, and will be given a mark for it.
The practical tests will test your individual understanding of the programming skills that you have been practicing in the laboratory exercises. NOTE: Due to the size of the class, practical tests may be run in multiple sessions. The tests for each session are different, but are similar in material and level of difficulty.
Each tutorial involves exercises that you should read before going to the tutorial. Tutorial exercises will be worked through during the tutorial, under the guidance of the tutor. You will be asked to attempt an exercise in a small group and hand in your attempt in the tutorial. You will receive either a 0 or a 1 for your attempt at the tutorial exercise. A 0 being an unsatisfactory attempt and a 1 being an attempt to the satisfaction of the tutor. To receive this mark you must attend the tutorial as you cannot hand in your attempt outside of the tutorial.
The first project deliverable is to create a paper prototype for the user interface of the application you will build. No coding is required for this part.
The second project deliverable is to create an application which satisfies the project specification. It is graded in two phases. First, it is verified in the laboratory and then the completed program is electronically collected in for marking. The marked project is available to be collected before the final exam.
Students must hand in their coursework by the due date. If they have not completed it, they should hand in what they have done so far. Individual extensions will not be given except for a medical certificate or counsellor's letter specifically referring to that item of assessment.
Internal assessment/final examination ratio 2:1 or 1:2, whichever works in your favour. The practical programme must be completed to the satisfaction of the co-ordinator for the paper.
An overall mark of 50% is required for a pass, with a minimum of 35% in the final exam. An RP grade will not normally be accepted as fulfilling a prerequisite for a more advanced paper (see Assessment Regulations, 20.(4) p125).
The 4 tests (3 practical tests and 1 in-class test) are 'compulsory assessment items' of the course (See the University Calendar 2013 - Assessment Regulations, 20.(5) p125). Missing these components of the course without excuse may result in a failing grade.
The internal assessment is:
|Tutorial Handins, 10 x 0.5%|| 5%|
|Moodle Quizzes, 10 x 0.5%|| 5%|
|Laboratory Exercises, 9 x 0.55% || 5%|
|Practical tests, 3 practical tests (5%, 12%, 13%)||30%|
|In-class theory test||10%|
|Project Deliverable 1|| 2%|
|Project Deliverable 2||10%|
|Practical test 1||Wed 31st July 2013|
|Practical test 2||Wed 14th August 2013|
|In-class theory test||Mon 16th September during Lecture time|
|Project Deliverable 1||Fri 20th September 2013 by 4pm|
|Practical test 3||Wed 25th September 2013|
|Project Deliverable 2||Fri 11th October 2013 by 4pm|
Class attendance is expected. The lecture material, tutorials and laboratory practicals are all integral parts of the paper. Failure to attend any of these means the student may miss material not presented elsewhere. Students are responsible for all material covered in class.
Resources in the form of lecture notes, videos of lectures, course outline, background material, various user guides, lab and test sign ups, practice tests, project specifications, sample code, data files and weekly quizzes will be made available through the course Moodle website. Also available on the course Moodle website will be support through various interactive forums.
This paper is compulsory for a major in Computer Science.
Follow this link for Academic Integrity information.
Follow this link for information on Performance Impairment.
Student Concerns and Complaints
Follow this link for Student Concerns and Complaints information.
Application for Extension
Follow this link for information on applying for an Extension.
Review of Grade
Follow this link for information on applying for a Review of Grade.
Your attention is drawn to the following regulations and policies, which are published in the University Calendar: