Example Structure/Template for the A Level CS H446 NEA

Section 1 – Analysis

Remember to always aim for the top mark band:

9-10 marks: Described and justified the features that make the problem solvable by computational
methods, explaining why it is amenable to a computational approach.

9-10 marks: Identified suitable stakeholders for the project and described them explaining how they
will make use of the proposed solution and why it is appropriate to their needs.

9-10 marks: Researched the problem in depth looking at existing solutions to similar problems,
identifying and justifying suitable approaches based on this research.

9-10 marks: Identified the essential features of the proposed computational solution explaining
these choices.

9-10 marks: Identified and explained with justification any limitations of the proposed solution.

9-10 marks: Specified and justified the requirements for the solution including (as appropriate) any
hardware and software requirements.

9-10 marks: Identified and justified measurable success criteria for the proposed solution.

Problem Definition

1. The problem statement – this should be a short paragraph.

2. Stakeholders, who will use it?
3. Decompose the problem (break it down to show how the problem is solvable through
computational methods).
4. Interviews/ Requirement gathering… however you want to do this is up to you…
questionnaires, interviews…. key thing is to analyse all the information you get.
5. Transcribe or show info gathered then analyse what it means for your project.
6. Research into other problems… what other similar applications are out there and how do
they work, what features do you want to take from them or improve?
7. Hardware requirements, what hardware or software is required to run this app?
8. What do the stakeholders want in terms of the design of the app and functionality.
9. LIST SUCCESS CRITIERA… these are your business cases e.g. users can search a stock and
analyse its price, users can buy a stock in the simulation, they can login etc.
Example Structure/Template for the A Level CS H446 NEA

Section 2 – Design

Remember to always aim for the top mark band:

13-15 marks: Broken the problem down systematically into a series of smaller problems suitable for
computational solutions, explaining and justifying the process.

13-15 marks: Defined in detail the structure of the solution to be developed.

13-15 marks: Described the solution fully using appropriate and accurate algorithms justifying how
these algorithms form a complete solution to the problem.

13-15 marks: Described, justifying choices made, the usability features to be included in the solution.

13-15 marks: Identified and justified the key variables data structures classes (as appropriate to the
proposed solution) justifying and explaining any necessary validation.

13-15 marks: Identified and justified the test data to be used during the iterative development of the
solution.

13-15 marks: Identified and justified any further data to be used in the post development phase.

1. User Interface design: Draw wireframes for each screen and describe each button or feature
saying how they link to success criteria
2. Justify and explain each screen, why is it there, how does it help to find a solution to your
problem?
3. How have you made your application usability, have you thought about user experience.
Justify and explain why the screens are like that
4. Get stakeholder input on the designs, analyse this feedback and change the designs
5. Algorithms — Describe any complex algorithms that you want to design to put into your
project, link to success criteria. Show pseudocode to give an idea of how the algorithms will
work.
6. Justify and explain the algorithms how they will be developed and how you will break the
algorithm down so you can develop.
7. Show a USE CASE and UML Class diagram of how the code in the app will
function Summary of Use Case and Class Diagrams (youtube.com)
8. Show how the flow of the actions lead into other screens DFD diagram or just from your
design of screen show the functions and code that will be run 4 — Data Flow Diagrams —
Unit 23 Systems Methodologies (youtube.com)
9. Show Data dictionaries highlight all the variables you will use CASE Tools Data Dictionaries
Decision Tables Screen Design (youtube.com)
10. Show decision tables where necessary to describe the algorithms or key choices Tools Data
Dictionaries Decision Tables Screen Design (youtube.com)
11. For any databases show database schema ERD diagrams Entity Relationship Diagrams
(youtube.com) how to make one How to make an Entity Relationship Diagram
(youtube.com)
12. Design your testing table, show how you will comprehensively test your application,
describe how else you will test it?
Example Structure/Template for the A Level CS H446 NEA

Section 3 – Development & Testing

Remember to always aim for the top mark band:

13-15 marks: Provided evidence of each stage of the iterative development process for a coded
solution relating this to the breakdown of the problem from the analysis stage and explaining what
they did and justifying why.

