Difference between revisions of "IS480 Team wiki: 2012T1 Team Glocal"
(15 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | < | + | <font face = "Gill Sans MT" size="5"> |
− | + | Introduction | |
+ | <font face = "Gill Sans MT" size="3"> | ||
− | + | [[Image:Team_Glocal_Home_Pg.jpg|450px|right]] | |
− | |||
− | |||
− | + | The growing pace of economic globalization has created more migrant workers than ever before. Unemployment and increasing poverty have prompted many workers in developing countries to seek work elsewhere, while developed countries have increased their demand for labour, especially unskilled labour. As a result, millions of workers and their families travel to countries other than their own to find work. At present there are approximately 175 million migrants around the world, roughly half of them workers (of these, around 15% are estimated to have an irregular status). | |
− | |||
− | |||
− | + | Women make up almost half of migrants. Migrant workers contribute to the economies of their host countries, and the remittances they send home help to boost the economies of their countries of origin. Yet at the same time migrant workers often enjoy little social protection and are vulnerable to exploitation and human trafficking. Skilled migrant workers are less vulnerable to exploitation, but their departure has deprived some developing countries of valuable labour needed for their own economies. | |
− | |||
− | |||
− | + | There were 201,000 female domestic workers in Singapore on Work Permits (end of 2010), as reported by the Ministry of Manpower. That made it about one for every five households in the country. In 2002, there were 140,000. The majority, by far, are from Indonesia and the Philippines; smaller numbers come from Sri Lanka, Myanmar, India, Thailand, and Bangladesh. | |
− | |||
− | |||
− | + | == <span class="mw-headline"><div style="background: #669933; padding: 14px; font-weight: bold"><center><font align="center" color="#FFFFFF" size="5" face="Castellar"><b>Team GLOCAL</b></font></center></div></span> == | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | === <span class="mw-headline"><div style="background: #99CC33; padding: 12px; font-weight: bold"><font color="black" size="3" face="verdana"><b>Roles and Responsibilities</b></font></div></span> === | |
− | |||
− | |||
+ | <table border="1"> | ||
+ | <tr bgcolor="#FF9900" align="center" style="color:#FFFFFF; font-weight:bold"> | ||
+ | <td width="140px"> MEMBER </td> | ||
+ | <td width="300px"> PRIMARY ROLE </td> | ||
+ | <td width="300px"> SECONDARY ROLE </td> | ||
+ | <td width="500px"> RESPONSIBILITIES</td> | ||
+ | </tr> | ||
+ | |||
+ | <tr> | ||
+ | <td align="center">[[Image:Team_Glocal_Member_UmaPic.jpg|140px]] Uma Devi D/O Krishna Moorthy [mailto:umadevi.km.2009@sis.smu.edu.sg] </td> | ||
+ | <td align="center"> Project Manager</td> | ||
+ | <td align="center">Usability Analyst</td> | ||
+ | <td> | ||
+ | <ul><li> Manage multiple tasks and assign tasks to team members. | ||
+ | </li><li> Monitor team progress and resolve conflicts. | ||
+ | </li><li> Manage communication between different key stakeholders. | ||
+ | </li><li> Plan and update project progress and mitigate any potential risks. | ||
+ | </li></ul> | ||
+ | </td> | ||
+ | </tr> | ||
+ | |||
+ | <tr bgcolor="#FFFFFF"> | ||
+ | <td align="center"> [[Image:Team_Glocal_Member_JohnPic.jpg|140px]]Aung Myat Ko, John[mailto:aungmyatko.2010@sis.smu.edu.sg]</td> | ||
+ | <td align="center"> Lead Developer </td> | ||
+ | <td align="center"> Tester </td> | ||
+ | <td> | ||
+ | <ul><li> Lead the team in developing specified functionalities. | ||
+ | </li><li> Research on new technologies and evaluate development tools. | ||
+ | </li><li> Develop system architecture and coding routine. | ||
+ | </li><li> Manage database and optimize database's capacity. | ||
+ | </li></ul> | ||
+ | </td> | ||
+ | </tr> | ||
+ | |||
+ | <tr> | ||
+ | <td align="center"> [[Image:Team_Glocal_Member_DannyPic.jpg|140px]]NGUYEN Minh Dang [mailto:mdnguyen.2009@sis.smu.edu.sg] </td> | ||
+ | <td align="center"> Lead Tester</td> | ||
+ | <td align="center"> Developer</td> | ||
+ | <td> | ||
+ | <ul><li> Find and evaluate various testing tools. | ||
+ | </li><li> Create test plans. | ||
+ | </li><li> Oversees User Testing 1 & User Testing 2. | ||
+ | </li><li> Assist in debugging. | ||
+ | </li></ul> | ||
+ | </td> | ||
+ | </tr> | ||
+ | |||
+ | <tr bgcolor="#FFFFFF"> | ||
+ | <td align="center"> [[Image:Team_Glocal_Member_ThaiPic.jpg|140px]] PHAM Duong Thai [mailto:dtpham.2009@sis.smu.edu.sg] </td> | ||
+ | <td align="center"> Usability Analyst</td> | ||
+ | <td align="center"> Business Analyst</td> | ||
+ | <td> | ||
+ | <ul><li> Define user experience on the prototype. | ||
+ | </li><li> Oversees test cases and give assurance on the system's stability and robustness. | ||
+ | </li><li> Optimize the application's usability. | ||
+ | </li><li> Assist in system integrations and modularizations. | ||
+ | </li></ul> | ||
+ | </td> | ||
+ | </tr> | ||
+ | |||
+ | <tr bgcolor="#FFFFFF"> | ||
+ | <td align="center"> [[Image:Team_Glocal_Member_NikPic.jpg|140px]] NG Qi You [mailto:qiyou.ng.2009@sis.smu.edu.sg] </td> | ||
+ | <td align="center"> Business Analyst</td> | ||
+ | <td align="center"> Developer</td> | ||
+ | <td> | ||
+ | <ul><li> Gather client needs and convert them into functionalities. | ||
+ | </li><li> Design business models and define scope | ||
+ | </li><li> Monitor the alignment between our system and business requirements from client. | ||
+ | </li><li> Assist PM in documentation. | ||
+ | </li></ul> | ||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
+ | |||
+ | == <span class="mw-headline"><div style="background: #669933; padding: 12px; font-weight: bold"><font color="#FFFFFF" size="5" face="hobo std"><b>Project Status<div style="float: right;"> [[#top|[top]]]</div></b></font></div></span>== | ||
+ | |||
+ | <ul><li><font size="3" color="black"> Our current updates are available [[IS480 Team wiki: 2012T1 Team Glocal Current Updates | here]]</font></li></ul> | ||
+ | <ul><li><font size="3" color="black"> Our midterm wiki is available [[IS480 Team wiki: 2012T1 Team Glocal Midterm | here]]</font></li></ul> | ||
+ | <ul><li><font size="3" color="black"> Our final wiki is available [[IS480 Team wiki: 2012T1 Team Glocal Final| here]]</font></li></ul> | ||
+ | |||
+ | == <span class="mw-headline"><div style="background: #669933; padding: 12px; font-weight: bold"><font color="#FFFFFF" size="5" face="hobo std"><b>Project Overview<div style="float: right;"> [[#top|[top]]]</div></b></font></div></span> == | ||
+ | |||
+ | === <span class="mw-headline"><div style="background: #99CC33; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>Motivation</b></font></div></span> === | ||
+ | |||
+ | To help migrant workers to assimilate into Singapore faster by providing avenues for them to get help and information quickly.Also, to shorten the response time for migrant workers to get help by creating a direct connection between the subscriber and officer on duty.We also want to provide insights into needs and sentiments of migrant workers in Singapore through analysis of data collected from subscribers’ day-to-day activities on our platform. Hence,these data can come from frequently-used words in messages, most frequently-viewed FAQs and common complaints submitted by subscribers (migrant workers). | ||
+ | |||
+ | === <span class="mw-headline"><div style="background: #99CC33; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>Description</b></font></div></span> === | ||
+ | |||
+ | We are building myHome, a social networking site which is accessible via a web-based application and a mobile optimised version targeting migrant workers in Singapore. On the backend, our site will capture user habits from day-to-day activities which subscribers perform on our web-based application and/or mobile application and later generate report (in charts and graphs) based on collective behaviour and activities performed on our site. | ||
+ | |||
+ | Activities are defined as user actions performed in our website (either via the web application or mobile application). Log ins and log outs, date and time of feedback submissions and frequently viewed FAQ are some examples. | ||
+ | |||
+ | Collective behaviour is defined as an action which is performed by a group of user (i.e. 10 or more) at the same time or in close timing. An example is between 5:30am to 6:30am, many users log into our website via their mobile phones, many also message their friends (i.e. other members of our site) during this time period. Therefore, we can determine that this is the “hot” period to disseminate events notification or new survey for our users to respond. | ||
+ | |||
+ | |||
+ | === <span class="mw-headline"><div style="background: #99CC33; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>Stakeholders</b></font></div></span> === | ||
+ | |||
+ | [[Image:Team_Glocal_Stakeholder.jpg|700px|center]] | ||
+ | |||
+ | === Client Background === | ||
+ | The Humanitarian Organisation for Migration Economics (HOME) is committed to the principle that migration of people benefits the global society with a focus on the effects of migration within the context of Singapore. | ||
+ | |||
+ | The mission objectives of HOME are: | ||
+ | #To develop research and education on the socioeconomic of migration on Singapore and the countries of origin; | ||
+ | #To provide social integration services for emigrants and immigrants; | ||
+ | #To provide humanitarian assistance for the effects of 'crisis' migration. | ||
+ | |||
+ | There are some 800,000 migrant workers or more in Singapore and HOME has provided direct assistance to more than 50,000 men and women migrants and victims of human trafficking and forced labour, who availed of our programme and services. Among those helped included migrants affected by the Tsunami disaster in 2005 and the present global economic crisis in 2008/2009. On one occasion, HOME provided shelter for 15 Indonesian women and their children, who were abandoned at sea by seamen. | ||
+ | |||
+ | [[Image:ClientInfo.jpg|700px|center]] | ||
+ | |||
+ | |||
+ | === <span class="mw-headline"><div style="background: #99CC33; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>Scope</b></font></div></span> === | ||
+ | |||
+ | [[Image:Team_Glocal_Scope.jpg|700px|centre]] | ||
+ | |||
+ | ==== <span class="mw-headline"><div style="background: #FF9900; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>Module 1: Account Management</b></font></div></span> ==== | ||
+ | |||
+ | |||
+ | Basic security feature to authenticate user and restrict the functions they can perform based on their assigned role. Currently, there are two roles – user and administrator. Also, users can link their Facebook account to myHome. | ||
+ | |||
+ | User: | ||
+ | #Register account | ||
+ | #Edit profile and account settings | ||
+ | #Restrict site information to logged-in users only | ||
+ | #Connect with Facebook | ||
+ | #Implement CAPTCHA | ||
+ | #Cancel account | ||
+ | |||
+ | Admin: | ||
+ | #Delete user(s) | ||
+ | #Manage site administration | ||
+ | #Validate user(s) | ||
+ | |||
+ | ==== <span class="mw-headline"><div style="background: #FF9900; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>Module 2: Social Interaction</b></font></div></span> ==== | ||
+ | |||
+ | Basic social network functionalities to facilitate online interaction. | ||
+ | #Create group | ||
+ | #Add friends to group | ||
+ | #Report inappropriate content | ||
+ | #Send message | ||
+ | #Accept/Reject friend invite | ||
+ | #Instant chat (with friends) | ||
+ | #Comment/Like/Post a picture | ||
+ | #Tickle (replaced with Gift) | ||
+ | |||
+ | ==== <span class="mw-headline"><div style="background: #FF9900; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>Module 3: Event Management</b></font></div></span> ==== | ||
+ | |||
+ | Subscribers can indicate attendance (Yes, No) for upcoming events. Administrators will be able to keep track of sign-up rate and make more accurate logistics arrangements (venue, food, tables & chairs, etc.) | ||
+ | |||
+ | User: | ||
+ | #Invite friends (replaced with event listing) | ||
+ | #Set event preferences | ||
+ | |||
+ | Admin | ||
+ | #Create/Edit/Delete event | ||
+ | #Set event privacy | ||
+ | #Invite attendee(s) (replaced with event listing) | ||
+ | #Noticeboard (Widget) | ||
+ | #Set targeted group | ||
+ | |||
+ | ==== <span class="mw-headline"><div style="background: #FF9900; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>Module 4: Feedback Management</b></font></div></span> ==== | ||
+ | |||
+ | Subscribers can submit a complaint or enquiry (grouped into feedback) while administrators will receive alert for inquiries (consolidated into topics) instantly or after fixed interval [for phone and email notification], and can respond to the feedback as soon as possible. | ||
+ | |||
+ | #Post an incident/inquiry (with email notification to admin) | ||
+ | #Reply to incident/inquiry by admin | ||
+ | |||
+ | ==== <span class="mw-headline"><div style="background: #FF9900; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>Module 5: Q & A Management</b></font></div></span> ==== | ||
+ | |||
+ | Users can search for answers to their questions either by entering their questions into the search box or browse through the category list of previously posted questions and their respective answers. Each question posted will go through the text parsing to be categorized under three main topics: legal, employment, health. | ||
+ | |||
+ | #Search Question(s) | ||
+ | #List most freqently asked questions (by category, search count) | ||
+ | #Post Question(s) & Answer(s) | ||
+ | |||
+ | ==== <span class="mw-headline"><div style="background: #FF9900; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>Module 6: Survey Management</b></font></div></span> ==== | ||
+ | |||
+ | Subscribers can respond to surveys and view their list of previously completed surveys. Administrator can create new surveys, delete outdated or error surveys, close surveys which have passed their closing dates. | ||
+ | |||
+ | #Draft/Post/Delete Surveys | ||
+ | #Updated: Show surveys on user profile | ||
+ | #Respond to survey | ||
+ | #Disseminate survey (via email) | ||
+ | |||
+ | ==== <span class="mw-headline"><div style="background: #FF9900; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>Module 7: Analytics & Reporting</b></font></div></span> ==== | ||
+ | |||
+ | For administrators only, they will be able to: | ||
+ | See site user statistics (user access log, user demographics, etc) using embedded Google Analytic code and Generate reports about most frequently appeared words in categories - employment, legal, and health. Each category will have a set of predefined key words to help do text parsing for posted questions. Reports will come under the form of pie charts for words under each category and bar charts to give general comparison among the top three categories. | ||
+ | |||
+ | #Data Analytics | ||
+ | ##'''Simple chart''', post by user - most influential user [Top 10 users],[Dropdown list of timing] | ||
+ | ##'''Medium chart''', category breakdown based on number of questions [legal/healthcare/employment], joining 3 or 4 tables together and gathering sentiments. *collate the topics to categories | ||
+ | ##'''Complex chart''', tag cloud based on number of questions posted in Q&A, similar to word cloud. | ||
+ | |||
+ | ==== <span class="mw-headline"><div style="background: #FF9900; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>Module 8: X Factor</b></font></div></span> ==== | ||
+ | |||
+ | '''Voice-enabled myHOME Social Network for Android''' | ||
+ | |||
+ | This function will enhance the site-wide navigation of myHOME social network on mobile where the screen size is substantially small by adding the ability to say voice commands to go to different pages. <br> | ||
+ | |||
+ | Our android app will recognize the voice commands, make necessary processing of the commands and then redirect the user to a different page. (e.g. registration page, profile page, activity page, event page etc.). First, we will start with English commands only but will add support for other languages if time and technology permit. <br> | ||
+ | |||
+ | |||
+ | == <span class="mw-headline"><div style="background: #669933; padding: 12px; font-weight: bold"><font color="#FFFFFF" size="5" face="hobo std"><b>Project Management<div style="float: right;"> [[#top|[top]]]</div></b></font></div></span> == | ||
+ | |||
+ | === <span class="mw-headline"><div style="background: #99CC33; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>Schedule</b></font></div></span> === | ||
+ | |||
+ | Project Schedule (Planned): [https://docs.google.com/spreadsheet/ccc?key=0Aj0FmZKCZ5yMdDFYdWxCR0NBWlFFWkctdHNmTGdEbEE#gid=1 Link] | ||
+ | |||
+ | Project Schedule (Actual): [https://docs.google.com/spreadsheet/ccc?key=0Aj0FmZKCZ5yMdExQa2NwNEphT1RyVmwySzhvZXF6Y2c#gid=0 Link] | ||
+ | |||
+ | Project Schedule (Adjusted): [https://docs.google.com/spreadsheet/ccc?key=0Aj0FmZKCZ5yMdGNGcDlnWmJHS2FrUUM5Qk9JaTU5NFE#gid=1 Link] | ||
+ | |||
+ | Schedule Metric: [https://docs.google.com/spreadsheet/ccc?key=0Aj0FmZKCZ5yMdGNGcDlnWmJHS2FrUUM5Qk9JaTU5NFE#gid=5 Link] | ||
+ | |||
+ | |||
+ | === <span class="mw-headline"><div style="background: #99CC33; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>Timeline</b></font></div></span> === | ||
+ | |||
+ | Project Timeline: [https://docs.google.com/spreadsheet/ccc?key=0Aj0FmZKCZ5yMdGNGcDlnWmJHS2FrUUM5Qk9JaTU5NFE#gid=3 Link] | ||
+ | |||
+ | === <span class="mw-headline"><div style="background: #99CC33; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>Bug Log & Metric</b></font></div></span> === | ||
+ | |||
+ | Bug Log & Metric: [https://docs.google.com/spreadsheet/ccc?key=0Aj0FmZKCZ5yMdEhuc2NzWEI5TGVQZ1RHb2ZwS0dMQWc#gid=0 Link] | ||
+ | [[Image:Team_Glocal_Formula-Bug-Metric.jpg|700px|center]] | ||
+ | |||
+ | === <span class="mw-headline"><div style="background: #99CC33; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>Risk Management & Metric</b></font></div></span> === | ||
+ | |||
+ | [[Image:Team_Glocal_RiskMatrix.jpg|700px|center]] | ||
+ | |||
+ | |||
+ | {| class="wikitable centered" width"90%" | ||
+ | !No | ||
+ | !Type of risk | ||
+ | !Description | ||
+ | !Probability | ||
+ | !Impact | ||
+ | !Assessment | ||
+ | !Mitigation Strategy | ||
+ | |||
+ | |- | ||
+ | |width="10pt" align="center"|<!--No-->1 | ||
+ | |width="90pt" align="center"|<!--Type of risk-->Technical | ||
+ | |width="400pt"|<!--Description-->[Despite research and sourcing done prior to procuring our current server.] Sudden unforeseen problems (crashes + slowness) with production server during our UT#1, disrupting our team's ability to consolidate valuable inputs from our invited testers. This caused us not to be able to collect concrete results and findings from the UT, causing us to haul the UT process. | ||
+ | |width="50pt" align="center"|<!--Probability-->High | ||
+ | |width="50pt" align="center"|<!--Impact-->High | ||
+ | |width="60pt" align="center"|<!--Assessment-->A* | ||
+ | |width="400pt"|<!--Mitigation Strategy-->Inform sponsor of the problem while contacting hosting company to find out the root cause of problems encountered. Next, source for another hosting plan - preferably "tried & tested". If user testing and/or mid-term presentation are affected, make the necessary arrangement to postpone them. | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |width="10pt" align="center"|<!--No-->2 | ||
+ | |width="90pt" align="center"|<!--Type of risk-->Business | ||
+ | |width="400pt"|<!--Description--> Broken commitment from Client, promised to provide migrant workers to test our application during UT#1, however Client had sudden change of plan as an event was organised by the NGO on the same day as our UT#1. | ||
+ | |width="50pt" align="center"|<!--Probability-->Medium-High | ||
+ | |width="50pt" align="center"|<!--Impact-->High | ||
+ | |width="60pt" align="center"|<!--Assessment-->A* | ||
+ | |width="400pt"|<!--Mitigation Strategy--> To continue with the scheduled UT date by getting 40 pseudo testers [SMU students] to assist us with our UT#1, as their capabilities and skills acquired through Facebook would very much similar to the migrant workers. | ||
+ | Team also continued to confirm with Client to conduct the UT with the actual testers on 7th October 2012. | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |width="10pt" align="center"|<!--No-->3 | ||
+ | |width="90pt" align="center"|<!--Type of risk-->Technical | ||
+ | |width="400pt"|<!--Description-->Members are unfamiliar with the new technologies and their accompanying framework, for instance ELGG framework, Kettle Analytics Tool, PHP. Hence causing delays in development and testing. | ||
+ | |width="50pt" align="center"|<!--Probability-->Medium | ||
+ | |width="50pt" align="center"|<!--Impact-->Medium | ||
+ | |width="60pt" align="center"|<!--Assessment-->B | ||
+ | |width="400pt"|<!--Mitigation Strategy-->Assign each member to cover a technical aspect of the technologies and ensure they are comfortable with it. Do a bi-weekly sharing of what was read and practised - to ease the learning curve and encourage peer learning. | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |width="10pt" align="center"|<!--No-->4 | ||
+ | |width="90pt" align="center"|<!--Type of risk-->Technical | ||
+ | |width="400pt"|<!--Description-->Since there are tons of open source codes to assist us in our project, we have to select and test many packages and use the appropriate ones in our project. This process can be both time-consuming and demoralising causing the team time and energy. | ||
+ | |width="50pt" align="center"|<!--Probability-->Low-Medium | ||
+ | |width="50pt" align="center"|<!--Impact-->Medium | ||
+ | |width="60pt" align="center"|<!--Assessment-->C <br />[Monitor] | ||
+ | |width="400pt"|<!--Mitigation Strategy-->Encourage each member to prepare simple documentation of the technologies covered along the way and share these documents internally (via Google Docs). | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |width="10pt" align="center"|<!--No-->5 | ||
+ | |width="90pt" align="center"|<!--Type of risk-->Technical | ||
+ | |width="400pt"|<!--Description-->As the project is dealing with an existing (huge) framework, weakness in the framework may cause unexpected bugs to surface. | ||
+ | |width="50pt" align="center"|<!--Probability-->Low | ||
+ | |width="50pt" align="center"|<!--Impact-->Low | ||
+ | |width="60pt" align="center"|<!--Assessment-->C <br />[Monitor] | ||
+ | |width="400pt"|<!--Mitigation Strategy-->Utilize the testing phase of each iteration to look out for potential bugs that may exist. When possible, try to get 1 or 2 people from the public/friends/focus group members to test out the functions of the concerned scope. | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |width="10pt" align="center"|<!--No-->6 | ||
+ | |width="90pt" align="center"|<!--Type of risk-->Technical | ||
+ | |width="400pt"|<!--Description--> Earlier this week, our site was down for two days because our own nameservers used for the cpanel account were down after the server was unexpectedly restarted but the ip aliases were not. Limited knowledge in server handling knowledge had put us at a risk. | ||
+ | |width="50pt" align="center"|<!--Probability-->Low | ||
+ | |width="50pt" align="center"|<!--Impact-->High | ||
+ | |width="60pt" align="center"|<!--Assessment-->B | ||
+ | |width="400pt"|<!--Mitigation Strategy--> We talked to GoDaddy Live support and used their off-site DNS servers for our domain vivamyhome.com instead. After a few hours, the new DNS records were properly propagated and the site was up and running again. | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |width="10pt" align="center"|<!--No-->7 | ||
+ | |width="90pt" align="center"|<!--Type of risk-->Technical | ||
+ | |width="400pt"|<!--Description--> The risk we had for SOLR which is a type of search function was only explored after midterm once the sponsor's main requirements were re-highlighted with additional tasks. Therefore, the team has no prior experience or knowledge in this field, as well as it was not included in the early development phases. | ||
+ | |width="50pt" align="center"|<!--Probability-->Low | ||
+ | |width="50pt" align="center"|<!--Impact-->Medium | ||
+ | |width="60pt" align="center"|<!--Assessment-->C | ||
+ | |width="400pt"|<!--Mitigation Strategy--> Team got advice from sponsor, supervisor and Professor Feida, and based on the advises and suggestions the team progressively managed to build the function and complete the iteration. | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |width="10pt" align="center"|<!--No-->8 | ||
+ | |width="90pt" align="center"|<!--Type of risk-->Business | ||
+ | |width="400pt"|<!--Description-->Impromptu changes to user requirements from client (beneficiary) | ||
+ | |width="50pt" align="center"|<!--Probability-->Medium | ||
+ | |width="50pt" align="center"|<!--Impact-->High | ||
+ | |width="60pt" align="center"|<!--Assessment-->A | ||
+ | |width="400pt"|<!--Mitigation Strategy-->Regular communication with client, schedule bi-weekly meetings with client and conduct focus group discussion with end users every three weeks. Also, team (led by our Project Manager) will try to get our client to commit to discussed scopes and functionalities (verbal agreement of project deliveries). | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |width="10pt" align="center"|<!--No-->9 | ||
+ | |width="90pt" align="center"|<!--Type of risk-->Business | ||
+ | |width="400pt"|<!--Description-->Last-minute cancellation of meeting with client due to travel commitments, urgent meetings/discussions/incidents to attend to. | ||
+ | |width="50pt" align="center"|<!--Probability-->Medium (prev. Low) | ||
+ | |width="50pt" align="center"|<!--Impact-->Medium | ||
+ | |width="60pt" align="center"|<!--Assessment-->B | ||
+ | |width="400pt"|<!--Mitigation Strategy-->Open several channels of communication with the client (Facebook, Emails, (Project Manager) mobile number). Also, make sure there's always a point of contact (nominated representative to stand-in) if she is not available. | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |width="10pt" align="center"|<!--No-->10 | ||
+ | |width="90pt" align="center"|<!--Type of risk-->Resources | ||
+ | |width="400pt"|<!--Description-->Underestimating resource required, poor resource allocation; Members having internship and travel commitments. | ||
+ | |width="50pt" align="center"|<!--Probability-->High | ||
+ | |width="50pt" align="center"|<!--Impact-->High | ||
+ | |width="60pt" align="center"|<!--Assessment-->A* <br />[Risk Eliminated] | ||
+ | |width="400pt"|<!--Mitigation Strategy-->Forward planning and periodic review of schedule, start early – have regular meetings 2 to 3 times weekly and also create a Facebook group to share ideas, news, and web links to interesting technologies to look at and iron out small issues ahead of meetings | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |width="10pt" align="center"|<!--No-->11 | ||
+ | |width="90pt" align="center"|<!--Type of risk-->Resources | ||
+ | |width="400pt"|<!--Description-->Multiple users working on multiple files, hence information and file sharing can become hectic and team may face overlaps at times which may cause unneccessary delays. | ||
+ | |width="50pt" align="center"|<!--Probability-->Medium | ||
+ | |width="50pt" align="center"|<!--Impact-->Medium | ||
+ | |width="60pt" align="center"|<!--Assessment-->B <br />[Risk Reduced] | ||
+ | |width="400pt"|<!--Mitigation Strategy-->To eliminate these problems from arising, team has to come up with a shared folder, eg) SVN for committing of codes to compile it frequently. The group also has to practice proper committing procedure. | ||
+ | |- | ||
+ | |||
+ | |||
+ | |||
+ | |} | ||
+ | |||
+ | <br> | ||
+ | |||
+ | === <span class="mw-headline"><div style="background: #99CC33; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>Meeting Minutes</b></font></div></span> === | ||
+ | |||
+ | * [[Media:Meeting-01_070512.pdf|Meeting Minutes 1]] | ||
+ | * [[Media:Meeting-02_240512.pdf|Meeting Minutes 2]] | ||
+ | * [[Media:Meeting-03_030612.pdf|Meeting Minutes 3]] | ||
+ | * [[Media:Meeting-04_100612.pdf|Meeting Minutes 4]] | ||
+ | * [[Media:Meeting-05_300612.pdf|Meeting Minutes 5]] | ||
+ | * [[Media:Meeting-06_210712.pdf|Meeting Minutes 6]] | ||
+ | * [[Media:Meeting-07_210712.pdf|Meeting Minutes 7]] | ||
+ | * [[Media:MeetingMinutes-Supervisor-120912.pdf|Meeting Minutes 8]] | ||
+ | * [[Media:MeetingMinutes-Client-160912.pdf|Meeting Minutes 9]] | ||
+ | * [[Media:MeetingMinutes-Sponsor-170912.pdf|Meeting Minutes 10]] | ||
+ | * [[Media:MeetingMinutes-Sponsor-260912.pdf|Meeting Minutes 11]] | ||
+ | * [[Media:MeetingMinutes-Supervisor-270912.pdf|Meeting Minutes 12]] | ||
+ | * [[Media:MeetingMinutes-Supervisor-041012.pdf|Meeting Minutes 13]] | ||
+ | * [[Media:MeetingMinutes-Supervisor-181012.pdf|Meeting Minutes 14]] | ||
+ | * [[Media:MeetingMinutes-Supervisor-211012.pdf|Meeting Minutes 15]] | ||
+ | * [[Media:MeetingMinutes-Supervisor-241012.pdf|Meeting Minutes 16]] | ||
+ | * [[Media:MeetingMinutes-Supervisor-211112.pdf|Meeting Minutes 17]] | ||
+ | |||
+ | == <span class="mw-headline"><div style="background: #669933; padding: 12px; font-weight: bold"><font color="#FFFFFF" size="5" face="hobo std"><b>Project Documentation<div style="float: right;"> [[#top|[top]]]</div></b></font></div></span>== | ||
+ | |||
+ | === <span class="mw-headline"><div style="background: #99CC33; padding: 12px; font-weight: bold"><font color="#FFFFFF" size="5" face="hobo std"><b>Use Case Diagrams</b></font></div></span>=== | ||
+ | |||
+ | <gallery> | ||
+ | Image:Team_Glocal_Subscriber.jpg|Subscriber | ||
+ | Image:Team_Glocal_Administrator.jpg|Administrator | ||
+ | </gallery> | ||
+ | |||
+ | === <span class="mw-headline"><div style="background: #99CC33; padding: 12px; font-weight: bold"><font color="#FFFFFF" size="5" face="hobo std"><b>Functional Flow Diagrams</b></font></div></span>=== | ||
+ | |||
+ | <gallery> | ||
+ | Image:Team_Glocal_Account-Creation.jpg|Create Account | ||
+ | Image:Team_Glocal_Profile-Update.jpg|Edit Profile | ||
+ | Image:Team_Glocal_Create-Join-Group.jpg|Create/Join Group(s) | ||
+ | Image:Team_Glocal_Add-Remove-Friend.jpg|Add/Remove Friend(s) | ||
+ | Image:Team_Glocal_Accept-Reject-Friend-Request.jpg|Accept/Reject Friend Request(s) | ||
+ | Image:Team_Glocal_Send-Gift.jpg|Send Gift(s) | ||
+ | Image:Team_Glocal_Manage-Event.jpg|Manage Event(s) | ||
+ | Image:Team_Glocal_Respond-To-Survey.jpg|Respond to Survey | ||
+ | </gallery> | ||
+ | |||
+ | === <span class="mw-headline"><div style="background: #99CC33; padding: 12px; font-weight: bold"><font color="#FFFFFF" size="5" face="hobo std"><b>UI Mock Up Diagrams</b></font></div></span>=== | ||
+ | |||
+ | ====Web==== | ||
+ | <gallery> | ||
+ | Image:Team_Glocal_UI_Mockup_1-Login.png|Login | ||
+ | Image:Team_Glocal_UI_Mockup_2-Homepage.png|Homepage | ||
+ | Image:Team_Glocal_UI_Mockup_3-Friends-List.png|Friends List | ||
+ | Image:Team_Glocal_UI_Mockup_4-Forum.png|Forum | ||
+ | Image:Team_Glocal_UI_Mockup_5-Activities.png|Activities | ||
+ | Image:Team_Glocal_UI_Mockup_6-Events.png|Events | ||
+ | Image:Team_Glocal_UI_Mockup_7-Profile (friend's).png|Profile (Friend's) | ||
+ | Image:Team_Glocal_UI_Mockup_8-Analytics-Reporting-Dashboard.png|Analytics & Reporting Dashboard | ||
+ | </gallery> | ||
+ | <br> | ||
+ | |||
+ | ====Mobile==== | ||
+ | <gallery> | ||
+ | Image:Team_Glocal_UI_Mockup_Mobile_1-Login.jpg|Login | ||
+ | Image:Team_Glocal_UI_Mockup_Mobile_2-Homepage.jpg|Homepage | ||
+ | Image:Team_Glocal_UI_Mockup_Mobile_3-Friends-List.jpg|Friends List | ||
+ | Image:Team_Glocal_UI_Mockup_Mobile_7-Profile (friend's).jpg|Profile (Friend's) | ||
+ | </gallery> | ||
+ | |||
+ | === <span class="mw-headline"><div style="background: #99CC33; padding: 12px; font-weight: bold"><font color="#FFFFFF" size="5" face="hobo std"><b>Application Architecture Diagrams</b></font></div></span>=== | ||
+ | |||
+ | ==== <span class="mw-headline"><div style="background: #FF9900; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>Project Overview Model</b></font></div></span> ==== | ||
+ | |||
+ | [[Image:Team_Glocal_Project_Overview.jpg|700px|center]] | ||
+ | |||
+ | |||
+ | ==== <span class="mw-headline"><div style="background: #FF9900; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>MVC Model</b></font></div></span> ==== | ||
+ | |||
+ | [[Image:MVC_Model.png|700px|center]] | ||
+ | |||
+ | |||
+ | ==== <span class="mw-headline"><div style="background: #FF9900; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>System Architecture Model</b></font></div></span> ==== | ||
+ | |||
+ | [[Image:Team_Glocal_System_Architecture.jpg|700px|center]] | ||
+ | |||
+ | ==== <span class="mw-headline"><div style="background: #FF9900; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>ELGG Data Model</b></font></div></span> ==== | ||
+ | |||
+ | [[Image:ELGG_Model.png|700px|center]] | ||
+ | |||
+ | ==== <span class="mw-headline"><div style="background: #FF9900; padding: 12px; font-weight: bold"><font color="black" size="5" ><b>BI Flow Model</b></font></div></span> ==== | ||
+ | |||
+ | [[Image:Team_Glocal_BI_Flow.jpg|700px|center]] | ||
+ | <br> | ||
+ | [[Image:CombinedAnalytics.jpg|700px|center]] | ||
+ | |||
+ | === <span class="mw-headline"><div style="background: #99CC33; padding: 12px; font-weight: bold"><font color="#FFFFFF" size="5" face="hobo std"><b>Technologies Used</b></font></div></span>=== | ||
+ | |||
+ | {| class="wikitable centered" width"90%" | ||
+ | !Technology | ||
+ | !Pros | ||
+ | !Cons | ||
+ | |- | ||
+ | |width="100pt"|<!-- Technology-->BuddyPress | ||
+ | |width="1000pt"|<!-- Pros--> | ||
+ | * Easy administrator management: good admin panel | ||
+ | * Clean UI | ||
+ | * Easy to implement themes and manage blogging on the website using WordPress core | ||
+ | |width="1000pt"|<!-- Cons--> | ||
+ | * Lack detailed documentation | ||
+ | * Not a standalone engine. Only a plugin to WordPress platform. | ||
+ | * Development limitation: based on Wordpress API | ||
+ | * Does not provide strong framework | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |width="100pt"|<!-- Technology-->Oxwall | ||
+ | |width="1000pt"|<!-- Pros--> | ||
+ | * Written in PHP | ||
+ | * Regular version updates | ||
+ | * Basic package already contains basic community features (login, friends networking, user management, etc.) | ||
+ | * Easy installation and setup on localhost or web host of Softaculous hosting partners | ||
+ | |width="1000pt"|<!-- Cons--> | ||
+ | * Limited documentation and references | ||
+ | * Limited libraries of plug-ins | ||
+ | * Reasonable developers and forum support | ||
+ | * Power few organisation websites | ||
+ | |- | ||
|} | |} | ||
− | + | === <span class="mw-headline"><div style="background: #99CC33; padding: 12px; font-weight: bold"><font color="#FFFFFF" size="5" face="hobo std"><b>Surveys Conducted</b></font></div></span>=== | |
+ | |||
+ | {| class="wikitable centered" width"90%" | ||
+ | !No | ||
+ | !Objective | ||
+ | !Results | ||
+ | |- | ||
+ | |width="10pt" align="center"|<!--No-->1 | ||
+ | |width="250pt"|<!--Objective--> | ||
+ | *Finding a market for our idea | ||
+ | *Targeted response: 250 | ||
+ | *Actual response: 245 | ||
+ | |width="250pt" align="center"|<!--Results-->[[Media:Team_Glocal_Survey1.pdf|Survey 1 Responses]] | ||
+ | (Updated as of 7 July 2012) | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |width="10pt" align="center"|<!--No-->2 | ||
+ | |width="250pt"|<!--Objective--> | ||
+ | *Understanding our target market | ||
+ | *Targeted response: 250 | ||
+ | *Actual response: 241 | ||
+ | |width="250pt" align="center"|<!--Results-->[[Media:Team_Glocal_Survey2.pdf|Survey 2 Responses]] | ||
+ | (Updated as of 18 August 2012) | ||
+ | |- | ||
+ | |} | ||
+ | |||
+ | |||
+ | == <span class="mw-headline"><div style="background: #669933; padding: 12px; font-weight: bold"><font color="#FFFFFF" size="5" face="hobo std"><b>Learning Outcome Management<div style="float: right;"> [[#top|[top]]]</div></b></font></div></span>== | ||
+ | |||
+ | {| style="border:1px solid #bfbeba" | ||
+ | |- | ||
+ | ! style="background: #ffffff; background-color:#ffffff; border:1px solid #bfbeba" width="30px"| <font color="#000000">No.</font> | ||
+ | ! style="background: #ffffff; background-color:#ffffff; border:1px solid #bfbeba" width="210px"| <font color="#000000">Description</font> | ||
+ | ! style="background: #ffffff; background-color:#ffffff; border:1px solid #bfbeba" width="510px" | <font color="#000000">Expected Learning Outcomes</font> | ||
+ | ! style="background: #ffffff; background-color:#ffffff; border:1px solid #bfbeba" width="310px"| <font color="#000000">Methods of Measurements</font> | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | '''1''' | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" colspan="3" | ''' Integration of business and technology in a sector context ''' | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | 1.1 | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | Business IT Value Linkage Skills | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | #Identify the processes and how it correlates with the IT systems. | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Feedbacks from Clients and Supervisor | ||
+ | # Project Team Discussion | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | '''2''' | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" colspan="3" | ''' IT Architecture, design and development skills ''' | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | 2.1 | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | System Requirements Specification skills | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Gathered client’s requirements and expectations of project. | ||
+ | # Analyse and propose relevant and useful requirements to clients. | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Feedbacks from Clients and Supervisor | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | 2.2 | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | Software and IT Architecture analysis and Design skills | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Identify, design and develop solutions for project so that information can flow smoothly from one end to another. | ||
+ | # Develop application prior to requirements given, that can work on both Web and Mobile platform. | ||
+ | # Integrates existing technologies and social networking sites with application | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Feedbacks from Clients and Supervisor | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | 2.3 | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | Implementation Skills | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Implementing project into place by performing User Tests and Integration and Deployment Test. | ||
+ | # Gather feedbacks on testing and amend changes accordingly. | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Feedbacks from Clients, Supervisor and Users [Pseudo Users and Migrant Workers] | ||
+ | # Project Team Review | ||
+ | # Bug Metrics | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | 2.4 | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | Technology Application Skills | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | #Taking the initiative to learn the following programming Languages and mobile Framework so as to develop HOME Social Network Application: | ||
+ | #*PhoneGap | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Feedbacks from Client, Supervisor and Users | ||
+ | # Project Team Discussion | ||
+ | |||
+ | |- | ||
+ | | colspan="4" | | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | '''3''' | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" colspan="3" | ''' Project management skills ''' | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | 3.1 | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | Scope Management Skills | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # To managed project scope by distributing tasks accordingly to member’s skills and capabilities. | ||
+ | # To justify the project scope by adding or reducing functionalities when neccessary. | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Feedbacks from Supervisor | ||
+ | # Project Team Review | ||
+ | # Schedule Metrics | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | 3.2 | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | Risks Management Skills | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # To constantly monitor, evaluate and identify risk that will affect the project. | ||
+ | # Implementation of mitigation plans to reduce the impact on the project. | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Feedbacks from Supervisor | ||
+ | # Project Team Review | ||
+ | # Schedule Metrics | ||
+ | # Risk Metrics | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | 3.3 | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | Project Integration and Time Management Skills | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Identified the milestones and critical paths of the project. | ||
+ | # Highlight the bottleneck of the project and allocate more resource for the task. | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Feedbacks from Clients and Supervisor | ||
+ | # Project Team Review | ||
+ | # Schedule Metrics | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | 3.4 | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | Configuration Management Skills | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Maintain standards of naming convention and proper audit trails for revision of codes. | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Project Team Review | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | 3.5 | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | Quality Management Skills | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Develop concrete test plans to ensure the quality of the project. | ||
+ | # Evaluate feedbacks from various parties during meetings and UAT and make appreciate changes. | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Feedbacks from Clients and Supervisor | ||
+ | # Feedbacks and results from UAT | ||
+ | # Project Team Review | ||
+ | # Bug Metrics | ||
+ | |||
+ | |- | ||
+ | | colspan="4" | | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | '''4''' | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" colspan="3" | ''' Learning to learn skills ''' | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | 4.1 | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | Search Skills | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Sourcing for useful information from online such as development tools and technologies | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Internal group discussion | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | 4.2 | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | Skills for developing a methodology for learning | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Sharing sessions regularly on the development tools and technologies | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Internal group discussion | ||
+ | |||
+ | |- | ||
+ | | colspan="4" | | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | '''5''' | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" colspan="3" | ''' Collaboration (or team) skills ''' | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | 5.1 | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | Skills to improve the effectiveness of group processes and work products | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Learn from each member’s strengths and complement each others weaknesses. | ||
+ | # Effective communication among all members. | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Internal group discussion | ||
+ | |||
+ | |- | ||
+ | | colspan="4" | | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | '''6''' | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" colspan="3" | ''' Change management skills for enterprise systems ''' | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | 6.1 | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | Skills to diagnose business changes | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Analyze the changes in the business requirements | ||
+ | # Gather future trends of this e-learning and the business value | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Feedbacks from Clients | ||
+ | # Internal group discussion | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | 6.2 | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | Skills to implement and sustain business changes | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Be flexible about the deployment of the solutions to adapt to the changes Supervisor Feedback | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Feedbacks from Clients | ||
+ | |||
+ | |- | ||
+ | | colspan="4" | | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | '''7''' | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" colspan="3" | ''' Communication Skills ''' | ||
+ | |||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | 7.1 | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | Presentation Skills | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Presentations for acceptance, mid-terms and final. | ||
+ | # Regular presentations to supervisor and sponsor on progress of project. | ||
+ | # Frequent meet-ups with Sponsor for requirements gathering and mock-ups to ensure accuracy in understanding between both parties. | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Feedbacks from Clients and Supervisor | ||
+ | # Presentations | ||
+ | |- | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | 7.2 | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | Writing Skills | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Constantly updating and sharing information on Wiki | ||
+ | # Documentation for project management | ||
+ | | style="background: #ffffff; border:1px solid #bfbeba" | | ||
+ | # Feedbacks from Clients and Supervisor | ||
+ | |||
+ | |- | ||
+ | | colspan="4" | | ||
+ | |||
+ | |} |
Latest revision as of 03:34, 30 November 2012
Introduction
The growing pace of economic globalization has created more migrant workers than ever before. Unemployment and increasing poverty have prompted many workers in developing countries to seek work elsewhere, while developed countries have increased their demand for labour, especially unskilled labour. As a result, millions of workers and their families travel to countries other than their own to find work. At present there are approximately 175 million migrants around the world, roughly half of them workers (of these, around 15% are estimated to have an irregular status).
Women make up almost half of migrants. Migrant workers contribute to the economies of their host countries, and the remittances they send home help to boost the economies of their countries of origin. Yet at the same time migrant workers often enjoy little social protection and are vulnerable to exploitation and human trafficking. Skilled migrant workers are less vulnerable to exploitation, but their departure has deprived some developing countries of valuable labour needed for their own economies.
There were 201,000 female domestic workers in Singapore on Work Permits (end of 2010), as reported by the Ministry of Manpower. That made it about one for every five households in the country. In 2002, there were 140,000. The majority, by far, are from Indonesia and the Philippines; smaller numbers come from Sri Lanka, Myanmar, India, Thailand, and Bangladesh.
Contents
Team GLOCAL
Roles and Responsibilities
MEMBER | PRIMARY ROLE | SECONDARY ROLE | RESPONSIBILITIES |
Uma Devi D/O Krishna Moorthy [1] | Project Manager | Usability Analyst |
|
Aung Myat Ko, John[2] | Lead Developer | Tester |
|
NGUYEN Minh Dang [3] | Lead Tester | Developer |
|
PHAM Duong Thai [4] | Usability Analyst | Business Analyst |
|
NG Qi You [5] | Business Analyst | Developer |
|
Project Status
- Our current updates are available here
- Our midterm wiki is available here
- Our final wiki is available here
Project Overview
Motivation
To help migrant workers to assimilate into Singapore faster by providing avenues for them to get help and information quickly.Also, to shorten the response time for migrant workers to get help by creating a direct connection between the subscriber and officer on duty.We also want to provide insights into needs and sentiments of migrant workers in Singapore through analysis of data collected from subscribers’ day-to-day activities on our platform. Hence,these data can come from frequently-used words in messages, most frequently-viewed FAQs and common complaints submitted by subscribers (migrant workers).
Description
We are building myHome, a social networking site which is accessible via a web-based application and a mobile optimised version targeting migrant workers in Singapore. On the backend, our site will capture user habits from day-to-day activities which subscribers perform on our web-based application and/or mobile application and later generate report (in charts and graphs) based on collective behaviour and activities performed on our site.
Activities are defined as user actions performed in our website (either via the web application or mobile application). Log ins and log outs, date and time of feedback submissions and frequently viewed FAQ are some examples.
Collective behaviour is defined as an action which is performed by a group of user (i.e. 10 or more) at the same time or in close timing. An example is between 5:30am to 6:30am, many users log into our website via their mobile phones, many also message their friends (i.e. other members of our site) during this time period. Therefore, we can determine that this is the “hot” period to disseminate events notification or new survey for our users to respond.
Stakeholders
Client Background
The Humanitarian Organisation for Migration Economics (HOME) is committed to the principle that migration of people benefits the global society with a focus on the effects of migration within the context of Singapore.
The mission objectives of HOME are:
- To develop research and education on the socioeconomic of migration on Singapore and the countries of origin;
- To provide social integration services for emigrants and immigrants;
- To provide humanitarian assistance for the effects of 'crisis' migration.
There are some 800,000 migrant workers or more in Singapore and HOME has provided direct assistance to more than 50,000 men and women migrants and victims of human trafficking and forced labour, who availed of our programme and services. Among those helped included migrants affected by the Tsunami disaster in 2005 and the present global economic crisis in 2008/2009. On one occasion, HOME provided shelter for 15 Indonesian women and their children, who were abandoned at sea by seamen.
Scope
Module 1: Account Management
Basic security feature to authenticate user and restrict the functions they can perform based on their assigned role. Currently, there are two roles – user and administrator. Also, users can link their Facebook account to myHome.
User:
- Register account
- Edit profile and account settings
- Restrict site information to logged-in users only
- Connect with Facebook
- Implement CAPTCHA
- Cancel account
Admin:
- Delete user(s)
- Manage site administration
- Validate user(s)
Module 2: Social Interaction
Basic social network functionalities to facilitate online interaction.
- Create group
- Add friends to group
- Report inappropriate content
- Send message
- Accept/Reject friend invite
- Instant chat (with friends)
- Comment/Like/Post a picture
- Tickle (replaced with Gift)
Module 3: Event Management
Subscribers can indicate attendance (Yes, No) for upcoming events. Administrators will be able to keep track of sign-up rate and make more accurate logistics arrangements (venue, food, tables & chairs, etc.)
User:
- Invite friends (replaced with event listing)
- Set event preferences
Admin
- Create/Edit/Delete event
- Set event privacy
- Invite attendee(s) (replaced with event listing)
- Noticeboard (Widget)
- Set targeted group
Module 4: Feedback Management
Subscribers can submit a complaint or enquiry (grouped into feedback) while administrators will receive alert for inquiries (consolidated into topics) instantly or after fixed interval [for phone and email notification], and can respond to the feedback as soon as possible.
- Post an incident/inquiry (with email notification to admin)
- Reply to incident/inquiry by admin
Module 5: Q & A Management
Users can search for answers to their questions either by entering their questions into the search box or browse through the category list of previously posted questions and their respective answers. Each question posted will go through the text parsing to be categorized under three main topics: legal, employment, health.
- Search Question(s)
- List most freqently asked questions (by category, search count)
- Post Question(s) & Answer(s)
Module 6: Survey Management
Subscribers can respond to surveys and view their list of previously completed surveys. Administrator can create new surveys, delete outdated or error surveys, close surveys which have passed their closing dates.
- Draft/Post/Delete Surveys
- Updated: Show surveys on user profile
- Respond to survey
- Disseminate survey (via email)
Module 7: Analytics & Reporting
For administrators only, they will be able to: See site user statistics (user access log, user demographics, etc) using embedded Google Analytic code and Generate reports about most frequently appeared words in categories - employment, legal, and health. Each category will have a set of predefined key words to help do text parsing for posted questions. Reports will come under the form of pie charts for words under each category and bar charts to give general comparison among the top three categories.
- Data Analytics
- Simple chart, post by user - most influential user [Top 10 users],[Dropdown list of timing]
- Medium chart, category breakdown based on number of questions [legal/healthcare/employment], joining 3 or 4 tables together and gathering sentiments. *collate the topics to categories
- Complex chart, tag cloud based on number of questions posted in Q&A, similar to word cloud.
Module 8: X Factor
Voice-enabled myHOME Social Network for Android
This function will enhance the site-wide navigation of myHOME social network on mobile where the screen size is substantially small by adding the ability to say voice commands to go to different pages.
Our android app will recognize the voice commands, make necessary processing of the commands and then redirect the user to a different page. (e.g. registration page, profile page, activity page, event page etc.). First, we will start with English commands only but will add support for other languages if time and technology permit.
Project Management
Schedule
Project Schedule (Planned): Link
Project Schedule (Actual): Link
Project Schedule (Adjusted): Link
Schedule Metric: Link
Timeline
Project Timeline: Link
Bug Log & Metric
Bug Log & Metric: Link
Risk Management & Metric
No | Type of risk | Description | Probability | Impact | Assessment | Mitigation Strategy |
---|---|---|---|---|---|---|
1 | Technical | [Despite research and sourcing done prior to procuring our current server.] Sudden unforeseen problems (crashes + slowness) with production server during our UT#1, disrupting our team's ability to consolidate valuable inputs from our invited testers. This caused us not to be able to collect concrete results and findings from the UT, causing us to haul the UT process. | High | High | A* | Inform sponsor of the problem while contacting hosting company to find out the root cause of problems encountered. Next, source for another hosting plan - preferably "tried & tested". If user testing and/or mid-term presentation are affected, make the necessary arrangement to postpone them. |
2 | Business | Broken commitment from Client, promised to provide migrant workers to test our application during UT#1, however Client had sudden change of plan as an event was organised by the NGO on the same day as our UT#1. | Medium-High | High | A* | To continue with the scheduled UT date by getting 40 pseudo testers [SMU students] to assist us with our UT#1, as their capabilities and skills acquired through Facebook would very much similar to the migrant workers.
Team also continued to confirm with Client to conduct the UT with the actual testers on 7th October 2012. |
3 | Technical | Members are unfamiliar with the new technologies and their accompanying framework, for instance ELGG framework, Kettle Analytics Tool, PHP. Hence causing delays in development and testing. | Medium | Medium | B | Assign each member to cover a technical aspect of the technologies and ensure they are comfortable with it. Do a bi-weekly sharing of what was read and practised - to ease the learning curve and encourage peer learning. |
4 | Technical | Since there are tons of open source codes to assist us in our project, we have to select and test many packages and use the appropriate ones in our project. This process can be both time-consuming and demoralising causing the team time and energy. | Low-Medium | Medium | C [Monitor] |
Encourage each member to prepare simple documentation of the technologies covered along the way and share these documents internally (via Google Docs). |
5 | Technical | As the project is dealing with an existing (huge) framework, weakness in the framework may cause unexpected bugs to surface. | Low | Low | C [Monitor] |
Utilize the testing phase of each iteration to look out for potential bugs that may exist. When possible, try to get 1 or 2 people from the public/friends/focus group members to test out the functions of the concerned scope. |
6 | Technical | Earlier this week, our site was down for two days because our own nameservers used for the cpanel account were down after the server was unexpectedly restarted but the ip aliases were not. Limited knowledge in server handling knowledge had put us at a risk. | Low | High | B | We talked to GoDaddy Live support and used their off-site DNS servers for our domain vivamyhome.com instead. After a few hours, the new DNS records were properly propagated and the site was up and running again. |
7 | Technical | The risk we had for SOLR which is a type of search function was only explored after midterm once the sponsor's main requirements were re-highlighted with additional tasks. Therefore, the team has no prior experience or knowledge in this field, as well as it was not included in the early development phases. | Low | Medium | C | Team got advice from sponsor, supervisor and Professor Feida, and based on the advises and suggestions the team progressively managed to build the function and complete the iteration. |
8 | Business | Impromptu changes to user requirements from client (beneficiary) | Medium | High | A | Regular communication with client, schedule bi-weekly meetings with client and conduct focus group discussion with end users every three weeks. Also, team (led by our Project Manager) will try to get our client to commit to discussed scopes and functionalities (verbal agreement of project deliveries). |
9 | Business | Last-minute cancellation of meeting with client due to travel commitments, urgent meetings/discussions/incidents to attend to. | Medium (prev. Low) | Medium | B | Open several channels of communication with the client (Facebook, Emails, (Project Manager) mobile number). Also, make sure there's always a point of contact (nominated representative to stand-in) if she is not available. |
10 | Resources | Underestimating resource required, poor resource allocation; Members having internship and travel commitments. | High | High | A* [Risk Eliminated] |
Forward planning and periodic review of schedule, start early – have regular meetings 2 to 3 times weekly and also create a Facebook group to share ideas, news, and web links to interesting technologies to look at and iron out small issues ahead of meetings |
11 | Resources | Multiple users working on multiple files, hence information and file sharing can become hectic and team may face overlaps at times which may cause unneccessary delays. | Medium | Medium | B [Risk Reduced] |
To eliminate these problems from arising, team has to come up with a shared folder, eg) SVN for committing of codes to compile it frequently. The group also has to practice proper committing procedure. |
Meeting Minutes
- Meeting Minutes 1
- Meeting Minutes 2
- Meeting Minutes 3
- Meeting Minutes 4
- Meeting Minutes 5
- Meeting Minutes 6
- Meeting Minutes 7
- Meeting Minutes 8
- Meeting Minutes 9
- Meeting Minutes 10
- Meeting Minutes 11
- Meeting Minutes 12
- Meeting Minutes 13
- Meeting Minutes 14
- Meeting Minutes 15
- Meeting Minutes 16
- Meeting Minutes 17
Project Documentation
Use Case Diagrams
Functional Flow Diagrams
UI Mock Up Diagrams
Web
Mobile
Application Architecture Diagrams
Project Overview Model
MVC Model
System Architecture Model
ELGG Data Model
BI Flow Model
Technologies Used
Technology | Pros | Cons |
---|---|---|
BuddyPress |
|
|
Oxwall |
|
|
Surveys Conducted
No | Objective | Results |
---|---|---|
1 |
|
Survey 1 Responses
(Updated as of 7 July 2012) |
2 |
|
Survey 2 Responses
(Updated as of 18 August 2012) |
Learning Outcome Management
No. | Description | Expected Learning Outcomes | Methods of Measurements |
---|---|---|---|
1 | Integration of business and technology in a sector context | ||
1.1 | Business IT Value Linkage Skills |
|
|
2 | IT Architecture, design and development skills | ||
2.1 | System Requirements Specification skills |
|
|
2.2 | Software and IT Architecture analysis and Design skills |
|
|
2.3 | Implementation Skills |
|
|
2.4 | Technology Application Skills |
|
|
3 | Project management skills | ||
3.1 | Scope Management Skills |
|
|
3.2 | Risks Management Skills |
|
|
3.3 | Project Integration and Time Management Skills |
|
|
3.4 | Configuration Management Skills |
|
|
3.5 | Quality Management Skills |
|
|
4 | Learning to learn skills | ||
4.1 | Search Skills |
|
|
4.2 | Skills for developing a methodology for learning |
|
|
5 | Collaboration (or team) skills | ||
5.1 | Skills to improve the effectiveness of group processes and work products |
|
|
6 | Change management skills for enterprise systems | ||
6.1 | Skills to diagnose business changes |
|
|
6.2 | Skills to implement and sustain business changes |
|
|
7 | Communication Skills | ||
7.1 | Presentation Skills |
|
|
7.2 | Writing Skills |
|
|