Advanced Higher Computing Science The Project Introduction Worth

Introduction Worth 60% of the total marks for the course Must include: • An

Project proposal • Project idea • End-user group • Discussion with assessor

Project Plan 1. 2. 3. 4. 5. Research Description of project (Functional requirements) Resources

Project Plan: 1 Research • Background to the project • Look at existing products

Project Plan: 2 Description Describe your project as an answer to the question: What

Project Plan: 3. Resources • Access to individuals / organisations/ Web resources • Hardware

Project Plan: 4 Timetable 1. Project plan (10 marks) 2. Requirements specification (10 marks)

Project Plan: 5 Record of Progress Diary / Blog Include screengrabs and scans of

Requirements Specification 1. 2. 3. 4. Purpose Scope and Boundaries User requirements Detailed functional

Requirements Specification 2: Scope and Boundaries Scope: What your solution will be able to

Requirements Specification 3 : User requirements • End users • Clients • Content providers

Requirements Specification 4: functional requirements • Interface • Coding / Scripting requirements • Data

Requirements Specification 5: Inputs and Outputs • Input data from: § External file §

Requirements Specification 6: Test Plan • What is to be tested • How it

Interface Design • Screen layouts • Interrelation of screen layouts • Input validation and

Program Design Use an appropriate design methodology • Top level design (pseudocode) • Refinement

Data structure design • Variables ( arrays, records, lists etc. ) • Files •

Implementation Include at least two from: • 2 -D arrays or arrays of records

Implementation Document your progress Keep track of your time (20 marks = 18% of

Testing During implementation • Component testing: use stubs and drivers • Integration testing After

Evaluation • The solution: • Fitness for purpose (requirements specification) • Interface (end user

Presentation • Can be paper / electronic or both • Must be clear and

Submission deadlines: • • • Project proposal Project plan Interface design Requirements Specification Program

Slides: 24

Download presentation

Advanced Higher Computing Science The Project

Introduction Worth 60% of the total marks for the course 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)

Project proposal • Project idea • End-user group • Discussion with assessor

Project Plan 1. 2. 3. 4. 5. Research Description of project (Functional requirements) Resources Timetable (Gannt Chart) Record of Progress

Project Plan: 1 Research • Background to the project • Look at existing products / technologies • Survey of potential users • Online research • Feasibility study • Select a strategy

Project Plan: 2 Description Describe your project as an answer to the question: What will your completed solution be able to do?

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

Project Plan: 4 Timetable 1. Project plan (10 marks) 2. Requirements specification (10 marks) 3. Interface design (10 marks 4. Program / Data structure design (10 marks) 5. Implementation (20 marks) 6. Testing (10 marks) 7. Evaluation (10 marks) 8. Report (10 marks)

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

Requirements Specification 1. 2. 3. 4. Purpose Scope and Boundaries User requirements Detailed functional requirements • Interface • Coding • Data structures 5. Inputs and Outputs 6. Test Plan

Requirements Specification 2: Scope and Boundaries Scope: What your solution will be able to do Boundaries: What your solution will not be able to do

Requirements Specification 3 : User requirements • End users • Clients • Content providers • Administrators

Requirements Specification 4: functional requirements • Interface • Coding / Scripting requirements • Data structure requirements

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

Requirements Specification 6: Test Plan • What is to be tested • How it is to be tested • Test data and expected results

Interface Design • Screen layouts • Interrelation of screen layouts • Input validation and expected outputs • Detailed description and reasons for design decisions • Accessibility

Program Design Use an appropriate design methodology • Top level design (pseudocode) • Refinement of sub programs

Data structure design • Variables ( arrays, records, lists etc. ) • Files • Data flow between modules / sub programs

Implementation 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

Implementation Document your progress Keep track of your time (20 marks = 18% of total)

Testing During implementation • Component testing: use stubs and drivers • Integration testing After implementation • Use your original test plan • Test documentation • Corrective Maintenance

Evaluation • The solution: • 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

Presentation • Can be paper / electronic or both • Must be clear and well structured. • Must include comments on any legal, ethical, economic, environmental or social implications • Include your documentation from all previous 7 stages

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 Final presentation