INTRODUCTION TO PROGRAMMING (NCOS 515 09)
INTRODUCTION TO PROGRAMMING (NCOS 515 09)
1
Table of Contents
1. GENERAL INFORMATION ............................................................................................................ 3
1.1 Welcome and Introduction ....................................................................................................... 3
1.2 Lecturer & Tutor Information .................................................................................................... 4
1.3 General Course Information..................................................................................................... 4
1.3.1 Formal Contact Time ......................................................................................................... 4
1.3.2 Non-Contact Time .............................................................................................................. 5
1.3.3 Notional Learning Hours.................................................................................................... 5
1.3.4 Experiential Training/Service Learning/Work Integrated Learning (WIL) .................. 6
1.4 Learning and Teaching Strategies .......................................................................................... 6
1.5 Assessment Criteria .................................................................................................................. 6
1.5.1 Formative Assessment ...................................................................................................... 6
1.5.2 Summative Assessment .................................................................................................... 6
1.5.3 Examination......................................................................................................................... 7
1.5.4 Final Mark Calculation - Opportunity Final Examination .............................................. 7
1.5.5 Re-marking, absence from exams due to illness, special examinations ................... 7
1.6 Learning Materials and Stationery Requirements ................................................................ 7
1.6.1 Prescribed Textbook(s) ..................................................................................................... 7
1.6.2 The following books are also recommended reading: .................................................. 7
1.7 Plagiarism ................................................................................................................................... 8
2. TECHNICAL COMPONENT .......................................................................................................... 8
2.1 Admission Requirements and Pre-Requisites ...................................................................... 8
2.2 Course Exit Level Outcomes ................................................................................................... 8
2.3 Moderation .................................................................................................................................. 8
2.4 Articulation .................................................................................................................................. 8
3. LEARNING COMPONENT............................................................................................................. 8
3.1 Topics and Specific Outcomes ................................................................................................ 8
3.2 Work Schedule: Introductiokn to Programming (8 CREDITS) ............................................ 9
3.3 Critical cross-field outcomes .................................................................................................... 9
4 Roles, Responsibilities and Attendance Requirements ............................................................ 10
5. Student Contract: 2025 (Introduction to Programming) ........................................................... 11
2
1. GENERAL INFORMATION
1.1 Welcome and Introduction
On behalf of Sol Plaatje University, we welcome you to the BSc programme with a
specialization in Mathematical and Computer Sciences, and more specifically to Introduction
to Programming as a module. This module is mainly intended to logically introduce you to
programming. The content will include the use of C++ / CodeBlocks as the IDE of choice.
Detailed module information is given in subsequent sections of this learner guide, showing
you the number of lectures, practical and tutorial periods per week, and providing information
about additional time you will be expected to spend on module-related work. Your
responsibilities about participation and attendance are stated and an overview is provided of
the learning and teaching approaches. Comprehensive assessment details for the module are
also given, including the materials that will be used.
This learner guide also provides you with guidelines on what to expect from the University and
what the University, in turn, expects from you regarding this module. The module is divided
into six sections, all of which collectively contribute towards preparing you for the challenges
faced in commercial software development environments.
In section 1, the module introduces you to the fundamental principles of programming in C++.
Key C++ programming concepts are discussed, together with the main programming tools and
constructs. In this section, emphasis is on understanding the C++ program structure, tools,
operators, and developing linear programs.
In section 2, the concept of conditional structures is introduced. In this section, students are
taught to use the IF and the SWITCH statements in developing branching programs. Emphasis
will be placed on problem solving and practical implementation of the code.
Section 3 will focus on looping structures. Also, emphasis will be placed on problem solving
using the FOR, DO, and WHILE statements.
Section 4 will introduce students to the concept of methods before the concept of recursion is
brought in to close the concept of looping. In this section, aspects of methods overloading,
polymorphism, and parameters will be discussed.
Section 5 will now dwell on data management, emphasizing the use of different data structures
required in handling data in memory. Precisely, 1D arrays, 2D, 3D, 4D and nD arrays is drawn
to picture. A mention (in passing) of the concepts of stacks, queues, and double linked lists is
3
made to give a picture of the various data management tools available. Operations on these
data structures are discussed, including searching and sorting algorithms.
Section 6 extends the concept of arrays to string manipulation. Key is students’ understanding
of the different string functions and their application in problem solving.
The BSc – Mathematics and Computer Sciences qualification is primarily professional and
industry specific. The knowledge students acquire emphasizes general principles and
application, developing the graduates who can demonstrate focused knowledge and skills in
programming.
1.3.1 Formal Contact Time – attendance at all classes is compulsory. The lecturer will
administer unannounced quizzes which contribute towards the final CASS mark every now
and again to curb attendance issues.
Theory 4 x 45-minute periods per week – preferably two double periods per week
Practical 2 x 45-minute periods per week - preferably one double period per week
4
1.3.2 Non-Contact Time
Students are expected to spend at least six hours in a week self-studying and completing work
outside of the formal contact time and tutorial sessions.
Lectures L 20
Tutorials T 5
Practical Work PW 10
Laboratory Work LW -
Research R 10
Service Learning SL -
Others O -
Total 80
5
1.3.4 Experiential Training/Service Learning/Work Integrated Learning (WIL)
There is currently no WIL component in this course.
The University has adopted a smart based student-centred, interactive teaching and
assessment strategy applicable.
Formative assessment will be used to inform both the student and the lecturer regarding
progress. It will be allocated marks. We use this type of assessment to allow the student and
lecturer to jointly monitor progress in achieving the module goals and specific module
outcomes. It will take the form of self-review, peer review, and lecturer reviews, and should be
seen by the student as a valuable learning aid. It will also be used to provide valuable feedback
to the lecturer regarding his/her instruction techniques, topics that require revision or additional
attention. Students will be asked to provide comprehensive evaluations of the course and
lecturer at least once during the course cycle. All formative assessments will count towards
the semester mark as indicated in the table in section 1.5.2 below.
Total 100
6
Please Note: A student must score at least 50% for the final mark (calculated as
shown above) to pass the course.
Medical certificates regarding missed tests and/or assignments, etc. must be submitted to the
lecturer or site department secretary within 5 working days of the test date or due date. Medical
certificates not received within 4 days will not be considered – unless the student was
hospitalized. If a medical certificate is accepted, an assessment would be prepared for the
student. Complaints or queries about assessment marks must be raised with the lecturer
concerned within 7 days of the assessment being returned to the students.
1.5.3 Examination
There will be a 3-hour written examination at the end of the semester. However, there will be
a subminimum of 40% required to pass an examination. If a student scores below 40% in the
examination, he/she does not qualify for a final mark and does not pass the course.
A student must score at least 50% for the final mark (calculated as shown above) in order to
pass the course. A student may be allowed to write a second opportunity examination if missed
or failed the first opportunity examination and a Final Mark would be calculated using the same
criteria used in first opportunity.
7
1.7 Plagiarism
Plagiarism should be always avoided whenever a student uses an author’s work without
recognizing it and /or cutting and pasting it (not stating facts/thought in own words). Plagiarized
work will not be accepted for marking and students may be subjected to disciplinary action.
2. TECHNICAL COMPONENT
2.1 Admission Requirements and Pre-Requisites
Refer to University General Prospectus
2.3 Moderation
All summative assessment question papers and memoranda for programming are internally
moderated at the end of the semester.
2.4 Articulation
Completion of this module offers vertical articulation to second year) and is portable to other
institutions offering the same qualification.
3. LEARNING COMPONENT
8
variables, as well as the concept of
parameters. We highlight the importance of the • Problem solving
method overloading and polymorphism. The
concept of recursion is brought in this section.
Below is a proposed work schedule which may change due to unforeseen circumstances.
Test 1
Week 7- Students to complete codes to
Week 8 - Topic 4 implement the concepts
Week 9– Students to complete codes to
Week10 - Topic 5 implement the concepts
Week11- Students to complete codes to
Week 12 - Topic 6 implement the concepts
Test 2
Examination
3.3 Critical cross-field outcomes
• Identify and creatively solve basic commercial/scientific problems within the context of
each scenario given. You can achieve this by:
o applying basic logic skills
9
o applying basic business skills
o applying programming principles
o making informed and meaningful decisions
o thinking creatively
o considering alternative solutions
• Work effectively with others as a member of a team/group.
• Organize and manage yourself and your activities responsibly and effectively.
• Collect, analyze, organize, and critically evaluate information.
• Communicate effectively using language skills in the modes of oral and/or written
persuasion.
• Use technology responsibly, effectively, and critically, showing responsibility towards
the environment and health of others.
According to University Policy all lectures must be attended punctually and regularly.
Attendance at all practical classes is especially important for students studying within the
Department of Computer Science as the computer laboratory time is at a premium and skills
gained in practical classes are fundamental for all Computer Science courses. Registers will
be taken at all classes and filed for future reference.
Participation is an important part of the class sessions. Participation means both attendance
and engagement. Students are expected to attend and fully participate in all the scheduled
classes, group learning opportunities, discussion sessions and practical sessions. In addition,
punctuality is important. Students are expected to be on time and ready to begin at the stated
time on the timetable.
Students who are not able to attend a formal contact session must provide the lecturer with a
written note explaining their non-attendance. These notes will be kept in the course file in
case queries regarding a student’s poor performance are raised.
Misunderstandings about course content or failure to understand a topic can often be cleared
up in one-on-one sessions with the lecturer and students are urged to consult their lecturers
if they have any queries, etc. It is also important for a lecturer to be aware of any personal
problems which may affect a student’s performance.
Grievance procedures
Students who have grievances should first discuss the matter with the lecturer concerned. If
reasonable cooperation from the lecturer is not forthcoming, the student may report it to the
10
class representative, who will in turn take it to the SRC, who will then inform the Head of
School who will then take the matter to the Registrar (in that order).
Academic dishonesty will NOT be tolerated in any form whatsoever. This includes cheating
during any test, submitting someone else’s work as your own (plagiarism) and copying
someone else’s program. Students caught cheating during a test (whether official or class
test), will have their answer book/paper taken away, and will be handed a new answer
book/paper to continue with. A committee consisting of the subject lecturers will then discuss
the situation and make recommendations to the Programme Head. Where two or more
students’ handed-in programs seem undeniably to be identical copies of each other, ALL the
students involved will receive a mark of ZERO.
Lecturers are expected to attend all scheduled contact classes. If possible, notice will be given
if a lecturer cannot attend a class, and arrangements will be made by the lecturer to cover the
work missed. Students are advised to check the department notice board daily for any
information pertaining to their course, classes, etc.
11
l) Student must inform the lecturer in good time of any special needs.
I hereby acknowledge that I have read and understood the Learner Guide for
Introduction to Programming (NCOS 515 08) and I agree to the contents
12