Difference between revisions of "IS480 Team wiki: 2012T1 STEEP Final Wiki"
Line 38: | Line 38: | ||
'''1. Acceptance -''' We had issues with Amazon EC2 Cloud deployment a week before acceptance. Hence, we felt that it would be better to have abit more time.<br> | '''1. Acceptance -''' We had issues with Amazon EC2 Cloud deployment a week before acceptance. Hence, we felt that it would be better to have abit more time.<br> | ||
− | '''2. Google Play Deployment -''' We were challenged by Prof Gan to have it deployed to Google Play by Midterm and we wanted to achieve it. Furthermore, we felt that it would be better for users to test on their own mobile phone. This is something that we are really proud of<br> | + | '''2. Google Play Deployment -''' We were challenged by Prof Gan to have it deployed to Google Play by Midterm and we wanted to achieve it. Furthermore, we felt that it would be better for users to test on their own mobile phone. This is something that we are really proud of.<br> |
'''3. User Testing 3 -''' <br> | '''3. User Testing 3 -''' <br> | ||
Revision as of 19:59, 28 November 2012
Contents
Project Progress Summary
Progress Description
Project Highlights
Project Achievements
Project Management
Project Status
Project Milestones(Plan vs. Actual)
For our milestones, we had 3 key changes from our planned schedule :
1. Acceptance - We had issues with Amazon EC2 Cloud deployment a week before acceptance. Hence, we felt that it would be better to have abit more time.
2. Google Play Deployment - We were challenged by Prof Gan to have it deployed to Google Play by Midterm and we wanted to achieve it. Furthermore, we felt that it would be better for users to test on their own mobile phone. This is something that we are really proud of.
3. User Testing 3 -
Project Schedule(Plan vs. Actual)
Project Metrics
Link: Metrics |
|
Project Risks
Link : Risks |
|
Technical Complexity
Quality of Product
Deliverables
Deployment
Mobile
Our Mobile application Gr8Quest has been published on Google Play since 25 September 2012. We were required to create an account, pay for a developer account and upload the relevant APK file into the Google Play Store.
Users with android devices are able to download and use our application. As compared to our previous versions, this version allows various versions of android to use the application and compatible with different screen sizes.
Get our app now on Google Play
Website
Our Website has been deployed using Microsoft Azure.
Testing
We conduct 2 User Testing - User Testing 2 & 3.
Link: User Testing |
|
Learning Outcomes & Reflections
Learning Outcomes
Link: Learning Outcomes |
|
Team Reflection
Individual Reflection
Sunita
Minh Tri
Qianying
The overall FYP journey was an exciting and enriching one. As a group, we pushed our limits to not just attaining an acceptable level, but to go beyond that with continuously improvements by consistently reviewing issues and conducting endless discussion.
As a usability analyst, I learnt to think like a first timer who has never use the application before and pick up information or functions which are important to aid user in navigating the application. To ensure high quality of functions, I would pretend to be someone who tries to crash the system by stress testing the application. I would test every possible scenario to ensure that the system works properly and does not crash.
Eileen
FYP emphasize the need to learn as you go as I had to heavily research about the Dos and Don'ts when developing the Android application. And that it is also important to try and modify, as what might work for one developer, might not be the solution you are looking for.
Aside from that, having teammates to bounce ideas about how the function should be presented is rather important. Endless discussions has led to our User Interface changing drastically from the beginning to the end. And I rather like the results.