INFO4 Coursework Guide AQA

INFO4

Project Guide

Authors / Contributors Wendy Banks Whitby Community College and Fyling Hall School, North YorkshirePaul Armstrong Whitby Community College, North YorkshireKathryn Shaw Riverside College, CheshireAQA Background, specification, marking grids and exemplar material

Contents INTRODUCTION 5Brief 5Working together (with clients and other students) 5Using software 6Further project ideas 6Important note about malpractice 7Sections of the project 7Hints & Tips 8Deadlines 8Specification 9

Practical issues involved in the useof ICT in the digital world

A2 ICTCoursework

http://www.thestudentroom.co.uk/attachment.php?attachmentid=199703&d=1361712975#_Toc264663285 19/11/2015, 13:22Page 1 of 21

1 BACKGROUND AND INVESTIGATION (14 MARKS) 121.1 Introduction to the Organisation (2 marks) 121.2 Description of the Current System (3 marks) 121.3 Identification of Client, Users and Audience (2 marks) 121.4 A Business Case for Change (2 marks) 131.5 Investigation Techniques (3 marks) 131.6 Client Requirements (2 marks) 141.7 Terms of Reference 152 ANALYSIS AND DELIVERABLES (15 MARKS) 162.1 Statement of Scope (3 marks) 162.2 Description of the Proposed System and Deliverables (3 marks) 172.3 Documentation of Processes (3 marks) 192.4 Description of the Users of the Proposed System (3 marks) 192.5 Evaluation Criteria (3 marks) 202.6 Evidence of Checking the Findings with the Client 203 DESIGN AND PLANNING FOR IMPLEMENTATION (14 MARKS) 213.1 Alternative Design Solutions (2 marks) 213.2 Design of the Solution (3 marks) 213.3 Implementation Plan and Training Requirements (3 marks) 223.4 Testing Strategy (3 marks) 233.5 Test Plan (3 marks) 244 TESTING AND DOCUMENTATION OF THE IMPLEMENTATION (13MARKS) 254.1 Testing the Whole Solution (3 marks) 254.2 Testing with Client and Users (3 marks) 254.3 Documentation (3 marks) 264.4 Technical Documentation (2 marks) 264.5 Appropriateness of Documentation (2 marks) 275 EVALUATION (7 MARKS) 285.1 Evaluation of the Whole Solution (2 marks) 285.2 Evaluation against Client Requirements and Evaluation Criteria (2 marks) 285.3 Evaluation of Students Own Performance (3 marks) 286 PROJECT REPORT (7 MARKS) 296.1 Use of Software (3 marks) 296.2 Organisation and Use of Language (2 marks) 296.3 Diagrams and Illustrations (2 marks) 297 BIBLIOGRAPHY 308 APPENDIX 30

Introduction

Brief


This unit provides you with the opportunity to complete a substantial project involving the productionof an ICT-related system over an extended period of time. In so doing, you will enhance yourtransferable practical skills. It is important for your project to have a level of complexity and demandappropriate to the second year of an A Level. Regular involvement of the end-user is essential to thesuccess of the project. You will need to provide evidence to verify this.

The following may help to illustrate the range of possible projects that could be undertaken. Theyshow how you might be able to work on an individual or group project whilst still producing anindividual project report that has your own work clearly identified.

You may, for example, produce

a software solution such as an e-commerce or multimedia system a training system, including training materials for a client. This could, for example, be for a

course for someone working from home a user support system, such as for a user help desk in a company or school/college, or a fault

logging system a system for ensuring the security of an organisations ICT systems. An idea here would be to

formulate a policy to specify appropriate use of a company or a schools/colleges laptopcomputers and other mobile devices, or a database to record usage

a system for communication within an organisation: for example, for how schools could usetechnology to communicate with students within the school or a communal diary system

a system for evaluating new software to be purchased or for a new system to be installed,including hardware, software, communications, consumables and services

a backup and recovery system and a disaster recovery plan for an organisation a system for managing relationships with customers

Working together (with clients and other students)

It is intended that you will become involved in real situations in organisations where you can applyyour skills, knowledge and understanding of ICT to solve problems for a client. An organisation isdefined as any group of people who use ICT to achieve their aims and objectives. Examples of anorganisation include a local company, a retailer, a school or college, a charity, a club or society, or justa group of people coming together to organise an event.

It is quite acceptable for you to work in a team for the same client, if that is what is required for thework being undertaken.

The team could consist of two or more students working with one or more members from the clientorganisation. This approach is encouraged if it allows students to become involved in larger morerealistic projects where each student can work on part of a system.

Using software

The project should involve you using applications software for a variety of purposes and should alsointroduce you to the fundamentals of project management.

You will be expected to make full use of the functionality available in word processing software forthe production of the project report and, if required, to enable collaborative working.

The project should encourage you to think creatively, innovatively, analytically, logically and criticallyas you consider and suggest alternative approaches, investigate and discuss possibilities, andrecommend actions to be taken.

You will produce a project report that will be assessed internally by the school, to the criteria providedin this specification. The schools assessment will then be moderated by AQA. For this reason,although collaborative working is encouraged, it is imperative that assessors are able to identify yourown contribution, and you must produce your own project report.

Further project ideas


The following may help to illustrate the range of possible projects that could be undertaken, and howgroups of students could work together, whilst still producing an individual project report that has theirown work clearly identified. It is perfectly acceptable to produce a spreadsheet or database solution toa problem if that holds more interest for you.

Website, intranet site or extranet siteFor any organisation (or event), students could produce parts of an intranet for different departmentswithin an organisation, working collaboratively to establish house styles and consistency of endproduct, and in sharing their skills in the use of the variety of applications software needed to createthe end product.

