Edited by Christopher Douce, Tuesday 17 November 2026 at 07:14
If you create a software product as a part of your project, a really good project report will describe how you have thoroughly tested what you have built.
Testing can be thought about in two different ways. The first is strategically. In other words, your testing strategy can be considered to be your overall testing approach, and how it relates to the aims and objectives of your software product. The other approach is, perhaps unsurprisingly, tactical. Tactical testing can be thought of the groups of tests that you use to either identify or solve a problem. A test strategy is your overall approach or plan. Tactical tests help you to complete your plan.
Figure 1 also shares a really useful way to think about testing. This figure which has been drawn from a level 1 module, TM113 Computing Fundamentals 2: programming, databases and software engineering.
Figure 1 Testing v-model
You will clearly see that it is split into two parts. Validation relates to the question of ‘are we building the right thing?’ Verification, on the other hand, relates to the question ‘are we building it right?’ In other words, are we going about our engineering or software development the right way.
Concerning requirements
The term requirements can be seen at the very top of Figure 1. Your requirements should guide what tests you carry out. Your requirements should also be traceable across all the phases of your project; your examiner should be able to see exactly where they have come from. They might come from something that a potential user said during an interview, or from a document you have found – try to be as clear as you can.
A practical tip: create an appendix that contains a single table that contains all your software requirements. In your requirements table, give each of your requirements a unique identifier or number (perhaps FR1 for a functional requirement, or NFR1 for a non-functional requirement), and use these identifiers throughout your project. In your project report, refer your examiner to your requirements table.
Acceptance testing
In Figure 1, you will see the term acceptance testing, on the opposite side to requirements. If a software product passes a set of acceptance tests, it is deemed to do what it is supposed to do; it is accepted by whoever commissioned it. In your project you are unlikely to carry out an acceptance test, but you may wish to carry out one or more usability evaluations.
If you are interested in the topic of acceptance testing and whether it might apply to your project, a useful tool to look at is Cucumber. Accompanying this tool is a domain specific language which allows you to express high level tests.
Usability evaluations
The aim of a usability evaluation is to determine whether a software product meets the needs of a particular user (or set of users) and helps to solve a particular problem. A usability evaluation could be carried out toward the end of a project to determine whether (or not) the project was a success, or as a part of a series of design and development iterations to gather some useful information about how a design might potentially be improved. Although a usability evaluation can be used to determine whether a product or a design meets a set of requirement, if used well, it can also be used to uncover and identify new requirements, or requirements that had been overlooked.
In very simple terms, there are usability evaluation paradigms (or approaches) that require people, and there are those that do not. Here is a summary of the three paradigms that are highlighted by Preece et al. in their textbook Interaction Design: beyond human-computer interaction:
Heuristic evaluation. A heuristic is a rule of thumb. With heuristic evaluation, you scrutinise your user interface design to determine whether it satisfies a set of well know design principles. A heuristic evaluation is typically carried out by a usability expert who is familiar with interface design principles. In terms of your project, you can apply design principles to your own interface design, and comment on what you have learnt.
Cognitive Walkthrough. This technique is all about putting yourself in the shoes of a potential user and asking some really simple questions, such as will the user know what to do, and will the user receive effective feedback?
Usability testing. Usability testing is where you recruit one or more participants to use your software product to complete a particular task. Whilst a usability test is taking place, you record the actions that the user takes, and any final result.
To do a usability evaluation well, you need to do some planning. To help you to plan, Preece et al. introduce a useful framework which they have called DECIDE. Here is what each of the letters in the DECIDE framework stand for:
D: Determine the goals for an evaluation. What is the overall aim of your evaluation? What are its goals?
E: Explore the questions. What questions will be you attempting to answer? Are you going to be carrying out an evaluation that determines whether some usability or user experience goals have been met?
C: Choose an evaluation paradigm. Usability evaluation can be carried out using different approaches. Which approach will you use? Usability testing is a common approach where you might observe what users do when they use a software product.
I: Identify practical issues. How might you go about recruiting participants? What tasks will they perform? How will your record what they do? Will you write things down, or will you use some kind of tool that records their interactions? You will need to create some kind of resources to make sure your evaluation runs smoothly.
D: Decide how to deal with ethical issues. When working with real users (or proxy users; people who pretend to be real users) you need to give them as much information as possible, which means that you will need to prepare an information sheet. You will also need a consent form to protect your participant as well as yourself.
E: Evaluate, interpret and present the data. This final stage is about figuring out what has happened, and whether you have answered your questions.
To use DECIDE, you should work through each step. Your decision about which evaluation paradigm you adopt may well be guided by the resources that you have available.
Usability testing
If you decide you would like to carry out a usability test, you need to pay attention to step I, identify practical issues, carefully. The first thing that you need to do is to recruit potential participants. It is okay to ask friends and family to help, who could take on the role of proxy users (participants who pretend to be real users).
If your project is linked to your workplace, you may want to ask some co-workers to help with your usability test, but do be aware of the ethical issues of doing this (which is, of course, the next letter in the DECIDE framework).
Three questions to ask are:
Is there any issue regarding power? Are you their line manager?
Will involvement in your project them away from their work in a significant way?
Do you have permission from their line manager to approach them?
A personal recommendation is to avoid recruiting complete strangers. There is a simple reason for this. Although your project is a real demonstration of your skills and abilities, it remains artificial in the sense that it is primarily a vehicle for academic study and personal development. Involving a wider group of participants exposes you to risks, which can only be address through a more rigorous and formal ethics process.
When preparing for your usability test, it is important to create some materials:
Prepare an information sheet. The aim of this is to tell the participant what will happen during the usability test. Send each participant a copy of this single page summary before the evaluation begins.
Prepare a consent form. This is a short form is used to gain consent from your participant to carry out your usability test. In the form, tell them that their participation is entirely voluntary and they can stop the usability test at any point without any consequences or judgement. Do highlight the different ways that data is collected, and how it will be used.
Prepare a list of tasks or instructions. You might even need to write a short script to tell your participant what to do. This is to ensure that every participant is asked exactly the same questions.
Prepare a data collection form. A form can be useful to structure any notes that you might take during a usability test. You might use a table. On the left there might be a summary of the task, on the right might be space to make some notes.
In your project report, you should share all the resources you have created in your report. You might provide an example in the body of your report, or provide one or more appendices; it is up to you.
Although user testing is often thought of a technique that can be applied to a functioning system or product, it can also be applied to evaluate a prototype or an interim design. It is possible to carry out user tests using mock-ups of interfaces created using tools such as PowerPoint, or even using paper sketches of interfaces. Rather than having a computer present the next step in an interaction sequence, you could pretend to be the computer or mobile device, presenting a participant with the next steps.
After you have completed a usability test, you need to find some way to summarise and then to analyse your data. You might provide a sample of the data in the body of your report, and provide all the important or notable data in an appendix, potentially following any appendices that you may have used to share your resources. You might want to comment on limitation of your evaluation, such as, the demographics of any friendly and willing participants you have recruited.
In terms of resources, some really useful guidance is provided within Preece et al.’s Interaction Design text. Useful ethical guidance has been published by the ACM Code of Ethics and Professional Conduct (ACM, 2006) Practice, and the British Computer Society (BCS, 2026).
Accessibility testing
The term accessibility refers to whether a software product can be used by people who have a disability; people who may have sensory or cognitive impairments. Every user-facing software product should have a requirement to be accessible.
If you are creating a product that makes use of web technology, a really useful resource is the Web Content Accessibility Guidelines (WCAG) from the W3C, the organisation that publishes and maintains web standard. Since web pages can be interactive and dynamic, there is also a suite of standards known as WAI-ARIA, the Web Accessibility Initiative Accessible Rich Internet Applications.
Accessibility testing is a specialised version of usability testing. Ideally, every software product should be evaluated by real people, but since this is not always possible, it is important that you consider alternative ways of carrying out accessibility tests.
Here are some practical suggestions of some accessibility tests you could use:
Using a screen reader to determine whether your user interface can be sensibly converted to speech, so it can be used by someone who has a visual impairment.
Using a colour contrast checker to determine whether the your interface can be seen or navigated by someone who has a visual impairment.
Using a keyboard, rather than a mouse or touch screen, to determine whether your interface can be used by someone who has a mobility impairment.
Using an online checking tool to determine whether your interface conforms to the W3C WCAG guidelines.
The W3C has published a useful list of Web Accessibility Evaluation Tools, which you may find useful if you need to carry out an accessibility evaluation. If you use any of these tools, please explain why you have chosen one over another, and also share the details of any output that has been created, perhaps by using an appendix. You should also explain what the output from the tool has told you.
Unit testing
Returning to Figure 1, Unit Testing can be found in the bottom right of the diagram. The diagram shows a firm connection between the software code that you create and unit tests. A unit test can be thought of as a formal requirements specification that is expressed in the language of the programming language that is used to create your software. A unit test typically tests the operation of a function, or group of functions, to make sure they do exactly what is expected of them.
A software development approach that emphasises the importance of testing is called Test-Driven Development (Beck, 2023). The idea is simple. Before you write any code, you begin by writing a test. You then run your tests to check to see that everything fails as expected. You then add code that satisfies your tests. Your unit tests are intended to provide helpful feedback about the state of your software.
One of the benefits of unit testing is that it helps with regression testing. A regression test is a set of tests that are carried out to make sure that a change has not inadvertently introduced any errors or mistakes. If you have a suite of well-designed tests, you can run your tests to make sure that any update or modification has not broken anything.
The most popular unit testing framework is called xUnit, where the letter ‘x’ refers to a different programming language. There is likely to be a unit testing framework for whatever language you choose.
If the creation of software is a priority in your project, it is important to share evidence of unit testing, or to justify why you have decided against it. A practical suggestion is to provide an example of one or more unit tests in the body of your report (to perhaps show you have you tested particularly difficult bits of code), and a screenshot that shows the running of unit tests. You need to also explain what you are testing, and why. The more practical detail you provide in your project report. the happier your examiner will become.
To find out more about unit testing, a good starting place is xUnit. There is also JUnit for Java and PyUnit for Python.
Integration testing
Integration testing is about making sure the different bits of your software system work together. If you are creating a software system that contains one or more microservice, a useful question to ask is: how can I test my microservices? There are some bits of terminology that might be useful. A mock is a bit of software that pretends to be another bit of software. There is also the idea of a test harness, which can exercise bit of software before it is then later integrated with, or connected to other bits of software.
If you create any bits of code that tests other bits of code, do remember to discuss what they are, what you did, and what you learnt. Also remember to share any test harness code within an appendix, along with any configuration files or test data you needed to create.
Integration testing is harder to write about, since every software project is made up of different components. This said, there are some tools that might be useful to look at, such as Wiremock or Playwright if you need to understand more about how to test the different elements of your software product.
Security testing
It is easier to carry out tests against functional requirements than it is to test whether a software product satisfies non-functional requirements. A difficult requirement to test is security.
As useful way to think about security testing is whether test can be performed by people, or whether tests can be automated. Here are two sets of tests that relate to security that people can carry out:
Code reviews. A code review is where a fellow software engineer examines a bit of software before it is formally accepted into a software product.
Pen testing (short penetration testing); a technique where a tester deliberately attempts to gain access to a software product or system. Pen testing is a significant subject in its own right, and requires a lot of specialist knowledge.
There are some automated tools that could be used to help with security testing:
Linters. A linter is a static analysis tool that examines your software code that has been written before it is run. A lint roller will pick up annoying bits of fluff, or lint, from your clothing. A linter is a program that will pick up, or identifies points that might need to be attended to.
If you have studied TM113 Computing Fundamentals 2, you will be already familiar with the idea of a linter, which introduced a tool called Ruff. Linters have been made for different programming languages and different problems. In some automated deployment processes, new program code may be required to be run through linter software before it could be put into production.
If security is an important non-functional requirement, discuss what approach you might take to test your product. If you run aspects of your code through a static analysis tool, do share the results from that tool, and comment on the results you have gathered.
Performance testing
Another important non-functional requirement that you might have considered is performance; you may need your software product to respond with a certain amount of time. Since your project is likely only involve a small number of users, the necessity to address or explore performance isn’t as important as some of the other non-requirements you may have defined.
A beginning point to begin to think about performance is the programming language or languages you may be using. This can dictate the tools you may choose. There is, of course, a link between performance and your chosen software architecture. Some architectures may enable your design to more efficiently respond to changes in demand.
If your software solution makes use of the Java language, a well-known tool is JMeter. JMeter can also be used with the Python language, through PyMeter. The operating system of your computer, and services provided by your cloud computing provider also provides tools to monitor and check performance. You may also wish to find a way to instrument your code; to take some measurements of how long it might take to carry out particular operations.
If performance is a real issue, you may well turn to the topic of debugging. In turn, you may look to the topic of refactoring, and ask whether you need to refactor your code, or even refactor (or change) your software architecture. A final point is that it is important to take measurements to understand what you have, what you may need to change, and the consequence of any changes that you might make. If you take any measurements within your own project, remember to share them in your project report. Your examiner always wants to see your thinking.
Resources
The following blog posts, which relate to other project module topics, might also be helpful:
Testing is a big subject. There are entire suites of industrial qualifications that are dedicated to it. It impossible to test everything in a software project. You need to make practical decisions about what to test, and when to test. In your project report, you need to explain why you have chosen a particular testing strategy, and also show the examiner very clearly what you have done. Do add appendices to share evidence of the tests that you have designed, and the results you have gained; the more detailed they are, the better. The best reports connect testing back to your project requirements. One testing approach will not be enough. You need to study your software system from a number of different perspectives.
Figure 1 the Testing v-model has been drawn from TM113 Computing Fundamentals 2: programming, databases and software engineering. Thanks are extended to the TM113 module team, as well as the TM356 Interaction Design and the User Experience module team. It is through the predecessor module that I first gained awareness of the very helpful DECIDE framework.
TM470 Testing
If you create a software product as a part of your project, a really good project report will describe how you have thoroughly tested what you have built.
Testing can be thought about in two different ways. The first is strategically. In other words, your testing strategy can be considered to be your overall testing approach, and how it relates to the aims and objectives of your software product. The other approach is, perhaps unsurprisingly, tactical. Tactical testing can be thought of the groups of tests that you use to either identify or solve a problem. A test strategy is your overall approach or plan. Tactical tests help you to complete your plan.
Figure 1 also shares a really useful way to think about testing. This figure which has been drawn from a level 1 module, TM113 Computing Fundamentals 2: programming, databases and software engineering.
Figure 1 Testing v-model
You will clearly see that it is split into two parts. Validation relates to the question of ‘are we building the right thing?’ Verification, on the other hand, relates to the question ‘are we building it right?’ In other words, are we going about our engineering or software development the right way.
Concerning requirements
The term requirements can be seen at the very top of Figure 1. Your requirements should guide what tests you carry out. Your requirements should also be traceable across all the phases of your project; your examiner should be able to see exactly where they have come from. They might come from something that a potential user said during an interview, or from a document you have found – try to be as clear as you can.
A practical tip: create an appendix that contains a single table that contains all your software requirements. In your requirements table, give each of your requirements a unique identifier or number (perhaps FR1 for a functional requirement, or NFR1 for a non-functional requirement), and use these identifiers throughout your project. In your project report, refer your examiner to your requirements table.
Acceptance testing
In Figure 1, you will see the term acceptance testing, on the opposite side to requirements. If a software product passes a set of acceptance tests, it is deemed to do what it is supposed to do; it is accepted by whoever commissioned it. In your project you are unlikely to carry out an acceptance test, but you may wish to carry out one or more usability evaluations.
If you are interested in the topic of acceptance testing and whether it might apply to your project, a useful tool to look at is Cucumber. Accompanying this tool is a domain specific language which allows you to express high level tests.
Usability evaluations
The aim of a usability evaluation is to determine whether a software product meets the needs of a particular user (or set of users) and helps to solve a particular problem. A usability evaluation could be carried out toward the end of a project to determine whether (or not) the project was a success, or as a part of a series of design and development iterations to gather some useful information about how a design might potentially be improved. Although a usability evaluation can be used to determine whether a product or a design meets a set of requirement, if used well, it can also be used to uncover and identify new requirements, or requirements that had been overlooked.
In very simple terms, there are usability evaluation paradigms (or approaches) that require people, and there are those that do not. Here is a summary of the three paradigms that are highlighted by Preece et al. in their textbook Interaction Design: beyond human-computer interaction:
To do a usability evaluation well, you need to do some planning. To help you to plan, Preece et al. introduce a useful framework which they have called DECIDE. Here is what each of the letters in the DECIDE framework stand for:
To use DECIDE, you should work through each step. Your decision about which evaluation paradigm you adopt may well be guided by the resources that you have available.
Usability testing
If you decide you would like to carry out a usability test, you need to pay attention to step I, identify practical issues, carefully. The first thing that you need to do is to recruit potential participants. It is okay to ask friends and family to help, who could take on the role of proxy users (participants who pretend to be real users).
If your project is linked to your workplace, you may want to ask some co-workers to help with your usability test, but do be aware of the ethical issues of doing this (which is, of course, the next letter in the DECIDE framework).
Three questions to ask are:
A personal recommendation is to avoid recruiting complete strangers. There is a simple reason for this. Although your project is a real demonstration of your skills and abilities, it remains artificial in the sense that it is primarily a vehicle for academic study and personal development. Involving a wider group of participants exposes you to risks, which can only be address through a more rigorous and formal ethics process.
When preparing for your usability test, it is important to create some materials:
In your project report, you should share all the resources you have created in your report. You might provide an example in the body of your report, or provide one or more appendices; it is up to you.
Although user testing is often thought of a technique that can be applied to a functioning system or product, it can also be applied to evaluate a prototype or an interim design. It is possible to carry out user tests using mock-ups of interfaces created using tools such as PowerPoint, or even using paper sketches of interfaces. Rather than having a computer present the next step in an interaction sequence, you could pretend to be the computer or mobile device, presenting a participant with the next steps.
After you have completed a usability test, you need to find some way to summarise and then to analyse your data. You might provide a sample of the data in the body of your report, and provide all the important or notable data in an appendix, potentially following any appendices that you may have used to share your resources. You might want to comment on limitation of your evaluation, such as, the demographics of any friendly and willing participants you have recruited.
In terms of resources, some really useful guidance is provided within Preece et al.’s Interaction Design text. Useful ethical guidance has been published by the ACM Code of Ethics and Professional Conduct (ACM, 2006) Practice, and the British Computer Society (BCS, 2026).
Accessibility testing
The term accessibility refers to whether a software product can be used by people who have a disability; people who may have sensory or cognitive impairments. Every user-facing software product should have a requirement to be accessible.
If you are creating a product that makes use of web technology, a really useful resource is the Web Content Accessibility Guidelines (WCAG) from the W3C, the organisation that publishes and maintains web standard. Since web pages can be interactive and dynamic, there is also a suite of standards known as WAI-ARIA, the Web Accessibility Initiative Accessible Rich Internet Applications.
Accessibility testing is a specialised version of usability testing. Ideally, every software product should be evaluated by real people, but since this is not always possible, it is important that you consider alternative ways of carrying out accessibility tests.
Here are some practical suggestions of some accessibility tests you could use:
The W3C has published a useful list of Web Accessibility Evaluation Tools, which you may find useful if you need to carry out an accessibility evaluation. If you use any of these tools, please explain why you have chosen one over another, and also share the details of any output that has been created, perhaps by using an appendix. You should also explain what the output from the tool has told you.
Unit testing
Returning to Figure 1, Unit Testing can be found in the bottom right of the diagram. The diagram shows a firm connection between the software code that you create and unit tests. A unit test can be thought of as a formal requirements specification that is expressed in the language of the programming language that is used to create your software. A unit test typically tests the operation of a function, or group of functions, to make sure they do exactly what is expected of them.
A software development approach that emphasises the importance of testing is called Test-Driven Development (Beck, 2023). The idea is simple. Before you write any code, you begin by writing a test. You then run your tests to check to see that everything fails as expected. You then add code that satisfies your tests. Your unit tests are intended to provide helpful feedback about the state of your software.
One of the benefits of unit testing is that it helps with regression testing. A regression test is a set of tests that are carried out to make sure that a change has not inadvertently introduced any errors or mistakes. If you have a suite of well-designed tests, you can run your tests to make sure that any update or modification has not broken anything.
The most popular unit testing framework is called xUnit, where the letter ‘x’ refers to a different programming language. There is likely to be a unit testing framework for whatever language you choose.
If the creation of software is a priority in your project, it is important to share evidence of unit testing, or to justify why you have decided against it. A practical suggestion is to provide an example of one or more unit tests in the body of your report (to perhaps show you have you tested particularly difficult bits of code), and a screenshot that shows the running of unit tests. You need to also explain what you are testing, and why. The more practical detail you provide in your project report. the happier your examiner will become.
To find out more about unit testing, a good starting place is xUnit. There is also JUnit for Java and PyUnit for Python.
Integration testing
Integration testing is about making sure the different bits of your software system work together. If you are creating a software system that contains one or more microservice, a useful question to ask is: how can I test my microservices? There are some bits of terminology that might be useful. A mock is a bit of software that pretends to be another bit of software. There is also the idea of a test harness, which can exercise bit of software before it is then later integrated with, or connected to other bits of software.
If you create any bits of code that tests other bits of code, do remember to discuss what they are, what you did, and what you learnt. Also remember to share any test harness code within an appendix, along with any configuration files or test data you needed to create.
Integration testing is harder to write about, since every software project is made up of different components. This said, there are some tools that might be useful to look at, such as Wiremock or Playwright if you need to understand more about how to test the different elements of your software product.
Security testing
It is easier to carry out tests against functional requirements than it is to test whether a software product satisfies non-functional requirements. A difficult requirement to test is security.
As useful way to think about security testing is whether test can be performed by people, or whether tests can be automated. Here are two sets of tests that relate to security that people can carry out:
There are some automated tools that could be used to help with security testing:
If you have studied TM113 Computing Fundamentals 2, you will be already familiar with the idea of a linter, which introduced a tool called Ruff. Linters have been made for different programming languages and different problems. In some automated deployment processes, new program code may be required to be run through linter software before it could be put into production.
If security is an important non-functional requirement, discuss what approach you might take to test your product. If you run aspects of your code through a static analysis tool, do share the results from that tool, and comment on the results you have gathered.
Performance testing
Another important non-functional requirement that you might have considered is performance; you may need your software product to respond with a certain amount of time. Since your project is likely only involve a small number of users, the necessity to address or explore performance isn’t as important as some of the other non-requirements you may have defined.
A beginning point to begin to think about performance is the programming language or languages you may be using. This can dictate the tools you may choose. There is, of course, a link between performance and your chosen software architecture. Some architectures may enable your design to more efficiently respond to changes in demand.
If your software solution makes use of the Java language, a well-known tool is JMeter. JMeter can also be used with the Python language, through PyMeter. The operating system of your computer, and services provided by your cloud computing provider also provides tools to monitor and check performance. You may also wish to find a way to instrument your code; to take some measurements of how long it might take to carry out particular operations.
If performance is a real issue, you may well turn to the topic of debugging. In turn, you may look to the topic of refactoring, and ask whether you need to refactor your code, or even refactor (or change) your software architecture. A final point is that it is important to take measurements to understand what you have, what you may need to change, and the consequence of any changes that you might make. If you take any measurements within your own project, remember to share them in your project report. Your examiner always wants to see your thinking.
Resources
The following blog posts, which relate to other project module topics, might also be helpful:
Reflections
Testing is a big subject. There are entire suites of industrial qualifications that are dedicated to it. It impossible to test everything in a software project. You need to make practical decisions about what to test, and when to test. In your project report, you need to explain why you have chosen a particular testing strategy, and also show the examiner very clearly what you have done. Do add appendices to share evidence of the tests that you have designed, and the results you have gained; the more detailed they are, the better. The best reports connect testing back to your project requirements. One testing approach will not be enough. You need to study your software system from a number of different perspectives.
References
ACM (2026) ACM Code of Ethics and Professional Conduct. Available at: https://www.acm.org/code-of-ethics (Accessed 16/11/26)
BCS (2026) BCS Code of Conduct https://www.bcs.org/membership-and-registrations/become-a-member/bcs-code-of-conduct/ (Accessed 16/11/26)
Beck, K. (2021) Test Driven Development: By Example. First edition. Pearson Education.
NCSE (2006) Secure development and deployment guidance. Available at: https://www.ncsc.gov.uk/collection/developers-collection (Accessed 16/11/26)
Sharp, H., Rogers, Y. and Preece, J. (2023) Interaction design: beyond human-computer interaction. 6th edition. Wiley.
W3C (2026a) WCAG 2 Overview. Available at: https://www.w3.org/WAI/standards-guidelines/wcag/ (Accessed 16/11/26)
W3C (2026b) WAI-ARIA Overview. Available at: https://www.w3.org/WAI/standards-guidelines/aria/ (Accessed 16/11/26)
Acknowledgements
Figure 1 the Testing v-model has been drawn from TM113 Computing Fundamentals 2: programming, databases and software engineering. Thanks are extended to the TM113 module team, as well as the TM356 Interaction Design and the User Experience module team. It is through the predecessor module that I first gained awareness of the very helpful DECIDE framework.