GCE Advanced Level Computing Scheme of Work www
Contents
1. annotated code try and use features available in the language chosen e g naming conventions good layout and use of commenting instructions for modification anything else that will help to maintain or update the system For a package operating environment hardware software algorithm descriptions for each section of the solution purpose and inter relationship of modules within the system data structures annotated listings of macros annotated design screens showing details of package generated forms reports queries buttons cross tabulations etc instructions for modification anything else that will help to maintain or update the system Documentation for both a programmed solution and a package based solution should be discussed Some students may be using both bear this in mind during the discussion Technical Manual e annotated code macros and or annotated design screen views of other elements e g tables forms reports QBE grids etc e data dictionary including all elements developed e instructions for modification e operating environment hardware software Remind the students that the technical guide is a stand alone document They should think about the purpose of the document when they are writing it which is to make it easy for someone who does not know the system to maintain and upgrade the system UCLES 2006 8 Session Plan 122 Documentation User Guide A2. e backup procedures e glossary of terms used User Manual includes e step by step instructions for operating all aspects of the system e how to deal with any errors that may occur e appropriate Help and messages within the software solution or in the form of a hypertext document backup procedures glossary of terms used UCLES 2006 9 Session Plan 123 Design Assessment Performance Criteria Classroom Ideas MS MPC Objectives e 42 4 2 1 e design and document Input Output 16 1 9 1 Output Design 1 9 2 4 2 2 1 9 3 Input Design 1 2 2 21 2 1 3 17 1 10 1 4 2 3 e design data structures necessary to 20 2 1 2 Data Structures Model solve the inefficiencies problems indicated in the requirements 14 1 7 5 specification 1 7 6 e include full documentation of the 22 2 1 4 data structures 105 3 4 4 4 2 4 110 3 6 1 Process Model 3 6 2 e design and document an algorithm pseudo code top down diagram or other form of process model 106 3 4 4 Classroom Exercises Notes Detailed models of the proposed interface discuss these with the third party user before implementation and show any changes made Include e report layouts e screen displays e other forms of output for example charts sound animation e data capture forms these could be online e screen layouts Data structures that solve the inefficiencies identified in the requirements specificat
3. 3 8 1 current data structures 2 1 4 e analyse the data and processes For each process work out the data required for input and describe the 1 4 2 way that it is out put 4 1 5 e specify inefficiencies and problems ___ Identify problems apparent from discussions with the inefficiencies with current user and the analysis work carried out system Specif a 6 t e derive the user and information 14 1 7 6 PEGI negqurements requirements of the system e specify the required hardware and 1 ue A reasons for choice 2 121 e specify the required software and l 11 1 5 2 reasons for choice 1 5 3 e develop and document a clear 15 1 8 1 requirement specification 182 1 8 3 17 1 10 2 Resources e examples of good and poor problem definitions e revision of different methods of fact finding e revision of different methods of system documentation UCLES 2006 Classroom Exercises Notes Give the students a number of prepared problem definitions of varying quality and use these to discuss the characteristics of a good problem definition The students set out their problem definition and word process it These problem definitions need to be checked for suitability by the teacher before the investigation and analysis proceeds 4 1 1 Review the different methods of fact finding and why they are used e questionnaires e observation e structured interviews e also include a document search Stress the importance of using these with
4. planning how the software solution evolves for its implementation e produce detailed output from the testing cross referencing as appropriate to the test plan Classroom Exercises Notes Review testing look at Session Plans 25 and 26 the development of a test strategy and the use of test plans and test data Provide the students with an outline for a test plan to ensure all elements are fully tested and modifications are recorded Test plans are often best set out on tabular form clearly cross referenced to annotated output Remedial Action Actual results Test Purpose Data Expected No Results Set students homework to develop one routine and the associated test plan Use classroom discussion of the test plans to ensure that all types of testing are included and any modifications recorded Allow students to test and modify this routine Set up peer testing of the finished routines to simulate user testing Encourage students to fully justify the choice of data Explain clearly the difference between valid and invalid data and demonstrate how extreme data can be either valid or invalid Relate your discussion to normal erroneous and extreme data Make sure the students can answer the question If the system fails when does it fail UCLES 2006 11 Session Plan 125 Software Development Further Testing including User Testing Asses
5. e obtained This may take the form of a recorded interview with the candidate e atthe software development testing and implementation stages where the user is involved in prototyping e atthe evaluation stage where the user is involved in checking that the system is completed as specified and leading on from this is then willing to write a letter of acceptance of the system including any criticisms of it In this way candidates can be encouraged to look beyond school or college life into the businesses and companies in the community of the surrounding area The emphasis is on analysing an existing system and producing a computer based solution to fit the needs of the user Projects should be chosen to demonstrate the integrative aspects of the work and should avoid needless repetition of the demonstration of a given skill Each candidate must submit a report on their piece of work supported by evidence of software development and testing The solution may be implemented using one or more of the following a programming language pre written modules or toolkits applications software programmable packages The teacher marks the projects according to the guidance on marking projects provided in the syllabus by CIE after which moderation takes place according to CIE procedures Recommended Prior Knowledge Candidates should have studied Paper One Computer Systems Communications and Software and Paper Two Structured Practica
6. ep a project diary showing any major decisions made Introduce the idea of word processing their report as the project develops Provide an outline of the report structure perhaps using a template Stress the use of word processing features to provide a professional report including the following ts NOOR WN Title and contents page clear and logical organisation set out in sections continuous page numbering information presented in continuous prose good use of grammar punctuation and spelling use of a clear font style and size e g Times New Roman 10 pt or 12 pt use of appropriate techniques e g headers and footers consistent styles for headings use of tables etc footers should contain the candidate s name and page number inclusion of a bibliography UCLES 2006 5 Session Plan 120 Definition Investigation and Analysis Assessment Performance Criteria Classroom Ideas MS MPC Objectives e 4 1 Ask the students to bring in their project 13 1 7 1 ideas and discuss with individuals the following 1 7 3 4 1 1 e define the nature of the problem to be Define a problem solved 41 2 e identify methods by which to Investigate the current investigate the problem system e record information data and gather 4 1 3 sample documents currently used Record findings this could be set as a homework exercise 113 1 7 4 4 1 4 1 7 5 Analyse findings e identify the current processes and
7. i UNIVERSITY of CAMBRIDGE SY International Examinations GCE Advanced Level Computing Scheme of Work Paper 4 Computing Project Introduction The project is a substantial piece of work requiring analysis and design over an extended period of time which is organised evaluated and presented in a report Candidates choose in conjunction with their teacher a well defined user driven problem of an appropriate size which enables them to demonstrate their skills in Analysis Design Software Development Testing Implementation Documentation and Evaluation Guidance on Selecting Projects The selection of the problem for which a computerised system is to be designed and implemented is extremely important It should be chosen by the candidate in consultation with the teacher and should always involve a user ideally a third party user It is important to stress that the candidate should endeavour to produce a system which is non trivial and which will solve a given problem sensibly within the constraints of resources available to the candidate Since the computing project seeks to assess the systems analysis section of the specification in a practical manner candidates should not produce a system from their own limited knowledge of the requirements of the system The third party user has to be someone who is willing to be involved in the project e inthe analysis of the problem where the user s requirements ar
8. ion Discuss e normalisation e E R models Include a process model and processing tasks discussing where appropriate e JSP e Algorithms Discuss how to identify benefits and limitations of the proposed system Show students how to estimate the size of files required Emphasise the importance of uncluttered screens and clear instructions Ensure that students address the issue of data validation if necessary Allow the students enough time to develop their designs The design should include details of all aspects of the system for example data capture forms UCLES 2006 10 Session Plan 124 Software Development Testing and Implementation Assessment Performance Criteria Classroom Ideas MS MPC Objectives e 43 4 3 1 e implement the proposed process model 108 3 5 2 Software development using a software package and or 3 1 3 1 programming language 1 3 2 24 2 2 2 e develop the data structures of the design 23 2 2 1 using the appropriate features of a software package and or programming language e develop inputs outputs using the features of a software package and or a programming language 4 3 2 Test strategy plan e identify develop and document a test 6 1 3 4 strategy for the software solution 14 ee 25 231 4 3 3 e select suitable test data to carry out the 2 3 2 Test data test strategy 26 2 4 1 4 3 4 Testing a software test the software solution illustrating solution and
9. l Tasks UCLES 2006 2 Tutor Preparation Required to Start Paper 4 Decide on the programming languages and or packages to be used ensuring that candidates can fulfill all the syllabus requirements with the selected language or package Ifa programming language is chosen then it could be the same as used for Paper One ensure that the students have access to a word processing package for report writing install the software the students will need so that it is accessible to all students provide instructions showing what the students have to do provide an outline of the project requirements and the marks awarded for each section prepare a list of suitable project ideas prepare a list of suitable types of end users prepare a bank of project reports for students to study Important Note Some centres may wish to deliver elements of this module alongside Paper Three Systems Software Mechanisms Machine Architecture Database Theory Programming Paradigms and Integrated Information Systems To help centres that wish to use this approach the relevant session plans and performance criteria for the work on Papers One Two and Three are mapped for each element listed in Paper Four UCLES 2006 3 Scheme of Work The classroom exercises are designed to help the student through the stages of project development from choosing a project to the final evaluation They should be interspersed with project development sessions where the st
10. on of limitations extensions needed and how they could be carried out emphasise to the students the need for a user friendly solution it is important that the user is actively involved in the evaluation Discuss how to obtain feedback from the user For example use questionnaires or interviews UCLES 2006 13
11. ptions Identify and document any library elements e g general input routines calculating interest payments etc Students should then use this information to set out a reasoned rationale for the system requirements including the following e hardware and reasons for choice e software and reasons for choice e user requirements broken down into specific and measurable objectives 4 1 6 Stress the importance of explaining the nature of the organisation and the methods currently in use The report should include evidence of a high degree of user involvement with detailed recording of the user requirements Alternative approaches to the problem should be fully explained This session may take place over a number of weeks as the students develop their project ideas UCLES 2006 7 Session Plan 121 Documentation Technical Manual Assessment Performance Classroom Ideas MS MPC Objectives Criteria e 44 4 4 1 e Development of a detailed technical 14 1 7 6 manual 28 2 4 3 Classroom Exercises Notes Discuss the contents of technical manuals for given solutions Encourage students to develop these alongside the project implementation The contents should include at a minimum For a program operating environment hardware software data structures variables defined by name type and function clear definition and identification of purpose of subroutines and functions
12. roduce evidence of user testing Their evidence could include user comments photographs screenshots interview data UCLES 2006 12 Session Plan 126 Evaluation Assessment Performance Criteria Classroom Ideas MS MPC Objectives e 45 4 5 1 e evaluate the final system against the 14 1 7 6 Evaluate results against criteria described in the 114 3 8 4 the requirement specification 4 5 2 Evaluate user testing 4 5 3 Identify the good and bad points of the final system requirements specification evaluate the users responses to testing the system identify the good and bad points of the final system highlighting any limitations and necessary extensions to the system indicating how the extensions could be carried out Classroom Exercises Notes Provide an outline of the evaluation required and discuss how the students should develop it to match their solution The outline should include 1 Comparison between the requirements 1 look at each objective separately specification and system developed each criterion should be considered in the following way was it met if yes how was it met if not why not and what limitations does this bring to the system Evaluation of user testing with typical data feedback from user changes made as a result of this feedback Use the above to summarise the good and bad points of the system identificati
13. sment Performance Criteria Classroom Ideas MS MPC Objectives e 43 4 3 5 e test the software solution with the 1 7 7 User Testing user providing documented 3 8 3 evidence that the solution works 3 7 4 e devise a strategy for its implementation Classroom Exercises Notes Re enforce and extend previous work done including Expected types of test for a test strategy white box testing black box testing alpha testing with fellow students beta testing involving the third party user acceptance testing with user testing of user documentation Ensure software development takes place alongside this test strategy 4 3 2 Discuss how to set up and document an implementation strategy and plan Include the following Hint Look at the guidance on marking projects to advise candidates on how to improve user testing user acceptance testing obtaining feedback from user installation of system user training system changeover Include e normal data e erroneous data e extreme data Include e system testing e user testing with written feedback Discuss the implementation strategy looking at the options e parallel e phased e pilot e direct Emphasise to the students that they must be able to justify their choice of strategy Keep a word processed diary of the testing and note any corrective action taken 4 3 4 Make sure that the students understand that they need to p
14. ssessment Performance Classroom Ideas MS MPC Objectives Criteria e 44 4 4 2 e development of a detailed user 27 2 4 2 User Guide manual 118 3 10 3 Classroom Exercises Notes Discuss the contents of user manuals Encourage students to develop these alongside the project implementation Hint Saving appropriate Input Output screens including error messages to illustrate the user manual as the solution is developed and tested can save a lot of time The user guide is built up as the program develops It is a good idea to begin creating the manual at this stage but students should be prepared to be flexible as the program may change as time develops The advantages of using a word processor for the task are clear here The user manual should be structured as a stand alone document with contents or index page numbers etc and should include at a minimum e step by step instructions for operating all aspects of the system including installation use screen dumps of error messages as appropriate and test the instructions with the user to ensure that they are at an appropriate level for the target audience e how to deal with any errors that may occur use screen dumps of error messages as appropriate e appropriate Help in small meaningful easy to read sections and messages within the software solution or in the form of a hypertext document again these should be developed alongside the main solution
15. their user rather than the student relying on their own perceptions and ideas Students should select appropriate methods of fact finding for their project prepare appropriate documents for recording their findings and employ them with their user Tell the students that they should be able to justify their choices Stress the importance of keeping good records at this stage including sample copies of documents used by the current system to refer to at a later stage as necessary Students should use information to try and identify the data flows data structures and the processing done by the current system Also encourage students to pinpoint inefficiencies and problems at this stage This will help them identify possible needs for the development and maintenance of the system Hint The need for further information may be identified at this stage students should contact the third party user if this is so before trying to proceed with incomplete information or guessing what is required 4 1 2 Discuss the features of good questionnaire design such as unambiguous questions and attractive presentation Review the different methods of system documentation including e structure diagrams e data flow diagrams level two will include data stores and processes e system flowcharts Students should establish the data requirements and produce a full conceptual data model from these and document any constraints and assum
16. udents develop their individual projects A suggested plan is set out in the Course Programme Session Plan 119 Introduction Assessment Classroom Ideas MS MPC Objectives Project e choosing a project 13 1 7 1 1 7 9 Requirements e stages in project development e documenting a project e planning project development 114 3 8 4 e examiners requirements Classroom Exercises Notes Introduce the project work using pre determined scenarios to introduce the idea of a third party user rather than the teacher or the student Also explain the stages at which third party involvement is required e analysis software development evaluation e e Hints on finding a third party user e find a suitable problem to solve for another person consider school college clubs and societies small businesses charities ask family friends neighbours employers teachers etc look at manual systems partially computerised systems fully computerised systems Get students to brainstorm ideas for projects and users and discuss their suitability as a group If possible have project reports from previous students available both good and bad for the students to look at NB If students cannot find a third party user of their own it is better to persuade a colleague to fulfil this role rather that the teacher attempting to be both teacher and user An overview of all stages of the project sho
17. uld be included Because it is valuable for students to be able to see an overview of the whole process Definition Investigation and Analysis e definition nature of the problem 3 e investigation and analysis 8 Design nature of solution 7 intended benefits 2 limits of the scope of the solution 2 Software development testing amp implementation development and testing 9 implementation 6 appropriateness of structure and exploitation of available facilities 3 Documentation technical documentation 6 user guide 6 Evaluation discussion of the degree of success in meeting original objectives 3 evaluate the users response 3 desirable extensions 2 These elements are taken from the marking scheme The marks available for each element are shown in brackets Resources e sample project ideas requirements for each section outline of report requirements Key MS Mapping Session MPC Mapped Performance Criteria Session Plan 119 Introduction Continued Classroom Exercises Prepare a document showing the requirements for each section and the marks awarded Use this to introduce the idea of formal time planning for their project When the students have chosen their project topic get them to draw up a Gantt chart to use as a working document in planning their project Perhaps show the students an outline template for their Gantt chart Also encourage students to ke
Download Pdf Manuals
Related Search