Training materialsTraining materials could be developed for a course within the centre or for an external organisation.Materials could take a variety of formats and be created using a range of software. Individual studentscould work on one aspect or one format, whilst the whole group has to adopt consistent styles andapproaches to development. For example, training could be needed in

a new piece of software using new laptops, PDAs or other portable devices using loan items such as digital cameras or recording equipment a new security policy a backup and recovery strategy health and safety legislation or guidelines environmental policies, such as disposal of computer equipment.

Other students could perhaps develop a system for storing, cataloguing or loaning out trainingmaterials that have been created.

User support and fault loggingA group of students could each work with a different type of user, or a different department of a schoolor other organisation. Materials required might be similar in purpose, but need to be produced so as tobest suit the individual types of user, or some may have specialist needs which need supporting.Recording and storage of requests for maintenance, error reporting or fault logging could be built in.

Managing relationships with customersThis could involve a system for the collection of customer feedback via a website and a back officesystem that can collect, store and classify responses, plus a system that results can be fed into forstatistical analysis. Individual students could take on one of the elements, where collaboration wouldbe essential to ensure effective data transfer, correctness and accuracy.

Multimedia solutionsThese can be used in a variety of situations. They can be extremely large systems and frequently needto be broken down into manageable chunks. Separate students could work on parts of an overallsolution. This could include producing an interactive map, where subject specialisms or specialinterests could determine with what areas students became involved. For example, one student couldprepare and incorporate information on areas of interest for young adults, another on sporting venues,a third on flora and fauna. This could be produced for the local tourist board or town council.

Important note about malpractice

You need to be aware that teachers should inform candidates of the AQA regulations concerningmalpractice. Candidates must not

submit work which is not their own; lend work to other candidates; allow other candidates access to, or the use of, their own independently-sourced source material

(this does not mean that candidates may not lend their books to another candidate, butcandidates should be prevented from plagiarising other candidates research);

include work copied directly from books, the Internet or other sources withoutacknowledgement or attribution;

submit work typed or word-processed by a third person without acknowledgement.


These actions constitute malpractice, for which a penalty (e.g. disqualification from the examination)will be applied.

Sections of the project

The project constitutes 20% of the full A Level qualification (40% of the A2 year).The project is marked out of 70 marks. Here is the breakdown of the marks for each section of theproject

Background and Investigation (14 marks) Analysis and Deliverables (15 marks) Design and Planning for Implementation (14 marks) Testing and Documentation of the Implementation (13 marks) Evaluation (7 marks) Project Report (7 marks)

Hints & Tips

As we have a tight time schedule for marking your project, you must ensure that youhand in your project by each deadline.

Keep a diary log of all the occasions you met or talked with your client / user and the reason forthe meeting.

Remember that project write-ups are time consuming Dont leave it until the last minute work on it throughout the project.

Divide your project into manageable sub-tasks (bite sized chunks) set yourself intermediatedeadlines for each one and stick to them.

Make sure that you complete all sections of the project.

Only your write up will be seen by the moderator you must make sure that it shows evidenceof everything you have done they will not see your work on computer.

You must provide evidence that your solution works.

Design sketches and annotations should be done by hand.

Leave a left hand margin of at least 20mm on all pages to allow for binding.

Annotated printouts, scans, diagrams, pictures etc should be given a fig number so that they canbe referred to in the write-up.

Dont be afraid to ask for help, if needed, but any direct assistance given by the teacher mayaffect your mark.

Provide a clear and detailed record of all sources of information gathered and used throughoutthe project.

Record any work done outside the supervision of your teachers.

Read through all documentation you receive so that you are clear of exactly what is expected ofyou.

Much of what you learn in INFO3 can be applied in this INFO4 coursework.

Deadlines

You will have interim deadlines for different parts of the project throughout the year when your workwill be handed in and interim marked. The final deadline for the completed work is

First lesson after the Easter holidaysMonday 27th April 2012

Specification

The following table has been copied directly from the AQA supplied specification and explains whatyou need to include in your project. It is therefore important that your project report covers all of thesections listed in the table.


You should refer to this table for help throughout the project plus the detailed notes that follow. Inaddition, you should refer to the A2 Nelson Thornes textbook. The mark scheme has also beenprovided so that you can see what you need to do within each mark range.

Section The project report

should IncludeAmplification

1. Background &investigation (14 marks)

An introduction to theorganisation.

This should include the type and purpose of theorganisation, and give an idea of its size and scale ofoperation. Your contact within the organisation should beidentified.

A description of thecurrent system (orexisting situation) andits environment.

Moving down in scale to describe the system (or existingsituation) within the organisation/for the organisationwhich is under investigation. The people/departmentsinvolved.

Identification of client,users and audience.

Who is it for? Clear identification of client, users andaudience (where applicable). N.B. It is likely that there isone client, but multiple users. At this level of study, it isexpected that this will be the case.

A business case(reasons) for change.

Why the project is needed by the organisation.

Evidence of the use ofrelevant investigationtechniques.

Evidence of, for example, planning, conducting,documenting and evaluating meetings with clients,interviews, observation, questionnaires, research asappropriate.

Requirements of theclient. What is the proposed system to provide?

2. Analysis &deliverables (15 marks)

Statement of scope. This should include any internal or external constraints onthe proposed system. These may include hardware,communication technologies, software, format of externalinformation requirements, staffing and environmentalfactors.

Description of theproposed system.

This may take various formats but should include thebenefits for, and likely impacts on, the organisation.

Documentation ofprocesses.

Again, the format for the documentation is not fixed butshould be appropriate to the system being analysed.

Description of theusers of the proposedsystem.

Details of the skills of the users of the proposed system,appropriate to the system.

Evaluation criteria. Both quantitative and qualitative criteria against whichthe solution can be tested and evaluated. These should bederived from the requirements of the client.

Agreed deliverables. What is to be produced and handed over to the client?This may be a prototype system or a partial system.

