1

ZIMBABWE SCHOOL EXAMINATIONS COUNCIL

CONTINUOUS ASSESSMENT TASK

COMPUTER SCIENCE 4021

FORM 3 PROJECT GUIDE 2017

______________________________________________________________________________
This project guide consists of 10 printed pages.
Copyright: Zimbabwe School Examinations Council, CA/2017.
ZIMSEC CA/2017 [Turn over
 2

SUBJECT : COMPUTER SCIENCE (4021)

LEVEL : FORM 3
TASK TYPE : PROJECT

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.

4021/CA/2017/PROJECT
 3

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

4021/CA/2017/PROJECT
[Turn over
 4

 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

4021/CA/2017/PROJECT
 5

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.

4021/CA/2017/PROJECT
[Turn over
 6

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]

4021/CA/2017/PROJECT
 7

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]
4021/CA/2017/PROJECT
 8

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]

Total: 50

4021/CA/2017/PROJECT

Computer Science (4021) Project
Achievement Standards
Dimensions/ Excellent
Criteria 40 - 50
Section A: Selection,
At least 4 points defining
Investigation and the problem
Analysis [22 marks]
At least 2 relevant research
instruments
Input, output, process,
storage of existing system
At least 2 weaknesses and
strengths of existing
system
At least one
software/hardware
requirement
At least 2 aims and
objectives
Evidence of at least 2
research instruments
Section B: Design
At least 2 alternative
[11 marks] methods
Data capture forms and
screen layouts
Specifications of at least 2
required outputs
Name, test data and
outcome of test plan
Section C: System At least2 Pseudocodes of
Development [7 any major modules.
marks] At least 1 flow charts for
any major modules.
Code/Program listing
Installation, running and
exiting the system
documents
9
Good Satisfactory Unsatisfactory
30 -39 25 - 29 0 - 24
4 points defining the 3 points defining the 2 points defining
problem problem the problem
2 relevant research 2 relevant research 1 relevant research
instruments instruments instruments
3 of input, output, 2 of input, output, process 2 of input, output,
process or storage of or storage of existing system process or storage
existing system of existing system
1 weakness and 1 strength of
2 weaknesses and 2 existing system 1 weaknesses or
strengths of existing strength of existing
1 software and 1 hardware
system system
requirement
1 software and 1 1 software or
1 aim and 1 objective
hardware requirement hardware
Evidence of 1 research requirement
2 aims and objectives
instrument
1 aim and 1
Evidence of 2 research
objective
instruments
Evidence of 1
research instrument
2 alternative methods 1 alternative method 1 or no alternative
method
Data capture forms and Data capture forms and
screen layouts screen layouts Data capture forms
and screen layouts
Specifications of 2 Specifications of 1 required
required outputs output Specifications of 1
required output
Any 2 of name, test data Any 2 of name, test data and
and outcome of test plan outcome of test plan Any 1 of name, test
data and outcome
of test plan
2 Pseudocodes of any 2 Pseudocodes of any major 1 Pseudocodes of
major modules module any major module
1 flow chart for any 1 flow chart for any major 1 flow chart for any
major module module major module
Code/Program listing Code/Program listing Code/Program
Installation, running and Any 2 of installation, listing
exiting the system running and exiting the Any 1 of
documents system documents installation, running
and exiting the
system documents
 10

Section D: Testing User testing : at least 2 of User testing : 2 of 1 of Test for standard data No test for standard
and evaluation Test for standard data Test for standard data Test for extreme data data
Test for extreme data Test for extreme data Test for invalid or abnormal Test for extreme
[5 marks] Test for invalid or Test for invalid or data data
abnormal data abnormal data Error messages Test for invalid or
Error messages Error messages abnormal data
All of achievements, 2 of achievements, Error messages
All or more of weaknesses or limitations,
weaknesses or
achievements, weaknesses limitations, opportunities for future One of
or limitations, opportunities for future developments of the new achievements,
opportunities for future developments of the new system weaknesses or
developments of the new system limitations,
system opportunities for
future
developments of
the new system

Section E: General Ease of use (user Ease of use (user Ease of use (user Ease of use (user
expectations documentation) documentation) documentation) documentation)

[5 marks] Defined at least all Defined sections, page Defined 2 of sections, page Defined 1 of
sections, page number and number and contents number and contents sections, page
contents number and
contents

4021/CA/2017/PROJECT