jack/website
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update some project info

Browse Source
This commit is contained in:
Jack Bond-Preston 2020-01-22 23:05:43 +00:00
parent b9c2897c76
commit 4b0c6b636c
1 changed files with 23 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
index.html
View File

@ -107,12 +107,19 @@
<a href="https://p.ota.to/">Potato</a>.
</p>
<p class="uk-visible@m">
Developed as part of a 4-person team for the Software Project Engineering unit at the University of Bristol.
Developed as part of a 4-person team for the Software Project Engineering unit at the
University of Bristol.
</p>
<p class="uk-visible@m">
The backend interfaces with a MySQL database to serve a REST API implemented in Spring. This Java application
is then deployed to the cloud. The frontend consists of static HTML using Bootstrap and Vue.js, served by the
internal Spring web-server - accessing and mutating the data through the REST API.
The Spring Boot backend interfaces with a MySQL database to serve a REST API. This Java
application is then deployed to the cloud. The frontend consists of static HTML
generated using Bootstrap and Vue.js, served by the internal Spring web-server -
accessing and mutating the data through the REST API.
</p>
<p class="uk-visible@m">
This project was developed using 6 Agile sprints to complete 76 user stories. We
utilised test driven development by using JUnit unit tests with Gitlab CI/CD to
automatically run tests and deploy the application to Oracle Cloud.
</p>
</div>
</div>
@ -128,18 +135,23 @@
A concurrent game of life implementation designed to run on a limited piece of hardware.
</p>
<p class="uk-visible@m">
Developed as part of a 2-person team for the Concurrent Computing unit at the University of Bristol.
Developed as part of a 2-person team for the Concurrent Computing unit at the University
of Bristol.
</p>
<p class="uk-visible@m">
This game of life implementation was written in
<a href="https://en.wikipedia.org/wiki/XC_(programming_language)">XC</a>
and designed to run on the XMOS xCORE-200 eXplorer. The program runs concurrently across tiles, utilising
channels for cross-thread communication. Hardware memory limitations posed interesting challenges, with
solutions such as packing the individual "cells" into individual bits of 32/16-bit integers to be as
memory-efficient as possible. Each turn, the board is split up into rows of these packed cells which are then
distributed across workers for processing, then returned to the distributor and consolidated back into a single
board each turn.
and designed to run on the XMOS xCORE-200 eXplorer. The program runs concurrently across
tiles, utilising channels for cross-thread communication. Hardware memory limitations
posed interesting challenges, with solutions such as packing the individual "cells" into
individual bits of 32/16-bit integers to be as memory-efficient as possible. Each turn,
the board is split up into rows of these packed cells which are then distributed across
workers for processing, then returned to the distributor and consolidated back into a
single board each turn.
</p>
<p class="uk-visible@m">
This coursework was later updated to be based in Go, and run on desktop PCs. I have also
completed this coursework assignment as part of my role TAing this new unit.
</div>
</div>
</div>