HeaderSIS.jpg

IS480 Team wiki: 2017T2 Tetris Finals

From IS480
Jump to navigation Jump to search
Tetris' Logo


TtMenu Home s.png TtMenu About.png TtMenu Overview.png TtMenu PM.png TtMenu Docu.png


TtMenu MidtermWiki.png TtMenu FinalWiki s.png


Project Progress Summary

Finals1 progress.png


Final Slides Deployed Site
Finals2 downloadppt.png link=http://www.default-environment.bxypxxac43.ap-southeast-1.elasticbeanstalk.com/home.jsp here

Project Highlights:

Our key highlights
- We developed a rule engine to monitor the behaviour of the elderly to send out notifications to social caregiver in the case of anomalies. Our rule engine is different than those our competitors. We allow more customisability - parameters in the rules can be modified.
- Innovation 1: Reduced caregiver efforts with collaboration and management tools. This is called Caregiver Groups. Caregivers can work together to care for one patient.
- Innovation 2: Reduced attention span required to look after elderly. This is called Escalation Policy. Allows caregiver to intervene timely only (through SMS) when an anomaly or an event of interest occurs.
- Managed a team with complicated HR aspects.

Project Challenges:

Our challenges faced includes:
- Miscommunication from Project Sponsor representative to the group on project scope initially. Team worked on Raspberry Pi, xbee, Mosquito and Python initially during project acceptance stage. Team believed the project involved heavily on IOT and sensors, which eventually was debunked. Our project takes in JSON from the sensors and sensors are out of the project scope.
- Team member absence was an issue. Work was entrusted to him and when the member went MIA and subsequently returned, we give him many chances, but each time, we were cheated of our good will. He went missing and went for overseas trips, giving unsubstantiated reasons. No handover was done and willingness to code share was limited. We had to figure out and recode some portions.

Project Achievements:

Our Key Achievement from the Project to our Client
- Simple and clean UI/UX that makes it easy for the client and the caregivers to use

Project Management

Project Schedule (Plan Vs Actual):

Planned vs ACTUAL.png

Project Metrics:

We collected data and compiled the analysis into these categories: risk, change management, schedule & bugs.

Technical Complexity:

Our technical complexity for the project is articulated in the Architecture Diagram, showing the interactions and technologies used.
For the Rule Engine, we devised and developed listeners which had to check at regular intervals for anomaly in sensor data as well as for the escalation tiers in SMS.

Quality of product

Intermediate Deliverables:

Documentation Link
Project Overview Description
Project Video Pitch
Poster
Project Management Schedule
Schedule Metrics
Risk Management
Change Management
Project Documentation Prototype
Scenario & Use Case

Deployment:

Our Project has been deployed here

Reflection

Team Reflection:

The team struggled, worked hard and emerged stronger as a team during the project. Forming–storming–norming–performing, following the Tuckman Ladder, and adjourning amicably.

Individual Reflection:

Zhen Hui (Project Manager)
IS480 was a good opportunity to work in a challenging project and in a challenging team. I learnt a lot about client relations, presentations, managing requirements, risks and expectation from multiple sources, coming in simultaneously. I believe that I grew and became stronger on a professional basis in the course of this SMUX course. It was a great learning experience.

Elliotz (Deputy PM, Systems Analyst)
I was given the opportunity to learn new programming concept and software. This project experience has helped me to improve my programming skills for my future career after graduation

Irshad (Lead Backend)
I learnt to develop the ability to explain how code and functionality works to other team members and external stakeholders. This is important because to integrate the various parts of the app together, they must be compatible with one another. Often, we are required to work on other people’s code, debug and add on if necessary. I also learnt to work with the client to translate requirements into use cases and working features of the app. It is important to be precise yet understandable.

Wei Liang (Lead Frontend)
The essences of good design are complex and subjective. The concept of aligning business requirement with user friendly interface forms another challenge. Through number of trial, I have learned that a good design is design for the user not for the individual.

Samantha (Quality Assurance)
I have learnt the importances of User Testing and how UTs are able to allow developers to better understand the user expectations. Though the whole process it can be quite time consuming, the UTs results does show where the application is leaking from the user's perspective.

Avinash (Backend)
Reflection is not prepared yet.