Footwear eCommerce Website

By

Sharif Sarker

Submitted to
The University of Roehampton

In partial fulfilment of the requirements

for the degree of

Master of Science

in

Computing /Data Science /Web Development

Declaration
I hereby certify that this report constitutes my own work, that where the language of others is
used, quotation marks so indicate, and that appropriate credit is given where I have used the
language, ideas, expressions, or writings of others.

I declare that this report describes the original work that has not been previously presented for
the award of any other degree of any other institution.

Enter your name here

Enter the date here

Apply your signature here

ii
Acknowledgements
I would like to express my heartfelt gratitude to our esteemed venture manager, Adekanmi Adegun, for his
outstanding guidance and support during the footgear eCommerce project. His deep skill and knowledge
have been essential in delving into the intricacies of this endeavor, and his crucial vision has consistently
guided our team toward our goals.

Adekanmi's unwavering commitment to brilliance and his passion to impart his wealth of knowledge have
been crucial in helping people overcome obstacles and achieve significant accomplishments. His aggressive
problem-solving style and unwavering support have continuously motivated us to strive for the best
outcomes.

I am really appreciative of Adekanmi's dedication, which hasn't exactly ensured the successful completion
of this project but has also considerably aided in my professional growth. His ability to foster a creative and
cooperative atmosphere has been truly remarkable, thus this extension is an improvement in involvement.

Thank you, Adekanmi Adegun, for your remarkable leadership, mentorship, and support.

iii
Abstract
GUIDANCE: Up to 500 words
A short summary of your project to include the problem, the main literature reviewed, your
implementation and your findings.
Write this after you have finished the entire report!

iv
Table of Contents
Declaration......................................................................................................................................... ii

Acknowledgements........................................................................................................................... iii

Abstract............................................................................................................................................. iv

Table of Contents............................................................................................................................v

List of Figures.................................................................................................................................... vii

List of Tables.................................................................................................................................... viii

Chapter 1 Introduction.......................................................................................................................1

1.1 Problem Description, Context and Motivation...................................................................2

1.2 Objectives........................................................................................................................... 3

1.3 Methodology...................................................................................................................... 3

1.4 Legal, Social, Ethical and Professional Considerations........................................................3

1.5 Background.........................................................................................................................3

1.6 Structure of Report.............................................................................................................4

Chapter 2 Literature – Technology Review........................................................................................ 5

2.1 Literature Review............................................................................................................... 5

2.2 Technology Review.............................................................................................................5

2.3 Summary............................................................................................................................ 6

Chapter 3 Implementation.................................................................................................................7

Chapter 4 Evaluation and Results.......................................................................................................8

4.1 Related Works.................................................................................................................... 8

Chapter 5 Conclusion......................................................................................................................... 9

5.1 Future Work....................................................................................................................... 9

5.2 Reflection........................................................................................................................... 9

References........................................................................................................................................11

Appendices.......................................................................................................................................... I

Appendix A: Project Proposal.............................................................................................................II

v
Appendix B: Project Management.....................................................................................................III

Appendix C: Artefact/Dataset........................................................................................................... IV

Appendix D: Screencast......................................................................................................................V

This contents page is automated based on your heading styles. It will bring in the heading and page number
of any content using the Heading 1, Heading 2 or Heading 3 styles. To update the table, you need to right-
click on this table and choose the update field.

vi
List of Figures
This list of figures is automated based on your use of captions (found in the references ribbon). It will bring
in any caption that uses the ‘Figure’ label. To update the list above, you need to right-click on this list and
choose Update Field.

vii
List of Tables
This list of tables is automated based on your use of captions (found in the references ribbon). It will bring
in any caption that uses the ‘Table’ label. To update the list above, you need to right-click on this list and
choose Update Field.

viii
Chapter 1 Introduction
Secure payment preparation, a responsive design, and strong visual skills are among the
fundamental features of cutting-edge eCommerce websites. Our website integrates Stripe for safe
exchanges of installment payments, ensuring that clients' payment information is protected by
cutting-edge encryption and anti-extortion safeguards. This connection creates a dependable
shopping environment by enabling quick, safe, and reliable swaps.

