Difference between revisions of "IS480 Team wiki: 2011T1 TheTalkies"

From IS480
Jump to navigation Jump to search
Line 42: Line 42:
<td align="center">3</td>
<td align="center">3</td>
<td> Khaing Pwint Wah [mailto:pwkhaing.2008@sis.smu.edu.sg]</td>
<td> Khaing Pwint Wah [mailto:pwkhaing.2008@sis.smu.edu.sg]</td>
<td> Lead Tester </td>
<td> Lead Tester/Quality Assurence </td>
*Preparing the test plan
*Preparing the test plan
Line 67: Line 67:
<td align="center">5</td>
<td align="center">5</td>
<td> Thandar Tun [mailto:thandar.tun.2009@sis.smu.edu.sg]</td>
<td> Thandar Tun [mailto:thandar.tun.2009@sis.smu.edu.sg]</td>
<td> Database Designer </td>
<td> Database Administrator </td>
*Planning and creating the database to support the application
*Planning and creating the database to support the application

Revision as of 20:32, 2 August 2011

Application Logo

The Talkies Team Members and Roles

1 Aung Myint Thein [1] Project Manager / 3D model designer
  • Planning for meeting agenda
  • Checking the team's progress
  • Communicate between the client, supervisor and the team
  • Managing the expectation of each stakeholders
  • Make sure the overall UI is simple, user friendly and intuitive
  • Building the simplified 3D model
2 Soe Thet Aung [2] System Administrator / System Architect
  • Ensure all the codes follow best practices
  • Providing support for Version Control System
  • Ensure the application is optimized in non-functionality aspect
  • Providing the overview of the connection between components
  • Main point of contact for server side troubleshooting
3 Khaing Pwint Wah [3] Lead Tester/Quality Assurence
  • Preparing the test plan
  • Making sure the bug are fixed
  • Ensure all documents are kept properly in organized manner
  • Helping the Project Manager with documentation and scheduling
4 Kyaw Moe Hein [4] Lead Designer / 3D model designer / GermaniumWeb developer
  • Responsible for User Interface
  • Create mock up for prototype of final product
  • Making sure the UI is simple, user friendly and intuitive
  • Building simplified 3D model
  • Making sure the 3D model is friendly with the user interface's design
5 Thandar Tun [5] Database Administrator
  • Planning and creating the database to support the application
  • Helping System Administrator for non-functionality requirements
6 Phyo Wint Wint Tun [6] Lead Developer
  • Leading the team at development in Twitter API
  • Support integration of front-end and back-end of application
  • Besides the above mentioned roles, each team member will be developer too. This is to make sure that each member will get chance to expose to the programming with Twitter API.


Prof Archan Misra

Project Overview

Project Description

Creating a fully customized social media dashboard on simplified 3D model of Singapore Management University categorizing tweets based on location and trending topics.


Figure 1: Trends in Singapore

Specific Location

SMU students and faculty members are sharing their thoughts and things happening around them by using various social media tools. Among them, twitter is the most popular tools. Twitter offers a social networking and microblogging service enabling its users to send and read messages called tweets. If I want to see someone's tweets with real time updates, I have to "follow" them. "Following" is one-way-adding-friend method and the other side doesn't need to accept my following. Although twitter is pretty popular among students and faculty members, "following" has a very subtle disadvantage. If another student or faculty is not following me, he will not see my tweets even if we are in the same campus. Similarly, if I didn't follow a student, I won't see his tweets even if we are in the same classroom. Do we really need to follow over thousands of students and professors to get tweets from SMU campus? No, we don't want and we should not. Is it the end of what the most popular modern social networking tool capable of?

No! We believe the social media can do better than this. Our social media dashboard will be customized to capture all the tweets in SMU campus and show them on simplified 3D model. Students can see what others think about a particular course or faculty. Faculty can see what is happening around university. All of them doesn't need to follow or explode their following people list just to see things happening around SMU.

Related Trends