Evidence of checkingthe findings with theclient.

Findings must be presented in such a way as to beunderstandable to the client.

3. Design &planning forimplementation (14 marks)

Evidence ofinvestigatingalternative designsolutions.

Should include investigating options for all elements ofan ICT system as appropriate to the project.

Draft design work. To be able to discuss with client. Final design work. From which to implement. Plan for

implementation, testingand instalment,including proposedtime scales.

Training requirementsfor the new system.

This may include what documentation will be requiredfor training the users.

Testing strategy. Should set out what testing is necessary, who will do it,when and where. You should describe here any


constraints on live testing that require a simulatedenvironment to be used.

Test plan. The tests that will be undertaken, what the tests aretesting, the order in which the tests will be completed.

4. Testing &documentation oftheimplementation (13 marks)

Evidence of testing. Where testing in the intended environment is notpossible, testing in a simulated environment will beacceptable providing this has been explained and justifiedin the testing strategy. Testing should concentrate on thetesting of complete processes and the system as a whole.Evidence of functional or unit tests, for example forvalidation or for the backing up of one file, is notrequired.

Evidence of testingshould includeevidence of clientand/or end user testing.

As appropriate, depending on whether the client is alsothe end user.

Comprehensivedocumentation of thesolution that wouldallow the solution to beused/maintained ordeveloped furtherwhich is appropriatefor the client/ users.

Documentation could be technical or user documentationdepending on the individual project undertaken and theagreed deliverables.

5. Evaluation ofthe implementedsolution (7 marks)

A critical evaluation ofthe solution that wouldallow the solution to beused/ maintained ordeveloped furtherwhich is appropriatefor the client/user.

The solution should be critically evaluated against theevaluation criteria and the client needs, as defined duringthe investigation and analysis stages. Evidence fromtesting should be referenced.

An evaluation of thestudents ownperformance.

This should identify strengths and weaknesses in theapproach they have identified, how they would improvetheir performance on a similar project in the future.

6. The projectreport (7 marks)

The complete workshould be submitted inthe format of a projectreport.

The report should be well structured and should make useof facilities available within software packages to enablethis to be done: for example, by including a contents list,headers/footers, pagination, indexes, effective use ofappendices and presentation techniques. Appropriate use of technically accurate illustrative andvisual material for effective communication. Anappropriate style of writing has been adopted. Thestandard of your written communication will be assessedin the report.

Detailed information for each section of the report is included on the following pages.The order of some of the items from the above specification has been changed to match the markinggrids. Copies of the marking grids are included at the end of the guide.

1 Background and Investigation (14 marks)

1.1 Introduction to the Organisation (2 marks)Give a description of the organisation that requires the new system you are going to develop. Try tobuild a mental picture for the reader of what the organisation is about. Suggested things to includeare:

o Company/organisation nameo What do they do?o How long have they been in operation?o Where they are located?

o Do they have multiple sites?


o Names of any key people involved. E.g. managing director,managers, staff using the current system

o The name of your contact within the organisation and what theirresponsibilities are

o A hierarchy diagram with explanation showing differentlevels within the organisation (see chapter 1)

o How many employees do they have?o What are the different job functions?o Any relevant history e.g. are they a new company?o Any photographs, pictures, helpful information to add?o Any particular reasons why they are looking to get a new system?o What do they want?

1.2 Description of the Current System (3 marks)Write a detailed description of the existing system how do they do things currently?

o Who are the people involved in the current situation?o What are the problems with the current system?o How did these problems come about?o Is there any background history to these problems?o What information does it produce? Who uses this?o If there is no current system, then explain what happens now instead even if it is not

a computerised system.o You can include data decomposition diagrams and data flow diagrams of the existing

system here. Make sure you explain any diagrams you include.

1.3 Identification of Client, Users and Audience (2marks)

o Describe the client, users and audience clearlyo Give names, job roles and positions within the organisationo How do these people use the current system?o What problems do these different people have with the current system?o Do they have different problems?

As part of your continuing contact with your client and users, you should keep a diary record to recordall your contact with them throughout the project. Make a note of who you met, when, where, thepurpose of the meeting and any outcomes or feedback from them. Also include any contact via phone,email or other means. This diary log can be presented in the Appendix and is probably best laid out ina table.

1.4 A Business Case for Change (2 marks)Explain why this project is needed by the organisation. Reasons for change usually fall into four maincategories.

o Technology perhaps a new technology has emerged which the business needs to

embrace e.g. when barcodes were invented, or perhaps existing technology is beingphased out and the current system will no longer be supported. Is their old system tooslow so it is losing them customers?

o Economic perhaps the existing system is too expensive to maintain or the new systemwould introduce cost savings? Are they losing business? Is it to save money? Do theywant to attract more customers as they need to make more money? Have they got acompetitor who is taking all their business? Have they grown quickly as a businessand are finding it difficult to maintain adequate records?

o Legal have there been changes to legislation that means the system is needed?o Operational does the existing system operate correctly? Perhaps it does not have the

required functions.

1.5 Investigation Techniques (3 marks)


There are a variety of techniques that you can use to investigate the current system and you need toinclude two or more to gain higher marks.

o Interviewso Questionnaireso Observationo Thought showerso Record searching / document analysiso Fact recording

Make sure you explain what techniques you are using, why you are using them, what data andinformation you can gain from them, how the techniques are appropriate for your project and whatpeople are involved etc. Include scanned copies of any documents and refer to them within your text. You could use photographs of observations if they are relevant.