The savvy consumer expects flexibility, and our website delivers with a fully flexible layout that makes for the best
possible experience across all devices, including computers and smartphones. This ensures that customers, regardless
of the device they are using, may peruse, choose, and purchase things with ease and efficiency.
Enhancing convenience and customer satisfaction starts with an intuitive look. Our website has a powerful search
feature that enables users to quickly find the products they desire by searching for specific titles or categories. This
optimized route ensures that customers can easily discover exactly what they're looking for while also making
shopping faster and more enjoyable.

This extension demonstrates our dedication to provide footgear enthusiasts worldwide with a safe, dependable, and
user-friendly eCommerce platform. Utilizing cutting-edge tools and a customer-focused strategy, our website appears
to be at the forefront of the advancement in computerized shopping.

1.1 Problem Description, Context and Motivation

Problem Statement: Our primary concern is the requirement for safe and efficient online shopping experiences in
the footwear industry. Customers often face difficulties with safe payments, continuous device surfing, and
straightforward item disclosure, all of which can derail their overall buying experience.

Who is Affected by the Problem?

Customers: Individuals searching for high-quality footwear struggle with flimsy-looking functionalities, insecure
installation doors, and unresponsive websites.

Retailers: retailers of footwear who are unable to attract and retain customers because they lack an efficient, safe,
and user-friendly platform for online buying.

Where and/or When Does the Problem Occur?

Where: The problem primarily arises in the digital marketplace, particularly on e-commerce platforms that sell
footwear.

When: Customers deal with these problems all the time when they shop online, from item searching to payment
processing.

1
Why is it Important to Solve the Problem?

Security Concerns: Ensuring secure transactions is essential for protecting clients' financial information and
fostering trust in the platform in light of the growing threat of cyberattacks.

User Experience: A site that is intuitive and responsive enhances the purchasing experience and increases
customer satisfaction and upkeep. Ensuring easy access to objects via a productive look work is essential.

Market Competitiveness: Offering a common purchasing experience can set [Your Site Title] apart from rivals
in the fiercely competitive eCommerce market, resulting in more sales and loyalty.

Scalability and Future Growth: Addressing these problems ensures that the platform is robust and flexible,
designed to accommodate upcoming demands and technological advancements.
By resolving these problems, [Your Site Title] hopes to establish a previously unheard-of standard in the footgear
eCommerce sector, providing customers with a safe, reliable, and enjoyable buying experience while enabling shops
to thrive in a safe, user-friendly digital environment.

1.2 Objectives
Implement Secure Payment Gateway

Task: synchronized Stripe payment page.

Outcome: Ensure encrypted and secure transactions to protect customer financial information.

Develop a Fully Responsive Design

Task: Create and evaluate formats that are responsive for various devices (desktops, tablets, smartphones).

Outcome: Provide a steady and consistent user experience across all devices.

Enhance Search Functionality

Task: Design and implement an advanced search feature that enables users to find products by keyword, category,
and title.

2
Outcome: Advancement of item disclosure and route simplicity of use.

Optimize Website Performance

Task: Perform optimization and execution testing, measuring server response times, page stack speeds, and
simplified code.

Outcome: Boost site performance and steadfast quality to provide a seamless buying experience.

Implement Robust Security Measures

Task: Update HTTPS, standard security fixes, and vulnerability assessments.

Outcome: Protect the website from possible online threats and maintain information intelligence.

Design
Approach:

User-Centered Design: Measure page stack speed, server response time, and simplified code while
performing execution testing and optimization.

Wireframing and Prototyping: Ensure a seamless purchasing experience by optimizing the speed and
consistency of the website.

Responsive Design: Install standard security patches, HTTPS, and vulnerability assessments.

Why: Maintain information shrewdness and protect the website from any potential cyber threats.

Project Management
Approach:

Agile Methodology Use Scrum principles to oversee work in a sprint-based manner.

3
Kanban Board: Track tasks and go through phases by using tools such as Trello or Jira, which count "To Do,"
"In Advance," and "Done."

Gantt Chart: For a high-level view of extended timescales and breakthroughs, use Gantt charts.

Why: Iterative improvement and adaptation are enabled by the spry approach. Gantt charts help with broad
project timetable tracking, whereas Kanban sheets provide visual management of tasks.

Technologies and Processes

Approach:

Development Frameworks: Because of React.js's component-based architecture and strong community

support, use it to progress front-end development.

Back-End Development:
For reliable and flexible server-side operations, leverage Express and Node.js.

Database: Use MongoDB because of its flexibility and agility in managing large amounts of data.

