8/6/2019 Critical Analysis of a Level Syllabus

http://slidepdf.com/reader/full/critical-analysis-of-a-level-syllabus 1/3

Critical Analysis of A Level Syllabus

Paper 4:

Topic Relevance Weaknesses Strengths

4.  4.1 Report (3 marks)

A report presenting the Coursework as specified

in 4.2 to 4.6.

Students are allowed to

demonstrate their word

processing skills acquired in

lower secondary

More details could have

been provided concerning

the layout of report and list

of word processing features

to be used

4.2 Definition, investigation and analysis (11marks)

Explanation of the problem to be solved, the

users requirements and how they were

obtained.

There should be a clear statement of 

requirements, agreed with the prospective

client.

Students gain exposure to:Problem Solving & Decision

making activities

4.3 Design (12 marks)Detailed system design including data structures,

input-output format and processes involved, and

testing

required. There should be a clear design

specification.

Application of knowledgeacquired in Paper 1 & Paper

2 Database Design/ HCI

4.4 Software development, programming,

testing and installation (18 marks)

A software solution that includes someprogramming code using a stand-alone

programming language

or program embedded within application

software (e.g. VBA used as the front end of a

database solution

written by the candidate). A comprehensive test

plan is developed from the design, which should

Help student develop

programming skills

8/6/2019 Critical Analysis of a Level Syllabus

http://slidepdf.com/reader/full/critical-analysis-of-a-level-syllabus 2/3

show

that the system works to the satisfaction of the

client by providing comprehensive functionaltesting,

both alpha and beta, of the solution. The test

plan should be clearly cross-referenced to the

agreed set of 

objectives to provide evidence that the system

has been tested during development and by the

client.

4.5 Documentation (10 marks)The Systems Maintenance Manual should

include an explanation of the structure of the

solution. All

the necessary information about the system that

would allow someone else to maintain and

develop it

should be included, for example, back up

procedures/cycles, annotated code/modules,data structures

used, and must include an element of adaptive

maintenance in order to provide some future-

proofing of 

the solution.

The User Manual should include step-by-step

instructions for operating all aspects of the

system,including a means of dealing with any errors that

may occur. As well as the manual, user

documentation

should include appropriate Help and messages

within the software solution, and be present in

the form

of a hypertext document.

8/6/2019 Critical Analysis of a Level Syllabus

http://slidepdf.com/reader/full/critical-analysis-of-a-level-syllabus 3/3

4.6 Evaluation (6 marks)

Discussion of the degree of success in meeting

the original objectives as specified in therequirements

specification, ease of the use of the package,

acceptability to the client (including where

possible a letter

of acceptance from the client and reference to

client and user testing results).