Scribd
Upload
721 views

PROJECT GUIDELINE

The document is a project guide for the Zimbabwe School Examinations Council's Computer Science curriculum, requiring learners to develop a computer-based project using a high-level programming language. It outlines the project layout, including sections on problem identification, design, development, testing, and evaluation, along with a detailed marking guide. Teachers are expected to provide ongoing support, and learners must document their process thoroughly.

Uploaded by

paulas2014
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
721 views

PROJECT GUIDELINE

The document is a project guide for the Zimbabwe School Examinations Council's Computer Science curriculum, requiring learners to develop a computer-based project using a high-level programming language. It outlines the project layout, including sections on problem identification, design, development, testing, and evaluation, along with a detailed marking guide. Teachers are expected to provide ongoing support, and learners must document their process thoroughly.

Uploaded by

paulas2014
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

APPENDIX 1

ZIMBABWE SCHOOL EXAMINATIONS COUNCIL


COMPUTER SCIENCE 4021

PROJECT GUIDE

The learner is required to develop a computer-based project to solve a specific problem using a
high level programming language for example Visual Basic or Python. The project is to be
carried out from Form 3 end of Term 2 up to Form 4 Term 2. This will enable the learners to use
their skills and experience gained during the course to analyse, design, implement, test and
evaluate the solution to a problem. Learners are advised to document every activity undertaken
as they carry out the project.
The mark a candidate achieves is linked to the problem definition. Guidance from the teacher is
needed in the choice of a problem. Teachers must provide on-going support, guidance and
supervision while learners carry out the project.

Project Guide
The project must include the following layout

1. Cover page
2. Table of contents
3. Appendices
Sample of completed questionnaires
Sample of interview questions with respondent answers
Sample documents
SECTION A
Selection, Investigation and Analysis

Problem Definition/Identification
Investigation of the current system
- Research instruments e.g. questionnaire, record inspection, interviews and
observation.
Broad description of existing system
Evaluation of existing solution
-weaknesses
-strengths
Requirements specifications
- Software
- Hardware.
Aims and objectives
Evidence that the research has been carried out.
- Examples are filled in questionnaires, interviews with respondent answers, sample
documents and write up on observation.
SECTION B
Design
Consideration of alternative method.
- Justification of method of solution
Input design
- Appropriate data capture forms and screen layouts
Output Design
- Specification and design of the required output
Test Plan
- design and document a test plan
SECTION C
Software Development
Technical documentation
- Algorithms related to system requirements
 pseudo codes
 flowcharts for modules
- codes/program listings
User documentation
Installation
Starting the systems
Exiting the system
SECTION D
Testing and Evaluation

User Testing
- Test for standard, extreme and abnormal/invalid data
- Evidence of testing to be shown through sample runs and error messages
Evaluation of the system
- Achievements
- Limitations
- Opportunities for future development

SECTION E
General Expectations
Depth of Knowledge and Understanding
- Reflects the degree of computing in the project
Degree of Originality
- Imagination and innovation
- Has an attempt been made to do something different/unique?
Quality of the completed report
- Written report should be easy to follow
- Defined sections, page numbers and an index.

COMPUTER SCIENCE 4021


Project Marking Guide

Section A: Selection, Investigation and Analysis [22]


i. Problem definition/Choice of problem area and background analysis [4]
Meaningful name of system
Location
When it started
Population Size
Accept any meaningful variations
[Any 4 marking points]

ii. Investigation of the current system [4]


Research Instruments [2 marks per instrument]
o Questionnaires, Interview guides, Record Inspection, observation [4]
iii. Broad description of existing system [4]
Clearly explain the input, output, process, storage of the existing system
o Input [1]
o Output [1]
o Process [1]
o storage [1]
iv. Evaluation of existing system [2]

weakness
strengths

v. Requirements specification [2]


Software requirements [1]
Hardware requirements [1]
vi. Aims and objectives [4]
Aims [Any two aim] [2]
2 Objectives [1 mark per 1 objective] [2]
vii. Evidence of research [2]
Any two from the following [ one mark each]
o Filled in questionnaire
o Interview session (Question and answer)
o Sample documents
o Description of observations
Section B: Design [11]
(i) Consideration of alternative methods [2]
At least 2 methods
(ii) Justification of method of solution [2]
(iii) Input design [2]
Data capture forms [1]
Screen layouts [1 ]
(iv) Output design [2]
Specification of required output [2]
[max 2]
(v) Test plan [3]
Name and describe a test plan including test data and expected outcome in your
description
o name [1]
o description [1]
o outcome [1]
Section C: System Development [7]
(i) Technical documentation [4]
At least2 Pseudocodes of any major modules. [2]
At least 1 flow charts for any major modules. [1]
Code/Program listing [1]
(ii) User documentation [3]
Installation [1]
Running the system [1]
Exiting the system [1]
Section D: Testing and evaluation [5]
(i) User testing (any two) [2]
Test for standard data. [1]
Test for extreme data [1]
Test for invalid/abnormal data [1]
Error messages [1]
(ii) Evaluation of the system [3]
Achievements [1]
Weaknesses/Limitations [1]
Opportunities for future developments [1]
Section E: General expectations [5]
Depth of knowledge and understanding [1]
Degree of originality [1]
Ease of use (user documentation) [1]
Quality [Defined sections, page number and contents) [2]

(FOR EXAM

You might also like