1.5.1 User Skills SurveyAt this point you should also conduct a survey of user skills. Documentation of this will follow in theanalysis section but it needs to be carried out now. You need to get a good idea of the skill level foreach user (or group of users) and determine exactly what they can and cant do, what skills theyalready have, how they prefer to learn (self taught, in a classroom, from a colleague, from a book or cdetc). Consider their business skills and non-technical skills too, not just what they can do on thecomputer. Think about how you can find out this information e.g. by questionnaire, interview,observation etc. If a questionnaire, then you need to think carefully about the design of the form andthe way you word your questions. Remember that users can be both internal and external to an organisation

o internal = member of own workforceo external = e.g. member of public using extranet to buy goods and services

1.6 Client Requirements (2 marks)You need to identify all of the requirements for the client. Requirements tend to be what the system has to be able to do and what it is to provide. They may be a mixture of qualitative (opinion) and quantitative (measurable) requirements. If you have clear requirements this will make it easier for you to evaluate your system at the end of theproject.

Types of requirements you should consider alongside the actual processes of the proposed system

o performance (e.g. time needed to complete a task)o timing (any deadlines for output to be produced)o archive (how long for, where, how etc)o system availability (24/7, 9-5, etc)o failures (contingency, computer failure)o System integrity (what to do about errors)

Examples of qualitative requirements (opinion)

o The system should be user friendlyo The system should be easy to learno The system should be easy to navigateo The system should be pleasant to look ato The system should be easy to read and understand

Examples of quantitative requirements (measurable)

o The system should be able to look up a customer in xminutes/seconds

o The system should be able to complete an order in xminutes/seconds

o The system should automatically print out an invoice on papero The system should include a facility for the user to provide

written feedbacko The system should include the company logo on all

documentationo The system should use the corporate colours and styles


It is very important that you have a logical numbering system for your requirements because you willbe referring to them throughout the project. You can number them in any way you wish but beconsistent e.g.

o 1, 2, 3, 4 etco A, B, C, D etco R1, R2, R3, R4 etc

The best way to lay this section out so that it is clear is to create a table with 3 columns (requirementnumber, short description, detailed description). For each requirement give some detailed explanationthat includes:

o A more detailed description of the requiremento The reason for the requirement why is it needed? What does it do for the user?o Limitations give any constraints imposed on the resolution of the requirement

Typical constraints could include hardware/software, legal constraints, policy constraints,system-related constraints, financial constraints etc

1.7 Terms of Reference

It is advisable to create a Terms of Reference document for your client although it is not specificallyreferred to in the specification or marking grids. It is what would happen in a real business and ithelps to set out all the initiation aspects of the project so everyone involved knows exactly what is tobe produced and what is being omitted. It should be a separate document and you should include it inthe appendix. It is not usually a long document probably only a couple of pages. The client shouldagree your Terms of Reference and provide you with signed approval, preferably on headed notepaper. A scanned copy of the letter should also be placed in the Appendix.

(See page 130). A Terms of Reference should include most or all of the following information (leaveout any that are not appropriate for your project):

Background An introduction to the project along with relevant background information to

set the scene for the justification of this project. Include referencesto the current problems and errors in the existing system.

Aims and Objectives Aim: a clear statement of the purpose of the proposed project.Objectives: set out what the project will do in specific, measurable terms. They

should be realistic and achievable in the time available.

Deliverables States what the project will deliver at each stage of the life cycle. Deliverablesare NOT the same as requirements. (See analysis section for furtherdetail).

Scope States what is included and what is excluded from the project.Resourcing What people are involved, when they will be needed, for how long, in what

capacity etc.

Timescales Overall timescales for the project including any specific deadlines e.g.proposed system design to be ready on dd/mm/ccyy, and theproposed end date when the system will be installed and fullyfunctioning.

Reporting arrangements States when and how you will contact your client.Client and User Description of who the client and users of the proposed system are and

what their roles are.

2 Analysis and Deliverables (15 marks)

2.1 Statement of Scope (3 marks)The scope of the project sets out exactly what will be produced by the proposed system and what willbe excluded. In other words it states the boundaries of the system. If you do not explicitly state what


the boundaries are you cannot get 3 marks. You also need to discuss the constraints on the proposedsystem and these can be internal or external constraints. Things to consider for both internal andexternal constraints are:

o Hardwareo Softwareo Communication technologieso The format of information requirementso Financeso Staffingo Environmental factors

An internal constraint is something that can limit your ability to complete the project, but issomething that you may have some control over. For example

o Do you have particular software that you have to use and why? Perhaps theorganisation has already licensed certain software and dont want to buy othersoftware or perhaps all their staff are already skilled in the software they specified.

o Do you have a budget to work to? There may be only a limited amount ofmoney to complete the work.

o Do you have particular timescales in which to complete the work?o Staff may have skills in particular software so you have to use that software to

produce the solution.o You only have a certain number of staff available to you to complete the work.

An external constraint is something that is outside of the business and that you may have no controlover.For example

o Your work is required to be compliant with the acts of law such as The DataProtection Act, The Copyright, Design and Patents Act and the DisabilityDiscrimination Act.

o You have to wait for delivery/installation of something at some point in yourplan. If that is delayed the project will be delayed. E.g. in a building project, theinstallation of the roof would be critical as inside work could not start until this iscompleted.

The teacher resource bank on the AQA website has an example of scope with examinerscomments. Even though it is a well written, very long example it only got 2 marks because thestudent did not define the boundaries of the proposed system.

2.2 Description of the Proposed System andDeliverables (3 marks)

At this stage you are still describing the proposed system in English and you should not be referringto specific pieces of software e.g. spreadsheets, databases etc, UNLESS your client hasSPECIFICALLY asked for a certain type of software to be used and it is one of yourrequirements/constraints. The Analysis section is all about WHAT the system is going to do andnothing about HOW it is going to be done that comes later in the Design section. The descriptionshould also consider the benefits of the proposed system to the organisation and any impacts (bothpositive and negative).

2.2.1 Description of the Proposed SystemYou should consider the following questions plus any others of your own:

