-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathkroy.html
293 lines (241 loc) · 12.8 KB
/
kroy.html
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
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Dalai Java - UoY SEPR</title>
<link rel="icon" href="./logo2.png">
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/css/bootstrap.min.css">
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.12.9/umd/popper.min.js"></script>
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/js/bootstrap.min.js"></script>
<script src="https://kit.fontawesome.com/44381eb229.js" crossorigin="anonymous"></script>
<link href="style.css" rel="stylesheet">
<meta name="google-site-verification" content="cXcpD51hZqy9ae6qZWoTBy65ULtsyOsEC3k13fUK7Ws" />
</head>
<body>
<!-- Navigation -->
<nav class="navbar navbar-expand-md navbar-light bg-light sticky-top">
<div class="container-fluid">
<a class="navbar-brand" href="#"><img src="./logo.png" height="100" width="120"></a>
<button class="navbar-toggler" type="button" data-toggle="collapse"
data-target="#navbarResponsive">
<span class="navbar-toggler-icon"></span>
</button>
<div class="collapse navbar-collapse" id="navbarResponsive">
<ul class="navbar-nav ml-auto">
<li class="nav-item">
<a class="nav-link" href="./index.html">Home</a>
</li>
<li class="nav-item active">
<a class="nav-link" href="#">Kroy</a>
</li>
<li class="nav-item">
<a class="nav-link" href="#Footer">Contact Us</a>
</li>
<li>
<div class="dropdown show">
<a class="btn btn-secondary dropdown-toggle" href="#" role="button" id="dropdownMenuLink" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
Assessments
</a>
<div class="dropdown-menu" aria-labelledby="dropdownMenuLink">
<a class="dropdown-item" href="./Assessment_1.html">Assessment 1</a>
<a class="dropdown-item" href="./Assessment_2.html">Assessment 2</a>
<a class="dropdown-item" href="#">Assessment 3</a>
<a class="dropdown-item" href="#">Assessment 4</a>
</div>
</div>
</li>
</ul>
</div>
</div>
</nav>
<div class="main-kroy-img">
<img src="https://anomalien.com/wp-content/uploads/2019/08/aliens-on-earth.jpg" class="img-fluid" alt="This is placeholder for the game logo img">
</div>
<div class="container-fluid padding">
<div class="row welcome text-center">
<div class="col-12">
<h1 class="display-4">Gameplay Features</h1>
</div>
<hr>
</div>
</div>
<div class="container-fluid padding">
<div class="row text-center padding">
<div class="col-xs-14 col-sm-12 col-md-6">
<i class="fas fa-pastafarianism"></i>
<h3>Dodge the incoming threat</h3>
<p>The aliens are here and ready to take over York</p>
</div>
<div class="col-xs-14 col-sm-12 col-md-6">
<i class="fas fa-user-astronaut"></i>
<h3>Take control</h3>
<p>Command the resistance and push back the invaders to save the city</p>
</div>
</div>
</div>
<div class="container-fluid padding">
<div class="row welcome text-center">
<hr>
<div class="col-12">
<h2 class="display-5">Find the latest release in the assessment tab of the navigation bar or click below</h2>
</div>
</div>
<div class="text-center"><a href="./Assessment_2.html"><button type="button" class="btn btn-outline-secondary btn-lg">
Latest Release</button></a></div>
</div>
<div class="container-fluid padding"
<div class="accordion" id="accordionInfo">
<div class="card">
<div class="card-header" id="headingOne">
<h2 class="mb-0">
<button class="btn btn-link" type="button" data-toggle="collapse" data-target="#collapseOne" aria-expanded="false" aria-controls="collapseOne">
Assessment 1
</button>
</h2>
</div>
<div id="collapseOne" class="collapse" aria-labelledby="headingOne" data-parent="#accordionInfo">
<div class="card-body">
Assessment 1 covers the early stages of requirements specification and design – including the architecture of our proposed
solution; method selection, planning; and risk assessment and mitigation. As part of the assessment, we identified
appropriate software engineering methods and techniques, set up a regular meeting schedule, and allocated
tasks to team members according to team member availability and skills.
</div>
</div>
</div>
<div class="card">
<div class="card-header" id="headingTwo">
<h2 class="mb-0">
<button class="btn btn-link collapsed" type="button" data-toggle="collapse" data-target="#collapseTwo" aria-expanded="false" aria-controls="collapseTwo">
Assessment 2
</button>
</h2>
</div>
<div id="collapseTwo" class="collapse" aria-labelledby="headingTwo" data-parent="#accordionInfo">
<div class="card-body">
Assessment 2 concerns the detailed software engineering design, and implementation of part of the software system,
based on the requirements and specification created for Assessment 1. We will revisit the Assessment 1 deliverables,
review and maintain non-code deliverables, and apply version control.<br><br>
Our group’s scenario (product brief) indicates which elements are to be designed and implemented for Assessment 2.
In Assessment 2, you must not exceed this brief: do not implement any other features.<br><br>
Our product must be consistent with the scenario, and with our Assessment 1 work, as described below.
</div>
</div>
</div>
<div class="card">
<div class="card-header" id="headingThree">
<h2 class="mb-0">
<button class="btn btn-link collapsed" type="button" data-toggle="collapse" data-target="#collapseThree" aria-expanded="false" aria-controls="collapseThree">
Assessment 3
</button>
</h2>
</div>
<div id="collapseThree" class="collapse" aria-labelledby="headingThree" data-parent="#accordionInfo">
<div class="card-body">
Assessment 3 requires each team to work on another team’s product. There are thus two phases to the assessment, below.
As in the previous assessment, Assessment 3 requires review, maintenance and version control activities.<br><br>
<b><u>Phase 1: selection</u></b><br><br>
After the submission of Assessment 2, each team has a short period to consider the products of the other teams. In the
Spring Week 3 practical class that your team attends, each team will present its product, and can then discuss with other
teams. On Spr/4/Monday, each team is required to register, by 10am, their choice of product to work on in Assessment 3, by
emailing the lecturers.<br><br>
The only constraint on selection is that a team is not allowed to use its own Assessment 2 software in Assessment 3.<br><br>
In selecting a software product, criteria that may be considered include: (1) the overall quality of the software product; (2)
estimates of effort remaining to complete the implementation; (3) clarity and quality of the requirements specification,
architecture, testing and implementation.<br><br>
A bonus of 2 marks will be added to the team’s Assessment 2 mark for each registered selection of the team’s software product,
with the condition that no individual can attain more than 100% for Assessment 2.<br><br>
<b><u>Phase 2: extension and integration</u></b><br><br>
Your selected product should have designed and implemented the initial elements of the game, as indicated in your group’s scenario.
For Assessment 3, the selected software product must be extended to cover the full product brief.<br><br>
For this assessment, you are allowed, but not required, to add other features or behaviours, as desired, but these must be fully
explained and justified in the deliverables, and must not violate the requirements for the game.
</div>
</div>
</div>
<div class="card">
<div class="card-header" id="headingFour">
<h2 class="mb-0">
<button class="btn btn-link collapsed" type="button" data-toggle="collapse" data-target="#collapseFour" aria-expanded="false" aria-controls="collapseFour">
Assessment 4
</button>
</h2>
</div>
<div id="collapseFour" class="collapse" aria-labelledby="headingFour" data-parent="#accordionInfo">
<div class="card-body">
Assessment 4 requires you to work on a product other than that which the team worked on in Assessment 3.
After product selection, changes will be issued. There are thus two preliminary phases before the main phase of
Assessment 4. For Assessment 4, there is also an assessed presentation which will take place in Summer week 4.<br><br>
<b><u>Phase 1: selection</u></b><br><br>
After the submission of Assessment 3. each team has a short period to consider the products of the other teams.
In the <b>Spring Week 7 practical</b> class that your team attends, each team will present its product, and can then
discuss with other teams. On Spr/8/Mon, each team is required to register, by 10am, their choice of product to
work on in Assessment 4, by <b>emailing the lecturers</b>.<br><br>
The only constraint on selection is that a team is not allowed to use its own Assessment 3 software for Assessment 4.
A team is allowed to use another team’s Assessment 3 extension of its original Assessment 2 product, but must work from
the Assessment 3 version.<br><br>
In selecting a software product, criteria that may be considered include: (1) the overall quality of the software product;
(2) estimates of effort remaining to make the required changes to the implementation; (3) clarity and quality of the requirements
specification, architecture, testing and implementation.<br><br>
A bonus of 2 marks will be added to the team’s Assessment 3 mark for each registered selection of the team’s software product
for Assessment 4, with the condition that no individual can attain more than 100% for Assessment 3.<br><br>
<b><u>Phase 2: requirements change</u></b><br><br>
For each group, a small set of changes will be issued on Spr/8/Mon (after all teams have registered their choice of product);
these may include changes to the scenario and/or introduction of new requirements.<br><br>
Using your selected software product, the team must modify the software product and supporting documentation to address these
changes. Teams must also produce an up-to-date website for the game.<br><br>
<b><u>Assessment 4: Assessed Presentation [20 marks]</u></b><br><br>
Each team is required to make a presentation of the finished game as if to an external client. The client, who will be an
experienced software engineer or games developer, will question the teams about their games and may ask to see the accompanying
marketing and technical information on the website.<br><br>
The presentation should assume that the client is interested in buying or marketing the product, and is thus aware of the
requirements specified for the product (including the changes in Assessment 4). Whilst the client will be interested, in
general, in major design decisions, the quality of the software, and the playability of the game, s/he is likely to be also
interested in the potential market for, and extensibility of, the product.<br><br>
The presentation will take place in a meeting room with access to the University computer network: within this constraint,
teams can use any appropriate media, and any combination of team members may take part. The presentation should take at most
<b>5 minutes</b>.<br><br>
Each team will be marked on the clarity and appropriateness of its presentation and its interaction with the client. Marking is
independent of the client’s award (the prize!) for what s/he considers the best product.
</div>
</div>
</div>
</div>
</div>
<!--- Footer -->
<footer id="Footer">
<div class="container-fluid padding">
<div class="row text-center">
<div class="col-md-4">
<h2><Dalai Java/></h2>
<hr class="light">
<p>DalaiJavaCS@gmail.com</p>
<p>University of York</p>
<p>Computer Science</p>
</div>
<div class="col-md-4">
<hr class="light">
<h5>Our Hours</h5>
<hr class="light">
<p>Monday: 9am- 5pm</p>
<p>Saturday: 10am - 4pm</p>
<p>Sunday: Closed</p>
</div>
<div class="col-md-4">
<hr class="light">
<h5>Other Stuff</h5>
<hr class="light">
<p>Monday: 9am- 5pm</p>
<p>Saturday: 10am - 4pm</p>
<p>Sunday: Closed</p>
</div>
<div class="col-12">
<hr class="light-100">
<h5>© Dalai Java</h5>
</div>
</div>
</div>
</footer>
</body>
</html>