Non-exam Assessment The A Level Project

The A level Project 20% of the A Level grade Need to identify a real problem that can be solved with a computer based solution Need to work through all stages of the software development Majority of the marks are for the technical solution.

Selecting a project Expected to identify a realistic problem with a real end user and create a system that allows interaction with the user and involve the storage manipulation and output of data or.. To investigate a specific aspect of computing such as artificial intelligence or 3D graphical modelling with reference to a project supervisor.

Selecting a project Marks break down. Analysis9 Documented design12 Technical solution42 Testing8 Evaluation4 Total75

Selecting a project – How to get one Start with family and friends to see if there is anything they do on which you could base a project. For example you could do something based on their work. Many students base projects on their own work experience placements, particularly if they still have contacts at the organisation Another source of projects is your own hobbies and interest. For example you may be able to create systems related to gaming, social media, clubs or societies that you are involved in. Maybe ask teachers from different subjects if they have an problems to solve or simulations they would like developed as a computer based system

Selecting a project – Some ideas A simulation of a business or scientific issue. For example a business issue such as modelling share prices, or a scientific issue such as modelling flu epidemics An investigation of a well known problem such as the Game of Life, the Towers of Hanoi or the Travelling Sales man problem. A solution to a data processing problem for an organisation such as: membership systems (e.g. clubs, gyms) booking systems for organisations such as holiday companies or medical appointments stock control systems; student timetabling and school reporting systems. The solution of an optimisation problem, such as production of a rota, shortest-path problems or route finding. A computer game An application of artificial intelligence or investigation into machine learning algorithms

Selecting a project – Some ideas A control system operated using a device such as an Arduino board, Raspberry Pi or robotic arm. A website with dynamic content, driven by a back-end database. Note that the creation of the website will not be sufficient for A Level. Rendering a three dimemsional world on screen. An app for a mobile phone or tablet of a suitable complexity, perhaps chosen from the list above. Exploring large datasets, looking for and visualising correlations.

Stages of project - Analysis Best find a real user as this makes this section easier. You will need – General background information on the organisation or person you are creating the system for. This should be sufficient for a third party to read and understand. A description of the problem with a clear statement that describes the problem area and specific problem that is being solved/investigated An analysis of the critical path of the project in terms of identifying the main stages and the sequence which these should be done and the dependency between the stages. An outline of how the problem was researched, which might include an interview, or questionnaire involving the user/supervisor.

Stages of project - Analysis Best find a real user as this makes this section easier. You will need – Source documents from the current system where relevant, or evidence of research into the chosen aspect of computing. Observation of the existing system where relevant. A list of the user requirements and any limitations A list of general and specific objectives that are realistic, achievable and measurable. Any modelling that helps inform the design stage, which may include graph models, entity-relationship models. Data flow diagrams

Stages of project - Analysis Marked according to these criteria 1)How well the problem has been scoped and whether it has been explained in a way that is easy to understand. 2)Whether there is a fully documented set of measurable and appropriate specific objectives 3)Whether the requirements were identified through proper research and dialogue with the user. 4)Whether the problem has been sufficiently well modelled to be of use in subsequent stages.

Stages of project - Design The overall design, perhaps in the form of a top-down design diagram, system flowchart or entity relationship model A description of the main modules that will make up the system. A description of the data items including data types and structures. A description of the file structures being used. Explanation of the main algorithms that will be used. It may be appropriate to use pseudo code or specific code, for example SQL queries. A sample of rough designs of inputs and outputs including forms and reports. Examples of the design of the Human- computer Interface. An Explanation of an library software that will be used, e.g. scientific or data visualisation libraries

Stages of project - Design An explanation of any database or web design frameworks being used. Marked on how well the solution is explained. 1)Fully explained 2)Adequately explained 3)Partially explained 4)Inadequately explained.

Stages of project – Technical Solution Split in two parts 1.The completeness of the solution. 15 marks. More requirements met – the better the mark. 2.Techniques used: 27 marks. Good efficient code producing working solutions You must include enough evidence to prove that you have fully implemented the design this can include: 1)Self-documenting code, which means code that uses meaningful identifiers, logical structures and annotation (comments) that allows a third party to understand it. 2)An overview guide, which amongst other things includes the names of entities such as executables, data filenames/URLs, database names and pathways.

Stages of project – Technical Solution 3) Explanations of particularly difficult to understand code sections. 4) A carefully division of the presentation of the code listing into appropriately labelled sections. Complexity of solution is awarded in categories A – Most Complex to C – simple NOTE – Tables are available to judge the complexity of your program – See specification. Coding styles is marked according to proficiency – Excellent / Good / Basic

Stages of project – System Testing 1)An overview of the test strategy including an explanation of the test data used (TEST PLAN – Probably best show this in a table) 2)Test data should include normal, boundary and erroneous data. As well as testing individual functions there should be whole system tests (Scenario testing) that help prove the original objectives of the system, have been met. 3)Evidence that tests have been carried out including annotated hard copies 4)All possible outcomes should be tested with a table to show expected and actual outcome. 5)Samples of screenshots or actual printouts as evidence.

Stages of project – Evaluation 1)Copy the original objectives that you wrote in the analysis section. Go through each and explain whether you met the objective, explain how effectively it was met and if you did not meet the objective, explain why not. 2)Give your user a chance to use the system and ask them for general and specific comments. Don’t invent the user/supervisor feedback – it will be obvious. 3)Address the user/supervisor feedback explaining how may incorporate any changes they have requested. 4)Based on these comments and your own opinions, identify any ways in which the system could be improved or enhanced.

Additional info. Refer to your notes on the Software Development life cycle work you did at AS level. Read chapter 48 and 49 in your text books.