-
Notifications
You must be signed in to change notification settings - Fork 3
Expand file tree
/
Copy pathsnapshots.html
More file actions
159 lines (155 loc) · 7.53 KB
/
snapshots.html
File metadata and controls
159 lines (155 loc) · 7.53 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
<!DOCTYPE html>
<html>
<head>
<!-- Manages the styles etc for the design e.g. don't touch unless you know what you're doing!-->
<title>devCharles</title>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,
initial-scale=1">
<link rel="stylesheet" href="styles.css">
</head>
<body>
<nav class="navbar">
<div class="container">
<div class="navbar-brand">
<!-- Logo placeholder-->
<a class="navbar-item" href="index.html">
<img class="logo" src="images/logo-light.png" alt="logo">
</a>
<span class="navbar-burger" data-target="navbarMenuHeroA">
<span></span>
<span></span>
<span></span>
</span>
</div>
<div id="navbarMenuHeroA" class="navbar-menu">
<div class="navbar-end">
<a href="index.html" class="navbar-item">
Home
</a>
<div class="navbar-item has-dropdown is-hoverable">
<a href="document.html" class="navbar-link">
Documentation
</a>
<div class="navbar-dropdown">
<a href="document.html" class="navbar-item">
Extra diagrams
</a>
<a href="docs/Requirements_Doc_NEW.pdf" class="navbar-item">
Requirements
</a>
<a href="docs/Architecture.pdf" class="navbar-item">
Architecture
</a>
<a href="docs/Method_selection_and_planning.pdf" class="navbar-item">
Method Selection and Planning
</a>
<a href="docs/Risk_assessment_and_mitigation.pdf" class="navbar-item">
Risk Assesment and Mitigation
</a>
<a href="docs/Implementation.pdf" class="navbar-item">
Implementation
</a>
<a href="javadoc/index.html" class="navbar-item">
Javadoc
</a>
</div>
</div>
<span class="navbar-item">
<!-- Set as primary so we can customise the colour scheme later with sass -->
<a href="piazzaPanic.jar" class="button is-link">
<span>Download</span>
</a>
</span>
</div>
</div>
</div>
</nav>
<section class="section content">
<div>
<h1>Week 1</h1>
<img src="weekly/week1.png" alt="">
<p>The first week was mostly about us meeting and getting to know each other and getting a general idea of what the project was. We did some research into things we might need, such as potential game engines and assets. We started to prepare for the client meeting by brainstorming questions to ask the client about what exactly we needed for the game.</p>
<br>
<br>
</div>
<div>
<h1>Week 2</h1>
<img src="weekly/week2.png" alt="">
<p>In the second week we had the client meeting where we asked the questions we had thought of and used that information along with the product brief to start work on the documentation. </p>
<br>
<br>
</div>
<div>
<h1>Week 3</h1>
<img src="weekly/week3.png" alt="">
<p>Some of us started work on the website, getting the structure of it ready so we could continue updating it with new work as the project progressed. The rest of us started work on other parts of the documentation, such as requirements and the risk assessment. We also made our initial plan for the project and decided on some of the tools we would use.</p>
<br>
<br>
</div>
<div>
<h1>Week 4</h1>
<img src="weekly/week4.png" alt="">
<p>We continued with our documentation for this week, particularly the requirements and risk assessment. We also started implementation. This was mostly deciding which game engine we wanted to use, we chose libGDX, and familiarising ourselves with it by doing a basic tutorial. We also started to plan out the game's architecture, thinking of classes we might need and starting the UML diagram.</p>
<br>
<br>
</div>
<div>
<h1>Week 5</h1>
<img src="weekly/week5.png" alt="">
<p>This was the first week of the Christmas holidays, during which we got less work done than when we were at uni, but we did continue to work on the features for the implementation that we had started the previous week.</p>
<br>
<br>
</div>
<div>
<h1>Week 6</h1>
<img src="weekly/week6.png" alt="">
<p>This week we continued to work on the basic implementation and started to do more research on which assets to use.</p>
<br>
<br>
</div>
<div>
<h1>Week 7</h1>
<img src="weekly/week7.png" alt="">
<p>This was the week of Christmas so we agreed to take a break.</p>
<br>
<br>
</div>
<div>
<h1>Week 8</h1>
<img src="weekly/week8.png" alt="">
<p>We continued to do some work on the implementation of the game, but didn’t get too much done because of the holidays.</p>
<br>
<br>
</div>
<div>
<h1>Week 9</h1>
<br>
<p>Week 9 was an exam week, so no snapshots are provided for that period.</p>
<br>
<br>
</div>
<div>
<h1>Week 10</h1>
<img src="weekly/week10.png" alt="">
<p>This week we started to implement collision detection for the game and started to create some tests for the game.We also started an updated UML diagram now that we had done more work on the game and had a better understanding of what classes we needed.</p>
<br>
<br>
</div>
<div>
<h1>Week 11</h1>
<img src="weekly/week11.png" alt="">
<p>This week we continued working on the games implementation, mostly working on the cooking stations and UI. We also updated some of our documentation now that we had a better idea of what the implementation required. Particularly the requirements but also some other sections. We also continued to work on the new UML diagram.</p>
<br>
<br>
</div>
<div>
<h1>Week 12</h1>
<img src="weekly/week12.png" alt="">
<p>This was the last few days, we made some finishing touches to the game and went through all of our deliverables, making any necessary changes and adding them to the website.</p>
<br>
<br>
</div>
</section>
</body>
</html>