Payment Integration: Stripe coordinated for reliable and safe handling of installations.

Version Control: Use GitHub as the storage and Git for form control and collaboration.

Why:

React.js: Selected due to its efficacy and ability to create dynamic client interactions.

Node.js/Express: Provides a robust framework for back-end development.

MongoDB: Manages unstructured data effectively, making it ideal for eCommerce phases.

4
Stripe: Offers simplicity of integration and extensive security characteristics.

Git/GitHub: Ensures easy form management and cooperation.

We aim to effectively and profitably achieve our project goals by employing these tactics and tools.

1.3 Legal, Social, Ethical and Professional Considerations

Legal Considerations
Compliance with Regulations:

General Data Protection Regulation (GDPR):

Ensure that customer data is gathered, stored, and managed in accordance with GDPR regulations.

Consumer Rights: Observe customer security regulations, including clear return policies and accurate item
descriptions.

Payment Security Standards: For secure installment planning, adhere to the PCI DSS (Installment Card
Industry Information Security Benchmarks).

Actions Taken:

putting information encryption into practice and improving secure capacity.

Providing transparent and unambiguous protection strategies and benefit terms.

routinely checking for adherence to PCI DSS requirements and GDPR.

Social Considerations
User Accessibility:

Inclusivity: Comply with Web Substance Availability Guidelines (WCAG) to ensure that the platform is
accessible to all clients, including those who are disabled.

User Experience: Make an effort to create a user-friendly interface that accommodates a variety of
socioeconomic groups, including varying age ranges and degrees of tech proficiency.

Actions Taken:

arrying out reviews of transparency and combining important changes.

Gathering client critique from a diverse source to create strides convenience.

.
5
Ethical Considerations
Data Privacy:

User Consent: Obtain unambiguous consent by clearly outlining the client's nearly complete information
gathering process.

Transparency: Make sure customers have control over their personal data and be open and honest about
how their information is used.

Actions Taken:

putting together a thorough protection plan.

allowing customers to choose whether to receive promotional mailings and information collecting.

Code of Conduct:

Professional Standards: Adhere to the most important standards for refined competence in all areas of
customer involvement, communication, and advancement.

Ethical Marketing: Ascertain that all promotional offers are authentic and do not mislead consumers.

Actions Taken:

establishing a code of behavior for the advancement team.

checking marketing materials on a regular basis to ensure accuracy and reliability.

Ethical Clearance

Need for Ethical Clearance: To ensure adherence to moral standards, moral clearance might be
necessary if the project involves gathering personal data from clients (such as surveys or feedback).

Actions Taken:

6
Ethical Review: If necessary, submit the extended proposal for a moral evaluation and obtain approval.

Ethical Management: Implement measures to address ethical reflections, such as protecting personal data
and ensuring informed consent.

By keeping these ethical, moral, social, and legal considerations in mind, we want to create a competent and
trustworthy eCommerce platform that respects customer rights and complies with industry standards.

1.4 Background
Context and Relevance
The growth of eCommerce continues to change how consumers and businesses interact. According to later estimates,
global eCommerce transactions are expected to surpass 6.3 trillion USD by 2024, demonstrating the exponential
growth of the industry.

This surge is driven by various factors:

Convenience: Being able to buy whenever and wherever you choose.

Diverse Product Range: Gain access to a wider range of products.

Competitive Pricing and Promotions: benefit from refunds that internet merchants advertise.

This kind of development highlights the growing reliance on eCommerce platforms, which need to keep improving in
order to satisfy consumers' ever-increasing demands.

Addressing Known Issues

Despite its growth, eCommerce faces several challenges critical to address for ensuring sustained
success and customer satisfaction. Key issues include:

Data Security and Privacy: Securing customer information is still essential given the increase in online
transactions. As per the Cybersecurity Wanders report (2023), it is projected that the annual damages caused by
cybercrime will reach 10.5 trillion USD by 2024. This emphasizes the need for stringent security protocols and
adherence to GDPR regulations.

7
User Experience: Communicating a remarkable level of customer involvement is essential as competition
increases. Subsequent analysis by the Baymard Founded (2023) indicates that laborious checkout forms account about
70% of online shopping basket abandonment. Future UX plans have the potential to significantly increase client
engagement and sales.

Accessibility: An inclusive plan ensures that all customers, including those with disabilities, may use and
benefit from eCommerce platforms. The goal of W3C's Web Openness Activity (2023) is to ensure a fair level of
client interaction by following WCAG 2.1 guidelines .

