A–Level Computing Project Introduction. Learning objectives Become familiar with the: Guidelines associated with choosing a project. Stages in project.

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

Definitions types added-value tutor role building-up informal learning awareness raising examples 1 Astrid Quasebart ESTA-Bildungswerk gGmbH senior project.
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
Title Page. Over course of two years you will complete 6 units. These will include: five portfolios Unit 1 – Using ICT to communicate Unit 3 - ICT for.
Managing a Club A club is trying to persuade more people to take part. Some features of the club are: Open to all ages Takes part in competitions and.
1 SESSION 3 FORMAL ASSESSMENT TASKS CAT and IT FORMS OF ASSESSMENT.
System Design and Analysis
introduction to MSc projects
Project Workshops Project Oral. 2 Supervisor plus one other member of academic staff Between final paper submission and exams (usually weeks 21-22) Maximum.
Research Methods for Business Students
CS350/550 Software Engineering Lecture 1. Class Work The main part of the class is a practical software engineering project, in teams of 3-5 people There.
Software Development, Programming, Testing & Implementation.
IT Job Roles Task 20. Software Engineer Job Description Software engineers are responsible for creating and maintaining software of various different.
"In the name of ALLAH, most Gracious, most Compassionate".
Introduction to Systems Analysis and Design Trisha Cummings.
Foundation Degree IT Project Methodologies (for reference)
AICT5 – eProject Project Planning for ICT. Process Centre receives Scenario Group Work Scenario on website in October Assessment Window Individual Work.
1 BTS330 Vision & Scope. 2 IT Projects What defines project success? On time Within budget Delivers what the clients want The reality Less than 20% of.
1 Shawlands Academy Higher Computing Software Development Unit.
Foundation Degree IT Project Milestone 3: Implementation, Testing and Evaluation.
Software Engineering 2003 Jyrki Nummenmaa 1 REQUIREMENT SPECIFICATION Today: Requirements Specification Requirements tell us what the system should.
Topic 4 How organisations promote quality care Codes of Practice
SE-02 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it. Requirements.
End HomeWelcome! The Software Development Process.
Feasibility Analysis What is feasibility and when should feasibility checkpoints occur? What are the four types of feasibility and what is the description.
1 The Software Development Process  Systems analysis  Systems design  Implementation  Testing  Documentation  Evaluation  Maintenance.
Software Engineering – University of Tampere, CS DepartmentJyrki Nummenmaa REQUIREMENT SPECIFICATION Today: Requirements Specification.
There are many occasions for fact-finding during the database system development lifecycle. fact-finding is particularly crucial to the early stages of.
BSc Honours Project Introduction CSY4010 Amir Minai Module Leader.
BSc Honours Project Introduction CSY4010 Amir Minai Module Leader.
Babcock 4S Limited PSHE INSET Sarah Lyles – PSHE Curriculum Consultant
IT Job Roles & Responsibilities Shannon Ciriaco Unit 2:
Systems Life Cycle. Know why it is necessary to evaluate a new system Understand the need to evaluate in terms of ease-of- use, appropriateness and efficiency.
COMP 208/214/215/216 – Lecture 8 Demonstrations and Portfolios.
Intermediate 2 Software Development Process. Software You should already know that any computer system is made up of hardware and software. The term hardware.
ASSIGNMENT 2 – Market Research and business plan.
The Software Development Process
BSc Honours Project Introduction CSY4010 Amir Minai Module Leader.
The Foundation Degree Project Geoff Leese September 2008.
Attending Meetings at School Louise Mottershead Aspire North West 2015.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
IS2210: Systems Analysis and Systems Design and Change Twitter:
Business Project Nicos Rodosthenous PhD 08/10/2013 1
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
Research Methods in Psychology Introduction to Psychology.
Planning AS 2.1 SUS 201 Plan, implement and evaluate a personal action that will contribute towards a sustainable future. 6 credits.
A2 Agreement Trial ICT November Outline Agenda  Welcome and introductions  10.05Travel Expenses  Outcomes and Issues  10.45Coffee.
BSc Honours Project Introduction CSY4010 Amir Minai Module Leader.
SYSTEM ANALYSIS AND DESIGN LAB NARZU TARANNUM(NAT)
Software Design and Development Development Methodoligies Computing Science.
A2 Agreement Trial ICT November Key Points from Moderation  Majority of centres applied the assessment criteria successfully  Tasks selected and.
Fifth Edition Mark Saunders, Philip Lewis and Adrian Thornhill 2009 Research Methods for Business Students.
Year 8 Clock Project Design & Technology Design Brief You are to design & make a 3D clock that is aesthetically pleasing and could be sold to a specific.
A2 Agreement Trial ICT November AGENDA  New Specification Principal Moderator’s Report Exemplar Materials  Lunch  1.00 Exemplar Materials.
1 International Institute of Business Analysis Vision: The world's leading association for Business Analysis professionals” Mission: To develop and maintain.
School of Engineering and Information and Communication Technology KIT305/607 Mobile Application Development Week 7: Usability (think-alouds) Dr. Rainer.
MANAGEMENT INFORMATION SYSTEM
How can we help our neighbours? BAMBOO BIRTH Research project: Assessment Criteria – Planning (P), Research (R), Development (D), Evaluation (E) Due: 4.
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.
Advanced Higher Computing Science
A Level Computer Science
COMP390/3/4/5 Final Year Project Introduction & Specification
Research Methods for Business Students
Coursework: The Use of Generic Application Software for Task Solution
THE BUSINESS ANALYSIS PROCESS MODEL
Foundation Degree IT Project
Chapter 49 Non-Exam Assessment.
COMP390/3/4/5 Final Year Project Introduction & Specification
Applied Software Project Management
An overview of course assessment
Presentation transcript:

