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
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 –when the problem started
Population Size –justify
Problem definition
Accept any meaningful variations eg purpose of the system

[Any 4 marking points] 1mark each

ii. Investigation of the current system [4] (explain the how part eg questionnaire for
receptionist)
explain how the research is going to be used in the project and link with the topic.
Research Instruments [2 marks per instrument] –state any two (1 mark stating 1mark qualification)
o Questionnaires, Interview guides, Record Inspection, observation [4] (indicate to who---)
iii. Broad description of existing system [4] (simply explain on tis part , no graphs or diagrams)
Clearly explain the input, output, process, storage of the existing system
o Input [1] eg name,surname(fields)
o Output [1] eg receipt,reports,(filled data of part 1)
o Process [1] eg sorting searching,manipulation
o storage [1] files,flash,CDs
accept even a flow chart on input and output

iv. Evaluation of existing system [2] (reject these…cheap,fast,efficient…..without explaining

further)accept one which is explained fully

weakness 1mark

strengths

v. Requirements specification [2] award zero if one stated without explaining

Software requirements [1]

Hardware requirements [1]

vi. Aims and objectives [4]
Aims [Any two aim] [2]
(effectiveness,determining,appreciate,understand,improve,develop,reduce(what u intend to do)
2 Objectives [1 mark per 1 objective] [2] all verbs

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] (link with part 11)

List alternative solutions including the one u are going to use as a solution in yr
project)
(i) Consideration of alternative methods [2]
At least 2 methods eg off the shelf,tailor made
(ii) Justification of method of solution [2] justify the one you have listed above (any one)

(iii) Input design [2] accept a blank input form without any information
Data capture forms [1] use word processing package,spreadsheet,no database(1mark data
space,1mark labels)
Design input form but any form created in Word -2marks,any created in vb or database -1mark)
Screen layouts [1 ]

(iv) Output design [2]

Specification of required output [2] use Ms Word again or spreadsheet
Accept any form with filled data in grids
Award any thing designed eg receipt or anything with filled data)

[max 2]
(v) Test plan [3]
Name and describe a test plan including test data and expected outcome in your description (eg
aipha ,intergration ,functional,acceptance testing,whitebox,blackbox,beta)
Link to the system
o name [1]
o description [1]
o outcome [1] (just describe the outcome)
Section C: System Development [7]
(i) Technical documentation [4]
At least2 Pseudocodes of any major modules. [2] (reject log in and exit modules and accept these –
input module,output module,process,amend,manipulate,search)one mark each
At least 1 flow charts for any major modules. [1]
Code/Program listing [1] sample code accept any including log in and exit9dont allow password
module
(ii) User documentation [3] state steps only and even screenshots)
Steps are more important than processes
Installation [1] how do….
Running the system [1] how do….
Exiting the system [1] how do……

4021/CA/2017/PROJECT 8
Section D: Testing and evaluation [5] screen shots needed
(i) User testing (any two) [2] samle runs
Test for standard data. [1]
Test for extreme data [1]
Test for invalid/abnormal data [1] error messages
Sample run –starndard and extreme data
Error messages [1]

(ii) Evaluation of the system [3]

Achievements [1] refers to objectives of solution
Weaknesses/Limitations [1] refers to objectives not met ..that system can not do
Opportunities for future developments [1] weacknesses

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 9
Computer Science (4021) Project
Achievement Standards
Dimensions/ Excellent Good Satisfactory Unsatisfactory
Criteria 40 - 50 30 -39 25 - 29 0 - 24
Section A: Selection, At least 4 points 4 points defining the 3 points defining the 2 points defining the
Investigation and defining the problem problem problem problem
Analysis [22 marks] At least 2 relevant 2 relevant research 2 relevant research 1 relevant research
research instruments instruments instruments instruments
Input, output, process, 3 of input, output, 2 of input, output, 2 of input, output,
storage of existing process or storage of process or storage of process or storage of
system existing system existing system existing system
At least 2 weaknesses 2 weaknesses and 2 1 weakness and 1 1 weaknesses or
and strengths of strengths of existing strength of existing strength of existing
existing system system system system
At least one 1 software and 1 1 software and 1 1 software or hardware
software/hardware hardware requirement hardware requirement requirement
requirement 2 aims and objectives 1 aim and 1 objective 1 aim and 1 objective
At least 2 aims and Evidence of 2 research Evidence of 1 research Evidence of 1 research
objectives instruments instrument instrument
Evidence of at least 2
 research instruments

Section B: Design [11 At least 2 alternative 2 alternative methods 1 alternative method 1 or no alternative
marks] methods Data capture forms and Data capture forms and method
Data capture forms and screen layouts screen layouts Data capture forms and
screen layouts Specifications of 2 Specifications of 1 screen layouts
Specifications of at required outputs required output Specifications of 1
least 2 required outputs Any 2 of name, test Any 2 of name, test required output
Name, test data and data and outcome of data and outcome of Any 1 of name, test
outcome of test plan test plan test plan data and outcome of
test plan
Section C: System At least2 Pseudocodes 2 Pseudocodes of any 2 Pseudocodes of any 1 Pseudocodes of any
Development [7 marks] of any major modules. major modules major module major module
At least 1 flow charts 1 flow chart for any 1 flow chart for any 1 flow chart for any
for any major modules. major module major module major module
Code/Program listing Code/Program listing Code/Program listing Code/Program listing
Installation, running Installation, running Any 2 of installation, Any 1 of installation,
and exiting the system and exiting the system running and exiting the running and exiting the
documents documents system documents system documents