Faculty of Informatics
MSC9114 Procedural Programming
Subject Outline
Autumn Session 2007
Head of School
–Professor Philip Ogunbona, Student Resource Centre, Tel: (02) 4221 3606
|
Subject
Coordinator |
Dr Jo Abrantes |
|
Telephone Number: |
4221 3872 |
|
Email: |
|
|
Location: |
3.212 |
Dr Abrantes Consultation Times During
Session
|
Day |
Time |
|
Wednesday Thursday |
15:30 – 17:30 10:30 – 12:30 |
|
Lecturer |
Associate Professor
Willy Susilo |
|
Telephone Number: |
4221 5535 |
|
Email: |
|
|
Location: |
3.203 |
Dr Susilo Consultation Times During
Session
|
Day |
Time |
|
Monday Thursday |
8.30 – 10.30 8.30 – 10.30 |
Subject
Organisation
|
Session: |
Autumn Session, |
||||||
|
Credit Points |
6 |
||||||
|
Contact hours per
week: |
4
hours lecture; 2 hours laboratory/tutorial
|
||||||
|
Lecture Times &
Location: |
|
||||||
|
Tutorial Day, Time and
Location can be found at: |
|
||||||
Students
should check the subject’s web site regularly as important information,
including details of unavoidable changes in assessment requirements will be
posted from time to time. Any
information posted to the web site is deemed to have been notified to all
students.
MCS9114 introduces the procedural approach to program design and
implementation. Covers basic language constructs for defining variables of
built-in types, flow control constructs and simple I/O. Explores functional
decomposition as a design technique, and the implementation of functions.
Introduces simple user-defined data types and aggregates.
On successful completion of this subject, students should be
able to:
1.Effectively use basic C++ functionality to code simple
algorithms
2. Analyse and explain the behaviour of simple programs
3. Design, implement, test and debug simple programs
4. Apply the techniques of structured decomposition to break a
program into smaller pieces
5. Display a working knowledge of good programming style
Attendance
Requirements
It is the responsibility of students to
attend all lectures/tutorials/labs/seminars/practical work for subjects for
which you are enrolled.
It should be noted that according to Course Rule 003{Interpretation Point 2 (t)} each credit point for a single session subject has the value of about two hours per week including class attendance. Therefore, the amount of time spent on each 6-credit point subject should be at least 12 hours per week, which includes lectures/tutorials/labs etc.
Satisfactory
attendance is deemed to be attendance at approximately 80% of the
allocated contact hours. Attendance rolls will be kept for the laboratories. If
you are present for less than 80% of the laboratories you need to apply for
special consideration, otherwise a fail grade may be recorded.
Students
MUST attend their allocated tutorial
unless they have the written permission of the subject coordinator.
This subject comprises lectures and
laboratory classes. Laboratory classes will relate to the lecture topics.
Laboratory classes commence in week 2.
Lecture slides and programming examples
will be available from the subject’s e-Learning website (previously
Laboratory
Procedures
· Students must abide by
the laboratory rules posted on the wall of the Laboratory (and included in this
document).
· Students may use the
computers outside their designated laboratory times provided the laboratory is
open and no other laboratory class is scheduled. If another class is scheduled
for the laboratory, you may enter no earlier than 20 minutes after the
scheduled starting time and ask the supervisor whether any vacant machines may
be used.
· To complete the assignment
component of the subject, students need to design and implement programs in C++
(using a C++ standard compiler). There is no requirement to carry out the
assignment in the laboratories. You may still work at home to develop
solutions. However, submissions are via the labs, and assistance in
laboratories will be for programs demonstrable in a Linux/UNIX environment.
· Copying software from
another person is in breach of copyright, as is selling original disks of
software whilst retaining a copy. Exchanging disks also leads to the
introduction of software viruses, which may corrupt the system.
· Students are advised to
purchase a Zip Disk/flash disk. It can be used to keep current and archive
copies of assignments. Loss or damage of disks is no excuse for failure
to submit assignments. It is students’ responsibility to make sure
that their assignments can be submitted on time.
· Students must do their
laboratory tasks during the laboratory time (see assessment for more detail).
· Assignments can be done
in the lab if the laboratory work has been completed. However, it is students’
responsibility to work outside the laboratory time and make sure that the
assignments can be submitted on time.
Students should check the subject's web
site regularly as important information, including details of unavoidable
changes in assessment requirements will be posted from time to time via e-Learning
website http://www.uow.edu.au/student/lol.
Any information posted to the web site is deemed to have been notified to all
students.
Lecture Schedule
|
|
Topics |
|
1 |
Introduction to
computing concepts. |
|
2 |
Introduction to
computer programming languages. |
|
3 |
Writing, editing,
compiling and linking programs |
|
4 |
Internal
representation of data. |
|
5 |
Numbering systems |
|
6 |
Introduction to
programming in C++ |
|
7 |
Programming style |
|
8 |
Introduction to
algorithms |
|
9 |
C++ Data Types,
operators and expressions |
|
10 |
Simple input/output |
|
11 |
Control Structures:
Conditional |
|
12 |
Control Structures:
Repetition |
|
13 |
Modular programming
with functions |
|
14 |
Variable Storage
Classes |
|
15 |
Arrays |
|
16 |
C-Strings |
|
17 |
Input/output
formatting and files |
|
18 |
User defined data
types: typedef, structures |
|
19 |
Recursion |
|
20 |
Bitwise programming,
Pseudorandom numbers |
CSCI114 and MCS9114 have a joint web
site, which will be made available through the CSCI114/MCS9114 e-Learning website
(http://www.uow.edu.au/student/lol).
Students should check the subject’s web
site regularly as important information, including details of unavoidable
changes in assessment requirements will be posted from time to time. Any information posted to the web site is
deemed to have been notified to all students.
Subject Materials
·
Tony
Gaddis
Starting
Out with C++: From Control Structures through Objects, 5th Edition, Pearson, 2007.
·
CSCI114 Laboratory
Manual
– it is compulsory that students have the Manual during the lab sessions.
· D. S. Malik
C++
Programming: Program Design Including Data Structures, Thompson
Learning, Third Edition, 2006
· Judy
Scholl
C++ Programming: From
Problem Analysis to Program Design, Lab Manual, 2005
· Walter
Savitch
Problem
Solving with C++: The Object of Programming, Third Edition,
Addison-Wesley, 2001
· Gary J.
Bronson
Program
Development and Design Using C++, Second Edition, Thompson
Learning, Brooks/Cole, 2000
· Bjarne
Stroustrup
The C++
Programming Language, Third (Hard Cover) Edition, Addison-Wesley,
2000
· Forouzan
and Gilberg
Computer
Science: A Structured Programming Approach Using C++, Nelson
Learning, 2000
·
Dean DeFino and Michael Bardzell
Lab
Manual to Accompany the Standard and Brief Versions of Starting Out with C++,
4th Edition, Pearson, 2004
These may be available
from UniCentre Bookshop.
These readings/references are recommended only and are not intended to be an exhaustive list. Students are encouraged to use the library catalogue and databases to locate additional readings
This subject has the following assessment
components.
|
Assessment Items & Format |
Percentage of Final
Mark |
Due Date |
|
4 Assignments |
32% |
See
notes below. Assignments are due in weeks 5, 7, 10 and 13 respectively |
|
Laboratory Manual |
3% |
See notes below. |
|
5 Laboratory Online Tests |
5% |
See notes below. |
|
Mid Term Test |
15% |
Week 7 on Thursday, during lecture time |
|
Final Examination |
45% |
Examination Period |
Unless
otherwise notified by the subject coordinator, all written assignments must be
submitted electronically.
(a) There will be 4
programming assignments, which will be assessed. These will contain programming
problems and/or complete programs that exercise particular skills as you learn
them. Your completed attempts must be submitted electronically via the
UNIX/Linux submit system. No submission via email will be accepted.
(b) All assignments are to
be completed independently. Plagiarism
may result in a zero mark being recorded for that assignment.
(c)
Eventual
changes on assignment due dates will be posted on the e-Learning website of the
subject. It is each student’s responsibility to regularly check the subject’s
website.
(d) Assignments are to be
submitted electronically before the scheduled time, normally by Monday, 11.59pm
(e) As
assignments are to assess a student's understanding of course material, each
assignment must be solved using only material covered up to that point in the
course (unless otherwise explicitly stated in the assignment).
(f) Assignment programs submitted which do not produce the required result on the laboratory Linux system cannot be awarded more than half marks. Programs that do not compile on the laboratory Linux system due to syntax errors may receive no marks, but still may be commented upon.
(g) Late assignments will be marked but the mark awarded will be reduced by 25% for each day late. Assignments will not be accepted more than four days late.
(h) Assignments will be
returned in laboratory classes. Enquiries about the marks can only be made to
the tutors during the laboratory class time, with a maximum of 1 week after
the assignment is handed back. After 1 week, no marks can be changed.
(i) Penalties may apply to all late work, except
if special consideration or an extension has been granted by your subject
coordinator or lecturer.
(j) Under some
circumstances, an assignment extension may be granted by the subject
coordinator/lecturer. The subject coordinator/lecturer has the full right to
deny/award the extension. Each student must apply for the extension through the
SOLS system before the assignment due date. In many circumstances,
students may be asked to produce documentation to support his/her case.
(k) Each student must
complete at least five online tests - seven of these tests will
take place throughout the session (in weeks 3, 5, 7, 9, 11, 12 and 13). These tests will be made available for 10
minutes during each student’s allocated lab.
(l) Each set of weekly
Lab Manual exercises starts with one exercise labelled Task 0 which must
be completed before the respective lab class, most of the other exercises are
to be completed in the lab class. Any remaining weekly exercises not completed
in class must be completed during the students own study time.
(m) Each student must
complete at least 70% his/her Lab Manual exercises to be awarded the 3% of the
final mark allocated to the Lab Manual. Lab Manuals may be checked at any time
during lab classes by the tutors or lecturers. Marks will be deducted for a
student’s failure to either (i) produce his/her Lab Manual, (ii) have all Task 0’s completed up to the current week, or
(iii) have less than 70% of the exercises up to the current week completed.
(n) Mark deductions for
failure to comply with the Lab Manual requirements mentioned above are as
follows:
§ Any Task 0, up to
the current week, not completed will incur in the loss of 0.5% of the final
mark
§ Less than 70% of
completion of the Lab Manual exercises, up to the current week, will
incur in the loss of 3% of the final mark, unless the student is able to show
his/her tutor in the following’s week lab class that he/she has completed all
the required exercises.
§ Failure to bring the Lab
Manual to class will incur in a loss of 3% of the final mark, unless the
student presents his/her Lab Manual to the subject coordinator or lecturer
before the end of the current week.
Note: the total
deductions may never be over the 3% allocated to the Lab Manual work.
(o)
There is no supplementary test available for mid term test.
The test will be conducted on Thursday’s
lecture time on Week 7. The venue will be arranged and published via SOLS.
You must ensure that you attend this test to avoid losing 15% of the total
marks in this subject.
Special
consideration
An
extension of time for the completion of an assignment may be granted in certain
circumstances. A request for an extension
must be made to the Subject Coordinator via SOLs before the due date.
Scaling
Final results in this subject may be scaled. The scaling method that will be used in this subject is as follows.
If
E is the student exam mark out of 40, and A is the student assignment mark out
of 60, the student final mark will be determined as follows:
if E >= 40% of the maximum exam mark: then
student final mark is E + A;
if 35% <= E < 40% of the maximum exam
mark: then student final mark is /min/{E+A, 47};
Students must refer to
the Faculty Handbook or online references which contains a range of policies on
educational issues and student matters.
Please note that if this is your last session and you are granted a supplementary exam, be aware that your results will not be processed in time to meet the graduation deadline.
Plagiarism
When you submit an assessment task, you are declaring the
following
1.
It is your own work and you did not collaborate
with or copy from others.
2.
You have read and understand your responsibilities
under the
3.
You have not plagiarised from published work
(including the internet). Where you have used the work from others, you have
referenced it in the text and provided a reference list at the end ot the
assignment.
4.
Plagiarism will not be tolerated.
5.
Students are responsible for submitting original
work for assessment, without plagiarising or cheating, abiding by the
University’s policies on Plagiarism as set out in the Calendar under University
Policies, and in Faculty handbooks and subject guides. Plagiarism has led to
the expulsion from the University.
This outline should be read in conjunction with the following documents:
|
Code of Practice -
Teaching and Assessment http://www.uow.edu.au/handbook/codesofprac/teaching_code.html |
Key Dates |
|
Code of Practice -
Students http://www.uow.edu.au/handbook/codesofprac/cop_students.html |
Information Literacies
Introduction Program |
|
Acknowledgement
Practice Plagiarism will not be
tolerated |
Student Academic
Grievance Policy http://www.uow.edu.au/handbook/codesofprac/cop_supervision.html#8 |
|
Special Consideration
Policy http://www.uow.edu.au/handbook/courserules/specialconsideration.html |
Code of
Practice-Honours |
|
Non-Discriminatory
Language Practice and Presentation |
Intellectual Property
Policy http://www.uow.edu.au/research/researchmanagement/1998IP.html |
|
Occupational Health and Safety http://staff.uow.edu.au/ohs/commitment/OHS039-ohspolicy.pdf |
SCSSE Internet Access
& Student Resource Centre http://www.sitacs.uow.edu.au/info/current/internet_access_and_resource.shtml |
|
SCSSE Computer Usage
Rules http://www.itacs.uow.edu.au/info/current/support/labs/rules.shtml |
SCSSE Style Guide for
Footnotes, Documentation, Essay and Report Writing |
|
SCSSE Student Guide |
Informatics Faculty
Librarian, Ms
Annette Meldrum, phone: 4221 4637,ameldrum@uow.edu.au |
|
SCSSE Subject Outlines |
|