Customer Trust and Transparency: Adhering to data security regulations such as GDPR and providing clear
methods increase consumer trust. In a subsequent analysis by PwC (2023), 84% of consumers stated that their
purchasing decisions are influenced by how much they trust the brand to protect their personal data.

By addressing these issues, our eCommerce platform aims to create a safe, easy-to-use, and all-encompassing
purchasing experience that satisfies evolving consumer demands while adhering to international standards for data
security and accessibility.

Personal Motivation
My own motivation comes from a need to use innovation to understand problems in the real world. Having spent
several years working in the technology sector, I can attest to the profound effects that well-thought-out digital
arrangements can have on both customers and organizations. This extension provides the ideal chance for me to apply
my skills and knowledge to develop a platform that tackles fundamental issues in the eCommerce industry, ultimately
enhancing customer engagement and trust.

Literature References

Statista. (2023). Global eCommerce Sales Projections. Retrieved from Statista.

Cybersecurity Ventures. (2023). Cybercrime Damages Projected by 2024. Retrieved

from Cybersecurity Ventures .

Baymard Institute. (2023). Cart Abandonment Data. Retrieved from Baymard.

W3C's Web Accessibility Initiative. (2023). Understanding WCAG 2.1. Retrieved from W3C.

PwC. (2023). Consumer Trust Survey. Retrieved from PwC.

My own motivation comes from a need to use innovation to understand problems in the real
world. Having spent several years working in the technology sector, I can attest to the profound
effects that well-thought-out digital arrangements can have on both customers and organizations.
This extension provides the ideal chance for me to apply my skills and knowledge to develop a
platform that tackles fundamental issues in the eCommerce industry, ultimately enhancing
customer engagement and trust.

8
1.5 Structure of Report
Insert your text here

Describe the upcoming sections in order -- this provides your reader with a roadmap of the report.
You may find this link useful

9
Chapter 2 Literature – Technology Review
GUIDANCE: Up to 1500 words
Note: All projects will require a technology review. However, not all projects will require a literature review.
Please speak to your supervisor to confirm what is required for your project.

2.1 Literature Review

Insert text here

The literature review is a key part of your project and has specific marking criteria attached. The purpose of
the literature review is to show that you have researched, understood, and critically evaluated all aspects of
your problem statement. This is your ‘investigation’.
You should describe the problem in detail, mentioning any literature, organisations, institutions or
individuals who are important in the context or the solution.
You should correctly reference using IEEE style key articles, books, or papers you have read that are
relevant to the problem.
It is not enough to list relevant points. You also need to show the ability to:
• Summarise the main points.
• Discuss (e.g., point out strengths, weaknesses, differences of approach etc).
• Describe how the literature you have found relates to the problem you are addressing.
• Apply your own critical thinking to the material you include.
• Draw your own conclusions from your investigation and show how these will guide your
methodology and implementation.
Everything that you write in your literature review must be clearly relevant to your problem statement and
aims and objectives, and you must clearly state this.

2.2 Technology Review

Summarized Technology Options
Front-End Development Technologies:

React.js

Pros: Reusable components, virtual DOM for faster rendering, strong community support, component-based
design.

10
Cons: For more inexperienced learners, a steeper learning curve that requires additional libraries to fully
utilize.

Vue.js

Pros: Easy to learn, suitable for small to medium-sized applications, well-documented, flexible, and less
obstinate.

Cons: smaller community and limited venture support than Respond.

Angular

Pros: Comprehensive system, built-in state administration and testing utilities, solid Google back.

Cons: more intense learning curve, typically overwhelming and unyielding.

Back-End Development Technologies:

Node.js/Express

Pros: Rapid and flexible, I/O operations without blocking, strong community support, and a vast module
ecosystem.

Cons: It can be difficult to write nonconcurrent programs, and they are not ideal for CPU-intensive tasks.

Django (Python)

Pros: High-level system with integrated verification, ORM for database management, and extensive
documentation that promotes quick improvement.

Cons: Well-engineered, but less flexible than systems with microservices.

Ruby on Rails

Pros: Tradition over planning, quick development, integrated testing, and strong community support.

11
Cons: limited adaptability and problems with large-scale application execution.

Database Technologies:

MongoDB

