-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathEvaluation.html
More file actions
193 lines (159 loc) · 10.3 KB
/
Evaluation.html
File metadata and controls
193 lines (159 loc) · 10.3 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
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
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<meta name="description" content="">
<meta name="author" content="">
<title>Evaluation</title>
<!-- Bootstrap core CSS -->
<link href="vendor/bootstrap/css/bootstrap.min.css" rel="stylesheet">
<!-- Custom fonts for this template -->
<link href="vendor/fontawesome-free/css/all.min.css" rel="stylesheet">
<link href="https://fonts.googleapis.com/css?family=Varela+Round" rel="stylesheet">
<link href="https://fonts.googleapis.com/css?family=Nunito:200,200i,300,300i,400,400i,600,600i,700,700i,800,800i,900,900i" rel="stylesheet">
<!-- Custom styles for this template -->
<link href="css/grayscale.min.css" rel="stylesheet">
</head>
<body id="page-top">
<!-- Navigation -->
<nav class="navbar navbar-expand-lg navbar-light fixed-top" id="mainNav">
<div class="container">
<a class="navbar-brand js-scroll-trigger" href="#page-top">Team 18</a>
<button class="navbar-toggler navbar-toggler-right" type="button" data-toggle="collapse" data-target="#navbarResponsive" aria-controls="navbarResponsive" aria-expanded="false" aria-label="Toggle navigation">
Menu
<i class="fas fa-bars"></i>
</button>
<div class="collapse navbar-collapse" id="navbarResponsive">
<ul class="navbar-nav ml-auto">
<li class="nav-item">
<a class="nav-link js-scroll-trigger" href="index.html">Home</a>
</li>
<li class="nav-item">
<a class="nav-link js-scroll-trigger" href="Research.html">Research</a>
</li>
<li class="nav-item">
<a class="nav-link js-scroll-trigger" href="Requirements.html">Requirements</a>
</li>
<li class="nav-item">
<a class="nav-link js-scroll-trigger" href="HCI.html">HCI</a>
</li>
<li class="nav-item">
<a class="nav-link js-scroll-trigger" href="Design.html">Design</a>
</li>
<li class="nav-item">
<a class="nav-link js-scroll-trigger" href="Testing.html">Testing</a>
</li>
<li class="nav-item">
<a class="nav-link js-scroll-trigger" href="Evaluation.html">Evaluation</a>
</li>
<li class="nav-item">
<a class="nav-link js-scroll-trigger" href="Management.html">Management</a>
</li>
</ul>
</div>
</div>
</nav>
<!-- about Section -->
<section id="about" class="about-section ">
<div class="container">
<div class="row">
<div class="col-lg-8 mx-auto">
<strong><h1 style="color:#729E9D"><img src="img/EvaluationIcon.png" alt="pic" height="75" width="75" hspace="15">EVALUATION</h1></strong><br>
<h3 style="color:white;">Achievements Table</h3>
<span class="text-white-50 text"><img src="img/Requirements.png" alt="pic" height="1080" width="1020" class="req2" ><br><br></span><br><br>
<h3 style="color:white;">Individual Contribution Table</h3>
<span class="text-white-50 text"><img src="img/Cont.png" alt="pic" height="450" class="req2" ><br><br><br></span><br><br>
<h3 style="color:white;">Bugs</h3>
<span class="text-white-50 text">Here is a list of known bugs, and areas where certain functionalities aren't working as intended
<uL>
<li>Adding company association doesn't always work</li>
<li>On the other side, for corporate users they can't always see the individual users linked to them</li>
<li>Not all of the old graphs work</li>
<li>Some parts of the dashboard such as certain graphs aren't responsive </li>
<li>Sometimes, even if the user is logged out, the main dashboard is still visible</li>
</uL>
</span><br><br>
<h3 style="color:white;">Critical evaluation of the project</h3>
<span class="text-white-50 text"><br>
<h5 style="color:white;">User Interface & User Experience</h5>
Although the user interface and experience is fairly simple and minimalistic, it does achieve what it needs to do and we have
put a fair amount of work into making the login page, registeration page and the visualisations look nicer compared to what they looked like.
<br><br>Moreover, most of the user cases are somewhat similar to what you might find in a regular dashboard and thus it is highly likely that
the user experience would be smooth. Finally, a significant point to note is that our requirements were mostly concerned
with the backend of the web application rather than the front-end<br><br>
<h5 style="color:white;">Functionality</h5>
This part was the most challenging one as we had to make sure that the previos version of fhir fli still works in addition to
what we add to it. We did try our best to achieve that, however there were a lot of bugs introduced when attempting to add
new functionalities, we did fix most of them, but some still remain, mainly on the corporate side.<br><br>
<h5 style="color:white;">Stability</h5>
The project was developed using very popular and stable JavaScript libraries, and this was noted during our research and
affected our choices. And thus it the stability of the project is fairly good. Also, future developers will be able to find
a wide range of resources and tutorials about the technologies used in developing this project which will keep this project
alive for a long while as it is open-source.<br><br>
<h5 style="color:white;">Efficiency</h5>
As mentioned in our Design section, we have done a lot of refactoring and thought a lot about our design decisions to make
generating the visualisations as smooth and efficient as possible (as this project doesn't have any particular algorithms) and thus
the efficiency section is concerned with the front-end which is basically using React, Redux and Victory to manipulte the DOM.<br><br>
<h5 style="color:white;">Compatability</h5>
The project was fairly tested (as in the Testing section) on several distinct platforms including but not limited to Firefox,
Google Chrome, Microsoft Edge, and Safari and was found to be working as expected. However, regarding on mobile phones and tablets it wasn't as
thoroughly tested. <br><br>
Web browser compatibility was less of a priority for this project. Furthermore, as the practical usecase of the system would be for an internal visualization tool for the Client's company, the range of expected browser types would be significantly smaller - i.e for security reasons, company users would not be using older versions of Internet Explorer, as it has numerous vulnerabilities.
Thus,test were only performed recent browser versions (< 1 year since last update) and only tested desktop based screen resolutions.
<br><br>
<h5 style="color:white;">Maintainability</h5>
This was one of the most significant parts when developing FHiR FLI 2.0 as we took this project over from someone else and we
knew that someone else is going to take it over from us and thus there are a wide range of explanations that can be found on this
website to help future developers understand the current codebase. We also made sure to comment and document every part of the
code that we have written ourselves just that future developers wouldn't struggle too much to understand it and build upon it.<br><br>
<h5 style="color:white;">Project Management</h5>
After our first month, we started setting milestones and deadlines for finishing the tasks (which can be found in the Gantt chart below)
There were a good amount of tasks to do ranging from HCI diagrams, reports, presentations to technical ones and thus we had to make sure
that those tasks were spread out across the span of 5 months and not quickly rushed through in the last month. Certainly, the bi-weekly reports
and the weekly progress check on both the labs and the term one did help keep us on track.
</span><br><br>
<h3 style="color:white;">Future Work</h3>
<span class="text-white-50 text">This section is about features that we wanted to implement but didn't have enough
to implement due to time constraints, however, for future developers it is fairly easy to start where we stopped.<br><br>
<ul>
<li>Improve the design of the user's dashboard, this is due to the fact that the current design is fairly minimalistic
and doesn't adhere to modern data visualisations dashboards, we worked on this by improving the login and registeration
page, but we didn't improve the user's dashboard.
</li><br><br>
<li>
Improve the decentralised data storage system, this was one of our most challenging requirements, at the beginning
we attempted the implementation of Solid inrupt (can be found here <a href="https://solid.inrupt.com ">Solid Inrupt</a>)
but we couldn't finish certain parts due to lacking documentation and support, however, there are a lot of useful information
that will certainly help that can be found on our Research tab, also here is a general outline of what needs to be done
<ol>
<li>Implement solid-auth which is a JS browser library that allows users to authenticate access to their Solid PODS,
this can be found here <a href="https://github.com/solid/solid-auth-client">solid-auth</a>
</li>
<li>After doing that, integrate the rdflib NodeJS library on the backend, this can be found here
<a href="https://www.npmjs.com/package/rdflib">rdlib</a>, this is based on manipulating linked data which is the
essential foundation of Solid inrupt, this is the part where the actual writing data process is done to the users
Solid Pods
</li>
</ol>
</li><br><br>
<li>Design more distinct graphs for representing the Fitbit data, the best library for doing this is
<a href="https://formidable.com/open-source/victory/">Victory JS</a>, you will find that our codebase is
designed to facilitate the use of this library. </li><br><br>
<li>Integrate the goals system with the Fitbit data</li>
</ul>
</span><br><br>
<br><br><br><br>
</div>
</div>
</div>
</section>
<!-- Bootstrap core JavaScript -->
<script src="vendor/jquery/jquery.min.js"></script>
<script src="vendor/bootstrap/js/bootstrap.bundle.min.js"></script>
<!-- Plugin JavaScript -->
<script src="vendor/jquery-easing/jquery.easing.min.js"></script>
<!-- Custom scripts for this template -->
<script src="js/grayscale.min.js"></script>
</body>
</html>