How to Apply

The appliant sould be in possession of an undergraduate Bachalor in Science degree, in Computer Science or an equivalent with major in Computer Science. Applications should be submitted by 30 September. There is NO fee payable for your postgraduate application. Minimum entry requirements is 60% average in third year Computer Science modules with a B.Sc degree in Computer Science. Please note: Amissions is not guaranteed when the applicant meets the minimum entry requirements. 

International Applicants

All applicants who did not obtain their qualifications in South Africa / Non South African students, must please submit all your qualifications to SAQA (South African Qualifications Authority) for an evaluation. For an application fee, SAQA will evaluate your qualifications. You can visit their website at www.saqa.org.za for more information. We cannot respond to your application until you submit a certificate issued by SAQA stating the NQF level of your qualifications.

How To Apply

Applicants are required to apply online via https://www.uwc.ac.za/

To ensure the successful completion of your application, please submit the following supporting documents (certified) to the Natural Sciences Faculty:

• The documents to be submitted by foreign students:
  
  • Certified copy of passport
  • Certified copies of all official academic transcripts / record of results
  • Certified copy of degree certificate
  • SAQA Evaluation Certificate
  • Short Curriculum Vitae (CV)
  • One page letter of motivation
  • Proof of funding
• The documents to be submitted by South African students:
  
  • Certified copy of South African ID
  • Certified copies of all academic transcripts / record of results
  • Certified copy of degree certificate
  • Short Curriculum Vitae (CV)
  • One page letter of motivation
  • Proof of funding

Consult the Natural Science Faculty if additional documentation is required to science-postgrad@uwc.ac.za or +27 21 959 2975.

Consult the Department if Computer Science for the status of your applications to Mrs Fatima Jacobs-Samsodien fjacobs@uwc.ac.za or +27 21 959 2635

Each student must register for 8 modules of 15 credits = 120 credits. Students may also register 2 modules from another department with the permission of the HOD of Computer Science, within the group of selections as stated in the year book.

HONOURS COURSES

MORE INFORMATION ON COURSES

Honours Project Documentaiton Guidelines 

In addition to a working program and its source code, you must also author the documents discussed below to gain full credit for the programming project. The fundamental structure of these documents is entirely independent of project, programming language, and operating system. You will find a number of advantages when you pursue a rigid documentation approach to programming. First of all, you will have a firm understanding of the task at hand before you start coding. A good understand of the problem leads to a clean design that tends to have fewer bugs. Always make your goal to program it right the first time! The next advantage is that others will be able to use your documentation to test the program, fix bugs, and make enhancements. In the corporate world, these duties are normally performed by different people and often by different groups within a single company. Therefore, the more detailed, organized, and easy-to-read your documentation is, the more you help other people do their jobs. As you learn to writesolid documentation, you will also come to appreciate reading solid documentation, and will eventually detest reading technical crap (the world is full of poorly written technical books and manuals). In other words, write simply and clearly. The way you write is just as important as the details you present. Always strive to spell correctly and use proper grammar. The campus Writing Center can aid you in this respect.

• User Requirements Document (URD)
• Requirements Analysis Document (RAD)
• User Interface Specification (UIS)
• The Prototype
• Object Orientated Analysis (OOA) or High Level Design (HLD)
• Object Orientated Design (OOD) or Low Level Design (LLD)
• Code Document
• Testing Document (TD)
• User Guide

Project Planning and Meetings 

Each term, you must define a project plan that includes the specific tasks of your project, and the dates by which you intend to accomplish them. Everyone’s project plan will include dates for the submission of project documents, weekly meetings, monthly reports, and the presentation. However, the most important items on the project plan will relate specifically to the technical issues of your project. The project plan should be continually updated. Essentially, the project plan maps out a schedule for each term, and should be updated as you work ahead or fall behind the schedule, or discover things that you need to do along the way. If you organise your project plan well, by the end of each month, you will have a summary of what you have accomplished for the month. 

You are required to meet with your project supervisor on a weekly basis to discuss the progress and problems related to your project. The format, length and content of the meetings will vary from supervisor to supervisor, and even student to student, but the overall objectives are to inform your supervisor of your progress and also to get advice on how to go about defining and prioritising the activities required to complete each module’s objectives. If you miss three of these meetings, you will not be allowed to pass the module.

CHOOSING A SUPERVISOR

Supervisors and List of Research Interests