13-15 marks: Provided evidence of prototype versions of their solution for each stage of the process.
The solution will be well structured and modular in nature.

13-15 marks: Code will be annotated to aid future maintenance of the system. All variables and
structures will be appropriately named.

13-15 marks: There will be evidence of validation for all key elements of the solution.

13-15 marks: The development will show review at all key stages in the process.

• An iterative detailed description explaining and justifying why you have written he code you
wrote in there…break the project down into stages or sprints saying what you delivered and
how you tested it at the end of each stage.
• Show how you tested each part that you developed, you need to keep a record of all the
parts you developed, what went wrong and how you fixed the bugs.
• You should show why you made the code easily adaptable and maintainable
• You should explain in detail how you developed all the algorithms you said you were going
to write in your design
• At the end of each stage of development describe: What has been done, how it has been
tested, how it meets your success criteria, whether you changed the design or not, where
you are in the project what else needs to be done

Basic Structure: Documenting the milestones

1. For each milestone, include the following:
2. Objective of the milestone: In one or two sentences, describe what this milestone achieves.
3. Code listing: Provide a listing of the code for this milestone. Code must be commented with
appropriate variable and data structure names.
4. Explanation of the code: Explain what the code section does and justify algorithms or
approaches. It might not be immediately obvious to an examiner how the code works or why
problems have been solved in the way they have. Remember, the examiner may not be
familiar with the language you are using. If input validation is required, explain that too.
5. Module testing: Explain the tests you performed for this section of code and the outcome of
those tests. You will likely be playing the game and tweaking the variables a lot to get the
outcome you want. You should provide evidence of this process.
6. User feedback: Your user should tell you what they like and dislike about this aspect of the
development so far, with ideas for future development. Your user must be an integral part
of the iterative development process.
7. Reflections: As a result of playtesting and user feedback, discuss what needs to be changed.
Example Structure/Template for the A Level CS H446 NEA

Section 3 – Testing for development & testing to inform evaluation

Remember to always aim for the top mark band:

(Testing for dev) 9-10 marks: Provided evidence of testing at each stage of the iterative development
process.

(Testing for dev) 9-10 marks: Provided evidence of any failed tests and the remedial actions taken
with full justification for any actions taken.

(Testing for eval) 5 marks: Provided annotated evidence of post development testing for function
and robustness.

(Testing for eval) 5 marks: Provided annotated evidence for usability testing.

• Final Testing — You need to carry out the tests you designed in the design section saying
whether or not they passed and the application meets the success criteria. Describe the
tests in detail highlighting where the tests went wrong and what you need to do to fix them.
• Stakeholder or user testing — Hand the application to the users and let them play with it.
You need to monitor them then interview them again like you did for design to fully
understand the things that went well or not so much.

Section 3 – Evaluation of solution

Remember to always aim for the top mark band:

13-15 marks: Used the test evidence to cross reference with the success criteria to evaluate the
solution explain how the evidence shows that the criteria has been fully, partially, or not met in each
case.

13-15 marks: Provided comments on how any partially or unmet criteria could be addressed in
further development.

13-15 marks: Provided evidence of the usability features justifying their success, partial success, or
failure as effective usability features.

13-15 marks: Provided comments on how any issues with partially or unmet usability features could
be addressed in further development.

13-15 marks: Considered maintenance issues and limitations of the solution.

13-15 marks: Described how the program could be developed to deal with limitations and potential
improvements changes.

13-15 marks: There is a well-developed line of reasoning which is clear and logically structured. The
information presented is relevant and substantiated.
Example Structure/Template for the A Level CS H446 NEA

1. List all the success criteria and say whether or not you met it
2. Show evidence of each success criteria being met by showing screen shots and detailed
descriptions
3. Explain and justify why you did or did not meet the success criteria
4. Explain and justify how usable your application is to users, what could be improved

Limitations

• Show that you can be critical of your work, show what you think worked well and what did
not.
• Describe how you can improve it by giving solutions. Justify and explain it.

Maintenance

• How will you plan to maintain and update the application? Why? Justify and explain