IS480 Team wiki: 2012T2 Team Techbusterz Midterm Wiki
- Back to Main Wiki
- Project Progress Summary
- Project Highlights
- Project Management
- Quality of Product
- Reflection
Contents
Project Progress Summary
To download our MidTerm Slides, please download from this link: https://docs.google.com/file/d/0B0voeAJvlpn2bnNQQWlVendPak0/edit
To download our project proposal, please click Techbusterz Proposal
Acceptance to Midterm
Our team has embarked on the journey to provide a an iOS application that provides integrated information about restaurants, places of attraction, places of entertainment and shopping centers in Singapore. The application aims to be a compact and reliable guide for tourists as well as general mobile users who want to search for places of the above categories.
Project Highlights
Mitigation Plan for project management was adopted. In Construction Iteration 6, we foresee that we will be delayed due to not able to receive the crawled data from our client because they are having shortage of manpower. Therefore, we mitigated this delay by revising our project schedule. This is our action plan:
Iteration No. | Affected Metric | Metric Level (High/Med/Low) |
Cause | Action Plan |
---|---|---|---|---|
Construction Iteration 6 | Schedule Metric | Red | In Construction Iteration 6, we are supposed to integrate crawled data for our various categories such as Arty Farty, Local Culture, etc. However, our sponsor is not able to send us the crawled data on time due to some unforeseen circumstances. Therefore, the PM has to carry out the action plan according to the metric. | PM has to reschedule plan and swap Iteration 7 and 6. Instead of working on the integrating of crawled data, our developers will work on the Facebook & Google integration |
Initial Plan:
Revised Plan:
Project Management
Project Status:
Our team have completed all the categories implemenatation, facebook and google map integration. Conducted 1 UT.
Task/function/features, etc | Status | Confident Level (0-1) | Comment |
Login / Logout Function | Fully deployed and tested 100% | 1 | Sponsor Approved |
Share Function | Fully deployed and tested 100% | 1 | Sponsor Approved |
Get Direction Function | Fully deployed and tested 100% | 1 | Sponsor Approved |
Camera Function | Fully deployed and tested 100% | 1 | Sponsor Approved |
Project Schedule (Plan Vs Actual):
Compare the project plan during acceptance with the actual work done at this point. Briefly describe a summary here. Everything went as plan, everything has changed and the team is working on a new project with new sponsors or the supervisor is missing. A good source for this section comes from the project weekly report.
Project Metrics:
Schedule Metric: Our team track the schedule metric based on the schedule which we have planned from the start to the end. Click here to view detailed project schedule.
Bugs Metric: Our team track the bugs metrics based on the score tested by our system analyst at the end of every iteration.
Efficiency Metric: Our team measure the efficiency of team based on the schedule as well as programming logs. Click here to download the programming logs
Project Risks:
Risk | Probability | Impact | Mitigation |
Miscommunication with sponsor | High (Now is Low) | High | Business Requirement Document to make sure that everything that is agreed upon is stated clearly |
Unfamiliar with new technologies | High (Now is Low) | High | Peer learning, increased time allocation for learning |
Under estimation of Manhours | High (Now is Moderate) | High (Now is Moderate) | Buffer in schedule, constant revision to schedule |
Technical Complexity:
The complexity of our project is:
1. Normalization where we transform the crawled data into a common format for insertion into the database.
2. ETL(Extract-Transform-Load)
3. Search APIs to write our own breadcrumps search APIs for the iPad application
4. Front end to enhance users' experience
Quality of Product
Intermediate Deliverables:
There should be some evidence of work in progress.
Stage | Specification | Modules |
Project Management | Minutes | Internal modules 1-17, Sponsor modules 1-10, Supervisor 1- 9 |
Metrics | Schedule, Bug & Efficiency Metrics | |
Requirements | Users Specifications & Research | Requirement Specifications , Domain and Website (Initial Research) , Finalize Website for crawling |
Analysis | Use Case | Overall |
System Sequence Diagram | Overall | |
Deployment Diagram | Overall | |
Design | Initial Storyboard | Prototype Initial |
Final Storyboard | Final Prototype | |
Testing | UT 1 Execution Plan | User test plan |
Not all parts of the deliverables are necessary but the evidence should be convincing of the progress. Try to include design deliverables that shows the quality of your project.
Deployment:
To view our deployment diagram, please click [Deployment Diagram].
Testing:
Objective
The objective of this user acceptance test (UAT) is to find out whether user finds our application user friendly and the usability of the application. Through this UAT, we hope that the intrusiveness and cosmetic of the application will be up to the mark.
Features
1) Login with their Facebook account.
2) Select the category that they are interested in:
a. Nearby
b. Foodie
c. Arty Farty
d. Adventure
e. Family
f. Local culture
3) Type a keyword that they want to search for to return a list of result
4) Click on the result to return details of the place of interest.
5) Sharing the place of interest with Google+ account.
6) Sharing the place of interest with Facebook account
7) See the reviews
8) Locate the place of interest on the map
9) Able to get direction to the place
10) Able to add and remove the place of interest onto the favorite tab.
Tester Profile
20 Student participants
Test Cases
Please click Techbusterz TestCases
Survey Results
Please click Techbusterz Survey Results
Reflection
Name | Reflection Points |
---|---|
Tan Wei Hao |
I have learnt is that it is very important to have a backup plan, as servers may fail at important times. I also learnt that communication with teammates are critical, otherwise we may end up coding parts that do not link well with each other. |
Brian Li |
Through this FYP, I have realised that data normalisation of different web sources is no easy feat. Though, it was no easy feat, it was indeed a challenge for us to normalise the different data set given to us correctly. |
Tan Jian Wei |
As a PM, I learnt to adopt an “initiative-oriented” behavior and to be more thick skinned. These act as my tool to effectively engage everyone during meetings and tactically prevent others from digressing. |
Jessie Choo |
My takeaways for the past seven weeks was that anything can happen. And when something does happen, we should take a step back and remember our priorities. Also, to remain calm and keep communication open with the team at ALL times. |
Goh Kuang Quan |
Communication with other team mates are very important to get information across and getting work done on time. We need to be flexible and react fast to overcome obstacles which come in our way and especially problems that occurs unexpectedly. |
Edward Tan |
It is always fun to learn a new programming language. It seems daunting at first to learn Objective-C but with right attitude and perseverance, nothing is impossible. FYP also taught me how to better communicate my needs with my fellow team mates. Every single thing in this team is so tightly integrated that if any one of us got delayed, our entire plan will go down the pit. I learnt to better manage my time as a result of that. |
Team Reflection
Learning Point | Description |
---|---|
Project Management Skills |
One of the main purposes of IS480 is to provide students the opportunity to manage and oversee the entire phase of an IT project, from conceptualization all the way to development and finally implementation. Through this journey, our team hope to further refine the project management concepts and skills we picked up in our Software Engineering module. We want to learn how to better manage the scope of a project, manage its timeline and milestones, how to set KPIs and metrics to monitor progress and success and last but not least, how to manage risks and changes. |
Communication Skills |
Good communication is key to ensuring a successful project. However, communication is always going to be difficult especially when working in a team setting. Our team hopes to use this opportunity to learn how to effectively communication amongst each other and with our sponsors. The latter is especially important since we will be required to constantly cooperate and work together with our sponsors. |
Business and IT Integration |
A successful product hinges not just on how well the product is made but rather how much value it can provide to the clients. It is therefore very important to identify and define the business values and propositions the product can bring about. This business and IT integration is not easy as it will require the client and the project team to come together to agree upon a set of values and requirements to meet. Through IS480, our team hope to apply what we learnt in our previous modules and learn how to integrate business and IT together to bring about a successful working product. |