o What software do you propose to use? (only if this is a specific requiremente.g. a website)

o What hardware will it run on?o Does it need any extra hardware/software e.g. printer, scanner, barcode reader,

Flash installed etc.o Describe any particular key features it will haveo What will the user be able to do with it?o How will the user and audience use it?o How will it be updated?o How will it be backed up?o Will people be able to use it at the same time?


o Will it have any particular security on it?

2.2.2 Benefits of the Proposed SystemDescribe what benefits the new system will bring to the client, user and audience. For example:

o Will it make them money?o Will it improve customer satisfaction?o Will it make anyones job easier how?o Will it bring more customers?o Will it raise their profile?o Will it make them more competitive?o Will it help them to expand or move into other markets?o Will it make it easier for customers to contact them?

2.2.3 Impact of the Proposed SystemFor each of the benefits you have identified you should consider what impact each one could have.

o In the case of a business opening an online shop, the extra business couldsecure existing jobs or result in more jobs being created.

o In the case of a tourist information website, the impact could be morecustomers in the tourist information shop possibly requiring more staff, andmore visitors to the region resulting in an improved local economy.

2.2.4 DeliverablesDeliverables are NOT the same as requirements. A deliverable is something you are going to provideto your client at various stages in the development of your system and what you will hand over at theend. You need to be specific when listing the deliverables so there is no confusion over what youintend to deliver. For example, if you say you are going to deliver web pages, the customer mayexpect the website to have been registered and be up and running, whereas you may be expecting tojust hand over the files and it is up to them to find a host and register the URL.

Some examples could include:

o A project plan showing timescales, key milestones etc.o Identification of user skills and training requirementso User documentation in the form of a User Guideo Design of the system such as online forms, printed reports etco Microsoft Access Database meeting set requirementso Administrator Guideo Website pages to be handed over to customer to register URL and host.o Website with registered URL and hosting included.o Desktop Hardware (2Ghz processor, 2GB memory, 20GB HDD, 17 monitor)o 1 week training course between 1-5 Sept to train all staff on the new system,o 1 person providing support for 1 month after the system is implemented.

See p46 for further examples.You need to list all of your deliverables, explain each one and give a due date for each one.It is important to include the deliverables with dates in your Terms of Reference and get clientapproval.

2.2.5 Project PlanAll projects need a plan of how they are going to proceed and your project is no different. You needan overall project length with a defined total duration plus start date and end date. Then sub-divide theproject into sections for example, Analysis, Design, Construction, Testing, Installation etc. For eachsection work out a realistic duration, start date and end date. Remember that some tasks can be doneat the same time and you dont have to be working exclusively on one section fully at one time sothere can be some overlap. You may for example do both implementation and testing of differentparts of the system at the same time.

The easiest way to show this information is in a Gantt chart. Include week numbers and dates andshow any milestones such as design documentation or user training etc. These are identified by adiamond shape. You can use any software. There is dedicated software available for project planningbut it is perfectly acceptable to create a table in Word or Excel that will be sufficient for what youneed. At this stage this is an overall project plan. In the Design section you will create a moredetailed plan by further developing your Gantt chart and adding more detail to encompass the sub


tasks you have designed and the different types of testing you will undertake.

A simple example of a Gantt chart:

week 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22date 0

2/11/09

09/11/09

16/11/09

23/11/09

30/11/09

07/12/09

14/12/09

21/12/09

28/12/09

04/01/10

11/01/10

18/01/10

25/01/10

01/02/10

08/02/10

15/02/10

22/02/10

01/03/10

08/03/10

15/03/10

22/03/10

29/03/10

Analysis Design Construction Testing Installation

2.3 Documentation of Processes (3 marks)As well as a written description of what the new system is going to do you should also consider usingdata decomposition diagrams and DFD diagrams (data flow diagrams). These can be created atdifferent levels (level 0, level 1 etc) and help to define how the data flows around the proposedsystem, where it comes from, where it goes to, where data needs to be stored etc. You could alsoconsider the use of flowcharts to document the logical processes involved. Examples of these can be found in the textbook Coursework for A2 ICT by Barbara Wilson.

You need to document all the inputs, processes and outputs. It is always easier to start with theoutputs and then identify the inputs and processes needed to create that output. For example:

INPUT PROCESS OUTPUTCustomer name and addressItem code and descriptionQuantityPrice

Multiply price by quantity to get total cost of itemsAdd up all total costs to get overall total costCalculate vatAdd vat to overall total cost to get grand total

Invoice for acustomer

IMPORTANT these must be non-software specific. The example above just lists data that would berelevant, says how calculations are done and what needs to be produced. It does not mention any typeof software at all and it does not imply where any data is stored.

Also look at the activity on page 139 in your textbook. This will help you identify what informationwill be useful when defining your processes.

2.4 Description of the Users of the Proposed System (3marks)

Use the information gathered / questionnaire you created in the investigation stage to document theuser skills. If there are multiple users, describe each of their skills individually. This need not only betheir technical skills e.g. how well can they use spreadsheets, but also what business experience theyhave and how quickly they can pick up new skills. If the users have completed the questionnaires byhand then scan them into your work.

Things to consider for each user:

o Identify the job roleo What parts of the proposed system are they likely to be using?o What skill levels have you identified for these users?o Describe what skills (technical, non technical, business) you think they will need to use

the proposed systemo What they can and cant do will influence how you design the system and what types

of help and support you may include. Describe how you will consider their skills and


knowledge when creating your design in the next stageo Do you think they will need any training?o What types of training will be the most suitable for them? Refer to Section 8 in the

textbooko What support do you need to provide for them once the system is up & running?o How would they cope with problems that occur during use?o Do they need user guides? Online help? etc

Remember, anything you need to provide for your user needs to be included in your test plan later.

