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/Quality Assurance </td>
<td> Lead Tester/ Quality Assurance </td>
*Preparing the test plan
*Preparing the test plan

Revision as of 16:49, 6 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 Assurance
  • 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. Users can also search the tweets based on the time. It won't be a problem if I want to search the tweets about #LostNFound for last Friday. 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 Likelihood of Occurrence Impact on Project Mitigation Strategy
1. Schedule Risk
1.1 Underestimation of a task or an iteration Medium High
  • Reschedule for the next iteration
  • The pair with unfinished task can ask for the help of other members who already finished their task
1.2 Timetable conflict High Medium
  • To put FYP the highest priority on weekends and after class hour (7:30 p.m.)
2. Specification Breakdown Risk
2.1 Incomplete Requirement Specifications or changes of requirement specifications by client Low High
  • To have some buffer time for some flexibility and unexpected changes
  • Maintain the clear, concise communication with client regarding the requirements
3. Technical Risk
3.1 Unfamiliarity with twitter and Germanium 3d APIs Medium Medium
  • Do thorough research on API and other necessary technical information by all the team members or assign one member to do the research and give one training session for the rest of the members
3.2 Integration difficulties with Germanium and twitter Medium High
  • Integrate phase by phase, test function by function and implement
4. Resource Risk
4.1 One member have to drop the course if the team do not get at least A- for acceptance presentation since he is doing FYP as IS 481 Medium High
  • Readjust the tasks and responsibilities
  • Readjust the schedule and scope
4.2 Computers crashing High High
  • Back up everything not only on Git repository but also on some cloud medium like dropbox

Learning outcomes

No Learning Outcomes Learning Potential Actions to Achieve the Outcomes
1. Integration of business & technology in a sector context
1.1 Business IT value linkage skills YY
  • Gather the requirements from client and interpret those business requirements into system requirements
  • Describe the objective and value statement of the project
  • Define the project scope according to client’s desired business scope
2. IT architecture, design and development skills
2.1 System requirements specification skills YY
  • Verify the GermaniumWeb’s needs with the sponsor and specify the requirements for project
  • Prioritize the requirements
  • Estimate the effort required for the functions and map it to the needs
2.2 Software and IT architecture analysis and design skills YY
  • Design the system architecture carefully since client requested to minimize the 3D loading time.
2.3 Implementation skills YY
  • Deploy the system phase by phase
  • Prepare detailed test cases for each phase and test the application thoroughly
  • Continuously get feedbacks from sponsor
2.4 Technology Application Skills YY
  • Make use of twitter API
  • Make use of Germanium 3D API
  • Make use of jQuery API
3. Project management skills
3.1 Scope management skills YY
  • Define the project scope carefully since in the early stage of the project and estimate the efforts and resources required to fulfill the scope
  • Make sure that all the team members are on the same page to give the necessary commitments in order to fulfill the scope
3.2 Risks management skills YY
  • Brainstorm all the risks that can be occurred throughout the project and prepare strategies to mitigate those risks
  • Monitor the risk and mitigation plan according to the iteration by PM
3.3 Project integration and time management skills YY
  • Use a very realistic approach to plan the schedule by taking consideration of different team members’ different timetable
  • Update or adjust the schedule after each iteration using the data collected from previous iteration
  • Continuously monitor the progress of each task during each iteration by PM
3.4 Configuration management skills YY
  • Decided to use Git for version control and code repository
  • Use Eclipse for IDE
  • Follow established and correct guidelines for version control and all the team members are well-practiced to use the tools since the early stage off the project
3.5 Quality management skills YY
  • Prepare UAT and test plan meticulously in order to assure the quality of application
  • Continuously gather the feedbacks from both client and supervisor
  • Plan to make a sample of users from SMU to use the application once most of the feature are done in order to evaluate the user-friendliness of the application
4. Learning to learn skills
4.1 Search skills YY
  • Research through twitter and Germanium APIs and any other information that can be useful for the project
4.2 Skills for developing a methodology for learning YY
  • Share of all the information or a new technique learned by every team member through social networking like facebook and twitter
  • Assist and explain each others on every team meeting
5. Collaboration (or team) skills
5.1 Team work skills YY
  • Make sure every one is on the same page of the team progress by constantly informing through team’s group page on Facebook
  • Decided and agreed on some protocols such as being on time for meeting and being contactable since the start of the project
  • Encourage each other to ask questions, to be open if any difficulties encounter and to ensure FYP as an enjoyable learning experience
6. Communication skills
6.1 Presentation skills YY
  • Communication with sponsor
  • Presenting project proposal (Acceptance Presentation)
  • Conducting Mid-term and final presentation
6.2 Writing skills Y
  • Using clear and concise writing for email communication between team members as well as sponsor and supervisor
  • Using simple and easy to understand/follow writing for preparing documents such as UAT and test cases
  • Document details of project on Wiki and team shared documents such as meeting minutes