Twitter has a very interesting feature called "trends". If users from Singapore tweet about a topic (for example #F1) to a certain amount of times, that keyword is promoted into "trends" and it was shown on the twitter page as Figure 1. However, students are not interested in those random topics or trends happening in whole Singapore. We are more interested in trends happening in SMU. Can we change the setting? No, we can only change the country level or worldwide. Therefore, trends such as #SIS will never appear in Singapore trends. That is not what students want from social media.

We will not only capture the tweets around SMU campus but we will also analyze them and develop trends only related to SMU. For example, when students are tweets about #Steve in matriculation, we will make #Steve as trends. Moreover, we will create a list of possible keywords and use them when we capture the tweets too. For example, #SMUSIS, #SMUSOE, etc. So, it will make trends in our page more relevant and related to SMU.

Combining the specific localized tweets and relevant trends, our website will be one stop dashboard for students and faculty members to stay connect with people around them. Potential students can also see the culture and interaction of current students. Last but not least, the expertise from community can discuss and contribute to the trends and topics in SMU as well. All of them don't need to follow anyone. All the tweets in our web site are specifically localized for SMU and the trends are highly relevant and related to SMU as well.

Project Scope

Main Features

There are 3 main features in our application.

  • It is boring to look at the text only pages. We believe creating 3D model of SMU and showing tweets on the 3D model is much more fun and more meaningful for us. With the limitation of the time and resource, we won't be able to create detailed model of SMU. Moreover, why don't we create more fun-type 3D model to reflect the friendliness of the application? This is our very first feature: Creating simplified yet fun 3D model of SMU.

  • We realized that only showing tweets doesn't complete the twitter experience. After we got the tweets based on the location and the pre-defined keywords, we are going to process them and show the trending topics around SMU. This will definitely facilitate the discussion and interaction among our application users mainly students. So, this is our second feature: Trending page.

  • In and around SMU, students lost all sort of things including but not limited to pen, mp3 player, and student card most importantly. We can report to lost and found at each school building and library. Do I need to walk to all buildings? Yes. Do they consolidate the reports? I highly doubt No. So, there are multiple reports of lost and multiple reports of found. We can see that it is not a perfect system, at least not good enough. User can tweet about the lost and found with #LostNFound hashtag. We will show it in our permanent Lost and Found Trend page. Isn't it cool? This is our third main feature: Lost and Found Trend Page.


There are 9 components that will make our 3 main features complete. The visualization of those 9 components is provided in the image below and description of each component is explained in the following table.

Visualization of features
No Component Description
1 3D model

We are going to build a simplified and block scale 3D model of Singapore Management University on which we will show the tweets and the trending topics.

2 Location Search

Using twitter API of searching tweets only around the campus, we will pull only the relevant tweets for our website. So, we will get all the tweets from students, faculty, and even community if they are tweeting in the campus and they enabled the geo-tagged feature.

3 # Search (hashtag keyword searching)

To complement location search, we will also search tweets on pre-assigned keywords. We are going to list possible keywords in SMU campus as much as possible. By doing so, our application will not need to sacrifice for non-geo-tagged tweets.

4 Trending Page

When a user selects a #keyword, we will show the page with tweets with the selected keyword.

When a user selects a faculty name, we will show the page with tweets which are located around the selected faculty and the tweets with related keywords. For example, when a user selects SIS faculty, the page will show all tweets located around SIS and with keywords IS480.

5 Lost & Found Trend Page

In every trending page, there will be #LostNFound keyword and we will keep it permanent regardless of the selected faculty and keyword. We want to make students life easier by just tweeting when they lost or found some valuables. This can be one stop lost and found portal powered by social media technology.

6 Tweet

Users with twitter credentials can log in, tweet and discuss on every above mentioned pages. When a user tweets on the keyword page, the keyword will be automatically added at the end of the tweet.

7 Discuss

Users without twitter credentials will not be left out. They can tweet and discuss in the trending page just by filling nickname field. His tweets will not be broadcasted to twitter page but users can see those tweets through our website.

8 Logging

We will keep record for the captured tweets from search, trends, nicknames for anonymous users and source IP to certain time period.

9 Statistics

Powered by the logging feature, we can display the statistics such as ranking of users, trends and most active faculty for a period of time.


1. Mobile friendly interfaces using HTML 5 and javascript As people are consuming information on mobile phones, we want to make our website mobile friendly using HTML 5 and javascript if time permits.

Our application can be accessed at http://3dsocializer.phpfogapp.com/index.php . Although we are not completed yet, we are very proud to show case our efforts and what we have done so far. Please comment at below if you have any thoughts.

Resources and references

  • Web space hosting – provided by client
  • Version control system (Git) – provided by client
  • Development tools (Notepad++, Eclipse) – free and open-sourced
  • 3D Modeling tools (Germanium 3D, 3D Max 2010) – provided by client and student licence
  • Bug tracker – free and open-sourced
  • Twitter API – online sources

Project Management

Project Milestones

Major Milestones

Our detailed planning and schedules are available Here.

Test plan will also be provided when we are ready to released. Please stay tune!!

Risk and Mitigation plan

No Risk Description Severity level Risk Mitigation plan
1 Schedule Risk
  • Wrong time estimation and failure to identify the time required to develop complex functionalities.
  • Check the task's status after every iteration. Commit more time if any task is not finished on time.
  • Manage project schedule effectively and put buffer time for unexpected circumstances.
2 Specification breakdown Risk
  • When coding and integration begin, it becomes apparent that the specification is incomplete or contains conflicting requirements.
  • Maintain a clear, concise communication with client and prepare detailed specification requirements.
3 Technical Risk
  • When integration the source codes with Germanium3D features, there might be some system compatibility issues.
  • Develop a prototype and conduct testing iteratively. Don't fall for water-fall.
4 API unfamiliarity Risk
  • Since all of our team members have never used Twitter API before, it might take some time for us to get familiar with twitter API.
  • Set aside somoe time to understand twitter API during summer break

Learning outcomes