9691 - Paper 4 (Checking Resource) (2) (3)

9691/04‘A’ Level Computing Project26th January 2008

2

Moderation of Project Work

Needed for9691/04 – Practical Programming Project9691/04 – Computing Project

Objective:Standardisation of Marks from Schools and

Institutes External Moderation by CIE

3

Internal Moderation

Ensure students submit their own work Teachers/Supervisors Mark Projects

Candidate Record Card Project Marking Details Form Coursework Assessment Summary Form

Moderation by the British Council Schools/Institutes with up to 10 students Schools/Submitting more than 10 projects

9691/04 CIE A-Level Computing Computing Project

9691/04 Computing Project Outline

Definition, Investigation & Analysis (11)

Design(11)

Software Development Testing and Implementation

(18) Documentation

(12) Evaluation

(8)

5

9691/04 Chapter 1

Definition, Investigation and Analysis

6

9691/04 Definition, Investigation & Analysis

Introduction Brief description of the organization involved

Operation of the current system Description of the current methods used,

Origin and form of data

7


Fact finding (Investigation) Selection (and justification) of methods

Interview with userQuestionnaireObservationAnalysis of Documents used in the current system

Preparation – Identify information that needs to be collected

Fact finding evidence – Present evidence of carrying out the fact finding methods

8


Analysis Description of current system – use flowcharts or other appropriate

tools Identify Problems in the existing system User requirements – include input, storage, processing, output and

hardware and software requirements and be signed by the userAlternative solutions

Discuss outlines and evaluate against each other – (Include advantages and disadvantages)

• Manual system – possible enhancements to current system• Computerised solution (Off-the shelf)• Computerised solution (Custom-made database).

9

9691/04 Chapter 2

Design

10

9691/04 Design

11

Introduction - This should include the Aims and Objectives of this phase

E-R modeling - Clearly identify entities involved in the system and their relationships

Table structure - Describe the data structure of each entity identifying the following attributes e.g.

Field Name Type Size Description Validation Examplee.g CustomerID

e.g. Autonumber (Text currency number etc)

e.g. 5

e.g. The key identifier of each customer This is a unique number

e.g. Presence check

e.g. 12345

Nature of the solution 1 of 2

9691/04 Design

12

Input Design - Design and annotate the input screens to the system (Identify Purpose, Link to table(s), Fields, Annotation of elements)

Ouput Design - Design and Annotate the screens used for output as well as the reports generated by the system. (Identify Purpose, Link to table(s), Fields used, Criteria, Sorting, Grouping, Annotation of elements)

Process Design - Using Data Flow Diagrams and Flowcharts describe the processes carried out by the system – detailed textual descriptions of each diagram are needed

Nature of the solution 2 of 2

Intended Benefits Comparison of merits of the new system in relation to the

old system Limits of the scope of the Solution

Some discussion of limitations e.g. time, budget, available hardware, computer literacy etc.

Estimation of file size required for the implemented system

13

9691/04 Design Intended Benefits &

Limits of the scope of the solution

9691/04 Chapter 3

Software Development,Testing and Implementation

14

9691/04 Software Development ,Testing and Implementation

15

DevelopmentParagraph to refer Development evidence as part of the Technical manual

Test PlanTest plan that includes expected outcomes and cross-references to the appropriate page of the testing e.g.

Testing Evidence This should satisfy that the system successfully performs the intended functionality

Test no.

Test Objective

Test Method

Test Data Used

Expected Outcome

Actual Outcome

Evidence on page…

1 CustomerID should be automatically generated

Click on Add Button

n/a Next ID should be generated

Test Successful 95


16

Clear Implementation plan that includes the following: System Changeover details User Training required User Testing and User Acceptance

Evidence in the form of a written statement signed by the user that they have seen the product in operation and agree with the implementation strategy


17

Appropriateness of structure and exploitation of available facilities Discussion of the suitability of the hardware and software

used for the system Recognition and brief discussion of problems encountered Actions taken to overcome the problems

A log of problems should be included in a table – At least 8-10 problems should be mentionedDate Problem Description Action taken Comments

Creation of Relationship in Access between customer and product

Primary key not the same type! Had to change the type of the primary key.

Problem solved!

Reports not printing Printer Cable checked and repluged on the computer. Printer drivers were checked

Problem solved.

9691/04 Chapter 4

Technical Documentation

18

9691/04 Technical Documentation

Note Most of the work will have been produced as a by-

product of the design and development work earlier in the project

However a technical guide is a stand alone document produced to facilitate easy maintenance and upgrade of a system. Therefore its contents should be fully annotated and well presented in this section

19

9691/04 Technical Documentation

The technical manual should include the following: Specification of the Software and Hardware on which the system can

be implemented. Record, file and data structures used Database modeling and organization (in the form of an E-R diagram) Data Dictionary Detailed flowcharts of the system functionality Navigation paths in the system Annotated program listings (where appropriate) Details of algorithms and formulae used. Screens of the system including Menus Reports

20

9691/04 Chapter 5

User Documentation

21

9691/04 User Documentation

The user manual should provide guidance to the users for all the operations that they will be required to perform using the system

This should be in a user-friendly manner (include screenshots!) and could be produced as a separate booklet or an Appendix to the report

22


The user manual should contain sections that describe the following: Installation of the system Description of how to start the system Mention of the relationship between Access and the data held in the

system Security of Access to data Description of how to perform each function (eg. How to add a new

customer) including the Input format and screen displays in each case On-Screen help examples Print Options Back up Procedures Guide to common errors that may occur

23


Additionally the user guide should have an index and if necessary a glossary of the terms used

24

9691/04 Chapter 6

Evaluation

25

9691/04 Evaluation

Success in meeting the original Objectives Evaluate the effectiveness of the completed system

Original objectives should be matched to achievements (taking into account any limitations) giving evidence from the project to support this

User Evaluation of the system should be included either In the form of a questionnaire or Direct user evaluation using a set of typical data that

would arise in the normal use of the system

26

9691/04 Evaluation

User’s response to the system Letter signed from the user to say that a user friendly

system that meets the requirements have been met and that there are no known faults with the system

Desirable extensions Identify the good and bad points of the final system Highlight any limitations and necessary extensions Indicate how extensions could be carried out

27