Pros: Lacks a schema, is flexible, adept at handling unstructured data, and is reasonably versatile.

Cons: Exchanges support less information repetition potential when compared to social databases.

PostgreSQL

Pros: Strong corrosive compliance, supports intricate questions, aggressive implementation, and expandable
with add-ons.

Cons: slower than NoSQL databases when processing massive volumes, and additional setup is needed.

MySQL

Pros: Broadly employed, strong Corrosive compliance, productive for read-heavy operations, develop and
steady.

Cons: Limitated to handling unstructured data, performance can deteriorate when handling large amounts of
data.

Payment Integration Options:

Stripe

Pros: Strong security features, extensive documentation, support for a variety of payment methods and forms,
and easy integration are the pros.

Cons: Exchange costs, limited to online transactions, can be high for large volumes.

PayPal

Pros: well acknowledged, reliable, easy to set up, and secure for buyers.

12
Cons: Increased exchange costs and possible account limitations.

Square

Pros: easy to use, clear estimating, and equipment options for in-person installations coordinated.

Cons: limited to specific countries, more costs for international trade.

Version Control Systems:

Git

Pros: Effective adaptation control, strong community support, collaboration with several advancement tools,
and dynamic branching demonstration.

Cons: More difficult learning curve with intricate historical administration for klutzs.

SVN (Subversion)

Pros: Better for direct improvement, centralized adaption control, and simpler to present for underutilized
clients.

Cons: Single point of disappointment and a branching display that is less flexible.

Rationale for Chosen Technologies

Front-End Development: React.js

Rationale: React.js is a good choice for creating dynamic and responsive client interfaces because of its
virtual DOM and component-based engineering, which provide a powerful engineer experience. Libraries offer
additional tools for state administration and direction due to their rich surroundings and strong community
support, which makes them an ideal option for the long term.

Back-End Development: Node.js/Express

Rationale: Non-blocking, event-driven design is provided by Node.js/Express and is essential for handling
many synchronous transactions and providing real-time highlights. It is an excellent option for our eCommerce
stage due to its swift execution and adaptability.

Database: MongoDB

Rationale: Because MongoDB is schema-less, it can manage changing item data types with the flexibility
needed, and its adaptability supports growth as the user base grows. Because of its ability to manage
unstructured data, eCommerce databases benefit from its dynamic structure.

13
Payment Integration: Stripe

Rationale: Stripe is a preferred option for handling online payments due to its straightforward integration,
extensive documentation, and robust security features. Its support for various payment methods and
currencies adapts to the needs of a global eCommerce platform, ensuring a reliable payment experience.

Version Control System: Git

Rationale: Git's distributed adaption control system provides flexibility and robustness, enabling designers to
work on different features simultaneously without causing conflicts. Its strong community support and
compatibility with various technological devices make it an essential part of efficiently managing the codebase
for our project.

Summarized Choice of Technologies

Front-End Development: React.js

Back-End Development: Node.js/Express

Database: MongoDB

Payment Integration: Stripe

Version Control System: Git

Conclusion
The innovations selected for this project have been selected on the basis of their ability to meet
the specific requirements of an eCommerce platform, which include adaptability, versatility, skill,
and user-friendliness. Node.js/Express will enable speedy and flexible back-end handling, while
React.js will provide a dynamic and responsive client experience. MongoDB provides the flexibility
to manage updated and dynamic item data. Stripe ensures reliable and secure installment
planning, which is essential for winning over customers. Finally, Git provides strong adaption
control, which is essential for managing a cooperative development environment.
All of these advancements work together to create an eCommerce platform that is safe, efficient,
and easy to use while also meeting the strict requirements of the modern digital business center.

14
2.3 Summary
The selected inventions and methods provide unique advantages and restrictions that will essentially
mold our extended strategy. React.js's virtual DOM facilitates component-based engineering and
execution, but it has a steep learning curve and needs additional libraries for state management.
Node.js/Express's nonconcurrent I/O ensures efficient execution, but managing its async operations
can be challenging. Although MongoDB's schema-less architecture risks information duplication
and less active exchanges, it is advantageous for quick development and adaptability. The Stripe
installment gateway has strict security measures and is easy to integrate, but it also has higher
exchange costs and depends on a stable web network. Git can be difficult for modern clients to use,
but it promotes strong form control and teamwork. These insights inform our methodological focus,
which is on thorough planning, optimal techniques for nonconcurrent programming, rigorous
exchange management, and ongoing security assessments, all aimed at delivering a safe, adaptable,
and user-focused eCommerce platform.

