Difference between revisions of "IS480 Team wiki: 2012T2 Viaxeiros Mid Terms"
Line 487: | Line 487: | ||
|- | |- | ||
| [[Image:Zijun mid.jpg | 150px]] || | | [[Image:Zijun mid.jpg | 150px]] || | ||
+ | I have learnt to better manage my time by prioritizing my work accordingly. As the Quality Assurance Manager and Assistant Designer, I realized that it is very difficult to develop a native android app without any frameworks as there is a need to cater to different screen sizes for the phones. Sometimes it might look okay on my phone but looks different in another phone. I hope that through this project, I am able to learn things to give a better user experiences for users. | ||
|- | |- | ||
| [[Image:Yukai mid.jpg | 150px]] || | | [[Image:Yukai mid.jpg | 150px]] || | ||
+ | I set out to learn hard skills such as technical coding and soft skills such as project management skills, which I believe is still an ongoing process. | ||
+ | |||
+ | However, the learning outcomes since acceptance have been much more overwhelming than I’ve expected. Being the lead developer for offline maps has really tested my patience and perseverance due to the need to meet project requirements and deadlines. I’ve also gained more experience working in an agile development where we have to constantly gauge and prioritize the importance of certain functions, either due to client requirements or insights from user testing. | ||
|- | |- | ||
| [[Image:Melissa mid.jpg | 150px]] || | | [[Image:Melissa mid.jpg | 150px]] || | ||
+ | As a designer, it was indeed challenging as it was my first being exposed to Android Coding. Editing the XML layout code was quite different as compared to editing on a CSS template. Furthermore, I have to take consideration to different layouts and densities. Therefore , I have earnt the virtue of being patient and to continue to play around with the layout values to ensure that the outlook of the application appears correctly in different models. Communication is also key amongst the team to ensure the quality of the application is there. | ||
|- | |- | ||
| [[Image:Singlim mid.jpg | 150px]] || | | [[Image:Singlim mid.jpg | 150px]] || | ||
+ | Coding is about coding and writing efficient logics and displaying them correctly (UI). Other areas include performance and usability issues, especially when there are different android phone models and versions out there. I have also enjoyed the opportunity of learning from one another. Our group started off with no one knowing how to develop an android app. As it progresses, each of us has forged our strength in different areas. Working with An has also widened my knowledge on many other technical know how such as performance testing etc. As a lead business analyst, I have explored available travel apps and design a survey questionnaire prior the start of the project to decide on interesting features that users would want in a travel app. At the same time, touching up on design prototyping and diagrams to clarify with sponsor and supervisor | ||
|- | |- | ||
| [[Image:Siew mid.jpg | 150px]] || | | [[Image:Siew mid.jpg | 150px]] || |
Revision as of 20:49, 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