UNIT 1 COMPUTER SCIENCE

CRITERIA FOR MARKING INTERNAL ASSESSMENT PROJECT

The project will be graded out of a total of 60 marks and marks will be allocated to each task
as outlined below.

1. Identification of Specification [4]

• Complete and accurate description of the problem INCLUDING the background of

the problem, the reasons for creating this program, the user of the program,
In bullet point format, add the following:
• All the functional requirements (the proposed functions) of the system, and
• All the nonfunctional requirements.

2. Design [21]

• Algorithms expressed as flow charts or pseudocode (6)

- pseudocode is logical, easy to follow and is an accurate description of a solution
using the appropriate symbols or algorithmicstructures

• Use of files (4)

- selection and justification of file structure (sequential and random-access
files)
- state the sources of data and types of outputs
- state the uses of outputs (Draw a table showing the name of the file,
the inputs, and outputs from the file)

• Use of appropriate data structures (6)

- the data structure chosen was appropriate for the problem definition

• Demonstration of structured programming concepts (5)

- design demonstrates excellent use of structured programming concepts
3. Coding of Program [19]

• Structured decomposition using functions (6)

- Overall, program comprises functions as independent units

• Demonstration of the concept of structured programming (3)

- Evidence of looping structures
- Evidence of conditional statements
- Evidence of other structures (for example assignment, input, output)

• Appropriate programming style and documentation (4)

- Appropriate document in significant areas
- Standard indentation of code

• Evidence that code matches algorithm (4)

- Code matches sequencing of algorithm

• Evidence of file manipulation (2)

- Correct file types used, for example, text file (.txt)
- File used appropriately
4. Testing and presentation [11]

• Test Plan - Test Plan with exhaustive data set (3)

• Test Results (5)

- Normal input giving correct results
- Extreme input giving correct results or appropriate error message
- Erroneous input (for example, text when number required) giving
appropriate error message
- Incomplete input giving appropriate message

• Overall presentation (3)

- Appropriate cover page
- Use of table of contents
- Sequencing in document easy to follow

5. Documentation [5]

• Technical Documentation (3)

- presents a system architecture that clearly shows inputs, outputs,
processing, and storage points.

• User Documentation (2)

- communicates information in a logical way using correct grammar and
appropriate jargon ALL of the time.

TOTAL 60 MARKS