2.5 Evaluation Criteria (3 marks)Evaluation criteria are a way of measuring the success of the project once it is completed. Just likerequirements, they should be a mixture of qualitative and quantitative measures. It is important thatyour evaluation criteria relate to your original requirements. Each requirement should have at leastone evaluation criteria, preferably more and they should be identifiable e.g. numbered. For example:

REQ Requirement Evaluation Criteria1 The system must

print out class listsfor each teacher

1.1 Class lists must be sorted into alphabetical order of surname

1.2 Class lists must be printed on A4 paper in portrait format 1.3 Class lists must use the house style and show the school logo in the top

right hand corner 1.4 Class lists must look professional and easy to read 1.5 It should take no more than 1 minute to locate the correct class and

print it

Note that neither the requirements nor the evaluation criteria specifically mention or imply a certainpiece of software. Sometimes it is unavoidable especially for example, if your client has requested awebsite, but try as far as you can to keep them generic and independent of any software. Evaluation criteria categories that you could consider (see p134):

o Performance e.g. overall time to complete a business processo Timing e.g. output deadlineso Archive e.g. retention period for datao System availability e.g. required hours per dayo Failure measures e.g. contingency procedureso System integrity e.g. error management

2.6 Evidence of Checking the Findings with the Client

It is now very important that you get some feedback from your client to make sure that what you havedescribed in your investigation and analysis is what they actually want. Give your client a copy of therelevant parts of your work. They need to give you written feedback and explain in writing anychanges that they need you to make. You should then update your work to include the changes thatthey have requested.

Describe here what documents and information you are providing for your clients and what changesthey have requested. Provide evidence of letters, emails, scans etc.

3 Design and Planning for Implementation (14 marks)

3.1 Alternative Design Solutions (2 marks)You need to provide evidence of investigating alternative solutions to the problem. Identify two orthree different design solutions which could be used to meet the clients requirements. It could bedifferent types of software (e.g. databases vs spreadsheets vs manual) or it could be different ways ofsolving the problem with the same type of software. For each alternative

o Describe the alternative solutiono Refer back to the clients requirements and discuss whether or not this solution can


meet the requirements and how well. Discuss advantages and disadvantages of eachsolution.

A clear way of presenting your findings could be in a table as below.

Requirement Option A Option B

After you have completed the comparison, state which option you are going to use and why.

3.2 Design of the Solution (3 marks)This section will probably be a long section! You need to document the whole design of your system,including the hardware and software, and designing all the inputs, processes and outputs (in otherwords, HOW you will do everything). You will also need to get user feedback after you havecompleted this part, provide evidence that you have consulted them and then incorporate any changesinto a final design. How you provide this evidence is up to you. For example you may have giventhem some screen designs and they have hand written comments and changes directly onto the paper. You could include these copies in the appendix and describe the changes within the body of yourreport. Or you could include scans of these documents within this section and show the final design ofthat feature incorporating their changes. Or you could ask the client to summarise all the findings in aformal letter which you then scan into your report. The choice is yours.

o What hardware needs to be used and why?o Where will that hardware be located?o What type of network structure will be needed?o What software is needed for the application components e.g. operating system, DBMS,

applications software, communications software etco What type of backups will be needed? Where will they be stored? etc

What else you include in this section will again depend on the type of system you are creating. Remember that these are designs of what you are going to create; you havent created anything yet (oryou shouldnt have!) so therefore screenshots are unacceptable. Screen layouts and reports should bedone by hand and scanned. Make sure each design is clear with a short description of each. You needto consider the following:

o Style sheetso Data Dictionary all items of data within the systemo Database table designs field names, types, keys, sizes, descriptions, restrictions etco Data dependencies and relationshipso Data capture and Data inputo Validation and Verificationo Input formso Queries, searches, sorts,o Output screens and reportso Data backup, security, archivingo User interface standardso Screen based interactionso Hierarchy diagrams for website pageso (see page 142- for further information)

3.3 Implementation Plan and Training Requirements (3marks)

3.3.1 Implementation PlanDivide your system design into manageable chunks or subtasks and describe what each subtask is. You have already created a project plan by using a Gantt chart. You now need to expand it to includeall of the subtasks within your system. You need to allocate durations, start dates and end dates for


each subtask. This will affect the construction, testing and installation parts of the plan. You also needto prioritise each task and work out what order each task needs to be done in. Think about where usertesting could be incorporated and whether any user testing could be done at the same time as you areworking on other parts of the system. If you copy your original project plan you can add all thesubtasks onto the same plan. Make sure you include an explanation of what your plan is showing. Itis not sufficient to just have a Gantt chart and nothing else. Also include user training, installation,conversion of existing data etc in your plans.

3.3.2 Training RequirementsYou have already investigated the skills of your users and documented this. You now need to describewhat training needs the users have and any support needs they may have for when the system iscompleted and installed. More than one method may be needed and different users may have differentneeds. Provide justification for your choices. Training and Support Options could include:

o Initial training via one-to-one tutoring or whole group sessiono Printed Manual / User Guideo CD-ROM Training Guideo Powerpoint Presentationo Website / online screenso Online help built into the system

3.4 Testing Strategy (3 marks)A test strategy is an overall plan for all testing activities that will be carried out to check that theoriginal needs have been met. The strategy is concerned with checking the solution as a whole andthat all the original requirements are working as they should. Testing is carried out at several levelswhich are listed below and for each level you need to consider the following in your strategy:

o Purpose, type and scope of the tests and what deliverables are expectedo Who is responsible for these testso Who will do the testing (mention user involvement where appropriate)o What activities will take place and which people will be involvedo Where the testing will take place

o When the testing will take placeo What resources are needed

o Any constraints on live testing?o Is volume testing required?