A–Level Computing Project Introduction

Learning objectives Become familiar with the: Guidelines associated with choosing a project. Stages in project development. ‘GUIDANCE ON MARKING THE COMPUTING PROJECT’ in the syllabus. Be able to choose a suitable project.

SCHEME OF ASSESSMENT The computing project is a major part of the A2 specification (40%).

General Description Do not underestimate the volume of work expected. While the degree of difficulty is largely decided by you and by the problem to be solved, the time required to produce a first class piece of work is considerable. Despite having almost a year to complete the work, there is no room for time wasting.

Computing Techniques The degree of difficulty of computing techniques employed in completing the solution is secondary to the analysis and design of the circumstances surrounding the problem and the implementation of the proposed solution, along with the testing to ensure its satisfactory performance. You are expected to play the part of the systems analyst This emphasis on the aspects of problem solving other than the software development can be illustrated by reference to the mark distribution. Only 18 of the 60 marks (c.30%) are available for implementing the solution that has been designed and of those 18 marks fewer than half are for manipulating a software package, or for writing original software. Only 18 of the 60 marks (c.30%) are available for implementing the solution that has been designed and of those 18 marks fewer than half are for manipulating a software package, or for writing original software.

Design Evaluation Definition, Investigation and Analysis Software development, testing & implementation

Definition, Investigation and Analysis: Definition - nature of the problem (3) Definition - nature of the problem (3) Investigation and analysis (8) Investigation and analysis (8)

Design: Nature of solution (7) Nature of solution (7) Intended benefits (2) Intended benefits (2) Limits of the scope of the solution (2) Limits of the scope of the solution (2)

Software development, testing & implementation: Development and testing (9) Development and testing (9) Implementation (6) Implementation (6) Appropriateness of structure and exploitation of available facilities (3) Appropriateness of structure and exploitation of available facilities (3)

Documentation: Technical documentation (6) Technical documentation (6) User guide (6) User guide (6)

Project Selection The project is a single problem which needs to be followed through over a long period of time. Because of this, considerable thought must be given to the selection of a suitable problem, that selection being dictated by a number of criteria.

Syllabus fit A-Level Computing Project Guidance pdf document pdf document Familiarise yourselves with this and choose a problem the solution to which will require you to complete all the sections mentioned. The purpose of the marking section in the syllabus is to act as a guide, indicating what is expected at each stage, it is not intended to be a strait jacket and you should realise that many types of project are possible.

