IS480 Team wiki: 2016T1 Hungrymen FinalWiki
|HOME||ABOUT US||PROJECT OVERVIEW||PROJECT MANAGEMENT||DOCUMENTATION|
- 1 Project Progress Summary
- 2 Project Management
- 3 Quality of Product
- 4 Reflections
Project Progress Summary
Finals Slides, Video and Poster
- Conducted Market Survey to review feasibility, problems and potential solutions.
- Conducted two Expert Testing to gain insights about Smart Hawker App's interface and two UATs
- Conducted two User Acceptance Tests to validate and collate feedback according to Hawker's surveyed, to make necessary app improvements.
- Deployed onto testflight on the 8th of April 2016
- Deployed onto App Store on the 27th of September 2016
- Smart Hawker iOS Application compatible for iOS 9.3 and above
- Backend migrated from Parse to self-hosted AWS
- Finding Users:
Our team had to find the correct timing to go down and conduct our UATs as well as promoting our app. Initially, we went down around noon which was the lunch period and they were all busy. Hence our team handle this situation by going down at off-peak hours.
- Learning New Programming Languages:
Our team find it particularly challenging when there was no one to guide us. However, we dealt with this by watching Youtube tutorials, Google and consulting friends that had done an iPhone App before.
The most challenging area of is480 project is the communication between team members, sponsors and supervisors. To ensure that there is no conflicts, tension or miscommunication, our team abide by the rule of speaking up and also constant communication with our sponsors and supervisors of our progress.
- Available on App Store
- Application features and ideas validated with the target market and improved to fit their preferences.
- More than 70 users sign ups
- More than 15 weekly users consistent usage for 1-Month
Highlights of Schedule Changes
|1||Added sync function in iteration 9 upon midterm review feedback|
|2||1. Added iOS10 upgrade in iteration 10. Initially our team did consider a possibility of an iOS10 upgrade but was not sure if it would be release during our FYP period as apple did not give a concrete date. So when they release iOS10 upgrade, our team wanted to make sure that xcode 8 IDE is stable before we planned it into our schedule. |
2. Added migration in iteration 10
|3||Included poster and video into our documentation at Iteration 10|
|4||At the end of iteration 10, our team realize that backend admin module and migration was more complex than expected hence we will delay backend admin module to iteration 11 and migration to iteration 12|
|5||At the end of iteration 11, there was additional function for backend admin module and hence our team delay it till iteration 12|
|Iteration||Bug Score||Summary of Bugs and Issue||Action Taken|
|Stopped progress for Iteration 3 to resolve bugs that were unsolved by end of iteration 2. All bugs were resolved within 1 day (4th July).|
|Stopped progress for Iteration 7 to resolve bugs that were unsolved by end of iteration 6. All bugs were resolved within 1 day (29th Aug).|
|Stopped progress for Iteration 8 to resolve bugs that were unsolved by end of iteration 7. All bugs were resolved within 2 days (12-13th Sept).|
|Stopped progress for Iteration 10 to resolve bugs that were unsolved by end of iteration 9. All bugs were resolved within 2 days (10-11th Oct).|
Migration of Parse
1. Understand of System Architecture
With no prior knowledge on server architecture, migration of Parse challenges us as we will have to study typical architecture before we are able to set up the server. We will have to understand which layer to setup the database, which layer to host Parse API server, as well as how to configure each individual layer.
2. Configuring node.js
We will be hosting the backend of our application on AWS EC2. Our DB will be on node.js server. The learning curve is steep as we have no experience in node.js, especially on AWS where there is no GUI for us to work on, only linux commands.
3. MailGun Adaptor
While testing on the migration of our application, one major functionality failed when we are running our testing server on AWS. The emailing function is not working and users will not be able to receive the email to reset their password. After investigation, we realized that Parse Server does not provide emailing functionality, and we will have to set up our own emailAdaptor on our Parse server. After setting up our MailGun account, we set up the adaptor, and finally use the adaptor in our Parse server.
Quality of Product
|Risk Management||Risk Management|
|Change Management||Change Management|
|Project Overview||Project Overview||Project Overview|
|Project Scope||Project Scope|
|SmartHawker App Design||SmartHawker App Design|
|Testing||Expert Test 1||Expert Test I|
|Expert Test 2||Expert Test II|
|User Acceptance Test 1||User Acceptance Test I|
|User Acceptance Test 2||User Acceptance Test II|
|User Guide Documentation||User Guide Documentation|
- Smart Hawker is deployed and available at: https://itunes.apple.com/us/app/smarthawker/id1139427249?mt=8
|Expert Test 1||5th - 7th August 2016||Singapore Management University||30 iOS users who use applications on a daily basis.|
|Expert Test 2||9th September 2016 to 11th September 2016||Various Locations||30 iOS users who are closer to hawkers age range of above 30 years old.|
|User Acceptance Test 1||23th September 2016 to 25th September 2016||Various Locations (Tanjong Pajar Food Centre, Golden Mile Food Centre etc)||30 hawkers who operate small businesses in Singapore.|
|User Acceptance Test 2||29th October to 1st November 2016||Various Locations (Kovan Hawker Centre, Eunos Hawker Centre, Albert Centre)||30 hawkers who operate small businesses in Singapore.|
- Mr Edmund Foo, Mr Boon Teck Tan, Mr Marcus Lee