15
Chapter 3 Implementation
Insert your text here

GUIDANCE: Up to 3000 words

Discuss how did you apply the methodologies you have described in the section above to your actual
problem.
Some strategies that can help you write this part:
• Start this section with any design work you might have done e.g., experimentations, system
design/architecture, UX design artefacts etc.
• If you divided your work into sprints, that can be a good structure for this section.
• Only include code snippets for particularly challenging parts of your implementation.
• Pick out a few difficult problems you had to solve and tell us in detail how you solved them. This
brings your experience to life.

16
Chapter 4 Evaluation and Results
Insert text here

GUIDANCE: Up to 2000 words

This is an important section where you weigh up the strengths and weaknesses of your
artefact/experimentation.
Guidance: If your project has a user-facing element, we expect to see some kind of evaluation of this with
representative intended users, for example a ‘think aloud’ usability test.
You can also apply standard metrics for the domain you are working in and see how you have done against
them. Your project does not have to be perfect -- indeed the outcomes might have been bad. The point is
you must evaluate the outcome and discuss its strengths and weaknesses.
This section should include the following subheadings:
• Related Works

4.1 Related Works

Insert text here

17
Chapter 5 Conclusion
Insert text here

GUIDANCE: Up to 1500 words

The conclusion summarises the project. Start by summarising the overall outcome of your project and to
what extent the aims and objectives have been met. You need to highlight your key outputs and/or
discoveries.
The following subsections that must appear in your conclusion.

5.1Future Work
Insert text here

Answer the question -- What next?

You've completed a significant piece of work -- perhaps the largest piece of work you have ever done. But
no project is ever 100% complete, and you will have found new ideas along the way. If someone were to
pick up your project, what avenues should be explored next?
This is an important section, and it helps us understand what you have learned by doing the project and
allows you to show you understand what a more ideal solution might look like, outside the constraints of
the MSc Project timeframe.

5.2Reflection
Insert text here

You must critically reflect on the entire project process and how well you have worked on the project. What
particular things have you learned during the project? Why were you able and unable to meet project
goals? What would you have done differently in hindsight?

Insert text here

18
Additional chapters can be added using the Heading 1 style.

19
References
Insert text here

You should include your reference list at the end of your report but before the appendices. You must
ensure you use the appropriate IEEE format for your subject area.
Your referencing must use the IEEE referencing style IEEE Citation Guidelines.
It is highly recommended that you use reference management software such as RefWorks that is provided
by the university. Your project should have as many references as is required. However, having few
references indicates that no thorough investigation has occurred.
It is your responsibility to ensure that you have actually read all the material you reference, and that the
references provided in your report are legitimate and NOT AI-generated.
A Note about EndNote
If you are using EndNote for your references, your reference list will initially appear below the appendix.
You can cut and paste it to this page and it will stay here after that.

Below this line is a hidden Section Break (Next Page). DO NOT DELETE THIS!
You can see hidden elements by using the Show/Hide option ( ) on the home ribbon.

20
 Appendices
Appendices appear after references. Your appendices depend on the nature of your project. If you direct
them to do so in your main text, appendices are considered additional information and should not be relied
upon to understand your main body of work. Refer readers to an appendix using a phrase such as see
Appendix A for further details.
The following documents must be included as references:
• Your Project Proposal.
• Evidence of your use of a project management tool.
• A description of accessing (link) any technical output, such as the developed dataset and coding. It
is strongly recommended you use GitHub or something similar to do this.
• Provide a link to the video recording for demonstrating your artefact
For any important communications between you and external stakeholders, please remove private data
and anonymise communications.
Use Heading back matter style for the headings of appendices.
You can delete these guidelines but you need to leave the rest of page black with “Appendices” on the top.

I
Appendix A: Project Proposal
Insert text here

II
Appendix B: Project Management
Insert text here

III
Appendix C: Artefact/Dataset
Insert text here

Provide a link and on how to access any technical output such as the developed/used dataset and coding. It
is strongly recommended you use GitHub or something similar to do this.

IV
Appendix D: Screencast
Insert text here

Provide a link to your video file here. You can share your screencast using Microsoft Stream, OneDrive or
any other method which gives full access to your supervisor and second marker.
A PowerPoint is not required.