o Does the system need to operate on a variety of platforms or different screen sizes(e.g. different screen resolutions for displaying web pages)

o Is a simulated environment needed?o How will you test against the client requirements and evaluation criteria you specified?o How will the finished solution be installed? Direct, phased, parallel, pilot? See p75

The different types of test you will undertake fall into these broad categories (see p48):

o Unit testingo Integration testingo Functional testingo Systems testingo User testingo Operational testing

For example, if you were writing a computer program that contained several modules, each modulewould be unit tested on its own first and then integration tested to make sure the modules fit togethercorrectly. They are both concerned with what the actual code does within the program. Thenfunctional testing checks that if you put abc in, you get xyz out. System testing would then lookat the system as a whole and tests would be devised to consider different possibilities, e.g. if we add anew customer and choose products to buy does the system produce an invoice and send a confirmationemail? User testing is only started once the system is working correctly and you are completely happywith it.

You may wish to consider prototyping where you give your client a limited version of a solution e.g. aset of web pages that have functioning hyperlinks but the text content of the pages is omitted, to givethem a feel for the solution. They offer their comments and you then make changes.


Your strategy should also consider backups for when the system is live. You will need to check thatthe backup process works correctly when you do your testing:

o How will the backups be done?o How often will backups be done and when will they be done?o What will be backed up?o Who will be responsible for doing the backups?o What medium will be used and where will they be stored?

3.5 Test Plan (3 marks)A test plan is a very important part of creating a solution and you must make sure it is thorough andcomplete. It is important that you carry out unit testing for example, validation settings, extreme data,erroneous data etc to make sure the system works, data can be fully seen, all the correct information ispresent etc, though there is no requirement for you to document this in the project report. The testplan must focus on systems tests, user tests and operational tests (where appropriate).

A test plan is created after the design of the solution has been completed, but before the solution isactually created. In a large organisation, different people would be responsible for the design andconstruction of the solution so once the analysts have completed the design, they will pass it over toprogrammers who will create the solution. While the system is being created the analysts will thenwork on producing system test plans and user test plans so that they will be ready to use once thesystem has been completed. The programmers would be responsible for doing any unit and programtesting before handing it back to the analysts.

It may be helpful to break your system testing into the subtasks you identified earlier. This will helpyou to focus on all the different aspects of your system and make sure nothing is omitted. You can usea logical numbering system to do this make sure you explain any numbering / organisation schemesyou use. Also, dont forget to include tests for all of your client requirements and any relevantdeliverables e.g. a user guide. Your user test plan should be on a separate page to the system test planso that it can be given to the user for testing.

The best way to lay out your test plan is to turn the page landscape and use a table with severalcolumns. This is one example though you may see variations. At this point, the last two columns willbe empty, and will be populated once you commence your testing.

TestNo.

Description Input Expected Results Actual Results Comments

1.1 1.2

For your user test plan, it is advantageous to contact your client / users and ask them to identify reallive data that can be used for testing purposes. Sometimes this can be difficult because ofconfidentiality, data protection rules etc, but it is worth trying to get them involved if you possibly can.

4 Testing and Documentation of theImplementation (13 marks)

4.1 Testing the Whole Solution (3 marks)It is important that you complete full unit testing to make sure your system works, that all validation iscorrect etc before you start formal system testing. There is NO requirement for you to provideevidence of unit testing. If you include it you will not gain any credit for it and AQA have specificallystated that they only wish to see evidence of testing the whole solution.

As there is no requirement for unit testing, and you no longer have to provide any evidence of creatingthe solution (implementation), testing and documentation is the only place you have to show thequality and extent of what you have created. The marker and examiner will not see your finishedsolution, only your project report, so if you have an all-singing, all-dancing spreadsheet or databasethen you need to make sure there is evidence of it here. If it is not appropriate to include it in thetesting section, then consider whether it would be more appropriate in the technical documentation


section e.g. database structures, finished web pages etc.

Copy the test plan from the design section into this section and carry out each test systematically oneat a time. For EVERY test you need to add what actually happened to the Actual Results column. You must provide evidence via screenshots, scans of reports etc plus a description of what theevidence shows. In the comments column you can add any modifications you had to make or includea reference to the page number of where the testing results can be found. Make sure every piece oftest evidence refers to the correct test number. Before and after screenshots may be applicable in somecases to prove something works. If any test fails, for whatever reason, you must retest it and showevidence of it working.

4.2 Testing with Client and Users (3 marks)It is essential you have your client and users test the system you have created. There needs to beevidence of their involvement and it is beneficial if you can get all of your users to test the system.

Print out the user test plan you created in the design section and give a copy to your users (you shouldhave more than one user). You may have different tests being done by different users so make it clearwhich users are doing which tests. Ask them to do all the tests you have identified and to add theirresults and comments to the page. It is also sometimes beneficial to give the users a blank test plan sothat they can add any extra tests they think of that you may have overlooked. Or ask them to write ashort document about their findings. (Refer to sections 4.5, 5.1 and 5.2 regarding client feedback).These documents can then be scanned into the appropriate place in your project report.

4.3 Documentation (3 marks)The types of documentation you could consider creating:

o User Guideo Technical or maintenance documentationo Installation Guideo Training Manualo Training Instructors Manual

You will probably create just the first two of these, unless you have a specific requirement from yourclient to create any of the others, or to deliver a training course. Include a paragraph in your report ofhow you think your documentation (all types) meets the needs of the client/user. Make sure youreference where the documents can be found in the Appendix.

4.3.1 User GuideA User Guide should be a separate document provided for your users and should be presented in theappendix. It should be written in language that your users can understand (i.e. not technical!) andshould be pleasing to the eye. Try and find some good and bad examples of manuals to help informyour choice. What you include will depend on your system but you could consider:

o A Front Covero A Table of Contentso An introduction stating what the system is about and who uses ito Instructions on how to load the system (and install it if appropriate)o Routes through menus/website navigation guideo An explanation of what each option on a menu does using screen shots to illustrateo Samples of output on screen and paper outputso Any special instructions on how to input data e.g. the format of a date field or the range

of accepted values for a fieldo How to save changeso Explanation of error messages and what to do if they occur / FAQ

4.4 Technical Documentation (2 marks)A separate document that can be used as technical documentation is strongly recommended though itdoes depend on what type of system you have created. Include it as a separate document with its ownfront cover, table of contents, page numbering etc and include it in the appendix. This is NOT a guideon how to use the software (assume that the reader knows the software); it is documentation to help


someone maintain your system and make changes to its structure, add new features etc. Rememberwhat was said in the testing evidence. If you have a complex solution but it hasnt been evidencedvery well in testing or anywhere else, consider putting it in the technical documentation. What youinclude will depend on your system but you could consider:

o Hardware and Software requirementso Instructions for opening and configuring the systemo Database relationship diagramso Database table structureso Validation and verification procedureso Macroso Complex formulae, functions, calculations etco Any programming code you have usedo How web pages link together (hierarchy diagram)o How to upload changes to a websiteo Information about domains, web hosting etc

4.5 Appropriateness of Documentation (2 marks)You need to get feedback from all of your users so that they can comment on the documentation youhave supplied. You could do this via a questionnaire if you wish. It could also be combined with allthe feedback you need to get for the whole solution, not just the documentation. Write a concludingparagraph to back up your evidence and explain your conclusions. Include any client and usercomments here with evidence e.g. scans, letters, emails etc.

5 Evaluation (7 marks)

5.1 Evaluation of the Whole Solution (2 marks)Ask your client and users for feedback about your solution. This could be in the form of aquestionnaire so you can ask specific questions, or it could be general comments from them. Eitherway, you must include some feedback in your evaluation and also refer back to your testing to back upany statements you make. Include any written feedback you receive in your report.

Look at the solution as a whole and identify the strengths and weaknesses of the system.

o What works really well? o What is not so successful?o Is the solution an effective one?o What improvements and enhancements would you suggest?o Are there any changes the user would like to make? Why?

5.2 Evaluation against Client Requirements and EvaluationCriteria (2 marks)

Now you need to evaluate your system in more detail by referring back to the original clientrequirements and evaluation criteria. Copy your table of requirements and evaluation criteria into thissection from the analysis section. For each requirement, comment critically about each of the evaluation criteria that relate to thatrequirement. Again refer to client feedback and your own testing to back up your comments. You caninclude any suggested improvements here too. Use the four questions above to help structure yourcomments.

5.3 Evaluation of Students Own Performance (3marks)

Finally you need to evaluate your own performance. You are required to identify your strengths andweaknesses in the approach you took and how you have learned from any problems or achievements. Then you need to consider areas for improvement. Students usually find this part quite difficult. AQA have included an example of a self evaluation on the teacher resource bank of the website andyou should have a look at this for ideas. Also, try the following:

o Identify an achievement, something you were pleased with, or proud of, in this projecto What have you achieved? What has changed for you? Is there something you can do


now that you could not do before? Is there something you now understand that beforewasnt clear?

o Why is this achievement important? What does it mean to you?o How do you know what youve achieved? What specific evidence do you have? This

could be a skill you have acquired in your project.o How did you get there? What specific actions did you take?o Can you build on what youve achieved? Is there a next step? Are there still aspects

you would like to improve that would make an impact on your performance in thefuture?

o Try and answer the above questions for other achievements in this project.

6 Project Report (7 marks)

6.1 Use of Software (3 marks)o Use styles to ensure all headings are consistent throughout the reporto Make good use of consistent styles for different levels of your worko Use bullets, outline numbering techniques (i, ii etc)o Page numbers are essential in the footer and should be sequentialo Use headers and footers for other relevant/helpful informationo Page layout (both landscape and portrait may be required within the document)o Use of section breakso Use consistent marginso Include a table of contentso Include an index if appropriateo Captions for any illustrative materialo Use an Appendix where appropriate e.g. for Terms of Reference, User Guide

etco Appendices should be used sparingly

6.2 Organisation and Use of Language (2 marks)o Use the section headers detailed in this guide, this will help with your

organisationo Use appropriate technical languageo Make sure you use the spell checker and that it uses UK spellings not USAo Use correct grammaro Dont use text-speak!o Get someone to proof read your worko Check, check and check again. There is nothing worse as a marker seeing

constant spelling and typing errors.

6.3 Diagrams and Illustrations (2 marks)Illustrate your work as appropriate using

o Photographs and pictureso scans of original documentso sketcheso screenshotso hierarchical diagrams e.g. in website design or organisation structureo Use captions on your illustrations e.g. Fig 1 etc and refer to them in your

written work

7 BibliographyInclude references to all sources of information that you have used e.g. textbooks, other books, printedmaterial from your client, Internet websites etc.


8 AppendixThe appendix should not be huge. It is very time consuming for the marker/examiner to keep havingto jump around a project report trying to find the relevant material especially if it hasnt been cross-referenced very well. Try and keep all diagrams, scans, questionnaires and client involvementevidence etc in the correct place in your document. This will ensure your numbering is sequential andmake it easier for you to organise. For each document you need to add to the appendix, make sure youhave a front cover for it and number the appendices sequentially Appendix I, Appendix II, etc. If youuse the heading styles consistent with the rest of your report then they will also appear in your table ofcontents which is desirable.

The main documents that you are likely to need to put into the Appendix are:

o Terms of Referenceo Diary Log of Client/User contacto User Documentationo Technical Documentation

A2 INFO4 Coursework Guide Page 16


Documents

INFO4 Coursework Guide AQA