Advanced Higher Computing Science The Project

In this session we will look at the 8 stages in preparing, implementing and submitting your project.

Learning content What is the Project? Project proposal Project Plan Requirements Specification Implementation Testing Presentation Evaluation

Worth 60% of the total marks for the course (90 marks) Must include: Introduction Worth 60% of the total marks for the course (90 marks) Must include: An appropriate interface using input validation Interaction with stored data A minimum of two from: standard algorithms (binary search, sorts, recursion) data structures (linked list, queues, stacks) data processing (SQL) web development (HTML forms, scripting) 3 sorts insertion selection with 2 lists and bubble

Discussion with assessor Project proposal Project idea End-user group Discussion with assessor You will already have come up with an idea, and checked with your teacher that it is both feasible and at a suitable level of complexity. The end user group is important because it determines the user interface and also influences your test plan.

Description of project (Functional requirements) Resources Project Plan Research Description of project (Functional requirements) Resources Timetable (Gannt Chart) Record of Progress You are bound to have to make changes to your plan as the project progresses. It is important that you document these changes and the reasons for them.

Project Plan: 1 Research Background to the project Look at existing products / technologies Survey of potential users Online research Feasibility study Select a strategy Look at a variety of different ways of building your program - what programming languages / technologies could you use? Consider several different solutions in your feasibility study.

Project Plan: 2 Description Describe your project as an answer to the question: What will your completed solution be able to do? This is a functional description – what it will do rather than how it will do it. ie. Your program from the point of view of the client / user

Project Plan: 3 Resources Access to individuals / organisations/ Web resources Hardware and Software Data storage requirements Access to web services: Web server Database server Mail server Backup strategy List possible resources. You don't necessarily have to use them all.

Project Plan: 4 Timetable Project plan (10 marks) Requirements specification (10 marks) Test plan (10 marks) Interface design (10 marks) Program / Data structure design (10 marks) Implementation (20 marks) Testing (10 marks) Evaluation (10 marks) Be prepared for your timetable to be flexible, so allow for unforeseen problems if you can. There are a variety of Gantt charting programs available. https://www.ganttproject.biz/

Project Plan: 5 Record of Progress Diary / Blog Include screengrabs and scans of sketches where possible Make regular notes: Research done Problems encountered / solved Decisions made Help given / resources used Using a blog means that you can add to it whether you are at school or at home. Your teacher will be able to see it and comment. If they use an aggregator they will be able to see whenever you make a new post. Your record of progress will be an invaluable resource when you come to write up your evaluation final presentation

Requirements Specification Scope and Boundaries User requirements Detailed functional requirements Interface Coding Data structures Inputs and Outputs This is how your project will work rather than just what it will do.

Requirements Specification 1: Scope and Boundaries Scope: What your solution will be able to do Boundaries: What your solution will not be able to do Example of ecommerce database – no of simultaneous users, no of products,

Requirements Specification 2: User requirements End users Clients Content providers Administrators Consider all users, not just the customers they might need different interfaces and different levels of security / access

Requirements Specification 3: Functional requirements Interface Coding / Scripting requirements Data structure requirements You will be producing more detailed material later on, so consider this at top level You might want to create a top level structure diagram to show the expected program structure. You also need an overview of the data requirements – data stored externally, either on file or in a database

Requirements Specification 4: Inputs and Outputs Input data from: External file Database User Output data to: Screen

How will results be recorded? Test data and expected results Test Plan What is to be tested? Input validation End user testing How it is to be tested? How will results be recorded? Test data and expected results The test plan should test both functional and non-functional requirements and include criteria for end-user testing.

Interrelation of screen layouts Input validation and expected outputs Interface Design Screen layouts Interrelation of screen layouts Input validation and expected outputs Detailed description and reasons for design decisions Accessibility Make sketches of the interface, or use wireframe software to design it. For real commercial projects clients will often be provided with a variety of interface designs / wireframes so that they can evaluate them. You may wish to discuss existing user interfaces for similar programs and their advantages and disadvantages Show inputs and outputs on your interface e design Remember to include accessibility in the design of your interface

Use an appropriate design methodology Top level design (pseudocode) Program Design Use an appropriate design methodology Top level design (pseudocode) Refinement of sub programs If you are using an object oriented programming language then use UML class diagrams and use case diagrams You may also wish to use structure diagrams and Data flow diagrams

Variables ( arrays, records, lists etc.) Files Data structure design Variables ( arrays, records, lists etc.) Files Data flow between modules / sub programs Your data structure design will depend on the nature if your project. If you are using a database to store external data then the record structure will need to be documented

You must include at least two from: 2-D arrays or arrays of records Implementation Your implementation must match your design. Document changes as they are implemented You must include at least two from: 2-D arrays or arrays of records linked lists, queues or stacks a binary search, a sort algorithm or other coding of similar complexity recursion form structure using HTML form processing using client-side or server-side scripting appropriate SQL operations You should not be tempted to create your design after implementation This is a minimum requirement, however "other coding of similar complexity" is broad enough to allow some flexibility Remember you must also implement a user interface with input validation and your program must interface with stored data of some sort (database or file)

Implementation Document your progress Keep track of your time (20 marks = 18% of total) Documenting progress Is very important. Particularly if there are major changes to your plan. Although there are bound to be changes to your plan as the project develops, don't wait until y8ou have completed your project before writing up the design Its very easy to devote more time to this than the marks are worth.

During implementation Component testing: use stubs and drivers Integration testing After implementation Use your original test plan Test documentation Corrective Maintenance It is very important that you document your testing both during and after implementation. You need to get your users to test your program both as beta testers but also to do usability testing on the interface. Questionnaires are useful for collecting user reactions. If you do have to make changes, remember that these will have to be tested and documented by referring back to your design as well Keep your diary of progress up to date

Evaluation The solution: Your performance: Possible next steps Fitness for purpose (requirements specification) Interface (end user requirements) Maintainability (test results) Your performance: Refer to your record of progress Successes and failures Lessons learned Responses to Feedback Possible next steps

Can be paper / electronic or both Must be clear and well structured. Report Can be paper / electronic or both Must be clear and well structured. Include the documentation from every stage Your tutor will want to see your program working and will ask you questions about it.

Submission deadlines: Project proposal Project plan Interface design Requirements Specification Program and data design Documented Code (solution on CD or web) Test plan and results Evaluation Record of Progress Check with your tutor for deadlines! http://www.sqa.org.uk/files_ccc/GAInfoCompScience.pdf

Thank you Please complete the online evaluation form