HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki:2017T2 Zenith FinalWiki"

From IS480
Jump to navigation Jump to search
 
(21 intermediate revisions by 2 users not shown)
Line 45: Line 45:
 
===Deployed site link===
 
===Deployed site link===
 
<center>
 
<center>
[[Image: Zenith deployment link.jpeg |600px|link=http://www.themedsense.com]]
+
[[Image: Zenith deployment link.jpeg |600px|link=https://themedsense.com/]]
 +
 
 +
Staging site: http://medsense-staging-env.ap-southeast-1.elasticbeanstalk.com/
 
</center>
 
</center>
  
Line 52: Line 54:
 
Our project schedule is divided into 13 iterations.  
 
Our project schedule is divided into 13 iterations.  
 
* We are currently on our 12th iteration (26 Mar - 8 Apr 2018).
 
* We are currently on our 12th iteration (26 Mar - 8 Apr 2018).
* Up till 3 Apr 2018, we have completed <b>94</b>% of our development progress.  
+
* Up till 4 Apr 2018, we have completed <b>100</b>% of our development progress.  
 
* 2 User Acceptance Tests were conducted before the Final Presentation. The results are shown [[IS480_Team_wiki:2017T2 Zenith_user_testing|here]].  
 
* 2 User Acceptance Tests were conducted before the Final Presentation. The results are shown [[IS480_Team_wiki:2017T2 Zenith_user_testing|here]].  
* Achieved and exceeded [[IS480_Team_wiki:2017T2 Zenith_x-factor|Midterms X-factor]]. <<update after UAT>>
+
* Achieved and exceeded [[IS480_Team_wiki:2017T2 Zenith_x-factor|Finals X-factor]].
 
 
  
 
Unexpected events:
 
Unexpected events:
* List of requirement changes after Midterms can be viewed [[IS480_Team_wiki:2017T2_Zenith_change_management#Change log (till Midterms)| here]].
+
* List of requirement changes after Midterms can be viewed [[IS480_Team_wiki:2017T2_Zenith_change_management#Change log (till Finals)| here]].
 
</div>
 
</div>
  
 
==Project Management==
 
==Project Management==
 
<div style="font-family: Verdana;">
 
<div style="font-family: Verdana;">
<b>Iteration Progress:</b> 12 of 13<br/>
+
<b>Iteration Progress:</b> 13 of 13<br/>
<b>Features Completion:</b> 94% (43 out of 46 features)<br/>
+
<b>Features Completion:</b> 100% (46 out of 46 features)<br/>
 
<b>Confidence Level:</b> 100%
 
<b>Confidence Level:</b> 100%
 
</div>  
 
</div>  
Line 75: Line 76:
 
<br>
 
<br>
 
[[File:Zenith_final_scope.JPG|center|800px]]
 
[[File:Zenith_final_scope.JPG|center|800px]]
<br>
 
<center><b>  Note: will be updated after our last UAT. </b> </center>
 
 
<br>
 
<br>
  
Line 197: Line 196:
  
 
[[File:Zenith risk metric.png|center|600px]]
 
[[File:Zenith risk metric.png|center|600px]]
 
 
{| class="wikitable" style="font-family:Garamond; background-color:#FFFFFF; width: 1000px"|+ '''Cells left-aligned, table centered'''
 
{| class="wikitable" style="font-family:Garamond; background-color:#FFFFFF; width: 1000px"|+ '''Cells left-aligned, table centered'''
 
|-
 
|-
Line 211: Line 209:
  
 
|style="text-align: center;"| 1
 
|style="text-align: center;"| 1
|style="text-align: center;"| Technical
+
|style="text-align: center;"| Project Management
|style="text-align: left;vertical-align: center"| Ransomware attacks on Database
+
|style="text-align: left;vertical-align: top"| The schedule is planned based on macro functionalities, so small coding tasks may have been left out / time is underestimated due to lack of experience.
|style="text-align: center;"| Low (but it happened)
+
|style="text-align: center;"| Medium
|style="text-align: center;"| High
+
|style="text-align: center;"| High  
|style="text-align: center;"| B
+
|style="text-align: center;"| A
|style="text-align: left;vertical-align: top"| System Architect to improve database security  
+
|style="text-align: left;vertical-align: top"|Project Manager will review the project schedule and the time needed for each task regularly, and make changes when necessary.  
 
|-
 
|-
  
 
|style="text-align: center;"| 2
 
|style="text-align: center;"| 2
|style="text-align: center;"| Organizational
+
|style="text-align: center;"| Client Management
|style="text-align: left;vertical-align: center"| New members in NUS MedSense Team
+
|style="text-align: left;vertical-align: top"| Client may request for changes to existing functionalities or request for new functionalities. These increases in scope may delay the project completion.
 
|style="text-align: center;"| Medium
 
|style="text-align: center;"| Medium
 
|style="text-align: center;"| Medium  
 
|style="text-align: center;"| Medium  
 
|style="text-align: center;"| B
 
|style="text-align: center;"| B
|style="text-align: left;vertical-align: center"| Project Manager will be in constant communication with new members, and will regularly review the scope with them.
+
|style="text-align: left;vertical-align: top"| Team will have to consider expertise and time required. Project Manager will manage the expectations of the client.  
 
|-
 
|-
  
 
|style="text-align: center;"| 3
 
|style="text-align: center;"| 3
 
|style="text-align: center;"| Project Management
 
|style="text-align: center;"| Project Management
|style="text-align: left;vertical-align: center"| Members falling sick or going overseas doing school period, reducing team's available manpower. This can cause a potential delays in the project
+
|style="text-align: left;vertical-align: top"| Team members feel overwhelmed by the workload, and feel that they are increasingly burned out.  
 
|style="text-align: center;"| Medium
 
|style="text-align: center;"| Medium
|style="text-align: center;"| Medium
+
|style="text-align: center;"| Low
|style="text-align: center;"| B
+
|style="text-align: center;"| C
|style="text-align: left;vertical-align: center"| Team members should constantly check on the health and well-being of one another, as well as update the Project Manager of any overseas plans as early as possible
+
|style="text-align: left;vertical-align: top"| Team members will limit the increases in scope, and prioritize functions in case functions need to be dropped.
 
|-
 
|-
 
|}
 
|}
Line 243: Line 241:
 
===Technical Complexity:===
 
===Technical Complexity:===
  
====Natural Language Processing====
 
 
<div style="font-family: Verdana;">
 
<div style="font-family: Verdana;">
Natural Language Processing, or NLP for short, is broadly defined as the automatic manipulation of natural language, like speech and text, by software. The study of natural language processing has been around for more than 50 years and grew out of the field of linguistics with the rise of computers.
+
Our technical complexity comprises of:
 
+
* Use of Natural Language Processing to mark open-ended questions. [[IS480 Team wiki:2017T2 Zenith Midterm Wiki#Natural Language Processing|(Discussed here during Midterms) ]]
Our team decided to employ NLP techniques to perform automated marking for open ended questions. This benefits the user as professors do not need to mark each answer and students can receive immediate feedback with regards to their answers.
+
* Development of game for students, including anti-cheating mechanisms. [[IS480 Team wiki:2017T2 Zenith Midterm Wiki#Game development|(Discussed here during Midterms)]]  
 
+
* Security features: firewall, automated backup for database, HTTPS protocol, SSH tunnel, and encryption of environment variables. [[IS480 Team wiki:2017T2 Zenith Midterm Wiki#Added security features|(Discussed here during Midterms)]]
Below are some of the techniques used:
+
* Recommendation Models for Students and Professors.
 
+
</div> <br>  
<b>Tokenization</b>
 
 
 
Given a character sequence and a defined document unit, tokenization is the task of chopping it up into pieces, called tokens , perhaps at the same time throwing away certain characters, such as punctuation.  
 
 
 
[[Image:Zenith tokenization.PNG|center|600px|link=]]
 
<center><b>An example of tokenization. Library used: Natural for Nodejs</b> https://github.com/NaturalNode/natural#tokenizers</center>
 
 
 
<b>Removing Stopwords</b>
 
 
 
Sometimes, some extremely common words which would appear to be of little value in helping select documents matching a user need are excluded from the vocabulary entirely. In natural language processing, Stopwords are words that are so frequent that they can safely be removed from a text without altering its meaning. Hence, for automated marking, we removed all common words from the submitted answer. Doing this significantly reduces the number of tokens our system has to match and store.  
 
 
 
 
 
[[Image:Zenith stopwords.png|center|500px|link=]]
 
<b><center>An example of a stop list of 25 semantically non-selective words</center></b>
 
 
 
<b>Stemming</b>
 
 
 
For grammatical reasons, answers are going to use different forms of a word, such as organize, organizes, and organizing. Additionally, there are families of derivationally related words with similar meanings, such as democracy, democratic, and democratization. In these situations, we have to treat these words to be the same, as they have the same root meaning.
 
 
 
The goal of both stemming is to reduce inflectional forms and sometimes derivationally related forms of a word to a common base form.
 
 
 
We decided to use the Porter Stemming Algorithm (https://tartarus.org/martin/PorterStemmer/index.html) as it is the most popular algorithm for stemming English and has shown to be empirically very effective.
 
 
 
Porter's algorithm consists of 5 phases of word reductions, applied sequentially. Within each phase there are various conventions to select rules, such as selecting the rule from each rule group that applies to the longest suffix.
 
  
[[Image:Zenith stemming.png|center|500px|link=]]
+
====Recommendation Models  ====
<b><center>Example of a rule in the Porter Stemming Algorithm</center></b>
+
=====Student Recommendation Model=====
</div>
 
<br>
 
 
 
====Game development ====
 
 
<div style="font-family: Verdana;">
 
<div style="font-family: Verdana;">
Together with the NUS team, we developed a few basic game rules.  
+
We have implemented a recommendation model for students, to address their individual weaknesses.This model is guided by the following principles: <br> <br>  
 
+
# Recommend beginner/advanced cases based on year of study: Medical students in their third year and below will be recommended beginner cases, while medical students who are in the fourth and fifth year of study will be recommended advanced cases. This is in accordance with their curriculum in school. <br> <br>  
<b>Leveling System</b>  
+
# Recommend most popular cases for new users: A new user might feel overwhelmed with the selection of cases. Hence, we will recommend the popular cases for them to familiarize themselves with the games. Their performance in these popular cases is a good gauge of their personal strengths and weaknesses, and will serve as a starting point for more targeted recommendations in the future. <br> <br>  
 
+
# Recommend cases in the sub-specialties they are weakest in, based on the cases they have previously done: Through our model, we aim to tailor instruction to individual learner's needs. By recommending students to practice on topics they are weaker in, we believe that the medical students will be able to learn in a more holistic manner. <br> <br>
For our application, we introduce a leveling system for student. In its simplest form, leveling up occurs through the process of gaining enough experience points until a target experience point total is reached. Once the target is met, the student's character "levels up," and a new target experience threshold is set. Students gains experience points (XP) by attempting a medical case. The amount of XP is dependent on how well the student scores.
+
</div>
 
+
=====Professor Recommendation Model=====
Currently, the main selling point of the medical cases is to practice for their exams. By introducing the leveling system, we hope to further incentivise students to attempt  medical cases on our application.  The idea is to ensure that students will be playing the cases throughout the year rather than just during peak (exam) periods.
 
[[Image:Zenith leveling formula.PNG|center|300px|link=]]
 
<b><center>Formula for calculating Level</center></b>
 
 
 
<b>Anti Cheat Mechanism for MCQ Scoring</b>
 
 
 
There can be more than one correct answer for each MCQ questions. Hence we use multi-select MCQ questions in our game. However, the problem we face is that students can simply tick all the options to get the correct answer. Hence, we developed a rule that penalizes the student for every wrong option selected.  
 
 
 
<b>Anti Cheat Mechanism for Repeating Cases</b>
 
 
 
Another rule we developed is to halve the total amount of experience points gained for each subsequent game play of the same case. This is to reduce the incentive of repeating the same case again and again for the sake of leveling up. Furthermore, students are already expected to score better after doing the case, as the answers are revealed at the end of each case.
 
 
 
</div>  
 
<br>
 
 
 
====Added security features====
 
 
<div style="font-family: Verdana;">
 
<div style="font-family: Verdana;">
In December 2017, our MongoDB database was compromised and held hostage by ransomware. We were instructed to pay 0.1 bitcoin (USD $1594) for the return of our data. Fortunately, we had backed up the data so there was no need for us to pay the ransom. Since this incident, we have taken additional measures to ensure that this does not happen again.
+
For Professors, knowing which areas students are commonly weak in will assist them in their course planning. We would like to encourage Professors to upload more cases on the students' weaker topics. The recommendation model is guided by the following principles: <br> <br>
 
+
# The recommended sub-specialties are based on the overall cohort performances. <br> <br>
 
+
# Recommend sub-specialties with the least number of cases if there is insufficient data to determine the weaker topics: Professors will not be able to gauge students' performances in areas where there are no cases for students to try. The model will encourage them to upload cases in those sub-specialties, so that they can get a more accurate idea of the students' weaknesses. <br> <br>
We have implemented / will be implementing the following:
+
# Recommend sub-specialties where the number of pending cases is above a certain threshold: Doing so will encourage Professors to vet the pending cases, which will increase the number of cases for students to practice on. <br> <br>
*Firewall
 
*SSH Tunnel
 
*Automated backup
 
*HTTPS protocol
 
*Encrypt environment variables
 
 
</div>
 
</div>
  
Line 390: Line 338:
 
===Team Reflection:===
 
===Team Reflection:===
 
<div style="font-family: Verdana;">
 
<div style="font-family: Verdana;">
 
+
Throughout our FYP journey, we have tried our best to implement the changes that our clients have requested, even if it meant additional coding hours or having to rework the project schedule multiple times. This is because we place emphasis on our project's value to the clients. However, as we approach the completion of our project, we had to scrutinize every change more closely. We had to find a balance between providing the best value to the clients, as well as our workload and confidence of completing the project in time.  
Our team has learnt the importance of working together closely with our clients, to ensure an ideal alignment between the client business requirements and our end-product. Throughout our development process, we are constantly plagued with minor hiccups and bugs. However, our team feels that our most valuable quality is resilience, as we tackle each and every problem with our ineffable tenacity and innovation.
 
 
</div>
 
</div>
  
 
=== Individual Reflections: ===
 
=== Individual Reflections: ===
 
<div style="font-family: Verdana;">
 
<div style="font-family: Verdana;">
<b>Amelia: </b>
+
<b>Amelia: </b><br>
 +
Our stakeholders have been actively involved in our project right from the start. Apart from meeting our supervisor regularly, we have been in constant communication with our other stakeholders. Working with a team of 17 entails certain challenges. I have learnt to manage different perspectives and expectations, as well as balance the workload and priorities of my team.
 +
<br> <br>  
  
It has been a very experimental journey managing the team since the project started. New challenges are always popping up, and I have learnt to manage the workload of each member more carefully. I believe communication is today’s important skill, be it raising issues with the team or simple dissemination of information. That is why I ensure that there are no communication lapses in our team.
+
<b>Chin Rui: </b> <br>
<br>  
+
It has been a challenging journey technically. The application architecture has undergone multiple major changes, especially our security configurations, to ensure better quality and continuity for our clients. I have also discovered the difficulties in planning a software architecture after taking into account budget, skill and technical constrains.
 +
<br> <br>  
  
<b>Chin Rui: </b>  
+
<b>Ervin: </b><br>  
 
+
As the Quality Assurance lead, I had to scrutinize every single corner case in the application, and constantly come up with more test cases. After our midterm presentation we conducted regression testing, a User Acceptance Test and load testing. I learnt that observing users during the UAT is imperative, as some users tend to not notice certain issues, or they do not voice them out. The UAT is also an opportunity for us to see if the functions are indeed useful for the users.  
It has been a challenging 7 weeks since our acceptance. The application architecture has undergone multiple major changes, especially our security configrations, to ensure better quality and continuity for our clients. The security breach incident was an eye-opening experience for me, and I have learnt to never take security for granted. I have realised that security should be a key consideration when planning an application's architecture because every implementation or change made could introduce a new vulnerability for potential attackers to take advantage of. Aside from the security enhancements, I have also discovered the difficulties in planning a software architecture after taking into account of budget, skill and technical constrains.
+
<br><br>  
<br>  
 
 
 
<b>Ervin: </b>
 
 
 
Being the previous Business Analyst, it was an enriching and mind-boggling experience researching on various Natural Language Processing techniques and trying to appraise their adequacy and appropriateness for our application. Moving on as the Quality Assurance lead, I hope I do not offend everyone involved in development by scrutinizing every single corner case in the application.
 
<br>
 
 
   
 
   
<b>Ming Rui: </b>
+
<b>Ming Rui: </b><br>  
 
+
After our Midterm presentation, we completely changed the UI of our application. We went back to the paper and Axure prototypes, and thought of ways to improve the user experience. The final designs are a product of multiple revamps, each better compared to the previous. I have learnt the importance of gathering feedback from a larger group of users, instead of just the Medsense team from NUS.
The opportunity to be able to apply the entire design thinking process from the creation of prototypes to the actual web development have been arduous but rewarding journey. The final designs of the application are a product of multiple revamps, each better compared to the previous. I have learnt the importance of gathering feedback from the clients as well as real users.
+
<br> <br>  
<br>
 
 
 
<b>Qimin: </b>
 
 
 
Having to pick up Node.js and React.js in a short period of time really pushed me to learn and adapt at a much faster pace. There are many front-end and back-end considerations to factor in during the design process, such as the communication between parent-child components and the use of redux store versus a direct http request to the database. I believe that my technical skills have definitely improved over the past few weeks.
 
<br>  
 
  
<b>Ricky: </b>
+
<b>Qimin: </b><br>
 +
Due to the various changes we have made over the course of our project, we had to do some refactoring. I have learnt that regardless of the time and effort we put into getting the schema right at the start of the project, changes are inevitable during the development process. Being the Full-Stack Support has definitely challenged me to improve my technical skills and resilience as I dealt with the bug infestation that came with the refactoring.
 +
<br> <br>  
  
It has been a great experience seeing how the project has grown from infancy to where it is today. As a backend developer, I have realised that is important to have a seamless integration of the frontend components with the server side logic as well as designing and implementing data storage solutions. Throughout the past few months working on the project, I have learnt that what’s even more important than completing the work assigned to me is to help my team members with their tasks. This will enable smoother and faster progression as a team.
+
<b>Ricky: </b><br>
 +
As a backend developer, I have realised that is important to have a seamless integration of the frontend components with the server side logic as well as designing and implementing data storage solutions. It has been a great experience being the technical lead, and I am glad that I could help my team members with the technical issues they faced.  
 
<br>  
 
<br>  
 
<div>
 
<div>

Latest revision as of 14:46, 16 April 2018

Zenith banner.png

Home

Team

Project Overview

Project Management

Documentation

Main Wiki

Midterm Wiki Final Wiki


Zenith final header.PNG


Project Progress Summary

Finals Slides

Zenith Finals Slides

Deployed site link

Zenith deployment link.jpeg

Staging site: http://medsense-staging-env.ap-southeast-1.elasticbeanstalk.com/

Project Highlights

Our project schedule is divided into 13 iterations.

  • We are currently on our 12th iteration (26 Mar - 8 Apr 2018).
  • Up till 4 Apr 2018, we have completed 100% of our development progress.
  • 2 User Acceptance Tests were conducted before the Final Presentation. The results are shown here.
  • Achieved and exceeded Finals X-factor.

Unexpected events:

  • List of requirement changes after Midterms can be viewed here.

Project Management

Iteration Progress: 13 of 13
Features Completion: 100% (46 out of 46 features)
Confidence Level: 100%

Project Status:

A breakdown of tasks is shown in our project scope.


Zenith final scope.JPG


Project Schedule (Plan Vs Actual):

Milestones Overview:

Planned (Acceptance) Actual (Midterms)

Zenith midterm actual timeline.png

Zenith final actual timeline.png

Project Schedule:

Planned Schedule (Midterm)

Zenith final expected schedule.png



Changes in planned schedule (Midterm)

Zenith final changed schedule.png



Actual Schedule (Final)

Zenith final actual schedule.png

Project Metrics:

Task metric

Zenith task metric.png
Score TM <= 50 50 < TM <= 75 75 < TM <= 125 125 < TM <= 150 150 > TM
Action 1. Inform supervisor within 24 hours.
2. Re-estimate tasks for future iterations.
3. Consider dropping Tasks.
1. Re-estimate tasks for future iterations.
2. Deduct number of days behind from buffer days.
3. If there are no more buffer days, decide the functionalities to drop.
1. Our estimates are fairly accurate, and are roughly on track.
2. Add/deduct number of days ahead / behind from buffer days.
1. Re-estimate tasks for future iterations.
2. Add number of days ahead to buffer days.
1. Inform supervisor within 24 hours.
2. Re-estimate tasks for future iterations.

Bug metric

Zenith bug count.png

Zenith bug score.png

Note: There were no coding tasks for iteration 1.


Severity Low Impact High Impact Critical Impact
Description User interface display errors, such as out of alignment, colour used is not according to theme.

It does not affect the functionality of the system.

The system is functional with some non-critical functionalities are not working. The system is not functional.

Bugs have to be fixed before proceeding.


Points BM <= 5 5 < BM < 10 BM >= 10
Description The system does not need immediate fixing, could be fixed during buffer time or during coding sessions Coders to use planned debugging time in the iteration to solve the bug The team has to stop all current development and resolve the bug immediately



Project Risks:

Zenith risk metric.png
S/N Risk Type Description Likelihood Impact Level Threat Level Mitigation Plan
1 Project Management The schedule is planned based on macro functionalities, so small coding tasks may have been left out / time is underestimated due to lack of experience. Medium High A Project Manager will review the project schedule and the time needed for each task regularly, and make changes when necessary.
2 Client Management Client may request for changes to existing functionalities or request for new functionalities. These increases in scope may delay the project completion. Medium Medium B Team will have to consider expertise and time required. Project Manager will manage the expectations of the client.
3 Project Management Team members feel overwhelmed by the workload, and feel that they are increasingly burned out. Medium Low C Team members will limit the increases in scope, and prioritize functions in case functions need to be dropped.



Technical Complexity:

Our technical complexity comprises of:


Recommendation Models

Student Recommendation Model

We have implemented a recommendation model for students, to address their individual weaknesses.This model is guided by the following principles:

  1. Recommend beginner/advanced cases based on year of study: Medical students in their third year and below will be recommended beginner cases, while medical students who are in the fourth and fifth year of study will be recommended advanced cases. This is in accordance with their curriculum in school.

  2. Recommend most popular cases for new users: A new user might feel overwhelmed with the selection of cases. Hence, we will recommend the popular cases for them to familiarize themselves with the games. Their performance in these popular cases is a good gauge of their personal strengths and weaknesses, and will serve as a starting point for more targeted recommendations in the future.

  3. Recommend cases in the sub-specialties they are weakest in, based on the cases they have previously done: Through our model, we aim to tailor instruction to individual learner's needs. By recommending students to practice on topics they are weaker in, we believe that the medical students will be able to learn in a more holistic manner.

Professor Recommendation Model

For Professors, knowing which areas students are commonly weak in will assist them in their course planning. We would like to encourage Professors to upload more cases on the students' weaker topics. The recommendation model is guided by the following principles:

  1. The recommended sub-specialties are based on the overall cohort performances.

  2. Recommend sub-specialties with the least number of cases if there is insufficient data to determine the weaker topics: Professors will not be able to gauge students' performances in areas where there are no cases for students to try. The model will encourage them to upload cases in those sub-specialties, so that they can get a more accurate idea of the students' weaknesses.

  3. Recommend sub-specialties where the number of pending cases is above a certain threshold: Doing so will encourage Professors to vet the pending cases, which will increase the number of cases for students to practice on.

Quality of product

Intermediate Deliverables:

Stage Specification
Project Management Schedule
Minutes
Bug metrics
Task metrics
Risk management
Change management
Requirements Overview
Scope
Personas
Analysis Use case diagram
Architecture diagram
Technologies used
Design Prototypes
Testing User Acceptance Test 1 (11 - 13 Feb 2018)
User Acceptance Test 2 (4 - 10 Apr 2018)

Testing:

  • Creation of test cases during development.
  • Functionality testing after completion of function.
  • Regression testing at the end of every iteration.
  • 2 UATs completed by Final Presentation.
  • 1 UAT has been completed after Midterms. To view the results of this UAT, click here.

Reflections

Team Reflection:

Throughout our FYP journey, we have tried our best to implement the changes that our clients have requested, even if it meant additional coding hours or having to rework the project schedule multiple times. This is because we place emphasis on our project's value to the clients. However, as we approach the completion of our project, we had to scrutinize every change more closely. We had to find a balance between providing the best value to the clients, as well as our workload and confidence of completing the project in time.

Individual Reflections:

Amelia:
Our stakeholders have been actively involved in our project right from the start. Apart from meeting our supervisor regularly, we have been in constant communication with our other stakeholders. Working with a team of 17 entails certain challenges. I have learnt to manage different perspectives and expectations, as well as balance the workload and priorities of my team.

Chin Rui:
It has been a challenging journey technically. The application architecture has undergone multiple major changes, especially our security configurations, to ensure better quality and continuity for our clients. I have also discovered the difficulties in planning a software architecture after taking into account budget, skill and technical constrains.

Ervin:
As the Quality Assurance lead, I had to scrutinize every single corner case in the application, and constantly come up with more test cases. After our midterm presentation we conducted regression testing, a User Acceptance Test and load testing. I learnt that observing users during the UAT is imperative, as some users tend to not notice certain issues, or they do not voice them out. The UAT is also an opportunity for us to see if the functions are indeed useful for the users.

Ming Rui:
After our Midterm presentation, we completely changed the UI of our application. We went back to the paper and Axure prototypes, and thought of ways to improve the user experience. The final designs are a product of multiple revamps, each better compared to the previous. I have learnt the importance of gathering feedback from a larger group of users, instead of just the Medsense team from NUS.

Qimin:
Due to the various changes we have made over the course of our project, we had to do some refactoring. I have learnt that regardless of the time and effort we put into getting the schema right at the start of the project, changes are inevitable during the development process. Being the Full-Stack Support has definitely challenged me to improve my technical skills and resilience as I dealt with the bug infestation that came with the refactoring.

Ricky:
As a backend developer, I have realised that is important to have a seamless integration of the frontend components with the server side logic as well as designing and implementing data storage solutions. It has been a great experience being the technical lead, and I am glad that I could help my team members with the technical issues they faced.