Identifying possible extensions to your project Select a problem whose solution is within your capabilities, but do not imagine that the whole solution will be possible during the time that you have available. Indeed, if the solution is complete, you will be penalised because the final mark points are awarded for identifying possible extensions to your project. Many of the marks in the scheme are awarded for the you identifying the need for a partnership between the owner of the problem and the analyst (you). If there is no real end user, the student is severely handicapped when it comes to the marking.

Real end user The problem should be real and consequently the person who has the problem should be real. The end-user is the expert (along with other members of the organisation) in the problem and what has given rise to it. The systems analyst (you) are the expert in computing and the limitations that are inherent in any computer solution to a problem. The interaction between the end-user and the student forms the major part of the project.

The end-user should be involved throughout the project The end-user should not be thought of as someone who is prepared to give time to be interviewed about the problem and then will try to use the solution 9 months later. At different stages you should keep the end-user involved so that they develop an ownership of the solution and that they feel to be important to the project. It is a good idea, for example, if the prototypes of the different parts of the solution are shown to the end-user and then altered according to their comments.

Exceptions However, such a goal is not always possible because of individual circumstance. In such cases, the use of family members or members of staff within school is perfectly acceptable, but the student should try to maintain a professional relationship with the person being used in order to make the experience as real as possible. Try not to use fellow students as end users because rarely would the problem be real and the fact that you are both students make it impossible to create the professional, working relationship so essential to this project.

Interest You will be working on the problem for a long time. It is essential that there is plenty of scope for maintaining your interest. The project of the football club is unlikely to be suitable because it is about football, although it may be if the local football club is considering computerising its manual filing system because the national association states that information in the future must be in electronic form. This is a real problem, and the choice of project has changed from a choice based on football to a choice based on the solution of a problem.

A little knowledge is a dangerous thing Be aware of choosing something you know something about. This will make the analysis and the information collection very tricky. This will make the analysis and the information collection very tricky. Try to choose a project about which you have no knowledge so that you are forced to find out enough to solve the problem, meaning all the marks will be available. If you have the knowledge already you are likely not to include it in the documentation because you assume that such knowledge is general. If you have the knowledge already you are likely not to include it in the documentation because you assume that such knowledge is general.

Hardware and software You should have some idea what is going to be required by the solution; otherwise there is the danger that half way through the solution it is found that the hardware or software required to complete the solution is not available. If you stick to the basic data handling type of project then such problems are unlikely to arise (unless the solution involves specialist hardware like barcode readers), but if the problem requires a solution which is a bit more unusual, then care should be taken to anticipate problems before they arise.

Problems that may arise Do not worry about problems that arise during the solution. If the project is a real one, there will be problems. If the project is a real one, there will be problems. Parts of the solution may not work as anticipated leading to revisiting that part of the analysis. Parts of the solution may not work as anticipated leading to revisiting that part of the analysis. Hardware may malfunction at particularly inopportune times. Hardware may malfunction at particularly inopportune times. Such problems should be logged and the solution should be part of the final report.

Hints on finding a ‘third party’ user: Look at manual systems, partially computerised systems, fully computerised systems. Consider clubs and societies, small businesses, charities, school/college. Find a suitable problem to solve for another person Ask family, friends, neighbours, employers, teachers etc.

Sample Project A snooker club called Smiley’s Snooker. It is a private club with 20 snooker tables and about 400 members. It is a private club with 20 snooker tables and about 400 members. 300 of these are Seniors (over 18 years of age) and 100 are Juniors. The club is open from am to pm each day. There is no booking system at present. There is no booking system at present. Members just turn up and ask to play. Members just turn up and ask to play. The part of the business that Smiley's has asked you to computerise is handling the allocation of tables and to keep a record of the membership of the club. The part of the business that Smiley's has asked you to computerise is handling the allocation of tables and to keep a record of the membership of the club.

Brainstorm Brainstorm ideas for projects and users. Are they suitable?

Homework Choose a project! Choose a project!