9691 - paper 4

9691/04‘A’ L l C i P j‘A’ Level Computing ProjectNicosia, Cyprus, 26th January 2008

© Dr. Antonis Kaniclides 2008

Moderation of Project WorkModeration of Project Work

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

Objective:jStandardisation of Marks from Schools and Institutes

External Moderation by CIE

22

Internal ModerationInternal Moderation

Ensure students submit their own workTeachers/Supervisors Mark Projectsp j

Candidate Record CardProject Marking Details FormCoursework Assessment Summary Form

Moderation by the British CouncilSchools/Institutes with up to 10 studentsSchools/Submitting more than 10 projects

33

9691/049691/04 CIE A-Level Computing Computing Project

9691/04 Computing Project Outline

Definition, Investigation & Analysis (11)Design (11)Software Development Testing and I l t ti (18)Implementation (18)Documentation (12)Evaluation (8)Evaluation (8)

55

9691/04 Chapter 1

D fi iti I ti tiDefinition, Investigation and Analysisand Analysis

66

9691/04 Definition, Investigation & Analysis

IntroductionBrief description of the organization involved

Operation of the current systemD i ti f th t th d dDescription of the current methods used, Origin and form of data

77


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

Interview with userQuestionnaireObservationAnalysis of Documents used in the current systemAnalysis of Documents used in the current system

Preparation – Identify information that needs to be collectedFact finding evidence – Present evidence of carrying out the fact finding methods

88


A l iAnalysisDescription of current system – use use flowchartsflowcharts or other appropriate or other appropriate toolstoolsId tif P bl i th i ti tIdentify Problems in the existing systemUser requirements – include inputinput, storage,storage, processingprocessing, outputoutput and hardwarehardware and softwaresoftware requirementsrequirements and be signed by the user

Alt ti l tiAlternative solutionsDiscuss outlines and evaluate against each other – (Include advantagesadvantages and disadvantagesdisadvantages)

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

99

9691/04 Chapter 2

D iDesign

1010

9691/04 Design Nature of the solution 1 of 2

Introduction - This should include the Aims and Objectives of this phaseE R modeling Clearly identify entities involved in theE-R modeling - Clearly identify entities involved in the system and their relationshipsTable structure - Describe the data structure of each entity identifying the following attributes e.g.

Field Name Type Size Description Validation Examplee.g e.g. Autonumber e.g. e.g. The key identifier of e.g. e.g. 12345gCustomerID

g(Text currency number etc)

g5

g yeach customer This is a unique number

gPresence check

g

1111

9691/04 Design Nature of the solution 2 of 2

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)

P D i U i D t Fl Di dProcess Design - Using Data Flow Diagrams and Flowcharts describe the processes carried out by the system – detailed textual descriptions of each diagram are

1212needed

9691/04 Design Intended Benefits &

Limits of the scope of the solution

Intended BenefitsComparison of merits of the new system in relation to the old systemold system

Limits of the scope of the SolutionpSome discussion of limitations e.g. time, budget, available hardware, computer literacy etc.Estimation of file size required for the implementedEstimation of file size required for the implemented system

1313

9691/04 Chapter 3

S ft D l tSoftware Development,Testing and ImplementationTesting and Implementation

1414

9691/04 Software Development Testing andSoftware Development ,Testing and Implementation

DevelopmentDevelopmentParagraph to refer Development evidence as part of the Technical manual

Test PlanTest PlanTest plan that includes expected outcomes and cross-references to the appropriate page of the testing e.g.Test Test Test Test Data Expected Actual Evidence onTest 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

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

1515

intended functionality


Clear Implementation plan that includes theClear Implementation plan that includes the following:

System Changeover detailsy gUser Training requiredUser Testing and User Acceptance

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

1616

implementation strategy


Appropriateness of structure and exploitation ofAppropriateness of structure and exploitation of available facilities

Discussion of the suitability of the hardware and software d f th tused for the system

Recognition and brief discussion of problems encounteredActions taken to overcome the problemsp

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 onthe computer. Printer drivers werechecked

Problem solved.

1717

9691/04 Chapter 4

T h i lTechnical DocumentationDocumentation

1818

9691/04 Technical Documentation

NoteMost of the work will have been produced as a by-product of the design and development work earlier inproduct of the design and development work earlier inthe projectHowever a technical guide is a stand alone documentprod ced to facilitate eas maintenance and pgrade ofproduced to facilitate easy maintenance and upgrade ofa system. Therefore its contents should be fullyannotated and well presented in this section

1919

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 usedDatabase modeling and organization (in the form of an E-R diagram)Data DictionaryDetailed flowcharts of the system functionalityNavigation paths in the systemAnnotated program listings (where appropriate)p g g ( pp p )Details of algorithms and formulae used. Screens of the system including MenusReportsp

2020

9691/04 Chapter 5

UUser DocumentationDocumentation

2121

9691/04 User Documentation

The user manual should provide guidance to the users for all the operations that they will beusers 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 reportseparate booklet or an Appendix to the report

2222


The user manual should contain sections thatThe user manual should contain sections that describe the following:

Installation of the systemD i i f h hDescription of how to start the systemMention of the relationship between Access and the data held in the systemSecurity of access to dataSecurity of access to dataDescription of how to perform each function (eg. How to add a new customer) including the Input format and screen displays in each caseOn-Screen help examplesOn-Screen help examplesPrint OptionsBack up ProceduresGuide to common errors that may occurGuide to common errors that may occur

2323


Additionally the user guide should have an indexand if necessary a glossary of the terms usedy g y

2424

9691/04 Chapter 6

E l tiEvaluation

2525

9691/04 Evaluation

Success in meeting the original ObjectivesEvaluate the effectiveness of the completed system

Original objectives should be matched to achievements (taking into account any limitations) giving evidence f th j t t t thifrom the project to support this

User Evaluation of the system should be included eitherIn the form of a questionnaire orDirect user evaluation using a set of typical data thatwould arise in the normal use of the systemwould arise in the normal use of the system

2626

9691/04 Evaluation

U ’ t th tUser’s response to the systemLetter signed from the user to say that a user friendly system that meets the requirements have been metsystem that meets the requirements have been met and that there are no known faults with the system

Desirable extensionsIdentify the good and bad points of the final systemHighlight any limitations and necessary extensionsIndicate how extensions could be carried out

2727