GCSE PROJECT GUIDELINES Use this presentation to make sure you have the correct content for you project - click on.

Slides:



Advertisements
Similar presentations
B – Design B(i) How the solution solves the problem In this section you specify exactly how your chosen software will meet the requirements. For example.
Advertisements

DT Coursework By D. Henwood.
JAVA Coursework (the same for 2A and 2B). Fundamental Information The coursework is 30 marks in your O’Level = 15% of the exam Must be word processed.
Phase 3 PAT / Research project. PAT - Research project - Phase 3 Big purpose Investigate problem In Word report provide evidence of full investigation.
285 Final Project. Document Specification: Rough Draft Due April 10th Purpose: Purpose: Economy of effort Economy of effort Input from instructors and.
185 Final Project (Also covers Project Proposal and Document Specification)
A452 – Programming project – Mark Scheme
Unit 03 – Computer Systems M/601/7261
Lecture 3: Writing the Project Documentation Part I
Software Development, Programming, Testing & Implementation.
Systems Analysis Chapter 8 P 94 to P 101
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
Systems Life Cycle A summary of what needs to be done.
Problem Solving Methodology
IPortfolio assignment Mandatory Unit evidence. Centres may use some or all of these activities or some of their own devising to help candidates complete.
Unit 3 – Problem Solving Vale Market Research is a large market research company who provides market research solutions to high profile blue chip companies.
AICT5 – eProject Project Planning for ICT. Process Centre receives Scenario Group Work Scenario on website in October Assessment Window Individual Work.
Review of Unit 1 SBA By Nyoka English. Problem Definition Identifies an organization and gives a brief description of the organization, zeroing in on.
“Prepare for Success” Academic Year 2011/2012. What is a report? A presentation of facts and findings, often as a basis for recommendations Written for.
LESSON 8 Booklet Sections: 12 & 13 Systems Analysis.
Chapter 8: Systems analysis and design
Advanced Business Communication Spring Advanced Business Communication Spring 2012 Introduction Our last project for the class is a recommendation.
Controlled Assessment
Feasibility Study.
Making a great Project 2 OCR 1994/2360. Analysis This is the key to getting it right. Too many candidates skip through this section. It’s worth 20% of.
Making a great Project 2 OCR 1994/2360. Design Some candidates dive in, make a database or spreadsheet, then try and make a design afterwards. This won’t.
Feedback on marking and next section. Feedback Do not copy from exemplar materials. All information in the project must be your own or acknowledged Remember.
The Project – Database Design. The following is the high mark band for the Database design: Analysed a given situation and produced and analysed a given.
User Documentation. User documentation  Is needed to help people (the users) understand how to use a computer system or software application, such as.
I Power Higher Computing Software Development The Software Development Process.
Controlled Assessment A(iii) Recommended solution Recommended solution Reasons for this recommendation Refer to the information requirements and your research.
Intermediate 2 Software Development Process. Software You should already know that any computer system is made up of hardware and software. The term hardware.
Test and Review chapter State the differences between archive and back-up data. Answer: Archive data is a copy of data which is no longer in regular.
The Software Development Process
Systems Development Life Cycle
GCSE ICT Systems Analysis. Systems analysis Systems analysis is the application of analytical processes to the planning, design and implementation of.
Task Analysis Exercise Project criteria Command term objectives Describe – give a detailed account of the PROBLEM and DESIGN NEED OR OPPORTUNITY (Page.
Systems Development The Kingsway School. Systems Development This is carried out when a company is having a problem. They usually employ an ICT Consultant.
M4 BTEC Level 3 Subsidiary Diploma in ICT. Technical Documentation The technical documentation may be a section in the user documentation or could be.
Making a great Project 2 OCR 1994/2360. Implementation This is about how you make your system. It should have enough detail for a competent user to be.
Software Requirements Specification Document (SRS)
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
CMPSC 16 Problem Solving with Computers I Spring 2014 Instructor: Tevfik Bultan Lecture 4: Introduction to C: Control Flow.
GCSE ICT 3 rd Edition The system life cycle 18 The system life cycle is a series of stages that are worked through during the development of a new information.
Chapter 11 Data Input and Output. Input Data Capture Forms Data can be collected using a data capture form or questionnaire that is printed on a piece.
1080 and the Control of mammalian pests Report on a biological issue 3 credits.
1. Design: Plan in detail Get the analysis document from this folder. There are two GCSE ICT tasks in unit 2: Power Point for the garden centre and Database.
Unit R005: Creating an interactive product using multimedia components Learning Outcome 03 : Be able to carry out usability testing Cambridge Nationals.
Investigate Plan Design Create Evaluate (Test it to objective evaluation at each stage of the design cycle) state – describe - explain the problem some.
Analysis. This involves investigating what is required from the new system and what facilities are available. It would probably include:
Unit F451 Computer Fundamentals Components of a Computer System Software Data: Its representation, structure and management in information.
In today’s lesson we will be looking at: what we mean by the software development lifecycle the phases in the lifecycle We will focus particularly on testing:
AS Level ICT Analysis. Analysis is the process of breaking down a problem into small parts so that it is easier to understand and therefore easier to.
Advanced Higher Computing Science
Writing Scientific Research Paper
Presentation Title Your Name
Database Systems Unit 16.
Reports Chapter 17 © Pearson 2012.
Report Writing.
Systems Analysis and Design
FEASIBILITY STUDY Feasibility study is a means to check whether the proposed system is correct or not. The results of this study arte used to make decision.
Testing a Solution.
This year you will complete Unit 1 (ICT Skills for Business) and Unit 21 (Creating Computer Graphics). You will gain a OCR Level 2 National First Award.
Task words Task words guide the writer to perform a particular function in answering a question. Task words are usually in bold font in AP Biology homework.
The Scientific Method ♫A Way to Solve a Problem♫
Introduction to Database Programs
Writing reports Wrea Mohammed
Unit 5 – eProject – Starting to look at projects Unit 5
Types of Information Systems
Introduction to Database Programs
Presentation transcript:

GCSE PROJECT GUIDELINES Use this presentation to make sure you have the correct content for you project - click on

CONTENTS Description of the Problem Investigation & Analysis of Problem and Specification of Solution Design of the Solution Review of Resources Data Collection, Data Capture and Input Data Verification and Validation Data and Program Structures

CONTENTS - cont Output Format Testing of the Solution Documentation of the Solution Evaluation of the Solution Printouts

Description of the Problem Describe the Company/Business – make it seem real. State:  what it does  where it is  who works there  number of employees  how long established  management structure etc State the nature of the problem Explain:  what they do at the moment in relation to the nature of the problem  explain why this is a problem (give specific examples that have caused problems)  give an outline of what they want to take the present systems place and give reasons why n Give reasons why you think this is a suitable problem for you to tackle

Investigation & Analysis of Problem and Specification of Solution Evidence of Investigation usually in the form of a completed questionnaire, which should: Be answered by someone in the company Give you all the information to be able to draw up a solution for your problem Investigation Report This is a summary of the questionnaire and states what the questionnaire has revealed Analysis Bubble Diagram This is a diagram of wants. It should show what you have learnt from the investigation and therefore what you think the company wants to solve their problem.

Investigation & Analysis of Problem and Specification of Solution - cont. Specification n This should be in the form of bullet points and show what the solution should achieve in all areas of the problem. It should: n List all recommendations and wants with examples in specific areas i.e. Databases DTP etc. n Be detailed enough to be followed by someone else should you leave the project. THIS SHOULD/WILL FORM THE BASIS OF YOUR TESTING LATER IN THE PROJECT SO NEEDS TO BE DETAILED. Evaluation Criteria n This should be in the form of bullet points and should describe how you will evaluate your solution once you have finished the project. You should look at it in 2 ways: n How will you judge the solution after your testing has been finished n How will you judge the solution in a years time THIS SHOULD/WILL FORM THE BASIS OF YOUR EVALUATION LATER IN THE PROJECT SO NEEDS TO BE DETAILED

Design of Solution Written explanation of your design – justifying all decisions using the following format: Hardware – what you will need for the solution to work Software - what you will need for the solution to work Data needed for the solution to work What data will you need – give specific details, names of fields etc How will you collect the data How will it be input into the system How will old/existing info be transferred How will data be protected – validation/verification and security Outputs – screen and printed Security arrangements for info and computers New Jobs/Responsibilities – if any Training – methods of THE ABOVE WILL PROVIDE THE BASIS FOR ALL THE SECTIONS TO COME SO NEEDS TO BE VERY DETAILED AND JUSTIFIED. GIVE EXAMPLES WHEREVER NECESSARY OR ABLE TO

Design of Solution - cont. Spider Diagram Showing the above in one clear diagram Hierarchical Diagrams of all software programs and tasks Broken down into separate diagrams for each software application. System Flowchart for main software application i.e. either a database for project 1 or spreadsheet for project 2 ALL DIAGRAMS NEED TO CLEAR AND HAVE A TITLE AND EXPLANATION OF WHAT THEY SHOW

Review of the Resources This section must show a detailed and justified choice of both hardware and software Hardware  State what the company has already – give detailed specification.  State what you need for the solution to work – talk about speed of processor; memory capacity; peripherals etc  Make recommendations about the hardware you will select. You need to provide a detailed comparison of other hardware or provide a full and justified account of your reasoning. Software  State what the company has already – give detailed specification.  State what you need for the solution to work – talk about the program requirements related to your design and specification  Make recommendations about the software you will select. You need to provide a detailed comparison of other programs or provide a full and justified account of your reasoning.

Data Collection, Data Capture and Input Data Collection  State what information you will be using for your solution State where you will get the above information from  Justify the above statements Data Capture  How will you capture your information – which format will you use  Who will capture the information  If you are using a DCF to capture the information show it and justify its design and layout  Justify the above statements Data Input  How will you input your data – which method will be used  Who will input the information  Where will this take place  What about the transfer of existing data  Justify the above statements

Data Verification and Validation Verification  Definition of verification from Letts  List examples of different methods and relate to your solution  Explain how you will do it. Make sure you justify all decisions Validation  Definition of validation from Letts  List examples of different methods and relate to your solution  Explain how you will do it. Make sure you justify in detail all decisions in the form of a table

Data and Program Structures This should be in the form of a table. It must have a title and an explanatory paragraph.

Data and Program Structures - cont For Databases  You must state why the field is positioned where it is. This can be referenced with the section on Data Capture  State why you have made the field that particular size, i.e. what is it expected to have in it  State why you have made the field that particular format, i.e. what is it expected to have in it For Spreadsheets  You must state why the cell/s are positioned where it is. This can be referenced with the section on Data Capture  State why you have made the cell/s that particular size, i.e. what is expected to go in it  State why you have made the cell/s that particular format, i.e. what is expected to go in it

Output Format This section should include examples of all outputs - printouts and screen  State the purpose of each output  Explain the design  Show the DCF and include an explanation of its layout etc  Show a screen shot of the outputs from the spreadsheet model – graphs, screen view etc and include an explanation of its layout etc  Justify its inclusion in the project

Testing of Solution State what you will test  This should be determined by your specification in the INVESTIGATION section. You must refer to this.  You must test everything. Everything above and every validation check for each field/cell Design Test Data  This should show the above  It should allow you to forecast the results Predict the outcomes of your tests  This should cover all tests  It should be mentioned in the order that you will carry the tests out  It should be comprehensive Tests  The tests should be carried out and results recorded either as printouts or screen shots  The tests should be referenced so that you can refer to them in the evaluation section

Documentation of the Solution User Guide  Should be designed for novice  Should refer specifically to your solution  Must explain ‘jargon’ i.e. sort search  Must include screenshots of your solution Technical Information  In the form of a PowerPoint presentation  Must include technical information – i.e. specification of hardware and software: capabilities of the solution Include a SYSTEM FLOWCHART that is fully explained

Evaluation of the Solution Tests  Go through the tests one at a time and state if they were successful or not – refer to them by index number Explain the limitations of your solution  refer to the tests that went wrong and give reasons why  Point out any failings in the software that you chose Success or Failure  Judge your solution on the criteria that you have set yourself  Refer to the Specification of the solution and the Evaluation Criteria Refinements  What would you change next time round – suggest improvements for the future – software and hardware  What do you need to do to make the solution better

PRINTOUTS FOR A PRINTOUT OF THESE NOTES IN MS WORD FORMAT CLICK ON THE ICON