Difference between revisions of "IS480 Team wiki: 2012T2 Viaxeiros Mid Terms"
Line 344: | Line 344: | ||
* '''Perfomance''' | * '''Perfomance''' | ||
− | #Gzip - To reduce long period of dependency for a stable connnection, it is critical to ensure that the file size of the required API is kept to a minimum. Comparing the data size between a Gzip file and a text String, Gzip file is calculated to be approximately 10 times smaller. This means that much less time is needed to retrieve the required data. This is critical for us as many users might always constantly be on the move and stable connection might be hard to get. At the same time, the data we require from QIITO is known to be relatively huge (A travelogue can contain 100s of places, with many pictures | + | #Gzip - To reduce long period of dependency for a stable connnection, it is critical to ensure that the file size of the required API is kept to a minimum. Comparing the data size between a Gzip file and a text String, Gzip file is calculated to be approximately 10 times smaller. This means that much less time is needed to retrieve the required data. This is critical for us as many users might always constantly be on the move and stable connection might be hard to get. At the same time, the data we require from QIITO is known to be relatively huge (A travelogue can contain 100s of places, with many pictures associated to each of the place). |
#Lazy Loading - The idea of lazing loading is to reduce the required time needed to load and display a page. This is especially crucial when our application is required to retrieve and display a large number of images. What we have done is to make the downloading of images asynchronous and to create a queuing system (5 threads at a time) to download these images. Once an image is downloaded, it will be cached in the phone's memory and will be displayed on the page. | #Lazy Loading - The idea of lazing loading is to reduce the required time needed to load and display a page. This is especially crucial when our application is required to retrieve and display a large number of images. What we have done is to make the downloading of images asynchronous and to create a queuing system (5 threads at a time) to download these images. Once an image is downloaded, it will be cached in the phone's memory and will be displayed on the page. | ||
Revision as of 14:48, 25 February 2013
Welcome to Viaxeiros FYP Wiki Page
Mid Term Slides
|
Project Progress Summary
Progress
Currently, Viaxeiros in in their Iteration 9 on 26 February 2013, and in the midst of meeting the upcoming milestone, which is the Midterms presentation, at 26 February 2013. Currently, since the Acceptance Presentation which is at 5 November 2013, The following main features have been completed:
Based on the current status of the project, our team has decided to focus only on one of the additional functions proposed in the Acceptance Presentation, which is the Augmented Reality. |
Project Highlights
|
Project Management
Project Status
|
Project Schedule (Plan Vs Actual)
Key Changes
For more information on the schedule of our application, please click here. |
Project Metrics
Schedule Metric The following shows the summary of our schedule metric thus far: Please refer to our Schedule metric calculation here.Highlights In general, there is a delay in Iteration 3. This is due to having examinations during that period of time. Thus, despite the relatively less functions during that period of time, there is a slight delay in completing the schedule. Due to this, we have decided to increase the time period for the next iteration and also to allocate more tasks to be done then. Links:
Total Bug Count: Please refer to our bug metric calculation here.Highlights There is a spike in bug metrics during iteration 5 due to the coding sessions in iteration 4 as well as after our first user testing. In order to reduce the bug points, we have stopped coding out functions and focus instead on solving the current bugs that we have. Similarly for iteration 7, in order to solve the bugs found, more time has been allocated in iteration 8 to solve the bugs. Links
Highlights In iteration 4, 2 of our team members have many tasks on hand as compared to other team members. Using this metric as a reference as well as the actual schedule breakdown, we have decided to allocated less tasks for the members in the next iteration and more tasks for the other members. Links |
Project Risks
The following shows the top 3 list of risks that our team is currently facing. For more information of the other risks, please visit here:
|
Application Development
Intermediate Deliverables
|
Technical Complexity
|
Deployment
To download the application, you can visit this link to get the latest application in the Google Play Store. |
User Testing
|
Reflections
Learning Outcomes
Team Reflection |