https://wiki.smu.edu.sg/is480/api.php?action=feedcontributions&user=Huiling.ong.2010&feedformat=atomIS480 - User contributions [en-gb]2024-03-28T10:30:44ZUser contributionsMediaWiki 1.33.1https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit&diff=114789IS480 Team wiki: 2012T1 6-bit2012-12-05T07:22:07Z<p>Huiling.ong.2010: /* Final */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Current Status</font></div>=<br />
<br />
{| class="wikitable" cellpadding="15"<br />
<br />
|-<br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 46%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Current Iteration</b> <br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 50%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Meeting Status</b> <br />
|-<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Iteration Number :''' <br />
16 *Final Iteration*<br />
<br><br />
'''Iteration Start Date : '''<br />
24 November 2012<br />
<br><br />
'''Iteration End Date :'''<br />
3 December 2012<br />
<br><br />
'''Iteration Task :'''<br />
<br><br />
1. Final Presentation<br />
<br><br />
2. Poster Day<br />
<br><br />
<br />
<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Weekly Meeting Schedule'''<br />
<br><br />
Every Monday, Wednesday, Friday<br />
<br><br />
SIS Analytics Kitchen<br />
<br><br />
12pm to 3pm<br />
<br><br />
<br />
'''Weekly Supervisor Meeting'''<br />
<br><br />
Every Monday<br />
<br><br />
2pm to 3pm<br />
|}<br />
<div style="text-align: right;"><br />
<font size="2">''Last Update: 28 November 2012''</font><br />
</div><br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Team</font></div>=<br />
[[Image:6-bitTeamMembers.png|alt=text|6-bitTeamMembers|centre|650px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Project: Chapalang</font></div>=<br />
<div style="text-align: center"><font color="#00BFFF">''Talk, Buy, Sell, Share, all on Chapalang!''</font></div><br />
<font color="#FE2EF7">Chapalang!</font> is a social utility that connects people with friends and new friends by offering a place for exchanging ideas and information on its public domain. People use our discussion forums to write HOWTOs, share findings, ask questions, comment on news, and many more.<br />
<br><br />
<font color="#FE2EF7">Chapalang!</font> also features a social marketplace for you to buy online, and participate in mass orders in a convenient and reliable way.<br />
<br><br />
Best of all, you can browse wish lists of your friends to know what are the right things to buy on special occasions. You could buy the gift on <br />
<font color="#FE2EF7">Chapalang!</font> and have it sent to their doorsteps, or organize a Gift Sharing campaign to share the costs of gift with other friends.<br />
<br />
[[Image:chapalangprocesses.png|1100px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Main Features</font></div>=<br />
[[Image:ChapalangLogo.png|left|150px]]<br />
<br><br />
<i>proposes the following unique features:</i><br />
<br><br />
[[Image:6-bitGroupbuyprocess.png|center|1000px]]<br />
<br><br />
<b>Gifts Sharing</b> : <br />
<br><br />
Gifting can be simple or collective. A simple gift is purchased when a user pays for the full costs of the gift, and states the recipient’s contact details upon checkout. Chapalang! will contact the recipient for their address, and subsequently fulfil the order with the delivery of goods.<br />
<br><br />
<br><br />
A collective gift is purchased when a user takes on the role of an organizer and initiates a Gift Sharing Campaign. He will select a product from a user’s wish list, or any other product in the marketplace, and designate it to be the gift to be shared. He will also decide on the product options, if any, as well as the delivery method. <br />
<br><br />
<br><br />
Thereafter, he can invite a list of mutual friends whom he wants to share the gift with. The invitees will be informed of the campaign via a notification, and will be able to contribute any varying amount on the campaign page. They will also be able to hide their amount of contribution, or even hide their contribution record from public. Upon successfully raising the target amount which is the price of the gift, an email will be sent to the recipient for him/her to update their address for fulfilment and delivery.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitMassorderprocess.png|center|1000px]]<br />
<b>Mass orders</b> : <br />
<br>Mass Orders (MO) should be structured and organized, just like a regular product item in the marketplace. <br />
<br><br />
<br><br />
When creating an MO, the buyer will input the price, description, minimum collective quantity for the MO to go through, the maximum collective quantity accepted for the MO if it’s a limited quantity offer, as well as the start and end period of the MO. An MO organizer can be an individual or a company. The organizer will be able to invite his/her friends, or regular customers to the MO. <br />
<br><br />
<br><br />
Participants of an MO will be able to view the MO page, enter a desired quantity and checkout. In the checkout process, participants will be required to enter their delivery address and choose their preferred shipping method. Payment is made upon ordering, safeguarded by the esrow service, and will be paid to the sellers if the MO is successful. In the event that MO is unsuccessful or cancelled, full amount of their orders will be refunded to all participants automatically.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitEscrowprocess.png|centre|1000px]]<br />
<b>Escrow</b> : <br />
<br><br />
In most other agent websites, buyers either pay to sellers directly or buyers pay to the agent and agent will pay the buyers 30 days later. We will turn this credit period to the advantage of buyers and sellers, introducing assurance.<br />
<br><br><br />
In any transaction on Chapalang!, the buyer will pay to Chapalang! directly. Sellers are notified of the receipt of payment, and will proceed to ship the item out to the buyer. Upon receipt of the order, buyers will revisit Chapalang! and indicate that the goods are received satisfactorily, and Chapalang! will then pay the sellers in the next 3 days. However, if there is no response or dispute from the buyers within 30 days, the order is assumed to be satisfactorily fulfilled and the payment will be released to the seller. In the event of disputes, buyers and sellers are encouraged to negotiate for a recovery, or in the case of an exhausted negotiation, Chapalang! may issue a full or partial refund to the customers.<br />
<br><br><br />
Systematically, the Chapalang! system will support this this use case through a series of functions. <br />
*Firstly, the system will support a goods receipt acknowledgement process, recording the goods receipt, triggering of payment activities to sellers upon 30 days grace or upon the record of goods receipt. <br />
*Secondly, sellers should be able to see their sales and know how much they will be receiving from Chapalang! and when. <br />
*Thirdly, there should be a messaging channel to facilitate communications between the buyer and seller<br />
*Fourthly, there should be a refund method to allow sellers to refund a transaction should be accept that he’s unable to recover or fulfil the order<br />
*Lastly, administrator of Chapalang! should be able to see a list of fulfilled, or assumed fulfilled transactions ready for payment to the sellers<br />
<br />
<div style="text-align: right;"><br />
<font size="2">''Prototype of Chapalang's Features: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype Click Here]''</font><br />
</div><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Low Level Functions</font></div>=<br />
==Web Parser==<br />
As an interactive feature, URLs shared on Chapalang! will offer a preview which contains the site title, url, image and description. This should reflect the final URL, instead of any redirecting URL at a higher level.<br />
<br><br><br />
The picking of appropriate objects (title, url, image or description) is important, where standardized Open Graph (OG) protocol meta data of a webpage will be prioritized, before seeking through the other HTML components for referencing objects.<br />
==Private Message==<br />
[[Image:6-bit_message.png|center|600px]]<br />
There should be an in-system communication channel for general users, buyers and sellers. Potential buyers can clarify product specifications with sellers, sellers can confirm delivery address with buyers in case of anomalies, and general users can use it for chatting purposes.<br />
<br><br />
<br>It should be able to perform CRUD of messages between 2 users, in a conversational format. Users are notified via email whenever they receive a message. They will also be able to see past messages exchanged, in a single conversation page.<br />
==Image Cropping Tool==<br />
As all images uploaded by users can be of different dimensions, our system will need a tool to automatically resize and crop away unimportant parts to fit the image dimensions on different pages.<br />
<br><br><br />
Hence, the Image Cropping Tool will help us with automatically resizing an image to the most suitable resolution, before cropping away any extended sides and focus on the centre of the image which is usually the most important message. This tool will be applied throughout the entire platform, on both discussion forums and marketplace.<br />
<br />
==Notifications==<br />
[[Image:6-bit_notification.png|center|300px]]<br />
Users should be appropriately notified on any activities concerning them. They will have a new notifications whenever someone replies to their post, whenever a friend is following them in Chapalang!, or when a product purchased is being shipped, et cetera.<br />
<br><br />
<br><br />
Notification entries should link them to appropriate pages for follow-up actions or even simply viewing more details of the notification. Each in-system notification should also be tied to an email notification for a timelier update to users, and users should have the ability to modify their notifications settings for privacy or information flood control.<br />
<br />
==Search function==<br />
[[Image:6-bit_search.png|center|600px]]<br />
There are many content types on Chapalang!, which includes people, messages, products, posts, et cetera. These content types should be searchable for the purpose of conveniently accessing specific content.<br />
==Profile page==<br />
[[Image:6-bit_profilepage.png|center|600px]]<br />
Every user will have a dedicated profile page, which contains their profile picture, basic particulars, activities and friends. This will create a more social environment, where information of a user is shared among friends.<br />
==Management pages==<br />
[[Image:6-bit_management.png|center|250px]]<br />
There should be a set of management pages, for the management of sales, orders or products. These pages will be able to perform basic CRUD functions, as well as other functions allowing appropriate manipulation of an activity. For example, Manage Sales will allow sellers to view transactional details as well as updating shipping details when an order is fulfilled. On the other hand, Manage Orders will allow buyers to review their purchases and be informed whether their orders are fulfilled. Correspondingly, Manage Products will allow the sellers administer all aspects of a product, from its description, images, pricing, to its options and shipping methods.<br />
<br />
==Settings pages==<br />
[[Image:6-bit_settings.png|center|600px]]<br />
There will be separate pages for Accounts Settings, Privacy Settings and Notifications Settings. Firstly, Account Settings will allow a user to change their basic information imported from Facebook. Secondly, Privacy Settings will provide the option to show or hide certain sensitive information that a user may choose not to show in the public. Lastly, Notifications Settings will help the users manage the quantity and quality of notifications that they receive as they might choose not to be informed of certain activities to prevent information overload.<br />
==Personalized dashboard==<br />
[[Image:6-bit_personalizeddb.png|center|600px]]<br />
A dashboard is the first page the user will see upon login, and will contain a mash up of content from various components on the portal. The content published to the dashboard is personalized through stratification supported by data-driven analytics.<br />
<br><br />
<br><br />
The dashboard will contain the following data:<br />
* Relevant topics from subscribed forums<br />
* Featured discussions<br />
* Product recommendations generated by analytics<br />
* Recent purchases made by friends<br />
* Featured mass orders recommendations generated by analytics<br />
* Seasonal or holidays promotional products recommendations generated by analytics<br />
* New arrival products recommendations generated by analytics<br />
* Reminders on upcoming special dates, friends’ birthdays, and activity invites<br />
The dashboard has a 3-step approach in deriving personalized content. <br />
<br><br><br />
Firstly, a set of meta data describing a user is generated. We will perform sentimental analysis with user activities, Facebook status feed and likes, as data input, and generate the meta data using Chapalang Analytics engine.<br />
<br><br />
Secondly, another set of meta data describing a product is also generated. We have developed an algorithm where it will take in all product-related attributes as input, and generate a list of meta data after removing language prepositions with emphasis on extracting nouns.<br />
Lastly, both set of meta data are matched to produce a list of recommendations by using the Naïve Bayes Classifier which applies Bayes’ Theorem with strong naïve independent assumptions. More information on the underlying analytics can be found in the Chapalang Analytics section.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Sponsor</font></div>=<br />
[[Image:Dotcom_Logo.jpg|left]]<br />
<b>Chapalang</b> is a self-proposed project for DotCom Enterprise. Upon successful development, DotCom will commercialize the project for live operations. Mr. Eric Chew, Special Projects Manager will be the primary contact from DotCom. Throughout the development and implementation stages, our team will deploy the project on the live systems provided by DotCom.<br />
<div style="margin-bottom:30px;><br />
<br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Academic Milestones</font></div>=<br />
==Acceptance==<br />
[[Media:Chapalang_Acceptance_Slides.pdf|<font color="#CD004E"> Acceptance Presentation Slides]]<br />
==Midterm==<br />
[[IS480_Team_wiki:_2012T1_6-bit_Midterm_Wikipage | <font color="#CD004E"><b>Mid Term Wiki</b></font>]]<br />
<br><br />
[[Media:Chapalang_Midterm_Slides.pdf|<font color="#CD004E"> Midterm Presentation Slides]]<br />
==Final==<br />
[https://dl.dropbox.com/u/56071797/Final_Presentation.pdf <font color="#CD004E"><b>Final Presentation Slides</b></font>]<br />
==FYP Report==<br />
[https://dl.dropbox.com/u/56071797/6-bit%20Final%20Report.docx <font color="#CD004E"><b>Final Report</b></font>]</div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_PD_Business_Intelligence_and_Analytics&diff=114788IS480 Team wiki: 2012T1 6-bit PD Business Intelligence and Analytics2012-12-05T07:17:39Z<p>Huiling.ong.2010: /* Analysis of User’s Facebook Persona */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #FE2E64; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:110%; text-align:center; color:#FE2E64" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams|<font color="#CD004E"><b>Technical Diagrams</b></font>]]<br />
<br />
| style="font-size:110%; text-align:center; color:#FE2E64" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype|<font color="#CD004E"><b>User Interface Prototype</b></font>]]<br />
<br />
| style="font-size:110%; text-align:center; color:#FE2E64" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_PD_Business_Intelligence_and_Analytics|<font color="#CD004E"><b>Business Intelligence and Analytics</b></font>]]<br />
|}<br />
<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang Benchmark</font></div>=<br />
CodeIgniter has a Benchmarking class that is always active, enabling the time difference between any two marked points to be calculated. In addition, the benchmark is always started the moment the framework is invoked, and ended by the output class right before sending the final view to the browser, enabling a very accurate timing of the entire system execution to be shown.<br />
<br><br><br />
Chapalang Benchmark is a custom tool developed with the foundation of CodeIgniter’s Benchmarking class. Additional customization has been made to reflect extended measurement of execution for process-based series of activities, integrated with a database table to support other analytical execution.<br />
==Audit Trail==<br />
One of the purpose of Chapalang Benchmark is to support an audit trail on the activities performed by users on Chapalang!. The tool collects the following set of data:<br />
* Member ID<br />
* Controller<br />
* Controller method<br />
* URL<br />
* Start timestamp<br />
* End timestamp<br />
* Elapsed time<br />
By having Chapalang Benchmark to support an audit trail, we are able to trace the series of activities performed by a specific user on our system, given any time period. <br />
<br><br><br />
While it may not be friendly to the privacy of users, and not efficient to design models customized to a specific user, it is useful to use the activity data collected to support advance analytics. At this stage, the data acts as a complementary operational data source for our analytics behind the Personalized Dashboard.<br />
<br><br><br />
There are other usefulness of the activity data to discover system anomalies, user experiences, and more. Some examples are further elaborated below. <br />
<!-- <br />
==Sample stored operations==<br />
--><br />
<!-- <br />
==Findings from Chapalang Benchmark==<br />
--><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang Analytics</font></div>=<br />
==Purpose==<br />
The purpose of Chapalang Analytics is primarily to support the low-level function, Personalized Dashboard of the portal. While that is the only application of Chapalang Analytics at this stage, it can be further expanded into other data-driven and user-oriented features which include but not limited to, target advertising and content filtering.<br />
==Operational Data Source==<br />
The analytics will make use of the following data:<br />
* Facebook statuses, likes, post times, friends, gender, birthday, relationship status<br />
* Chapalang Benchmark, which collects data on all user activities on Chapalang!, such as browsing history and past purchases<br />
* Sentimental database, containing a list of words that characterises user’s personality and behaviour<br />
==Analytical Techniques==<br />
The analytics will make use of the following techniques:<br />
* Semantic Analytics<br />
* Sentimental Analytics<br />
* Rule-based Analytics<br />
==Analysis of User’s Facebook Persona==<br />
The first analytical step of Chapalang Analytics is to analyse a user’s Facebook persona. Through the analysis of the user-specific ODS, we will identify certain characteristics of a user.<br />
<br><br />
===Discoveries from Chapalang Benchmark===<br />
As we analyse the data from Chapalang Benchmark, there are some interesting discoveries that would otherwise be hidden or unknown to us.<br />
====Inconsistent elapsed time for view_product page====<br />
Despite using the same set of application files, the elapsed time for different products is different. We have some product pages which take as long as varying 15-30 seconds to load, while the rest are mostly under our acceptable response time of 3 seconds. Though we have yet to isolate the cause and find a permanent solution, the discovery will help us identify problems like these which may not be reported by users lead to a reduction in returning visitors.<br />
====Electronic products are most interesting to visitors====<br />
As we run more analysis, we realized that electronic products are most interesting to visitors because 87% of our visitors will view at 2 or more electronics products. They also spend longer time on electronics product pages than other pages on the portal. This might be useful for the company to offer more electronic goods deals, promotions or marketing.<br />
====Most traffic comes early in the morning and evening====<br />
From Chapalang Benchmark data, we also noticed a trend that most visitors, both registered and unregistered, visit our portal between 9am and 10am, and 3pm to 4pm. We are speculating that this might be because we have a user base consisting of SMU students and young working adults. The time window matches approximately the start time of classes in the morning and evening sessions. Also, it appears to be the first hour of work and evening tea-break time for working adults. Both of the reasons indirectly supports that they might be visiting our portal during break time and hence the company can hold hourly sales during these periods.<br />
<br />
[https://dl.dropbox.com/u/56071797/Chapalang%20Analytics.docx |<font color="#CD004E"><b>Chapalang Analytics</b></font>]</div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_PD_Business_Intelligence_and_Analytics&diff=114787IS480 Team wiki: 2012T1 6-bit PD Business Intelligence and Analytics2012-12-05T07:15:28Z<p>Huiling.ong.2010: /* Outcome */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #FE2E64; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:110%; text-align:center; color:#FE2E64" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams|<font color="#CD004E"><b>Technical Diagrams</b></font>]]<br />
<br />
| style="font-size:110%; text-align:center; color:#FE2E64" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype|<font color="#CD004E"><b>User Interface Prototype</b></font>]]<br />
<br />
| style="font-size:110%; text-align:center; color:#FE2E64" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_PD_Business_Intelligence_and_Analytics|<font color="#CD004E"><b>Business Intelligence and Analytics</b></font>]]<br />
|}<br />
<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang Benchmark</font></div>=<br />
CodeIgniter has a Benchmarking class that is always active, enabling the time difference between any two marked points to be calculated. In addition, the benchmark is always started the moment the framework is invoked, and ended by the output class right before sending the final view to the browser, enabling a very accurate timing of the entire system execution to be shown.<br />
<br><br><br />
Chapalang Benchmark is a custom tool developed with the foundation of CodeIgniter’s Benchmarking class. Additional customization has been made to reflect extended measurement of execution for process-based series of activities, integrated with a database table to support other analytical execution.<br />
==Audit Trail==<br />
One of the purpose of Chapalang Benchmark is to support an audit trail on the activities performed by users on Chapalang!. The tool collects the following set of data:<br />
* Member ID<br />
* Controller<br />
* Controller method<br />
* URL<br />
* Start timestamp<br />
* End timestamp<br />
* Elapsed time<br />
By having Chapalang Benchmark to support an audit trail, we are able to trace the series of activities performed by a specific user on our system, given any time period. <br />
<br><br><br />
While it may not be friendly to the privacy of users, and not efficient to design models customized to a specific user, it is useful to use the activity data collected to support advance analytics. At this stage, the data acts as a complementary operational data source for our analytics behind the Personalized Dashboard.<br />
<br><br><br />
There are other usefulness of the activity data to discover system anomalies, user experiences, and more. Some examples are further elaborated below. <br />
<!-- <br />
==Sample stored operations==<br />
--><br />
<!-- <br />
==Findings from Chapalang Benchmark==<br />
--><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang Analytics</font></div>=<br />
==Purpose==<br />
The purpose of Chapalang Analytics is primarily to support the low-level function, Personalized Dashboard of the portal. While that is the only application of Chapalang Analytics at this stage, it can be further expanded into other data-driven and user-oriented features which include but not limited to, target advertising and content filtering.<br />
==Operational Data Source==<br />
The analytics will make use of the following data:<br />
* Facebook statuses, likes, post times, friends, gender, birthday, relationship status<br />
* Chapalang Benchmark, which collects data on all user activities on Chapalang!, such as browsing history and past purchases<br />
* Sentimental database, containing a list of words that characterises user’s personality and behaviour<br />
==Analytical Techniques==<br />
The analytics will make use of the following techniques:<br />
* Semantic Analytics<br />
* Sentimental Analytics<br />
* Rule-based Analytics<br />
==Analysis of User’s Facebook Persona==<br />
The first analytical step of Chapalang Analytics is to analyse a user’s Facebook persona. Through the analysis of the user-specific ODS, we will identify certain characteristics of a user.<br />
<br><br />
===Discoveries from Chapalang Benchmark===<br />
As we analyse the data from Chapalang Benchmark, there are some interesting discoveries that would otherwise be hidden or unknown to us.<br />
====Inconsistent elapsed time for view_product page====<br />
Despite using the same set of application files, the elapsed time for different products is different. We have some product pages which take as long as varying 15-30 seconds to load, while the rest are mostly under our acceptable response time of 3 seconds. Though we have yet to isolate the cause and find a permanent solution, the discovery will help us identify problems like these which may not be reported by users lead to a reduction in returning visitors.<br />
====Electronic products are most interesting to visitors====<br />
As we run more analysis, we realized that electronic products are most interesting to visitors because 87% of our visitors will view at 2 or more electronics products. They also spend longer time on electronics product pages than other pages on the portal. This might be useful for the company to offer more electronic goods deals, promotions or marketing.<br />
====Most traffic comes early in the morning and evening====<br />
From Chapalang Benchmark data, we also noticed a trend that most visitors, both registered and unregistered, visit our portal between 9am and 10am, and 3pm to 4pm. We are speculating that this might be because we have a user base consisting of SMU students and young working adults. The time window matches approximately the start time of classes in the morning and evening sessions. Also, it appears to be the first hour of work and evening tea-break time for working adults. Both of the reasons indirectly supports that they might be visiting our portal during break time and hence the company can hold hourly sales during these periods.</div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_PD_Business_Intelligence_and_Analytics&diff=114786IS480 Team wiki: 2012T1 6-bit PD Business Intelligence and Analytics2012-12-05T07:15:22Z<p>Huiling.ong.2010: /* Model for Personalized Dashboard */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #FE2E64; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:110%; text-align:center; color:#FE2E64" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams|<font color="#CD004E"><b>Technical Diagrams</b></font>]]<br />
<br />
| style="font-size:110%; text-align:center; color:#FE2E64" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype|<font color="#CD004E"><b>User Interface Prototype</b></font>]]<br />
<br />
| style="font-size:110%; text-align:center; color:#FE2E64" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_PD_Business_Intelligence_and_Analytics|<font color="#CD004E"><b>Business Intelligence and Analytics</b></font>]]<br />
|}<br />
<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang Benchmark</font></div>=<br />
CodeIgniter has a Benchmarking class that is always active, enabling the time difference between any two marked points to be calculated. In addition, the benchmark is always started the moment the framework is invoked, and ended by the output class right before sending the final view to the browser, enabling a very accurate timing of the entire system execution to be shown.<br />
<br><br><br />
Chapalang Benchmark is a custom tool developed with the foundation of CodeIgniter’s Benchmarking class. Additional customization has been made to reflect extended measurement of execution for process-based series of activities, integrated with a database table to support other analytical execution.<br />
==Audit Trail==<br />
One of the purpose of Chapalang Benchmark is to support an audit trail on the activities performed by users on Chapalang!. The tool collects the following set of data:<br />
* Member ID<br />
* Controller<br />
* Controller method<br />
* URL<br />
* Start timestamp<br />
* End timestamp<br />
* Elapsed time<br />
By having Chapalang Benchmark to support an audit trail, we are able to trace the series of activities performed by a specific user on our system, given any time period. <br />
<br><br><br />
While it may not be friendly to the privacy of users, and not efficient to design models customized to a specific user, it is useful to use the activity data collected to support advance analytics. At this stage, the data acts as a complementary operational data source for our analytics behind the Personalized Dashboard.<br />
<br><br><br />
There are other usefulness of the activity data to discover system anomalies, user experiences, and more. Some examples are further elaborated below. <br />
<!-- <br />
==Sample stored operations==<br />
--><br />
<!-- <br />
==Findings from Chapalang Benchmark==<br />
--><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang Analytics</font></div>=<br />
==Purpose==<br />
The purpose of Chapalang Analytics is primarily to support the low-level function, Personalized Dashboard of the portal. While that is the only application of Chapalang Analytics at this stage, it can be further expanded into other data-driven and user-oriented features which include but not limited to, target advertising and content filtering.<br />
==Operational Data Source==<br />
The analytics will make use of the following data:<br />
* Facebook statuses, likes, post times, friends, gender, birthday, relationship status<br />
* Chapalang Benchmark, which collects data on all user activities on Chapalang!, such as browsing history and past purchases<br />
* Sentimental database, containing a list of words that characterises user’s personality and behaviour<br />
==Analytical Techniques==<br />
The analytics will make use of the following techniques:<br />
* Semantic Analytics<br />
* Sentimental Analytics<br />
* Rule-based Analytics<br />
==Analysis of User’s Facebook Persona==<br />
The first analytical step of Chapalang Analytics is to analyse a user’s Facebook persona. Through the analysis of the user-specific ODS, we will identify certain characteristics of a user.<br />
<br><br />
===Discoveries from Chapalang Benchmark===<br />
As we analyse the data from Chapalang Benchmark, there are some interesting discoveries that would otherwise be hidden or unknown to us.<br />
====Inconsistent elapsed time for view_product page====<br />
Despite using the same set of application files, the elapsed time for different products is different. We have some product pages which take as long as varying 15-30 seconds to load, while the rest are mostly under our acceptable response time of 3 seconds. Though we have yet to isolate the cause and find a permanent solution, the discovery will help us identify problems like these which may not be reported by users lead to a reduction in returning visitors.<br />
====Electronic products are most interesting to visitors====<br />
As we run more analysis, we realized that electronic products are most interesting to visitors because 87% of our visitors will view at 2 or more electronics products. They also spend longer time on electronics product pages than other pages on the portal. This might be useful for the company to offer more electronic goods deals, promotions or marketing.<br />
====Most traffic comes early in the morning and evening====<br />
From Chapalang Benchmark data, we also noticed a trend that most visitors, both registered and unregistered, visit our portal between 9am and 10am, and 3pm to 4pm. We are speculating that this might be because we have a user base consisting of SMU students and young working adults. The time window matches approximately the start time of classes in the morning and evening sessions. Also, it appears to be the first hour of work and evening tea-break time for working adults. Both of the reasons indirectly supports that they might be visiting our portal during break time and hence the company can hold hourly sales during these periods.<br />
<br />
<br />
<br />
==Outcome==<br />
--></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_PD_Business_Intelligence_and_Analytics&diff=114785IS480 Team wiki: 2012T1 6-bit PD Business Intelligence and Analytics2012-12-05T07:15:15Z<p>Huiling.ong.2010: /* Analysis of User’s Facebook Persona */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #FE2E64; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:110%; text-align:center; color:#FE2E64" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams|<font color="#CD004E"><b>Technical Diagrams</b></font>]]<br />
<br />
| style="font-size:110%; text-align:center; color:#FE2E64" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype|<font color="#CD004E"><b>User Interface Prototype</b></font>]]<br />
<br />
| style="font-size:110%; text-align:center; color:#FE2E64" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_PD_Business_Intelligence_and_Analytics|<font color="#CD004E"><b>Business Intelligence and Analytics</b></font>]]<br />
|}<br />
<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang Benchmark</font></div>=<br />
CodeIgniter has a Benchmarking class that is always active, enabling the time difference between any two marked points to be calculated. In addition, the benchmark is always started the moment the framework is invoked, and ended by the output class right before sending the final view to the browser, enabling a very accurate timing of the entire system execution to be shown.<br />
<br><br><br />
Chapalang Benchmark is a custom tool developed with the foundation of CodeIgniter’s Benchmarking class. Additional customization has been made to reflect extended measurement of execution for process-based series of activities, integrated with a database table to support other analytical execution.<br />
==Audit Trail==<br />
One of the purpose of Chapalang Benchmark is to support an audit trail on the activities performed by users on Chapalang!. The tool collects the following set of data:<br />
* Member ID<br />
* Controller<br />
* Controller method<br />
* URL<br />
* Start timestamp<br />
* End timestamp<br />
* Elapsed time<br />
By having Chapalang Benchmark to support an audit trail, we are able to trace the series of activities performed by a specific user on our system, given any time period. <br />
<br><br><br />
While it may not be friendly to the privacy of users, and not efficient to design models customized to a specific user, it is useful to use the activity data collected to support advance analytics. At this stage, the data acts as a complementary operational data source for our analytics behind the Personalized Dashboard.<br />
<br><br><br />
There are other usefulness of the activity data to discover system anomalies, user experiences, and more. Some examples are further elaborated below. <br />
<!-- <br />
==Sample stored operations==<br />
--><br />
<!-- <br />
==Findings from Chapalang Benchmark==<br />
--><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang Analytics</font></div>=<br />
==Purpose==<br />
The purpose of Chapalang Analytics is primarily to support the low-level function, Personalized Dashboard of the portal. While that is the only application of Chapalang Analytics at this stage, it can be further expanded into other data-driven and user-oriented features which include but not limited to, target advertising and content filtering.<br />
==Operational Data Source==<br />
The analytics will make use of the following data:<br />
* Facebook statuses, likes, post times, friends, gender, birthday, relationship status<br />
* Chapalang Benchmark, which collects data on all user activities on Chapalang!, such as browsing history and past purchases<br />
* Sentimental database, containing a list of words that characterises user’s personality and behaviour<br />
==Analytical Techniques==<br />
The analytics will make use of the following techniques:<br />
* Semantic Analytics<br />
* Sentimental Analytics<br />
* Rule-based Analytics<br />
==Analysis of User’s Facebook Persona==<br />
The first analytical step of Chapalang Analytics is to analyse a user’s Facebook persona. Through the analysis of the user-specific ODS, we will identify certain characteristics of a user.<br />
<br><br />
===Discoveries from Chapalang Benchmark===<br />
As we analyse the data from Chapalang Benchmark, there are some interesting discoveries that would otherwise be hidden or unknown to us.<br />
====Inconsistent elapsed time for view_product page====<br />
Despite using the same set of application files, the elapsed time for different products is different. We have some product pages which take as long as varying 15-30 seconds to load, while the rest are mostly under our acceptable response time of 3 seconds. Though we have yet to isolate the cause and find a permanent solution, the discovery will help us identify problems like these which may not be reported by users lead to a reduction in returning visitors.<br />
====Electronic products are most interesting to visitors====<br />
As we run more analysis, we realized that electronic products are most interesting to visitors because 87% of our visitors will view at 2 or more electronics products. They also spend longer time on electronics product pages than other pages on the portal. This might be useful for the company to offer more electronic goods deals, promotions or marketing.<br />
====Most traffic comes early in the morning and evening====<br />
From Chapalang Benchmark data, we also noticed a trend that most visitors, both registered and unregistered, visit our portal between 9am and 10am, and 3pm to 4pm. We are speculating that this might be because we have a user base consisting of SMU students and young working adults. The time window matches approximately the start time of classes in the morning and evening sessions. Also, it appears to be the first hour of work and evening tea-break time for working adults. Both of the reasons indirectly supports that they might be visiting our portal during break time and hence the company can hold hourly sales during these periods.<br />
<br />
==Model for Personalized Dashboard==<br />
<br />
==Outcome==<br />
--></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4&diff=114784IS480 Team wiki: 2012T1 6-bit Project Management UT42012-12-05T07:13:08Z<p>Huiling.ong.2010: /* Scalability & Performance Test */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule</font></div>=<br />
==Planned Schedule==<br />
[[Image:6-bit_ScheduleDiagramOverview.png|left|750px|link=""]]<br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
==Meeting Minutes==<br />
===Team Meeting Minutes===<br />
{|<br />
|[[https://docs.google.com/document/d/1nHl51M2qzY4gynJ8tVR6wKqV_lWtJtncl3nbESSnQvU/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]]<br />
|[[https://docs.google.com/document/d/129JDPU8l7PbX-JjferJ-J83JXSIAo5-cXM4_Odw3o5c/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]]<br />
|[[https://docs.google.com/document/d/1BPn6a-XMMAN18TbdlDER27f8Eleb8sUJhcas1bgDOQI/edit |<font color="#CD004E"><b>Meeting Minute 21</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LtSANlI6pDyV_PpGDAVg85PjFVKmDmWWnYC5lXAHh68/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qx6hX462uQDEfwiB3r3ee71eTKaPXSArCZS7y1TOWA4/edit |<font color="#CD004E"><b>Meeting Minute 12</b></font>]]<br />
|[[https://docs.google.com/document/d/1IdjkCbomLgszePgImX2XsTeUHX54e54xRTIjjFoZM6g/edit |<font color="#CD004E"><b>Meeting Minute 22</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/11lQzKaddghH7FHACcTnPQDJnE6ZaScT8Q8nU2YvH8gU/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]]<br />
|[[https://docs.google.com/document/d/1HPdXr28aTDK-RmijqPYTLG1iCUv-JbpkIJ8zzgzTplg/edit |<font color="#CD004E"><b>Meeting Minute 13</b></font>]]<br />
|[[https://docs.google.com/document/d/1gMoTceQakeT42-FO0duVxRajea2hJAUVw8Eu1AfqtfY/edit |<font color="#CD004E"><b>Meeting Minute 23</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1gZuhKW-QMbhUR_oh6Ty8EE17JTYkTFkWCfG6UHrU7-c/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]]<br />
|[[https://docs.google.com/document/d/1ii-ZenbOTZR9drEQCFJ4hX8raXvpgufELaZY80M2GYI/edit |<font color="#CD004E"><b>Meeting Minute 14</b></font>]]<br />
|[[https://docs.google.com/document/d/12vYfm8jo9c2eZ3VwnL2z6vn6l__D6heDhCHdEWVPg4I/edit |<font color="#CD004E"><b>Meeting Minute 24</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1H-8fODLc79U6-IXScSfemjRLOyjvzC6_k0aig6BDcBY/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]]<br />
|[[https://docs.google.com/document/d/1I3qlvujdLVmY_L22VMsKrtISIFI5CnxmtZnMNdJdxfc/edit |<font color="#CD004E"><b>Meeting Minute 15</b></font>]]<br />
|[[https://docs.google.com/document/d/1jPIW-xe7p6kjzGF_YMmk0K2mPzWil1zUfBQOwGc8wRk/edit |<font color="#CD004E"><b>Meeting Minute 25</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Qx4jdRZoE8hXv3u1R4dWke5b-kyMxIc7ASzPIh4ShRQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]]<br />
|[[https://docs.google.com/document/d/1Pcd6ZADI7ZEuXzq3exrss4nJQhotxAq7-ENfy_OVs6o/edit |<font color="#CD004E"><b>Meeting Minute 16</b></font>]]<br />
|[[https://docs.google.com/document/d/1NDCoF37ckdhbys57BLEXShcAcraxzOKpoNbFvpWWUQM/edit |<font color="#CD004E"><b>Meeting Minute 26</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1uSkv_cux0PqnRTKS-w72wQLgL1ZKaCpXhzDm5uamfMU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]]<br />
|[[https://docs.google.com/document/d/12jW-ycBkfivYL2pg7nrVvb9SF7_XmiglVGGnWAjp6uQ/edit |<font color="#CD004E"><b>Meeting Minute 17</b></font>]]<br />
|[[https://docs.google.com/document/d/1Amo6YgCkVA3YD-iqyIxhyG8embuClo50KXsznVgoWQE/edit |<font color="#CD004E"><b>Meeting Minute 27</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1pTivyZ9D3jSU1Kf5VoW4-Xl_C9Abg-fL_6SI6GP_hz0/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qbhow5u8GsE42hr9b8o1S2HNeJfG5PTX24W70ZHyCfI/edit |<font color="#CD004E"><b>Meeting Minute 18</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LTLnY5JN2EfiU9drp3d7zGmoCxsSYr1nL4UMvwfXDdU/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]]<br />
|[[https://docs.google.com/document/d/1fbnoWNTimFyUC01lgeblvVCLTySS8Ik2JU_wdZ656RU/edit |<font color="#CD004E"><b>Meeting Minute 19</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Nlo5hnsYbfh4dFSnfsV6Wyv5nxJsmDWF8ZMFKFA9Pac/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]]<br />
|[[https://docs.google.com/document/d/1o1zVXcdHaXCLNzS9rHq528rLEmXMFl3df3ffTFLMtho/edit |<font color="#CD004E"><b>Meeting Minute 20</b></font>]]<br />
|}<br />
<br />
===Supervisor Meeting Minutes===<br />
[https://docs.google.com/document/d/1iuSvaC9Wu-v7dToRp41IwmpdpQ0KtSTJIgpabmiolXQ/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1rXJuYE684ZpYbRyHknn4pmLpJZ9Y5o01QaJT34TD0gY/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1Gy7TOJr9aeyd8pcU_loabY1l3NByVm3nVKqOQnnJRbM/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1DGrSXaCTOtRL_iSOaOI_mHC2DOS7z4Vi6clzomkGkcI/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1VLEizDPdae_enbEtoHo9IGPM4-k9JXe7RFJ1hhiDTBA/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/13MyE--Ymz-dNiQPvgCjGutL23JZwotnoIPlYw7QqmXQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1UUDCW8YMttW2rwAxLJhSfqccBdedYoofVskc9qerIxU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/17QEpHsvitqzO9BO9MkB42umN3_9k6Useli4N2fYoCNU/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1masrY10EdoXrAdwmTnW-POF0RVEYGeHbOorf-0EEC-0/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1u2jcuwSkGqk4lGcGdF4UriFgzT9dNgNAb1ekERDvitQ/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1eHVDrzwLxkGhrElcgPUOWhcQBwLdGdXcmCVvT_u-Va8/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]<br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Testing</font></div>=<br />
==Test Cases==<br />
[https://dl.dropbox.com/u/56071797/Test%20Cases.docx |<font color="#CD004E"><b>Test Cases</b></font>]<br />
<br />
==Test Plans==<br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2001_17_10_2012.docx <font color="#CD004E"><b>Test Plan 1 ''on 17 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2002_28_09_2012.docx <font color="#CD004E"><b>Test Plan 2 ''on 28 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2003_19_10_2012.docx <font color="#CD004E"><b>Test Plan 3 ''on 19 October 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2004_01_11_2012.docx <font color="#CD004E"><b>Test Plan 4 ''on 4 November 2012''</b></font>]<br />
<br />
==User Testing==<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #728FCE; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing|<font color="#CD004E"><b>User Testing 1</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing|<font color="#CD004E"><b>User Testing 2</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing|<font color="#CD004E"><b>User Testing 3</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing|<font color="#CD004E"><b>User Testing 4</b></font>]]<br />
<br />
|}<br />
===User Testing 4===<br />
[[Image:6bituser-testing4.png]]<br />
<br />
====Test Description====<br />
The objective of User Test 4 is on scalability, performance and analytics testing of the system. This is a 2-part test session, firstly on scalability and performance which does not require physical testers, and secondly on inter-rater reliability which requires rating judges.<br />
<br><br><br />
The coverage of the scalability and performance test is focused on the bottleneck functions, which are the discussion forums and marketplace. The terms “performance” and “scalability” are commonly used interchangeably, but the two are distinct: performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. <br />
<br><br><br />
Additionally, Inter-Rater Reliability Test is performed on the Personalized Dashboard to determine the concordance of the personalized results and actual personality of user stereotypes.<br />
<br />
====Testers Background====<br />
=====Scalability & Performance Testing=====<br />
As the test does not require physical testers, the following appends the test environment.<br><br />
[[Image:6-bit_ut4spec.png|400px]]<br />
<br />
=====Inter-Rater Reliability Test=====<br />
Testers will assume the role of raters or judges for our Inter-Rater Reliability Test, represented by a total of 20 people with a 50-50 male is to female ratio. Testers are stratified from a diverse background, intended to represent personality stereotypes designed.<br />
<br><br><br />
Personality stereotypes include characteristics such as gender, age group, education, personality traits, online activity, mobility and interested topics.<br />
<br />
====Test Groups====<br />
There is no test grouping employed in this test.<br />
<br />
====Test Procedures====<br />
=====Scalability & Performance Testing=====<br />
The first part of the test is on scalability and performance testing. Chapalang Benchmark is configured to measure the time taken for each controller method before it starts and as soon as it ends. The results will be used to study the performance of the system and application at different scales of operations. <br />
<br><br><br />
Additionally, custom application is used to perform a series of activities on a forum and marketplace, simulating an arbitrary number of concurrent users on the system, or the load. <br />
<br><br />
<br><br />
Subsequently, we will study the benchmark timing data to understand the performance differences under different load.<br />
=====Inter-Rater Reliability Test=====<br />
An Inter-Rater Reliability (IRR) is the degree of agreement among raters. It gives a score of how much homogeneity or consensus there is in the ratings given by judges.<br />
<br><br><br />
The first rater is the system itself, which will generate a list of 10 products and 10 discussion topics recommendations in descending order of relevance to a target user. Every recommendation is tied to a specific and distinct order number.<br />
<br><br><br />
The second rater is a human tester, who will be provided with the same list of 10 products and 10 discussion topics generated by the system in relevance to him or herself. To mitigate the effects of Experimenter’s Bias, the order of each item is unordered and randomized without any intended logic. The second rater is expected to reorder the items according to his or her preferences in descending order.<br />
<br><br><br />
Subsequently, we will make use of Spearman’s Rank Correlation Coefficient to understand the reliability of our personalized dashboard which features product and topic recommendations.<br />
<br />
====Test Instruction====<br />
=====Inter-Rater Reliability Test=====<br />
This is a sample output of the first rater, for a product recommendation test.<br />
<br><br />
[[Image:6-bit_ut4a.png|750px]]<br />
<br><br />
This is a sample input sheet for the second rater, on product recommendation test.<br />
<br><br />
[[Image:6-bit_ut4b.png|750px]]<br />
<br><br />
In a descending order, 1 represents the most relevant item while 10 represents the least relevant item.<br />
<br />
====Test Results====<br />
=====Scalability & Performance Test=====<br />
The terms “performance” and “scalability” are commonly used interchangeably, but the two are distinct: performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. <br />
*(a) Identification of activities<br />
[[Image:ChapalangA.png|300px]]<br />
*(b) Identification of bottleneck<br />
Based on the table above, we have identified that if a user experience is sequential, “Display single product” page has the longest elapsed time. At the same time, it has the longest elapsed time by itself, when compared to all the functions. Hence, we have identified this activity as the bottleneck.<br />
*(c) Measurement Performance<br />
Referring to the same table above, we have determined the average of 5 tests on the “Display single product” activity for 1 concurrent user to have an elapsed time of 1.76997 seconds. Due to natural variation of the recorded timing, we will adopt 2 seconds as the performance upper limit.<br />
<br><br />
[[Image:ChapalangC.png|600px]]<br />
*(d) Scalability<br />
We will now attempt to find out the maximum number of concurrent users that the system is able to support, given the performance of a single concurrent user. If we assume the performance upper limit to be 2 seconds, there is an estimated number of 16 concurrent users which has performed 2 seconds of lower.<br />
*(e) Results of up to 300 concurrent users<br />
Performing further tests based on the markers of up to 300 concurrent users with 25-user intervals, for the purpose of intentionally simulating a load on the server to observe its deterioration in performance, if any. <br />
<br><br><br />
Firstly, we have determined an arbitrary of acceptable performance of 3 seconds elapsed time for optimal user experience. Given this benchmark, we can observe that the system is capable of supporting up to 25 concurrent users.<br />
<br><br><br />
Secondly, we have also observed peak deterioration in the trend line till approximately 75 users before the elapsed time for 100 concurrent users actually improved and reduced. The performance improved till approximately 200 concurrent users before it begins deterioration again. This is an unexpected and unusual observation for the team. With further consultation with technical experts, there are a variety of reasons which may lead to this anomaly. It could be due to simple outliers in our data, or it could be the use of swap memory on a Linux system (equivalent to pagination in Windows), and it could also be the nature of a switching between threading and non-threading operations of an apache web server.<br />
<br><br><br />
Thirdly, the test crashed after approximately 260 concurrent connections. However, MySQL was still running but apache requires a reboot. Investigating into the log files, we understood that the MaxClient in our apache configuration is 256 and hence it is natural for it to fail. In addition, we found many forked and unreleased processes in the Linux server, which could have been further improved with system-level adjustments.<br />
<br />
<br />
<br><br><br><br />
While the test shows that our system is capable of supporting 25 concurrent users within our acceptable performance, there are several variables in the circumstances that may limit the validity of this test result. Network performance is one key variable that can directly affect a user’s actual experience. <br />
Other limitations of the test include:<br />
* A standard MySQL is setup to handle 100 concurrent connections. For the purpose of test, we have lifted this limit.<br />
* Actual operations on the server consist of multiple concurrent connections on different pages, which make different SQL calls. The results above are limited because it tests on a single bottleneck controller, which locks a table and executes before it releases for the next process to perform. Hence, the elapsed time will be incurred exponentially which is rarely the case in real situations. As such, the above results may be pessimistic.<br />
* A server’s performance is also limited to a standard Apache non-threaded setup which serves 256 concurrent users using the mod_prefork module.<br />
Even though the test result is not conclusive, it is sufficient for us to have a reasonable assumption that the server and application is capable of scaling up to 50 concurrent users while maintaining the same performance, and handling a load of approximately 25 concurrent users before suffering sub-optimal performance deterioration.<br />
<br />
=====Inter-Rater Reliability Test=====<br />
In order to evaluate the test results, we rely on the statistical model called Spearman’s Rank Correlation Coefficient (SRCC). The model is appended below:<br />
<br><br />
[[Image: 6bituser-testing4formula.png]]<br />
<br><br />
In short, the SRCC model takes into account the rank rating from 2 different raters, represented by xi and yi respectively. In conventional Correlation of determination model, it takes in absolute data instead to find out statistical and data-driven correlation between 2 inputs. <br />
<br><br />
<br><br />
However, we are interested in the consensus between human judgment on the data, therefore SRCC is a suitable model of analysis. <br />
The SRCC model assumes that the rating scale is ordinal, or basically serial scale of rating. This assumption is aligned with our 1 – 10 rating score which is incremental and serial. Additionally, the SRCC model considers only relative position of the ratings. For example, (1, 2, 1, 3) is considered perfectly correlated with (2, 3, 2, 4). This is acceptable in our test because each rating in our test is distinct and exhaustive, where no repeats or unused score is allowed.<br />
<br> <br><br />
The following is a sample of data tabulation in visual form.<br />
<br><br />
[[Image: 6bituser-testing4z.png]]<br />
<br><br />
With [[Image: 6bituser-testing4di2.png]] found, we can add them to find [[Image: 6bituser-testing4sumdi2.png]] 28. The value of n is 10. So these values can now be substituted back into the equation, we evaluate that p = 0.83.<br />
<br><br />
Based on the nature of correlation coefficient value p, it has a range between -1 to 1. Here are some of the characteristics of the p value.<br />
<br><br />
* A negative number suggests negative relationship, <br />
* A positive number suggests positive relationship, <br />
* A size of a positive or negative number closer to 1 or -1 suggests strength of relationship,<br />
* and A p value of 0 suggests an absolute lack of relationship in the input attributes.<br />
<br />
It should be noted that if there is a strongly negative correlation, it may suggest a reversal in the order of recommendations in our system may eventually become an ideal model.<br />
<br><br />
The accuracy sentimental analysis system is, in principle, how well it agrees with human judgment, despite the fact that the applied accuracy in our test is to ensure an optimal user experience and optimal sales exposure. <br><br />
However, the limitation of the model is that human raters typically agree about 70% of the time and even if a system is 100% accurate by assumption, humans will still disagree about 30% of the time. Hence, for the purpose of our study, it may be suggested that an application with 100% human agreeableness can only be statistically justified to be 70% accurate and more sophisticated methods should be used to endorse the remaining 30% of accuracy. <br><br><br />
After conducting the IRR Test, the results are tabulated and appended as follows.<br />
<br><br />
[[Image: 6bituser-testing4results.png]]<br />
<br><br />
Tester IDs that begins with M denotes male testers, while F denotes Female testers. The categorization of results will help us understand a basic level of stereotyping accuracy by gender. If need it, the results can be further drilled down to represent a more specific personality stereotype.<br />
<br><br><br />
Summarising the test results tabulated above, the average for median p-value for male is 0.8695 and median p-value for female is 0.8675. Based on the median values, there is no significant difference in accuracy for male and females. In addition, it is satisfactorily justified that there is a strong positive correlation between the recommendations of our system and the preferences of the testers, a sample from our potential users, based on their consensus.<br />
<br />
<br />
<br />
<br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Milestones</font></div>=<br />
<br />
[[Image:6-bit_schedule.png|600px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule Metric</font></div>=<br />
Every iteration, schedule metric values are calculated to understand the project progress. They are broadly categorized into 5 different groups, where different action plans will apply. The acceptable range of value is within 90% to 110%, offering some buffer for natural inaccuracies between forecasting and execution.<br />
<br><br><br />
Total Schedule Metric Value = Planned no. of days taken (P) / Actual no. of Days Assigned (A) x 100%<br />
<br><br><br />
[[Image:6-bit_schedulemetric.png|center|600px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Bug Metric</font></div>=<br />
==Log==<br />
[[Image:6-bit_BugMetric.png|550px]]<br />
[[Image:6-bit_BugLog.png|600px]]<br />
<div style="text-align: right;"><br />
Bug Log: [https://docs.google.com/spreadsheet/ccc?key=0Aqd6IiSLbMwQdEI5TldNSEhpcVRjb1puYzU3ZHJOckE |<font color="#CD004E"><b>Click Here</b></font>]<br />
</div><br />
<br><br />
Bug logging for Chapalang! takes the direction of being practical and easily monitored from both macro and micro perspectives. Whenever a bug is found, a new row is entered with the following data:<br />
* Index number<br />
* Bug description<br />
* Found by<br />
* Found date<br />
* Expected solve-by date<br />
* Bug severity<br />
* Status<br />
* Owner of the function<br />
* Fixed date<br />
* Closed by (Tester)<br />
* Close date<br />
* Additional comments<br />
==Metric==<br />
Bugs are classified into 3 different categories of complexity, easy, moderate and hard. Each category is assigned points of 1, 5 and 10 respectively, lower is better.<br />
<br><br><br />
Total Points for Each Iteration = Σ Points of the Bugs in each iteration<br />
<br><br />
[[Image:6-bit_BugMetricFormula.png|500px|center]]<br />
<br><br />
After assigning each bug with points associated by its complexity, we will track the total bug scores at the end of each week before deciding if there should be any actions to be taken. The following is an action plan for our bug metric:<br />
<br><br />
[[Image:6-bit_BugMetricFormula2.png|500px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Risk & Mitigation</font></div>=<br />
<br><br />
[[Image:6-bit_RiskDiagram.png|600px]]<br />
<br><br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4&diff=114783IS480 Team wiki: 2012T1 6-bit Project Management UT42012-12-05T07:12:24Z<p>Huiling.ong.2010: /* Scalability & Performance Test */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule</font></div>=<br />
==Planned Schedule==<br />
[[Image:6-bit_ScheduleDiagramOverview.png|left|750px|link=""]]<br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
==Meeting Minutes==<br />
===Team Meeting Minutes===<br />
{|<br />
|[[https://docs.google.com/document/d/1nHl51M2qzY4gynJ8tVR6wKqV_lWtJtncl3nbESSnQvU/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]]<br />
|[[https://docs.google.com/document/d/129JDPU8l7PbX-JjferJ-J83JXSIAo5-cXM4_Odw3o5c/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]]<br />
|[[https://docs.google.com/document/d/1BPn6a-XMMAN18TbdlDER27f8Eleb8sUJhcas1bgDOQI/edit |<font color="#CD004E"><b>Meeting Minute 21</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LtSANlI6pDyV_PpGDAVg85PjFVKmDmWWnYC5lXAHh68/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qx6hX462uQDEfwiB3r3ee71eTKaPXSArCZS7y1TOWA4/edit |<font color="#CD004E"><b>Meeting Minute 12</b></font>]]<br />
|[[https://docs.google.com/document/d/1IdjkCbomLgszePgImX2XsTeUHX54e54xRTIjjFoZM6g/edit |<font color="#CD004E"><b>Meeting Minute 22</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/11lQzKaddghH7FHACcTnPQDJnE6ZaScT8Q8nU2YvH8gU/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]]<br />
|[[https://docs.google.com/document/d/1HPdXr28aTDK-RmijqPYTLG1iCUv-JbpkIJ8zzgzTplg/edit |<font color="#CD004E"><b>Meeting Minute 13</b></font>]]<br />
|[[https://docs.google.com/document/d/1gMoTceQakeT42-FO0duVxRajea2hJAUVw8Eu1AfqtfY/edit |<font color="#CD004E"><b>Meeting Minute 23</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1gZuhKW-QMbhUR_oh6Ty8EE17JTYkTFkWCfG6UHrU7-c/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]]<br />
|[[https://docs.google.com/document/d/1ii-ZenbOTZR9drEQCFJ4hX8raXvpgufELaZY80M2GYI/edit |<font color="#CD004E"><b>Meeting Minute 14</b></font>]]<br />
|[[https://docs.google.com/document/d/12vYfm8jo9c2eZ3VwnL2z6vn6l__D6heDhCHdEWVPg4I/edit |<font color="#CD004E"><b>Meeting Minute 24</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1H-8fODLc79U6-IXScSfemjRLOyjvzC6_k0aig6BDcBY/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]]<br />
|[[https://docs.google.com/document/d/1I3qlvujdLVmY_L22VMsKrtISIFI5CnxmtZnMNdJdxfc/edit |<font color="#CD004E"><b>Meeting Minute 15</b></font>]]<br />
|[[https://docs.google.com/document/d/1jPIW-xe7p6kjzGF_YMmk0K2mPzWil1zUfBQOwGc8wRk/edit |<font color="#CD004E"><b>Meeting Minute 25</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Qx4jdRZoE8hXv3u1R4dWke5b-kyMxIc7ASzPIh4ShRQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]]<br />
|[[https://docs.google.com/document/d/1Pcd6ZADI7ZEuXzq3exrss4nJQhotxAq7-ENfy_OVs6o/edit |<font color="#CD004E"><b>Meeting Minute 16</b></font>]]<br />
|[[https://docs.google.com/document/d/1NDCoF37ckdhbys57BLEXShcAcraxzOKpoNbFvpWWUQM/edit |<font color="#CD004E"><b>Meeting Minute 26</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1uSkv_cux0PqnRTKS-w72wQLgL1ZKaCpXhzDm5uamfMU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]]<br />
|[[https://docs.google.com/document/d/12jW-ycBkfivYL2pg7nrVvb9SF7_XmiglVGGnWAjp6uQ/edit |<font color="#CD004E"><b>Meeting Minute 17</b></font>]]<br />
|[[https://docs.google.com/document/d/1Amo6YgCkVA3YD-iqyIxhyG8embuClo50KXsznVgoWQE/edit |<font color="#CD004E"><b>Meeting Minute 27</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1pTivyZ9D3jSU1Kf5VoW4-Xl_C9Abg-fL_6SI6GP_hz0/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qbhow5u8GsE42hr9b8o1S2HNeJfG5PTX24W70ZHyCfI/edit |<font color="#CD004E"><b>Meeting Minute 18</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LTLnY5JN2EfiU9drp3d7zGmoCxsSYr1nL4UMvwfXDdU/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]]<br />
|[[https://docs.google.com/document/d/1fbnoWNTimFyUC01lgeblvVCLTySS8Ik2JU_wdZ656RU/edit |<font color="#CD004E"><b>Meeting Minute 19</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Nlo5hnsYbfh4dFSnfsV6Wyv5nxJsmDWF8ZMFKFA9Pac/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]]<br />
|[[https://docs.google.com/document/d/1o1zVXcdHaXCLNzS9rHq528rLEmXMFl3df3ffTFLMtho/edit |<font color="#CD004E"><b>Meeting Minute 20</b></font>]]<br />
|}<br />
<br />
===Supervisor Meeting Minutes===<br />
[https://docs.google.com/document/d/1iuSvaC9Wu-v7dToRp41IwmpdpQ0KtSTJIgpabmiolXQ/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1rXJuYE684ZpYbRyHknn4pmLpJZ9Y5o01QaJT34TD0gY/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1Gy7TOJr9aeyd8pcU_loabY1l3NByVm3nVKqOQnnJRbM/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1DGrSXaCTOtRL_iSOaOI_mHC2DOS7z4Vi6clzomkGkcI/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1VLEizDPdae_enbEtoHo9IGPM4-k9JXe7RFJ1hhiDTBA/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/13MyE--Ymz-dNiQPvgCjGutL23JZwotnoIPlYw7QqmXQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1UUDCW8YMttW2rwAxLJhSfqccBdedYoofVskc9qerIxU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/17QEpHsvitqzO9BO9MkB42umN3_9k6Useli4N2fYoCNU/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1masrY10EdoXrAdwmTnW-POF0RVEYGeHbOorf-0EEC-0/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1u2jcuwSkGqk4lGcGdF4UriFgzT9dNgNAb1ekERDvitQ/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1eHVDrzwLxkGhrElcgPUOWhcQBwLdGdXcmCVvT_u-Va8/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]<br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Testing</font></div>=<br />
==Test Cases==<br />
[https://dl.dropbox.com/u/56071797/Test%20Cases.docx |<font color="#CD004E"><b>Test Cases</b></font>]<br />
<br />
==Test Plans==<br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2001_17_10_2012.docx <font color="#CD004E"><b>Test Plan 1 ''on 17 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2002_28_09_2012.docx <font color="#CD004E"><b>Test Plan 2 ''on 28 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2003_19_10_2012.docx <font color="#CD004E"><b>Test Plan 3 ''on 19 October 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2004_01_11_2012.docx <font color="#CD004E"><b>Test Plan 4 ''on 4 November 2012''</b></font>]<br />
<br />
==User Testing==<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #728FCE; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing|<font color="#CD004E"><b>User Testing 1</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing|<font color="#CD004E"><b>User Testing 2</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing|<font color="#CD004E"><b>User Testing 3</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing|<font color="#CD004E"><b>User Testing 4</b></font>]]<br />
<br />
|}<br />
===User Testing 4===<br />
[[Image:6bituser-testing4.png]]<br />
<br />
====Test Description====<br />
The objective of User Test 4 is on scalability, performance and analytics testing of the system. This is a 2-part test session, firstly on scalability and performance which does not require physical testers, and secondly on inter-rater reliability which requires rating judges.<br />
<br><br><br />
The coverage of the scalability and performance test is focused on the bottleneck functions, which are the discussion forums and marketplace. The terms “performance” and “scalability” are commonly used interchangeably, but the two are distinct: performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. <br />
<br><br><br />
Additionally, Inter-Rater Reliability Test is performed on the Personalized Dashboard to determine the concordance of the personalized results and actual personality of user stereotypes.<br />
<br />
====Testers Background====<br />
=====Scalability & Performance Testing=====<br />
As the test does not require physical testers, the following appends the test environment.<br><br />
[[Image:6-bit_ut4spec.png|400px]]<br />
<br />
=====Inter-Rater Reliability Test=====<br />
Testers will assume the role of raters or judges for our Inter-Rater Reliability Test, represented by a total of 20 people with a 50-50 male is to female ratio. Testers are stratified from a diverse background, intended to represent personality stereotypes designed.<br />
<br><br><br />
Personality stereotypes include characteristics such as gender, age group, education, personality traits, online activity, mobility and interested topics.<br />
<br />
====Test Groups====<br />
There is no test grouping employed in this test.<br />
<br />
====Test Procedures====<br />
=====Scalability & Performance Testing=====<br />
The first part of the test is on scalability and performance testing. Chapalang Benchmark is configured to measure the time taken for each controller method before it starts and as soon as it ends. The results will be used to study the performance of the system and application at different scales of operations. <br />
<br><br><br />
Additionally, custom application is used to perform a series of activities on a forum and marketplace, simulating an arbitrary number of concurrent users on the system, or the load. <br />
<br><br />
<br><br />
Subsequently, we will study the benchmark timing data to understand the performance differences under different load.<br />
=====Inter-Rater Reliability Test=====<br />
An Inter-Rater Reliability (IRR) is the degree of agreement among raters. It gives a score of how much homogeneity or consensus there is in the ratings given by judges.<br />
<br><br><br />
The first rater is the system itself, which will generate a list of 10 products and 10 discussion topics recommendations in descending order of relevance to a target user. Every recommendation is tied to a specific and distinct order number.<br />
<br><br><br />
The second rater is a human tester, who will be provided with the same list of 10 products and 10 discussion topics generated by the system in relevance to him or herself. To mitigate the effects of Experimenter’s Bias, the order of each item is unordered and randomized without any intended logic. The second rater is expected to reorder the items according to his or her preferences in descending order.<br />
<br><br><br />
Subsequently, we will make use of Spearman’s Rank Correlation Coefficient to understand the reliability of our personalized dashboard which features product and topic recommendations.<br />
<br />
====Test Instruction====<br />
=====Inter-Rater Reliability Test=====<br />
This is a sample output of the first rater, for a product recommendation test.<br />
<br><br />
[[Image:6-bit_ut4a.png|750px]]<br />
<br><br />
This is a sample input sheet for the second rater, on product recommendation test.<br />
<br><br />
[[Image:6-bit_ut4b.png|750px]]<br />
<br><br />
In a descending order, 1 represents the most relevant item while 10 represents the least relevant item.<br />
<br />
====Test Results====<br />
=====Scalability & Performance Test=====<br />
The terms “performance” and “scalability” are commonly used interchangeably, but the two are distinct: performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. <br />
*(a) Identification of activities<br />
[[Image:ChapalangA.png|300px]]<br />
*(b) Identification of bottleneck<br />
Based on the table above, we have identified that if a user experience is sequential, “Display single product” page has the longest elapsed time. At the same time, it has the longest elapsed time by itself, when compared to all the functions. Hence, we have identified this activity as the bottleneck.<br />
*(c) Measurement Performance<br />
Referring to the same table above, we have determined the average of 5 tests on the “Display single product” activity for 1 concurrent user to have an elapsed time of 1.76997 seconds. Due to natural variation of the recorded timing, we will adopt 2 seconds as the performance upper limit.<br />
<br><br />
[[Image:ChapalangC.png|600px]]<br />
*(d) Scalability<br />
We will now attempt to find out the maximum number of concurrent users that the system is able to support, given the performance of a single concurrent user. If we assume the performance upper limit to be 2 seconds, there is an estimated number of 16 concurrent users which has performed 2 seconds of lower.<br />
*(e) Results of up to 300 concurrent users<br />
Performing further tests based on the markers of up to 300 concurrent users with 25-user intervals, for the purpose of intentionally simulating a load on the server to observe its deterioration in performance, if any. <br />
<br><br><br />
Firstly, we have determined an arbitrary of acceptable performance of 3 seconds elapsed time for optimal user experience. Given this benchmark, we can observe that the system is capable of supporting up to 25 concurrent users.<br />
<br><br><br />
Secondly, we have also observed peak deterioration in the trend line till approximately 75 users before the elapsed time for 100 concurrent users actually improved and reduced. The performance improved till approximately 200 concurrent users before it begins deterioration again. This is an unexpected and unusual observation for the team. With further consultation with technical experts, there are a variety of reasons which may lead to this anomaly. It could be due to simple outliers in our data, or it could be the use of swap memory on a Linux system (equivalent to pagination in Windows), and it could also be the nature of a switching between threading and non-threading operations of an apache web server.<br />
<br><br><br />
Thirdly, the test crashed after approximately 260 concurrent connections. However, MySQL was still running but apache requires a reboot. Investigating into the log files, we understood that the MaxClient in our apache configuration is 256 and hence it is natural for it to fail. In addition, we found many forked and unreleased processes in the Linux server, which could have been further improved with system-level adjustments.<br />
<br />
=====Inter-Rater Reliability Test=====<br />
In order to evaluate the test results, we rely on the statistical model called Spearman’s Rank Correlation Coefficient (SRCC). The model is appended below:<br />
<br><br />
[[Image: 6bituser-testing4formula.png]]<br />
<br><br />
In short, the SRCC model takes into account the rank rating from 2 different raters, represented by xi and yi respectively. In conventional Correlation of determination model, it takes in absolute data instead to find out statistical and data-driven correlation between 2 inputs. <br />
<br><br />
<br><br />
However, we are interested in the consensus between human judgment on the data, therefore SRCC is a suitable model of analysis. <br />
The SRCC model assumes that the rating scale is ordinal, or basically serial scale of rating. This assumption is aligned with our 1 – 10 rating score which is incremental and serial. Additionally, the SRCC model considers only relative position of the ratings. For example, (1, 2, 1, 3) is considered perfectly correlated with (2, 3, 2, 4). This is acceptable in our test because each rating in our test is distinct and exhaustive, where no repeats or unused score is allowed.<br />
<br> <br><br />
The following is a sample of data tabulation in visual form.<br />
<br><br />
[[Image: 6bituser-testing4z.png]]<br />
<br><br />
With [[Image: 6bituser-testing4di2.png]] found, we can add them to find [[Image: 6bituser-testing4sumdi2.png]] 28. The value of n is 10. So these values can now be substituted back into the equation, we evaluate that p = 0.83.<br />
<br><br />
Based on the nature of correlation coefficient value p, it has a range between -1 to 1. Here are some of the characteristics of the p value.<br />
<br><br />
* A negative number suggests negative relationship, <br />
* A positive number suggests positive relationship, <br />
* A size of a positive or negative number closer to 1 or -1 suggests strength of relationship,<br />
* and A p value of 0 suggests an absolute lack of relationship in the input attributes.<br />
<br />
It should be noted that if there is a strongly negative correlation, it may suggest a reversal in the order of recommendations in our system may eventually become an ideal model.<br />
<br><br />
The accuracy sentimental analysis system is, in principle, how well it agrees with human judgment, despite the fact that the applied accuracy in our test is to ensure an optimal user experience and optimal sales exposure. <br><br />
However, the limitation of the model is that human raters typically agree about 70% of the time and even if a system is 100% accurate by assumption, humans will still disagree about 30% of the time. Hence, for the purpose of our study, it may be suggested that an application with 100% human agreeableness can only be statistically justified to be 70% accurate and more sophisticated methods should be used to endorse the remaining 30% of accuracy. <br><br><br />
After conducting the IRR Test, the results are tabulated and appended as follows.<br />
<br><br />
[[Image: 6bituser-testing4results.png]]<br />
<br><br />
Tester IDs that begins with M denotes male testers, while F denotes Female testers. The categorization of results will help us understand a basic level of stereotyping accuracy by gender. If need it, the results can be further drilled down to represent a more specific personality stereotype.<br />
<br><br><br />
Summarising the test results tabulated above, the average for median p-value for male is 0.8695 and median p-value for female is 0.8675. Based on the median values, there is no significant difference in accuracy for male and females. In addition, it is satisfactorily justified that there is a strong positive correlation between the recommendations of our system and the preferences of the testers, a sample from our potential users, based on their consensus.<br />
<br />
<br />
<br />
<br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Milestones</font></div>=<br />
<br />
[[Image:6-bit_schedule.png|600px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule Metric</font></div>=<br />
Every iteration, schedule metric values are calculated to understand the project progress. They are broadly categorized into 5 different groups, where different action plans will apply. The acceptable range of value is within 90% to 110%, offering some buffer for natural inaccuracies between forecasting and execution.<br />
<br><br><br />
Total Schedule Metric Value = Planned no. of days taken (P) / Actual no. of Days Assigned (A) x 100%<br />
<br><br><br />
[[Image:6-bit_schedulemetric.png|center|600px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Bug Metric</font></div>=<br />
==Log==<br />
[[Image:6-bit_BugMetric.png|550px]]<br />
[[Image:6-bit_BugLog.png|600px]]<br />
<div style="text-align: right;"><br />
Bug Log: [https://docs.google.com/spreadsheet/ccc?key=0Aqd6IiSLbMwQdEI5TldNSEhpcVRjb1puYzU3ZHJOckE |<font color="#CD004E"><b>Click Here</b></font>]<br />
</div><br />
<br><br />
Bug logging for Chapalang! takes the direction of being practical and easily monitored from both macro and micro perspectives. Whenever a bug is found, a new row is entered with the following data:<br />
* Index number<br />
* Bug description<br />
* Found by<br />
* Found date<br />
* Expected solve-by date<br />
* Bug severity<br />
* Status<br />
* Owner of the function<br />
* Fixed date<br />
* Closed by (Tester)<br />
* Close date<br />
* Additional comments<br />
==Metric==<br />
Bugs are classified into 3 different categories of complexity, easy, moderate and hard. Each category is assigned points of 1, 5 and 10 respectively, lower is better.<br />
<br><br><br />
Total Points for Each Iteration = Σ Points of the Bugs in each iteration<br />
<br><br />
[[Image:6-bit_BugMetricFormula.png|500px|center]]<br />
<br><br />
After assigning each bug with points associated by its complexity, we will track the total bug scores at the end of each week before deciding if there should be any actions to be taken. The following is an action plan for our bug metric:<br />
<br><br />
[[Image:6-bit_BugMetricFormula2.png|500px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Risk & Mitigation</font></div>=<br />
<br><br />
[[Image:6-bit_RiskDiagram.png|600px]]<br />
<br><br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4&diff=114782IS480 Team wiki: 2012T1 6-bit Project Management UT42012-12-05T07:11:21Z<p>Huiling.ong.2010: /* Scalability & Performance Test */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule</font></div>=<br />
==Planned Schedule==<br />
[[Image:6-bit_ScheduleDiagramOverview.png|left|750px|link=""]]<br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
==Meeting Minutes==<br />
===Team Meeting Minutes===<br />
{|<br />
|[[https://docs.google.com/document/d/1nHl51M2qzY4gynJ8tVR6wKqV_lWtJtncl3nbESSnQvU/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]]<br />
|[[https://docs.google.com/document/d/129JDPU8l7PbX-JjferJ-J83JXSIAo5-cXM4_Odw3o5c/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]]<br />
|[[https://docs.google.com/document/d/1BPn6a-XMMAN18TbdlDER27f8Eleb8sUJhcas1bgDOQI/edit |<font color="#CD004E"><b>Meeting Minute 21</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LtSANlI6pDyV_PpGDAVg85PjFVKmDmWWnYC5lXAHh68/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qx6hX462uQDEfwiB3r3ee71eTKaPXSArCZS7y1TOWA4/edit |<font color="#CD004E"><b>Meeting Minute 12</b></font>]]<br />
|[[https://docs.google.com/document/d/1IdjkCbomLgszePgImX2XsTeUHX54e54xRTIjjFoZM6g/edit |<font color="#CD004E"><b>Meeting Minute 22</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/11lQzKaddghH7FHACcTnPQDJnE6ZaScT8Q8nU2YvH8gU/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]]<br />
|[[https://docs.google.com/document/d/1HPdXr28aTDK-RmijqPYTLG1iCUv-JbpkIJ8zzgzTplg/edit |<font color="#CD004E"><b>Meeting Minute 13</b></font>]]<br />
|[[https://docs.google.com/document/d/1gMoTceQakeT42-FO0duVxRajea2hJAUVw8Eu1AfqtfY/edit |<font color="#CD004E"><b>Meeting Minute 23</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1gZuhKW-QMbhUR_oh6Ty8EE17JTYkTFkWCfG6UHrU7-c/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]]<br />
|[[https://docs.google.com/document/d/1ii-ZenbOTZR9drEQCFJ4hX8raXvpgufELaZY80M2GYI/edit |<font color="#CD004E"><b>Meeting Minute 14</b></font>]]<br />
|[[https://docs.google.com/document/d/12vYfm8jo9c2eZ3VwnL2z6vn6l__D6heDhCHdEWVPg4I/edit |<font color="#CD004E"><b>Meeting Minute 24</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1H-8fODLc79U6-IXScSfemjRLOyjvzC6_k0aig6BDcBY/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]]<br />
|[[https://docs.google.com/document/d/1I3qlvujdLVmY_L22VMsKrtISIFI5CnxmtZnMNdJdxfc/edit |<font color="#CD004E"><b>Meeting Minute 15</b></font>]]<br />
|[[https://docs.google.com/document/d/1jPIW-xe7p6kjzGF_YMmk0K2mPzWil1zUfBQOwGc8wRk/edit |<font color="#CD004E"><b>Meeting Minute 25</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Qx4jdRZoE8hXv3u1R4dWke5b-kyMxIc7ASzPIh4ShRQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]]<br />
|[[https://docs.google.com/document/d/1Pcd6ZADI7ZEuXzq3exrss4nJQhotxAq7-ENfy_OVs6o/edit |<font color="#CD004E"><b>Meeting Minute 16</b></font>]]<br />
|[[https://docs.google.com/document/d/1NDCoF37ckdhbys57BLEXShcAcraxzOKpoNbFvpWWUQM/edit |<font color="#CD004E"><b>Meeting Minute 26</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1uSkv_cux0PqnRTKS-w72wQLgL1ZKaCpXhzDm5uamfMU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]]<br />
|[[https://docs.google.com/document/d/12jW-ycBkfivYL2pg7nrVvb9SF7_XmiglVGGnWAjp6uQ/edit |<font color="#CD004E"><b>Meeting Minute 17</b></font>]]<br />
|[[https://docs.google.com/document/d/1Amo6YgCkVA3YD-iqyIxhyG8embuClo50KXsznVgoWQE/edit |<font color="#CD004E"><b>Meeting Minute 27</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1pTivyZ9D3jSU1Kf5VoW4-Xl_C9Abg-fL_6SI6GP_hz0/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qbhow5u8GsE42hr9b8o1S2HNeJfG5PTX24W70ZHyCfI/edit |<font color="#CD004E"><b>Meeting Minute 18</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LTLnY5JN2EfiU9drp3d7zGmoCxsSYr1nL4UMvwfXDdU/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]]<br />
|[[https://docs.google.com/document/d/1fbnoWNTimFyUC01lgeblvVCLTySS8Ik2JU_wdZ656RU/edit |<font color="#CD004E"><b>Meeting Minute 19</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Nlo5hnsYbfh4dFSnfsV6Wyv5nxJsmDWF8ZMFKFA9Pac/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]]<br />
|[[https://docs.google.com/document/d/1o1zVXcdHaXCLNzS9rHq528rLEmXMFl3df3ffTFLMtho/edit |<font color="#CD004E"><b>Meeting Minute 20</b></font>]]<br />
|}<br />
<br />
===Supervisor Meeting Minutes===<br />
[https://docs.google.com/document/d/1iuSvaC9Wu-v7dToRp41IwmpdpQ0KtSTJIgpabmiolXQ/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1rXJuYE684ZpYbRyHknn4pmLpJZ9Y5o01QaJT34TD0gY/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1Gy7TOJr9aeyd8pcU_loabY1l3NByVm3nVKqOQnnJRbM/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1DGrSXaCTOtRL_iSOaOI_mHC2DOS7z4Vi6clzomkGkcI/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1VLEizDPdae_enbEtoHo9IGPM4-k9JXe7RFJ1hhiDTBA/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/13MyE--Ymz-dNiQPvgCjGutL23JZwotnoIPlYw7QqmXQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1UUDCW8YMttW2rwAxLJhSfqccBdedYoofVskc9qerIxU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/17QEpHsvitqzO9BO9MkB42umN3_9k6Useli4N2fYoCNU/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1masrY10EdoXrAdwmTnW-POF0RVEYGeHbOorf-0EEC-0/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1u2jcuwSkGqk4lGcGdF4UriFgzT9dNgNAb1ekERDvitQ/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1eHVDrzwLxkGhrElcgPUOWhcQBwLdGdXcmCVvT_u-Va8/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]<br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Testing</font></div>=<br />
==Test Cases==<br />
[https://dl.dropbox.com/u/56071797/Test%20Cases.docx |<font color="#CD004E"><b>Test Cases</b></font>]<br />
<br />
==Test Plans==<br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2001_17_10_2012.docx <font color="#CD004E"><b>Test Plan 1 ''on 17 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2002_28_09_2012.docx <font color="#CD004E"><b>Test Plan 2 ''on 28 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2003_19_10_2012.docx <font color="#CD004E"><b>Test Plan 3 ''on 19 October 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2004_01_11_2012.docx <font color="#CD004E"><b>Test Plan 4 ''on 4 November 2012''</b></font>]<br />
<br />
==User Testing==<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #728FCE; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing|<font color="#CD004E"><b>User Testing 1</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing|<font color="#CD004E"><b>User Testing 2</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing|<font color="#CD004E"><b>User Testing 3</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing|<font color="#CD004E"><b>User Testing 4</b></font>]]<br />
<br />
|}<br />
===User Testing 4===<br />
[[Image:6bituser-testing4.png]]<br />
<br />
====Test Description====<br />
The objective of User Test 4 is on scalability, performance and analytics testing of the system. This is a 2-part test session, firstly on scalability and performance which does not require physical testers, and secondly on inter-rater reliability which requires rating judges.<br />
<br><br><br />
The coverage of the scalability and performance test is focused on the bottleneck functions, which are the discussion forums and marketplace. The terms “performance” and “scalability” are commonly used interchangeably, but the two are distinct: performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. <br />
<br><br><br />
Additionally, Inter-Rater Reliability Test is performed on the Personalized Dashboard to determine the concordance of the personalized results and actual personality of user stereotypes.<br />
<br />
====Testers Background====<br />
=====Scalability & Performance Testing=====<br />
As the test does not require physical testers, the following appends the test environment.<br><br />
[[Image:6-bit_ut4spec.png|400px]]<br />
<br />
=====Inter-Rater Reliability Test=====<br />
Testers will assume the role of raters or judges for our Inter-Rater Reliability Test, represented by a total of 20 people with a 50-50 male is to female ratio. Testers are stratified from a diverse background, intended to represent personality stereotypes designed.<br />
<br><br><br />
Personality stereotypes include characteristics such as gender, age group, education, personality traits, online activity, mobility and interested topics.<br />
<br />
====Test Groups====<br />
There is no test grouping employed in this test.<br />
<br />
====Test Procedures====<br />
=====Scalability & Performance Testing=====<br />
The first part of the test is on scalability and performance testing. Chapalang Benchmark is configured to measure the time taken for each controller method before it starts and as soon as it ends. The results will be used to study the performance of the system and application at different scales of operations. <br />
<br><br><br />
Additionally, custom application is used to perform a series of activities on a forum and marketplace, simulating an arbitrary number of concurrent users on the system, or the load. <br />
<br><br />
<br><br />
Subsequently, we will study the benchmark timing data to understand the performance differences under different load.<br />
=====Inter-Rater Reliability Test=====<br />
An Inter-Rater Reliability (IRR) is the degree of agreement among raters. It gives a score of how much homogeneity or consensus there is in the ratings given by judges.<br />
<br><br><br />
The first rater is the system itself, which will generate a list of 10 products and 10 discussion topics recommendations in descending order of relevance to a target user. Every recommendation is tied to a specific and distinct order number.<br />
<br><br><br />
The second rater is a human tester, who will be provided with the same list of 10 products and 10 discussion topics generated by the system in relevance to him or herself. To mitigate the effects of Experimenter’s Bias, the order of each item is unordered and randomized without any intended logic. The second rater is expected to reorder the items according to his or her preferences in descending order.<br />
<br><br><br />
Subsequently, we will make use of Spearman’s Rank Correlation Coefficient to understand the reliability of our personalized dashboard which features product and topic recommendations.<br />
<br />
====Test Instruction====<br />
=====Inter-Rater Reliability Test=====<br />
This is a sample output of the first rater, for a product recommendation test.<br />
<br><br />
[[Image:6-bit_ut4a.png|750px]]<br />
<br><br />
This is a sample input sheet for the second rater, on product recommendation test.<br />
<br><br />
[[Image:6-bit_ut4b.png|750px]]<br />
<br><br />
In a descending order, 1 represents the most relevant item while 10 represents the least relevant item.<br />
<br />
====Test Results====<br />
=====Scalability & Performance Test=====<br />
The terms “performance” and “scalability” are commonly used interchangeably, but the two are distinct: performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. <br />
*(a) Identification of activities<br />
[[Image:ChapalangA.png|300px]]<br />
*(b) Identification of bottleneck<br />
Based on the table above, we have identified that if a user experience is sequential, “Display single product” page has the longest elapsed time. At the same time, it has the longest elapsed time by itself, when compared to all the functions. Hence, we have identified this activity as the bottleneck.<br />
*(c) Measurement Performance<br />
Referring to the same table above, we have determined the average of 5 tests on the “Display single product” activity for 1 concurrent user to have an elapsed time of 1.76997 seconds. Due to natural variation of the recorded timing, we will adopt 2 seconds as the performance upper limit.<br />
<br><br />
[[Image:ChapalangC.png|300px]]<br />
*(d) Scalability<br />
We will now attempt to find out the maximum number of concurrent users that the system is able to support, given the performance of a single concurrent user. If we assume the performance upper limit to be 2 seconds, there is an estimated number of 16 concurrent users which has performed 2 seconds of lower.<br />
*(e) Results of up to 300 concurrent users<br />
Performing further tests based on the markers of up to 300 concurrent users with 25-user intervals, for the purpose of intentionally simulating a load on the server to observe its deterioration in performance, if any. <br />
<br><br><br />
Firstly, we have determined an arbitrary of acceptable performance of 3 seconds elapsed time for optimal user experience. Given this benchmark, we can observe that the system is capable of supporting up to 25 concurrent users.<br />
<br><br><br />
Secondly, we have also observed peak deterioration in the trend line till approximately 75 users before the elapsed time for 100 concurrent users actually improved and reduced. The performance improved till approximately 200 concurrent users before it begins deterioration again. This is an unexpected and unusual observation for the team. With further consultation with technical experts, there are a variety of reasons which may lead to this anomaly. It could be due to simple outliers in our data, or it could be the use of swap memory on a Linux system (equivalent to pagination in Windows), and it could also be the nature of a switching between threading and non-threading operations of an apache web server.<br />
<br><br><br />
Thirdly, the test crashed after approximately 260 concurrent connections. However, MySQL was still running but apache requires a reboot. Investigating into the log files, we understood that the MaxClient in our apache configuration is 256 and hence it is natural for it to fail. In addition, we found many forked and unreleased processes in the Linux server, which could have been further improved with system-level adjustments.<br />
<br />
=====Inter-Rater Reliability Test=====<br />
In order to evaluate the test results, we rely on the statistical model called Spearman’s Rank Correlation Coefficient (SRCC). The model is appended below:<br />
<br><br />
[[Image: 6bituser-testing4formula.png]]<br />
<br><br />
In short, the SRCC model takes into account the rank rating from 2 different raters, represented by xi and yi respectively. In conventional Correlation of determination model, it takes in absolute data instead to find out statistical and data-driven correlation between 2 inputs. <br />
<br><br />
<br><br />
However, we are interested in the consensus between human judgment on the data, therefore SRCC is a suitable model of analysis. <br />
The SRCC model assumes that the rating scale is ordinal, or basically serial scale of rating. This assumption is aligned with our 1 – 10 rating score which is incremental and serial. Additionally, the SRCC model considers only relative position of the ratings. For example, (1, 2, 1, 3) is considered perfectly correlated with (2, 3, 2, 4). This is acceptable in our test because each rating in our test is distinct and exhaustive, where no repeats or unused score is allowed.<br />
<br> <br><br />
The following is a sample of data tabulation in visual form.<br />
<br><br />
[[Image: 6bituser-testing4z.png]]<br />
<br><br />
With [[Image: 6bituser-testing4di2.png]] found, we can add them to find [[Image: 6bituser-testing4sumdi2.png]] 28. The value of n is 10. So these values can now be substituted back into the equation, we evaluate that p = 0.83.<br />
<br><br />
Based on the nature of correlation coefficient value p, it has a range between -1 to 1. Here are some of the characteristics of the p value.<br />
<br><br />
* A negative number suggests negative relationship, <br />
* A positive number suggests positive relationship, <br />
* A size of a positive or negative number closer to 1 or -1 suggests strength of relationship,<br />
* and A p value of 0 suggests an absolute lack of relationship in the input attributes.<br />
<br />
It should be noted that if there is a strongly negative correlation, it may suggest a reversal in the order of recommendations in our system may eventually become an ideal model.<br />
<br><br />
The accuracy sentimental analysis system is, in principle, how well it agrees with human judgment, despite the fact that the applied accuracy in our test is to ensure an optimal user experience and optimal sales exposure. <br><br />
However, the limitation of the model is that human raters typically agree about 70% of the time and even if a system is 100% accurate by assumption, humans will still disagree about 30% of the time. Hence, for the purpose of our study, it may be suggested that an application with 100% human agreeableness can only be statistically justified to be 70% accurate and more sophisticated methods should be used to endorse the remaining 30% of accuracy. <br><br><br />
After conducting the IRR Test, the results are tabulated and appended as follows.<br />
<br><br />
[[Image: 6bituser-testing4results.png]]<br />
<br><br />
Tester IDs that begins with M denotes male testers, while F denotes Female testers. The categorization of results will help us understand a basic level of stereotyping accuracy by gender. If need it, the results can be further drilled down to represent a more specific personality stereotype.<br />
<br><br><br />
Summarising the test results tabulated above, the average for median p-value for male is 0.8695 and median p-value for female is 0.8675. Based on the median values, there is no significant difference in accuracy for male and females. In addition, it is satisfactorily justified that there is a strong positive correlation between the recommendations of our system and the preferences of the testers, a sample from our potential users, based on their consensus.<br />
<br />
<br />
<br />
<br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Milestones</font></div>=<br />
<br />
[[Image:6-bit_schedule.png|600px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule Metric</font></div>=<br />
Every iteration, schedule metric values are calculated to understand the project progress. They are broadly categorized into 5 different groups, where different action plans will apply. The acceptable range of value is within 90% to 110%, offering some buffer for natural inaccuracies between forecasting and execution.<br />
<br><br><br />
Total Schedule Metric Value = Planned no. of days taken (P) / Actual no. of Days Assigned (A) x 100%<br />
<br><br><br />
[[Image:6-bit_schedulemetric.png|center|600px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Bug Metric</font></div>=<br />
==Log==<br />
[[Image:6-bit_BugMetric.png|550px]]<br />
[[Image:6-bit_BugLog.png|600px]]<br />
<div style="text-align: right;"><br />
Bug Log: [https://docs.google.com/spreadsheet/ccc?key=0Aqd6IiSLbMwQdEI5TldNSEhpcVRjb1puYzU3ZHJOckE |<font color="#CD004E"><b>Click Here</b></font>]<br />
</div><br />
<br><br />
Bug logging for Chapalang! takes the direction of being practical and easily monitored from both macro and micro perspectives. Whenever a bug is found, a new row is entered with the following data:<br />
* Index number<br />
* Bug description<br />
* Found by<br />
* Found date<br />
* Expected solve-by date<br />
* Bug severity<br />
* Status<br />
* Owner of the function<br />
* Fixed date<br />
* Closed by (Tester)<br />
* Close date<br />
* Additional comments<br />
==Metric==<br />
Bugs are classified into 3 different categories of complexity, easy, moderate and hard. Each category is assigned points of 1, 5 and 10 respectively, lower is better.<br />
<br><br><br />
Total Points for Each Iteration = Σ Points of the Bugs in each iteration<br />
<br><br />
[[Image:6-bit_BugMetricFormula.png|500px|center]]<br />
<br><br />
After assigning each bug with points associated by its complexity, we will track the total bug scores at the end of each week before deciding if there should be any actions to be taken. The following is an action plan for our bug metric:<br />
<br><br />
[[Image:6-bit_BugMetricFormula2.png|500px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Risk & Mitigation</font></div>=<br />
<br><br />
[[Image:6-bit_RiskDiagram.png|600px]]<br />
<br><br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=File:ChapalangC.png&diff=114781File:ChapalangC.png2012-12-05T07:10:39Z<p>Huiling.ong.2010: </p>
<hr />
<div></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=File:ChapalangA.png&diff=114780File:ChapalangA.png2012-12-05T07:10:30Z<p>Huiling.ong.2010: </p>
<hr />
<div></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4&diff=114779IS480 Team wiki: 2012T1 6-bit Project Management UT42012-12-05T07:10:20Z<p>Huiling.ong.2010: /* Scalability & Performance Test */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule</font></div>=<br />
==Planned Schedule==<br />
[[Image:6-bit_ScheduleDiagramOverview.png|left|750px|link=""]]<br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
==Meeting Minutes==<br />
===Team Meeting Minutes===<br />
{|<br />
|[[https://docs.google.com/document/d/1nHl51M2qzY4gynJ8tVR6wKqV_lWtJtncl3nbESSnQvU/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]]<br />
|[[https://docs.google.com/document/d/129JDPU8l7PbX-JjferJ-J83JXSIAo5-cXM4_Odw3o5c/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]]<br />
|[[https://docs.google.com/document/d/1BPn6a-XMMAN18TbdlDER27f8Eleb8sUJhcas1bgDOQI/edit |<font color="#CD004E"><b>Meeting Minute 21</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LtSANlI6pDyV_PpGDAVg85PjFVKmDmWWnYC5lXAHh68/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qx6hX462uQDEfwiB3r3ee71eTKaPXSArCZS7y1TOWA4/edit |<font color="#CD004E"><b>Meeting Minute 12</b></font>]]<br />
|[[https://docs.google.com/document/d/1IdjkCbomLgszePgImX2XsTeUHX54e54xRTIjjFoZM6g/edit |<font color="#CD004E"><b>Meeting Minute 22</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/11lQzKaddghH7FHACcTnPQDJnE6ZaScT8Q8nU2YvH8gU/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]]<br />
|[[https://docs.google.com/document/d/1HPdXr28aTDK-RmijqPYTLG1iCUv-JbpkIJ8zzgzTplg/edit |<font color="#CD004E"><b>Meeting Minute 13</b></font>]]<br />
|[[https://docs.google.com/document/d/1gMoTceQakeT42-FO0duVxRajea2hJAUVw8Eu1AfqtfY/edit |<font color="#CD004E"><b>Meeting Minute 23</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1gZuhKW-QMbhUR_oh6Ty8EE17JTYkTFkWCfG6UHrU7-c/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]]<br />
|[[https://docs.google.com/document/d/1ii-ZenbOTZR9drEQCFJ4hX8raXvpgufELaZY80M2GYI/edit |<font color="#CD004E"><b>Meeting Minute 14</b></font>]]<br />
|[[https://docs.google.com/document/d/12vYfm8jo9c2eZ3VwnL2z6vn6l__D6heDhCHdEWVPg4I/edit |<font color="#CD004E"><b>Meeting Minute 24</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1H-8fODLc79U6-IXScSfemjRLOyjvzC6_k0aig6BDcBY/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]]<br />
|[[https://docs.google.com/document/d/1I3qlvujdLVmY_L22VMsKrtISIFI5CnxmtZnMNdJdxfc/edit |<font color="#CD004E"><b>Meeting Minute 15</b></font>]]<br />
|[[https://docs.google.com/document/d/1jPIW-xe7p6kjzGF_YMmk0K2mPzWil1zUfBQOwGc8wRk/edit |<font color="#CD004E"><b>Meeting Minute 25</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Qx4jdRZoE8hXv3u1R4dWke5b-kyMxIc7ASzPIh4ShRQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]]<br />
|[[https://docs.google.com/document/d/1Pcd6ZADI7ZEuXzq3exrss4nJQhotxAq7-ENfy_OVs6o/edit |<font color="#CD004E"><b>Meeting Minute 16</b></font>]]<br />
|[[https://docs.google.com/document/d/1NDCoF37ckdhbys57BLEXShcAcraxzOKpoNbFvpWWUQM/edit |<font color="#CD004E"><b>Meeting Minute 26</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1uSkv_cux0PqnRTKS-w72wQLgL1ZKaCpXhzDm5uamfMU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]]<br />
|[[https://docs.google.com/document/d/12jW-ycBkfivYL2pg7nrVvb9SF7_XmiglVGGnWAjp6uQ/edit |<font color="#CD004E"><b>Meeting Minute 17</b></font>]]<br />
|[[https://docs.google.com/document/d/1Amo6YgCkVA3YD-iqyIxhyG8embuClo50KXsznVgoWQE/edit |<font color="#CD004E"><b>Meeting Minute 27</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1pTivyZ9D3jSU1Kf5VoW4-Xl_C9Abg-fL_6SI6GP_hz0/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qbhow5u8GsE42hr9b8o1S2HNeJfG5PTX24W70ZHyCfI/edit |<font color="#CD004E"><b>Meeting Minute 18</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LTLnY5JN2EfiU9drp3d7zGmoCxsSYr1nL4UMvwfXDdU/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]]<br />
|[[https://docs.google.com/document/d/1fbnoWNTimFyUC01lgeblvVCLTySS8Ik2JU_wdZ656RU/edit |<font color="#CD004E"><b>Meeting Minute 19</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Nlo5hnsYbfh4dFSnfsV6Wyv5nxJsmDWF8ZMFKFA9Pac/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]]<br />
|[[https://docs.google.com/document/d/1o1zVXcdHaXCLNzS9rHq528rLEmXMFl3df3ffTFLMtho/edit |<font color="#CD004E"><b>Meeting Minute 20</b></font>]]<br />
|}<br />
<br />
===Supervisor Meeting Minutes===<br />
[https://docs.google.com/document/d/1iuSvaC9Wu-v7dToRp41IwmpdpQ0KtSTJIgpabmiolXQ/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1rXJuYE684ZpYbRyHknn4pmLpJZ9Y5o01QaJT34TD0gY/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1Gy7TOJr9aeyd8pcU_loabY1l3NByVm3nVKqOQnnJRbM/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1DGrSXaCTOtRL_iSOaOI_mHC2DOS7z4Vi6clzomkGkcI/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1VLEizDPdae_enbEtoHo9IGPM4-k9JXe7RFJ1hhiDTBA/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/13MyE--Ymz-dNiQPvgCjGutL23JZwotnoIPlYw7QqmXQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1UUDCW8YMttW2rwAxLJhSfqccBdedYoofVskc9qerIxU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/17QEpHsvitqzO9BO9MkB42umN3_9k6Useli4N2fYoCNU/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1masrY10EdoXrAdwmTnW-POF0RVEYGeHbOorf-0EEC-0/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1u2jcuwSkGqk4lGcGdF4UriFgzT9dNgNAb1ekERDvitQ/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1eHVDrzwLxkGhrElcgPUOWhcQBwLdGdXcmCVvT_u-Va8/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]<br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Testing</font></div>=<br />
==Test Cases==<br />
[https://dl.dropbox.com/u/56071797/Test%20Cases.docx |<font color="#CD004E"><b>Test Cases</b></font>]<br />
<br />
==Test Plans==<br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2001_17_10_2012.docx <font color="#CD004E"><b>Test Plan 1 ''on 17 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2002_28_09_2012.docx <font color="#CD004E"><b>Test Plan 2 ''on 28 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2003_19_10_2012.docx <font color="#CD004E"><b>Test Plan 3 ''on 19 October 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2004_01_11_2012.docx <font color="#CD004E"><b>Test Plan 4 ''on 4 November 2012''</b></font>]<br />
<br />
==User Testing==<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #728FCE; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing|<font color="#CD004E"><b>User Testing 1</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing|<font color="#CD004E"><b>User Testing 2</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing|<font color="#CD004E"><b>User Testing 3</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing|<font color="#CD004E"><b>User Testing 4</b></font>]]<br />
<br />
|}<br />
===User Testing 4===<br />
[[Image:6bituser-testing4.png]]<br />
<br />
====Test Description====<br />
The objective of User Test 4 is on scalability, performance and analytics testing of the system. This is a 2-part test session, firstly on scalability and performance which does not require physical testers, and secondly on inter-rater reliability which requires rating judges.<br />
<br><br><br />
The coverage of the scalability and performance test is focused on the bottleneck functions, which are the discussion forums and marketplace. The terms “performance” and “scalability” are commonly used interchangeably, but the two are distinct: performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. <br />
<br><br><br />
Additionally, Inter-Rater Reliability Test is performed on the Personalized Dashboard to determine the concordance of the personalized results and actual personality of user stereotypes.<br />
<br />
====Testers Background====<br />
=====Scalability & Performance Testing=====<br />
As the test does not require physical testers, the following appends the test environment.<br><br />
[[Image:6-bit_ut4spec.png|400px]]<br />
<br />
=====Inter-Rater Reliability Test=====<br />
Testers will assume the role of raters or judges for our Inter-Rater Reliability Test, represented by a total of 20 people with a 50-50 male is to female ratio. Testers are stratified from a diverse background, intended to represent personality stereotypes designed.<br />
<br><br><br />
Personality stereotypes include characteristics such as gender, age group, education, personality traits, online activity, mobility and interested topics.<br />
<br />
====Test Groups====<br />
There is no test grouping employed in this test.<br />
<br />
====Test Procedures====<br />
=====Scalability & Performance Testing=====<br />
The first part of the test is on scalability and performance testing. Chapalang Benchmark is configured to measure the time taken for each controller method before it starts and as soon as it ends. The results will be used to study the performance of the system and application at different scales of operations. <br />
<br><br><br />
Additionally, custom application is used to perform a series of activities on a forum and marketplace, simulating an arbitrary number of concurrent users on the system, or the load. <br />
<br><br />
<br><br />
Subsequently, we will study the benchmark timing data to understand the performance differences under different load.<br />
=====Inter-Rater Reliability Test=====<br />
An Inter-Rater Reliability (IRR) is the degree of agreement among raters. It gives a score of how much homogeneity or consensus there is in the ratings given by judges.<br />
<br><br><br />
The first rater is the system itself, which will generate a list of 10 products and 10 discussion topics recommendations in descending order of relevance to a target user. Every recommendation is tied to a specific and distinct order number.<br />
<br><br><br />
The second rater is a human tester, who will be provided with the same list of 10 products and 10 discussion topics generated by the system in relevance to him or herself. To mitigate the effects of Experimenter’s Bias, the order of each item is unordered and randomized without any intended logic. The second rater is expected to reorder the items according to his or her preferences in descending order.<br />
<br><br><br />
Subsequently, we will make use of Spearman’s Rank Correlation Coefficient to understand the reliability of our personalized dashboard which features product and topic recommendations.<br />
<br />
====Test Instruction====<br />
=====Inter-Rater Reliability Test=====<br />
This is a sample output of the first rater, for a product recommendation test.<br />
<br><br />
[[Image:6-bit_ut4a.png|750px]]<br />
<br><br />
This is a sample input sheet for the second rater, on product recommendation test.<br />
<br><br />
[[Image:6-bit_ut4b.png|750px]]<br />
<br><br />
In a descending order, 1 represents the most relevant item while 10 represents the least relevant item.<br />
<br />
====Test Results====<br />
=====Scalability & Performance Test=====<br />
The terms “performance” and “scalability” are commonly used interchangeably, but the two are distinct: performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. <br />
*(a) Identification of activities<br />
[[Image:ChapalangA.png|300px]]<br />
*(b) Identification of bottleneck<br />
Based on the table above, we have identified that if a user experience is sequential, “Display single product” page has the longest elapsed time. At the same time, it has the longest elapsed time by itself, when compared to all the functions. Hence, we have identified this activity as the bottleneck.<br />
*(c) Measurement Performance<br />
Referring to the same table above, we have determined the average of 5 tests on the “Display single product” activity for 1 concurrent user to have an elapsed time of 1.76997 seconds. Due to natural variation of the recorded timing, we will adopt 2 seconds as the performance upper limit.<br />
[[Image:ChapalangC.png|300px]]<br />
*(d) Scalability<br />
We will now attempt to find out the maximum number of concurrent users that the system is able to support, given the performance of a single concurrent user. If we assume the performance upper limit to be 2 seconds, there is an estimated number of 16 concurrent users which has performed 2 seconds of lower.<br />
*(e) Results of up to 300 concurrent users<br />
Performing further tests based on the markers of up to 300 concurrent users with 25-user intervals, for the purpose of intentionally simulating a load on the server to observe its deterioration in performance, if any. <br />
<br><br><br />
Firstly, we have determined an arbitrary of acceptable performance of 3 seconds elapsed time for optimal user experience. Given this benchmark, we can observe that the system is capable of supporting up to 25 concurrent users.<br />
<br><br><br />
Secondly, we have also observed peak deterioration in the trend line till approximately 75 users before the elapsed time for 100 concurrent users actually improved and reduced. The performance improved till approximately 200 concurrent users before it begins deterioration again. This is an unexpected and unusual observation for the team. With further consultation with technical experts, there are a variety of reasons which may lead to this anomaly. It could be due to simple outliers in our data, or it could be the use of swap memory on a Linux system (equivalent to pagination in Windows), and it could also be the nature of a switching between threading and non-threading operations of an apache web server.<br />
<br><br><br />
Thirdly, the test crashed after approximately 260 concurrent connections. However, MySQL was still running but apache requires a reboot. Investigating into the log files, we understood that the MaxClient in our apache configuration is 256 and hence it is natural for it to fail. In addition, we found many forked and unreleased processes in the Linux server, which could have been further improved with system-level adjustments.<br />
<br />
=====Inter-Rater Reliability Test=====<br />
In order to evaluate the test results, we rely on the statistical model called Spearman’s Rank Correlation Coefficient (SRCC). The model is appended below:<br />
<br><br />
[[Image: 6bituser-testing4formula.png]]<br />
<br><br />
In short, the SRCC model takes into account the rank rating from 2 different raters, represented by xi and yi respectively. In conventional Correlation of determination model, it takes in absolute data instead to find out statistical and data-driven correlation between 2 inputs. <br />
<br><br />
<br><br />
However, we are interested in the consensus between human judgment on the data, therefore SRCC is a suitable model of analysis. <br />
The SRCC model assumes that the rating scale is ordinal, or basically serial scale of rating. This assumption is aligned with our 1 – 10 rating score which is incremental and serial. Additionally, the SRCC model considers only relative position of the ratings. For example, (1, 2, 1, 3) is considered perfectly correlated with (2, 3, 2, 4). This is acceptable in our test because each rating in our test is distinct and exhaustive, where no repeats or unused score is allowed.<br />
<br> <br><br />
The following is a sample of data tabulation in visual form.<br />
<br><br />
[[Image: 6bituser-testing4z.png]]<br />
<br><br />
With [[Image: 6bituser-testing4di2.png]] found, we can add them to find [[Image: 6bituser-testing4sumdi2.png]] 28. The value of n is 10. So these values can now be substituted back into the equation, we evaluate that p = 0.83.<br />
<br><br />
Based on the nature of correlation coefficient value p, it has a range between -1 to 1. Here are some of the characteristics of the p value.<br />
<br><br />
* A negative number suggests negative relationship, <br />
* A positive number suggests positive relationship, <br />
* A size of a positive or negative number closer to 1 or -1 suggests strength of relationship,<br />
* and A p value of 0 suggests an absolute lack of relationship in the input attributes.<br />
<br />
It should be noted that if there is a strongly negative correlation, it may suggest a reversal in the order of recommendations in our system may eventually become an ideal model.<br />
<br><br />
The accuracy sentimental analysis system is, in principle, how well it agrees with human judgment, despite the fact that the applied accuracy in our test is to ensure an optimal user experience and optimal sales exposure. <br><br />
However, the limitation of the model is that human raters typically agree about 70% of the time and even if a system is 100% accurate by assumption, humans will still disagree about 30% of the time. Hence, for the purpose of our study, it may be suggested that an application with 100% human agreeableness can only be statistically justified to be 70% accurate and more sophisticated methods should be used to endorse the remaining 30% of accuracy. <br><br><br />
After conducting the IRR Test, the results are tabulated and appended as follows.<br />
<br><br />
[[Image: 6bituser-testing4results.png]]<br />
<br><br />
Tester IDs that begins with M denotes male testers, while F denotes Female testers. The categorization of results will help us understand a basic level of stereotyping accuracy by gender. If need it, the results can be further drilled down to represent a more specific personality stereotype.<br />
<br><br><br />
Summarising the test results tabulated above, the average for median p-value for male is 0.8695 and median p-value for female is 0.8675. Based on the median values, there is no significant difference in accuracy for male and females. In addition, it is satisfactorily justified that there is a strong positive correlation between the recommendations of our system and the preferences of the testers, a sample from our potential users, based on their consensus.<br />
<br />
<br />
<br />
<br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Milestones</font></div>=<br />
<br />
[[Image:6-bit_schedule.png|600px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule Metric</font></div>=<br />
Every iteration, schedule metric values are calculated to understand the project progress. They are broadly categorized into 5 different groups, where different action plans will apply. The acceptable range of value is within 90% to 110%, offering some buffer for natural inaccuracies between forecasting and execution.<br />
<br><br><br />
Total Schedule Metric Value = Planned no. of days taken (P) / Actual no. of Days Assigned (A) x 100%<br />
<br><br><br />
[[Image:6-bit_schedulemetric.png|center|600px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Bug Metric</font></div>=<br />
==Log==<br />
[[Image:6-bit_BugMetric.png|550px]]<br />
[[Image:6-bit_BugLog.png|600px]]<br />
<div style="text-align: right;"><br />
Bug Log: [https://docs.google.com/spreadsheet/ccc?key=0Aqd6IiSLbMwQdEI5TldNSEhpcVRjb1puYzU3ZHJOckE |<font color="#CD004E"><b>Click Here</b></font>]<br />
</div><br />
<br><br />
Bug logging for Chapalang! takes the direction of being practical and easily monitored from both macro and micro perspectives. Whenever a bug is found, a new row is entered with the following data:<br />
* Index number<br />
* Bug description<br />
* Found by<br />
* Found date<br />
* Expected solve-by date<br />
* Bug severity<br />
* Status<br />
* Owner of the function<br />
* Fixed date<br />
* Closed by (Tester)<br />
* Close date<br />
* Additional comments<br />
==Metric==<br />
Bugs are classified into 3 different categories of complexity, easy, moderate and hard. Each category is assigned points of 1, 5 and 10 respectively, lower is better.<br />
<br><br><br />
Total Points for Each Iteration = Σ Points of the Bugs in each iteration<br />
<br><br />
[[Image:6-bit_BugMetricFormula.png|500px|center]]<br />
<br><br />
After assigning each bug with points associated by its complexity, we will track the total bug scores at the end of each week before deciding if there should be any actions to be taken. The following is an action plan for our bug metric:<br />
<br><br />
[[Image:6-bit_BugMetricFormula2.png|500px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Risk & Mitigation</font></div>=<br />
<br><br />
[[Image:6-bit_RiskDiagram.png|600px]]<br />
<br><br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage&diff=114778IS480 Team wiki: 2012T1 6-bit Final Wikipage2012-12-05T07:05:57Z<p>Huiling.ong.2010: /* Multivariate Distribution-based Clustering */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Project Progress Summary</font></div>=<br />
[https://dl.dropbox.com/u/56071797/Final_Presentation.pdf <font color="#CD004E"><b>Final Presentation Slides</b></font>]<br />
<br />
<br><br />
Our website: http://www.chapalang.com<br />
==Project Overview==<br />
<div style="text-align: center"><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#X-Factors Click Here to View our X-Factors!]<br />
<br><br />
Problem Scenario: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#Problem_Scenario Click Here]<br><br />
''Team 6-bit is formed during the month of May in 2012. We have battled through 16 iterations of planning, designing, constructing and deploying our project, Chapalang and have successfully completed the project, maintaining to our planned scope. Throughout 16 iterations, we have our ups and downs. We faced several unexpected technical challenges which brought down the morale of the team. People with different methods of solving problems created communication problems. However, having a common goal in mind, we endure and frantically looking for workarounds and alternatives to overcome these challenges. We, too, faced some project management challenges where some tasks are not complete on time and caused disturbance to our schedule. These project challenges allow us to iron out our differences and streamlined a better working process. After overcoming these challenges, we had improved ourselves as individuals as well as improved as a team!''<br />
<br />
</div><br />
<br>[[Image:6-bit_poster.jpg|right|450px]]<br />
<br>[http://www.youtube.com/watch?v=8Y8Q9iCKQUY Click here to view our 1min Video Pitch!] <br />
<br><br />
[[Image:6-bit_videopitch.gif|left|450px]]<br />
<br><br><br><br><br><br><br><br><br><br><br><br />
<br><br />
<br />
<br><br />
<br />
<br />
<br />
==Project Challenges==<br />
There are several challenges that the team has faced throughout the IS480 journey. The bulk of Chapalang! is a highly functional and complete solution to a business opportunity of our sponsor, and hence it is not on the basis of a single sophisticated function.<br />
<br><br> <br />
However, it is a cumulatively complex system as it is formed by several functions, and the team has been challenged in different levels on integration issues, and micro-components of the project. One example of the micro-component is Paypal integration where Paypal documentations have been brief and changes are frequent, resulting in integration difficulties but eventually resolved. Another example is on our image cropping tool, where significant amount of time is spent on getting it right especially when none of us in the team has ever ventured into image manipulation.<br />
<br><br><br />
Nonetheless, there are two other independent challenges which introduce much learning lessons for the team.<br />
<br />
===Scalability and Load Testing===<br />
As part of our User Test 4, we attempted to have a better understanding of scalability and load handling of our system by conducting a test.<br><br />
To reiterate, performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. In order to conduct the test, the following steps are required.<br />
* Performance Testing<br />
** Identify a system process with a series of activities<br />
** Measure the elapse time of each activity<br />
** Identify the bottleneck which is the single important activity which has highest elapse time <br />
* Scalability Testing<br />
** Increase the number of concurrent connections for the identified activity and measure of elapse time of each connection<br />
** Count the number of concurrent connections possible, within the same approximate amount of elapse time of each connection<br />
* Load Testing<br />
** Measure the elapse time of each connection over a range of concurrent connections, including 1, 25, 50, 75, 100 as markers<br />
<br />
====Difficulty in simulating accurate multiple concurrent connections====<br />
Amongst all the steps involved, it is easiest to conduct performance testing because we have already developed Chapalang Benchmark which will help us measure the elapsed time from the moment the framework receives the command until the output is prepared and sent to the end-user.<br />
<br><br><br />
However, the first challenge appeared when simulating multiple concurrent connections. There were several options that we tried for the simulation, and they include:<br />
* Asynchronous Javascript (AJAX)<br />
We started off with AJAX because we are most familiar with it and it is one of the easiest to implement. However, when we observe the start_time in Chapalang Benchmark, each connect has a different start_time even though it overlaps between the start_time and end_time of the previous connection. <br />
<br><br><br />
At this stage, we cleared our misunderstanding about asynchronous calls that we had all along. While it is capable of initiating multiple asynchronous calls, where each call initiates a new connection, it does not initiate all the calls concurrently. It continues to initiate calls sequentially, but it does not wait for the previously initiated connection to be closed before it initiates the next one.<br />
<br><br><br />
As such, we realized that AJAX will not be able to accurately simulate the same-second concurrent connections that we needed for our test.<br />
* PHP popen()<br />
After some research and tests, we found out popen() which opens a pipe to a process executed by forking the command. It is also possible to create an environment where executions are done in parallel and will be suitable for simulating concurrency.<br />
<br><br><br />
While it is fairly easy to use, it offers only a unidirectional process pipe and hence unable to give us a connection response to confirm the number of concurrent connections registered at the server-side. As such, it is not a suitable tool for our test.<br />
* PHP fsocketopen()<br />
We went back to research for a new solution and it appears that fsocketopen() will be able to help us with concurrency and a bidirectional process pipe. <br />
<br><br><br />
As we developed a simple script to simulate concurrent users, we faced a problem where Apache Web Server crashes at an unexpectedly low number of 96 concurrent connections. After some investigations, we realized that fsocketopen() itself opens the same number of concurrent connections as the number of connections Apache is expected to receive and create. Essentially, there were a doubled number of connections that the server has to create, and a check on the background process on the server-side revealed a total of 156 registered apache processes. <br />
<br><br><br />
This led to some biasness in our test, because the intention was to create concurrency at the receiving end but the execution causes inaccuracies in the results. We attempt to solve it by hosting the wrapper file for fsocketopen() on our localhost machine, but we really wanted to take out the network performance uncertainty of every different users who may be using our services, and normalize it solely based on our system performance.<br />
<br><br><br />
Again, we need a methodology where we can simulate concurrency at the web server, without creating additional connections to execute.<br />
* PHP curl_multi_exec()<br />
Finally, we chanced upon curl_multi_exec() method in PHP 5 documentation manual. Libcurl is a PHP library where it performs a cURL session calling upon an internet or UNIX pointer. Additionally, curl_multi enables us to execute its sub-connections in the stack.<br />
<br><br><br />
This method did exactly what we need; it offers us a single connection, multiple threads on the execution. The overall processing time is also faster than fsocketopen() that we attempted earlier by several times.<br />
<br />
===Personalization Analytics===<br />
The personalized dashboard is an adopted feature at a later stage of the project, and hence the natural difficulty is the time constraints. In the process, we had to go through standard cycle of research, prototypes, implement, integrate and test. Every stage is time-consuming and plagued with problems.<br />
<br><br><br />
More objectively, though we are able to map an analytical process, the most challenging task is identifying a suitable data-drive semantic algorithm which is able to suit our needs. Due to time constraints, our research sources are highly limited to consultations with professors and online research.<br />
<br><br><br />
We spoke to an Adjunct Professor who is also a Consulting Researcher in a government research agency, and he recommended for us to try out <br />
<br />
====Multivariate Distribution-based Clustering====<br />
<br><br />
[[Image:6-bitChapalang1.png|500px]]<br />
<br><br />
The above diagrams illustrates some sample on Multivariate Distribution-based Clustering. Clusters can then easily be defined as objects belonging most likely to the same distribution. A nice property of this approach is that this closely resembles the way artificial data sets are generated: by sampling random objects from a distribution.<br />
<br><br><br />
While the theoretical foundation of these methods is excellent, they suffer from one key problem known as overfitting, unless constraints are put on the model complexity. A more complex model will usually always be able to explain the data better, which makes choosing the appropriate model complexity inherently difficult.<br />
<br><br><br />
Distribution-based clustering is a semantically strong method, as it not only provides you with clusters, but also produces complex models for the clusters that can also capture correlation and independence of attributes. However, using these algorithms puts an extra burden on the user: to choose appropriate data models to optimize, and for many real data sets, there may be no mathematical model available the algorithm is able to optimize<br />
<br><br><br />
In short, we are not able to simply create a system model based on this statistical model for the purpose of our analytics engine.<br />
<br />
====Latent Semantic Index (LSI)====<br />
While researching deeper into semantic analysis, we discovered another model which is Latent Semantic Indexing (LSI). LSI is an indexing and retrieval method which uses a mathematical technique called Singular Value Decomposition (SVD) to identify patterns in relationships between terms and concepts contained in an unstructured collection of text. <br />
<br><br><br />
LSI is based on the principle that words that are used in the same contexts tend to have similar meaning, and its key feature is to extract conceptual content of a body of text by establishing associations. The key benefits of LSI is that it overcomes two of the most problematic constraints of Boolean keyword queries, which is synonymy (words with similar meanings) and polysemy (words with more than one meaning).<br />
<br><br><br />
However, LSI was originally a patented property in the late 1980s and till today, there are no opensource materials that we are able to make use of in our project.<br />
====Naïve Bayes Classifier (NBC)====<br />
Finally, we went back to the basics of statistics and found that in Bayesian statistics, it supports the model Naïve Bayes Classifier (NBC). <br />
NBC is a simple probabilistic classifier based on Bayes’ Theorem with strong independence assumptions. Its major and naïve assumption is that all input features are independent and contributes to the object. For example, an orange is “round” and is about 4 inches in “diameter”. While diameter is a measurement unit for rounded objects, and hence a dependence of “diameter” on “round”, NBC assumes that they are independent and may affect the objectivity of the results being oversimplified.<br />
<br><br><br />
While NBC appears to be skewed and bias in most applications, it appears to match what we need because we have an exhaustive list of product or topical categories that we want to make an exhaustive recommendations from. Hence, the constraint of objectivity and dependence in the results does not create a new problem for our analytics engine.<br />
<br><br><br />
Correspondingly, we found an open source script which applies NBC and tested to work. It appears that it is possible to configure NBC to accept different weightage of each independent characteristic. <br />
<br><br><br />
By default, each characteristic has equal weightage with a combined maximum of 1. We found this particularly useful because we are able to adjust the weightage to suit different circumstances. Firstly, the weightage can be adjusted if there is any particular category of products or topics that we want to have higher exposure rates to system users. Hence, this can potentially be a model that suits targeted advertising. Secondly, we are able to incorporate machine learning into the system which skews the weightage according to user’s actual and future activities. Since we capture user activities in our system, the data can be further used to help in the automated skewing of weightage to provide a data-driven model not solely based on historical data but instead, more recent and futuristic data.<br />
<br />
<br />
<br />
<!-- ==Project Achievements==<br />
Methods, technologies, processes, teamwork, etc. which were particularly successful – highlight things which worked very well towards completing the project. A bulleted list of one to two sentences each will do. If there are no achievement, remove this section. --><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Project Management</font></div>=<br />
==Schedule==<br />
[[Image:6-bit_schedule.png|center|600px]]<br />
Detailed Schedule: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Schedule Click Here]<br />
===Schedule Changes===<br />
Throughout the whole project period, there were several scope adjustments and changes and they affect the schedule directly. The following documents some of the noteworthy changes made:<br />
<br><br />
[[Image:60bit_schedulechanges.png|center|500px]]<br />
<br><br />
The tasks and allocated time for the functions removed, which occurs in iteration 14-15 are replaced with the tasks for the newly added tasks.<br />
<br><br />
<br />
<br />
<div style="text-align: right;"><br />
<font size="2">''[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Technical_Overview#Scope_Prioritization Click Here to see how we prioritize our scope!]<br />
<br><br />
Visit http://www.chapalang.com to try these features out yourself! =)''<br />
</font><br />
</div><br />
==Metrics==<br />
===Schedule Metric===<br />
Schedule Metric: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Schedule_Metric Click Here]<br />
<br><br />
Metric Value: [[Image:6bit_schedulevalue.png|500px]]<br />
<br><br><br />
The acceptable range of schedule metric value is between 90% and 110%, catering to the natural inaccuracies in forecasting and actual implementation of time required to complete a task. Most of our schedules are on time, with the exception of 3 iterations.<br />
<br><br><br />
In iteration 6, there was overestimation of the amount of work that we are able to handle within the first 2-week iteration that we have, resulting in an off schedule by 20%. Previously, all our iterations are weekly. The additional tasks allocated for that iteration was to catch up with the scope to be presented for Acceptance Presentation. Many of us were however, busy with the handing over of work at our respective internship workplace and could not meet the original schedule plan. As there is a schedule lapse, we have reviewed the workload per iteration and spaced out the work for future iterations.<br />
<br><br><br />
In iteration 9, there was sufficient time to complete tasks that were planned for the iteration. However, the rush to complete the tasks before User Test 2 has led to lower quality unit testing performed by each developer in the team. This resulted in higher bug counts than usual, and the team had to stop new developers and instead spend the time fixing the bugs. As such, the schedule missed by 30% and we gained a new learning lesson that there should be buffer time for each iteration to cater for unexpected events.<br />
In iteration 15, there were fewer tasks in the iteration than much other previous iteration. However, the schedule was missed by approximately 20%. The team has discussed, and attributed the lapse to project fatigue as well as the submission of projects from other academic modules. While this could be better planned for, it was difficult to forecast the effort required for each member’s other projects. Nonetheless, there was buffer time in the final iteration which was eventually activated to make up for the schedule lapse in iteration 15.<br />
===Bug Metric===<br />
Bug Metric: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Bug_Metric Click Here]<br />
<br><br />
Metric Value: [[Image:6bit_bugvalue.png|500px]]<br />
<br><br><br />
As our acceptable range of bug points is under 20, there are 2 iterations where we have exceeded and remedies were applied as per our action plan. <br />
<br><br><br />
In iteration 11, we have conducted our User Test 2 which has a wide range of functions coverage. As a bigger system tends to also have more bugs, the user test exposes bugs that were previously unknown to us. Immediately after the user test, we have stopped new developments and focused on fixing all the bugs before we continue. Steps were taken to allow more time per task to ensure developments in the team have more time to conduct unit testing before committing their codes. Our team tester has also drafted more comprehensive test cases for her test work.<br />
<br><br><br />
In iteration 15, there was another spike in bugs metric value after the team is gradually facing project fatigue. We accepted the nature that the team has been working on the system for the past 7 months, and that there were many other school projects due during that period. As much as we have justified the cause, we stopped new developments and proceeded with a full day of bugs fixing to ensure the system is functioning properly.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Quality of Product</font></div>=<br />
<br />
{| class="wikitable"<br />
|- style="background:#58ACFA; color:white" <br />
|align="center"| Stage <br />
|align="center"| Specification<br />
|align="center"| Modules<br />
|-<br />
<br />
|rowspan="3"| Project Management<br />
|| Minutes<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Meeting_Minutes Click Here]<br />
|-<br />
<br />
|rowspan="2"| Metrics<br />
|| Schedule metrics: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Meeting_Minutes Click Here]<br />
|-<br />
<br />
|| Bug metrics: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Bug_Metric Click Here]<br />
|-<br />
<br />
|rowspan="4"| Requirements<br />
|| Scope<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables Click Here]<br />
|-<br />
<br />
|| Scope Prioritization<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Technical_Overview#Scope_Prioritization Click Here]<br />
|-<br />
<br />
|rowspan="2"| Problem Scenario<br />
|| As-Is: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#As-Is Click Here]<br />
|-<br />
<br />
|| To-Be: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#To-Be Click Here]<br />
|-<br />
<br />
|rowspan="3"| Analysis<br />
|| Use case<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Use_Case_Diagram Click Here]<br />
|-<br />
<br />
|| Business Process Diagram<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Bug_Metric Click Here]<br />
|-<br />
<br />
|| Screen Shots<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype Click Here]<br />
|-<br />
<br />
|rowspan="4"| Design<br />
|| Logical Diagram<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Logical_Diagram Click Here]<br />
|-<br />
<br />
|| Class Diagram<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Class_Diagram Click Here]<br />
|-<br />
<br />
|| Sequence Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Sequence_Diagram Click Here]<br />
|-<br />
<br />
|| Data Architecture<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Technical_Overview#Data_Architecture Click Here]<br />
|-<br />
|| Testing<br />
|| Test plan<br />
|| [[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Testing Click Here]]<br />
|-<br />
<br />
|}<br />
<br />
==Key Performance Indicators(KPI)==<br />
For the purpose of benchmarking ourselves with specific goals, we have derived on a set of indicators to understand our progress.<br />
<br><br />
[[Image:6bit_kpi.png]]<br />
<br><br />
The following figures are accurate as of 21st November 2012.<br />
<br><br />
505 real members<br />
<br><br />
106 real transactions<br />
<br><br />
189 real physical items sold<br />
<br><br />
$2536.50 real revenue<br />
<br><br />
9 registered and active sellers<br />
<br><br />
62 real products<br />
<br><br />
49 days of operations<br />
<br><br />
<div style="text-align: right;"><br />
<font size="2">''[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes Click Here to see our Learning Outcome!]''</font><br />
</div><br />
<br />
==Testing==<br />
There are a total of 4 User Tests conducted, each with a different coverage and test methodology.<br />
<br><br />
[[Image:6bituser-testingoverview.png|500px]]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing Click Here to view the details of User Test 1]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing Click Here to view the details of User Test 2]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing Click Here to view the details of User Test 3]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing Click Here to view the details of User Test 4]<br />
<br><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Reflection</font></div>=<br />
<br />
==Sponsor Comment==<br />
[https://dl.dropbox.com/u/56071797/Sponsor%28DotCom%29%20Evaluation.doc Click Here to Download our Sponsor's Comments!]<br />
<br />
==Team Reflection==<br />
<div style="text-align: center"><br />
Learning Outcome: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes#Learning_Outcome Click Here]<br />
</div><br />
[[Image:6-bit_teamReflection.png|850px|center]]<br />
==Individual Reflection==<br />
[[Image:6-bit_tianxiangReflection.png|850px|center]]<br />
<br><br />
[[Image:6-bit_geksengReflection.png|850px|left]]<br />
<br><br />
[[Image:6-bit_houstonReflection.png|850px|right]]<br />
<br><br />
[[Image:6-bit_aloysiusReflection.png|850px|center]]<br />
<br><br />
[[Image:6-bit_kennethReflection.png|850px|left]]<br />
<br><br />
[[Image:6-bit_huilingReflection.png|850px|right]]<br />
<br><br />
<br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage&diff=114777IS480 Team wiki: 2012T1 6-bit Final Wikipage2012-12-05T07:05:40Z<p>Huiling.ong.2010: /* Personalization Analytics */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Project Progress Summary</font></div>=<br />
[https://dl.dropbox.com/u/56071797/Final_Presentation.pdf <font color="#CD004E"><b>Final Presentation Slides</b></font>]<br />
<br />
<br><br />
Our website: http://www.chapalang.com<br />
==Project Overview==<br />
<div style="text-align: center"><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#X-Factors Click Here to View our X-Factors!]<br />
<br><br />
Problem Scenario: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#Problem_Scenario Click Here]<br><br />
''Team 6-bit is formed during the month of May in 2012. We have battled through 16 iterations of planning, designing, constructing and deploying our project, Chapalang and have successfully completed the project, maintaining to our planned scope. Throughout 16 iterations, we have our ups and downs. We faced several unexpected technical challenges which brought down the morale of the team. People with different methods of solving problems created communication problems. However, having a common goal in mind, we endure and frantically looking for workarounds and alternatives to overcome these challenges. We, too, faced some project management challenges where some tasks are not complete on time and caused disturbance to our schedule. These project challenges allow us to iron out our differences and streamlined a better working process. After overcoming these challenges, we had improved ourselves as individuals as well as improved as a team!''<br />
<br />
</div><br />
<br>[[Image:6-bit_poster.jpg|right|450px]]<br />
<br>[http://www.youtube.com/watch?v=8Y8Q9iCKQUY Click here to view our 1min Video Pitch!] <br />
<br><br />
[[Image:6-bit_videopitch.gif|left|450px]]<br />
<br><br><br><br><br><br><br><br><br><br><br><br />
<br><br />
<br />
<br><br />
<br />
<br />
<br />
==Project Challenges==<br />
There are several challenges that the team has faced throughout the IS480 journey. The bulk of Chapalang! is a highly functional and complete solution to a business opportunity of our sponsor, and hence it is not on the basis of a single sophisticated function.<br />
<br><br> <br />
However, it is a cumulatively complex system as it is formed by several functions, and the team has been challenged in different levels on integration issues, and micro-components of the project. One example of the micro-component is Paypal integration where Paypal documentations have been brief and changes are frequent, resulting in integration difficulties but eventually resolved. Another example is on our image cropping tool, where significant amount of time is spent on getting it right especially when none of us in the team has ever ventured into image manipulation.<br />
<br><br><br />
Nonetheless, there are two other independent challenges which introduce much learning lessons for the team.<br />
<br />
===Scalability and Load Testing===<br />
As part of our User Test 4, we attempted to have a better understanding of scalability and load handling of our system by conducting a test.<br><br />
To reiterate, performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. In order to conduct the test, the following steps are required.<br />
* Performance Testing<br />
** Identify a system process with a series of activities<br />
** Measure the elapse time of each activity<br />
** Identify the bottleneck which is the single important activity which has highest elapse time <br />
* Scalability Testing<br />
** Increase the number of concurrent connections for the identified activity and measure of elapse time of each connection<br />
** Count the number of concurrent connections possible, within the same approximate amount of elapse time of each connection<br />
* Load Testing<br />
** Measure the elapse time of each connection over a range of concurrent connections, including 1, 25, 50, 75, 100 as markers<br />
<br />
====Difficulty in simulating accurate multiple concurrent connections====<br />
Amongst all the steps involved, it is easiest to conduct performance testing because we have already developed Chapalang Benchmark which will help us measure the elapsed time from the moment the framework receives the command until the output is prepared and sent to the end-user.<br />
<br><br><br />
However, the first challenge appeared when simulating multiple concurrent connections. There were several options that we tried for the simulation, and they include:<br />
* Asynchronous Javascript (AJAX)<br />
We started off with AJAX because we are most familiar with it and it is one of the easiest to implement. However, when we observe the start_time in Chapalang Benchmark, each connect has a different start_time even though it overlaps between the start_time and end_time of the previous connection. <br />
<br><br><br />
At this stage, we cleared our misunderstanding about asynchronous calls that we had all along. While it is capable of initiating multiple asynchronous calls, where each call initiates a new connection, it does not initiate all the calls concurrently. It continues to initiate calls sequentially, but it does not wait for the previously initiated connection to be closed before it initiates the next one.<br />
<br><br><br />
As such, we realized that AJAX will not be able to accurately simulate the same-second concurrent connections that we needed for our test.<br />
* PHP popen()<br />
After some research and tests, we found out popen() which opens a pipe to a process executed by forking the command. It is also possible to create an environment where executions are done in parallel and will be suitable for simulating concurrency.<br />
<br><br><br />
While it is fairly easy to use, it offers only a unidirectional process pipe and hence unable to give us a connection response to confirm the number of concurrent connections registered at the server-side. As such, it is not a suitable tool for our test.<br />
* PHP fsocketopen()<br />
We went back to research for a new solution and it appears that fsocketopen() will be able to help us with concurrency and a bidirectional process pipe. <br />
<br><br><br />
As we developed a simple script to simulate concurrent users, we faced a problem where Apache Web Server crashes at an unexpectedly low number of 96 concurrent connections. After some investigations, we realized that fsocketopen() itself opens the same number of concurrent connections as the number of connections Apache is expected to receive and create. Essentially, there were a doubled number of connections that the server has to create, and a check on the background process on the server-side revealed a total of 156 registered apache processes. <br />
<br><br><br />
This led to some biasness in our test, because the intention was to create concurrency at the receiving end but the execution causes inaccuracies in the results. We attempt to solve it by hosting the wrapper file for fsocketopen() on our localhost machine, but we really wanted to take out the network performance uncertainty of every different users who may be using our services, and normalize it solely based on our system performance.<br />
<br><br><br />
Again, we need a methodology where we can simulate concurrency at the web server, without creating additional connections to execute.<br />
* PHP curl_multi_exec()<br />
Finally, we chanced upon curl_multi_exec() method in PHP 5 documentation manual. Libcurl is a PHP library where it performs a cURL session calling upon an internet or UNIX pointer. Additionally, curl_multi enables us to execute its sub-connections in the stack.<br />
<br><br><br />
This method did exactly what we need; it offers us a single connection, multiple threads on the execution. The overall processing time is also faster than fsocketopen() that we attempted earlier by several times.<br />
<br />
===Personalization Analytics===<br />
The personalized dashboard is an adopted feature at a later stage of the project, and hence the natural difficulty is the time constraints. In the process, we had to go through standard cycle of research, prototypes, implement, integrate and test. Every stage is time-consuming and plagued with problems.<br />
<br><br><br />
More objectively, though we are able to map an analytical process, the most challenging task is identifying a suitable data-drive semantic algorithm which is able to suit our needs. Due to time constraints, our research sources are highly limited to consultations with professors and online research.<br />
<br><br><br />
We spoke to an Adjunct Professor who is also a Consulting Researcher in a government research agency, and he recommended for us to try out <br />
<br />
====Multivariate Distribution-based Clustering====<br />
<br><br />
[[Image:6-bitChapalang1.png|800px]]<br />
<br><br />
The above diagrams illustrates some sample on Multivariate Distribution-based Clustering. Clusters can then easily be defined as objects belonging most likely to the same distribution. A nice property of this approach is that this closely resembles the way artificial data sets are generated: by sampling random objects from a distribution.<br />
<br><br><br />
While the theoretical foundation of these methods is excellent, they suffer from one key problem known as overfitting, unless constraints are put on the model complexity. A more complex model will usually always be able to explain the data better, which makes choosing the appropriate model complexity inherently difficult.<br />
<br><br><br />
Distribution-based clustering is a semantically strong method, as it not only provides you with clusters, but also produces complex models for the clusters that can also capture correlation and independence of attributes. However, using these algorithms puts an extra burden on the user: to choose appropriate data models to optimize, and for many real data sets, there may be no mathematical model available the algorithm is able to optimize<br />
<br><br><br />
In short, we are not able to simply create a system model based on this statistical model for the purpose of our analytics engine. <br />
====Latent Semantic Index (LSI)====<br />
While researching deeper into semantic analysis, we discovered another model which is Latent Semantic Indexing (LSI). LSI is an indexing and retrieval method which uses a mathematical technique called Singular Value Decomposition (SVD) to identify patterns in relationships between terms and concepts contained in an unstructured collection of text. <br />
<br><br><br />
LSI is based on the principle that words that are used in the same contexts tend to have similar meaning, and its key feature is to extract conceptual content of a body of text by establishing associations. The key benefits of LSI is that it overcomes two of the most problematic constraints of Boolean keyword queries, which is synonymy (words with similar meanings) and polysemy (words with more than one meaning).<br />
<br><br><br />
However, LSI was originally a patented property in the late 1980s and till today, there are no opensource materials that we are able to make use of in our project.<br />
====Naïve Bayes Classifier (NBC)====<br />
Finally, we went back to the basics of statistics and found that in Bayesian statistics, it supports the model Naïve Bayes Classifier (NBC). <br />
NBC is a simple probabilistic classifier based on Bayes’ Theorem with strong independence assumptions. Its major and naïve assumption is that all input features are independent and contributes to the object. For example, an orange is “round” and is about 4 inches in “diameter”. While diameter is a measurement unit for rounded objects, and hence a dependence of “diameter” on “round”, NBC assumes that they are independent and may affect the objectivity of the results being oversimplified.<br />
<br><br><br />
While NBC appears to be skewed and bias in most applications, it appears to match what we need because we have an exhaustive list of product or topical categories that we want to make an exhaustive recommendations from. Hence, the constraint of objectivity and dependence in the results does not create a new problem for our analytics engine.<br />
<br><br><br />
Correspondingly, we found an open source script which applies NBC and tested to work. It appears that it is possible to configure NBC to accept different weightage of each independent characteristic. <br />
<br><br><br />
By default, each characteristic has equal weightage with a combined maximum of 1. We found this particularly useful because we are able to adjust the weightage to suit different circumstances. Firstly, the weightage can be adjusted if there is any particular category of products or topics that we want to have higher exposure rates to system users. Hence, this can potentially be a model that suits targeted advertising. Secondly, we are able to incorporate machine learning into the system which skews the weightage according to user’s actual and future activities. Since we capture user activities in our system, the data can be further used to help in the automated skewing of weightage to provide a data-driven model not solely based on historical data but instead, more recent and futuristic data.<br />
<br />
<br />
<br />
<!-- ==Project Achievements==<br />
Methods, technologies, processes, teamwork, etc. which were particularly successful – highlight things which worked very well towards completing the project. A bulleted list of one to two sentences each will do. If there are no achievement, remove this section. --><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Project Management</font></div>=<br />
==Schedule==<br />
[[Image:6-bit_schedule.png|center|600px]]<br />
Detailed Schedule: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Schedule Click Here]<br />
===Schedule Changes===<br />
Throughout the whole project period, there were several scope adjustments and changes and they affect the schedule directly. The following documents some of the noteworthy changes made:<br />
<br><br />
[[Image:60bit_schedulechanges.png|center|500px]]<br />
<br><br />
The tasks and allocated time for the functions removed, which occurs in iteration 14-15 are replaced with the tasks for the newly added tasks.<br />
<br><br />
<br />
<br />
<div style="text-align: right;"><br />
<font size="2">''[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Technical_Overview#Scope_Prioritization Click Here to see how we prioritize our scope!]<br />
<br><br />
Visit http://www.chapalang.com to try these features out yourself! =)''<br />
</font><br />
</div><br />
==Metrics==<br />
===Schedule Metric===<br />
Schedule Metric: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Schedule_Metric Click Here]<br />
<br><br />
Metric Value: [[Image:6bit_schedulevalue.png|500px]]<br />
<br><br><br />
The acceptable range of schedule metric value is between 90% and 110%, catering to the natural inaccuracies in forecasting and actual implementation of time required to complete a task. Most of our schedules are on time, with the exception of 3 iterations.<br />
<br><br><br />
In iteration 6, there was overestimation of the amount of work that we are able to handle within the first 2-week iteration that we have, resulting in an off schedule by 20%. Previously, all our iterations are weekly. The additional tasks allocated for that iteration was to catch up with the scope to be presented for Acceptance Presentation. Many of us were however, busy with the handing over of work at our respective internship workplace and could not meet the original schedule plan. As there is a schedule lapse, we have reviewed the workload per iteration and spaced out the work for future iterations.<br />
<br><br><br />
In iteration 9, there was sufficient time to complete tasks that were planned for the iteration. However, the rush to complete the tasks before User Test 2 has led to lower quality unit testing performed by each developer in the team. This resulted in higher bug counts than usual, and the team had to stop new developers and instead spend the time fixing the bugs. As such, the schedule missed by 30% and we gained a new learning lesson that there should be buffer time for each iteration to cater for unexpected events.<br />
In iteration 15, there were fewer tasks in the iteration than much other previous iteration. However, the schedule was missed by approximately 20%. The team has discussed, and attributed the lapse to project fatigue as well as the submission of projects from other academic modules. While this could be better planned for, it was difficult to forecast the effort required for each member’s other projects. Nonetheless, there was buffer time in the final iteration which was eventually activated to make up for the schedule lapse in iteration 15.<br />
===Bug Metric===<br />
Bug Metric: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Bug_Metric Click Here]<br />
<br><br />
Metric Value: [[Image:6bit_bugvalue.png|500px]]<br />
<br><br><br />
As our acceptable range of bug points is under 20, there are 2 iterations where we have exceeded and remedies were applied as per our action plan. <br />
<br><br><br />
In iteration 11, we have conducted our User Test 2 which has a wide range of functions coverage. As a bigger system tends to also have more bugs, the user test exposes bugs that were previously unknown to us. Immediately after the user test, we have stopped new developments and focused on fixing all the bugs before we continue. Steps were taken to allow more time per task to ensure developments in the team have more time to conduct unit testing before committing their codes. Our team tester has also drafted more comprehensive test cases for her test work.<br />
<br><br><br />
In iteration 15, there was another spike in bugs metric value after the team is gradually facing project fatigue. We accepted the nature that the team has been working on the system for the past 7 months, and that there were many other school projects due during that period. As much as we have justified the cause, we stopped new developments and proceeded with a full day of bugs fixing to ensure the system is functioning properly.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Quality of Product</font></div>=<br />
<br />
{| class="wikitable"<br />
|- style="background:#58ACFA; color:white" <br />
|align="center"| Stage <br />
|align="center"| Specification<br />
|align="center"| Modules<br />
|-<br />
<br />
|rowspan="3"| Project Management<br />
|| Minutes<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Meeting_Minutes Click Here]<br />
|-<br />
<br />
|rowspan="2"| Metrics<br />
|| Schedule metrics: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Meeting_Minutes Click Here]<br />
|-<br />
<br />
|| Bug metrics: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Bug_Metric Click Here]<br />
|-<br />
<br />
|rowspan="4"| Requirements<br />
|| Scope<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables Click Here]<br />
|-<br />
<br />
|| Scope Prioritization<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Technical_Overview#Scope_Prioritization Click Here]<br />
|-<br />
<br />
|rowspan="2"| Problem Scenario<br />
|| As-Is: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#As-Is Click Here]<br />
|-<br />
<br />
|| To-Be: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#To-Be Click Here]<br />
|-<br />
<br />
|rowspan="3"| Analysis<br />
|| Use case<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Use_Case_Diagram Click Here]<br />
|-<br />
<br />
|| Business Process Diagram<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Bug_Metric Click Here]<br />
|-<br />
<br />
|| Screen Shots<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype Click Here]<br />
|-<br />
<br />
|rowspan="4"| Design<br />
|| Logical Diagram<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Logical_Diagram Click Here]<br />
|-<br />
<br />
|| Class Diagram<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Class_Diagram Click Here]<br />
|-<br />
<br />
|| Sequence Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Sequence_Diagram Click Here]<br />
|-<br />
<br />
|| Data Architecture<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Technical_Overview#Data_Architecture Click Here]<br />
|-<br />
|| Testing<br />
|| Test plan<br />
|| [[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Testing Click Here]]<br />
|-<br />
<br />
|}<br />
<br />
==Key Performance Indicators(KPI)==<br />
For the purpose of benchmarking ourselves with specific goals, we have derived on a set of indicators to understand our progress.<br />
<br><br />
[[Image:6bit_kpi.png]]<br />
<br><br />
The following figures are accurate as of 21st November 2012.<br />
<br><br />
505 real members<br />
<br><br />
106 real transactions<br />
<br><br />
189 real physical items sold<br />
<br><br />
$2536.50 real revenue<br />
<br><br />
9 registered and active sellers<br />
<br><br />
62 real products<br />
<br><br />
49 days of operations<br />
<br><br />
<div style="text-align: right;"><br />
<font size="2">''[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes Click Here to see our Learning Outcome!]''</font><br />
</div><br />
<br />
==Testing==<br />
There are a total of 4 User Tests conducted, each with a different coverage and test methodology.<br />
<br><br />
[[Image:6bituser-testingoverview.png|500px]]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing Click Here to view the details of User Test 1]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing Click Here to view the details of User Test 2]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing Click Here to view the details of User Test 3]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing Click Here to view the details of User Test 4]<br />
<br><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Reflection</font></div>=<br />
<br />
==Sponsor Comment==<br />
[https://dl.dropbox.com/u/56071797/Sponsor%28DotCom%29%20Evaluation.doc Click Here to Download our Sponsor's Comments!]<br />
<br />
==Team Reflection==<br />
<div style="text-align: center"><br />
Learning Outcome: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes#Learning_Outcome Click Here]<br />
</div><br />
[[Image:6-bit_teamReflection.png|850px|center]]<br />
==Individual Reflection==<br />
[[Image:6-bit_tianxiangReflection.png|850px|center]]<br />
<br><br />
[[Image:6-bit_geksengReflection.png|850px|left]]<br />
<br><br />
[[Image:6-bit_houstonReflection.png|850px|right]]<br />
<br><br />
[[Image:6-bit_aloysiusReflection.png|850px|center]]<br />
<br><br />
[[Image:6-bit_kennethReflection.png|850px|left]]<br />
<br><br />
[[Image:6-bit_huilingReflection.png|850px|right]]<br />
<br><br />
<br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=File:6-bitChapalang1.png&diff=114776File:6-bitChapalang1.png2012-12-05T07:05:12Z<p>Huiling.ong.2010: </p>
<hr />
<div></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage&diff=114775IS480 Team wiki: 2012T1 6-bit Final Wikipage2012-12-05T07:04:45Z<p>Huiling.ong.2010: /* Scalability and Load Testing */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Project Progress Summary</font></div>=<br />
[https://dl.dropbox.com/u/56071797/Final_Presentation.pdf <font color="#CD004E"><b>Final Presentation Slides</b></font>]<br />
<br />
<br><br />
Our website: http://www.chapalang.com<br />
==Project Overview==<br />
<div style="text-align: center"><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#X-Factors Click Here to View our X-Factors!]<br />
<br><br />
Problem Scenario: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#Problem_Scenario Click Here]<br><br />
''Team 6-bit is formed during the month of May in 2012. We have battled through 16 iterations of planning, designing, constructing and deploying our project, Chapalang and have successfully completed the project, maintaining to our planned scope. Throughout 16 iterations, we have our ups and downs. We faced several unexpected technical challenges which brought down the morale of the team. People with different methods of solving problems created communication problems. However, having a common goal in mind, we endure and frantically looking for workarounds and alternatives to overcome these challenges. We, too, faced some project management challenges where some tasks are not complete on time and caused disturbance to our schedule. These project challenges allow us to iron out our differences and streamlined a better working process. After overcoming these challenges, we had improved ourselves as individuals as well as improved as a team!''<br />
<br />
</div><br />
<br>[[Image:6-bit_poster.jpg|right|450px]]<br />
<br>[http://www.youtube.com/watch?v=8Y8Q9iCKQUY Click here to view our 1min Video Pitch!] <br />
<br><br />
[[Image:6-bit_videopitch.gif|left|450px]]<br />
<br><br><br><br><br><br><br><br><br><br><br><br />
<br><br />
<br />
<br><br />
<br />
<br />
<br />
==Project Challenges==<br />
There are several challenges that the team has faced throughout the IS480 journey. The bulk of Chapalang! is a highly functional and complete solution to a business opportunity of our sponsor, and hence it is not on the basis of a single sophisticated function.<br />
<br><br> <br />
However, it is a cumulatively complex system as it is formed by several functions, and the team has been challenged in different levels on integration issues, and micro-components of the project. One example of the micro-component is Paypal integration where Paypal documentations have been brief and changes are frequent, resulting in integration difficulties but eventually resolved. Another example is on our image cropping tool, where significant amount of time is spent on getting it right especially when none of us in the team has ever ventured into image manipulation.<br />
<br><br><br />
Nonetheless, there are two other independent challenges which introduce much learning lessons for the team.<br />
<br />
===Scalability and Load Testing===<br />
As part of our User Test 4, we attempted to have a better understanding of scalability and load handling of our system by conducting a test.<br><br />
To reiterate, performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. In order to conduct the test, the following steps are required.<br />
* Performance Testing<br />
** Identify a system process with a series of activities<br />
** Measure the elapse time of each activity<br />
** Identify the bottleneck which is the single important activity which has highest elapse time <br />
* Scalability Testing<br />
** Increase the number of concurrent connections for the identified activity and measure of elapse time of each connection<br />
** Count the number of concurrent connections possible, within the same approximate amount of elapse time of each connection<br />
* Load Testing<br />
** Measure the elapse time of each connection over a range of concurrent connections, including 1, 25, 50, 75, 100 as markers<br />
<br />
====Difficulty in simulating accurate multiple concurrent connections====<br />
Amongst all the steps involved, it is easiest to conduct performance testing because we have already developed Chapalang Benchmark which will help us measure the elapsed time from the moment the framework receives the command until the output is prepared and sent to the end-user.<br />
<br><br><br />
However, the first challenge appeared when simulating multiple concurrent connections. There were several options that we tried for the simulation, and they include:<br />
* Asynchronous Javascript (AJAX)<br />
We started off with AJAX because we are most familiar with it and it is one of the easiest to implement. However, when we observe the start_time in Chapalang Benchmark, each connect has a different start_time even though it overlaps between the start_time and end_time of the previous connection. <br />
<br><br><br />
At this stage, we cleared our misunderstanding about asynchronous calls that we had all along. While it is capable of initiating multiple asynchronous calls, where each call initiates a new connection, it does not initiate all the calls concurrently. It continues to initiate calls sequentially, but it does not wait for the previously initiated connection to be closed before it initiates the next one.<br />
<br><br><br />
As such, we realized that AJAX will not be able to accurately simulate the same-second concurrent connections that we needed for our test.<br />
* PHP popen()<br />
After some research and tests, we found out popen() which opens a pipe to a process executed by forking the command. It is also possible to create an environment where executions are done in parallel and will be suitable for simulating concurrency.<br />
<br><br><br />
While it is fairly easy to use, it offers only a unidirectional process pipe and hence unable to give us a connection response to confirm the number of concurrent connections registered at the server-side. As such, it is not a suitable tool for our test.<br />
* PHP fsocketopen()<br />
We went back to research for a new solution and it appears that fsocketopen() will be able to help us with concurrency and a bidirectional process pipe. <br />
<br><br><br />
As we developed a simple script to simulate concurrent users, we faced a problem where Apache Web Server crashes at an unexpectedly low number of 96 concurrent connections. After some investigations, we realized that fsocketopen() itself opens the same number of concurrent connections as the number of connections Apache is expected to receive and create. Essentially, there were a doubled number of connections that the server has to create, and a check on the background process on the server-side revealed a total of 156 registered apache processes. <br />
<br><br><br />
This led to some biasness in our test, because the intention was to create concurrency at the receiving end but the execution causes inaccuracies in the results. We attempt to solve it by hosting the wrapper file for fsocketopen() on our localhost machine, but we really wanted to take out the network performance uncertainty of every different users who may be using our services, and normalize it solely based on our system performance.<br />
<br><br><br />
Again, we need a methodology where we can simulate concurrency at the web server, without creating additional connections to execute.<br />
* PHP curl_multi_exec()<br />
Finally, we chanced upon curl_multi_exec() method in PHP 5 documentation manual. Libcurl is a PHP library where it performs a cURL session calling upon an internet or UNIX pointer. Additionally, curl_multi enables us to execute its sub-connections in the stack.<br />
<br><br><br />
This method did exactly what we need; it offers us a single connection, multiple threads on the execution. The overall processing time is also faster than fsocketopen() that we attempted earlier by several times.<br />
<br />
===Personalization Analytics===<br />
The personalized dashboard is an adopted feature at a later stage of the project, and hence the natural difficulty is the time constraints. In the process, we had to go through standard cycle of research, prototypes, implement, integrate and test. Every stage is time-consuming and plagued with problems.<br />
<br><br><br />
More objectively, though we are able to map an analytical process, the most challenging task is identifying a suitable data-drive semantic algorithm which is able to suit our needs. Due to time constraints, our research sources are highly limited to consultations with professors and online research.<br />
<br><br><br />
We spoke to an Adjunct Professor who is also a Consulting Researcher in a government research agency, and he recommended for us to try out ====Multivariate Distribution-based Clustering====<br />
<br><br />
[[Image:6-bitChapalang1.png|400px]]<br />
<br><br />
The above diagrams illustrates some sample on Multivariate Distribution-based Clustering. Clusters can then easily be defined as objects belonging most likely to the same distribution. A nice property of this approach is that this closely resembles the way artificial data sets are generated: by sampling random objects from a distribution.<br />
<br><br><br />
While the theoretical foundation of these methods is excellent, they suffer from one key problem known as overfitting, unless constraints are put on the model complexity. A more complex model will usually always be able to explain the data better, which makes choosing the appropriate model complexity inherently difficult.<br />
<br><br><br />
Distribution-based clustering is a semantically strong method, as it not only provides you with clusters, but also produces complex models for the clusters that can also capture correlation and independence of attributes. However, using these algorithms puts an extra burden on the user: to choose appropriate data models to optimize, and for many real data sets, there may be no mathematical model available the algorithm is able to optimize<br />
<br><br><br />
In short, we are not able to simply create a system model based on this statistical model for the purpose of our analytics engine. <br />
====Latent Semantic Index (LSI)====<br />
While researching deeper into semantic analysis, we discovered another model which is Latent Semantic Indexing (LSI). LSI is an indexing and retrieval method which uses a mathematical technique called Singular Value Decomposition (SVD) to identify patterns in relationships between terms and concepts contained in an unstructured collection of text. <br />
<br><br><br />
LSI is based on the principle that words that are used in the same contexts tend to have similar meaning, and its key feature is to extract conceptual content of a body of text by establishing associations. The key benefits of LSI is that it overcomes two of the most problematic constraints of Boolean keyword queries, which is synonymy (words with similar meanings) and polysemy (words with more than one meaning).<br />
<br><br><br />
However, LSI was originally a patented property in the late 1980s and till today, there are no opensource materials that we are able to make use of in our project.<br />
====Naïve Bayes Classifier (NBC)====<br />
Finally, we went back to the basics of statistics and found that in Bayesian statistics, it supports the model Naïve Bayes Classifier (NBC). <br />
NBC is a simple probabilistic classifier based on Bayes’ Theorem with strong independence assumptions. Its major and naïve assumption is that all input features are independent and contributes to the object. For example, an orange is “round” and is about 4 inches in “diameter”. While diameter is a measurement unit for rounded objects, and hence a dependence of “diameter” on “round”, NBC assumes that they are independent and may affect the objectivity of the results being oversimplified.<br />
<br><br><br />
While NBC appears to be skewed and bias in most applications, it appears to match what we need because we have an exhaustive list of product or topical categories that we want to make an exhaustive recommendations from. Hence, the constraint of objectivity and dependence in the results does not create a new problem for our analytics engine.<br />
<br><br><br />
Correspondingly, we found an open source script which applies NBC and tested to work. It appears that it is possible to configure NBC to accept different weightage of each independent characteristic. <br />
<br><br><br />
By default, each characteristic has equal weightage with a combined maximum of 1. We found this particularly useful because we are able to adjust the weightage to suit different circumstances. Firstly, the weightage can be adjusted if there is any particular category of products or topics that we want to have higher exposure rates to system users. Hence, this can potentially be a model that suits targeted advertising. Secondly, we are able to incorporate machine learning into the system which skews the weightage according to user’s actual and future activities. Since we capture user activities in our system, the data can be further used to help in the automated skewing of weightage to provide a data-driven model not solely based on historical data but instead, more recent and futuristic data.<br />
<br />
<br />
<br />
<!-- ==Project Achievements==<br />
Methods, technologies, processes, teamwork, etc. which were particularly successful – highlight things which worked very well towards completing the project. A bulleted list of one to two sentences each will do. If there are no achievement, remove this section. --><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Project Management</font></div>=<br />
==Schedule==<br />
[[Image:6-bit_schedule.png|center|600px]]<br />
Detailed Schedule: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Schedule Click Here]<br />
===Schedule Changes===<br />
Throughout the whole project period, there were several scope adjustments and changes and they affect the schedule directly. The following documents some of the noteworthy changes made:<br />
<br><br />
[[Image:60bit_schedulechanges.png|center|500px]]<br />
<br><br />
The tasks and allocated time for the functions removed, which occurs in iteration 14-15 are replaced with the tasks for the newly added tasks.<br />
<br><br />
<br />
<br />
<div style="text-align: right;"><br />
<font size="2">''[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Technical_Overview#Scope_Prioritization Click Here to see how we prioritize our scope!]<br />
<br><br />
Visit http://www.chapalang.com to try these features out yourself! =)''<br />
</font><br />
</div><br />
==Metrics==<br />
===Schedule Metric===<br />
Schedule Metric: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Schedule_Metric Click Here]<br />
<br><br />
Metric Value: [[Image:6bit_schedulevalue.png|500px]]<br />
<br><br><br />
The acceptable range of schedule metric value is between 90% and 110%, catering to the natural inaccuracies in forecasting and actual implementation of time required to complete a task. Most of our schedules are on time, with the exception of 3 iterations.<br />
<br><br><br />
In iteration 6, there was overestimation of the amount of work that we are able to handle within the first 2-week iteration that we have, resulting in an off schedule by 20%. Previously, all our iterations are weekly. The additional tasks allocated for that iteration was to catch up with the scope to be presented for Acceptance Presentation. Many of us were however, busy with the handing over of work at our respective internship workplace and could not meet the original schedule plan. As there is a schedule lapse, we have reviewed the workload per iteration and spaced out the work for future iterations.<br />
<br><br><br />
In iteration 9, there was sufficient time to complete tasks that were planned for the iteration. However, the rush to complete the tasks before User Test 2 has led to lower quality unit testing performed by each developer in the team. This resulted in higher bug counts than usual, and the team had to stop new developers and instead spend the time fixing the bugs. As such, the schedule missed by 30% and we gained a new learning lesson that there should be buffer time for each iteration to cater for unexpected events.<br />
In iteration 15, there were fewer tasks in the iteration than much other previous iteration. However, the schedule was missed by approximately 20%. The team has discussed, and attributed the lapse to project fatigue as well as the submission of projects from other academic modules. While this could be better planned for, it was difficult to forecast the effort required for each member’s other projects. Nonetheless, there was buffer time in the final iteration which was eventually activated to make up for the schedule lapse in iteration 15.<br />
===Bug Metric===<br />
Bug Metric: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Bug_Metric Click Here]<br />
<br><br />
Metric Value: [[Image:6bit_bugvalue.png|500px]]<br />
<br><br><br />
As our acceptable range of bug points is under 20, there are 2 iterations where we have exceeded and remedies were applied as per our action plan. <br />
<br><br><br />
In iteration 11, we have conducted our User Test 2 which has a wide range of functions coverage. As a bigger system tends to also have more bugs, the user test exposes bugs that were previously unknown to us. Immediately after the user test, we have stopped new developments and focused on fixing all the bugs before we continue. Steps were taken to allow more time per task to ensure developments in the team have more time to conduct unit testing before committing their codes. Our team tester has also drafted more comprehensive test cases for her test work.<br />
<br><br><br />
In iteration 15, there was another spike in bugs metric value after the team is gradually facing project fatigue. We accepted the nature that the team has been working on the system for the past 7 months, and that there were many other school projects due during that period. As much as we have justified the cause, we stopped new developments and proceeded with a full day of bugs fixing to ensure the system is functioning properly.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Quality of Product</font></div>=<br />
<br />
{| class="wikitable"<br />
|- style="background:#58ACFA; color:white" <br />
|align="center"| Stage <br />
|align="center"| Specification<br />
|align="center"| Modules<br />
|-<br />
<br />
|rowspan="3"| Project Management<br />
|| Minutes<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Meeting_Minutes Click Here]<br />
|-<br />
<br />
|rowspan="2"| Metrics<br />
|| Schedule metrics: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Meeting_Minutes Click Here]<br />
|-<br />
<br />
|| Bug metrics: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Bug_Metric Click Here]<br />
|-<br />
<br />
|rowspan="4"| Requirements<br />
|| Scope<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables Click Here]<br />
|-<br />
<br />
|| Scope Prioritization<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Technical_Overview#Scope_Prioritization Click Here]<br />
|-<br />
<br />
|rowspan="2"| Problem Scenario<br />
|| As-Is: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#As-Is Click Here]<br />
|-<br />
<br />
|| To-Be: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#To-Be Click Here]<br />
|-<br />
<br />
|rowspan="3"| Analysis<br />
|| Use case<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Use_Case_Diagram Click Here]<br />
|-<br />
<br />
|| Business Process Diagram<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Bug_Metric Click Here]<br />
|-<br />
<br />
|| Screen Shots<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype Click Here]<br />
|-<br />
<br />
|rowspan="4"| Design<br />
|| Logical Diagram<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Logical_Diagram Click Here]<br />
|-<br />
<br />
|| Class Diagram<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Class_Diagram Click Here]<br />
|-<br />
<br />
|| Sequence Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Sequence_Diagram Click Here]<br />
|-<br />
<br />
|| Data Architecture<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Technical_Overview#Data_Architecture Click Here]<br />
|-<br />
|| Testing<br />
|| Test plan<br />
|| [[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Testing Click Here]]<br />
|-<br />
<br />
|}<br />
<br />
==Key Performance Indicators(KPI)==<br />
For the purpose of benchmarking ourselves with specific goals, we have derived on a set of indicators to understand our progress.<br />
<br><br />
[[Image:6bit_kpi.png]]<br />
<br><br />
The following figures are accurate as of 21st November 2012.<br />
<br><br />
505 real members<br />
<br><br />
106 real transactions<br />
<br><br />
189 real physical items sold<br />
<br><br />
$2536.50 real revenue<br />
<br><br />
9 registered and active sellers<br />
<br><br />
62 real products<br />
<br><br />
49 days of operations<br />
<br><br />
<div style="text-align: right;"><br />
<font size="2">''[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes Click Here to see our Learning Outcome!]''</font><br />
</div><br />
<br />
==Testing==<br />
There are a total of 4 User Tests conducted, each with a different coverage and test methodology.<br />
<br><br />
[[Image:6bituser-testingoverview.png|500px]]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing Click Here to view the details of User Test 1]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing Click Here to view the details of User Test 2]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing Click Here to view the details of User Test 3]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing Click Here to view the details of User Test 4]<br />
<br><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Reflection</font></div>=<br />
<br />
==Sponsor Comment==<br />
[https://dl.dropbox.com/u/56071797/Sponsor%28DotCom%29%20Evaluation.doc Click Here to Download our Sponsor's Comments!]<br />
<br />
==Team Reflection==<br />
<div style="text-align: center"><br />
Learning Outcome: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes#Learning_Outcome Click Here]<br />
</div><br />
[[Image:6-bit_teamReflection.png|850px|center]]<br />
==Individual Reflection==<br />
[[Image:6-bit_tianxiangReflection.png|850px|center]]<br />
<br><br />
[[Image:6-bit_geksengReflection.png|850px|left]]<br />
<br><br />
[[Image:6-bit_houstonReflection.png|850px|right]]<br />
<br><br />
[[Image:6-bit_aloysiusReflection.png|850px|center]]<br />
<br><br />
[[Image:6-bit_kennethReflection.png|850px|left]]<br />
<br><br />
[[Image:6-bit_huilingReflection.png|850px|right]]<br />
<br><br />
<br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Technical_Overview&diff=114774IS480 Team wiki: 2012T1 6-bit Technical Overview2012-12-05T06:57:19Z<p>Huiling.ong.2010: /* Staging Area */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Technical Resources</font></div>=<br />
[[Image:6-bit_Technical.png|500px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Data Architecture</font></div>=<br />
[[Image:6-bit_dataarch.png|550px|center]]<br />
<div style="text-align: center ">In this data architecture, there are 2 Operational Data Sources (ODS), 4 data stores and 1 consuming portal which is chapalang.com.</div><br />
==Operational Data Source (ODS)==<br />
Operational data are obtained through Facebook Graph API, which provides data such as user’s posts, likes, friends and basic information, and stored in the Staging Area. Additionally, user activities data captured on the portal are also stored Staging Area for further Extract, Transform, Load (ETL) cycle.<br />
==Staging Area==<br />
Each data store is hosted independently by design. The Staging Area data store is required to store crawled data from ODS. Due to the nature of crawling which is highly dependent on the login frequency and concurrency of users, the Staging Area should be independently hosted to avoid usage spikes to cause operational problems. <br />
<br><br><br />
Additionally, it will be configured with writing performance optimization since this is the primary activity. Hence, Staging Area is not designed to be normalized, and will instead have a database structure that is matching to the incoming data structure.<br />
<br><br><br />
There is also a Time To Live (TTL) to provide suitable expiry of the data stored on the Staging Area. As the objective of each crawling execution is to obtain the latest data of a user, hence the staging area should not store outdated data. For the purpose of Chapalang! operations in the rudimentary stage, data on the Staging Area is dropped each time a user logs in and be replaced with new data.<br />
<br />
==Data Warehouse==<br />
After the storage of crawled data into the Staging Area, the data go through an ETL cycle to be archived in a Data Warehouse. A Data Warehouse is independently hosted as it is optimized for storage instead of read or write activities.<br />
<br><br><br />
The purpose of the Data Warehouse is for storage of all data for an indefinite period of time, or otherwise dropped at the discretion of the administrator should it be determined to be outdated and irrelevant. As such, Data Warehouse has a highly normalized database structure for the purpose of storage and removal of redundancy in data. With a highly normalized structure, it is usually sub-optimal for Online Transaction Processing (OLTP) purposes.<br />
==Data Mart (OLTP)==<br />
It may be too intensive to work directly on a Data Warehouse which is optimized for storage by the design of a highly normalized database structure, and it will cause high resources consumption and long query lead-time due to the multiple joins, re-indexing and sub-queries. Similarly, an OLTP Data Mart will be hosted independently to ensure isolated uptime and performance reliability for the operations of our portal, Chapalang.com.<br />
<br><br><br />
As such, materialized views of denormalized data, possibly of selective time periods, are created for the purpose of transactional processing. Denormalization introduces redundant data or data groups to optimize read performance of a database. These materialized views will periodically be replaced and stored in a OLTP Data Mart, which supports the direct transactional queries of the portal.<br />
==Data Mart (OLAP)==<br />
Online Analytical Processing (OLAP) supports the basis of Chapalang Analytics, a set of Business Intelligence and Analytics tools which performs analysis of data collected about a user from various ODS. <br />
<br><br><br />
Chapalang Analytics predicts user behaviours, personalities and preferences, and matches them with generated set of meta data tags of products or discussion content, before finally generating recommendations of products or content suitable for a user and publishing to the user’s view.<br />
<br><br><br />
In its process of generating recommendations, Chapalang Analytics adopt a combination of analytical techniques such as Sentimental Analysis and Rule-Based Analysis. Recommendations are generated on-the-fly, integrating multiple sources of data in large amount, as and when users hit on a particular page which requires content filtering in favour of recommendations. Hence, it requires high amount of computing resources on-demand supports for an OLAP Data Mart to be hosted independently.<br />
<br><br><br />
In addition, another advantage of hosting the OLAP Data Mart independently is that in the event of any unusual failure or deteriorating performance of the OLAP Data Mart for any reason, the OLAP Data Mart will continue to function, generating sub-optimal random recommendations for the users while the administrator is notified about the anomaly. Therefore, it reduces the impact of single point of failure and isolates the bottleneck in the event of catastrophic occurrences.<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >System Architecture</font></div>=<br />
In our setup, database, web and application servers are running independently to offer performance optimization and future scalability.<br />
<br><br />
[[Image:6-bit_systemarch.png|550px|center]]<br />
There is total of 4 database servers, running off virtual machines of a single power server. The purpose of segregation is to leverage on different configurations of database servers, to optimize for storage or for performance. In this manner, database servers which consume high resources for indexing or creating views from big data will not cannibalize the resources to be reserved or prioritized for operational purposes. <br />
<br><br><br />
Additionally, virtual servers allow advance network configurations which enable each virtual machine to have custom network facilities. Bandwidth shaping can be design to place operational and analytical servers on different network to avoid cross interference in performance.<br />
<br><br><br />
Correspondingly, there is an Analytics Server which performs complex analysis on the data from Operational Data Sources. It is independent because it is expected to perform data analysis on-the-fly which takes up high amount of resources.<br />
<br><br><br />
Lastly, there is only 1 web server at this stage. The web server stores the application files, as well as media files uploaded by user. It can be further scaled up to have more web servers with a load balancer, and another storage server, when consumption of the service grows. <br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Scope Prioritization</font></div>=<br />
As we progress in the development, we will conduct several rounds of tests and consultation with stakeholders. In the process, many recommendations are offered and we need a methodology to evaluate what we can adopt, what we have to reject, and what we may have to sacrifice if we were to adopt something.<br />
<br><br />
Hence, we have come up with a Scope Prioritization Decision Model to help us cope with the scope changes.<br />
==Model==<br />
[[Image:6-bit_Scope_Prior.png|500px|center]]<br />
<br><br />
The first step in our scope prioritization is to list down all proposed functions, and categorize them into 3 groups. Group A classifies the basic utility functions, Group B consists of main features, and Group C groups the supplementary features. The categorization of features into different groups, allow us to be more objective in deciding what features offers more value.<br />
<br />
==Decision Table==<br />
[[Image:6-bit_DecisionTable.png|500px|center]]<br><br />
Using the table, we evaluate a group of functions based on a set of criteria which includes the following:<br />
* Time required<br />
* Ease of implementation<br />
* Combined risk<br />
* Aligned with business strategy (whether it matches with existing strategy)<br />
* Provide competitive advantage (whether it provides additional value to existing strategy)<br />
For each function-criteria box, we will assign a rank value between 1 and 3. Finally, we will tabulate the scores to calculate the overall benefit. The overall benefit value will be helpful in deciding to add or drop a proposed function.</div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit&diff=114773IS480 Team wiki: 2012T1 6-bit2012-12-05T06:56:28Z<p>Huiling.ong.2010: /* Personalized dashboard */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Current Status</font></div>=<br />
<br />
{| class="wikitable" cellpadding="15"<br />
<br />
|-<br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 46%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Current Iteration</b> <br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 50%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Meeting Status</b> <br />
|-<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Iteration Number :''' <br />
16 *Final Iteration*<br />
<br><br />
'''Iteration Start Date : '''<br />
24 November 2012<br />
<br><br />
'''Iteration End Date :'''<br />
3 December 2012<br />
<br><br />
'''Iteration Task :'''<br />
<br><br />
1. Final Presentation<br />
<br><br />
2. Poster Day<br />
<br><br />
<br />
<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Weekly Meeting Schedule'''<br />
<br><br />
Every Monday, Wednesday, Friday<br />
<br><br />
SIS Analytics Kitchen<br />
<br><br />
12pm to 3pm<br />
<br><br />
<br />
'''Weekly Supervisor Meeting'''<br />
<br><br />
Every Monday<br />
<br><br />
2pm to 3pm<br />
|}<br />
<div style="text-align: right;"><br />
<font size="2">''Last Update: 28 November 2012''</font><br />
</div><br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Team</font></div>=<br />
[[Image:6-bitTeamMembers.png|alt=text|6-bitTeamMembers|centre|650px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Project: Chapalang</font></div>=<br />
<div style="text-align: center"><font color="#00BFFF">''Talk, Buy, Sell, Share, all on Chapalang!''</font></div><br />
<font color="#FE2EF7">Chapalang!</font> is a social utility that connects people with friends and new friends by offering a place for exchanging ideas and information on its public domain. People use our discussion forums to write HOWTOs, share findings, ask questions, comment on news, and many more.<br />
<br><br />
<font color="#FE2EF7">Chapalang!</font> also features a social marketplace for you to buy online, and participate in mass orders in a convenient and reliable way.<br />
<br><br />
Best of all, you can browse wish lists of your friends to know what are the right things to buy on special occasions. You could buy the gift on <br />
<font color="#FE2EF7">Chapalang!</font> and have it sent to their doorsteps, or organize a Gift Sharing campaign to share the costs of gift with other friends.<br />
<br />
[[Image:chapalangprocesses.png|1100px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Main Features</font></div>=<br />
[[Image:ChapalangLogo.png|left|150px]]<br />
<br><br />
<i>proposes the following unique features:</i><br />
<br><br />
[[Image:6-bitGroupbuyprocess.png|center|1000px]]<br />
<br><br />
<b>Gifts Sharing</b> : <br />
<br><br />
Gifting can be simple or collective. A simple gift is purchased when a user pays for the full costs of the gift, and states the recipient’s contact details upon checkout. Chapalang! will contact the recipient for their address, and subsequently fulfil the order with the delivery of goods.<br />
<br><br />
<br><br />
A collective gift is purchased when a user takes on the role of an organizer and initiates a Gift Sharing Campaign. He will select a product from a user’s wish list, or any other product in the marketplace, and designate it to be the gift to be shared. He will also decide on the product options, if any, as well as the delivery method. <br />
<br><br />
<br><br />
Thereafter, he can invite a list of mutual friends whom he wants to share the gift with. The invitees will be informed of the campaign via a notification, and will be able to contribute any varying amount on the campaign page. They will also be able to hide their amount of contribution, or even hide their contribution record from public. Upon successfully raising the target amount which is the price of the gift, an email will be sent to the recipient for him/her to update their address for fulfilment and delivery.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitMassorderprocess.png|center|1000px]]<br />
<b>Mass orders</b> : <br />
<br>Mass Orders (MO) should be structured and organized, just like a regular product item in the marketplace. <br />
<br><br />
<br><br />
When creating an MO, the buyer will input the price, description, minimum collective quantity for the MO to go through, the maximum collective quantity accepted for the MO if it’s a limited quantity offer, as well as the start and end period of the MO. An MO organizer can be an individual or a company. The organizer will be able to invite his/her friends, or regular customers to the MO. <br />
<br><br />
<br><br />
Participants of an MO will be able to view the MO page, enter a desired quantity and checkout. In the checkout process, participants will be required to enter their delivery address and choose their preferred shipping method. Payment is made upon ordering, safeguarded by the esrow service, and will be paid to the sellers if the MO is successful. In the event that MO is unsuccessful or cancelled, full amount of their orders will be refunded to all participants automatically.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitEscrowprocess.png|centre|1000px]]<br />
<b>Escrow</b> : <br />
<br><br />
In most other agent websites, buyers either pay to sellers directly or buyers pay to the agent and agent will pay the buyers 30 days later. We will turn this credit period to the advantage of buyers and sellers, introducing assurance.<br />
<br><br><br />
In any transaction on Chapalang!, the buyer will pay to Chapalang! directly. Sellers are notified of the receipt of payment, and will proceed to ship the item out to the buyer. Upon receipt of the order, buyers will revisit Chapalang! and indicate that the goods are received satisfactorily, and Chapalang! will then pay the sellers in the next 3 days. However, if there is no response or dispute from the buyers within 30 days, the order is assumed to be satisfactorily fulfilled and the payment will be released to the seller. In the event of disputes, buyers and sellers are encouraged to negotiate for a recovery, or in the case of an exhausted negotiation, Chapalang! may issue a full or partial refund to the customers.<br />
<br><br><br />
Systematically, the Chapalang! system will support this this use case through a series of functions. <br />
*Firstly, the system will support a goods receipt acknowledgement process, recording the goods receipt, triggering of payment activities to sellers upon 30 days grace or upon the record of goods receipt. <br />
*Secondly, sellers should be able to see their sales and know how much they will be receiving from Chapalang! and when. <br />
*Thirdly, there should be a messaging channel to facilitate communications between the buyer and seller<br />
*Fourthly, there should be a refund method to allow sellers to refund a transaction should be accept that he’s unable to recover or fulfil the order<br />
*Lastly, administrator of Chapalang! should be able to see a list of fulfilled, or assumed fulfilled transactions ready for payment to the sellers<br />
<br />
<div style="text-align: right;"><br />
<font size="2">''Prototype of Chapalang's Features: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype Click Here]''</font><br />
</div><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Low Level Functions</font></div>=<br />
==Web Parser==<br />
As an interactive feature, URLs shared on Chapalang! will offer a preview which contains the site title, url, image and description. This should reflect the final URL, instead of any redirecting URL at a higher level.<br />
<br><br><br />
The picking of appropriate objects (title, url, image or description) is important, where standardized Open Graph (OG) protocol meta data of a webpage will be prioritized, before seeking through the other HTML components for referencing objects.<br />
==Private Message==<br />
[[Image:6-bit_message.png|center|600px]]<br />
There should be an in-system communication channel for general users, buyers and sellers. Potential buyers can clarify product specifications with sellers, sellers can confirm delivery address with buyers in case of anomalies, and general users can use it for chatting purposes.<br />
<br><br />
<br>It should be able to perform CRUD of messages between 2 users, in a conversational format. Users are notified via email whenever they receive a message. They will also be able to see past messages exchanged, in a single conversation page.<br />
==Image Cropping Tool==<br />
As all images uploaded by users can be of different dimensions, our system will need a tool to automatically resize and crop away unimportant parts to fit the image dimensions on different pages.<br />
<br><br><br />
Hence, the Image Cropping Tool will help us with automatically resizing an image to the most suitable resolution, before cropping away any extended sides and focus on the centre of the image which is usually the most important message. This tool will be applied throughout the entire platform, on both discussion forums and marketplace.<br />
<br />
==Notifications==<br />
[[Image:6-bit_notification.png|center|300px]]<br />
Users should be appropriately notified on any activities concerning them. They will have a new notifications whenever someone replies to their post, whenever a friend is following them in Chapalang!, or when a product purchased is being shipped, et cetera.<br />
<br><br />
<br><br />
Notification entries should link them to appropriate pages for follow-up actions or even simply viewing more details of the notification. Each in-system notification should also be tied to an email notification for a timelier update to users, and users should have the ability to modify their notifications settings for privacy or information flood control.<br />
<br />
==Search function==<br />
[[Image:6-bit_search.png|center|600px]]<br />
There are many content types on Chapalang!, which includes people, messages, products, posts, et cetera. These content types should be searchable for the purpose of conveniently accessing specific content.<br />
==Profile page==<br />
[[Image:6-bit_profilepage.png|center|600px]]<br />
Every user will have a dedicated profile page, which contains their profile picture, basic particulars, activities and friends. This will create a more social environment, where information of a user is shared among friends.<br />
==Management pages==<br />
[[Image:6-bit_management.png|center|250px]]<br />
There should be a set of management pages, for the management of sales, orders or products. These pages will be able to perform basic CRUD functions, as well as other functions allowing appropriate manipulation of an activity. For example, Manage Sales will allow sellers to view transactional details as well as updating shipping details when an order is fulfilled. On the other hand, Manage Orders will allow buyers to review their purchases and be informed whether their orders are fulfilled. Correspondingly, Manage Products will allow the sellers administer all aspects of a product, from its description, images, pricing, to its options and shipping methods.<br />
<br />
==Settings pages==<br />
[[Image:6-bit_settings.png|center|600px]]<br />
There will be separate pages for Accounts Settings, Privacy Settings and Notifications Settings. Firstly, Account Settings will allow a user to change their basic information imported from Facebook. Secondly, Privacy Settings will provide the option to show or hide certain sensitive information that a user may choose not to show in the public. Lastly, Notifications Settings will help the users manage the quantity and quality of notifications that they receive as they might choose not to be informed of certain activities to prevent information overload.<br />
==Personalized dashboard==<br />
[[Image:6-bit_personalizeddb.png|center|600px]]<br />
A dashboard is the first page the user will see upon login, and will contain a mash up of content from various components on the portal. The content published to the dashboard is personalized through stratification supported by data-driven analytics.<br />
<br><br />
<br><br />
The dashboard will contain the following data:<br />
* Relevant topics from subscribed forums<br />
* Featured discussions<br />
* Product recommendations generated by analytics<br />
* Recent purchases made by friends<br />
* Featured mass orders recommendations generated by analytics<br />
* Seasonal or holidays promotional products recommendations generated by analytics<br />
* New arrival products recommendations generated by analytics<br />
* Reminders on upcoming special dates, friends’ birthdays, and activity invites<br />
The dashboard has a 3-step approach in deriving personalized content. <br />
<br><br><br />
Firstly, a set of meta data describing a user is generated. We will perform sentimental analysis with user activities, Facebook status feed and likes, as data input, and generate the meta data using Chapalang Analytics engine.<br />
<br><br />
Secondly, another set of meta data describing a product is also generated. We have developed an algorithm where it will take in all product-related attributes as input, and generate a list of meta data after removing language prepositions with emphasis on extracting nouns.<br />
Lastly, both set of meta data are matched to produce a list of recommendations by using the Naïve Bayes Classifier which applies Bayes’ Theorem with strong naïve independent assumptions. More information on the underlying analytics can be found in the Chapalang Analytics section.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Sponsor</font></div>=<br />
[[Image:Dotcom_Logo.jpg|left]]<br />
<b>Chapalang</b> is a self-proposed project for DotCom Enterprise. Upon successful development, DotCom will commercialize the project for live operations. Mr. Eric Chew, Special Projects Manager will be the primary contact from DotCom. Throughout the development and implementation stages, our team will deploy the project on the live systems provided by DotCom.<br />
<div style="margin-bottom:30px;><br />
<br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Academic Milestones</font></div>=<br />
==Acceptance==<br />
[[Media:Chapalang_Acceptance_Slides.pdf|<font color="#CD004E"> Acceptance Presentation Slides]]<br />
==Midterm==<br />
[[IS480_Team_wiki:_2012T1_6-bit_Midterm_Wikipage | <font color="#CD004E"><b>Mid Term Wiki</b></font>]]<br />
<br><br />
[[Media:Chapalang_Midterm_Slides.pdf|<font color="#CD004E"> Midterm Presentation Slides]]<br />
==Final==<br />
[https://dl.dropbox.com/u/56071797/Final_Presentation.pdf <font color="#CD004E"><b>Final Presentation Slides</b></font>]</div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=File:6-bitEscrowprocess.png&diff=114771File:6-bitEscrowprocess.png2012-12-05T06:54:14Z<p>Huiling.ong.2010: uploaded a new version of "Image:6-bitEscrowprocess.png"</p>
<hr />
<div></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=File:6-bitMassorderprocess.png&diff=114770File:6-bitMassorderprocess.png2012-12-05T06:54:12Z<p>Huiling.ong.2010: uploaded a new version of "Image:6-bitMassorderprocess.png"</p>
<hr />
<div></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=File:6-bitGroupbuyprocess.png&diff=114768File:6-bitGroupbuyprocess.png2012-12-05T06:53:41Z<p>Huiling.ong.2010: uploaded a new version of "Image:6-bitGroupbuyprocess.png"</p>
<hr />
<div></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit&diff=114731IS480 Team wiki: 2012T1 6-bit2012-12-05T02:32:50Z<p>Huiling.ong.2010: /* Final */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Current Status</font></div>=<br />
<br />
{| class="wikitable" cellpadding="15"<br />
<br />
|-<br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 46%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Current Iteration</b> <br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 50%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Meeting Status</b> <br />
|-<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Iteration Number :''' <br />
16 *Final Iteration*<br />
<br><br />
'''Iteration Start Date : '''<br />
24 November 2012<br />
<br><br />
'''Iteration End Date :'''<br />
3 December 2012<br />
<br><br />
'''Iteration Task :'''<br />
<br><br />
1. Final Presentation<br />
<br><br />
2. Poster Day<br />
<br><br />
<br />
<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Weekly Meeting Schedule'''<br />
<br><br />
Every Monday, Wednesday, Friday<br />
<br><br />
SIS Analytics Kitchen<br />
<br><br />
12pm to 3pm<br />
<br><br />
<br />
'''Weekly Supervisor Meeting'''<br />
<br><br />
Every Monday<br />
<br><br />
2pm to 3pm<br />
|}<br />
<div style="text-align: right;"><br />
<font size="2">''Last Update: 28 November 2012''</font><br />
</div><br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Team</font></div>=<br />
[[Image:6-bitTeamMembers.png|alt=text|6-bitTeamMembers|centre|650px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Project: Chapalang</font></div>=<br />
<div style="text-align: center"><font color="#00BFFF">''Talk, Buy, Sell, Share, all on Chapalang!''</font></div><br />
<font color="#FE2EF7">Chapalang!</font> is a social utility that connects people with friends and new friends by offering a place for exchanging ideas and information on its public domain. People use our discussion forums to write HOWTOs, share findings, ask questions, comment on news, and many more.<br />
<br><br />
<font color="#FE2EF7">Chapalang!</font> also features a social marketplace for you to buy online, and participate in mass orders in a convenient and reliable way.<br />
<br><br />
Best of all, you can browse wish lists of your friends to know what are the right things to buy on special occasions. You could buy the gift on <br />
<font color="#FE2EF7">Chapalang!</font> and have it sent to their doorsteps, or organize a Gift Sharing campaign to share the costs of gift with other friends.<br />
<br />
[[Image:chapalangprocesses.png|1100px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Main Features</font></div>=<br />
[[Image:ChapalangLogo.png|left|150px]]<br />
<br><br />
<i>proposes the following unique features:</i><br />
<br><br />
[[Image:6-bitGroupbuyprocess.png|center|1000px]]<br />
<br><br />
<b>Gifts Sharing</b> : <br />
<br><br />
Gifting can be simple or collective. A simple gift is purchased when a user pays for the full costs of the gift, and states the recipient’s contact details upon checkout. Chapalang! will contact the recipient for their address, and subsequently fulfil the order with the delivery of goods.<br />
<br><br />
<br><br />
A collective gift is purchased when a user takes on the role of an organizer and initiates a Gift Sharing Campaign. He will select a product from a user’s wish list, or any other product in the marketplace, and designate it to be the gift to be shared. He will also decide on the product options, if any, as well as the delivery method. <br />
<br><br />
<br><br />
Thereafter, he can invite a list of mutual friends whom he wants to share the gift with. The invitees will be informed of the campaign via a notification, and will be able to contribute any varying amount on the campaign page. They will also be able to hide their amount of contribution, or even hide their contribution record from public. Upon successfully raising the target amount which is the price of the gift, an email will be sent to the recipient for him/her to update their address for fulfilment and delivery.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitMassorderprocess.png|center|1000px]]<br />
<b>Mass orders</b> : <br />
<br>Mass Orders (MO) should be structured and organized, just like a regular product item in the marketplace. <br />
<br><br />
<br><br />
When creating an MO, the buyer will input the price, description, minimum collective quantity for the MO to go through, the maximum collective quantity accepted for the MO if it’s a limited quantity offer, as well as the start and end period of the MO. An MO organizer can be an individual or a company. The organizer will be able to invite his/her friends, or regular customers to the MO. <br />
<br><br />
<br><br />
Participants of an MO will be able to view the MO page, enter a desired quantity and checkout. In the checkout process, participants will be required to enter their delivery address and choose their preferred shipping method. Payment is made upon ordering, safeguarded by the esrow service, and will be paid to the sellers if the MO is successful. In the event that MO is unsuccessful or cancelled, full amount of their orders will be refunded to all participants automatically.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitEscrowprocess.png|centre|1000px]]<br />
<b>Escrow</b> : <br />
<br><br />
In most other agent websites, buyers either pay to sellers directly or buyers pay to the agent and agent will pay the buyers 30 days later. We will turn this credit period to the advantage of buyers and sellers, introducing assurance.<br />
<br><br><br />
In any transaction on Chapalang!, the buyer will pay to Chapalang! directly. Sellers are notified of the receipt of payment, and will proceed to ship the item out to the buyer. Upon receipt of the order, buyers will revisit Chapalang! and indicate that the goods are received satisfactorily, and Chapalang! will then pay the sellers in the next 3 days. However, if there is no response or dispute from the buyers within 30 days, the order is assumed to be satisfactorily fulfilled and the payment will be released to the seller. In the event of disputes, buyers and sellers are encouraged to negotiate for a recovery, or in the case of an exhausted negotiation, Chapalang! may issue a full or partial refund to the customers.<br />
<br><br><br />
Systematically, the Chapalang! system will support this this use case through a series of functions. <br />
*Firstly, the system will support a goods receipt acknowledgement process, recording the goods receipt, triggering of payment activities to sellers upon 30 days grace or upon the record of goods receipt. <br />
*Secondly, sellers should be able to see their sales and know how much they will be receiving from Chapalang! and when. <br />
*Thirdly, there should be a messaging channel to facilitate communications between the buyer and seller<br />
*Fourthly, there should be a refund method to allow sellers to refund a transaction should be accept that he’s unable to recover or fulfil the order<br />
*Lastly, administrator of Chapalang! should be able to see a list of fulfilled, or assumed fulfilled transactions ready for payment to the sellers<br />
<br />
<div style="text-align: right;"><br />
<font size="2">''Prototype of Chapalang's Features: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype Click Here]''</font><br />
</div><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Low Level Functions</font></div>=<br />
==Web Parser==<br />
As an interactive feature, URLs shared on Chapalang! will offer a preview which contains the site title, url, image and description. This should reflect the final URL, instead of any redirecting URL at a higher level.<br />
<br><br><br />
The picking of appropriate objects (title, url, image or description) is important, where standardized Open Graph (OG) protocol meta data of a webpage will be prioritized, before seeking through the other HTML components for referencing objects.<br />
==Private Message==<br />
[[Image:6-bit_message.png|center|600px]]<br />
There should be an in-system communication channel for general users, buyers and sellers. Potential buyers can clarify product specifications with sellers, sellers can confirm delivery address with buyers in case of anomalies, and general users can use it for chatting purposes.<br />
<br><br />
<br>It should be able to perform CRUD of messages between 2 users, in a conversational format. Users are notified via email whenever they receive a message. They will also be able to see past messages exchanged, in a single conversation page.<br />
==Image Cropping Tool==<br />
As all images uploaded by users can be of different dimensions, our system will need a tool to automatically resize and crop away unimportant parts to fit the image dimensions on different pages.<br />
<br><br><br />
Hence, the Image Cropping Tool will help us with automatically resizing an image to the most suitable resolution, before cropping away any extended sides and focus on the centre of the image which is usually the most important message. This tool will be applied throughout the entire platform, on both discussion forums and marketplace.<br />
<br />
==Notifications==<br />
[[Image:6-bit_notification.png|center|300px]]<br />
Users should be appropriately notified on any activities concerning them. They will have a new notifications whenever someone replies to their post, whenever a friend is following them in Chapalang!, or when a product purchased is being shipped, et cetera.<br />
<br><br />
<br><br />
Notification entries should link them to appropriate pages for follow-up actions or even simply viewing more details of the notification. Each in-system notification should also be tied to an email notification for a timelier update to users, and users should have the ability to modify their notifications settings for privacy or information flood control.<br />
<br />
==Search function==<br />
[[Image:6-bit_search.png|center|600px]]<br />
There are many content types on Chapalang!, which includes people, messages, products, posts, et cetera. These content types should be searchable for the purpose of conveniently accessing specific content.<br />
==Profile page==<br />
[[Image:6-bit_profilepage.png|center|600px]]<br />
Every user will have a dedicated profile page, which contains their profile picture, basic particulars, activities and friends. This will create a more social environment, where information of a user is shared among friends.<br />
==Management pages==<br />
[[Image:6-bit_management.png|center|250px]]<br />
There should be a set of management pages, for the management of sales, orders or products. These pages will be able to perform basic CRUD functions, as well as other functions allowing appropriate manipulation of an activity. For example, Manage Sales will allow sellers to view transactional details as well as updating shipping details when an order is fulfilled. On the other hand, Manage Orders will allow buyers to review their purchases and be informed whether their orders are fulfilled. Correspondingly, Manage Products will allow the sellers administer all aspects of a product, from its description, images, pricing, to its options and shipping methods.<br />
<br />
==Settings pages==<br />
[[Image:6-bit_settings.png|center|600px]]<br />
There will be separate pages for Accounts Settings, Privacy Settings and Notifications Settings. Firstly, Account Settings will allow a user to change their basic information imported from Facebook. Secondly, Privacy Settings will provide the option to show or hide certain sensitive information that a user may choose not to show in the public. Lastly, Notifications Settings will help the users manage the quantity and quality of notifications that they receive as they might choose not to be informed of certain activities to prevent information overload.<br />
==Personalized dashboard==<br />
[[Image:6-bit_personalizeddb.png|center|600px]]<br />
A dashboard is the first page the user will see upon login, and will contain a mash up of content from various components on the portal. The content published to the dashboard is personalized through stratification supported by data-driven analytics.<br />
<br><br />
<br><br />
The dashboard will contain the following data:<br />
* Relevant topics from subscribed forums<br />
* Featured discussions<br />
* Product recommendations generated by analytics<br />
* Recent purchases made by friends<br />
* Featured mass orders recommendations generated by analytics<br />
* Seasonal or holidays promotional products recommendations generated by analytics<br />
* New arrival products recommendations generated by analytics<br />
* Reminders on upcoming special dates, friends’ birthdays, and activity invites<br />
The dashboard has a 2-step approach in deriving personalized content. Firstly, a set of meta data describing a user is generated. Secondly, another set of meta data describing a product is also generated. Subsequently, both set of meta data are matched to produce a list of recommendations.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Sponsor</font></div>=<br />
[[Image:Dotcom_Logo.jpg|left]]<br />
<b>Chapalang</b> is a self-proposed project for DotCom Enterprise. Upon successful development, DotCom will commercialize the project for live operations. Mr. Eric Chew, Special Projects Manager will be the primary contact from DotCom. Throughout the development and implementation stages, our team will deploy the project on the live systems provided by DotCom.<br />
<div style="margin-bottom:30px;><br />
<br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Academic Milestones</font></div>=<br />
==Acceptance==<br />
[[Media:Chapalang_Acceptance_Slides.pdf|<font color="#CD004E"> Acceptance Presentation Slides]]<br />
==Midterm==<br />
[[IS480_Team_wiki:_2012T1_6-bit_Midterm_Wikipage | <font color="#CD004E"><b>Mid Term Wiki</b></font>]]<br />
<br><br />
[[Media:Chapalang_Midterm_Slides.pdf|<font color="#CD004E"> Midterm Presentation Slides]]<br />
==Final==<br />
[https://dl.dropbox.com/u/56071797/Final_Presentation.pdf <font color="#CD004E"><b>Final Presentation Slides</b></font>]</div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage&diff=114730IS480 Team wiki: 2012T1 6-bit Final Wikipage2012-12-05T02:32:30Z<p>Huiling.ong.2010: /* Project Progress Summary */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Project Progress Summary</font></div>=<br />
[https://dl.dropbox.com/u/56071797/Final_Presentation.pdf <font color="#CD004E"><b>Final Presentation Slides</b></font>]<br />
<br />
<br><br />
Our website: http://www.chapalang.com<br />
==Project Overview==<br />
<div style="text-align: center"><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#X-Factors Click Here to View our X-Factors!]<br />
<br><br />
Problem Scenario: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#Problem_Scenario Click Here]<br><br />
''Team 6-bit is formed during the month of May in 2012. We have battled through 16 iterations of planning, designing, constructing and deploying our project, Chapalang and have successfully completed the project, maintaining to our planned scope. Throughout 16 iterations, we have our ups and downs. We faced several unexpected technical challenges which brought down the morale of the team. People with different methods of solving problems created communication problems. However, having a common goal in mind, we endure and frantically looking for workarounds and alternatives to overcome these challenges. We, too, faced some project management challenges where some tasks are not complete on time and caused disturbance to our schedule. These project challenges allow us to iron out our differences and streamlined a better working process. After overcoming these challenges, we had improved ourselves as individuals as well as improved as a team!''<br />
<br />
</div><br />
<br>[[Image:6-bit_poster.jpg|right|450px]]<br />
<br>[http://www.youtube.com/watch?v=8Y8Q9iCKQUY Click here to view our 1min Video Pitch!] <br />
<br><br />
[[Image:6-bit_videopitch.gif|left|450px]]<br />
<br><br><br><br><br><br><br><br><br><br><br><br />
<br><br />
<br />
<br><br />
<br />
<br />
<br />
==Project Challenges==<br />
There are several challenges that the team has faced throughout the IS480 journey. The bulk of Chapalang! is a highly functional and complete solution to a business opportunity of our sponsor, and hence it is not on the basis of a single sophisticated function.<br />
<br><br> <br />
However, it is a cumulatively complex system as it is formed by several functions, and the team has been challenged in different levels on integration issues, and micro-components of the project. One example of the micro-component is Paypal integration where Paypal documentations have been brief and changes are frequent, resulting in integration difficulties but eventually resolved. Another example is on our image cropping tool, where significant amount of time is spent on getting it right especially when none of us in the team has ever ventured into image manipulation.<br />
<br><br><br />
Nonetheless, there are two other independent challenges which introduce much learning lessons for the team.<br />
<br />
===Scalability and Load Testing===<br />
As part of our User Test 4, we attempted to have a better understanding of scalability and load handling of our system by conducting a test.<br><br />
To reiterate, performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. In order to conduct the test, the following steps are required.<br />
* Performance Testing<br />
** Identify a system process with a series of activities<br />
** Measure the elapse time of each activity<br />
** Identify the bottleneck which is the single important activity which has highest elapse time <br />
* Scalability Testing<br />
** Increase the number of concurrent connections for the identified activity and measure of elapse time of each connection<br />
** Count the number of concurrent connections possible, within the same approximate amount of elapse time of each connection<br />
* Load Testing<br />
** Measure the elapse time of each connection over a range of concurrent connections, including 1, 25, 50, 75, 100 as markers<br />
<br />
====Difficulty in simulating accurate multiple concurrent connections====<br />
Amongst all the steps involved, it is easiest to conduct performance testing because we have already developed Chapalang Benchmark which will help us measure the elapsed time from the moment the framework receives the command until the output is prepared and sent to the end-user.<br />
<br><br><br />
However, the first challenge appeared when simulating multiple concurrent connections. There were several options that we tried for the simulation, and they include:<br />
* Asynchronous Javascript (AJAX)<br />
We started off with AJAX because we are most familiar with it and it is one of the easiest to implement. However, when we observe the start_time in Chapalang Benchmark, each connect has a different start_time even though it overlaps between the start_time and end_time of the previous connection. <br />
<br><br><br />
At this stage, we cleared our misunderstanding about asynchronous calls that we had all along. While it is capable of initiating multiple asynchronous calls, where each call initiates a new connection, it does not initiate all the calls concurrently. It continues to initiate calls sequentially, but it does not wait for the previously initiated connection to be closed before it initiates the next one.<br />
<br><br><br />
As such, we realized that AJAX will not be able to accurately simulate the same-second concurrent connections that we needed for our test.<br />
* PHP popen()<br />
After some research and tests, we found out popen() which opens a pipe to a process executed by forking the command. It is also possible to create an environment where executions are done in parallel and will be suitable for simulating concurrency.<br />
<br><br><br />
While it is fairly easy to use, it offers only a unidirectional process pipe and hence unable to give us a connection response to confirm the number of concurrent connections registered at the server-side. As such, it is not a suitable tool for our test.<br />
* PHP fsocketopen()<br />
We went back to research for a new solution and it appears that fsocketopen() will be able to help us with concurrency and a bidirectional process pipe. <br />
<br><br><br />
As we developed a simple script to simulate concurrent users, we faced a problem where Apache Web Server crashes at an unexpectedly low number of 96 concurrent connections. After some investigations, we realized that fsocketopen() itself opens the same number of concurrent connections as the number of connections Apache is expected to receive and create. Essentially, there were a doubled number of connections that the server has to create, and a check on the background process on the server-side revealed a total of 156 registered apache processes. <br />
<br><br><br />
This led to some biasness in our test, because the intention was to create concurrency at the receiving end but the execution causes inaccuracies in the results. We attempt to solve it by hosting the wrapper file for fsocketopen() on our localhost machine, but we really wanted to take out the network performance uncertainty of every different users who may be using our services, and normalize it solely based on our system performance.<br />
<br><br><br />
Again, we need a methodology where we can simulate concurrency at the web server, without creating additional connections to execute.<br />
* PHP curl_multi_exec()<br />
Finally, we chanced upon curl_multi_exec() method in PHP 5 documentation manual. Libcurl is a PHP library where it performs a cURL session calling upon an internet or UNIX pointer. Additionally, curl_multi enables us to execute its sub-connections in the stack.<br />
<br><br><br />
This method did exactly what we need; it offers us a single connection, multiple threads on the execution. The overall processing time is also faster than fsocketopen() that we attempted earlier by several times.<br />
<br />
<!-- ===Personalization Analytics=== --><br />
<br />
<br />
<!-- ==Project Achievements==<br />
Methods, technologies, processes, teamwork, etc. which were particularly successful – highlight things which worked very well towards completing the project. A bulleted list of one to two sentences each will do. If there are no achievement, remove this section. --><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Project Management</font></div>=<br />
==Schedule==<br />
[[Image:6-bit_schedule.png|center|600px]]<br />
Detailed Schedule: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Schedule Click Here]<br />
===Schedule Changes===<br />
Throughout the whole project period, there were several scope adjustments and changes and they affect the schedule directly. The following documents some of the noteworthy changes made:<br />
<br><br />
[[Image:60bit_schedulechanges.png|center|500px]]<br />
<br><br />
The tasks and allocated time for the functions removed, which occurs in iteration 14-15 are replaced with the tasks for the newly added tasks.<br />
<br><br />
<br />
<br />
<div style="text-align: right;"><br />
<font size="2">''[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Technical_Overview#Scope_Prioritization Click Here to see how we prioritize our scope!]<br />
<br><br />
Visit http://www.chapalang.com to try these features out yourself! =)''<br />
</font><br />
</div><br />
==Metrics==<br />
===Schedule Metric===<br />
Schedule Metric: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Schedule_Metric Click Here]<br />
<br><br />
Metric Value: [[Image:6bit_schedulevalue.png|500px]]<br />
<br><br><br />
The acceptable range of schedule metric value is between 90% and 110%, catering to the natural inaccuracies in forecasting and actual implementation of time required to complete a task. Most of our schedules are on time, with the exception of 3 iterations.<br />
<br><br><br />
In iteration 6, there was overestimation of the amount of work that we are able to handle within the first 2-week iteration that we have, resulting in an off schedule by 20%. Previously, all our iterations are weekly. The additional tasks allocated for that iteration was to catch up with the scope to be presented for Acceptance Presentation. Many of us were however, busy with the handing over of work at our respective internship workplace and could not meet the original schedule plan. As there is a schedule lapse, we have reviewed the workload per iteration and spaced out the work for future iterations.<br />
<br><br><br />
In iteration 9, there was sufficient time to complete tasks that were planned for the iteration. However, the rush to complete the tasks before User Test 2 has led to lower quality unit testing performed by each developer in the team. This resulted in higher bug counts than usual, and the team had to stop new developers and instead spend the time fixing the bugs. As such, the schedule missed by 30% and we gained a new learning lesson that there should be buffer time for each iteration to cater for unexpected events.<br />
In iteration 15, there were fewer tasks in the iteration than much other previous iteration. However, the schedule was missed by approximately 20%. The team has discussed, and attributed the lapse to project fatigue as well as the submission of projects from other academic modules. While this could be better planned for, it was difficult to forecast the effort required for each member’s other projects. Nonetheless, there was buffer time in the final iteration which was eventually activated to make up for the schedule lapse in iteration 15.<br />
===Bug Metric===<br />
Bug Metric: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Bug_Metric Click Here]<br />
<br><br />
Metric Value: [[Image:6bit_bugvalue.png|500px]]<br />
<br><br><br />
As our acceptable range of bug points is under 20, there are 2 iterations where we have exceeded and remedies were applied as per our action plan. <br />
<br><br><br />
In iteration 11, we have conducted our User Test 2 which has a wide range of functions coverage. As a bigger system tends to also have more bugs, the user test exposes bugs that were previously unknown to us. Immediately after the user test, we have stopped new developments and focused on fixing all the bugs before we continue. Steps were taken to allow more time per task to ensure developments in the team have more time to conduct unit testing before committing their codes. Our team tester has also drafted more comprehensive test cases for her test work.<br />
<br><br><br />
In iteration 15, there was another spike in bugs metric value after the team is gradually facing project fatigue. We accepted the nature that the team has been working on the system for the past 7 months, and that there were many other school projects due during that period. As much as we have justified the cause, we stopped new developments and proceeded with a full day of bugs fixing to ensure the system is functioning properly.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Quality of Product</font></div>=<br />
<br />
{| class="wikitable"<br />
|- style="background:#58ACFA; color:white" <br />
|align="center"| Stage <br />
|align="center"| Specification<br />
|align="center"| Modules<br />
|-<br />
<br />
|rowspan="3"| Project Management<br />
|| Minutes<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Meeting_Minutes Click Here]<br />
|-<br />
<br />
|rowspan="2"| Metrics<br />
|| Schedule metrics: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Meeting_Minutes Click Here]<br />
|-<br />
<br />
|| Bug metrics: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Bug_Metric Click Here]<br />
|-<br />
<br />
|rowspan="4"| Requirements<br />
|| Scope<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables Click Here]<br />
|-<br />
<br />
|| Scope Prioritization<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Technical_Overview#Scope_Prioritization Click Here]<br />
|-<br />
<br />
|rowspan="2"| Problem Scenario<br />
|| As-Is: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#As-Is Click Here]<br />
|-<br />
<br />
|| To-Be: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#To-Be Click Here]<br />
|-<br />
<br />
|rowspan="3"| Analysis<br />
|| Use case<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Use_Case_Diagram Click Here]<br />
|-<br />
<br />
|| Business Process Diagram<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Bug_Metric Click Here]<br />
|-<br />
<br />
|| Screen Shots<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype Click Here]<br />
|-<br />
<br />
|rowspan="4"| Design<br />
|| Logical Diagram<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Logical_Diagram Click Here]<br />
|-<br />
<br />
|| Class Diagram<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Class_Diagram Click Here]<br />
|-<br />
<br />
|| Sequence Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Sequence_Diagram Click Here]<br />
|-<br />
<br />
|| Data Architecture<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Technical_Overview#Data_Architecture Click Here]<br />
|-<br />
|| Testing<br />
|| Test plan<br />
|| [[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Testing Click Here]]<br />
|-<br />
<br />
|}<br />
<br />
==Key Performance Indicators(KPI)==<br />
For the purpose of benchmarking ourselves with specific goals, we have derived on a set of indicators to understand our progress.<br />
<br><br />
[[Image:6bit_kpi.png]]<br />
<br><br />
The following figures are accurate as of 21st November 2012.<br />
<br><br />
505 real members<br />
<br><br />
106 real transactions<br />
<br><br />
189 real physical items sold<br />
<br><br />
$2536.50 real revenue<br />
<br><br />
9 registered and active sellers<br />
<br><br />
62 real products<br />
<br><br />
49 days of operations<br />
<br><br />
<div style="text-align: right;"><br />
<font size="2">''[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes Click Here to see our Learning Outcome!]''</font><br />
</div><br />
<br />
==Testing==<br />
There are a total of 4 User Tests conducted, each with a different coverage and test methodology.<br />
<br><br />
[[Image:6bituser-testingoverview.png|500px]]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing Click Here to view the details of User Test 1]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing Click Here to view the details of User Test 2]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing Click Here to view the details of User Test 3]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing Click Here to view the details of User Test 4]<br />
<br><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Reflection</font></div>=<br />
<br />
==Sponsor Comment==<br />
[https://dl.dropbox.com/u/56071797/Sponsor%28DotCom%29%20Evaluation.doc Click Here to Download our Sponsor's Comments!]<br />
<br />
==Team Reflection==<br />
<div style="text-align: center"><br />
Learning Outcome: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes#Learning_Outcome Click Here]<br />
</div><br />
[[Image:6-bit_teamReflection.png|850px|center]]<br />
==Individual Reflection==<br />
[[Image:6-bit_tianxiangReflection.png|850px|center]]<br />
<br><br />
[[Image:6-bit_geksengReflection.png|850px|left]]<br />
<br><br />
[[Image:6-bit_houstonReflection.png|850px|right]]<br />
<br><br />
[[Image:6-bit_aloysiusReflection.png|850px|center]]<br />
<br><br />
[[Image:6-bit_kennethReflection.png|850px|left]]<br />
<br><br />
[[Image:6-bit_huilingReflection.png|850px|right]]<br />
<br><br />
<br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage&diff=114729IS480 Team wiki: 2012T1 6-bit Final Wikipage2012-12-05T02:29:31Z<p>Huiling.ong.2010: /* Project Progress Summary */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Project Progress Summary</font></div>=<br />
[https://dl.dropbox.com/u/56071797/Final_Presentation.pdf <font color="#CD004E"><b>Final Presentation Slides</b></font>]<br />
<br><br />
Our website: http://www.chapalang.com<br />
==Project Overview==<br />
<div style="text-align: center"><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#X-Factors Click Here to View our X-Factors!]<br />
<br><br />
Problem Scenario: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#Problem_Scenario Click Here]<br><br />
''Team 6-bit is formed during the month of May in 2012. We have battled through 16 iterations of planning, designing, constructing and deploying our project, Chapalang and have successfully completed the project, maintaining to our planned scope. Throughout 16 iterations, we have our ups and downs. We faced several unexpected technical challenges which brought down the morale of the team. People with different methods of solving problems created communication problems. However, having a common goal in mind, we endure and frantically looking for workarounds and alternatives to overcome these challenges. We, too, faced some project management challenges where some tasks are not complete on time and caused disturbance to our schedule. These project challenges allow us to iron out our differences and streamlined a better working process. After overcoming these challenges, we had improved ourselves as individuals as well as improved as a team!''<br />
<br />
</div><br />
<br>[[Image:6-bit_poster.jpg|right|450px]]<br />
<br>[http://www.youtube.com/watch?v=8Y8Q9iCKQUY Click here to view our 1min Video Pitch!] <br />
<br><br />
[[Image:6-bit_videopitch.gif|left|450px]]<br />
<br><br><br><br><br><br><br><br><br><br><br><br />
<br><br />
<br />
<br><br />
<br />
<br />
<br />
==Project Challenges==<br />
There are several challenges that the team has faced throughout the IS480 journey. The bulk of Chapalang! is a highly functional and complete solution to a business opportunity of our sponsor, and hence it is not on the basis of a single sophisticated function.<br />
<br><br> <br />
However, it is a cumulatively complex system as it is formed by several functions, and the team has been challenged in different levels on integration issues, and micro-components of the project. One example of the micro-component is Paypal integration where Paypal documentations have been brief and changes are frequent, resulting in integration difficulties but eventually resolved. Another example is on our image cropping tool, where significant amount of time is spent on getting it right especially when none of us in the team has ever ventured into image manipulation.<br />
<br><br><br />
Nonetheless, there are two other independent challenges which introduce much learning lessons for the team.<br />
<br />
===Scalability and Load Testing===<br />
As part of our User Test 4, we attempted to have a better understanding of scalability and load handling of our system by conducting a test.<br><br />
To reiterate, performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. In order to conduct the test, the following steps are required.<br />
* Performance Testing<br />
** Identify a system process with a series of activities<br />
** Measure the elapse time of each activity<br />
** Identify the bottleneck which is the single important activity which has highest elapse time <br />
* Scalability Testing<br />
** Increase the number of concurrent connections for the identified activity and measure of elapse time of each connection<br />
** Count the number of concurrent connections possible, within the same approximate amount of elapse time of each connection<br />
* Load Testing<br />
** Measure the elapse time of each connection over a range of concurrent connections, including 1, 25, 50, 75, 100 as markers<br />
<br />
====Difficulty in simulating accurate multiple concurrent connections====<br />
Amongst all the steps involved, it is easiest to conduct performance testing because we have already developed Chapalang Benchmark which will help us measure the elapsed time from the moment the framework receives the command until the output is prepared and sent to the end-user.<br />
<br><br><br />
However, the first challenge appeared when simulating multiple concurrent connections. There were several options that we tried for the simulation, and they include:<br />
* Asynchronous Javascript (AJAX)<br />
We started off with AJAX because we are most familiar with it and it is one of the easiest to implement. However, when we observe the start_time in Chapalang Benchmark, each connect has a different start_time even though it overlaps between the start_time and end_time of the previous connection. <br />
<br><br><br />
At this stage, we cleared our misunderstanding about asynchronous calls that we had all along. While it is capable of initiating multiple asynchronous calls, where each call initiates a new connection, it does not initiate all the calls concurrently. It continues to initiate calls sequentially, but it does not wait for the previously initiated connection to be closed before it initiates the next one.<br />
<br><br><br />
As such, we realized that AJAX will not be able to accurately simulate the same-second concurrent connections that we needed for our test.<br />
* PHP popen()<br />
After some research and tests, we found out popen() which opens a pipe to a process executed by forking the command. It is also possible to create an environment where executions are done in parallel and will be suitable for simulating concurrency.<br />
<br><br><br />
While it is fairly easy to use, it offers only a unidirectional process pipe and hence unable to give us a connection response to confirm the number of concurrent connections registered at the server-side. As such, it is not a suitable tool for our test.<br />
* PHP fsocketopen()<br />
We went back to research for a new solution and it appears that fsocketopen() will be able to help us with concurrency and a bidirectional process pipe. <br />
<br><br><br />
As we developed a simple script to simulate concurrent users, we faced a problem where Apache Web Server crashes at an unexpectedly low number of 96 concurrent connections. After some investigations, we realized that fsocketopen() itself opens the same number of concurrent connections as the number of connections Apache is expected to receive and create. Essentially, there were a doubled number of connections that the server has to create, and a check on the background process on the server-side revealed a total of 156 registered apache processes. <br />
<br><br><br />
This led to some biasness in our test, because the intention was to create concurrency at the receiving end but the execution causes inaccuracies in the results. We attempt to solve it by hosting the wrapper file for fsocketopen() on our localhost machine, but we really wanted to take out the network performance uncertainty of every different users who may be using our services, and normalize it solely based on our system performance.<br />
<br><br><br />
Again, we need a methodology where we can simulate concurrency at the web server, without creating additional connections to execute.<br />
* PHP curl_multi_exec()<br />
Finally, we chanced upon curl_multi_exec() method in PHP 5 documentation manual. Libcurl is a PHP library where it performs a cURL session calling upon an internet or UNIX pointer. Additionally, curl_multi enables us to execute its sub-connections in the stack.<br />
<br><br><br />
This method did exactly what we need; it offers us a single connection, multiple threads on the execution. The overall processing time is also faster than fsocketopen() that we attempted earlier by several times.<br />
<br />
<!-- ===Personalization Analytics=== --><br />
<br />
<br />
<!-- ==Project Achievements==<br />
Methods, technologies, processes, teamwork, etc. which were particularly successful – highlight things which worked very well towards completing the project. A bulleted list of one to two sentences each will do. If there are no achievement, remove this section. --><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Project Management</font></div>=<br />
==Schedule==<br />
[[Image:6-bit_schedule.png|center|600px]]<br />
Detailed Schedule: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Schedule Click Here]<br />
===Schedule Changes===<br />
Throughout the whole project period, there were several scope adjustments and changes and they affect the schedule directly. The following documents some of the noteworthy changes made:<br />
<br><br />
[[Image:60bit_schedulechanges.png|center|500px]]<br />
<br><br />
The tasks and allocated time for the functions removed, which occurs in iteration 14-15 are replaced with the tasks for the newly added tasks.<br />
<br><br />
<br />
<br />
<div style="text-align: right;"><br />
<font size="2">''[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Technical_Overview#Scope_Prioritization Click Here to see how we prioritize our scope!]<br />
<br><br />
Visit http://www.chapalang.com to try these features out yourself! =)''<br />
</font><br />
</div><br />
==Metrics==<br />
===Schedule Metric===<br />
Schedule Metric: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Schedule_Metric Click Here]<br />
<br><br />
Metric Value: [[Image:6bit_schedulevalue.png|500px]]<br />
<br><br><br />
The acceptable range of schedule metric value is between 90% and 110%, catering to the natural inaccuracies in forecasting and actual implementation of time required to complete a task. Most of our schedules are on time, with the exception of 3 iterations.<br />
<br><br><br />
In iteration 6, there was overestimation of the amount of work that we are able to handle within the first 2-week iteration that we have, resulting in an off schedule by 20%. Previously, all our iterations are weekly. The additional tasks allocated for that iteration was to catch up with the scope to be presented for Acceptance Presentation. Many of us were however, busy with the handing over of work at our respective internship workplace and could not meet the original schedule plan. As there is a schedule lapse, we have reviewed the workload per iteration and spaced out the work for future iterations.<br />
<br><br><br />
In iteration 9, there was sufficient time to complete tasks that were planned for the iteration. However, the rush to complete the tasks before User Test 2 has led to lower quality unit testing performed by each developer in the team. This resulted in higher bug counts than usual, and the team had to stop new developers and instead spend the time fixing the bugs. As such, the schedule missed by 30% and we gained a new learning lesson that there should be buffer time for each iteration to cater for unexpected events.<br />
In iteration 15, there were fewer tasks in the iteration than much other previous iteration. However, the schedule was missed by approximately 20%. The team has discussed, and attributed the lapse to project fatigue as well as the submission of projects from other academic modules. While this could be better planned for, it was difficult to forecast the effort required for each member’s other projects. Nonetheless, there was buffer time in the final iteration which was eventually activated to make up for the schedule lapse in iteration 15.<br />
===Bug Metric===<br />
Bug Metric: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Bug_Metric Click Here]<br />
<br><br />
Metric Value: [[Image:6bit_bugvalue.png|500px]]<br />
<br><br><br />
As our acceptable range of bug points is under 20, there are 2 iterations where we have exceeded and remedies were applied as per our action plan. <br />
<br><br><br />
In iteration 11, we have conducted our User Test 2 which has a wide range of functions coverage. As a bigger system tends to also have more bugs, the user test exposes bugs that were previously unknown to us. Immediately after the user test, we have stopped new developments and focused on fixing all the bugs before we continue. Steps were taken to allow more time per task to ensure developments in the team have more time to conduct unit testing before committing their codes. Our team tester has also drafted more comprehensive test cases for her test work.<br />
<br><br><br />
In iteration 15, there was another spike in bugs metric value after the team is gradually facing project fatigue. We accepted the nature that the team has been working on the system for the past 7 months, and that there were many other school projects due during that period. As much as we have justified the cause, we stopped new developments and proceeded with a full day of bugs fixing to ensure the system is functioning properly.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Quality of Product</font></div>=<br />
<br />
{| class="wikitable"<br />
|- style="background:#58ACFA; color:white" <br />
|align="center"| Stage <br />
|align="center"| Specification<br />
|align="center"| Modules<br />
|-<br />
<br />
|rowspan="3"| Project Management<br />
|| Minutes<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Meeting_Minutes Click Here]<br />
|-<br />
<br />
|rowspan="2"| Metrics<br />
|| Schedule metrics: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Meeting_Minutes Click Here]<br />
|-<br />
<br />
|| Bug metrics: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Bug_Metric Click Here]<br />
|-<br />
<br />
|rowspan="4"| Requirements<br />
|| Scope<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables Click Here]<br />
|-<br />
<br />
|| Scope Prioritization<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Technical_Overview#Scope_Prioritization Click Here]<br />
|-<br />
<br />
|rowspan="2"| Problem Scenario<br />
|| As-Is: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#As-Is Click Here]<br />
|-<br />
<br />
|| To-Be: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#To-Be Click Here]<br />
|-<br />
<br />
|rowspan="3"| Analysis<br />
|| Use case<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Use_Case_Diagram Click Here]<br />
|-<br />
<br />
|| Business Process Diagram<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Bug_Metric Click Here]<br />
|-<br />
<br />
|| Screen Shots<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype Click Here]<br />
|-<br />
<br />
|rowspan="4"| Design<br />
|| Logical Diagram<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Logical_Diagram Click Here]<br />
|-<br />
<br />
|| Class Diagram<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Class_Diagram Click Here]<br />
|-<br />
<br />
|| Sequence Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Sequence_Diagram Click Here]<br />
|-<br />
<br />
|| Data Architecture<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Technical_Overview#Data_Architecture Click Here]<br />
|-<br />
|| Testing<br />
|| Test plan<br />
|| [[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Testing Click Here]]<br />
|-<br />
<br />
|}<br />
<br />
==Key Performance Indicators(KPI)==<br />
For the purpose of benchmarking ourselves with specific goals, we have derived on a set of indicators to understand our progress.<br />
<br><br />
[[Image:6bit_kpi.png]]<br />
<br><br />
The following figures are accurate as of 21st November 2012.<br />
<br><br />
505 real members<br />
<br><br />
106 real transactions<br />
<br><br />
189 real physical items sold<br />
<br><br />
$2536.50 real revenue<br />
<br><br />
9 registered and active sellers<br />
<br><br />
62 real products<br />
<br><br />
49 days of operations<br />
<br><br />
<div style="text-align: right;"><br />
<font size="2">''[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes Click Here to see our Learning Outcome!]''</font><br />
</div><br />
<br />
==Testing==<br />
There are a total of 4 User Tests conducted, each with a different coverage and test methodology.<br />
<br><br />
[[Image:6bituser-testingoverview.png|500px]]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing Click Here to view the details of User Test 1]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing Click Here to view the details of User Test 2]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing Click Here to view the details of User Test 3]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing Click Here to view the details of User Test 4]<br />
<br><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Reflection</font></div>=<br />
<br />
==Sponsor Comment==<br />
[https://dl.dropbox.com/u/56071797/Sponsor%28DotCom%29%20Evaluation.doc Click Here to Download our Sponsor's Comments!]<br />
<br />
==Team Reflection==<br />
<div style="text-align: center"><br />
Learning Outcome: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes#Learning_Outcome Click Here]<br />
</div><br />
[[Image:6-bit_teamReflection.png|850px|center]]<br />
==Individual Reflection==<br />
[[Image:6-bit_tianxiangReflection.png|850px|center]]<br />
<br><br />
[[Image:6-bit_geksengReflection.png|850px|left]]<br />
<br><br />
[[Image:6-bit_houstonReflection.png|850px|right]]<br />
<br><br />
[[Image:6-bit_aloysiusReflection.png|850px|center]]<br />
<br><br />
[[Image:6-bit_kennethReflection.png|850px|left]]<br />
<br><br />
[[Image:6-bit_huilingReflection.png|850px|right]]<br />
<br><br />
<br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage&diff=114550IS480 Team wiki: 2012T1 6-bit Final Wikipage2012-12-04T15:12:23Z<p>Huiling.ong.2010: /* Project Progress Summary */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Project Progress Summary</font></div>=<br />
[https://dl.dropbox.com/u/56071797/Final_Presentation.pptx <font color="#CD004E"><b>Final Presentation Slides</b></font>]<br />
<br><br />
Our website: http://www.chapalang.com<br />
==Project Overview==<br />
<div style="text-align: center"><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#X-Factors Click Here to View our X-Factors!]<br />
<br><br />
Problem Scenario: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#Problem_Scenario Click Here]<br><br />
''Team 6-bit is formed during the month of May in 2012. We have battled through 16 iterations of planning, designing, constructing and deploying our project, Chapalang and have successfully completed the project, maintaining to our planned scope. Throughout 16 iterations, we have our ups and downs. We faced several unexpected technical challenges which brought down the morale of the team. People with different methods of solving problems created communication problems. However, having a common goal in mind, we endure and frantically looking for workarounds and alternatives to overcome these challenges. We, too, faced some project management challenges where some tasks are not complete on time and caused disturbance to our schedule. These project challenges allow us to iron out our differences and streamlined a better working process. After overcoming these challenges, we had improved ourselves as individuals as well as improved as a team!''<br />
<br />
</div><br />
<br>[[Image:6-bit_poster.jpg|right|450px]]<br />
<br>[http://www.youtube.com/watch?v=8Y8Q9iCKQUY Click here to view our 1min Video Pitch!] <br />
<br><br />
[[Image:6-bit_videopitch.gif|left|450px]]<br />
<br><br><br><br><br><br><br><br><br><br><br><br />
<br><br />
<br />
<br><br />
<br />
<br />
<br />
==Project Challenges==<br />
There are several challenges that the team has faced throughout the IS480 journey. The bulk of Chapalang! is a highly functional and complete solution to a business opportunity of our sponsor, and hence it is not on the basis of a single sophisticated function.<br />
<br><br> <br />
However, it is a cumulatively complex system as it is formed by several functions, and the team has been challenged in different levels on integration issues, and micro-components of the project. One example of the micro-component is Paypal integration where Paypal documentations have been brief and changes are frequent, resulting in integration difficulties but eventually resolved. Another example is on our image cropping tool, where significant amount of time is spent on getting it right especially when none of us in the team has ever ventured into image manipulation.<br />
<br><br><br />
Nonetheless, there are two other independent challenges which introduce much learning lessons for the team.<br />
<br />
===Scalability and Load Testing===<br />
As part of our User Test 4, we attempted to have a better understanding of scalability and load handling of our system by conducting a test.<br><br />
To reiterate, performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. In order to conduct the test, the following steps are required.<br />
* Performance Testing<br />
** Identify a system process with a series of activities<br />
** Measure the elapse time of each activity<br />
** Identify the bottleneck which is the single important activity which has highest elapse time <br />
* Scalability Testing<br />
** Increase the number of concurrent connections for the identified activity and measure of elapse time of each connection<br />
** Count the number of concurrent connections possible, within the same approximate amount of elapse time of each connection<br />
* Load Testing<br />
** Measure the elapse time of each connection over a range of concurrent connections, including 1, 25, 50, 75, 100 as markers<br />
<br />
====Difficulty in simulating accurate multiple concurrent connections====<br />
Amongst all the steps involved, it is easiest to conduct performance testing because we have already developed Chapalang Benchmark which will help us measure the elapsed time from the moment the framework receives the command until the output is prepared and sent to the end-user.<br />
<br><br><br />
However, the first challenge appeared when simulating multiple concurrent connections. There were several options that we tried for the simulation, and they include:<br />
* Asynchronous Javascript (AJAX)<br />
We started off with AJAX because we are most familiar with it and it is one of the easiest to implement. However, when we observe the start_time in Chapalang Benchmark, each connect has a different start_time even though it overlaps between the start_time and end_time of the previous connection. <br />
<br><br><br />
At this stage, we cleared our misunderstanding about asynchronous calls that we had all along. While it is capable of initiating multiple asynchronous calls, where each call initiates a new connection, it does not initiate all the calls concurrently. It continues to initiate calls sequentially, but it does not wait for the previously initiated connection to be closed before it initiates the next one.<br />
<br><br><br />
As such, we realized that AJAX will not be able to accurately simulate the same-second concurrent connections that we needed for our test.<br />
* PHP popen()<br />
After some research and tests, we found out popen() which opens a pipe to a process executed by forking the command. It is also possible to create an environment where executions are done in parallel and will be suitable for simulating concurrency.<br />
<br><br><br />
While it is fairly easy to use, it offers only a unidirectional process pipe and hence unable to give us a connection response to confirm the number of concurrent connections registered at the server-side. As such, it is not a suitable tool for our test.<br />
* PHP fsocketopen()<br />
We went back to research for a new solution and it appears that fsocketopen() will be able to help us with concurrency and a bidirectional process pipe. <br />
<br><br><br />
As we developed a simple script to simulate concurrent users, we faced a problem where Apache Web Server crashes at an unexpectedly low number of 96 concurrent connections. After some investigations, we realized that fsocketopen() itself opens the same number of concurrent connections as the number of connections Apache is expected to receive and create. Essentially, there were a doubled number of connections that the server has to create, and a check on the background process on the server-side revealed a total of 156 registered apache processes. <br />
<br><br><br />
This led to some biasness in our test, because the intention was to create concurrency at the receiving end but the execution causes inaccuracies in the results. We attempt to solve it by hosting the wrapper file for fsocketopen() on our localhost machine, but we really wanted to take out the network performance uncertainty of every different users who may be using our services, and normalize it solely based on our system performance.<br />
<br><br><br />
Again, we need a methodology where we can simulate concurrency at the web server, without creating additional connections to execute.<br />
* PHP curl_multi_exec()<br />
Finally, we chanced upon curl_multi_exec() method in PHP 5 documentation manual. Libcurl is a PHP library where it performs a cURL session calling upon an internet or UNIX pointer. Additionally, curl_multi enables us to execute its sub-connections in the stack.<br />
<br><br><br />
This method did exactly what we need; it offers us a single connection, multiple threads on the execution. The overall processing time is also faster than fsocketopen() that we attempted earlier by several times.<br />
<br />
<!-- ===Personalization Analytics=== --><br />
<br />
<br />
<!-- ==Project Achievements==<br />
Methods, technologies, processes, teamwork, etc. which were particularly successful – highlight things which worked very well towards completing the project. A bulleted list of one to two sentences each will do. If there are no achievement, remove this section. --><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Project Management</font></div>=<br />
==Schedule==<br />
[[Image:6-bit_schedule.png|center|600px]]<br />
Detailed Schedule: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Schedule Click Here]<br />
===Schedule Changes===<br />
Throughout the whole project period, there were several scope adjustments and changes and they affect the schedule directly. The following documents some of the noteworthy changes made:<br />
<br><br />
[[Image:60bit_schedulechanges.png|center|500px]]<br />
<br><br />
The tasks and allocated time for the functions removed, which occurs in iteration 14-15 are replaced with the tasks for the newly added tasks.<br />
<br><br />
<br />
<br />
<div style="text-align: right;"><br />
<font size="2">''[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Technical_Overview#Scope_Prioritization Click Here to see how we prioritize our scope!]<br />
<br><br />
Visit http://www.chapalang.com to try these features out yourself! =)''<br />
</font><br />
</div><br />
==Metrics==<br />
===Schedule Metric===<br />
Schedule Metric: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Schedule_Metric Click Here]<br />
<br><br />
Metric Value: [[Image:6bit_schedulevalue.png|500px]]<br />
<br><br><br />
The acceptable range of schedule metric value is between 90% and 110%, catering to the natural inaccuracies in forecasting and actual implementation of time required to complete a task. Most of our schedules are on time, with the exception of 3 iterations.<br />
<br><br><br />
In iteration 6, there was overestimation of the amount of work that we are able to handle within the first 2-week iteration that we have, resulting in an off schedule by 20%. Previously, all our iterations are weekly. The additional tasks allocated for that iteration was to catch up with the scope to be presented for Acceptance Presentation. Many of us were however, busy with the handing over of work at our respective internship workplace and could not meet the original schedule plan. As there is a schedule lapse, we have reviewed the workload per iteration and spaced out the work for future iterations.<br />
<br><br><br />
In iteration 9, there was sufficient time to complete tasks that were planned for the iteration. However, the rush to complete the tasks before User Test 2 has led to lower quality unit testing performed by each developer in the team. This resulted in higher bug counts than usual, and the team had to stop new developers and instead spend the time fixing the bugs. As such, the schedule missed by 30% and we gained a new learning lesson that there should be buffer time for each iteration to cater for unexpected events.<br />
In iteration 15, there were fewer tasks in the iteration than much other previous iteration. However, the schedule was missed by approximately 20%. The team has discussed, and attributed the lapse to project fatigue as well as the submission of projects from other academic modules. While this could be better planned for, it was difficult to forecast the effort required for each member’s other projects. Nonetheless, there was buffer time in the final iteration which was eventually activated to make up for the schedule lapse in iteration 15.<br />
===Bug Metric===<br />
Bug Metric: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Bug_Metric Click Here]<br />
<br><br />
Metric Value: [[Image:6bit_bugvalue.png|500px]]<br />
<br><br><br />
As our acceptable range of bug points is under 20, there are 2 iterations where we have exceeded and remedies were applied as per our action plan. <br />
<br><br><br />
In iteration 11, we have conducted our User Test 2 which has a wide range of functions coverage. As a bigger system tends to also have more bugs, the user test exposes bugs that were previously unknown to us. Immediately after the user test, we have stopped new developments and focused on fixing all the bugs before we continue. Steps were taken to allow more time per task to ensure developments in the team have more time to conduct unit testing before committing their codes. Our team tester has also drafted more comprehensive test cases for her test work.<br />
<br><br><br />
In iteration 15, there was another spike in bugs metric value after the team is gradually facing project fatigue. We accepted the nature that the team has been working on the system for the past 7 months, and that there were many other school projects due during that period. As much as we have justified the cause, we stopped new developments and proceeded with a full day of bugs fixing to ensure the system is functioning properly.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Quality of Product</font></div>=<br />
<br />
{| class="wikitable"<br />
|- style="background:#58ACFA; color:white" <br />
|align="center"| Stage <br />
|align="center"| Specification<br />
|align="center"| Modules<br />
|-<br />
<br />
|rowspan="3"| Project Management<br />
|| Minutes<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Meeting_Minutes Click Here]<br />
|-<br />
<br />
|rowspan="2"| Metrics<br />
|| Schedule metrics: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Meeting_Minutes Click Here]<br />
|-<br />
<br />
|| Bug metrics: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Bug_Metric Click Here]<br />
|-<br />
<br />
|rowspan="4"| Requirements<br />
|| Scope<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables Click Here]<br />
|-<br />
<br />
|| Scope Prioritization<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Technical_Overview#Scope_Prioritization Click Here]<br />
|-<br />
<br />
|rowspan="2"| Problem Scenario<br />
|| As-Is: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#As-Is Click Here]<br />
|-<br />
<br />
|| To-Be: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables#To-Be Click Here]<br />
|-<br />
<br />
|rowspan="3"| Analysis<br />
|| Use case<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Use_Case_Diagram Click Here]<br />
|-<br />
<br />
|| Business Process Diagram<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Bug_Metric Click Here]<br />
|-<br />
<br />
|| Screen Shots<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype Click Here]<br />
|-<br />
<br />
|rowspan="4"| Design<br />
|| Logical Diagram<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Logical_Diagram Click Here]<br />
|-<br />
<br />
|| Class Diagram<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Class_Diagram Click Here]<br />
|-<br />
<br />
|| Sequence Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams#Sequence_Diagram Click Here]<br />
|-<br />
<br />
|| Data Architecture<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Technical_Overview#Data_Architecture Click Here]<br />
|-<br />
|| Testing<br />
|| Test plan<br />
|| [[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management#Testing Click Here]]<br />
|-<br />
<br />
|}<br />
<br />
==Key Performance Indicators(KPI)==<br />
For the purpose of benchmarking ourselves with specific goals, we have derived on a set of indicators to understand our progress.<br />
<br><br />
[[Image:6bit_kpi.png]]<br />
<br><br />
The following figures are accurate as of 21st November 2012.<br />
<br><br />
505 real members<br />
<br><br />
106 real transactions<br />
<br><br />
189 real physical items sold<br />
<br><br />
$2536.50 real revenue<br />
<br><br />
9 registered and active sellers<br />
<br><br />
62 real products<br />
<br><br />
49 days of operations<br />
<br><br />
<div style="text-align: right;"><br />
<font size="2">''[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes Click Here to see our Learning Outcome!]''</font><br />
</div><br />
<br />
==Testing==<br />
There are a total of 4 User Tests conducted, each with a different coverage and test methodology.<br />
<br><br />
[[Image:6bituser-testingoverview.png|500px]]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing Click Here to view the details of User Test 1]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing Click Here to view the details of User Test 2]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing Click Here to view the details of User Test 3]<br />
<br><br />
[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing Click Here to view the details of User Test 4]<br />
<br><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Reflection</font></div>=<br />
<br />
==Sponsor Comment==<br />
[https://dl.dropbox.com/u/56071797/Sponsor%28DotCom%29%20Evaluation.doc Click Here to Download our Sponsor's Comments!]<br />
<br />
==Team Reflection==<br />
<div style="text-align: center"><br />
Learning Outcome: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes#Learning_Outcome Click Here]<br />
</div><br />
[[Image:6-bit_teamReflection.png|850px|center]]<br />
==Individual Reflection==<br />
[[Image:6-bit_tianxiangReflection.png|850px|center]]<br />
<br><br />
[[Image:6-bit_geksengReflection.png|850px|left]]<br />
<br><br />
[[Image:6-bit_houstonReflection.png|850px|right]]<br />
<br><br />
[[Image:6-bit_aloysiusReflection.png|850px|center]]<br />
<br><br />
[[Image:6-bit_kennethReflection.png|850px|left]]<br />
<br><br />
[[Image:6-bit_huilingReflection.png|850px|right]]<br />
<br><br />
<br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit&diff=114549IS480 Team wiki: 2012T1 6-bit2012-12-04T15:11:59Z<p>Huiling.ong.2010: /* Final */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Current Status</font></div>=<br />
<br />
{| class="wikitable" cellpadding="15"<br />
<br />
|-<br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 46%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Current Iteration</b> <br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 50%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Meeting Status</b> <br />
|-<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Iteration Number :''' <br />
16 *Final Iteration*<br />
<br><br />
'''Iteration Start Date : '''<br />
24 November 2012<br />
<br><br />
'''Iteration End Date :'''<br />
3 December 2012<br />
<br><br />
'''Iteration Task :'''<br />
<br><br />
1. Final Presentation<br />
<br><br />
2. Poster Day<br />
<br><br />
<br />
<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Weekly Meeting Schedule'''<br />
<br><br />
Every Monday, Wednesday, Friday<br />
<br><br />
SIS Analytics Kitchen<br />
<br><br />
12pm to 3pm<br />
<br><br />
<br />
'''Weekly Supervisor Meeting'''<br />
<br><br />
Every Monday<br />
<br><br />
2pm to 3pm<br />
|}<br />
<div style="text-align: right;"><br />
<font size="2">''Last Update: 28 November 2012''</font><br />
</div><br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Team</font></div>=<br />
[[Image:6-bitTeamMembers.png|alt=text|6-bitTeamMembers|centre|650px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Project: Chapalang</font></div>=<br />
<div style="text-align: center"><font color="#00BFFF">''Talk, Buy, Sell, Share, all on Chapalang!''</font></div><br />
<font color="#FE2EF7">Chapalang!</font> is a social utility that connects people with friends and new friends by offering a place for exchanging ideas and information on its public domain. People use our discussion forums to write HOWTOs, share findings, ask questions, comment on news, and many more.<br />
<br><br />
<font color="#FE2EF7">Chapalang!</font> also features a social marketplace for you to buy online, and participate in mass orders in a convenient and reliable way.<br />
<br><br />
Best of all, you can browse wish lists of your friends to know what are the right things to buy on special occasions. You could buy the gift on <br />
<font color="#FE2EF7">Chapalang!</font> and have it sent to their doorsteps, or organize a Gift Sharing campaign to share the costs of gift with other friends.<br />
<br />
[[Image:chapalangprocesses.png|1100px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Main Features</font></div>=<br />
[[Image:ChapalangLogo.png|left|150px]]<br />
<br><br />
<i>proposes the following unique features:</i><br />
<br><br />
[[Image:6-bitGroupbuyprocess.png|center|1000px]]<br />
<br><br />
<b>Gifts Sharing</b> : <br />
<br><br />
Gifting can be simple or collective. A simple gift is purchased when a user pays for the full costs of the gift, and states the recipient’s contact details upon checkout. Chapalang! will contact the recipient for their address, and subsequently fulfil the order with the delivery of goods.<br />
<br><br />
<br><br />
A collective gift is purchased when a user takes on the role of an organizer and initiates a Gift Sharing Campaign. He will select a product from a user’s wish list, or any other product in the marketplace, and designate it to be the gift to be shared. He will also decide on the product options, if any, as well as the delivery method. <br />
<br><br />
<br><br />
Thereafter, he can invite a list of mutual friends whom he wants to share the gift with. The invitees will be informed of the campaign via a notification, and will be able to contribute any varying amount on the campaign page. They will also be able to hide their amount of contribution, or even hide their contribution record from public. Upon successfully raising the target amount which is the price of the gift, an email will be sent to the recipient for him/her to update their address for fulfilment and delivery.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitMassorderprocess.png|center|1000px]]<br />
<b>Mass orders</b> : <br />
<br>Mass Orders (MO) should be structured and organized, just like a regular product item in the marketplace. <br />
<br><br />
<br><br />
When creating an MO, the buyer will input the price, description, minimum collective quantity for the MO to go through, the maximum collective quantity accepted for the MO if it’s a limited quantity offer, as well as the start and end period of the MO. An MO organizer can be an individual or a company. The organizer will be able to invite his/her friends, or regular customers to the MO. <br />
<br><br />
<br><br />
Participants of an MO will be able to view the MO page, enter a desired quantity and checkout. In the checkout process, participants will be required to enter their delivery address and choose their preferred shipping method. Payment is made upon ordering, safeguarded by the esrow service, and will be paid to the sellers if the MO is successful. In the event that MO is unsuccessful or cancelled, full amount of their orders will be refunded to all participants automatically.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitEscrowprocess.png|centre|1000px]]<br />
<b>Escrow</b> : <br />
<br><br />
In most other agent websites, buyers either pay to sellers directly or buyers pay to the agent and agent will pay the buyers 30 days later. We will turn this credit period to the advantage of buyers and sellers, introducing assurance.<br />
<br><br><br />
In any transaction on Chapalang!, the buyer will pay to Chapalang! directly. Sellers are notified of the receipt of payment, and will proceed to ship the item out to the buyer. Upon receipt of the order, buyers will revisit Chapalang! and indicate that the goods are received satisfactorily, and Chapalang! will then pay the sellers in the next 3 days. However, if there is no response or dispute from the buyers within 30 days, the order is assumed to be satisfactorily fulfilled and the payment will be released to the seller. In the event of disputes, buyers and sellers are encouraged to negotiate for a recovery, or in the case of an exhausted negotiation, Chapalang! may issue a full or partial refund to the customers.<br />
<br><br><br />
Systematically, the Chapalang! system will support this this use case through a series of functions. <br />
*Firstly, the system will support a goods receipt acknowledgement process, recording the goods receipt, triggering of payment activities to sellers upon 30 days grace or upon the record of goods receipt. <br />
*Secondly, sellers should be able to see their sales and know how much they will be receiving from Chapalang! and when. <br />
*Thirdly, there should be a messaging channel to facilitate communications between the buyer and seller<br />
*Fourthly, there should be a refund method to allow sellers to refund a transaction should be accept that he’s unable to recover or fulfil the order<br />
*Lastly, administrator of Chapalang! should be able to see a list of fulfilled, or assumed fulfilled transactions ready for payment to the sellers<br />
<br />
<div style="text-align: right;"><br />
<font size="2">''Prototype of Chapalang's Features: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype Click Here]''</font><br />
</div><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Low Level Functions</font></div>=<br />
==Web Parser==<br />
As an interactive feature, URLs shared on Chapalang! will offer a preview which contains the site title, url, image and description. This should reflect the final URL, instead of any redirecting URL at a higher level.<br />
<br><br><br />
The picking of appropriate objects (title, url, image or description) is important, where standardized Open Graph (OG) protocol meta data of a webpage will be prioritized, before seeking through the other HTML components for referencing objects.<br />
==Private Message==<br />
[[Image:6-bit_message.png|center|600px]]<br />
There should be an in-system communication channel for general users, buyers and sellers. Potential buyers can clarify product specifications with sellers, sellers can confirm delivery address with buyers in case of anomalies, and general users can use it for chatting purposes.<br />
<br><br />
<br>It should be able to perform CRUD of messages between 2 users, in a conversational format. Users are notified via email whenever they receive a message. They will also be able to see past messages exchanged, in a single conversation page.<br />
==Image Cropping Tool==<br />
As all images uploaded by users can be of different dimensions, our system will need a tool to automatically resize and crop away unimportant parts to fit the image dimensions on different pages.<br />
<br><br><br />
Hence, the Image Cropping Tool will help us with automatically resizing an image to the most suitable resolution, before cropping away any extended sides and focus on the centre of the image which is usually the most important message. This tool will be applied throughout the entire platform, on both discussion forums and marketplace.<br />
<br />
==Notifications==<br />
[[Image:6-bit_notification.png|center|300px]]<br />
Users should be appropriately notified on any activities concerning them. They will have a new notifications whenever someone replies to their post, whenever a friend is following them in Chapalang!, or when a product purchased is being shipped, et cetera.<br />
<br><br />
<br><br />
Notification entries should link them to appropriate pages for follow-up actions or even simply viewing more details of the notification. Each in-system notification should also be tied to an email notification for a timelier update to users, and users should have the ability to modify their notifications settings for privacy or information flood control.<br />
<br />
==Search function==<br />
[[Image:6-bit_search.png|center|600px]]<br />
There are many content types on Chapalang!, which includes people, messages, products, posts, et cetera. These content types should be searchable for the purpose of conveniently accessing specific content.<br />
==Profile page==<br />
[[Image:6-bit_profilepage.png|center|600px]]<br />
Every user will have a dedicated profile page, which contains their profile picture, basic particulars, activities and friends. This will create a more social environment, where information of a user is shared among friends.<br />
==Management pages==<br />
[[Image:6-bit_management.png|center|250px]]<br />
There should be a set of management pages, for the management of sales, orders or products. These pages will be able to perform basic CRUD functions, as well as other functions allowing appropriate manipulation of an activity. For example, Manage Sales will allow sellers to view transactional details as well as updating shipping details when an order is fulfilled. On the other hand, Manage Orders will allow buyers to review their purchases and be informed whether their orders are fulfilled. Correspondingly, Manage Products will allow the sellers administer all aspects of a product, from its description, images, pricing, to its options and shipping methods.<br />
<br />
==Settings pages==<br />
[[Image:6-bit_settings.png|center|600px]]<br />
There will be separate pages for Accounts Settings, Privacy Settings and Notifications Settings. Firstly, Account Settings will allow a user to change their basic information imported from Facebook. Secondly, Privacy Settings will provide the option to show or hide certain sensitive information that a user may choose not to show in the public. Lastly, Notifications Settings will help the users manage the quantity and quality of notifications that they receive as they might choose not to be informed of certain activities to prevent information overload.<br />
==Personalized dashboard==<br />
[[Image:6-bit_personalizeddb.png|center|600px]]<br />
A dashboard is the first page the user will see upon login, and will contain a mash up of content from various components on the portal. The content published to the dashboard is personalized through stratification supported by data-driven analytics.<br />
<br><br />
<br><br />
The dashboard will contain the following data:<br />
* Relevant topics from subscribed forums<br />
* Featured discussions<br />
* Product recommendations generated by analytics<br />
* Recent purchases made by friends<br />
* Featured mass orders recommendations generated by analytics<br />
* Seasonal or holidays promotional products recommendations generated by analytics<br />
* New arrival products recommendations generated by analytics<br />
* Reminders on upcoming special dates, friends’ birthdays, and activity invites<br />
The dashboard has a 2-step approach in deriving personalized content. Firstly, a set of meta data describing a user is generated. Secondly, another set of meta data describing a product is also generated. Subsequently, both set of meta data are matched to produce a list of recommendations.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Sponsor</font></div>=<br />
[[Image:Dotcom_Logo.jpg|left]]<br />
<b>Chapalang</b> is a self-proposed project for DotCom Enterprise. Upon successful development, DotCom will commercialize the project for live operations. Mr. Eric Chew, Special Projects Manager will be the primary contact from DotCom. Throughout the development and implementation stages, our team will deploy the project on the live systems provided by DotCom.<br />
<div style="margin-bottom:30px;><br />
<br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Academic Milestones</font></div>=<br />
==Acceptance==<br />
[[Media:Chapalang_Acceptance_Slides.pdf|<font color="#CD004E"> Acceptance Presentation Slides]]<br />
==Midterm==<br />
[[IS480_Team_wiki:_2012T1_6-bit_Midterm_Wikipage | <font color="#CD004E"><b>Mid Term Wiki</b></font>]]<br />
<br><br />
[[Media:Chapalang_Midterm_Slides.pdf|<font color="#CD004E"> Midterm Presentation Slides]]<br />
==Final==<br />
[https://dl.dropbox.com/u/56071797/Final_Presentation.pptx <font color="#CD004E"><b>Final Presentation Slides</b></font>]</div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit&diff=114548IS480 Team wiki: 2012T1 6-bit2012-12-04T15:11:48Z<p>Huiling.ong.2010: /* Final */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Current Status</font></div>=<br />
<br />
{| class="wikitable" cellpadding="15"<br />
<br />
|-<br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 46%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Current Iteration</b> <br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 50%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Meeting Status</b> <br />
|-<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Iteration Number :''' <br />
16 *Final Iteration*<br />
<br><br />
'''Iteration Start Date : '''<br />
24 November 2012<br />
<br><br />
'''Iteration End Date :'''<br />
3 December 2012<br />
<br><br />
'''Iteration Task :'''<br />
<br><br />
1. Final Presentation<br />
<br><br />
2. Poster Day<br />
<br><br />
<br />
<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Weekly Meeting Schedule'''<br />
<br><br />
Every Monday, Wednesday, Friday<br />
<br><br />
SIS Analytics Kitchen<br />
<br><br />
12pm to 3pm<br />
<br><br />
<br />
'''Weekly Supervisor Meeting'''<br />
<br><br />
Every Monday<br />
<br><br />
2pm to 3pm<br />
|}<br />
<div style="text-align: right;"><br />
<font size="2">''Last Update: 28 November 2012''</font><br />
</div><br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Team</font></div>=<br />
[[Image:6-bitTeamMembers.png|alt=text|6-bitTeamMembers|centre|650px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Project: Chapalang</font></div>=<br />
<div style="text-align: center"><font color="#00BFFF">''Talk, Buy, Sell, Share, all on Chapalang!''</font></div><br />
<font color="#FE2EF7">Chapalang!</font> is a social utility that connects people with friends and new friends by offering a place for exchanging ideas and information on its public domain. People use our discussion forums to write HOWTOs, share findings, ask questions, comment on news, and many more.<br />
<br><br />
<font color="#FE2EF7">Chapalang!</font> also features a social marketplace for you to buy online, and participate in mass orders in a convenient and reliable way.<br />
<br><br />
Best of all, you can browse wish lists of your friends to know what are the right things to buy on special occasions. You could buy the gift on <br />
<font color="#FE2EF7">Chapalang!</font> and have it sent to their doorsteps, or organize a Gift Sharing campaign to share the costs of gift with other friends.<br />
<br />
[[Image:chapalangprocesses.png|1100px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Main Features</font></div>=<br />
[[Image:ChapalangLogo.png|left|150px]]<br />
<br><br />
<i>proposes the following unique features:</i><br />
<br><br />
[[Image:6-bitGroupbuyprocess.png|center|1000px]]<br />
<br><br />
<b>Gifts Sharing</b> : <br />
<br><br />
Gifting can be simple or collective. A simple gift is purchased when a user pays for the full costs of the gift, and states the recipient’s contact details upon checkout. Chapalang! will contact the recipient for their address, and subsequently fulfil the order with the delivery of goods.<br />
<br><br />
<br><br />
A collective gift is purchased when a user takes on the role of an organizer and initiates a Gift Sharing Campaign. He will select a product from a user’s wish list, or any other product in the marketplace, and designate it to be the gift to be shared. He will also decide on the product options, if any, as well as the delivery method. <br />
<br><br />
<br><br />
Thereafter, he can invite a list of mutual friends whom he wants to share the gift with. The invitees will be informed of the campaign via a notification, and will be able to contribute any varying amount on the campaign page. They will also be able to hide their amount of contribution, or even hide their contribution record from public. Upon successfully raising the target amount which is the price of the gift, an email will be sent to the recipient for him/her to update their address for fulfilment and delivery.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitMassorderprocess.png|center|1000px]]<br />
<b>Mass orders</b> : <br />
<br>Mass Orders (MO) should be structured and organized, just like a regular product item in the marketplace. <br />
<br><br />
<br><br />
When creating an MO, the buyer will input the price, description, minimum collective quantity for the MO to go through, the maximum collective quantity accepted for the MO if it’s a limited quantity offer, as well as the start and end period of the MO. An MO organizer can be an individual or a company. The organizer will be able to invite his/her friends, or regular customers to the MO. <br />
<br><br />
<br><br />
Participants of an MO will be able to view the MO page, enter a desired quantity and checkout. In the checkout process, participants will be required to enter their delivery address and choose their preferred shipping method. Payment is made upon ordering, safeguarded by the esrow service, and will be paid to the sellers if the MO is successful. In the event that MO is unsuccessful or cancelled, full amount of their orders will be refunded to all participants automatically.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitEscrowprocess.png|centre|1000px]]<br />
<b>Escrow</b> : <br />
<br><br />
In most other agent websites, buyers either pay to sellers directly or buyers pay to the agent and agent will pay the buyers 30 days later. We will turn this credit period to the advantage of buyers and sellers, introducing assurance.<br />
<br><br><br />
In any transaction on Chapalang!, the buyer will pay to Chapalang! directly. Sellers are notified of the receipt of payment, and will proceed to ship the item out to the buyer. Upon receipt of the order, buyers will revisit Chapalang! and indicate that the goods are received satisfactorily, and Chapalang! will then pay the sellers in the next 3 days. However, if there is no response or dispute from the buyers within 30 days, the order is assumed to be satisfactorily fulfilled and the payment will be released to the seller. In the event of disputes, buyers and sellers are encouraged to negotiate for a recovery, or in the case of an exhausted negotiation, Chapalang! may issue a full or partial refund to the customers.<br />
<br><br><br />
Systematically, the Chapalang! system will support this this use case through a series of functions. <br />
*Firstly, the system will support a goods receipt acknowledgement process, recording the goods receipt, triggering of payment activities to sellers upon 30 days grace or upon the record of goods receipt. <br />
*Secondly, sellers should be able to see their sales and know how much they will be receiving from Chapalang! and when. <br />
*Thirdly, there should be a messaging channel to facilitate communications between the buyer and seller<br />
*Fourthly, there should be a refund method to allow sellers to refund a transaction should be accept that he’s unable to recover or fulfil the order<br />
*Lastly, administrator of Chapalang! should be able to see a list of fulfilled, or assumed fulfilled transactions ready for payment to the sellers<br />
<br />
<div style="text-align: right;"><br />
<font size="2">''Prototype of Chapalang's Features: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype Click Here]''</font><br />
</div><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Low Level Functions</font></div>=<br />
==Web Parser==<br />
As an interactive feature, URLs shared on Chapalang! will offer a preview which contains the site title, url, image and description. This should reflect the final URL, instead of any redirecting URL at a higher level.<br />
<br><br><br />
The picking of appropriate objects (title, url, image or description) is important, where standardized Open Graph (OG) protocol meta data of a webpage will be prioritized, before seeking through the other HTML components for referencing objects.<br />
==Private Message==<br />
[[Image:6-bit_message.png|center|600px]]<br />
There should be an in-system communication channel for general users, buyers and sellers. Potential buyers can clarify product specifications with sellers, sellers can confirm delivery address with buyers in case of anomalies, and general users can use it for chatting purposes.<br />
<br><br />
<br>It should be able to perform CRUD of messages between 2 users, in a conversational format. Users are notified via email whenever they receive a message. They will also be able to see past messages exchanged, in a single conversation page.<br />
==Image Cropping Tool==<br />
As all images uploaded by users can be of different dimensions, our system will need a tool to automatically resize and crop away unimportant parts to fit the image dimensions on different pages.<br />
<br><br><br />
Hence, the Image Cropping Tool will help us with automatically resizing an image to the most suitable resolution, before cropping away any extended sides and focus on the centre of the image which is usually the most important message. This tool will be applied throughout the entire platform, on both discussion forums and marketplace.<br />
<br />
==Notifications==<br />
[[Image:6-bit_notification.png|center|300px]]<br />
Users should be appropriately notified on any activities concerning them. They will have a new notifications whenever someone replies to their post, whenever a friend is following them in Chapalang!, or when a product purchased is being shipped, et cetera.<br />
<br><br />
<br><br />
Notification entries should link them to appropriate pages for follow-up actions or even simply viewing more details of the notification. Each in-system notification should also be tied to an email notification for a timelier update to users, and users should have the ability to modify their notifications settings for privacy or information flood control.<br />
<br />
==Search function==<br />
[[Image:6-bit_search.png|center|600px]]<br />
There are many content types on Chapalang!, which includes people, messages, products, posts, et cetera. These content types should be searchable for the purpose of conveniently accessing specific content.<br />
==Profile page==<br />
[[Image:6-bit_profilepage.png|center|600px]]<br />
Every user will have a dedicated profile page, which contains their profile picture, basic particulars, activities and friends. This will create a more social environment, where information of a user is shared among friends.<br />
==Management pages==<br />
[[Image:6-bit_management.png|center|250px]]<br />
There should be a set of management pages, for the management of sales, orders or products. These pages will be able to perform basic CRUD functions, as well as other functions allowing appropriate manipulation of an activity. For example, Manage Sales will allow sellers to view transactional details as well as updating shipping details when an order is fulfilled. On the other hand, Manage Orders will allow buyers to review their purchases and be informed whether their orders are fulfilled. Correspondingly, Manage Products will allow the sellers administer all aspects of a product, from its description, images, pricing, to its options and shipping methods.<br />
<br />
==Settings pages==<br />
[[Image:6-bit_settings.png|center|600px]]<br />
There will be separate pages for Accounts Settings, Privacy Settings and Notifications Settings. Firstly, Account Settings will allow a user to change their basic information imported from Facebook. Secondly, Privacy Settings will provide the option to show or hide certain sensitive information that a user may choose not to show in the public. Lastly, Notifications Settings will help the users manage the quantity and quality of notifications that they receive as they might choose not to be informed of certain activities to prevent information overload.<br />
==Personalized dashboard==<br />
[[Image:6-bit_personalizeddb.png|center|600px]]<br />
A dashboard is the first page the user will see upon login, and will contain a mash up of content from various components on the portal. The content published to the dashboard is personalized through stratification supported by data-driven analytics.<br />
<br><br />
<br><br />
The dashboard will contain the following data:<br />
* Relevant topics from subscribed forums<br />
* Featured discussions<br />
* Product recommendations generated by analytics<br />
* Recent purchases made by friends<br />
* Featured mass orders recommendations generated by analytics<br />
* Seasonal or holidays promotional products recommendations generated by analytics<br />
* New arrival products recommendations generated by analytics<br />
* Reminders on upcoming special dates, friends’ birthdays, and activity invites<br />
The dashboard has a 2-step approach in deriving personalized content. Firstly, a set of meta data describing a user is generated. Secondly, another set of meta data describing a product is also generated. Subsequently, both set of meta data are matched to produce a list of recommendations.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Sponsor</font></div>=<br />
[[Image:Dotcom_Logo.jpg|left]]<br />
<b>Chapalang</b> is a self-proposed project for DotCom Enterprise. Upon successful development, DotCom will commercialize the project for live operations. Mr. Eric Chew, Special Projects Manager will be the primary contact from DotCom. Throughout the development and implementation stages, our team will deploy the project on the live systems provided by DotCom.<br />
<div style="margin-bottom:30px;><br />
<br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Academic Milestones</font></div>=<br />
==Acceptance==<br />
[[Media:Chapalang_Acceptance_Slides.pdf|<font color="#CD004E"> Acceptance Presentation Slides]]<br />
==Midterm==<br />
[[IS480_Team_wiki:_2012T1_6-bit_Midterm_Wikipage | <font color="#CD004E"><b>Mid Term Wiki</b></font>]]<br />
<br><br />
[[Media:Chapalang_Midterm_Slides.pdf|<font color="#CD004E"> Midterm Presentation Slides]]<br />
==Final==<br />
[[Media:Chapalang_Final_Slides.pdf|<font color="#CD004E"> *Coming Soon!*]]<br />
[https://dl.dropbox.com/u/56071797/Final_Presentation.pptx <font color="#CD004E"><b>Final Presentation Slides</b></font>]</div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit&diff=114546IS480 Team wiki: 2012T1 6-bit2012-12-04T15:10:38Z<p>Huiling.ong.2010: /* Final */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Current Status</font></div>=<br />
<br />
{| class="wikitable" cellpadding="15"<br />
<br />
|-<br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 46%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Current Iteration</b> <br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 50%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Meeting Status</b> <br />
|-<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Iteration Number :''' <br />
16 *Final Iteration*<br />
<br><br />
'''Iteration Start Date : '''<br />
24 November 2012<br />
<br><br />
'''Iteration End Date :'''<br />
3 December 2012<br />
<br><br />
'''Iteration Task :'''<br />
<br><br />
1. Final Presentation<br />
<br><br />
2. Poster Day<br />
<br><br />
<br />
<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Weekly Meeting Schedule'''<br />
<br><br />
Every Monday, Wednesday, Friday<br />
<br><br />
SIS Analytics Kitchen<br />
<br><br />
12pm to 3pm<br />
<br><br />
<br />
'''Weekly Supervisor Meeting'''<br />
<br><br />
Every Monday<br />
<br><br />
2pm to 3pm<br />
|}<br />
<div style="text-align: right;"><br />
<font size="2">''Last Update: 28 November 2012''</font><br />
</div><br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Team</font></div>=<br />
[[Image:6-bitTeamMembers.png|alt=text|6-bitTeamMembers|centre|650px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Project: Chapalang</font></div>=<br />
<div style="text-align: center"><font color="#00BFFF">''Talk, Buy, Sell, Share, all on Chapalang!''</font></div><br />
<font color="#FE2EF7">Chapalang!</font> is a social utility that connects people with friends and new friends by offering a place for exchanging ideas and information on its public domain. People use our discussion forums to write HOWTOs, share findings, ask questions, comment on news, and many more.<br />
<br><br />
<font color="#FE2EF7">Chapalang!</font> also features a social marketplace for you to buy online, and participate in mass orders in a convenient and reliable way.<br />
<br><br />
Best of all, you can browse wish lists of your friends to know what are the right things to buy on special occasions. You could buy the gift on <br />
<font color="#FE2EF7">Chapalang!</font> and have it sent to their doorsteps, or organize a Gift Sharing campaign to share the costs of gift with other friends.<br />
<br />
[[Image:chapalangprocesses.png|1100px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Main Features</font></div>=<br />
[[Image:ChapalangLogo.png|left|150px]]<br />
<br><br />
<i>proposes the following unique features:</i><br />
<br><br />
[[Image:6-bitGroupbuyprocess.png|center|1000px]]<br />
<br><br />
<b>Gifts Sharing</b> : <br />
<br><br />
Gifting can be simple or collective. A simple gift is purchased when a user pays for the full costs of the gift, and states the recipient’s contact details upon checkout. Chapalang! will contact the recipient for their address, and subsequently fulfil the order with the delivery of goods.<br />
<br><br />
<br><br />
A collective gift is purchased when a user takes on the role of an organizer and initiates a Gift Sharing Campaign. He will select a product from a user’s wish list, or any other product in the marketplace, and designate it to be the gift to be shared. He will also decide on the product options, if any, as well as the delivery method. <br />
<br><br />
<br><br />
Thereafter, he can invite a list of mutual friends whom he wants to share the gift with. The invitees will be informed of the campaign via a notification, and will be able to contribute any varying amount on the campaign page. They will also be able to hide their amount of contribution, or even hide their contribution record from public. Upon successfully raising the target amount which is the price of the gift, an email will be sent to the recipient for him/her to update their address for fulfilment and delivery.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitMassorderprocess.png|center|1000px]]<br />
<b>Mass orders</b> : <br />
<br>Mass Orders (MO) should be structured and organized, just like a regular product item in the marketplace. <br />
<br><br />
<br><br />
When creating an MO, the buyer will input the price, description, minimum collective quantity for the MO to go through, the maximum collective quantity accepted for the MO if it’s a limited quantity offer, as well as the start and end period of the MO. An MO organizer can be an individual or a company. The organizer will be able to invite his/her friends, or regular customers to the MO. <br />
<br><br />
<br><br />
Participants of an MO will be able to view the MO page, enter a desired quantity and checkout. In the checkout process, participants will be required to enter their delivery address and choose their preferred shipping method. Payment is made upon ordering, safeguarded by the esrow service, and will be paid to the sellers if the MO is successful. In the event that MO is unsuccessful or cancelled, full amount of their orders will be refunded to all participants automatically.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitEscrowprocess.png|centre|1000px]]<br />
<b>Escrow</b> : <br />
<br><br />
In most other agent websites, buyers either pay to sellers directly or buyers pay to the agent and agent will pay the buyers 30 days later. We will turn this credit period to the advantage of buyers and sellers, introducing assurance.<br />
<br><br><br />
In any transaction on Chapalang!, the buyer will pay to Chapalang! directly. Sellers are notified of the receipt of payment, and will proceed to ship the item out to the buyer. Upon receipt of the order, buyers will revisit Chapalang! and indicate that the goods are received satisfactorily, and Chapalang! will then pay the sellers in the next 3 days. However, if there is no response or dispute from the buyers within 30 days, the order is assumed to be satisfactorily fulfilled and the payment will be released to the seller. In the event of disputes, buyers and sellers are encouraged to negotiate for a recovery, or in the case of an exhausted negotiation, Chapalang! may issue a full or partial refund to the customers.<br />
<br><br><br />
Systematically, the Chapalang! system will support this this use case through a series of functions. <br />
*Firstly, the system will support a goods receipt acknowledgement process, recording the goods receipt, triggering of payment activities to sellers upon 30 days grace or upon the record of goods receipt. <br />
*Secondly, sellers should be able to see their sales and know how much they will be receiving from Chapalang! and when. <br />
*Thirdly, there should be a messaging channel to facilitate communications between the buyer and seller<br />
*Fourthly, there should be a refund method to allow sellers to refund a transaction should be accept that he’s unable to recover or fulfil the order<br />
*Lastly, administrator of Chapalang! should be able to see a list of fulfilled, or assumed fulfilled transactions ready for payment to the sellers<br />
<br />
<div style="text-align: right;"><br />
<font size="2">''Prototype of Chapalang's Features: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype Click Here]''</font><br />
</div><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Low Level Functions</font></div>=<br />
==Web Parser==<br />
As an interactive feature, URLs shared on Chapalang! will offer a preview which contains the site title, url, image and description. This should reflect the final URL, instead of any redirecting URL at a higher level.<br />
<br><br><br />
The picking of appropriate objects (title, url, image or description) is important, where standardized Open Graph (OG) protocol meta data of a webpage will be prioritized, before seeking through the other HTML components for referencing objects.<br />
==Private Message==<br />
[[Image:6-bit_message.png|center|600px]]<br />
There should be an in-system communication channel for general users, buyers and sellers. Potential buyers can clarify product specifications with sellers, sellers can confirm delivery address with buyers in case of anomalies, and general users can use it for chatting purposes.<br />
<br><br />
<br>It should be able to perform CRUD of messages between 2 users, in a conversational format. Users are notified via email whenever they receive a message. They will also be able to see past messages exchanged, in a single conversation page.<br />
==Image Cropping Tool==<br />
As all images uploaded by users can be of different dimensions, our system will need a tool to automatically resize and crop away unimportant parts to fit the image dimensions on different pages.<br />
<br><br><br />
Hence, the Image Cropping Tool will help us with automatically resizing an image to the most suitable resolution, before cropping away any extended sides and focus on the centre of the image which is usually the most important message. This tool will be applied throughout the entire platform, on both discussion forums and marketplace.<br />
<br />
==Notifications==<br />
[[Image:6-bit_notification.png|center|300px]]<br />
Users should be appropriately notified on any activities concerning them. They will have a new notifications whenever someone replies to their post, whenever a friend is following them in Chapalang!, or when a product purchased is being shipped, et cetera.<br />
<br><br />
<br><br />
Notification entries should link them to appropriate pages for follow-up actions or even simply viewing more details of the notification. Each in-system notification should also be tied to an email notification for a timelier update to users, and users should have the ability to modify their notifications settings for privacy or information flood control.<br />
<br />
==Search function==<br />
[[Image:6-bit_search.png|center|600px]]<br />
There are many content types on Chapalang!, which includes people, messages, products, posts, et cetera. These content types should be searchable for the purpose of conveniently accessing specific content.<br />
==Profile page==<br />
[[Image:6-bit_profilepage.png|center|600px]]<br />
Every user will have a dedicated profile page, which contains their profile picture, basic particulars, activities and friends. This will create a more social environment, where information of a user is shared among friends.<br />
==Management pages==<br />
[[Image:6-bit_management.png|center|250px]]<br />
There should be a set of management pages, for the management of sales, orders or products. These pages will be able to perform basic CRUD functions, as well as other functions allowing appropriate manipulation of an activity. For example, Manage Sales will allow sellers to view transactional details as well as updating shipping details when an order is fulfilled. On the other hand, Manage Orders will allow buyers to review their purchases and be informed whether their orders are fulfilled. Correspondingly, Manage Products will allow the sellers administer all aspects of a product, from its description, images, pricing, to its options and shipping methods.<br />
<br />
==Settings pages==<br />
[[Image:6-bit_settings.png|center|600px]]<br />
There will be separate pages for Accounts Settings, Privacy Settings and Notifications Settings. Firstly, Account Settings will allow a user to change their basic information imported from Facebook. Secondly, Privacy Settings will provide the option to show or hide certain sensitive information that a user may choose not to show in the public. Lastly, Notifications Settings will help the users manage the quantity and quality of notifications that they receive as they might choose not to be informed of certain activities to prevent information overload.<br />
==Personalized dashboard==<br />
[[Image:6-bit_personalizeddb.png|center|600px]]<br />
A dashboard is the first page the user will see upon login, and will contain a mash up of content from various components on the portal. The content published to the dashboard is personalized through stratification supported by data-driven analytics.<br />
<br><br />
<br><br />
The dashboard will contain the following data:<br />
* Relevant topics from subscribed forums<br />
* Featured discussions<br />
* Product recommendations generated by analytics<br />
* Recent purchases made by friends<br />
* Featured mass orders recommendations generated by analytics<br />
* Seasonal or holidays promotional products recommendations generated by analytics<br />
* New arrival products recommendations generated by analytics<br />
* Reminders on upcoming special dates, friends’ birthdays, and activity invites<br />
The dashboard has a 2-step approach in deriving personalized content. Firstly, a set of meta data describing a user is generated. Secondly, another set of meta data describing a product is also generated. Subsequently, both set of meta data are matched to produce a list of recommendations.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Sponsor</font></div>=<br />
[[Image:Dotcom_Logo.jpg|left]]<br />
<b>Chapalang</b> is a self-proposed project for DotCom Enterprise. Upon successful development, DotCom will commercialize the project for live operations. Mr. Eric Chew, Special Projects Manager will be the primary contact from DotCom. Throughout the development and implementation stages, our team will deploy the project on the live systems provided by DotCom.<br />
<div style="margin-bottom:30px;><br />
<br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Academic Milestones</font></div>=<br />
==Acceptance==<br />
[[Media:Chapalang_Acceptance_Slides.pdf|<font color="#CD004E"> Acceptance Presentation Slides]]<br />
==Midterm==<br />
[[IS480_Team_wiki:_2012T1_6-bit_Midterm_Wikipage | <font color="#CD004E"><b>Mid Term Wiki</b></font>]]<br />
<br><br />
[[Media:Chapalang_Midterm_Slides.pdf|<font color="#CD004E"> Midterm Presentation Slides]]<br />
==Final==<br />
[[Media:Chapalang_Final_Slides.pdf|<font color="#CD004E"> *Coming Soon!*]]<br />
[[https://dl.dropbox.com/u/56071797/Test%20Plan%2004_01_11_2012.docx <font color="#CD004E"><b>Test Plan 4 ''on 4 November 2012''</b></font>]<br />
<font color="#CD004E"><b>Final Presentation Slides</b></font>]</div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit&diff=114544IS480 Team wiki: 2012T1 6-bit2012-12-04T15:10:21Z<p>Huiling.ong.2010: /* Final */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Current Status</font></div>=<br />
<br />
{| class="wikitable" cellpadding="15"<br />
<br />
|-<br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 46%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Current Iteration</b> <br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 50%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Meeting Status</b> <br />
|-<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Iteration Number :''' <br />
16 *Final Iteration*<br />
<br><br />
'''Iteration Start Date : '''<br />
24 November 2012<br />
<br><br />
'''Iteration End Date :'''<br />
3 December 2012<br />
<br><br />
'''Iteration Task :'''<br />
<br><br />
1. Final Presentation<br />
<br><br />
2. Poster Day<br />
<br><br />
<br />
<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Weekly Meeting Schedule'''<br />
<br><br />
Every Monday, Wednesday, Friday<br />
<br><br />
SIS Analytics Kitchen<br />
<br><br />
12pm to 3pm<br />
<br><br />
<br />
'''Weekly Supervisor Meeting'''<br />
<br><br />
Every Monday<br />
<br><br />
2pm to 3pm<br />
|}<br />
<div style="text-align: right;"><br />
<font size="2">''Last Update: 28 November 2012''</font><br />
</div><br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Team</font></div>=<br />
[[Image:6-bitTeamMembers.png|alt=text|6-bitTeamMembers|centre|650px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Project: Chapalang</font></div>=<br />
<div style="text-align: center"><font color="#00BFFF">''Talk, Buy, Sell, Share, all on Chapalang!''</font></div><br />
<font color="#FE2EF7">Chapalang!</font> is a social utility that connects people with friends and new friends by offering a place for exchanging ideas and information on its public domain. People use our discussion forums to write HOWTOs, share findings, ask questions, comment on news, and many more.<br />
<br><br />
<font color="#FE2EF7">Chapalang!</font> also features a social marketplace for you to buy online, and participate in mass orders in a convenient and reliable way.<br />
<br><br />
Best of all, you can browse wish lists of your friends to know what are the right things to buy on special occasions. You could buy the gift on <br />
<font color="#FE2EF7">Chapalang!</font> and have it sent to their doorsteps, or organize a Gift Sharing campaign to share the costs of gift with other friends.<br />
<br />
[[Image:chapalangprocesses.png|1100px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Main Features</font></div>=<br />
[[Image:ChapalangLogo.png|left|150px]]<br />
<br><br />
<i>proposes the following unique features:</i><br />
<br><br />
[[Image:6-bitGroupbuyprocess.png|center|1000px]]<br />
<br><br />
<b>Gifts Sharing</b> : <br />
<br><br />
Gifting can be simple or collective. A simple gift is purchased when a user pays for the full costs of the gift, and states the recipient’s contact details upon checkout. Chapalang! will contact the recipient for their address, and subsequently fulfil the order with the delivery of goods.<br />
<br><br />
<br><br />
A collective gift is purchased when a user takes on the role of an organizer and initiates a Gift Sharing Campaign. He will select a product from a user’s wish list, or any other product in the marketplace, and designate it to be the gift to be shared. He will also decide on the product options, if any, as well as the delivery method. <br />
<br><br />
<br><br />
Thereafter, he can invite a list of mutual friends whom he wants to share the gift with. The invitees will be informed of the campaign via a notification, and will be able to contribute any varying amount on the campaign page. They will also be able to hide their amount of contribution, or even hide their contribution record from public. Upon successfully raising the target amount which is the price of the gift, an email will be sent to the recipient for him/her to update their address for fulfilment and delivery.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitMassorderprocess.png|center|1000px]]<br />
<b>Mass orders</b> : <br />
<br>Mass Orders (MO) should be structured and organized, just like a regular product item in the marketplace. <br />
<br><br />
<br><br />
When creating an MO, the buyer will input the price, description, minimum collective quantity for the MO to go through, the maximum collective quantity accepted for the MO if it’s a limited quantity offer, as well as the start and end period of the MO. An MO organizer can be an individual or a company. The organizer will be able to invite his/her friends, or regular customers to the MO. <br />
<br><br />
<br><br />
Participants of an MO will be able to view the MO page, enter a desired quantity and checkout. In the checkout process, participants will be required to enter their delivery address and choose their preferred shipping method. Payment is made upon ordering, safeguarded by the esrow service, and will be paid to the sellers if the MO is successful. In the event that MO is unsuccessful or cancelled, full amount of their orders will be refunded to all participants automatically.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitEscrowprocess.png|centre|1000px]]<br />
<b>Escrow</b> : <br />
<br><br />
In most other agent websites, buyers either pay to sellers directly or buyers pay to the agent and agent will pay the buyers 30 days later. We will turn this credit period to the advantage of buyers and sellers, introducing assurance.<br />
<br><br><br />
In any transaction on Chapalang!, the buyer will pay to Chapalang! directly. Sellers are notified of the receipt of payment, and will proceed to ship the item out to the buyer. Upon receipt of the order, buyers will revisit Chapalang! and indicate that the goods are received satisfactorily, and Chapalang! will then pay the sellers in the next 3 days. However, if there is no response or dispute from the buyers within 30 days, the order is assumed to be satisfactorily fulfilled and the payment will be released to the seller. In the event of disputes, buyers and sellers are encouraged to negotiate for a recovery, or in the case of an exhausted negotiation, Chapalang! may issue a full or partial refund to the customers.<br />
<br><br><br />
Systematically, the Chapalang! system will support this this use case through a series of functions. <br />
*Firstly, the system will support a goods receipt acknowledgement process, recording the goods receipt, triggering of payment activities to sellers upon 30 days grace or upon the record of goods receipt. <br />
*Secondly, sellers should be able to see their sales and know how much they will be receiving from Chapalang! and when. <br />
*Thirdly, there should be a messaging channel to facilitate communications between the buyer and seller<br />
*Fourthly, there should be a refund method to allow sellers to refund a transaction should be accept that he’s unable to recover or fulfil the order<br />
*Lastly, administrator of Chapalang! should be able to see a list of fulfilled, or assumed fulfilled transactions ready for payment to the sellers<br />
<br />
<div style="text-align: right;"><br />
<font size="2">''Prototype of Chapalang's Features: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype Click Here]''</font><br />
</div><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Low Level Functions</font></div>=<br />
==Web Parser==<br />
As an interactive feature, URLs shared on Chapalang! will offer a preview which contains the site title, url, image and description. This should reflect the final URL, instead of any redirecting URL at a higher level.<br />
<br><br><br />
The picking of appropriate objects (title, url, image or description) is important, where standardized Open Graph (OG) protocol meta data of a webpage will be prioritized, before seeking through the other HTML components for referencing objects.<br />
==Private Message==<br />
[[Image:6-bit_message.png|center|600px]]<br />
There should be an in-system communication channel for general users, buyers and sellers. Potential buyers can clarify product specifications with sellers, sellers can confirm delivery address with buyers in case of anomalies, and general users can use it for chatting purposes.<br />
<br><br />
<br>It should be able to perform CRUD of messages between 2 users, in a conversational format. Users are notified via email whenever they receive a message. They will also be able to see past messages exchanged, in a single conversation page.<br />
==Image Cropping Tool==<br />
As all images uploaded by users can be of different dimensions, our system will need a tool to automatically resize and crop away unimportant parts to fit the image dimensions on different pages.<br />
<br><br><br />
Hence, the Image Cropping Tool will help us with automatically resizing an image to the most suitable resolution, before cropping away any extended sides and focus on the centre of the image which is usually the most important message. This tool will be applied throughout the entire platform, on both discussion forums and marketplace.<br />
<br />
==Notifications==<br />
[[Image:6-bit_notification.png|center|300px]]<br />
Users should be appropriately notified on any activities concerning them. They will have a new notifications whenever someone replies to their post, whenever a friend is following them in Chapalang!, or when a product purchased is being shipped, et cetera.<br />
<br><br />
<br><br />
Notification entries should link them to appropriate pages for follow-up actions or even simply viewing more details of the notification. Each in-system notification should also be tied to an email notification for a timelier update to users, and users should have the ability to modify their notifications settings for privacy or information flood control.<br />
<br />
==Search function==<br />
[[Image:6-bit_search.png|center|600px]]<br />
There are many content types on Chapalang!, which includes people, messages, products, posts, et cetera. These content types should be searchable for the purpose of conveniently accessing specific content.<br />
==Profile page==<br />
[[Image:6-bit_profilepage.png|center|600px]]<br />
Every user will have a dedicated profile page, which contains their profile picture, basic particulars, activities and friends. This will create a more social environment, where information of a user is shared among friends.<br />
==Management pages==<br />
[[Image:6-bit_management.png|center|250px]]<br />
There should be a set of management pages, for the management of sales, orders or products. These pages will be able to perform basic CRUD functions, as well as other functions allowing appropriate manipulation of an activity. For example, Manage Sales will allow sellers to view transactional details as well as updating shipping details when an order is fulfilled. On the other hand, Manage Orders will allow buyers to review their purchases and be informed whether their orders are fulfilled. Correspondingly, Manage Products will allow the sellers administer all aspects of a product, from its description, images, pricing, to its options and shipping methods.<br />
<br />
==Settings pages==<br />
[[Image:6-bit_settings.png|center|600px]]<br />
There will be separate pages for Accounts Settings, Privacy Settings and Notifications Settings. Firstly, Account Settings will allow a user to change their basic information imported from Facebook. Secondly, Privacy Settings will provide the option to show or hide certain sensitive information that a user may choose not to show in the public. Lastly, Notifications Settings will help the users manage the quantity and quality of notifications that they receive as they might choose not to be informed of certain activities to prevent information overload.<br />
==Personalized dashboard==<br />
[[Image:6-bit_personalizeddb.png|center|600px]]<br />
A dashboard is the first page the user will see upon login, and will contain a mash up of content from various components on the portal. The content published to the dashboard is personalized through stratification supported by data-driven analytics.<br />
<br><br />
<br><br />
The dashboard will contain the following data:<br />
* Relevant topics from subscribed forums<br />
* Featured discussions<br />
* Product recommendations generated by analytics<br />
* Recent purchases made by friends<br />
* Featured mass orders recommendations generated by analytics<br />
* Seasonal or holidays promotional products recommendations generated by analytics<br />
* New arrival products recommendations generated by analytics<br />
* Reminders on upcoming special dates, friends’ birthdays, and activity invites<br />
The dashboard has a 2-step approach in deriving personalized content. Firstly, a set of meta data describing a user is generated. Secondly, another set of meta data describing a product is also generated. Subsequently, both set of meta data are matched to produce a list of recommendations.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Sponsor</font></div>=<br />
[[Image:Dotcom_Logo.jpg|left]]<br />
<b>Chapalang</b> is a self-proposed project for DotCom Enterprise. Upon successful development, DotCom will commercialize the project for live operations. Mr. Eric Chew, Special Projects Manager will be the primary contact from DotCom. Throughout the development and implementation stages, our team will deploy the project on the live systems provided by DotCom.<br />
<div style="margin-bottom:30px;><br />
<br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Academic Milestones</font></div>=<br />
==Acceptance==<br />
[[Media:Chapalang_Acceptance_Slides.pdf|<font color="#CD004E"> Acceptance Presentation Slides]]<br />
==Midterm==<br />
[[IS480_Team_wiki:_2012T1_6-bit_Midterm_Wikipage | <font color="#CD004E"><b>Mid Term Wiki</b></font>]]<br />
<br><br />
[[Media:Chapalang_Midterm_Slides.pdf|<font color="#CD004E"> Midterm Presentation Slides]]<br />
==Final==<br />
[[Media:Chapalang_Final_Slides.pdf|<font color="#CD004E"> *Coming Soon!*]]<br />
[https://dl.dropbox.com/u/56071797/Final_Presentation.pptx <font color="#CD004E"><b>Final Presentation Slides</b></font>]</div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit&diff=114543IS480 Team wiki: 2012T1 6-bit2012-12-04T15:10:12Z<p>Huiling.ong.2010: /* Final */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Current Status</font></div>=<br />
<br />
{| class="wikitable" cellpadding="15"<br />
<br />
|-<br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 46%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Current Iteration</b> <br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 50%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Meeting Status</b> <br />
|-<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Iteration Number :''' <br />
16 *Final Iteration*<br />
<br><br />
'''Iteration Start Date : '''<br />
24 November 2012<br />
<br><br />
'''Iteration End Date :'''<br />
3 December 2012<br />
<br><br />
'''Iteration Task :'''<br />
<br><br />
1. Final Presentation<br />
<br><br />
2. Poster Day<br />
<br><br />
<br />
<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Weekly Meeting Schedule'''<br />
<br><br />
Every Monday, Wednesday, Friday<br />
<br><br />
SIS Analytics Kitchen<br />
<br><br />
12pm to 3pm<br />
<br><br />
<br />
'''Weekly Supervisor Meeting'''<br />
<br><br />
Every Monday<br />
<br><br />
2pm to 3pm<br />
|}<br />
<div style="text-align: right;"><br />
<font size="2">''Last Update: 28 November 2012''</font><br />
</div><br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Team</font></div>=<br />
[[Image:6-bitTeamMembers.png|alt=text|6-bitTeamMembers|centre|650px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Project: Chapalang</font></div>=<br />
<div style="text-align: center"><font color="#00BFFF">''Talk, Buy, Sell, Share, all on Chapalang!''</font></div><br />
<font color="#FE2EF7">Chapalang!</font> is a social utility that connects people with friends and new friends by offering a place for exchanging ideas and information on its public domain. People use our discussion forums to write HOWTOs, share findings, ask questions, comment on news, and many more.<br />
<br><br />
<font color="#FE2EF7">Chapalang!</font> also features a social marketplace for you to buy online, and participate in mass orders in a convenient and reliable way.<br />
<br><br />
Best of all, you can browse wish lists of your friends to know what are the right things to buy on special occasions. You could buy the gift on <br />
<font color="#FE2EF7">Chapalang!</font> and have it sent to their doorsteps, or organize a Gift Sharing campaign to share the costs of gift with other friends.<br />
<br />
[[Image:chapalangprocesses.png|1100px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Main Features</font></div>=<br />
[[Image:ChapalangLogo.png|left|150px]]<br />
<br><br />
<i>proposes the following unique features:</i><br />
<br><br />
[[Image:6-bitGroupbuyprocess.png|center|1000px]]<br />
<br><br />
<b>Gifts Sharing</b> : <br />
<br><br />
Gifting can be simple or collective. A simple gift is purchased when a user pays for the full costs of the gift, and states the recipient’s contact details upon checkout. Chapalang! will contact the recipient for their address, and subsequently fulfil the order with the delivery of goods.<br />
<br><br />
<br><br />
A collective gift is purchased when a user takes on the role of an organizer and initiates a Gift Sharing Campaign. He will select a product from a user’s wish list, or any other product in the marketplace, and designate it to be the gift to be shared. He will also decide on the product options, if any, as well as the delivery method. <br />
<br><br />
<br><br />
Thereafter, he can invite a list of mutual friends whom he wants to share the gift with. The invitees will be informed of the campaign via a notification, and will be able to contribute any varying amount on the campaign page. They will also be able to hide their amount of contribution, or even hide their contribution record from public. Upon successfully raising the target amount which is the price of the gift, an email will be sent to the recipient for him/her to update their address for fulfilment and delivery.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitMassorderprocess.png|center|1000px]]<br />
<b>Mass orders</b> : <br />
<br>Mass Orders (MO) should be structured and organized, just like a regular product item in the marketplace. <br />
<br><br />
<br><br />
When creating an MO, the buyer will input the price, description, minimum collective quantity for the MO to go through, the maximum collective quantity accepted for the MO if it’s a limited quantity offer, as well as the start and end period of the MO. An MO organizer can be an individual or a company. The organizer will be able to invite his/her friends, or regular customers to the MO. <br />
<br><br />
<br><br />
Participants of an MO will be able to view the MO page, enter a desired quantity and checkout. In the checkout process, participants will be required to enter their delivery address and choose their preferred shipping method. Payment is made upon ordering, safeguarded by the esrow service, and will be paid to the sellers if the MO is successful. In the event that MO is unsuccessful or cancelled, full amount of their orders will be refunded to all participants automatically.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitEscrowprocess.png|centre|1000px]]<br />
<b>Escrow</b> : <br />
<br><br />
In most other agent websites, buyers either pay to sellers directly or buyers pay to the agent and agent will pay the buyers 30 days later. We will turn this credit period to the advantage of buyers and sellers, introducing assurance.<br />
<br><br><br />
In any transaction on Chapalang!, the buyer will pay to Chapalang! directly. Sellers are notified of the receipt of payment, and will proceed to ship the item out to the buyer. Upon receipt of the order, buyers will revisit Chapalang! and indicate that the goods are received satisfactorily, and Chapalang! will then pay the sellers in the next 3 days. However, if there is no response or dispute from the buyers within 30 days, the order is assumed to be satisfactorily fulfilled and the payment will be released to the seller. In the event of disputes, buyers and sellers are encouraged to negotiate for a recovery, or in the case of an exhausted negotiation, Chapalang! may issue a full or partial refund to the customers.<br />
<br><br><br />
Systematically, the Chapalang! system will support this this use case through a series of functions. <br />
*Firstly, the system will support a goods receipt acknowledgement process, recording the goods receipt, triggering of payment activities to sellers upon 30 days grace or upon the record of goods receipt. <br />
*Secondly, sellers should be able to see their sales and know how much they will be receiving from Chapalang! and when. <br />
*Thirdly, there should be a messaging channel to facilitate communications between the buyer and seller<br />
*Fourthly, there should be a refund method to allow sellers to refund a transaction should be accept that he’s unable to recover or fulfil the order<br />
*Lastly, administrator of Chapalang! should be able to see a list of fulfilled, or assumed fulfilled transactions ready for payment to the sellers<br />
<br />
<div style="text-align: right;"><br />
<font size="2">''Prototype of Chapalang's Features: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype Click Here]''</font><br />
</div><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Low Level Functions</font></div>=<br />
==Web Parser==<br />
As an interactive feature, URLs shared on Chapalang! will offer a preview which contains the site title, url, image and description. This should reflect the final URL, instead of any redirecting URL at a higher level.<br />
<br><br><br />
The picking of appropriate objects (title, url, image or description) is important, where standardized Open Graph (OG) protocol meta data of a webpage will be prioritized, before seeking through the other HTML components for referencing objects.<br />
==Private Message==<br />
[[Image:6-bit_message.png|center|600px]]<br />
There should be an in-system communication channel for general users, buyers and sellers. Potential buyers can clarify product specifications with sellers, sellers can confirm delivery address with buyers in case of anomalies, and general users can use it for chatting purposes.<br />
<br><br />
<br>It should be able to perform CRUD of messages between 2 users, in a conversational format. Users are notified via email whenever they receive a message. They will also be able to see past messages exchanged, in a single conversation page.<br />
==Image Cropping Tool==<br />
As all images uploaded by users can be of different dimensions, our system will need a tool to automatically resize and crop away unimportant parts to fit the image dimensions on different pages.<br />
<br><br><br />
Hence, the Image Cropping Tool will help us with automatically resizing an image to the most suitable resolution, before cropping away any extended sides and focus on the centre of the image which is usually the most important message. This tool will be applied throughout the entire platform, on both discussion forums and marketplace.<br />
<br />
==Notifications==<br />
[[Image:6-bit_notification.png|center|300px]]<br />
Users should be appropriately notified on any activities concerning them. They will have a new notifications whenever someone replies to their post, whenever a friend is following them in Chapalang!, or when a product purchased is being shipped, et cetera.<br />
<br><br />
<br><br />
Notification entries should link them to appropriate pages for follow-up actions or even simply viewing more details of the notification. Each in-system notification should also be tied to an email notification for a timelier update to users, and users should have the ability to modify their notifications settings for privacy or information flood control.<br />
<br />
==Search function==<br />
[[Image:6-bit_search.png|center|600px]]<br />
There are many content types on Chapalang!, which includes people, messages, products, posts, et cetera. These content types should be searchable for the purpose of conveniently accessing specific content.<br />
==Profile page==<br />
[[Image:6-bit_profilepage.png|center|600px]]<br />
Every user will have a dedicated profile page, which contains their profile picture, basic particulars, activities and friends. This will create a more social environment, where information of a user is shared among friends.<br />
==Management pages==<br />
[[Image:6-bit_management.png|center|250px]]<br />
There should be a set of management pages, for the management of sales, orders or products. These pages will be able to perform basic CRUD functions, as well as other functions allowing appropriate manipulation of an activity. For example, Manage Sales will allow sellers to view transactional details as well as updating shipping details when an order is fulfilled. On the other hand, Manage Orders will allow buyers to review their purchases and be informed whether their orders are fulfilled. Correspondingly, Manage Products will allow the sellers administer all aspects of a product, from its description, images, pricing, to its options and shipping methods.<br />
<br />
==Settings pages==<br />
[[Image:6-bit_settings.png|center|600px]]<br />
There will be separate pages for Accounts Settings, Privacy Settings and Notifications Settings. Firstly, Account Settings will allow a user to change their basic information imported from Facebook. Secondly, Privacy Settings will provide the option to show or hide certain sensitive information that a user may choose not to show in the public. Lastly, Notifications Settings will help the users manage the quantity and quality of notifications that they receive as they might choose not to be informed of certain activities to prevent information overload.<br />
==Personalized dashboard==<br />
[[Image:6-bit_personalizeddb.png|center|600px]]<br />
A dashboard is the first page the user will see upon login, and will contain a mash up of content from various components on the portal. The content published to the dashboard is personalized through stratification supported by data-driven analytics.<br />
<br><br />
<br><br />
The dashboard will contain the following data:<br />
* Relevant topics from subscribed forums<br />
* Featured discussions<br />
* Product recommendations generated by analytics<br />
* Recent purchases made by friends<br />
* Featured mass orders recommendations generated by analytics<br />
* Seasonal or holidays promotional products recommendations generated by analytics<br />
* New arrival products recommendations generated by analytics<br />
* Reminders on upcoming special dates, friends’ birthdays, and activity invites<br />
The dashboard has a 2-step approach in deriving personalized content. Firstly, a set of meta data describing a user is generated. Secondly, another set of meta data describing a product is also generated. Subsequently, both set of meta data are matched to produce a list of recommendations.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Sponsor</font></div>=<br />
[[Image:Dotcom_Logo.jpg|left]]<br />
<b>Chapalang</b> is a self-proposed project for DotCom Enterprise. Upon successful development, DotCom will commercialize the project for live operations. Mr. Eric Chew, Special Projects Manager will be the primary contact from DotCom. Throughout the development and implementation stages, our team will deploy the project on the live systems provided by DotCom.<br />
<div style="margin-bottom:30px;><br />
<br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Academic Milestones</font></div>=<br />
==Acceptance==<br />
[[Media:Chapalang_Acceptance_Slides.pdf|<font color="#CD004E"> Acceptance Presentation Slides]]<br />
==Midterm==<br />
[[IS480_Team_wiki:_2012T1_6-bit_Midterm_Wikipage | <font color="#CD004E"><b>Mid Term Wiki</b></font>]]<br />
<br><br />
[[Media:Chapalang_Midterm_Slides.pdf|<font color="#CD004E"> Midterm Presentation Slides]]<br />
==Final==<br />
[[Media:Chapalang_Final_Slides.pdf|<font color="#CD004E"> *Coming Soon!*]]<br />
[https://dl.dropbox.com/u/56071797/Final_Presentation.pptx |<font color="#CD004E"><b>Final Presentation Slides</b></font>]</div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit&diff=114541IS480 Team wiki: 2012T1 6-bit2012-12-04T15:09:48Z<p>Huiling.ong.2010: /* Final */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Current Status</font></div>=<br />
<br />
{| class="wikitable" cellpadding="15"<br />
<br />
|-<br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 46%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Current Iteration</b> <br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 50%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Meeting Status</b> <br />
|-<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Iteration Number :''' <br />
16 *Final Iteration*<br />
<br><br />
'''Iteration Start Date : '''<br />
24 November 2012<br />
<br><br />
'''Iteration End Date :'''<br />
3 December 2012<br />
<br><br />
'''Iteration Task :'''<br />
<br><br />
1. Final Presentation<br />
<br><br />
2. Poster Day<br />
<br><br />
<br />
<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Weekly Meeting Schedule'''<br />
<br><br />
Every Monday, Wednesday, Friday<br />
<br><br />
SIS Analytics Kitchen<br />
<br><br />
12pm to 3pm<br />
<br><br />
<br />
'''Weekly Supervisor Meeting'''<br />
<br><br />
Every Monday<br />
<br><br />
2pm to 3pm<br />
|}<br />
<div style="text-align: right;"><br />
<font size="2">''Last Update: 28 November 2012''</font><br />
</div><br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Team</font></div>=<br />
[[Image:6-bitTeamMembers.png|alt=text|6-bitTeamMembers|centre|650px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Project: Chapalang</font></div>=<br />
<div style="text-align: center"><font color="#00BFFF">''Talk, Buy, Sell, Share, all on Chapalang!''</font></div><br />
<font color="#FE2EF7">Chapalang!</font> is a social utility that connects people with friends and new friends by offering a place for exchanging ideas and information on its public domain. People use our discussion forums to write HOWTOs, share findings, ask questions, comment on news, and many more.<br />
<br><br />
<font color="#FE2EF7">Chapalang!</font> also features a social marketplace for you to buy online, and participate in mass orders in a convenient and reliable way.<br />
<br><br />
Best of all, you can browse wish lists of your friends to know what are the right things to buy on special occasions. You could buy the gift on <br />
<font color="#FE2EF7">Chapalang!</font> and have it sent to their doorsteps, or organize a Gift Sharing campaign to share the costs of gift with other friends.<br />
<br />
[[Image:chapalangprocesses.png|1100px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Main Features</font></div>=<br />
[[Image:ChapalangLogo.png|left|150px]]<br />
<br><br />
<i>proposes the following unique features:</i><br />
<br><br />
[[Image:6-bitGroupbuyprocess.png|center|1000px]]<br />
<br><br />
<b>Gifts Sharing</b> : <br />
<br><br />
Gifting can be simple or collective. A simple gift is purchased when a user pays for the full costs of the gift, and states the recipient’s contact details upon checkout. Chapalang! will contact the recipient for their address, and subsequently fulfil the order with the delivery of goods.<br />
<br><br />
<br><br />
A collective gift is purchased when a user takes on the role of an organizer and initiates a Gift Sharing Campaign. He will select a product from a user’s wish list, or any other product in the marketplace, and designate it to be the gift to be shared. He will also decide on the product options, if any, as well as the delivery method. <br />
<br><br />
<br><br />
Thereafter, he can invite a list of mutual friends whom he wants to share the gift with. The invitees will be informed of the campaign via a notification, and will be able to contribute any varying amount on the campaign page. They will also be able to hide their amount of contribution, or even hide their contribution record from public. Upon successfully raising the target amount which is the price of the gift, an email will be sent to the recipient for him/her to update their address for fulfilment and delivery.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitMassorderprocess.png|center|1000px]]<br />
<b>Mass orders</b> : <br />
<br>Mass Orders (MO) should be structured and organized, just like a regular product item in the marketplace. <br />
<br><br />
<br><br />
When creating an MO, the buyer will input the price, description, minimum collective quantity for the MO to go through, the maximum collective quantity accepted for the MO if it’s a limited quantity offer, as well as the start and end period of the MO. An MO organizer can be an individual or a company. The organizer will be able to invite his/her friends, or regular customers to the MO. <br />
<br><br />
<br><br />
Participants of an MO will be able to view the MO page, enter a desired quantity and checkout. In the checkout process, participants will be required to enter their delivery address and choose their preferred shipping method. Payment is made upon ordering, safeguarded by the esrow service, and will be paid to the sellers if the MO is successful. In the event that MO is unsuccessful or cancelled, full amount of their orders will be refunded to all participants automatically.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitEscrowprocess.png|centre|1000px]]<br />
<b>Escrow</b> : <br />
<br><br />
In most other agent websites, buyers either pay to sellers directly or buyers pay to the agent and agent will pay the buyers 30 days later. We will turn this credit period to the advantage of buyers and sellers, introducing assurance.<br />
<br><br><br />
In any transaction on Chapalang!, the buyer will pay to Chapalang! directly. Sellers are notified of the receipt of payment, and will proceed to ship the item out to the buyer. Upon receipt of the order, buyers will revisit Chapalang! and indicate that the goods are received satisfactorily, and Chapalang! will then pay the sellers in the next 3 days. However, if there is no response or dispute from the buyers within 30 days, the order is assumed to be satisfactorily fulfilled and the payment will be released to the seller. In the event of disputes, buyers and sellers are encouraged to negotiate for a recovery, or in the case of an exhausted negotiation, Chapalang! may issue a full or partial refund to the customers.<br />
<br><br><br />
Systematically, the Chapalang! system will support this this use case through a series of functions. <br />
*Firstly, the system will support a goods receipt acknowledgement process, recording the goods receipt, triggering of payment activities to sellers upon 30 days grace or upon the record of goods receipt. <br />
*Secondly, sellers should be able to see their sales and know how much they will be receiving from Chapalang! and when. <br />
*Thirdly, there should be a messaging channel to facilitate communications between the buyer and seller<br />
*Fourthly, there should be a refund method to allow sellers to refund a transaction should be accept that he’s unable to recover or fulfil the order<br />
*Lastly, administrator of Chapalang! should be able to see a list of fulfilled, or assumed fulfilled transactions ready for payment to the sellers<br />
<br />
<div style="text-align: right;"><br />
<font size="2">''Prototype of Chapalang's Features: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype Click Here]''</font><br />
</div><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Low Level Functions</font></div>=<br />
==Web Parser==<br />
As an interactive feature, URLs shared on Chapalang! will offer a preview which contains the site title, url, image and description. This should reflect the final URL, instead of any redirecting URL at a higher level.<br />
<br><br><br />
The picking of appropriate objects (title, url, image or description) is important, where standardized Open Graph (OG) protocol meta data of a webpage will be prioritized, before seeking through the other HTML components for referencing objects.<br />
==Private Message==<br />
[[Image:6-bit_message.png|center|600px]]<br />
There should be an in-system communication channel for general users, buyers and sellers. Potential buyers can clarify product specifications with sellers, sellers can confirm delivery address with buyers in case of anomalies, and general users can use it for chatting purposes.<br />
<br><br />
<br>It should be able to perform CRUD of messages between 2 users, in a conversational format. Users are notified via email whenever they receive a message. They will also be able to see past messages exchanged, in a single conversation page.<br />
==Image Cropping Tool==<br />
As all images uploaded by users can be of different dimensions, our system will need a tool to automatically resize and crop away unimportant parts to fit the image dimensions on different pages.<br />
<br><br><br />
Hence, the Image Cropping Tool will help us with automatically resizing an image to the most suitable resolution, before cropping away any extended sides and focus on the centre of the image which is usually the most important message. This tool will be applied throughout the entire platform, on both discussion forums and marketplace.<br />
<br />
==Notifications==<br />
[[Image:6-bit_notification.png|center|300px]]<br />
Users should be appropriately notified on any activities concerning them. They will have a new notifications whenever someone replies to their post, whenever a friend is following them in Chapalang!, or when a product purchased is being shipped, et cetera.<br />
<br><br />
<br><br />
Notification entries should link them to appropriate pages for follow-up actions or even simply viewing more details of the notification. Each in-system notification should also be tied to an email notification for a timelier update to users, and users should have the ability to modify their notifications settings for privacy or information flood control.<br />
<br />
==Search function==<br />
[[Image:6-bit_search.png|center|600px]]<br />
There are many content types on Chapalang!, which includes people, messages, products, posts, et cetera. These content types should be searchable for the purpose of conveniently accessing specific content.<br />
==Profile page==<br />
[[Image:6-bit_profilepage.png|center|600px]]<br />
Every user will have a dedicated profile page, which contains their profile picture, basic particulars, activities and friends. This will create a more social environment, where information of a user is shared among friends.<br />
==Management pages==<br />
[[Image:6-bit_management.png|center|250px]]<br />
There should be a set of management pages, for the management of sales, orders or products. These pages will be able to perform basic CRUD functions, as well as other functions allowing appropriate manipulation of an activity. For example, Manage Sales will allow sellers to view transactional details as well as updating shipping details when an order is fulfilled. On the other hand, Manage Orders will allow buyers to review their purchases and be informed whether their orders are fulfilled. Correspondingly, Manage Products will allow the sellers administer all aspects of a product, from its description, images, pricing, to its options and shipping methods.<br />
<br />
==Settings pages==<br />
[[Image:6-bit_settings.png|center|600px]]<br />
There will be separate pages for Accounts Settings, Privacy Settings and Notifications Settings. Firstly, Account Settings will allow a user to change their basic information imported from Facebook. Secondly, Privacy Settings will provide the option to show or hide certain sensitive information that a user may choose not to show in the public. Lastly, Notifications Settings will help the users manage the quantity and quality of notifications that they receive as they might choose not to be informed of certain activities to prevent information overload.<br />
==Personalized dashboard==<br />
[[Image:6-bit_personalizeddb.png|center|600px]]<br />
A dashboard is the first page the user will see upon login, and will contain a mash up of content from various components on the portal. The content published to the dashboard is personalized through stratification supported by data-driven analytics.<br />
<br><br />
<br><br />
The dashboard will contain the following data:<br />
* Relevant topics from subscribed forums<br />
* Featured discussions<br />
* Product recommendations generated by analytics<br />
* Recent purchases made by friends<br />
* Featured mass orders recommendations generated by analytics<br />
* Seasonal or holidays promotional products recommendations generated by analytics<br />
* New arrival products recommendations generated by analytics<br />
* Reminders on upcoming special dates, friends’ birthdays, and activity invites<br />
The dashboard has a 2-step approach in deriving personalized content. Firstly, a set of meta data describing a user is generated. Secondly, another set of meta data describing a product is also generated. Subsequently, both set of meta data are matched to produce a list of recommendations.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Sponsor</font></div>=<br />
[[Image:Dotcom_Logo.jpg|left]]<br />
<b>Chapalang</b> is a self-proposed project for DotCom Enterprise. Upon successful development, DotCom will commercialize the project for live operations. Mr. Eric Chew, Special Projects Manager will be the primary contact from DotCom. Throughout the development and implementation stages, our team will deploy the project on the live systems provided by DotCom.<br />
<div style="margin-bottom:30px;><br />
<br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Academic Milestones</font></div>=<br />
==Acceptance==<br />
[[Media:Chapalang_Acceptance_Slides.pdf|<font color="#CD004E"> Acceptance Presentation Slides]]<br />
==Midterm==<br />
[[IS480_Team_wiki:_2012T1_6-bit_Midterm_Wikipage | <font color="#CD004E"><b>Mid Term Wiki</b></font>]]<br />
<br><br />
[[Media:Chapalang_Midterm_Slides.pdf|<font color="#CD004E"> Midterm Presentation Slides]]<br />
==Final==<br />
[[Media:Chapalang_Final_Slides.pdf|<font color="#CD004E"> *Coming Soon!*]]<br />
[[https://dl.dropbox.com/u/56071797/Final_Presentation.pptx |<font color="#CD004E"><b>Final Presentation Slides</b></font>]]</div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit&diff=114540IS480 Team wiki: 2012T1 6-bit2012-12-04T15:08:58Z<p>Huiling.ong.2010: /* Final */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Current Status</font></div>=<br />
<br />
{| class="wikitable" cellpadding="15"<br />
<br />
|-<br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 46%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Current Iteration</b> <br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 50%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Meeting Status</b> <br />
|-<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Iteration Number :''' <br />
16 *Final Iteration*<br />
<br><br />
'''Iteration Start Date : '''<br />
24 November 2012<br />
<br><br />
'''Iteration End Date :'''<br />
3 December 2012<br />
<br><br />
'''Iteration Task :'''<br />
<br><br />
1. Final Presentation<br />
<br><br />
2. Poster Day<br />
<br><br />
<br />
<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Weekly Meeting Schedule'''<br />
<br><br />
Every Monday, Wednesday, Friday<br />
<br><br />
SIS Analytics Kitchen<br />
<br><br />
12pm to 3pm<br />
<br><br />
<br />
'''Weekly Supervisor Meeting'''<br />
<br><br />
Every Monday<br />
<br><br />
2pm to 3pm<br />
|}<br />
<div style="text-align: right;"><br />
<font size="2">''Last Update: 28 November 2012''</font><br />
</div><br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Team</font></div>=<br />
[[Image:6-bitTeamMembers.png|alt=text|6-bitTeamMembers|centre|650px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Project: Chapalang</font></div>=<br />
<div style="text-align: center"><font color="#00BFFF">''Talk, Buy, Sell, Share, all on Chapalang!''</font></div><br />
<font color="#FE2EF7">Chapalang!</font> is a social utility that connects people with friends and new friends by offering a place for exchanging ideas and information on its public domain. People use our discussion forums to write HOWTOs, share findings, ask questions, comment on news, and many more.<br />
<br><br />
<font color="#FE2EF7">Chapalang!</font> also features a social marketplace for you to buy online, and participate in mass orders in a convenient and reliable way.<br />
<br><br />
Best of all, you can browse wish lists of your friends to know what are the right things to buy on special occasions. You could buy the gift on <br />
<font color="#FE2EF7">Chapalang!</font> and have it sent to their doorsteps, or organize a Gift Sharing campaign to share the costs of gift with other friends.<br />
<br />
[[Image:chapalangprocesses.png|1100px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Main Features</font></div>=<br />
[[Image:ChapalangLogo.png|left|150px]]<br />
<br><br />
<i>proposes the following unique features:</i><br />
<br><br />
[[Image:6-bitGroupbuyprocess.png|center|1000px]]<br />
<br><br />
<b>Gifts Sharing</b> : <br />
<br><br />
Gifting can be simple or collective. A simple gift is purchased when a user pays for the full costs of the gift, and states the recipient’s contact details upon checkout. Chapalang! will contact the recipient for their address, and subsequently fulfil the order with the delivery of goods.<br />
<br><br />
<br><br />
A collective gift is purchased when a user takes on the role of an organizer and initiates a Gift Sharing Campaign. He will select a product from a user’s wish list, or any other product in the marketplace, and designate it to be the gift to be shared. He will also decide on the product options, if any, as well as the delivery method. <br />
<br><br />
<br><br />
Thereafter, he can invite a list of mutual friends whom he wants to share the gift with. The invitees will be informed of the campaign via a notification, and will be able to contribute any varying amount on the campaign page. They will also be able to hide their amount of contribution, or even hide their contribution record from public. Upon successfully raising the target amount which is the price of the gift, an email will be sent to the recipient for him/her to update their address for fulfilment and delivery.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitMassorderprocess.png|center|1000px]]<br />
<b>Mass orders</b> : <br />
<br>Mass Orders (MO) should be structured and organized, just like a regular product item in the marketplace. <br />
<br><br />
<br><br />
When creating an MO, the buyer will input the price, description, minimum collective quantity for the MO to go through, the maximum collective quantity accepted for the MO if it’s a limited quantity offer, as well as the start and end period of the MO. An MO organizer can be an individual or a company. The organizer will be able to invite his/her friends, or regular customers to the MO. <br />
<br><br />
<br><br />
Participants of an MO will be able to view the MO page, enter a desired quantity and checkout. In the checkout process, participants will be required to enter their delivery address and choose their preferred shipping method. Payment is made upon ordering, safeguarded by the esrow service, and will be paid to the sellers if the MO is successful. In the event that MO is unsuccessful or cancelled, full amount of their orders will be refunded to all participants automatically.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitEscrowprocess.png|centre|1000px]]<br />
<b>Escrow</b> : <br />
<br><br />
In most other agent websites, buyers either pay to sellers directly or buyers pay to the agent and agent will pay the buyers 30 days later. We will turn this credit period to the advantage of buyers and sellers, introducing assurance.<br />
<br><br><br />
In any transaction on Chapalang!, the buyer will pay to Chapalang! directly. Sellers are notified of the receipt of payment, and will proceed to ship the item out to the buyer. Upon receipt of the order, buyers will revisit Chapalang! and indicate that the goods are received satisfactorily, and Chapalang! will then pay the sellers in the next 3 days. However, if there is no response or dispute from the buyers within 30 days, the order is assumed to be satisfactorily fulfilled and the payment will be released to the seller. In the event of disputes, buyers and sellers are encouraged to negotiate for a recovery, or in the case of an exhausted negotiation, Chapalang! may issue a full or partial refund to the customers.<br />
<br><br><br />
Systematically, the Chapalang! system will support this this use case through a series of functions. <br />
*Firstly, the system will support a goods receipt acknowledgement process, recording the goods receipt, triggering of payment activities to sellers upon 30 days grace or upon the record of goods receipt. <br />
*Secondly, sellers should be able to see their sales and know how much they will be receiving from Chapalang! and when. <br />
*Thirdly, there should be a messaging channel to facilitate communications between the buyer and seller<br />
*Fourthly, there should be a refund method to allow sellers to refund a transaction should be accept that he’s unable to recover or fulfil the order<br />
*Lastly, administrator of Chapalang! should be able to see a list of fulfilled, or assumed fulfilled transactions ready for payment to the sellers<br />
<br />
<div style="text-align: right;"><br />
<font size="2">''Prototype of Chapalang's Features: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype Click Here]''</font><br />
</div><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Low Level Functions</font></div>=<br />
==Web Parser==<br />
As an interactive feature, URLs shared on Chapalang! will offer a preview which contains the site title, url, image and description. This should reflect the final URL, instead of any redirecting URL at a higher level.<br />
<br><br><br />
The picking of appropriate objects (title, url, image or description) is important, where standardized Open Graph (OG) protocol meta data of a webpage will be prioritized, before seeking through the other HTML components for referencing objects.<br />
==Private Message==<br />
[[Image:6-bit_message.png|center|600px]]<br />
There should be an in-system communication channel for general users, buyers and sellers. Potential buyers can clarify product specifications with sellers, sellers can confirm delivery address with buyers in case of anomalies, and general users can use it for chatting purposes.<br />
<br><br />
<br>It should be able to perform CRUD of messages between 2 users, in a conversational format. Users are notified via email whenever they receive a message. They will also be able to see past messages exchanged, in a single conversation page.<br />
==Image Cropping Tool==<br />
As all images uploaded by users can be of different dimensions, our system will need a tool to automatically resize and crop away unimportant parts to fit the image dimensions on different pages.<br />
<br><br><br />
Hence, the Image Cropping Tool will help us with automatically resizing an image to the most suitable resolution, before cropping away any extended sides and focus on the centre of the image which is usually the most important message. This tool will be applied throughout the entire platform, on both discussion forums and marketplace.<br />
<br />
==Notifications==<br />
[[Image:6-bit_notification.png|center|300px]]<br />
Users should be appropriately notified on any activities concerning them. They will have a new notifications whenever someone replies to their post, whenever a friend is following them in Chapalang!, or when a product purchased is being shipped, et cetera.<br />
<br><br />
<br><br />
Notification entries should link them to appropriate pages for follow-up actions or even simply viewing more details of the notification. Each in-system notification should also be tied to an email notification for a timelier update to users, and users should have the ability to modify their notifications settings for privacy or information flood control.<br />
<br />
==Search function==<br />
[[Image:6-bit_search.png|center|600px]]<br />
There are many content types on Chapalang!, which includes people, messages, products, posts, et cetera. These content types should be searchable for the purpose of conveniently accessing specific content.<br />
==Profile page==<br />
[[Image:6-bit_profilepage.png|center|600px]]<br />
Every user will have a dedicated profile page, which contains their profile picture, basic particulars, activities and friends. This will create a more social environment, where information of a user is shared among friends.<br />
==Management pages==<br />
[[Image:6-bit_management.png|center|250px]]<br />
There should be a set of management pages, for the management of sales, orders or products. These pages will be able to perform basic CRUD functions, as well as other functions allowing appropriate manipulation of an activity. For example, Manage Sales will allow sellers to view transactional details as well as updating shipping details when an order is fulfilled. On the other hand, Manage Orders will allow buyers to review their purchases and be informed whether their orders are fulfilled. Correspondingly, Manage Products will allow the sellers administer all aspects of a product, from its description, images, pricing, to its options and shipping methods.<br />
<br />
==Settings pages==<br />
[[Image:6-bit_settings.png|center|600px]]<br />
There will be separate pages for Accounts Settings, Privacy Settings and Notifications Settings. Firstly, Account Settings will allow a user to change their basic information imported from Facebook. Secondly, Privacy Settings will provide the option to show or hide certain sensitive information that a user may choose not to show in the public. Lastly, Notifications Settings will help the users manage the quantity and quality of notifications that they receive as they might choose not to be informed of certain activities to prevent information overload.<br />
==Personalized dashboard==<br />
[[Image:6-bit_personalizeddb.png|center|600px]]<br />
A dashboard is the first page the user will see upon login, and will contain a mash up of content from various components on the portal. The content published to the dashboard is personalized through stratification supported by data-driven analytics.<br />
<br><br />
<br><br />
The dashboard will contain the following data:<br />
* Relevant topics from subscribed forums<br />
* Featured discussions<br />
* Product recommendations generated by analytics<br />
* Recent purchases made by friends<br />
* Featured mass orders recommendations generated by analytics<br />
* Seasonal or holidays promotional products recommendations generated by analytics<br />
* New arrival products recommendations generated by analytics<br />
* Reminders on upcoming special dates, friends’ birthdays, and activity invites<br />
The dashboard has a 2-step approach in deriving personalized content. Firstly, a set of meta data describing a user is generated. Secondly, another set of meta data describing a product is also generated. Subsequently, both set of meta data are matched to produce a list of recommendations.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Sponsor</font></div>=<br />
[[Image:Dotcom_Logo.jpg|left]]<br />
<b>Chapalang</b> is a self-proposed project for DotCom Enterprise. Upon successful development, DotCom will commercialize the project for live operations. Mr. Eric Chew, Special Projects Manager will be the primary contact from DotCom. Throughout the development and implementation stages, our team will deploy the project on the live systems provided by DotCom.<br />
<div style="margin-bottom:30px;><br />
<br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Academic Milestones</font></div>=<br />
==Acceptance==<br />
[[Media:Chapalang_Acceptance_Slides.pdf|<font color="#CD004E"> Acceptance Presentation Slides]]<br />
==Midterm==<br />
[[IS480_Team_wiki:_2012T1_6-bit_Midterm_Wikipage | <font color="#CD004E"><b>Mid Term Wiki</b></font>]]<br />
<br><br />
[[Media:Chapalang_Midterm_Slides.pdf|<font color="#CD004E"> Midterm Presentation Slides]]<br />
==Final==<br />
[[Media:Chapalang_Final_Slides.pdf|<font color="#CD004E"> *Coming Soon!*]]<br />
[[https://dl.dropbox.com/u/56071797/Final%20Presentation.pptx |<font color="#CD004E"><b>Final Presentation Slides</b></font>]]</div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Project_Management&diff=114538IS480 Team wiki: 2012T1 6-bit Project Management2012-12-04T15:07:52Z<p>Huiling.ong.2010: /* Log */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule</font></div>=<br />
==Planned Schedule==<br />
[[Image:6-bit_ScheduleDiagramOverview.png|750px|center]]<br />
<br />
==Meeting Minutes==<br />
===Team Meeting Minutes===<br />
{|<br />
|[[https://docs.google.com/document/d/1nHl51M2qzY4gynJ8tVR6wKqV_lWtJtncl3nbESSnQvU/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]]<br />
|[[https://docs.google.com/document/d/129JDPU8l7PbX-JjferJ-J83JXSIAo5-cXM4_Odw3o5c/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]]<br />
|[[https://docs.google.com/document/d/1BPn6a-XMMAN18TbdlDER27f8Eleb8sUJhcas1bgDOQI/edit |<font color="#CD004E"><b>Meeting Minute 21</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LtSANlI6pDyV_PpGDAVg85PjFVKmDmWWnYC5lXAHh68/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qx6hX462uQDEfwiB3r3ee71eTKaPXSArCZS7y1TOWA4/edit |<font color="#CD004E"><b>Meeting Minute 12</b></font>]]<br />
|[[https://docs.google.com/document/d/1IdjkCbomLgszePgImX2XsTeUHX54e54xRTIjjFoZM6g/edit |<font color="#CD004E"><b>Meeting Minute 22</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/11lQzKaddghH7FHACcTnPQDJnE6ZaScT8Q8nU2YvH8gU/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]]<br />
|[[https://docs.google.com/document/d/1HPdXr28aTDK-RmijqPYTLG1iCUv-JbpkIJ8zzgzTplg/edit |<font color="#CD004E"><b>Meeting Minute 13</b></font>]]<br />
|[[https://docs.google.com/document/d/1gMoTceQakeT42-FO0duVxRajea2hJAUVw8Eu1AfqtfY/edit |<font color="#CD004E"><b>Meeting Minute 23</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1gZuhKW-QMbhUR_oh6Ty8EE17JTYkTFkWCfG6UHrU7-c/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]]<br />
|[[https://docs.google.com/document/d/1ii-ZenbOTZR9drEQCFJ4hX8raXvpgufELaZY80M2GYI/edit |<font color="#CD004E"><b>Meeting Minute 14</b></font>]]<br />
|[[https://docs.google.com/document/d/12vYfm8jo9c2eZ3VwnL2z6vn6l__D6heDhCHdEWVPg4I/edit |<font color="#CD004E"><b>Meeting Minute 24</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1H-8fODLc79U6-IXScSfemjRLOyjvzC6_k0aig6BDcBY/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]]<br />
|[[https://docs.google.com/document/d/1I3qlvujdLVmY_L22VMsKrtISIFI5CnxmtZnMNdJdxfc/edit |<font color="#CD004E"><b>Meeting Minute 15</b></font>]]<br />
|[[https://docs.google.com/document/d/1jPIW-xe7p6kjzGF_YMmk0K2mPzWil1zUfBQOwGc8wRk/edit |<font color="#CD004E"><b>Meeting Minute 25</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Qx4jdRZoE8hXv3u1R4dWke5b-kyMxIc7ASzPIh4ShRQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]]<br />
|[[https://docs.google.com/document/d/1Pcd6ZADI7ZEuXzq3exrss4nJQhotxAq7-ENfy_OVs6o/edit |<font color="#CD004E"><b>Meeting Minute 16</b></font>]]<br />
|[[https://docs.google.com/document/d/1NDCoF37ckdhbys57BLEXShcAcraxzOKpoNbFvpWWUQM/edit |<font color="#CD004E"><b>Meeting Minute 26</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1uSkv_cux0PqnRTKS-w72wQLgL1ZKaCpXhzDm5uamfMU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]]<br />
|[[https://docs.google.com/document/d/12jW-ycBkfivYL2pg7nrVvb9SF7_XmiglVGGnWAjp6uQ/edit |<font color="#CD004E"><b>Meeting Minute 17</b></font>]]<br />
|[[https://docs.google.com/document/d/1Amo6YgCkVA3YD-iqyIxhyG8embuClo50KXsznVgoWQE/edit |<font color="#CD004E"><b>Meeting Minute 27</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1pTivyZ9D3jSU1Kf5VoW4-Xl_C9Abg-fL_6SI6GP_hz0/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qbhow5u8GsE42hr9b8o1S2HNeJfG5PTX24W70ZHyCfI/edit |<font color="#CD004E"><b>Meeting Minute 18</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LTLnY5JN2EfiU9drp3d7zGmoCxsSYr1nL4UMvwfXDdU/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]]<br />
|[[https://docs.google.com/document/d/1fbnoWNTimFyUC01lgeblvVCLTySS8Ik2JU_wdZ656RU/edit |<font color="#CD004E"><b>Meeting Minute 19</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Nlo5hnsYbfh4dFSnfsV6Wyv5nxJsmDWF8ZMFKFA9Pac/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]]<br />
|[[https://docs.google.com/document/d/1o1zVXcdHaXCLNzS9rHq528rLEmXMFl3df3ffTFLMtho/edit |<font color="#CD004E"><b>Meeting Minute 20</b></font>]]<br />
|}<br />
<br />
===Supervisor Meeting Minutes===<br />
[https://docs.google.com/document/d/1iuSvaC9Wu-v7dToRp41IwmpdpQ0KtSTJIgpabmiolXQ/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1rXJuYE684ZpYbRyHknn4pmLpJZ9Y5o01QaJT34TD0gY/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1Gy7TOJr9aeyd8pcU_loabY1l3NByVm3nVKqOQnnJRbM/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1DGrSXaCTOtRL_iSOaOI_mHC2DOS7z4Vi6clzomkGkcI/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1VLEizDPdae_enbEtoHo9IGPM4-k9JXe7RFJ1hhiDTBA/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/13MyE--Ymz-dNiQPvgCjGutL23JZwotnoIPlYw7QqmXQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1UUDCW8YMttW2rwAxLJhSfqccBdedYoofVskc9qerIxU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/17QEpHsvitqzO9BO9MkB42umN3_9k6Useli4N2fYoCNU/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1masrY10EdoXrAdwmTnW-POF0RVEYGeHbOorf-0EEC-0/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1u2jcuwSkGqk4lGcGdF4UriFgzT9dNgNAb1ekERDvitQ/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1eHVDrzwLxkGhrElcgPUOWhcQBwLdGdXcmCVvT_u-Va8/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]<br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Testing</font></div>=<br />
==Test Cases==<br />
[https://dl.dropbox.com/u/56071797/Test%20Cases.docx |<font color="#CD004E"><b>Test Cases</b></font>]<br />
<br />
==Test Plans==<br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2001_17_10_2012.docx <font color="#CD004E"><b>Test Plan 1 ''on 17 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2002_28_09_2012.docx <font color="#CD004E"><b>Test Plan 2 ''on 28 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2003_19_10_2012.docx <font color="#CD004E"><b>Test Plan 3 ''on 19 October 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2004_01_11_2012.docx <font color="#CD004E"><b>Test Plan 4 ''on 4 November 2012''</b></font>]<br />
<br />
==User Testing==<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #728FCE; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing|<font color="#CD004E"><b>User Testing 1</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing|<font color="#CD004E"><b>User Testing 2</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing|<font color="#CD004E"><b>User Testing 3</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing|<font color="#CD004E"><b>User Testing 4</b></font>]]<br />
<br />
|}<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Milestones</font></div>=<br />
<br />
[[Image:6-bit_schedule.png|600px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule Metric</font></div>=<br />
Every iteration, schedule metric values are calculated to understand the project progress. They are broadly categorized into 5 different groups, where different action plans will apply. The acceptable range of value is within 90% to 110%, offering some buffer for natural inaccuracies between forecasting and execution.<br />
<br><br><br />
Total Schedule Metric Value = Planned no. of days taken (P) / Actual no. of Days Assigned (A) x 100%<br />
<br><br><br />
[[Image:6-bit_schedulemetric.png|center|600px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Bug Metric</font></div>=<br />
==Log==<br />
[[Image:6-bit_BugLog.png|1000px|center]]<br />
<div style="text-align: right;"><br />
Bug Log: [https://docs.google.com/spreadsheet/ccc?key=0Aqd6IiSLbMwQdEI5TldNSEhpcVRjb1puYzU3ZHJOckE |<font color="#CD004E"><b>Click Here</b></font>]<br />
</div><br />
<br><br />
Bug logging for Chapalang! takes the direction of being practical and easily monitored from both macro and micro perspectives. Whenever a bug is found, a new row is entered with the following data:<br />
* Index number<br />
* Bug description<br />
* Found by<br />
* Found date<br />
* Expected solve-by date<br />
* Bug severity<br />
* Status<br />
* Owner of the function<br />
* Fixed date<br />
* Closed by (Tester)<br />
* Close date<br />
* Additional comments<br />
<br />
==Metric==<br />
Bugs are classified into 3 different categories of complexity, easy, moderate and hard. Each category is assigned points of 1, 5 and 10 respectively, lower is better.<br />
<br><br><br />
Total Points for Each Iteration = Σ Points of the Bugs in each iteration<br />
<br><br />
[[Image:6-bit_BugMetricFormula.png|500px|center]]<br />
<br><br />
After assigning each bug with points associated by its complexity, we will track the total bug scores at the end of each week before deciding if there should be any actions to be taken. The following is an action plan for our bug metric:<br />
<br><br />
[[Image:6-bit_BugMetricFormula2.png|500px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Risk & Mitigation</font></div>=<br />
<br><br />
[[Image:6-bit_RiskDiagram.png|600px]]<br />
<br><br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Project_Management&diff=114537IS480 Team wiki: 2012T1 6-bit Project Management2012-12-04T15:07:40Z<p>Huiling.ong.2010: /* Log */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule</font></div>=<br />
==Planned Schedule==<br />
[[Image:6-bit_ScheduleDiagramOverview.png|750px|center]]<br />
<br />
==Meeting Minutes==<br />
===Team Meeting Minutes===<br />
{|<br />
|[[https://docs.google.com/document/d/1nHl51M2qzY4gynJ8tVR6wKqV_lWtJtncl3nbESSnQvU/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]]<br />
|[[https://docs.google.com/document/d/129JDPU8l7PbX-JjferJ-J83JXSIAo5-cXM4_Odw3o5c/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]]<br />
|[[https://docs.google.com/document/d/1BPn6a-XMMAN18TbdlDER27f8Eleb8sUJhcas1bgDOQI/edit |<font color="#CD004E"><b>Meeting Minute 21</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LtSANlI6pDyV_PpGDAVg85PjFVKmDmWWnYC5lXAHh68/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qx6hX462uQDEfwiB3r3ee71eTKaPXSArCZS7y1TOWA4/edit |<font color="#CD004E"><b>Meeting Minute 12</b></font>]]<br />
|[[https://docs.google.com/document/d/1IdjkCbomLgszePgImX2XsTeUHX54e54xRTIjjFoZM6g/edit |<font color="#CD004E"><b>Meeting Minute 22</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/11lQzKaddghH7FHACcTnPQDJnE6ZaScT8Q8nU2YvH8gU/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]]<br />
|[[https://docs.google.com/document/d/1HPdXr28aTDK-RmijqPYTLG1iCUv-JbpkIJ8zzgzTplg/edit |<font color="#CD004E"><b>Meeting Minute 13</b></font>]]<br />
|[[https://docs.google.com/document/d/1gMoTceQakeT42-FO0duVxRajea2hJAUVw8Eu1AfqtfY/edit |<font color="#CD004E"><b>Meeting Minute 23</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1gZuhKW-QMbhUR_oh6Ty8EE17JTYkTFkWCfG6UHrU7-c/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]]<br />
|[[https://docs.google.com/document/d/1ii-ZenbOTZR9drEQCFJ4hX8raXvpgufELaZY80M2GYI/edit |<font color="#CD004E"><b>Meeting Minute 14</b></font>]]<br />
|[[https://docs.google.com/document/d/12vYfm8jo9c2eZ3VwnL2z6vn6l__D6heDhCHdEWVPg4I/edit |<font color="#CD004E"><b>Meeting Minute 24</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1H-8fODLc79U6-IXScSfemjRLOyjvzC6_k0aig6BDcBY/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]]<br />
|[[https://docs.google.com/document/d/1I3qlvujdLVmY_L22VMsKrtISIFI5CnxmtZnMNdJdxfc/edit |<font color="#CD004E"><b>Meeting Minute 15</b></font>]]<br />
|[[https://docs.google.com/document/d/1jPIW-xe7p6kjzGF_YMmk0K2mPzWil1zUfBQOwGc8wRk/edit |<font color="#CD004E"><b>Meeting Minute 25</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Qx4jdRZoE8hXv3u1R4dWke5b-kyMxIc7ASzPIh4ShRQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]]<br />
|[[https://docs.google.com/document/d/1Pcd6ZADI7ZEuXzq3exrss4nJQhotxAq7-ENfy_OVs6o/edit |<font color="#CD004E"><b>Meeting Minute 16</b></font>]]<br />
|[[https://docs.google.com/document/d/1NDCoF37ckdhbys57BLEXShcAcraxzOKpoNbFvpWWUQM/edit |<font color="#CD004E"><b>Meeting Minute 26</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1uSkv_cux0PqnRTKS-w72wQLgL1ZKaCpXhzDm5uamfMU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]]<br />
|[[https://docs.google.com/document/d/12jW-ycBkfivYL2pg7nrVvb9SF7_XmiglVGGnWAjp6uQ/edit |<font color="#CD004E"><b>Meeting Minute 17</b></font>]]<br />
|[[https://docs.google.com/document/d/1Amo6YgCkVA3YD-iqyIxhyG8embuClo50KXsznVgoWQE/edit |<font color="#CD004E"><b>Meeting Minute 27</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1pTivyZ9D3jSU1Kf5VoW4-Xl_C9Abg-fL_6SI6GP_hz0/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qbhow5u8GsE42hr9b8o1S2HNeJfG5PTX24W70ZHyCfI/edit |<font color="#CD004E"><b>Meeting Minute 18</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LTLnY5JN2EfiU9drp3d7zGmoCxsSYr1nL4UMvwfXDdU/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]]<br />
|[[https://docs.google.com/document/d/1fbnoWNTimFyUC01lgeblvVCLTySS8Ik2JU_wdZ656RU/edit |<font color="#CD004E"><b>Meeting Minute 19</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Nlo5hnsYbfh4dFSnfsV6Wyv5nxJsmDWF8ZMFKFA9Pac/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]]<br />
|[[https://docs.google.com/document/d/1o1zVXcdHaXCLNzS9rHq528rLEmXMFl3df3ffTFLMtho/edit |<font color="#CD004E"><b>Meeting Minute 20</b></font>]]<br />
|}<br />
<br />
===Supervisor Meeting Minutes===<br />
[https://docs.google.com/document/d/1iuSvaC9Wu-v7dToRp41IwmpdpQ0KtSTJIgpabmiolXQ/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1rXJuYE684ZpYbRyHknn4pmLpJZ9Y5o01QaJT34TD0gY/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1Gy7TOJr9aeyd8pcU_loabY1l3NByVm3nVKqOQnnJRbM/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1DGrSXaCTOtRL_iSOaOI_mHC2DOS7z4Vi6clzomkGkcI/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1VLEizDPdae_enbEtoHo9IGPM4-k9JXe7RFJ1hhiDTBA/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/13MyE--Ymz-dNiQPvgCjGutL23JZwotnoIPlYw7QqmXQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1UUDCW8YMttW2rwAxLJhSfqccBdedYoofVskc9qerIxU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/17QEpHsvitqzO9BO9MkB42umN3_9k6Useli4N2fYoCNU/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1masrY10EdoXrAdwmTnW-POF0RVEYGeHbOorf-0EEC-0/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1u2jcuwSkGqk4lGcGdF4UriFgzT9dNgNAb1ekERDvitQ/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1eHVDrzwLxkGhrElcgPUOWhcQBwLdGdXcmCVvT_u-Va8/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]<br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Testing</font></div>=<br />
==Test Cases==<br />
[https://dl.dropbox.com/u/56071797/Test%20Cases.docx |<font color="#CD004E"><b>Test Cases</b></font>]<br />
<br />
==Test Plans==<br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2001_17_10_2012.docx <font color="#CD004E"><b>Test Plan 1 ''on 17 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2002_28_09_2012.docx <font color="#CD004E"><b>Test Plan 2 ''on 28 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2003_19_10_2012.docx <font color="#CD004E"><b>Test Plan 3 ''on 19 October 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2004_01_11_2012.docx <font color="#CD004E"><b>Test Plan 4 ''on 4 November 2012''</b></font>]<br />
<br />
==User Testing==<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #728FCE; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing|<font color="#CD004E"><b>User Testing 1</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing|<font color="#CD004E"><b>User Testing 2</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing|<font color="#CD004E"><b>User Testing 3</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing|<font color="#CD004E"><b>User Testing 4</b></font>]]<br />
<br />
|}<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Milestones</font></div>=<br />
<br />
[[Image:6-bit_schedule.png|600px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule Metric</font></div>=<br />
Every iteration, schedule metric values are calculated to understand the project progress. They are broadly categorized into 5 different groups, where different action plans will apply. The acceptable range of value is within 90% to 110%, offering some buffer for natural inaccuracies between forecasting and execution.<br />
<br><br><br />
Total Schedule Metric Value = Planned no. of days taken (P) / Actual no. of Days Assigned (A) x 100%<br />
<br><br><br />
[[Image:6-bit_schedulemetric.png|center|600px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Bug Metric</font></div>=<br />
==Log==<br />
[[Image:6-bit_BugLog.png|600px]]<br />
<div style="text-align: right;"><br />
Bug Log: [https://docs.google.com/spreadsheet/ccc?key=0Aqd6IiSLbMwQdEI5TldNSEhpcVRjb1puYzU3ZHJOckE |<font color="#CD004E"><b>Click Here</b></font>]<br />
</div><br />
<br><br />
Bug logging for Chapalang! takes the direction of being practical and easily monitored from both macro and micro perspectives. Whenever a bug is found, a new row is entered with the following data:<br />
* Index number<br />
* Bug description<br />
* Found by<br />
* Found date<br />
* Expected solve-by date<br />
* Bug severity<br />
* Status<br />
* Owner of the function<br />
* Fixed date<br />
* Closed by (Tester)<br />
* Close date<br />
* Additional comments<br />
<br />
==Metric==<br />
Bugs are classified into 3 different categories of complexity, easy, moderate and hard. Each category is assigned points of 1, 5 and 10 respectively, lower is better.<br />
<br><br><br />
Total Points for Each Iteration = Σ Points of the Bugs in each iteration<br />
<br><br />
[[Image:6-bit_BugMetricFormula.png|500px|center]]<br />
<br><br />
After assigning each bug with points associated by its complexity, we will track the total bug scores at the end of each week before deciding if there should be any actions to be taken. The following is an action plan for our bug metric:<br />
<br><br />
[[Image:6-bit_BugMetricFormula2.png|500px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Risk & Mitigation</font></div>=<br />
<br><br />
[[Image:6-bit_RiskDiagram.png|600px]]<br />
<br><br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=File:Chapalangprocesses.png&diff=114398File:Chapalangprocesses.png2012-12-04T06:45:43Z<p>Huiling.ong.2010: uploaded a new version of "Image:Chapalangprocesses.png"</p>
<hr />
<div></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=File:Chapalangprocesses.png&diff=114397File:Chapalangprocesses.png2012-12-04T06:45:30Z<p>Huiling.ong.2010: uploaded a new version of "Image:Chapalangprocesses.png"</p>
<hr />
<div></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=File:Chapalangprocesses.png&diff=114396File:Chapalangprocesses.png2012-12-04T06:45:08Z<p>Huiling.ong.2010: uploaded a new version of "Image:Chapalangprocesses.png"</p>
<hr />
<div></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4&diff=114376IS480 Team wiki: 2012T1 6-bit Project Management UT42012-12-04T03:45:24Z<p>Huiling.ong.2010: /* Team Meeting Minutes */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule</font></div>=<br />
==Planned Schedule==<br />
[[Image:6-bit_ScheduleDiagramOverview.png|left|750px|link=""]]<br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
==Meeting Minutes==<br />
===Team Meeting Minutes===<br />
{|<br />
|[[https://docs.google.com/document/d/1nHl51M2qzY4gynJ8tVR6wKqV_lWtJtncl3nbESSnQvU/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]]<br />
|[[https://docs.google.com/document/d/129JDPU8l7PbX-JjferJ-J83JXSIAo5-cXM4_Odw3o5c/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]]<br />
|[[https://docs.google.com/document/d/1BPn6a-XMMAN18TbdlDER27f8Eleb8sUJhcas1bgDOQI/edit |<font color="#CD004E"><b>Meeting Minute 21</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LtSANlI6pDyV_PpGDAVg85PjFVKmDmWWnYC5lXAHh68/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qx6hX462uQDEfwiB3r3ee71eTKaPXSArCZS7y1TOWA4/edit |<font color="#CD004E"><b>Meeting Minute 12</b></font>]]<br />
|[[https://docs.google.com/document/d/1IdjkCbomLgszePgImX2XsTeUHX54e54xRTIjjFoZM6g/edit |<font color="#CD004E"><b>Meeting Minute 22</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/11lQzKaddghH7FHACcTnPQDJnE6ZaScT8Q8nU2YvH8gU/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]]<br />
|[[https://docs.google.com/document/d/1HPdXr28aTDK-RmijqPYTLG1iCUv-JbpkIJ8zzgzTplg/edit |<font color="#CD004E"><b>Meeting Minute 13</b></font>]]<br />
|[[https://docs.google.com/document/d/1gMoTceQakeT42-FO0duVxRajea2hJAUVw8Eu1AfqtfY/edit |<font color="#CD004E"><b>Meeting Minute 23</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1gZuhKW-QMbhUR_oh6Ty8EE17JTYkTFkWCfG6UHrU7-c/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]]<br />
|[[https://docs.google.com/document/d/1ii-ZenbOTZR9drEQCFJ4hX8raXvpgufELaZY80M2GYI/edit |<font color="#CD004E"><b>Meeting Minute 14</b></font>]]<br />
|[[https://docs.google.com/document/d/12vYfm8jo9c2eZ3VwnL2z6vn6l__D6heDhCHdEWVPg4I/edit |<font color="#CD004E"><b>Meeting Minute 24</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1H-8fODLc79U6-IXScSfemjRLOyjvzC6_k0aig6BDcBY/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]]<br />
|[[https://docs.google.com/document/d/1I3qlvujdLVmY_L22VMsKrtISIFI5CnxmtZnMNdJdxfc/edit |<font color="#CD004E"><b>Meeting Minute 15</b></font>]]<br />
|[[https://docs.google.com/document/d/1jPIW-xe7p6kjzGF_YMmk0K2mPzWil1zUfBQOwGc8wRk/edit |<font color="#CD004E"><b>Meeting Minute 25</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Qx4jdRZoE8hXv3u1R4dWke5b-kyMxIc7ASzPIh4ShRQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]]<br />
|[[https://docs.google.com/document/d/1Pcd6ZADI7ZEuXzq3exrss4nJQhotxAq7-ENfy_OVs6o/edit |<font color="#CD004E"><b>Meeting Minute 16</b></font>]]<br />
|[[https://docs.google.com/document/d/1NDCoF37ckdhbys57BLEXShcAcraxzOKpoNbFvpWWUQM/edit |<font color="#CD004E"><b>Meeting Minute 26</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1uSkv_cux0PqnRTKS-w72wQLgL1ZKaCpXhzDm5uamfMU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]]<br />
|[[https://docs.google.com/document/d/12jW-ycBkfivYL2pg7nrVvb9SF7_XmiglVGGnWAjp6uQ/edit |<font color="#CD004E"><b>Meeting Minute 17</b></font>]]<br />
|[[https://docs.google.com/document/d/1Amo6YgCkVA3YD-iqyIxhyG8embuClo50KXsznVgoWQE/edit |<font color="#CD004E"><b>Meeting Minute 27</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1pTivyZ9D3jSU1Kf5VoW4-Xl_C9Abg-fL_6SI6GP_hz0/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qbhow5u8GsE42hr9b8o1S2HNeJfG5PTX24W70ZHyCfI/edit |<font color="#CD004E"><b>Meeting Minute 18</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LTLnY5JN2EfiU9drp3d7zGmoCxsSYr1nL4UMvwfXDdU/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]]<br />
|[[https://docs.google.com/document/d/1fbnoWNTimFyUC01lgeblvVCLTySS8Ik2JU_wdZ656RU/edit |<font color="#CD004E"><b>Meeting Minute 19</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Nlo5hnsYbfh4dFSnfsV6Wyv5nxJsmDWF8ZMFKFA9Pac/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]]<br />
|[[https://docs.google.com/document/d/1o1zVXcdHaXCLNzS9rHq528rLEmXMFl3df3ffTFLMtho/edit |<font color="#CD004E"><b>Meeting Minute 20</b></font>]]<br />
|}<br />
<br />
===Supervisor Meeting Minutes===<br />
[https://docs.google.com/document/d/1iuSvaC9Wu-v7dToRp41IwmpdpQ0KtSTJIgpabmiolXQ/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1rXJuYE684ZpYbRyHknn4pmLpJZ9Y5o01QaJT34TD0gY/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1Gy7TOJr9aeyd8pcU_loabY1l3NByVm3nVKqOQnnJRbM/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1DGrSXaCTOtRL_iSOaOI_mHC2DOS7z4Vi6clzomkGkcI/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1VLEizDPdae_enbEtoHo9IGPM4-k9JXe7RFJ1hhiDTBA/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/13MyE--Ymz-dNiQPvgCjGutL23JZwotnoIPlYw7QqmXQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1UUDCW8YMttW2rwAxLJhSfqccBdedYoofVskc9qerIxU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/17QEpHsvitqzO9BO9MkB42umN3_9k6Useli4N2fYoCNU/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1masrY10EdoXrAdwmTnW-POF0RVEYGeHbOorf-0EEC-0/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1u2jcuwSkGqk4lGcGdF4UriFgzT9dNgNAb1ekERDvitQ/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1eHVDrzwLxkGhrElcgPUOWhcQBwLdGdXcmCVvT_u-Va8/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]<br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Testing</font></div>=<br />
==Test Cases==<br />
[https://dl.dropbox.com/u/56071797/Test%20Cases.docx |<font color="#CD004E"><b>Test Cases</b></font>]<br />
<br />
==Test Plans==<br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2001_17_10_2012.docx <font color="#CD004E"><b>Test Plan 1 ''on 17 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2002_28_09_2012.docx <font color="#CD004E"><b>Test Plan 2 ''on 28 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2003_19_10_2012.docx <font color="#CD004E"><b>Test Plan 3 ''on 19 October 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2004_01_11_2012.docx <font color="#CD004E"><b>Test Plan 4 ''on 4 November 2012''</b></font>]<br />
<br />
==User Testing==<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #728FCE; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing|<font color="#CD004E"><b>User Testing 1</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing|<font color="#CD004E"><b>User Testing 2</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing|<font color="#CD004E"><b>User Testing 3</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing|<font color="#CD004E"><b>User Testing 4</b></font>]]<br />
<br />
|}<br />
===User Testing 4===<br />
[[Image:6bituser-testing4.png]]<br />
<br />
====Test Description====<br />
The objective of User Test 4 is on scalability, performance and analytics testing of the system. This is a 2-part test session, firstly on scalability and performance which does not require physical testers, and secondly on inter-rater reliability which requires rating judges.<br />
<br><br><br />
The coverage of the scalability and performance test is focused on the bottleneck functions, which are the discussion forums and marketplace. The terms “performance” and “scalability” are commonly used interchangeably, but the two are distinct: performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. <br />
<br><br><br />
Additionally, Inter-Rater Reliability Test is performed on the Personalized Dashboard to determine the concordance of the personalized results and actual personality of user stereotypes.<br />
<br />
====Testers Background====<br />
=====Scalability & Performance Testing=====<br />
As the test does not require physical testers, the following appends the test environment.<br><br />
[[Image:6-bit_ut4spec.png|400px]]<br />
<br />
=====Inter-Rater Reliability Test=====<br />
Testers will assume the role of raters or judges for our Inter-Rater Reliability Test, represented by a total of 20 people with a 50-50 male is to female ratio. Testers are stratified from a diverse background, intended to represent personality stereotypes designed.<br />
<br><br><br />
Personality stereotypes include characteristics such as gender, age group, education, personality traits, online activity, mobility and interested topics.<br />
<br />
====Test Groups====<br />
There is no test grouping employed in this test.<br />
<br />
====Test Procedures====<br />
=====Scalability & Performance Testing=====<br />
The first part of the test is on scalability and performance testing. Chapalang Benchmark is configured to measure the time taken for each controller method before it starts and as soon as it ends. The results will be used to study the performance of the system and application at different scales of operations. <br />
<br><br><br />
Additionally, custom application is used to perform a series of activities on a forum and marketplace, simulating an arbitrary number of concurrent users on the system, or the load. <br />
<br><br />
<br><br />
Subsequently, we will study the benchmark timing data to understand the performance differences under different load.<br />
=====Inter-Rater Reliability Test=====<br />
An Inter-Rater Reliability (IRR) is the degree of agreement among raters. It gives a score of how much homogeneity or consensus there is in the ratings given by judges.<br />
<br><br><br />
The first rater is the system itself, which will generate a list of 10 products and 10 discussion topics recommendations in descending order of relevance to a target user. Every recommendation is tied to a specific and distinct order number.<br />
<br><br><br />
The second rater is a human tester, who will be provided with the same list of 10 products and 10 discussion topics generated by the system in relevance to him or herself. To mitigate the effects of Experimenter’s Bias, the order of each item is unordered and randomized without any intended logic. The second rater is expected to reorder the items according to his or her preferences in descending order.<br />
<br><br><br />
Subsequently, we will make use of Spearman’s Rank Correlation Coefficient to understand the reliability of our personalized dashboard which features product and topic recommendations.<br />
<br />
====Test Instruction====<br />
=====Inter-Rater Reliability Test=====<br />
This is a sample output of the first rater, for a product recommendation test.<br />
<br><br />
[[Image:6-bit_ut4a.png|750px]]<br />
<br><br />
This is a sample input sheet for the second rater, on product recommendation test.<br />
<br><br />
[[Image:6-bit_ut4b.png|750px]]<br />
<br><br />
In a descending order, 1 represents the most relevant item while 10 represents the least relevant item.<br />
<br />
====Test Results====<br />
=====Scalability & Performance Test=====<br />
The terms “performance” and “scalability” are commonly used interchangeably, but the two are distinct: performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. <br />
*(a) Identification of activities<br />
*(b) Identification of bottleneck<br />
*(c) Measurement of result of single user<br />
*(d) Maximum number of concurrent user, while maintaining single user performance<br />
*(e) Results of 1, 50, 100, 200, 400 users<br />
<br />
=====Inter-Rater Reliability Test=====<br />
In order to evaluate the test results, we rely on the statistical model called Spearman’s Rank Correlation Coefficient (SRCC). The model is appended below:<br />
<br><br />
[[Image: 6bituser-testing4formula.png]]<br />
<br><br />
In short, the SRCC model takes into account the rank rating from 2 different raters, represented by xi and yi respectively. In conventional Correlation of determination model, it takes in absolute data instead to find out statistical and data-driven correlation between 2 inputs. <br />
<br><br />
<br><br />
However, we are interested in the consensus between human judgment on the data, therefore SRCC is a suitable model of analysis. <br />
The SRCC model assumes that the rating scale is ordinal, or basically serial scale of rating. This assumption is aligned with our 1 – 10 rating score which is incremental and serial. Additionally, the SRCC model considers only relative position of the ratings. For example, (1, 2, 1, 3) is considered perfectly correlated with (2, 3, 2, 4). This is acceptable in our test because each rating in our test is distinct and exhaustive, where no repeats or unused score is allowed.<br />
<br> <br><br />
The following is a sample of data tabulation in visual form.<br />
<br><br />
[[Image: 6bituser-testing4z.png]]<br />
<br><br />
With [[Image: 6bituser-testing4di2.png]] found, we can add them to find [[Image: 6bituser-testing4sumdi2.png]] 28. The value of n is 10. So these values can now be substituted back into the equation, we evaluate that p = 0.83.<br />
<br><br />
Based on the nature of correlation coefficient value p, it has a range between -1 to 1. Here are some of the characteristics of the p value.<br />
<br><br />
* A negative number suggests negative relationship, <br />
* A positive number suggests positive relationship, <br />
* A size of a positive or negative number closer to 1 or -1 suggests strength of relationship,<br />
* and A p value of 0 suggests an absolute lack of relationship in the input attributes.<br />
<br />
It should be noted that if there is a strongly negative correlation, it may suggest a reversal in the order of recommendations in our system may eventually become an ideal model.<br />
<br><br />
The accuracy sentimental analysis system is, in principle, how well it agrees with human judgment, despite the fact that the applied accuracy in our test is to ensure an optimal user experience and optimal sales exposure. <br><br />
However, the limitation of the model is that human raters typically agree about 70% of the time and even if a system is 100% accurate by assumption, humans will still disagree about 30% of the time. Hence, for the purpose of our study, it may be suggested that an application with 100% human agreeableness can only be statistically justified to be 70% accurate and more sophisticated methods should be used to endorse the remaining 30% of accuracy. <br><br><br />
After conducting the IRR Test, the results are tabulated and appended as follows.<br />
<br><br />
[[Image: 6bituser-testing4results.png]]<br />
<br><br />
Tester IDs that begins with M denotes male testers, while F denotes Female testers. The categorization of results will help us understand a basic level of stereotyping accuracy by gender. If need it, the results can be further drilled down to represent a more specific personality stereotype.<br />
<br><br><br />
Summarising the test results tabulated above, the average for median p-value for male is 0.8695 and median p-value for female is 0.8675. Based on the median values, there is no significant difference in accuracy for male and females. In addition, it is satisfactorily justified that there is a strong positive correlation between the recommendations of our system and the preferences of the testers, a sample from our potential users, based on their consensus.<br />
<br />
<br />
<br />
<br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Milestones</font></div>=<br />
<br />
[[Image:6-bit_schedule.png|600px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule Metric</font></div>=<br />
Every iteration, schedule metric values are calculated to understand the project progress. They are broadly categorized into 5 different groups, where different action plans will apply. The acceptable range of value is within 90% to 110%, offering some buffer for natural inaccuracies between forecasting and execution.<br />
<br><br><br />
Total Schedule Metric Value = Planned no. of days taken (P) / Actual no. of Days Assigned (A) x 100%<br />
<br><br><br />
[[Image:6-bit_schedulemetric.png|center|600px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Bug Metric</font></div>=<br />
==Log==<br />
[[Image:6-bit_BugMetric.png|550px]]<br />
[[Image:6-bit_BugLog.png|600px]]<br />
<div style="text-align: right;"><br />
Bug Log: [https://docs.google.com/spreadsheet/ccc?key=0Aqd6IiSLbMwQdEI5TldNSEhpcVRjb1puYzU3ZHJOckE |<font color="#CD004E"><b>Click Here</b></font>]<br />
</div><br />
<br><br />
Bug logging for Chapalang! takes the direction of being practical and easily monitored from both macro and micro perspectives. Whenever a bug is found, a new row is entered with the following data:<br />
* Index number<br />
* Bug description<br />
* Found by<br />
* Found date<br />
* Expected solve-by date<br />
* Bug severity<br />
* Status<br />
* Owner of the function<br />
* Fixed date<br />
* Closed by (Tester)<br />
* Close date<br />
* Additional comments<br />
==Metric==<br />
Bugs are classified into 3 different categories of complexity, easy, moderate and hard. Each category is assigned points of 1, 5 and 10 respectively, lower is better.<br />
<br><br><br />
Total Points for Each Iteration = Σ Points of the Bugs in each iteration<br />
<br><br />
[[Image:6-bit_BugMetricFormula.png|500px|center]]<br />
<br><br />
After assigning each bug with points associated by its complexity, we will track the total bug scores at the end of each week before deciding if there should be any actions to be taken. The following is an action plan for our bug metric:<br />
<br><br />
[[Image:6-bit_BugMetricFormula2.png|500px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Risk & Mitigation</font></div>=<br />
<br><br />
[[Image:6-bit_RiskDiagram.png|600px]]<br />
<br><br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3&diff=114375IS480 Team wiki: 2012T1 6-bit Project Management UT32012-12-04T03:45:10Z<p>Huiling.ong.2010: /* Team Meeting Minutes */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule</font></div>=<br />
==Planned Schedule==<br />
[[Image:6-bit_ScheduleDiagramOverview.png|left|750px|link=""]]<br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
==Meeting Minutes==<br />
===Team Meeting Minutes===<br />
{|<br />
|[[https://docs.google.com/document/d/1nHl51M2qzY4gynJ8tVR6wKqV_lWtJtncl3nbESSnQvU/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]]<br />
|[[https://docs.google.com/document/d/129JDPU8l7PbX-JjferJ-J83JXSIAo5-cXM4_Odw3o5c/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]]<br />
|[[https://docs.google.com/document/d/1BPn6a-XMMAN18TbdlDER27f8Eleb8sUJhcas1bgDOQI/edit |<font color="#CD004E"><b>Meeting Minute 21</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LtSANlI6pDyV_PpGDAVg85PjFVKmDmWWnYC5lXAHh68/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qx6hX462uQDEfwiB3r3ee71eTKaPXSArCZS7y1TOWA4/edit |<font color="#CD004E"><b>Meeting Minute 12</b></font>]]<br />
|[[https://docs.google.com/document/d/1IdjkCbomLgszePgImX2XsTeUHX54e54xRTIjjFoZM6g/edit |<font color="#CD004E"><b>Meeting Minute 22</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/11lQzKaddghH7FHACcTnPQDJnE6ZaScT8Q8nU2YvH8gU/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]]<br />
|[[https://docs.google.com/document/d/1HPdXr28aTDK-RmijqPYTLG1iCUv-JbpkIJ8zzgzTplg/edit |<font color="#CD004E"><b>Meeting Minute 13</b></font>]]<br />
|[[https://docs.google.com/document/d/1gMoTceQakeT42-FO0duVxRajea2hJAUVw8Eu1AfqtfY/edit |<font color="#CD004E"><b>Meeting Minute 23</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1gZuhKW-QMbhUR_oh6Ty8EE17JTYkTFkWCfG6UHrU7-c/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]]<br />
|[[https://docs.google.com/document/d/1ii-ZenbOTZR9drEQCFJ4hX8raXvpgufELaZY80M2GYI/edit |<font color="#CD004E"><b>Meeting Minute 14</b></font>]]<br />
|[[https://docs.google.com/document/d/12vYfm8jo9c2eZ3VwnL2z6vn6l__D6heDhCHdEWVPg4I/edit |<font color="#CD004E"><b>Meeting Minute 24</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1H-8fODLc79U6-IXScSfemjRLOyjvzC6_k0aig6BDcBY/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]]<br />
|[[https://docs.google.com/document/d/1I3qlvujdLVmY_L22VMsKrtISIFI5CnxmtZnMNdJdxfc/edit |<font color="#CD004E"><b>Meeting Minute 15</b></font>]]<br />
|[[https://docs.google.com/document/d/1jPIW-xe7p6kjzGF_YMmk0K2mPzWil1zUfBQOwGc8wRk/edit |<font color="#CD004E"><b>Meeting Minute 25</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Qx4jdRZoE8hXv3u1R4dWke5b-kyMxIc7ASzPIh4ShRQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]]<br />
|[[https://docs.google.com/document/d/1Pcd6ZADI7ZEuXzq3exrss4nJQhotxAq7-ENfy_OVs6o/edit |<font color="#CD004E"><b>Meeting Minute 16</b></font>]]<br />
|[[https://docs.google.com/document/d/1NDCoF37ckdhbys57BLEXShcAcraxzOKpoNbFvpWWUQM/edit |<font color="#CD004E"><b>Meeting Minute 26</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1uSkv_cux0PqnRTKS-w72wQLgL1ZKaCpXhzDm5uamfMU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]]<br />
|[[https://docs.google.com/document/d/12jW-ycBkfivYL2pg7nrVvb9SF7_XmiglVGGnWAjp6uQ/edit |<font color="#CD004E"><b>Meeting Minute 17</b></font>]]<br />
|[[https://docs.google.com/document/d/1Amo6YgCkVA3YD-iqyIxhyG8embuClo50KXsznVgoWQE/edit |<font color="#CD004E"><b>Meeting Minute 27</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1pTivyZ9D3jSU1Kf5VoW4-Xl_C9Abg-fL_6SI6GP_hz0/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qbhow5u8GsE42hr9b8o1S2HNeJfG5PTX24W70ZHyCfI/edit |<font color="#CD004E"><b>Meeting Minute 18</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LTLnY5JN2EfiU9drp3d7zGmoCxsSYr1nL4UMvwfXDdU/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]]<br />
|[[https://docs.google.com/document/d/1fbnoWNTimFyUC01lgeblvVCLTySS8Ik2JU_wdZ656RU/edit |<font color="#CD004E"><b>Meeting Minute 19</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Nlo5hnsYbfh4dFSnfsV6Wyv5nxJsmDWF8ZMFKFA9Pac/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]]<br />
|[[https://docs.google.com/document/d/1o1zVXcdHaXCLNzS9rHq528rLEmXMFl3df3ffTFLMtho/edit |<font color="#CD004E"><b>Meeting Minute 20</b></font>]]<br />
|}<br />
<br />
===Supervisor Meeting Minutes===<br />
[https://docs.google.com/document/d/1iuSvaC9Wu-v7dToRp41IwmpdpQ0KtSTJIgpabmiolXQ/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1rXJuYE684ZpYbRyHknn4pmLpJZ9Y5o01QaJT34TD0gY/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1Gy7TOJr9aeyd8pcU_loabY1l3NByVm3nVKqOQnnJRbM/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1DGrSXaCTOtRL_iSOaOI_mHC2DOS7z4Vi6clzomkGkcI/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1VLEizDPdae_enbEtoHo9IGPM4-k9JXe7RFJ1hhiDTBA/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/13MyE--Ymz-dNiQPvgCjGutL23JZwotnoIPlYw7QqmXQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1UUDCW8YMttW2rwAxLJhSfqccBdedYoofVskc9qerIxU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/17QEpHsvitqzO9BO9MkB42umN3_9k6Useli4N2fYoCNU/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1masrY10EdoXrAdwmTnW-POF0RVEYGeHbOorf-0EEC-0/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1u2jcuwSkGqk4lGcGdF4UriFgzT9dNgNAb1ekERDvitQ/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1eHVDrzwLxkGhrElcgPUOWhcQBwLdGdXcmCVvT_u-Va8/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]<br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Testing</font></div>=<br />
==Test Cases==<br />
[https://dl.dropbox.com/u/56071797/Test%20Cases.docx |<font color="#CD004E"><b>Test Cases</b></font>]<br />
<br />
==Test Plans==<br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2001_17_10_2012.docx <font color="#CD004E"><b>Test Plan 1 ''on 17 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2002_28_09_2012.docx <font color="#CD004E"><b>Test Plan 2 ''on 28 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2003_19_10_2012.docx <font color="#CD004E"><b>Test Plan 3 ''on 19 October 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2004_01_11_2012.docx <font color="#CD004E"><b>Test Plan 4 ''on 4 November 2012''</b></font>]<br />
<br />
==User Testing==<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #728FCE; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing|<font color="#CD004E"><b>User Testing 1</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing|<font color="#CD004E"><b>User Testing 2</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing|<font color="#CD004E"><b>User Testing 3</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing|<font color="#CD004E"><b>User Testing 4</b></font>]]<br />
<br />
|}<br />
===User Testing 3===<br />
[[Image:6bituser-testing3.png]]<br />
<br />
====Test Description====<br />
The objective of User Test 3 is on functionality and usability testing of the system. The coverage of the test is focused on the key features of the system which is Private Message, Escrow, Gift Sharing and Mass Order. <br><br><br />
The purpose of the test is to test that the system is functioning according to design, and/or to spot any bugs or anomalies not detected by the team. The test also seeks to collect inputs on possible enhancements or improvements preferred by the sampled group of testers.<br />
<br />
====Testers Background====<br />
There are a total of 30 testers who attended the User Test, of which 70% (21) are male and 30% (9) are female, representing various schools in SMU with SIS students being the majority. It is also observed that most testers are users of Chrome and Firefox web browser.<br />
<br><br />
There is no significant difference between testers’ background in User Test 1, 2 and 3.<br />
<br><br />
[[Image:6bituser-testing3results.png|center]]<br />
<br />
====Test Groups====<br />
There are 2 test groups employed in this test.<br />
<br><br><br />
Group A consists of 15 testers who are guided by an instruction sheet on a series of tasks to be tested. The purpose of this group is to test the system by a set of test case based on the design of the system.<br />
<br><br />
Group B consists of 15 testers who are unguided, and encouraged to explore the full system seeking for any uncommon encounters in their experience. The purpose of this group is to test the system in the role of a random user who may explore use-cases or sequence of activities not intended by design but possible by usage.<br />
<br />
====Test Procedures====<br />
Testers are invited to attend the User Test session and required to bring their own laptops. They are informed on the purpose of the test and given a brief description of the system objective of Chapalang!. <br />
<br><br><br />
Only testers from Group A are provided with the instruction sheet. Thereafter, both groups of testers will fill in details in an open-ended form, should they encounter any bugs or suggestions for improvements.<br />
<br />
====Test Instruction====<br />
[https://dl.dropbox.com/u/56071797/User%20Testing%203%20Instructions.docx Click Here to Download User Testing 3 Instruction]<br />
<br />
====Test Results====<br />
There are also 19 reported bugs, and 32 recommendations for improvements received. The following are the top 10 bugs reported.<br />
<br><br />
[[Image: 6bituser-testing3bug.png|600px]]<br />
<br><br />
Most of the recommendations are repeated from User Test 1 and 2, and hence will not be published.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Milestones</font></div>=<br />
<br />
[[Image:6-bit_schedule.png|600px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule Metric</font></div>=<br />
Every iteration, schedule metric values are calculated to understand the project progress. They are broadly categorized into 5 different groups, where different action plans will apply. The acceptable range of value is within 90% to 110%, offering some buffer for natural inaccuracies between forecasting and execution.<br />
<br><br><br />
Total Schedule Metric Value = Planned no. of days taken (P) / Actual no. of Days Assigned (A) x 100%<br />
<br><br><br />
[[Image:6-bit_schedulemetric.png|center|600px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Bug Metric</font></div>=<br />
==Log==<br />
[[Image:6-bit_BugMetric.png|550px]]<br />
[[Image:6-bit_BugLog.png|600px]]<br />
<div style="text-align: right;"><br />
Bug Log: [https://docs.google.com/spreadsheet/ccc?key=0Aqd6IiSLbMwQdEI5TldNSEhpcVRjb1puYzU3ZHJOckE |<font color="#CD004E"><b>Click Here</b></font>]<br />
</div><br />
<br><br />
Bug logging for Chapalang! takes the direction of being practical and easily monitored from both macro and micro perspectives. Whenever a bug is found, a new row is entered with the following data:<br />
* Index number<br />
* Bug description<br />
* Found by<br />
* Found date<br />
* Expected solve-by date<br />
* Bug severity<br />
* Status<br />
* Owner of the function<br />
* Fixed date<br />
* Closed by (Tester)<br />
* Close date<br />
* Additional comments<br />
==Metric==<br />
Bugs are classified into 3 different categories of complexity, easy, moderate and hard. Each category is assigned points of 1, 5 and 10 respectively, lower is better.<br />
<br><br><br />
Total Points for Each Iteration = Σ Points of the Bugs in each iteration<br />
<br><br />
[[Image:6-bit_BugMetricFormula.png|500px|center]]<br />
<br><br />
After assigning each bug with points associated by its complexity, we will track the total bug scores at the end of each week before deciding if there should be any actions to be taken. The following is an action plan for our bug metric:<br />
<br><br />
[[Image:6-bit_BugMetricFormula2.png|500px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Risk & Mitigation</font></div>=<br />
<br><br />
[[Image:6-bit_RiskDiagram.png|600px]]<br />
<br><br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1&diff=114374IS480 Team wiki: 2012T1 6-bit Project Management UT12012-12-04T03:44:52Z<p>Huiling.ong.2010: /* Team Meeting Minutes */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule</font></div>=<br />
==Planned Schedule==<br />
[[Image:6-bit_ScheduleDiagramOverview.png|left|750px|link=""]]<br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
==Meeting Minutes==<br />
===Team Meeting Minutes===<br />
{|<br />
|[[https://docs.google.com/document/d/1nHl51M2qzY4gynJ8tVR6wKqV_lWtJtncl3nbESSnQvU/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]]<br />
|[[https://docs.google.com/document/d/129JDPU8l7PbX-JjferJ-J83JXSIAo5-cXM4_Odw3o5c/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]]<br />
|[[https://docs.google.com/document/d/1BPn6a-XMMAN18TbdlDER27f8Eleb8sUJhcas1bgDOQI/edit |<font color="#CD004E"><b>Meeting Minute 21</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LtSANlI6pDyV_PpGDAVg85PjFVKmDmWWnYC5lXAHh68/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qx6hX462uQDEfwiB3r3ee71eTKaPXSArCZS7y1TOWA4/edit |<font color="#CD004E"><b>Meeting Minute 12</b></font>]]<br />
|[[https://docs.google.com/document/d/1IdjkCbomLgszePgImX2XsTeUHX54e54xRTIjjFoZM6g/edit |<font color="#CD004E"><b>Meeting Minute 22</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/11lQzKaddghH7FHACcTnPQDJnE6ZaScT8Q8nU2YvH8gU/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]]<br />
|[[https://docs.google.com/document/d/1HPdXr28aTDK-RmijqPYTLG1iCUv-JbpkIJ8zzgzTplg/edit |<font color="#CD004E"><b>Meeting Minute 13</b></font>]]<br />
|[[https://docs.google.com/document/d/1gMoTceQakeT42-FO0duVxRajea2hJAUVw8Eu1AfqtfY/edit |<font color="#CD004E"><b>Meeting Minute 23</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1gZuhKW-QMbhUR_oh6Ty8EE17JTYkTFkWCfG6UHrU7-c/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]]<br />
|[[https://docs.google.com/document/d/1ii-ZenbOTZR9drEQCFJ4hX8raXvpgufELaZY80M2GYI/edit |<font color="#CD004E"><b>Meeting Minute 14</b></font>]]<br />
|[[https://docs.google.com/document/d/12vYfm8jo9c2eZ3VwnL2z6vn6l__D6heDhCHdEWVPg4I/edit |<font color="#CD004E"><b>Meeting Minute 24</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1H-8fODLc79U6-IXScSfemjRLOyjvzC6_k0aig6BDcBY/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]]<br />
|[[https://docs.google.com/document/d/1I3qlvujdLVmY_L22VMsKrtISIFI5CnxmtZnMNdJdxfc/edit |<font color="#CD004E"><b>Meeting Minute 15</b></font>]]<br />
|[[https://docs.google.com/document/d/1jPIW-xe7p6kjzGF_YMmk0K2mPzWil1zUfBQOwGc8wRk/edit |<font color="#CD004E"><b>Meeting Minute 25</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Qx4jdRZoE8hXv3u1R4dWke5b-kyMxIc7ASzPIh4ShRQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]]<br />
|[[https://docs.google.com/document/d/1Pcd6ZADI7ZEuXzq3exrss4nJQhotxAq7-ENfy_OVs6o/edit |<font color="#CD004E"><b>Meeting Minute 16</b></font>]]<br />
|[[https://docs.google.com/document/d/1NDCoF37ckdhbys57BLEXShcAcraxzOKpoNbFvpWWUQM/edit |<font color="#CD004E"><b>Meeting Minute 26</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1uSkv_cux0PqnRTKS-w72wQLgL1ZKaCpXhzDm5uamfMU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]]<br />
|[[https://docs.google.com/document/d/12jW-ycBkfivYL2pg7nrVvb9SF7_XmiglVGGnWAjp6uQ/edit |<font color="#CD004E"><b>Meeting Minute 17</b></font>]]<br />
|[[https://docs.google.com/document/d/1Amo6YgCkVA3YD-iqyIxhyG8embuClo50KXsznVgoWQE/edit |<font color="#CD004E"><b>Meeting Minute 27</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1pTivyZ9D3jSU1Kf5VoW4-Xl_C9Abg-fL_6SI6GP_hz0/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qbhow5u8GsE42hr9b8o1S2HNeJfG5PTX24W70ZHyCfI/edit |<font color="#CD004E"><b>Meeting Minute 18</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LTLnY5JN2EfiU9drp3d7zGmoCxsSYr1nL4UMvwfXDdU/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]]<br />
|[[https://docs.google.com/document/d/1fbnoWNTimFyUC01lgeblvVCLTySS8Ik2JU_wdZ656RU/edit |<font color="#CD004E"><b>Meeting Minute 19</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Nlo5hnsYbfh4dFSnfsV6Wyv5nxJsmDWF8ZMFKFA9Pac/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]]<br />
|[[https://docs.google.com/document/d/1o1zVXcdHaXCLNzS9rHq528rLEmXMFl3df3ffTFLMtho/edit |<font color="#CD004E"><b>Meeting Minute 20</b></font>]]<br />
|}<br />
<br />
===Supervisor Meeting Minutes===<br />
[https://docs.google.com/document/d/1iuSvaC9Wu-v7dToRp41IwmpdpQ0KtSTJIgpabmiolXQ/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1rXJuYE684ZpYbRyHknn4pmLpJZ9Y5o01QaJT34TD0gY/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1Gy7TOJr9aeyd8pcU_loabY1l3NByVm3nVKqOQnnJRbM/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1DGrSXaCTOtRL_iSOaOI_mHC2DOS7z4Vi6clzomkGkcI/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1VLEizDPdae_enbEtoHo9IGPM4-k9JXe7RFJ1hhiDTBA/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/13MyE--Ymz-dNiQPvgCjGutL23JZwotnoIPlYw7QqmXQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1UUDCW8YMttW2rwAxLJhSfqccBdedYoofVskc9qerIxU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/17QEpHsvitqzO9BO9MkB42umN3_9k6Useli4N2fYoCNU/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1masrY10EdoXrAdwmTnW-POF0RVEYGeHbOorf-0EEC-0/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1u2jcuwSkGqk4lGcGdF4UriFgzT9dNgNAb1ekERDvitQ/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1eHVDrzwLxkGhrElcgPUOWhcQBwLdGdXcmCVvT_u-Va8/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]<br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Testing</font></div>=<br />
==Test Cases==<br />
[https://dl.dropbox.com/u/56071797/Test%20Cases.docx |<font color="#CD004E"><b>Test Cases</b></font>]<br />
<br />
==Test Plans==<br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2001_17_10_2012.docx <font color="#CD004E"><b>Test Plan 1 ''on 17 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2002_28_09_2012.docx <font color="#CD004E"><b>Test Plan 2 ''on 28 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2003_19_10_2012.docx <font color="#CD004E"><b>Test Plan 3 ''on 19 October 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2004_01_11_2012.docx <font color="#CD004E"><b>Test Plan 4 ''on 4 November 2012''</b></font>]<br />
<br />
==User Testing==<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #728FCE; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing|<font color="#CD004E"><b>User Testing 1</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing|<font color="#CD004E"><b>User Testing 2</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing|<font color="#CD004E"><b>User Testing 3</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing|<font color="#CD004E"><b>User Testing 4</b></font>]]<br />
<br />
|}<br />
===User Testing 1===<br />
[[Image:6bituser-testing1.png|400px]]<br />
<br />
====Test Description====<br />
The objective of User Test 1 is on functionality and usability testing of the system. The coverage of the test is focused on forum functions.<br />
<br><br><br />
The purpose of the test is to allow neutral testers to endorse that the system is functioning according to design, or spot any bugs or anomalies. Click data which collects data about a user’s number of clicks or time taken to achieve a task is also collected to understand the experience, and for comparison purposes for future tests.<br />
====Testers Background====<br />
There are a total of 20 testers who attended the User Test, of which 60% (12) are male and 40% (8) are female, representing various schools in SMU with SIS students being the majority. There is no stratification in the test users, and testers are selected without any intended bias. It is also observed that most testers are users of Chrome and Firefox web browser.<br />
<br><br />
[[Image:6bituser-testing1results.png|550px|center]]<br />
<br />
====Test Groups====<br />
There is no test grouping employed in this test.<br />
====Test Procedures====<br />
Testers are invited to attend the User Test session and required to bring their own laptops. They are informed on the purpose of the test and given a brief description of the system objective of Chapalang!. <br />
Subsequently, they are provided with an instruction sheet for a guided test experience. Testers will be required to perform a series of system tasks based on a test case that will go through all the system features and use-case. Thereafter, testers will answer Yes/No binary questions, and can fill in details in an open-ended textbox appended after each question, should they encounter any bugs or suggestions for improvements.<br />
While the primary method of testing is on direct user experience and feedback, we have also employed secondary method which collects results indirectly. The number of clicks that each user made, together with the click coordinates or link URL, as well as timestamp of each click is captured for analytical purposes.<br />
====Test Instruction====<br />
[https://dl.dropbox.com/u/56071797/User%20Testing%201%20Instructions.docx Click Here to Download User Testing 1 Instruction]<br />
<br />
====Test Results====<br />
[[Image: 6bituser-testing1resultsfigure.png|250px]]<br />
<br><br />
Based on the abovementioned set of results, it is reasonable to conclude that the system is above satisfactory on functionalities for most testers while there are some rooms for improvements especially on intuitiveness.<br />
<br> <br><br />
There are also 4 reported bugs, and 19 recommendations for improvements received. <br />
<br><br />
[[Image: 6bituser-testing1bug.png|650px]]<br />
<br><br />
<br><br />
The top 10 most frequently mentioned or important recommendations will be published and appended below.<br />
<br><br />
[[Image: 6bituser-testing1recommendation.png]]<br />
<br />
====Click Data Analysis====<br />
Additionally, click data of each test session has also been collected and analysed. <br />
<br><br />
[[Image: 6bituser-testing1cda1.png]]<br />
<br><br />
Based on the computed statistics illustrated in the box-plot above, the median number of clicks it takes per tester to accomplish a task ranges from 1 to 8 clicks, with 3 clicks being the median. For the purpose of understanding, we could take the measurement of 3 clicks per task as a benchmark, to be compared on subsequent test sessions and observe if there are any improvements.<br />
<br><br><br />
[[Image: 6bituser-testing1cda2.png]]<br />
<br><br />
More statistics were computed in the box-plot diagram above to understand the median time spent to accomplish a task and we observe that the time taken ranges from 4 seconds to 18 seconds, with 10 seconds being the median. We will also be taking the measurement of 10 seconds per task as a benchmark to compare with subsequent test sessions and observe if there are any improvements.<br />
<br />
====Additional Observations====<br />
Further drill down on the click data has identified an observation where most testers take more clicks to accomplish Step 4 of the instructions. In Step 4, testers are required to subscribe a forum. In this observation, we are able to relate that testers are unable to easily find the Subscribe to Forum button. This finding is aligned with a common feedback that we should consider replicating the subscription button to a more intuitive location on the webpage.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Milestones</font></div>=<br />
<br />
[[Image:6-bit_schedule.png|600px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule Metric</font></div>=<br />
Every iteration, schedule metric values are calculated to understand the project progress. They are broadly categorized into 5 different groups, where different action plans will apply. The acceptable range of value is within 90% to 110%, offering some buffer for natural inaccuracies between forecasting and execution.<br />
<br><br><br />
Total Schedule Metric Value = Planned no. of days taken (P) / Actual no. of Days Assigned (A) x 100%<br />
<br><br><br />
[[Image:6-bit_schedulemetric.png|center|600px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Bug Metric</font></div>=<br />
==Log==<br />
[[Image:6-bit_BugMetric.png|550px]]<br />
[[Image:6-bit_BugLog.png|600px]]<br />
<div style="text-align: right;"><br />
Bug Log: [https://docs.google.com/spreadsheet/ccc?key=0Aqd6IiSLbMwQdEI5TldNSEhpcVRjb1puYzU3ZHJOckE |<font color="#CD004E"><b>Click Here</b></font>]<br />
</div><br />
<br><br />
Bug logging for Chapalang! takes the direction of being practical and easily monitored from both macro and micro perspectives. Whenever a bug is found, a new row is entered with the following data:<br />
* Index number<br />
* Bug description<br />
* Found by<br />
* Found date<br />
* Expected solve-by date<br />
* Bug severity<br />
* Status<br />
* Owner of the function<br />
* Fixed date<br />
* Closed by (Tester)<br />
* Close date<br />
* Additional comments<br />
==Metric==<br />
Bugs are classified into 3 different categories of complexity, easy, moderate and hard. Each category is assigned points of 1, 5 and 10 respectively, lower is better.<br />
<br><br><br />
Total Points for Each Iteration = Σ Points of the Bugs in each iteration<br />
<br><br />
[[Image:6-bit_BugMetricFormula.png|500px|center]]<br />
<br><br />
After assigning each bug with points associated by its complexity, we will track the total bug scores at the end of each week before deciding if there should be any actions to be taken. The following is an action plan for our bug metric:<br />
<br><br />
[[Image:6-bit_BugMetricFormula2.png|500px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Risk & Mitigation</font></div>=<br />
<br><br />
[[Image:6-bit_RiskDiagram.png|600px]]<br />
<br><br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2&diff=114373IS480 Team wiki: 2012T1 6-bit Project Management UT22012-12-04T03:44:19Z<p>Huiling.ong.2010: /* Team Meeting Minutes */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule</font></div>=<br />
==Planned Schedule==<br />
[[Image:6-bit_ScheduleDiagramOverview.png|left|750px|link=""]]<br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
==Meeting Minutes==<br />
===Team Meeting Minutes===<br />
{|<br />
|[[https://docs.google.com/document/d/1nHl51M2qzY4gynJ8tVR6wKqV_lWtJtncl3nbESSnQvU/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]]<br />
|[[https://docs.google.com/document/d/129JDPU8l7PbX-JjferJ-J83JXSIAo5-cXM4_Odw3o5c/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]]<br />
|[[https://docs.google.com/document/d/1BPn6a-XMMAN18TbdlDER27f8Eleb8sUJhcas1bgDOQI/edit |<font color="#CD004E"><b>Meeting Minute 21</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LtSANlI6pDyV_PpGDAVg85PjFVKmDmWWnYC5lXAHh68/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qx6hX462uQDEfwiB3r3ee71eTKaPXSArCZS7y1TOWA4/edit |<font color="#CD004E"><b>Meeting Minute 12</b></font>]]<br />
|[[https://docs.google.com/document/d/1IdjkCbomLgszePgImX2XsTeUHX54e54xRTIjjFoZM6g/edit |<font color="#CD004E"><b>Meeting Minute 22</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/11lQzKaddghH7FHACcTnPQDJnE6ZaScT8Q8nU2YvH8gU/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]]<br />
|[[https://docs.google.com/document/d/1HPdXr28aTDK-RmijqPYTLG1iCUv-JbpkIJ8zzgzTplg/edit |<font color="#CD004E"><b>Meeting Minute 13</b></font>]]<br />
|[[https://docs.google.com/document/d/1gMoTceQakeT42-FO0duVxRajea2hJAUVw8Eu1AfqtfY/edit |<font color="#CD004E"><b>Meeting Minute 23</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1gZuhKW-QMbhUR_oh6Ty8EE17JTYkTFkWCfG6UHrU7-c/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]]<br />
|[[https://docs.google.com/document/d/1ii-ZenbOTZR9drEQCFJ4hX8raXvpgufELaZY80M2GYI/edit |<font color="#CD004E"><b>Meeting Minute 14</b></font>]]<br />
|[[https://docs.google.com/document/d/12vYfm8jo9c2eZ3VwnL2z6vn6l__D6heDhCHdEWVPg4I/edit |<font color="#CD004E"><b>Meeting Minute 24</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1H-8fODLc79U6-IXScSfemjRLOyjvzC6_k0aig6BDcBY/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]]<br />
|[[https://docs.google.com/document/d/1I3qlvujdLVmY_L22VMsKrtISIFI5CnxmtZnMNdJdxfc/edit |<font color="#CD004E"><b>Meeting Minute 15</b></font>]]<br />
|[[https://docs.google.com/document/d/1jPIW-xe7p6kjzGF_YMmk0K2mPzWil1zUfBQOwGc8wRk/edit |<font color="#CD004E"><b>Meeting Minute 25</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Qx4jdRZoE8hXv3u1R4dWke5b-kyMxIc7ASzPIh4ShRQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]]<br />
|[[https://docs.google.com/document/d/1Pcd6ZADI7ZEuXzq3exrss4nJQhotxAq7-ENfy_OVs6o/edit |<font color="#CD004E"><b>Meeting Minute 16</b></font>]]<br />
|[[https://docs.google.com/document/d/1NDCoF37ckdhbys57BLEXShcAcraxzOKpoNbFvpWWUQM/edit |<font color="#CD004E"><b>Meeting Minute 26</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1uSkv_cux0PqnRTKS-w72wQLgL1ZKaCpXhzDm5uamfMU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]]<br />
|[[https://docs.google.com/document/d/12jW-ycBkfivYL2pg7nrVvb9SF7_XmiglVGGnWAjp6uQ/edit |<font color="#CD004E"><b>Meeting Minute 17</b></font>]]<br />
|[[https://docs.google.com/document/d/1Amo6YgCkVA3YD-iqyIxhyG8embuClo50KXsznVgoWQE/edit |<font color="#CD004E"><b>Meeting Minute 27</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1pTivyZ9D3jSU1Kf5VoW4-Xl_C9Abg-fL_6SI6GP_hz0/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qbhow5u8GsE42hr9b8o1S2HNeJfG5PTX24W70ZHyCfI/edit |<font color="#CD004E"><b>Meeting Minute 18</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LTLnY5JN2EfiU9drp3d7zGmoCxsSYr1nL4UMvwfXDdU/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]]<br />
|[[https://docs.google.com/document/d/1fbnoWNTimFyUC01lgeblvVCLTySS8Ik2JU_wdZ656RU/edit |<font color="#CD004E"><b>Meeting Minute 19</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Nlo5hnsYbfh4dFSnfsV6Wyv5nxJsmDWF8ZMFKFA9Pac/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]]<br />
|[[https://docs.google.com/document/d/1o1zVXcdHaXCLNzS9rHq528rLEmXMFl3df3ffTFLMtho/edit |<font color="#CD004E"><b>Meeting Minute 20</b></font>]]<br />
|}<br />
<br />
===Supervisor Meeting Minutes===<br />
[https://docs.google.com/document/d/1iuSvaC9Wu-v7dToRp41IwmpdpQ0KtSTJIgpabmiolXQ/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1rXJuYE684ZpYbRyHknn4pmLpJZ9Y5o01QaJT34TD0gY/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1Gy7TOJr9aeyd8pcU_loabY1l3NByVm3nVKqOQnnJRbM/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1DGrSXaCTOtRL_iSOaOI_mHC2DOS7z4Vi6clzomkGkcI/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1VLEizDPdae_enbEtoHo9IGPM4-k9JXe7RFJ1hhiDTBA/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/13MyE--Ymz-dNiQPvgCjGutL23JZwotnoIPlYw7QqmXQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1UUDCW8YMttW2rwAxLJhSfqccBdedYoofVskc9qerIxU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/17QEpHsvitqzO9BO9MkB42umN3_9k6Useli4N2fYoCNU/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1masrY10EdoXrAdwmTnW-POF0RVEYGeHbOorf-0EEC-0/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1u2jcuwSkGqk4lGcGdF4UriFgzT9dNgNAb1ekERDvitQ/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1eHVDrzwLxkGhrElcgPUOWhcQBwLdGdXcmCVvT_u-Va8/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]<br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Testing</font></div>=<br />
==Test Cases==<br />
[https://dl.dropbox.com/u/56071797/Test%20Cases.docx |<font color="#CD004E"><b>Test Cases</b></font>]<br />
<br />
==Test Plans==<br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2001_17_10_2012.docx <font color="#CD004E"><b>Test Plan 1 ''on 17 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2002_28_09_2012.docx <font color="#CD004E"><b>Test Plan 2 ''on 28 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2003_19_10_2012.docx <font color="#CD004E"><b>Test Plan 3 ''on 19 October 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2004_01_11_2012.docx <font color="#CD004E"><b>Test Plan 4 ''on 4 November 2012''</b></font>]<br />
<br />
==User Testing==<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #728FCE; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing|<font color="#CD004E"><b>User Testing 1</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing|<font color="#CD004E"><b>User Testing 2</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing|<font color="#CD004E"><b>User Testing 3</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing|<font color="#CD004E"><b>User Testing 4</b></font>]]<br />
<br />
|}<br />
===User Testing 2===<br />
[[Image:6bituser-testing2.png]]<br />
<br />
====Test Description====<br />
The objective of User Test 2 is on functionality and usability testing of the system. The coverage of the test is focused on forum and basic marketplace functions. <br><br><br />
The purpose of re-testing on forum function is to test for an experience improvement. Basic marketplace functions will consist of a complete product display to payment process. We will want to find out if the changes made after User Test 1 is offering an improved user experience to users, and whether the improvement is consistent between forum and marketplace functions.<br />
<br />
====Testers Background====<br />
There are a total of 46 testers who attended the User Test, of which 61% (28) are male and 39% (18) are female, representing various schools in SMU with SIS students being the majority. It is also observed that most testers are users of Chrome and Firefox web browser.<br />
There is no significant difference between testers’ background in User Test 1 and 2.<br />
<br><br />
[[Image:6bituser-testing2results.png|center]]<br />
<br />
====Test Groups====<br />
There are 2 test groups employed in this test.<br />
<br><br><br />
Group A (Control Group) consists of 17 testers who were testers from User Test 1. The purpose is to test if their return experience with the system has any improvements.<br />
<br><br />
Group B (Test Group) consists of 29 new testers who have not participated in any of our previous user tests. The purpose of their participation is for comparison, to find out if they have a different experience from the returning testers in Group A.<br />
<br />
====Test Procedures====<br />
Testers are invited to attend the User Test session and required to bring their own laptops. They are informed on the purpose of the test and given a brief description of the system objective of Chapalang!. <br />
<br><br><br />
Subsequently, they are provided with an instruction sheet for a guided test experience. Testers will be required to perform a series of system tasks based on a test case that will go through all the system features and use-case. Thereafter, testers will fill in details in an open-ended textbox appended after each question, should they encounter any bugs or suggestions for improvements.<br />
<br />
====Test Instruction====<br />
[https://dl.dropbox.com/u/56071797/User%20Testing%202%20Instructions.docx Click Here to Download User Testing 2 Instruction]<br />
<br />
====Test Results====<br />
[[Image: 6bituser-testing2resultsfigure.png|250px]]<br />
<br><br />
Based on the survey questions, the results are positive with most testers having a good level of comfort using our web application.<br />
<br> <br><br />
There are also 21 reported bugs, and 69 recommendations for improvements received. The following are the top 10 bugs reported.<br />
<br><br />
[[Image: 6bituser-testing2bug.png|600px]]<br />
<br><br />
<br><br />
The top 10 most frequently mentioned or important recommendations will be published and appended below.<br />
<br><br />
[[Image: 6bituser-testing2recommendation.png|600px]]<br />
<br />
====Click Data Analysis(User Test 1 vs. User Test 2 – Forum Functions Only)====<br />
Additionally, click data of each test session has also been collected and analysed. They are also being compared to that with the results of User Test 1.<br><br />
[[Image: 6bituser-testing2cda1.png]]<br />
<br><br />
The above box-plot represents 3 sets of data comparing the number of clicks per task, for discussion forum functions only. UT1 represents the results from User Test 1, UT2A represents the results from Group A testers of User Test 2, while UT2B represents the results from Group B testers of User Test 2. For the objective of fair comparisons, the results from User Test 2 has been drilled down to consists of data<br />
<br><br><br />
The median number of clicks it takes per tester to accomplish a forum-related task in User Test 2 ranges from 1 to 3 clicks with 2 clicks being the median, a decrement from the median of 3 clicks, as well as a smaller variance as compared to User Test 1. Additionally, it can also be observed that there is no significant difference in the results between Group A and Group B users.<br />
<br><br><br />
Preliminary, we can observe an improvement in the user experience for Group A users between the 2 tests. The improvement can be broadly attributed to the improvements made as well as the high learnability of the system interface design. However, this observation is not conclusive and more data is required.<br />
<br><br />
[[Image: 6bituser-testing2cda2.png]]<br />
<br><br />
Additional statistics were computer and observed that the median time spent to accomplish a forum-related task for Group A tester is 4 seconds, and Group B tester is 5 seconds. Again, this is a significant decrement in the time spent from User Test 1, where testers spent a median of 10 seconds between each task. <br />
Based on the finding, we can reasonably derive that there is an improved user experience between User Test 1 and User Test 2, attributing to the improvements made and high learnability of the system. In addition, the improved user experience is shared between both Group A and Group B users, possibly suggesting that the improved system does not require much training or high learning curve.<br />
====Click Data Analysis (Group A vs. Group B – Marketplace Functions)====<br />
Prospectively, we will also study the user experience difference between Group A and Group B testers on marketplace functions, based on the click data which measures the number of clicks involved per task and time taken in seconds between each task.<br />
<br><br><br />
In the box-plot diagram above, UT2A refers to User Test 2 Group A testers, while UT2B refers to User Test 2 Group B testers. Each box-plot is represented by data of a specific group of users, and the results computed based on the number of clicks of time pertaining to forum or marketplace functions.<br />
<br><br />
[[Image: 6bituser-testing2cda3.png]]<br />
<br><br />
Comparing marketplace functions, both Group A and Group B testers have made a median of 2 clicks to accomplish each task. While Group B testers have a wider variance of clicks of up to 4 clicks, it can be broadly attributed to outliers, user experiments or some learning curve involved in getting used to the functions or interface objects placements. <br />
<br><br />
[[Image: 6bituser-testing2cda4.png]]<br />
<br><br />
The result when comparing the time taken is consistent with the preliminary conclusion when comparing the number of clicks per task. The median time taken for Group A and Group B testers for forum and marketplace functions are within the range of 4 to 5 seconds. The difference between the median records is insignificant.<br />
<br><br><br />
Overall, the result is consistent across forums and marketplace functions, between testers from both User Tests and test groups. It is also consistent with our earlier preliminary conclusion that the improvements made between the two User Tests have resulted in improved user experience, and there is a good level of learnability in the interface design.<br />
<br><br><br />
While there are limitations in this test, where there are other externalities such as network performance, computing habits of testers and response time of each users, the macro results of the test provide a reasonable sampling on the objective of the test.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Milestones</font></div>=<br />
<br />
[[Image:6-bit_schedule.png|600px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule Metric</font></div>=<br />
Every iteration, schedule metric values are calculated to understand the project progress. They are broadly categorized into 5 different groups, where different action plans will apply. The acceptable range of value is within 90% to 110%, offering some buffer for natural inaccuracies between forecasting and execution.<br />
<br><br><br />
Total Schedule Metric Value = Planned no. of days taken (P) / Actual no. of Days Assigned (A) x 100%<br />
<br><br><br />
[[Image:6-bit_schedulemetric.png|center|600px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Bug Metric</font></div>=<br />
==Log==<br />
[[Image:6-bit_BugMetric.png|550px]]<br />
[[Image:6-bit_BugLog.png|600px]]<br />
<div style="text-align: right;"><br />
Bug Log: [https://docs.google.com/spreadsheet/ccc?key=0Aqd6IiSLbMwQdEI5TldNSEhpcVRjb1puYzU3ZHJOckE |<font color="#CD004E"><b>Click Here</b></font>]<br />
</div><br />
<br><br />
Bug logging for Chapalang! takes the direction of being practical and easily monitored from both macro and micro perspectives. Whenever a bug is found, a new row is entered with the following data:<br />
* Index number<br />
* Bug description<br />
* Found by<br />
* Found date<br />
* Expected solve-by date<br />
* Bug severity<br />
* Status<br />
* Owner of the function<br />
* Fixed date<br />
* Closed by (Tester)<br />
* Close date<br />
* Additional comments<br />
==Metric==<br />
Bugs are classified into 3 different categories of complexity, easy, moderate and hard. Each category is assigned points of 1, 5 and 10 respectively, lower is better.<br />
<br><br><br />
Total Points for Each Iteration = Σ Points of the Bugs in each iteration<br />
<br><br />
[[Image:6-bit_BugMetricFormula.png|500px|center]]<br />
<br><br />
After assigning each bug with points associated by its complexity, we will track the total bug scores at the end of each week before deciding if there should be any actions to be taken. The following is an action plan for our bug metric:<br />
<br><br />
[[Image:6-bit_BugMetricFormula2.png|500px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Risk & Mitigation</font></div>=<br />
<br><br />
[[Image:6-bit_RiskDiagram.png|600px]]<br />
<br><br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Project_Management&diff=114372IS480 Team wiki: 2012T1 6-bit Project Management2012-12-04T03:43:11Z<p>Huiling.ong.2010: /* Team Meeting Minutes */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule</font></div>=<br />
==Planned Schedule==<br />
[[Image:6-bit_ScheduleDiagramOverview.png|750px|center]]<br />
<br />
==Meeting Minutes==<br />
===Team Meeting Minutes===<br />
{|<br />
|[[https://docs.google.com/document/d/1nHl51M2qzY4gynJ8tVR6wKqV_lWtJtncl3nbESSnQvU/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]]<br />
|[[https://docs.google.com/document/d/129JDPU8l7PbX-JjferJ-J83JXSIAo5-cXM4_Odw3o5c/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]]<br />
|[[https://docs.google.com/document/d/1BPn6a-XMMAN18TbdlDER27f8Eleb8sUJhcas1bgDOQI/edit |<font color="#CD004E"><b>Meeting Minute 21</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LtSANlI6pDyV_PpGDAVg85PjFVKmDmWWnYC5lXAHh68/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qx6hX462uQDEfwiB3r3ee71eTKaPXSArCZS7y1TOWA4/edit |<font color="#CD004E"><b>Meeting Minute 12</b></font>]]<br />
|[[https://docs.google.com/document/d/1IdjkCbomLgszePgImX2XsTeUHX54e54xRTIjjFoZM6g/edit |<font color="#CD004E"><b>Meeting Minute 22</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/11lQzKaddghH7FHACcTnPQDJnE6ZaScT8Q8nU2YvH8gU/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]]<br />
|[[https://docs.google.com/document/d/1HPdXr28aTDK-RmijqPYTLG1iCUv-JbpkIJ8zzgzTplg/edit |<font color="#CD004E"><b>Meeting Minute 13</b></font>]]<br />
|[[https://docs.google.com/document/d/1gMoTceQakeT42-FO0duVxRajea2hJAUVw8Eu1AfqtfY/edit |<font color="#CD004E"><b>Meeting Minute 23</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1gZuhKW-QMbhUR_oh6Ty8EE17JTYkTFkWCfG6UHrU7-c/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]]<br />
|[[https://docs.google.com/document/d/1ii-ZenbOTZR9drEQCFJ4hX8raXvpgufELaZY80M2GYI/edit |<font color="#CD004E"><b>Meeting Minute 14</b></font>]]<br />
|[[https://docs.google.com/document/d/12vYfm8jo9c2eZ3VwnL2z6vn6l__D6heDhCHdEWVPg4I/edit |<font color="#CD004E"><b>Meeting Minute 24</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1H-8fODLc79U6-IXScSfemjRLOyjvzC6_k0aig6BDcBY/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]]<br />
|[[https://docs.google.com/document/d/1I3qlvujdLVmY_L22VMsKrtISIFI5CnxmtZnMNdJdxfc/edit |<font color="#CD004E"><b>Meeting Minute 15</b></font>]]<br />
|[[https://docs.google.com/document/d/1jPIW-xe7p6kjzGF_YMmk0K2mPzWil1zUfBQOwGc8wRk/edit |<font color="#CD004E"><b>Meeting Minute 25</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Qx4jdRZoE8hXv3u1R4dWke5b-kyMxIc7ASzPIh4ShRQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]]<br />
|[[https://docs.google.com/document/d/1Pcd6ZADI7ZEuXzq3exrss4nJQhotxAq7-ENfy_OVs6o/edit |<font color="#CD004E"><b>Meeting Minute 16</b></font>]]<br />
|[[https://docs.google.com/document/d/1NDCoF37ckdhbys57BLEXShcAcraxzOKpoNbFvpWWUQM/edit |<font color="#CD004E"><b>Meeting Minute 26</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1uSkv_cux0PqnRTKS-w72wQLgL1ZKaCpXhzDm5uamfMU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]]<br />
|[[https://docs.google.com/document/d/12jW-ycBkfivYL2pg7nrVvb9SF7_XmiglVGGnWAjp6uQ/edit |<font color="#CD004E"><b>Meeting Minute 17</b></font>]]<br />
|[[https://docs.google.com/document/d/1Amo6YgCkVA3YD-iqyIxhyG8embuClo50KXsznVgoWQE/edit |<font color="#CD004E"><b>Meeting Minute 27</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1pTivyZ9D3jSU1Kf5VoW4-Xl_C9Abg-fL_6SI6GP_hz0/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qbhow5u8GsE42hr9b8o1S2HNeJfG5PTX24W70ZHyCfI/edit |<font color="#CD004E"><b>Meeting Minute 18</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LTLnY5JN2EfiU9drp3d7zGmoCxsSYr1nL4UMvwfXDdU/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]]<br />
|[[https://docs.google.com/document/d/1fbnoWNTimFyUC01lgeblvVCLTySS8Ik2JU_wdZ656RU/edit |<font color="#CD004E"><b>Meeting Minute 19</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Nlo5hnsYbfh4dFSnfsV6Wyv5nxJsmDWF8ZMFKFA9Pac/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]]<br />
|[[https://docs.google.com/document/d/1o1zVXcdHaXCLNzS9rHq528rLEmXMFl3df3ffTFLMtho/edit |<font color="#CD004E"><b>Meeting Minute 20</b></font>]]<br />
|}<br />
<br />
===Supervisor Meeting Minutes===<br />
[https://docs.google.com/document/d/1iuSvaC9Wu-v7dToRp41IwmpdpQ0KtSTJIgpabmiolXQ/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1rXJuYE684ZpYbRyHknn4pmLpJZ9Y5o01QaJT34TD0gY/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1Gy7TOJr9aeyd8pcU_loabY1l3NByVm3nVKqOQnnJRbM/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1DGrSXaCTOtRL_iSOaOI_mHC2DOS7z4Vi6clzomkGkcI/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1VLEizDPdae_enbEtoHo9IGPM4-k9JXe7RFJ1hhiDTBA/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/13MyE--Ymz-dNiQPvgCjGutL23JZwotnoIPlYw7QqmXQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1UUDCW8YMttW2rwAxLJhSfqccBdedYoofVskc9qerIxU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/17QEpHsvitqzO9BO9MkB42umN3_9k6Useli4N2fYoCNU/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1masrY10EdoXrAdwmTnW-POF0RVEYGeHbOorf-0EEC-0/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1u2jcuwSkGqk4lGcGdF4UriFgzT9dNgNAb1ekERDvitQ/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1eHVDrzwLxkGhrElcgPUOWhcQBwLdGdXcmCVvT_u-Va8/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]<br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Testing</font></div>=<br />
==Test Cases==<br />
[https://dl.dropbox.com/u/56071797/Test%20Cases.docx |<font color="#CD004E"><b>Test Cases</b></font>]<br />
<br />
==Test Plans==<br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2001_17_10_2012.docx <font color="#CD004E"><b>Test Plan 1 ''on 17 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2002_28_09_2012.docx <font color="#CD004E"><b>Test Plan 2 ''on 28 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2003_19_10_2012.docx <font color="#CD004E"><b>Test Plan 3 ''on 19 October 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2004_01_11_2012.docx <font color="#CD004E"><b>Test Plan 4 ''on 4 November 2012''</b></font>]<br />
<br />
==User Testing==<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #728FCE; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing|<font color="#CD004E"><b>User Testing 1</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing|<font color="#CD004E"><b>User Testing 2</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing|<font color="#CD004E"><b>User Testing 3</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing|<font color="#CD004E"><b>User Testing 4</b></font>]]<br />
<br />
|}<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Milestones</font></div>=<br />
<br />
[[Image:6-bit_schedule.png|600px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule Metric</font></div>=<br />
Every iteration, schedule metric values are calculated to understand the project progress. They are broadly categorized into 5 different groups, where different action plans will apply. The acceptable range of value is within 90% to 110%, offering some buffer for natural inaccuracies between forecasting and execution.<br />
<br><br><br />
Total Schedule Metric Value = Planned no. of days taken (P) / Actual no. of Days Assigned (A) x 100%<br />
<br><br><br />
[[Image:6-bit_schedulemetric.png|center|600px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Bug Metric</font></div>=<br />
==Log==<br />
[[Image:6-bit_BugMetric.png|550px]]<br />
[[Image:6-bit_BugLog.png|600px]]<br />
<div style="text-align: right;"><br />
Bug Log: [https://docs.google.com/spreadsheet/ccc?key=0Aqd6IiSLbMwQdEI5TldNSEhpcVRjb1puYzU3ZHJOckE |<font color="#CD004E"><b>Click Here</b></font>]<br />
</div><br />
<br><br />
Bug logging for Chapalang! takes the direction of being practical and easily monitored from both macro and micro perspectives. Whenever a bug is found, a new row is entered with the following data:<br />
* Index number<br />
* Bug description<br />
* Found by<br />
* Found date<br />
* Expected solve-by date<br />
* Bug severity<br />
* Status<br />
* Owner of the function<br />
* Fixed date<br />
* Closed by (Tester)<br />
* Close date<br />
* Additional comments<br />
==Metric==<br />
Bugs are classified into 3 different categories of complexity, easy, moderate and hard. Each category is assigned points of 1, 5 and 10 respectively, lower is better.<br />
<br><br><br />
Total Points for Each Iteration = Σ Points of the Bugs in each iteration<br />
<br><br />
[[Image:6-bit_BugMetricFormula.png|500px|center]]<br />
<br><br />
After assigning each bug with points associated by its complexity, we will track the total bug scores at the end of each week before deciding if there should be any actions to be taken. The following is an action plan for our bug metric:<br />
<br><br />
[[Image:6-bit_BugMetricFormula2.png|500px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Risk & Mitigation</font></div>=<br />
<br><br />
[[Image:6-bit_RiskDiagram.png|600px]]<br />
<br><br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=File:6-bitTeamMembers.png&diff=114343File:6-bitTeamMembers.png2012-12-03T14:59:32Z<p>Huiling.ong.2010: uploaded a new version of "Image:6-bitTeamMembers.png"</p>
<hr />
<div></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=File:6-bitTeamMembers.png&diff=114342File:6-bitTeamMembers.png2012-12-03T14:57:02Z<p>Huiling.ong.2010: uploaded a new version of "Image:6-bitTeamMembers.png"</p>
<hr />
<div></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype&diff=114337IS480 Team wiki: 2012T1 6-bit PD User Interface Prototype2012-12-03T13:50:55Z<p>Huiling.ong.2010: /* Email Notification */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #FE2E64; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:110%; text-align:center; color:#FE2E64" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_PD_Technical_Diagrams|<font color="#CD004E"><b>Technical Diagrams</b></font>]]<br />
<br />
| style="font-size:110%; text-align:center; color:#FE2E64" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype|<font color="#CD004E"><b>User Interface Prototype</b></font>]]<br />
<br />
| style="font-size:110%; text-align:center; color:#FE2E64" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_PD_Business_Intelligence_and_Analytics|<font color="#CD004E"><b>Business Intelligence and Analytics</b></font>]]<br />
|}<br />
<br />
<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Prototype</font></div>=<br />
==About Chapalang.com==<br />
[[Image:6-bit_UI_11.png|center|650px]]<br />
==Login Page==<br />
[[Image:6-bit_UI_1.png|center|650px]]<br />
==Marketplace Front Page==<br />
[[Image:6-bit_UI_2.png|center|650px]]<br />
==Payment Process==<br />
[[Image:6-bit_UI_3.png|center|650px]]<br />
==Profile Page==<br />
[[Image:6-bit_UI_4.png|center|650px]]<br />
==Manage Product==<br />
[[Image:6-bit_UI_5.png|center|650px]]<br />
==Manage Order==<br />
[[Image:6-bit_UI_6.png|center|650px]]<br />
==Manage Sale==<br />
[[Image:6-bit_UI_15.png|center|650px]]<br />
==Giftsharing==<br />
[[Image:6-bit_UI_7.png|center|650px]]<br />
<br><br />
[[Image:6-bit_UI_8.png|center|650px]]<br />
==Invite Friends==<br />
[[Image:6-bit_UI_9.png|center|650px]]<br />
==Top Bar==<br />
[[Image:6-bit_UI_10.png|center|650px]]<br />
==Mass Order==<br />
[[Image:6-bit_UI_14.png|center|650px]]<br />
<br><br />
[[Image:6-bit_UI_12.png|center|650px]]</div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit&diff=114336IS480 Team wiki: 2012T1 6-bit2012-12-03T13:49:32Z<p>Huiling.ong.2010: /* Chapalang's Main Features */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Current Status</font></div>=<br />
<br />
{| class="wikitable" cellpadding="15"<br />
<br />
|-<br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 46%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Current Iteration</b> <br />
| style="border-bottom:1px solid #ffffff; border-top:1px solid #ffffff; background:none;border: 1px solid #ffffff" width="2%" | &nbsp;<br />
| style="background: #ffffff; color: #000000; font-weight: bold; text-indent: 2px; width: 50%; font-size:200%; text-align:left; border: 1px solid #ffffff" valign="top" |<b>Meeting Status</b> <br />
|-<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Iteration Number :''' <br />
16 *Final Iteration*<br />
<br><br />
'''Iteration Start Date : '''<br />
24 November 2012<br />
<br><br />
'''Iteration End Date :'''<br />
3 December 2012<br />
<br><br />
'''Iteration Task :'''<br />
<br><br />
1. Final Presentation<br />
<br><br />
2. Poster Day<br />
<br><br />
<br />
<br />
| style="border-bottom:1px solid #ffffff; background: #ffffff; color: #FFFFFF; font-weight: bold; padding: 10px 15px 0 15px; font-size: 26px;" valign="top"|<br />
| style= "background:#1C1C1C; color: #ffffff; padding: 10px 4px 0 15px; font-size: 15px;" valign="top" |<br />
<br />
'''Weekly Meeting Schedule'''<br />
<br><br />
Every Monday, Wednesday, Friday<br />
<br><br />
SIS Analytics Kitchen<br />
<br><br />
12pm to 3pm<br />
<br><br />
<br />
'''Weekly Supervisor Meeting'''<br />
<br><br />
Every Monday<br />
<br><br />
2pm to 3pm<br />
|}<br />
<div style="text-align: right;"><br />
<font size="2">''Last Update: 28 November 2012''</font><br />
</div><br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Team</font></div>=<br />
[[Image:6-bitTeamMembers.png|alt=text|6-bitTeamMembers|centre|650px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >The Project: Chapalang</font></div>=<br />
<div style="text-align: center"><font color="#00BFFF">''Talk, Buy, Sell, Share, all on Chapalang!''</font></div><br />
<font color="#FE2EF7">Chapalang!</font> is a social utility that connects people with friends and new friends by offering a place for exchanging ideas and information on its public domain. People use our discussion forums to write HOWTOs, share findings, ask questions, comment on news, and many more.<br />
<br><br />
<font color="#FE2EF7">Chapalang!</font> also features a social marketplace for you to buy online, and participate in mass orders in a convenient and reliable way.<br />
<br><br />
Best of all, you can browse wish lists of your friends to know what are the right things to buy on special occasions. You could buy the gift on <br />
<font color="#FE2EF7">Chapalang!</font> and have it sent to their doorsteps, or organize a Gift Sharing campaign to share the costs of gift with other friends.<br />
<br />
[[Image:chapalangprocesses.png|1100px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Main Features</font></div>=<br />
[[Image:ChapalangLogo.png|left|150px]]<br />
<br><br />
<i>proposes the following unique features:</i><br />
<br><br />
[[Image:6-bitGroupbuyprocess.png|center|1000px]]<br />
<br><br />
<b>Gifts Sharing</b> : <br />
<br><br />
Gifting can be simple or collective. A simple gift is purchased when a user pays for the full costs of the gift, and states the recipient’s contact details upon checkout. Chapalang! will contact the recipient for their address, and subsequently fulfil the order with the delivery of goods.<br />
<br><br />
<br><br />
A collective gift is purchased when a user takes on the role of an organizer and initiates a Gift Sharing Campaign. He will select a product from a user’s wish list, or any other product in the marketplace, and designate it to be the gift to be shared. He will also decide on the product options, if any, as well as the delivery method. <br />
<br><br />
<br><br />
Thereafter, he can invite a list of mutual friends whom he wants to share the gift with. The invitees will be informed of the campaign via a notification, and will be able to contribute any varying amount on the campaign page. They will also be able to hide their amount of contribution, or even hide their contribution record from public. Upon successfully raising the target amount which is the price of the gift, an email will be sent to the recipient for him/her to update their address for fulfilment and delivery.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitMassorderprocess.png|center|1000px]]<br />
<b>Mass orders</b> : <br />
<br>Mass Orders (MO) should be structured and organized, just like a regular product item in the marketplace. <br />
<br><br />
<br><br />
When creating an MO, the buyer will input the price, description, minimum collective quantity for the MO to go through, the maximum collective quantity accepted for the MO if it’s a limited quantity offer, as well as the start and end period of the MO. An MO organizer can be an individual or a company. The organizer will be able to invite his/her friends, or regular customers to the MO. <br />
<br><br />
<br><br />
Participants of an MO will be able to view the MO page, enter a desired quantity and checkout. In the checkout process, participants will be required to enter their delivery address and choose their preferred shipping method. Payment is made upon ordering, safeguarded by the esrow service, and will be paid to the sellers if the MO is successful. In the event that MO is unsuccessful or cancelled, full amount of their orders will be refunded to all participants automatically.<br />
<br><br />
[[Image: 6-bit_Border.png|center]]<br />
<br><br />
[[Image:6-bitEscrowprocess.png|centre|1000px]]<br />
<b>Escrow</b> : <br />
<br><br />
In most other agent websites, buyers either pay to sellers directly or buyers pay to the agent and agent will pay the buyers 30 days later. We will turn this credit period to the advantage of buyers and sellers, introducing assurance.<br />
<br><br><br />
In any transaction on Chapalang!, the buyer will pay to Chapalang! directly. Sellers are notified of the receipt of payment, and will proceed to ship the item out to the buyer. Upon receipt of the order, buyers will revisit Chapalang! and indicate that the goods are received satisfactorily, and Chapalang! will then pay the sellers in the next 3 days. However, if there is no response or dispute from the buyers within 30 days, the order is assumed to be satisfactorily fulfilled and the payment will be released to the seller. In the event of disputes, buyers and sellers are encouraged to negotiate for a recovery, or in the case of an exhausted negotiation, Chapalang! may issue a full or partial refund to the customers.<br />
<br><br><br />
Systematically, the Chapalang! system will support this this use case through a series of functions. <br />
*Firstly, the system will support a goods receipt acknowledgement process, recording the goods receipt, triggering of payment activities to sellers upon 30 days grace or upon the record of goods receipt. <br />
*Secondly, sellers should be able to see their sales and know how much they will be receiving from Chapalang! and when. <br />
*Thirdly, there should be a messaging channel to facilitate communications between the buyer and seller<br />
*Fourthly, there should be a refund method to allow sellers to refund a transaction should be accept that he’s unable to recover or fulfil the order<br />
*Lastly, administrator of Chapalang! should be able to see a list of fulfilled, or assumed fulfilled transactions ready for payment to the sellers<br />
<br />
<div style="text-align: right;"><br />
<font size="2">''Prototype of Chapalang's Features: [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T1_6-bit_PD_User_Interface_Prototype Click Here]''</font><br />
</div><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Chapalang's Low Level Functions</font></div>=<br />
==Web Parser==<br />
As an interactive feature, URLs shared on Chapalang! will offer a preview which contains the site title, url, image and description. This should reflect the final URL, instead of any redirecting URL at a higher level.<br />
<br><br><br />
The picking of appropriate objects (title, url, image or description) is important, where standardized Open Graph (OG) protocol meta data of a webpage will be prioritized, before seeking through the other HTML components for referencing objects.<br />
==Private Message==<br />
[[Image:6-bit_message.png|center|600px]]<br />
There should be an in-system communication channel for general users, buyers and sellers. Potential buyers can clarify product specifications with sellers, sellers can confirm delivery address with buyers in case of anomalies, and general users can use it for chatting purposes.<br />
<br><br />
<br>It should be able to perform CRUD of messages between 2 users, in a conversational format. Users are notified via email whenever they receive a message. They will also be able to see past messages exchanged, in a single conversation page.<br />
==Image Cropping Tool==<br />
As all images uploaded by users can be of different dimensions, our system will need a tool to automatically resize and crop away unimportant parts to fit the image dimensions on different pages.<br />
<br><br><br />
Hence, the Image Cropping Tool will help us with automatically resizing an image to the most suitable resolution, before cropping away any extended sides and focus on the centre of the image which is usually the most important message. This tool will be applied throughout the entire platform, on both discussion forums and marketplace.<br />
<br />
==Notifications==<br />
[[Image:6-bit_notification.png|center|300px]]<br />
Users should be appropriately notified on any activities concerning them. They will have a new notifications whenever someone replies to their post, whenever a friend is following them in Chapalang!, or when a product purchased is being shipped, et cetera.<br />
<br><br />
<br><br />
Notification entries should link them to appropriate pages for follow-up actions or even simply viewing more details of the notification. Each in-system notification should also be tied to an email notification for a timelier update to users, and users should have the ability to modify their notifications settings for privacy or information flood control.<br />
<br />
==Search function==<br />
[[Image:6-bit_search.png|center|600px]]<br />
There are many content types on Chapalang!, which includes people, messages, products, posts, et cetera. These content types should be searchable for the purpose of conveniently accessing specific content.<br />
==Profile page==<br />
[[Image:6-bit_profilepage.png|center|600px]]<br />
Every user will have a dedicated profile page, which contains their profile picture, basic particulars, activities and friends. This will create a more social environment, where information of a user is shared among friends.<br />
==Management pages==<br />
[[Image:6-bit_management.png|center|250px]]<br />
There should be a set of management pages, for the management of sales, orders or products. These pages will be able to perform basic CRUD functions, as well as other functions allowing appropriate manipulation of an activity. For example, Manage Sales will allow sellers to view transactional details as well as updating shipping details when an order is fulfilled. On the other hand, Manage Orders will allow buyers to review their purchases and be informed whether their orders are fulfilled. Correspondingly, Manage Products will allow the sellers administer all aspects of a product, from its description, images, pricing, to its options and shipping methods.<br />
<br />
==Settings pages==<br />
[[Image:6-bit_settings.png|center|600px]]<br />
There will be separate pages for Accounts Settings, Privacy Settings and Notifications Settings. Firstly, Account Settings will allow a user to change their basic information imported from Facebook. Secondly, Privacy Settings will provide the option to show or hide certain sensitive information that a user may choose not to show in the public. Lastly, Notifications Settings will help the users manage the quantity and quality of notifications that they receive as they might choose not to be informed of certain activities to prevent information overload.<br />
==Personalized dashboard==<br />
[[Image:6-bit_personalizeddb.png|center|600px]]<br />
A dashboard is the first page the user will see upon login, and will contain a mash up of content from various components on the portal. The content published to the dashboard is personalized through stratification supported by data-driven analytics.<br />
<br><br />
<br><br />
The dashboard will contain the following data:<br />
* Relevant topics from subscribed forums<br />
* Featured discussions<br />
* Product recommendations generated by analytics<br />
* Recent purchases made by friends<br />
* Featured mass orders recommendations generated by analytics<br />
* Seasonal or holidays promotional products recommendations generated by analytics<br />
* New arrival products recommendations generated by analytics<br />
* Reminders on upcoming special dates, friends’ birthdays, and activity invites<br />
The dashboard has a 2-step approach in deriving personalized content. Firstly, a set of meta data describing a user is generated. Secondly, another set of meta data describing a product is also generated. Subsequently, both set of meta data are matched to produce a list of recommendations.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Sponsor</font></div>=<br />
[[Image:Dotcom_Logo.jpg|left]]<br />
<b>Chapalang</b> is a self-proposed project for DotCom Enterprise. Upon successful development, DotCom will commercialize the project for live operations. Mr. Eric Chew, Special Projects Manager will be the primary contact from DotCom. Throughout the development and implementation stages, our team will deploy the project on the live systems provided by DotCom.<br />
<div style="margin-bottom:30px;><br />
<br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Academic Milestones</font></div>=<br />
==Acceptance==<br />
[[Media:Chapalang_Acceptance_Slides.pdf|<font color="#CD004E"> Acceptance Presentation Slides]]<br />
==Midterm==<br />
[[IS480_Team_wiki:_2012T1_6-bit_Midterm_Wikipage | <font color="#CD004E"><b>Mid Term Wiki</b></font>]]<br />
<br><br />
[[Media:Chapalang_Midterm_Slides.pdf|<font color="#CD004E"> Midterm Presentation Slides]]<br />
==Final==<br />
[[Media:Chapalang_Final_Slides.pdf|<font color="#CD004E"> Final Presentation Slides *Coming Soon!*]]</div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4&diff=114335IS480 Team wiki: 2012T1 6-bit Project Management UT42012-12-03T12:55:01Z<p>Huiling.ong.2010: /* Click Data Analysis (Group A vs. Group B – Marketplace Functions) */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule</font></div>=<br />
==Planned Schedule==<br />
[[Image:6-bit_ScheduleDiagramOverview.png|left|750px|link=""]]<br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
==Meeting Minutes==<br />
===Team Meeting Minutes===<br />
{|<br />
|[[https://docs.google.com/document/d/1nHl51M2qzY4gynJ8tVR6wKqV_lWtJtncl3nbESSnQvU/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]]<br />
|[[https://docs.google.com/document/d/129JDPU8l7PbX-JjferJ-J83JXSIAo5-cXM4_Odw3o5c/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]]<br />
|[[https://docs.google.com/document/d/1BPn6a-XMMAN18TbdlDER27f8Eleb8sUJhcas1bgDOQI/edit |<font color="#CD004E"><b>Meeting Minute 21</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LtSANlI6pDyV_PpGDAVg85PjFVKmDmWWnYC5lXAHh68/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qx6hX462uQDEfwiB3r3ee71eTKaPXSArCZS7y1TOWA4/edit |<font color="#CD004E"><b>Meeting Minute 12</b></font>]]<br />
|[[https://docs.google.com/document/d/1IdjkCbomLgszePgImX2XsTeUHX54e54xRTIjjFoZM6g/edit |<font color="#CD004E"><b>Meeting Minute 22</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/11lQzKaddghH7FHACcTnPQDJnE6ZaScT8Q8nU2YvH8gU/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]]<br />
|[[https://docs.google.com/document/d/1HPdXr28aTDK-RmijqPYTLG1iCUv-JbpkIJ8zzgzTplg/edit |<font color="#CD004E"><b>Meeting Minute 13</b></font>]]<br />
|[[https://docs.google.com/document/d/1gMoTceQakeT42-FO0duVxRajea2hJAUVw8Eu1AfqtfY/edit |<font color="#CD004E"><b>Meeting Minute 23</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1gZuhKW-QMbhUR_oh6Ty8EE17JTYkTFkWCfG6UHrU7-c/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]]<br />
|[[https://docs.google.com/document/d/1ii-ZenbOTZR9drEQCFJ4hX8raXvpgufELaZY80M2GYI/edit |<font color="#CD004E"><b>Meeting Minute 14</b></font>]]<br />
|[[https://docs.google.com/document/d/12vYfm8jo9c2eZ3VwnL2z6vn6l__D6heDhCHdEWVPg4I/edit |<font color="#CD004E"><b>Meeting Minute 24</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1H-8fODLc79U6-IXScSfemjRLOyjvzC6_k0aig6BDcBY/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]]<br />
|[[https://docs.google.com/document/d/1I3qlvujdLVmY_L22VMsKrtISIFI5CnxmtZnMNdJdxfc/edit |<font color="#CD004E"><b>Meeting Minute 15</b></font>]]<br />
|[[https://docs.google.com/document/d/1jPIW-xe7p6kjzGF_YMmk0K2mPzWil1zUfBQOwGc8wRk/edit |<font color="#CD004E"><b>Meeting Minute 25</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Qx4jdRZoE8hXv3u1R4dWke5b-kyMxIc7ASzPIh4ShRQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]]<br />
|[[https://docs.google.com/document/d/1Pcd6ZADI7ZEuXzq3exrss4nJQhotxAq7-ENfy_OVs6o/edit |<font color="#CD004E"><b>Meeting Minute 16</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1uSkv_cux0PqnRTKS-w72wQLgL1ZKaCpXhzDm5uamfMU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]]<br />
|[[https://docs.google.com/document/d/12jW-ycBkfivYL2pg7nrVvb9SF7_XmiglVGGnWAjp6uQ/edit |<font color="#CD004E"><b>Meeting Minute 17</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1pTivyZ9D3jSU1Kf5VoW4-Xl_C9Abg-fL_6SI6GP_hz0/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qbhow5u8GsE42hr9b8o1S2HNeJfG5PTX24W70ZHyCfI/edit |<font color="#CD004E"><b>Meeting Minute 18</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LTLnY5JN2EfiU9drp3d7zGmoCxsSYr1nL4UMvwfXDdU/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]]<br />
|[[https://docs.google.com/document/d/1fbnoWNTimFyUC01lgeblvVCLTySS8Ik2JU_wdZ656RU/edit |<font color="#CD004E"><b>Meeting Minute 19</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Nlo5hnsYbfh4dFSnfsV6Wyv5nxJsmDWF8ZMFKFA9Pac/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]]<br />
|[[https://docs.google.com/document/d/1o1zVXcdHaXCLNzS9rHq528rLEmXMFl3df3ffTFLMtho/edit |<font color="#CD004E"><b>Meeting Minute 20</b></font>]]<br />
|}<br />
<br />
===Supervisor Meeting Minutes===<br />
[https://docs.google.com/document/d/1iuSvaC9Wu-v7dToRp41IwmpdpQ0KtSTJIgpabmiolXQ/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1rXJuYE684ZpYbRyHknn4pmLpJZ9Y5o01QaJT34TD0gY/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1Gy7TOJr9aeyd8pcU_loabY1l3NByVm3nVKqOQnnJRbM/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1DGrSXaCTOtRL_iSOaOI_mHC2DOS7z4Vi6clzomkGkcI/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1VLEizDPdae_enbEtoHo9IGPM4-k9JXe7RFJ1hhiDTBA/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/13MyE--Ymz-dNiQPvgCjGutL23JZwotnoIPlYw7QqmXQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1UUDCW8YMttW2rwAxLJhSfqccBdedYoofVskc9qerIxU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/17QEpHsvitqzO9BO9MkB42umN3_9k6Useli4N2fYoCNU/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1masrY10EdoXrAdwmTnW-POF0RVEYGeHbOorf-0EEC-0/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1u2jcuwSkGqk4lGcGdF4UriFgzT9dNgNAb1ekERDvitQ/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1eHVDrzwLxkGhrElcgPUOWhcQBwLdGdXcmCVvT_u-Va8/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]<br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Testing</font></div>=<br />
==Test Cases==<br />
[https://dl.dropbox.com/u/56071797/Test%20Cases.docx |<font color="#CD004E"><b>Test Cases</b></font>]<br />
<br />
==Test Plans==<br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2001_17_10_2012.docx <font color="#CD004E"><b>Test Plan 1 ''on 17 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2002_28_09_2012.docx <font color="#CD004E"><b>Test Plan 2 ''on 28 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2003_19_10_2012.docx <font color="#CD004E"><b>Test Plan 3 ''on 19 October 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2004_01_11_2012.docx <font color="#CD004E"><b>Test Plan 4 ''on 4 November 2012''</b></font>]<br />
<br />
==User Testing==<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #728FCE; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing|<font color="#CD004E"><b>User Testing 1</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing|<font color="#CD004E"><b>User Testing 2</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing|<font color="#CD004E"><b>User Testing 3</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing|<font color="#CD004E"><b>User Testing 4</b></font>]]<br />
<br />
|}<br />
===User Testing 4===<br />
[[Image:6bituser-testing4.png]]<br />
<br />
====Test Description====<br />
The objective of User Test 4 is on scalability, performance and analytics testing of the system. This is a 2-part test session, firstly on scalability and performance which does not require physical testers, and secondly on inter-rater reliability which requires rating judges.<br />
<br><br><br />
The coverage of the scalability and performance test is focused on the bottleneck functions, which are the discussion forums and marketplace. The terms “performance” and “scalability” are commonly used interchangeably, but the two are distinct: performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. <br />
<br><br><br />
Additionally, Inter-Rater Reliability Test is performed on the Personalized Dashboard to determine the concordance of the personalized results and actual personality of user stereotypes.<br />
<br />
====Testers Background====<br />
=====Scalability & Performance Testing=====<br />
As the test does not require physical testers, the following appends the test environment.<br><br />
[[Image:6-bit_ut4spec.png|400px]]<br />
<br />
=====Inter-Rater Reliability Test=====<br />
Testers will assume the role of raters or judges for our Inter-Rater Reliability Test, represented by a total of 20 people with a 50-50 male is to female ratio. Testers are stratified from a diverse background, intended to represent personality stereotypes designed.<br />
<br><br><br />
Personality stereotypes include characteristics such as gender, age group, education, personality traits, online activity, mobility and interested topics.<br />
<br />
====Test Groups====<br />
There is no test grouping employed in this test.<br />
<br />
====Test Procedures====<br />
=====Scalability & Performance Testing=====<br />
The first part of the test is on scalability and performance testing. Chapalang Benchmark is configured to measure the time taken for each controller method before it starts and as soon as it ends. The results will be used to study the performance of the system and application at different scales of operations. <br />
<br><br><br />
Additionally, custom application is used to perform a series of activities on a forum and marketplace, simulating an arbitrary number of concurrent users on the system, or the load. <br />
<br><br />
<br><br />
Subsequently, we will study the benchmark timing data to understand the performance differences under different load.<br />
=====Inter-Rater Reliability Test=====<br />
An Inter-Rater Reliability (IRR) is the degree of agreement among raters. It gives a score of how much homogeneity or consensus there is in the ratings given by judges.<br />
<br><br><br />
The first rater is the system itself, which will generate a list of 10 products and 10 discussion topics recommendations in descending order of relevance to a target user. Every recommendation is tied to a specific and distinct order number.<br />
<br><br><br />
The second rater is a human tester, who will be provided with the same list of 10 products and 10 discussion topics generated by the system in relevance to him or herself. To mitigate the effects of Experimenter’s Bias, the order of each item is unordered and randomized without any intended logic. The second rater is expected to reorder the items according to his or her preferences in descending order.<br />
<br><br><br />
Subsequently, we will make use of Spearman’s Rank Correlation Coefficient to understand the reliability of our personalized dashboard which features product and topic recommendations.<br />
<br />
====Test Instruction====<br />
=====Inter-Rater Reliability Test=====<br />
This is a sample output of the first rater, for a product recommendation test.<br />
<br><br />
[[Image:6-bit_ut4a.png|750px]]<br />
<br><br />
This is a sample input sheet for the second rater, on product recommendation test.<br />
<br><br />
[[Image:6-bit_ut4b.png|750px]]<br />
<br><br />
In a descending order, 1 represents the most relevant item while 10 represents the least relevant item.<br />
<br />
====Test Results====<br />
=====Scalability & Performance Test=====<br />
The terms “performance” and “scalability” are commonly used interchangeably, but the two are distinct: performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. <br />
*(a) Identification of activities<br />
*(b) Identification of bottleneck<br />
*(c) Measurement of result of single user<br />
*(d) Maximum number of concurrent user, while maintaining single user performance<br />
*(e) Results of 1, 50, 100, 200, 400 users<br />
<br />
=====Inter-Rater Reliability Test=====<br />
In order to evaluate the test results, we rely on the statistical model called Spearman’s Rank Correlation Coefficient (SRCC). The model is appended below:<br />
<br><br />
[[Image: 6bituser-testing4formula.png]]<br />
<br><br />
In short, the SRCC model takes into account the rank rating from 2 different raters, represented by xi and yi respectively. In conventional Correlation of determination model, it takes in absolute data instead to find out statistical and data-driven correlation between 2 inputs. <br />
<br><br />
<br><br />
However, we are interested in the consensus between human judgment on the data, therefore SRCC is a suitable model of analysis. <br />
The SRCC model assumes that the rating scale is ordinal, or basically serial scale of rating. This assumption is aligned with our 1 – 10 rating score which is incremental and serial. Additionally, the SRCC model considers only relative position of the ratings. For example, (1, 2, 1, 3) is considered perfectly correlated with (2, 3, 2, 4). This is acceptable in our test because each rating in our test is distinct and exhaustive, where no repeats or unused score is allowed.<br />
<br> <br><br />
The following is a sample of data tabulation in visual form.<br />
<br><br />
[[Image: 6bituser-testing4z.png]]<br />
<br><br />
With [[Image: 6bituser-testing4di2.png]] found, we can add them to find [[Image: 6bituser-testing4sumdi2.png]] 28. The value of n is 10. So these values can now be substituted back into the equation, we evaluate that p = 0.83.<br />
<br><br />
Based on the nature of correlation coefficient value p, it has a range between -1 to 1. Here are some of the characteristics of the p value.<br />
<br><br />
* A negative number suggests negative relationship, <br />
* A positive number suggests positive relationship, <br />
* A size of a positive or negative number closer to 1 or -1 suggests strength of relationship,<br />
* and A p value of 0 suggests an absolute lack of relationship in the input attributes.<br />
<br />
It should be noted that if there is a strongly negative correlation, it may suggest a reversal in the order of recommendations in our system may eventually become an ideal model.<br />
<br><br />
The accuracy sentimental analysis system is, in principle, how well it agrees with human judgment, despite the fact that the applied accuracy in our test is to ensure an optimal user experience and optimal sales exposure. <br><br />
However, the limitation of the model is that human raters typically agree about 70% of the time and even if a system is 100% accurate by assumption, humans will still disagree about 30% of the time. Hence, for the purpose of our study, it may be suggested that an application with 100% human agreeableness can only be statistically justified to be 70% accurate and more sophisticated methods should be used to endorse the remaining 30% of accuracy. <br><br><br />
After conducting the IRR Test, the results are tabulated and appended as follows.<br />
<br><br />
[[Image: 6bituser-testing4results.png]]<br />
<br><br />
Tester IDs that begins with M denotes male testers, while F denotes Female testers. The categorization of results will help us understand a basic level of stereotyping accuracy by gender. If need it, the results can be further drilled down to represent a more specific personality stereotype.<br />
<br><br><br />
Summarising the test results tabulated above, the average for median p-value for male is 0.8695 and median p-value for female is 0.8675. Based on the median values, there is no significant difference in accuracy for male and females. In addition, it is satisfactorily justified that there is a strong positive correlation between the recommendations of our system and the preferences of the testers, a sample from our potential users, based on their consensus.<br />
<br />
<br />
<br />
<br />
<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Milestones</font></div>=<br />
<br />
[[Image:6-bit_schedule.png|600px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule Metric</font></div>=<br />
Every iteration, schedule metric values are calculated to understand the project progress. They are broadly categorized into 5 different groups, where different action plans will apply. The acceptable range of value is within 90% to 110%, offering some buffer for natural inaccuracies between forecasting and execution.<br />
<br><br><br />
Total Schedule Metric Value = Planned no. of days taken (P) / Actual no. of Days Assigned (A) x 100%<br />
<br><br><br />
[[Image:6-bit_schedulemetric.png|center|600px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Bug Metric</font></div>=<br />
==Log==<br />
[[Image:6-bit_BugMetric.png|550px]]<br />
[[Image:6-bit_BugLog.png|600px]]<br />
<div style="text-align: right;"><br />
Bug Log: [https://docs.google.com/spreadsheet/ccc?key=0Aqd6IiSLbMwQdEI5TldNSEhpcVRjb1puYzU3ZHJOckE |<font color="#CD004E"><b>Click Here</b></font>]<br />
</div><br />
<br><br />
Bug logging for Chapalang! takes the direction of being practical and easily monitored from both macro and micro perspectives. Whenever a bug is found, a new row is entered with the following data:<br />
* Index number<br />
* Bug description<br />
* Found by<br />
* Found date<br />
* Expected solve-by date<br />
* Bug severity<br />
* Status<br />
* Owner of the function<br />
* Fixed date<br />
* Closed by (Tester)<br />
* Close date<br />
* Additional comments<br />
==Metric==<br />
Bugs are classified into 3 different categories of complexity, easy, moderate and hard. Each category is assigned points of 1, 5 and 10 respectively, lower is better.<br />
<br><br><br />
Total Points for Each Iteration = Σ Points of the Bugs in each iteration<br />
<br><br />
[[Image:6-bit_BugMetricFormula.png|500px|center]]<br />
<br><br />
After assigning each bug with points associated by its complexity, we will track the total bug scores at the end of each week before deciding if there should be any actions to be taken. The following is an action plan for our bug metric:<br />
<br><br />
[[Image:6-bit_BugMetricFormula2.png|500px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Risk & Mitigation</font></div>=<br />
<br><br />
[[Image:6-bit_RiskDiagram.png|600px]]<br />
<br><br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4&diff=114334IS480 Team wiki: 2012T1 6-bit Project Management UT42012-12-03T12:54:35Z<p>Huiling.ong.2010: /* Scalability & Performance Test */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule</font></div>=<br />
==Planned Schedule==<br />
[[Image:6-bit_ScheduleDiagramOverview.png|left|750px|link=""]]<br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
==Meeting Minutes==<br />
===Team Meeting Minutes===<br />
{|<br />
|[[https://docs.google.com/document/d/1nHl51M2qzY4gynJ8tVR6wKqV_lWtJtncl3nbESSnQvU/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]]<br />
|[[https://docs.google.com/document/d/129JDPU8l7PbX-JjferJ-J83JXSIAo5-cXM4_Odw3o5c/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]]<br />
|[[https://docs.google.com/document/d/1BPn6a-XMMAN18TbdlDER27f8Eleb8sUJhcas1bgDOQI/edit |<font color="#CD004E"><b>Meeting Minute 21</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LtSANlI6pDyV_PpGDAVg85PjFVKmDmWWnYC5lXAHh68/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qx6hX462uQDEfwiB3r3ee71eTKaPXSArCZS7y1TOWA4/edit |<font color="#CD004E"><b>Meeting Minute 12</b></font>]]<br />
|[[https://docs.google.com/document/d/1IdjkCbomLgszePgImX2XsTeUHX54e54xRTIjjFoZM6g/edit |<font color="#CD004E"><b>Meeting Minute 22</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/11lQzKaddghH7FHACcTnPQDJnE6ZaScT8Q8nU2YvH8gU/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]]<br />
|[[https://docs.google.com/document/d/1HPdXr28aTDK-RmijqPYTLG1iCUv-JbpkIJ8zzgzTplg/edit |<font color="#CD004E"><b>Meeting Minute 13</b></font>]]<br />
|[[https://docs.google.com/document/d/1gMoTceQakeT42-FO0duVxRajea2hJAUVw8Eu1AfqtfY/edit |<font color="#CD004E"><b>Meeting Minute 23</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1gZuhKW-QMbhUR_oh6Ty8EE17JTYkTFkWCfG6UHrU7-c/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]]<br />
|[[https://docs.google.com/document/d/1ii-ZenbOTZR9drEQCFJ4hX8raXvpgufELaZY80M2GYI/edit |<font color="#CD004E"><b>Meeting Minute 14</b></font>]]<br />
|[[https://docs.google.com/document/d/12vYfm8jo9c2eZ3VwnL2z6vn6l__D6heDhCHdEWVPg4I/edit |<font color="#CD004E"><b>Meeting Minute 24</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1H-8fODLc79U6-IXScSfemjRLOyjvzC6_k0aig6BDcBY/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]]<br />
|[[https://docs.google.com/document/d/1I3qlvujdLVmY_L22VMsKrtISIFI5CnxmtZnMNdJdxfc/edit |<font color="#CD004E"><b>Meeting Minute 15</b></font>]]<br />
|[[https://docs.google.com/document/d/1jPIW-xe7p6kjzGF_YMmk0K2mPzWil1zUfBQOwGc8wRk/edit |<font color="#CD004E"><b>Meeting Minute 25</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Qx4jdRZoE8hXv3u1R4dWke5b-kyMxIc7ASzPIh4ShRQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]]<br />
|[[https://docs.google.com/document/d/1Pcd6ZADI7ZEuXzq3exrss4nJQhotxAq7-ENfy_OVs6o/edit |<font color="#CD004E"><b>Meeting Minute 16</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1uSkv_cux0PqnRTKS-w72wQLgL1ZKaCpXhzDm5uamfMU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]]<br />
|[[https://docs.google.com/document/d/12jW-ycBkfivYL2pg7nrVvb9SF7_XmiglVGGnWAjp6uQ/edit |<font color="#CD004E"><b>Meeting Minute 17</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1pTivyZ9D3jSU1Kf5VoW4-Xl_C9Abg-fL_6SI6GP_hz0/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qbhow5u8GsE42hr9b8o1S2HNeJfG5PTX24W70ZHyCfI/edit |<font color="#CD004E"><b>Meeting Minute 18</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LTLnY5JN2EfiU9drp3d7zGmoCxsSYr1nL4UMvwfXDdU/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]]<br />
|[[https://docs.google.com/document/d/1fbnoWNTimFyUC01lgeblvVCLTySS8Ik2JU_wdZ656RU/edit |<font color="#CD004E"><b>Meeting Minute 19</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Nlo5hnsYbfh4dFSnfsV6Wyv5nxJsmDWF8ZMFKFA9Pac/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]]<br />
|[[https://docs.google.com/document/d/1o1zVXcdHaXCLNzS9rHq528rLEmXMFl3df3ffTFLMtho/edit |<font color="#CD004E"><b>Meeting Minute 20</b></font>]]<br />
|}<br />
<br />
===Supervisor Meeting Minutes===<br />
[https://docs.google.com/document/d/1iuSvaC9Wu-v7dToRp41IwmpdpQ0KtSTJIgpabmiolXQ/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1rXJuYE684ZpYbRyHknn4pmLpJZ9Y5o01QaJT34TD0gY/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1Gy7TOJr9aeyd8pcU_loabY1l3NByVm3nVKqOQnnJRbM/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1DGrSXaCTOtRL_iSOaOI_mHC2DOS7z4Vi6clzomkGkcI/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1VLEizDPdae_enbEtoHo9IGPM4-k9JXe7RFJ1hhiDTBA/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/13MyE--Ymz-dNiQPvgCjGutL23JZwotnoIPlYw7QqmXQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1UUDCW8YMttW2rwAxLJhSfqccBdedYoofVskc9qerIxU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/17QEpHsvitqzO9BO9MkB42umN3_9k6Useli4N2fYoCNU/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1masrY10EdoXrAdwmTnW-POF0RVEYGeHbOorf-0EEC-0/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1u2jcuwSkGqk4lGcGdF4UriFgzT9dNgNAb1ekERDvitQ/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1eHVDrzwLxkGhrElcgPUOWhcQBwLdGdXcmCVvT_u-Va8/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]<br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Testing</font></div>=<br />
==Test Cases==<br />
[https://dl.dropbox.com/u/56071797/Test%20Cases.docx |<font color="#CD004E"><b>Test Cases</b></font>]<br />
<br />
==Test Plans==<br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2001_17_10_2012.docx <font color="#CD004E"><b>Test Plan 1 ''on 17 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2002_28_09_2012.docx <font color="#CD004E"><b>Test Plan 2 ''on 28 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2003_19_10_2012.docx <font color="#CD004E"><b>Test Plan 3 ''on 19 October 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2004_01_11_2012.docx <font color="#CD004E"><b>Test Plan 4 ''on 4 November 2012''</b></font>]<br />
<br />
==User Testing==<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #728FCE; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing|<font color="#CD004E"><b>User Testing 1</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing|<font color="#CD004E"><b>User Testing 2</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing|<font color="#CD004E"><b>User Testing 3</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing|<font color="#CD004E"><b>User Testing 4</b></font>]]<br />
<br />
|}<br />
===User Testing 4===<br />
[[Image:6bituser-testing4.png]]<br />
<br />
====Test Description====<br />
The objective of User Test 4 is on scalability, performance and analytics testing of the system. This is a 2-part test session, firstly on scalability and performance which does not require physical testers, and secondly on inter-rater reliability which requires rating judges.<br />
<br><br><br />
The coverage of the scalability and performance test is focused on the bottleneck functions, which are the discussion forums and marketplace. The terms “performance” and “scalability” are commonly used interchangeably, but the two are distinct: performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. <br />
<br><br><br />
Additionally, Inter-Rater Reliability Test is performed on the Personalized Dashboard to determine the concordance of the personalized results and actual personality of user stereotypes.<br />
<br />
====Testers Background====<br />
=====Scalability & Performance Testing=====<br />
As the test does not require physical testers, the following appends the test environment.<br><br />
[[Image:6-bit_ut4spec.png|400px]]<br />
<br />
=====Inter-Rater Reliability Test=====<br />
Testers will assume the role of raters or judges for our Inter-Rater Reliability Test, represented by a total of 20 people with a 50-50 male is to female ratio. Testers are stratified from a diverse background, intended to represent personality stereotypes designed.<br />
<br><br><br />
Personality stereotypes include characteristics such as gender, age group, education, personality traits, online activity, mobility and interested topics.<br />
<br />
====Test Groups====<br />
There is no test grouping employed in this test.<br />
<br />
====Test Procedures====<br />
=====Scalability & Performance Testing=====<br />
The first part of the test is on scalability and performance testing. Chapalang Benchmark is configured to measure the time taken for each controller method before it starts and as soon as it ends. The results will be used to study the performance of the system and application at different scales of operations. <br />
<br><br><br />
Additionally, custom application is used to perform a series of activities on a forum and marketplace, simulating an arbitrary number of concurrent users on the system, or the load. <br />
<br><br />
<br><br />
Subsequently, we will study the benchmark timing data to understand the performance differences under different load.<br />
=====Inter-Rater Reliability Test=====<br />
An Inter-Rater Reliability (IRR) is the degree of agreement among raters. It gives a score of how much homogeneity or consensus there is in the ratings given by judges.<br />
<br><br><br />
The first rater is the system itself, which will generate a list of 10 products and 10 discussion topics recommendations in descending order of relevance to a target user. Every recommendation is tied to a specific and distinct order number.<br />
<br><br><br />
The second rater is a human tester, who will be provided with the same list of 10 products and 10 discussion topics generated by the system in relevance to him or herself. To mitigate the effects of Experimenter’s Bias, the order of each item is unordered and randomized without any intended logic. The second rater is expected to reorder the items according to his or her preferences in descending order.<br />
<br><br><br />
Subsequently, we will make use of Spearman’s Rank Correlation Coefficient to understand the reliability of our personalized dashboard which features product and topic recommendations.<br />
<br />
====Test Instruction====<br />
=====Inter-Rater Reliability Test=====<br />
This is a sample output of the first rater, for a product recommendation test.<br />
<br><br />
[[Image:6-bit_ut4a.png|750px]]<br />
<br><br />
This is a sample input sheet for the second rater, on product recommendation test.<br />
<br><br />
[[Image:6-bit_ut4b.png|750px]]<br />
<br><br />
In a descending order, 1 represents the most relevant item while 10 represents the least relevant item.<br />
<br />
====Test Results====<br />
=====Scalability & Performance Test=====<br />
The terms “performance” and “scalability” are commonly used interchangeably, but the two are distinct: performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. <br />
*(a) Identification of activities<br />
*(b) Identification of bottleneck<br />
*(c) Measurement of result of single user<br />
*(d) Maximum number of concurrent user, while maintaining single user performance<br />
*(e) Results of 1, 50, 100, 200, 400 users<br />
<br />
=====Inter-Rater Reliability Test=====<br />
In order to evaluate the test results, we rely on the statistical model called Spearman’s Rank Correlation Coefficient (SRCC). The model is appended below:<br />
<br><br />
[[Image: 6bituser-testing4formula.png]]<br />
<br><br />
In short, the SRCC model takes into account the rank rating from 2 different raters, represented by xi and yi respectively. In conventional Correlation of determination model, it takes in absolute data instead to find out statistical and data-driven correlation between 2 inputs. <br />
<br><br />
<br><br />
However, we are interested in the consensus between human judgment on the data, therefore SRCC is a suitable model of analysis. <br />
The SRCC model assumes that the rating scale is ordinal, or basically serial scale of rating. This assumption is aligned with our 1 – 10 rating score which is incremental and serial. Additionally, the SRCC model considers only relative position of the ratings. For example, (1, 2, 1, 3) is considered perfectly correlated with (2, 3, 2, 4). This is acceptable in our test because each rating in our test is distinct and exhaustive, where no repeats or unused score is allowed.<br />
<br> <br><br />
The following is a sample of data tabulation in visual form.<br />
<br><br />
[[Image: 6bituser-testing4z.png]]<br />
<br><br />
With [[Image: 6bituser-testing4di2.png]] found, we can add them to find [[Image: 6bituser-testing4sumdi2.png]] 28. The value of n is 10. So these values can now be substituted back into the equation, we evaluate that p = 0.83.<br />
<br><br />
Based on the nature of correlation coefficient value p, it has a range between -1 to 1. Here are some of the characteristics of the p value.<br />
<br><br />
* A negative number suggests negative relationship, <br />
* A positive number suggests positive relationship, <br />
* A size of a positive or negative number closer to 1 or -1 suggests strength of relationship,<br />
* and A p value of 0 suggests an absolute lack of relationship in the input attributes.<br />
<br />
It should be noted that if there is a strongly negative correlation, it may suggest a reversal in the order of recommendations in our system may eventually become an ideal model.<br />
<br><br />
The accuracy sentimental analysis system is, in principle, how well it agrees with human judgment, despite the fact that the applied accuracy in our test is to ensure an optimal user experience and optimal sales exposure. <br><br />
However, the limitation of the model is that human raters typically agree about 70% of the time and even if a system is 100% accurate by assumption, humans will still disagree about 30% of the time. Hence, for the purpose of our study, it may be suggested that an application with 100% human agreeableness can only be statistically justified to be 70% accurate and more sophisticated methods should be used to endorse the remaining 30% of accuracy. <br><br><br />
After conducting the IRR Test, the results are tabulated and appended as follows.<br />
<br><br />
[[Image: 6bituser-testing4results.png]]<br />
<br><br />
Tester IDs that begins with M denotes male testers, while F denotes Female testers. The categorization of results will help us understand a basic level of stereotyping accuracy by gender. If need it, the results can be further drilled down to represent a more specific personality stereotype.<br />
<br><br><br />
Summarising the test results tabulated above, the average for median p-value for male is 0.8695 and median p-value for female is 0.8675. Based on the median values, there is no significant difference in accuracy for male and females. In addition, it is satisfactorily justified that there is a strong positive correlation between the recommendations of our system and the preferences of the testers, a sample from our potential users, based on their consensus.<br />
<br />
<br />
<br />
<br />
====Click Data Analysis (Group A vs. Group B – Marketplace Functions)====<br />
Prospectively, we will also study the user experience difference between Group A and Group B testers on marketplace functions, based on the click data which measures the number of clicks involved per task and time taken in seconds between each task.<br />
<br><br><br />
In the box-plot diagram above, UT2A refers to User Test 2 Group A testers, while UT2B refers to User Test 2 Group B testers. Each box-plot is represented by data of a specific group of users, and the results computed based on the number of clicks of time pertaining to forum or marketplace functions.<br />
<br><br />
[[Image: 6bituser-testing2cda3.png]]<br />
<br><br />
Comparing marketplace functions, both Group A and Group B testers have made a median of 2 clicks to accomplish each task. While Group B testers have a wider variance of clicks of up to 4 clicks, it can be broadly attributed to outliers, user experiments or some learning curve involved in getting used to the functions or interface objects placements. <br />
<br><br />
[[Image: 6bituser-testing2cda4.png]]<br />
<br><br />
The result when comparing the time taken is consistent with the preliminary conclusion when comparing the number of clicks per task. The median time taken for Group A and Group B testers for forum and marketplace functions are within the range of 4 to 5 seconds. The difference between the median records is insignificant.<br />
<br><br><br />
Overall, the result is consistent across forums and marketplace functions, between testers from both User Tests and test groups. It is also consistent with our earlier preliminary conclusion that the improvements made between the two User Tests have resulted in improved user experience, and there is a good level of learnability in the interface design.<br />
<br><br><br />
While there are limitations in this test, where there are other externalities such as network performance, computing habits of testers and response time of each users, the macro results of the test provide a reasonable sampling on the objective of the test.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Milestones</font></div>=<br />
<br />
[[Image:6-bit_schedule.png|600px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule Metric</font></div>=<br />
Every iteration, schedule metric values are calculated to understand the project progress. They are broadly categorized into 5 different groups, where different action plans will apply. The acceptable range of value is within 90% to 110%, offering some buffer for natural inaccuracies between forecasting and execution.<br />
<br><br><br />
Total Schedule Metric Value = Planned no. of days taken (P) / Actual no. of Days Assigned (A) x 100%<br />
<br><br><br />
[[Image:6-bit_schedulemetric.png|center|600px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Bug Metric</font></div>=<br />
==Log==<br />
[[Image:6-bit_BugMetric.png|550px]]<br />
[[Image:6-bit_BugLog.png|600px]]<br />
<div style="text-align: right;"><br />
Bug Log: [https://docs.google.com/spreadsheet/ccc?key=0Aqd6IiSLbMwQdEI5TldNSEhpcVRjb1puYzU3ZHJOckE |<font color="#CD004E"><b>Click Here</b></font>]<br />
</div><br />
<br><br />
Bug logging for Chapalang! takes the direction of being practical and easily monitored from both macro and micro perspectives. Whenever a bug is found, a new row is entered with the following data:<br />
* Index number<br />
* Bug description<br />
* Found by<br />
* Found date<br />
* Expected solve-by date<br />
* Bug severity<br />
* Status<br />
* Owner of the function<br />
* Fixed date<br />
* Closed by (Tester)<br />
* Close date<br />
* Additional comments<br />
==Metric==<br />
Bugs are classified into 3 different categories of complexity, easy, moderate and hard. Each category is assigned points of 1, 5 and 10 respectively, lower is better.<br />
<br><br><br />
Total Points for Each Iteration = Σ Points of the Bugs in each iteration<br />
<br><br />
[[Image:6-bit_BugMetricFormula.png|500px|center]]<br />
<br><br />
After assigning each bug with points associated by its complexity, we will track the total bug scores at the end of each week before deciding if there should be any actions to be taken. The following is an action plan for our bug metric:<br />
<br><br />
[[Image:6-bit_BugMetricFormula2.png|500px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Risk & Mitigation</font></div>=<br />
<br><br />
[[Image:6-bit_RiskDiagram.png|600px]]<br />
<br><br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3&diff=114333IS480 Team wiki: 2012T1 6-bit Project Management UT32012-12-03T12:53:51Z<p>Huiling.ong.2010: /* Testers Background */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule</font></div>=<br />
==Planned Schedule==<br />
[[Image:6-bit_ScheduleDiagramOverview.png|left|750px|link=""]]<br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
==Meeting Minutes==<br />
===Team Meeting Minutes===<br />
{|<br />
|[[https://docs.google.com/document/d/1nHl51M2qzY4gynJ8tVR6wKqV_lWtJtncl3nbESSnQvU/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]]<br />
|[[https://docs.google.com/document/d/129JDPU8l7PbX-JjferJ-J83JXSIAo5-cXM4_Odw3o5c/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]]<br />
|[[https://docs.google.com/document/d/1BPn6a-XMMAN18TbdlDER27f8Eleb8sUJhcas1bgDOQI/edit |<font color="#CD004E"><b>Meeting Minute 21</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LtSANlI6pDyV_PpGDAVg85PjFVKmDmWWnYC5lXAHh68/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qx6hX462uQDEfwiB3r3ee71eTKaPXSArCZS7y1TOWA4/edit |<font color="#CD004E"><b>Meeting Minute 12</b></font>]]<br />
|[[https://docs.google.com/document/d/1IdjkCbomLgszePgImX2XsTeUHX54e54xRTIjjFoZM6g/edit |<font color="#CD004E"><b>Meeting Minute 22</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/11lQzKaddghH7FHACcTnPQDJnE6ZaScT8Q8nU2YvH8gU/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]]<br />
|[[https://docs.google.com/document/d/1HPdXr28aTDK-RmijqPYTLG1iCUv-JbpkIJ8zzgzTplg/edit |<font color="#CD004E"><b>Meeting Minute 13</b></font>]]<br />
|[[https://docs.google.com/document/d/1gMoTceQakeT42-FO0duVxRajea2hJAUVw8Eu1AfqtfY/edit |<font color="#CD004E"><b>Meeting Minute 23</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1gZuhKW-QMbhUR_oh6Ty8EE17JTYkTFkWCfG6UHrU7-c/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]]<br />
|[[https://docs.google.com/document/d/1ii-ZenbOTZR9drEQCFJ4hX8raXvpgufELaZY80M2GYI/edit |<font color="#CD004E"><b>Meeting Minute 14</b></font>]]<br />
|[[https://docs.google.com/document/d/12vYfm8jo9c2eZ3VwnL2z6vn6l__D6heDhCHdEWVPg4I/edit |<font color="#CD004E"><b>Meeting Minute 24</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1H-8fODLc79U6-IXScSfemjRLOyjvzC6_k0aig6BDcBY/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]]<br />
|[[https://docs.google.com/document/d/1I3qlvujdLVmY_L22VMsKrtISIFI5CnxmtZnMNdJdxfc/edit |<font color="#CD004E"><b>Meeting Minute 15</b></font>]]<br />
|[[https://docs.google.com/document/d/1jPIW-xe7p6kjzGF_YMmk0K2mPzWil1zUfBQOwGc8wRk/edit |<font color="#CD004E"><b>Meeting Minute 25</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Qx4jdRZoE8hXv3u1R4dWke5b-kyMxIc7ASzPIh4ShRQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]]<br />
|[[https://docs.google.com/document/d/1Pcd6ZADI7ZEuXzq3exrss4nJQhotxAq7-ENfy_OVs6o/edit |<font color="#CD004E"><b>Meeting Minute 16</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1uSkv_cux0PqnRTKS-w72wQLgL1ZKaCpXhzDm5uamfMU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]]<br />
|[[https://docs.google.com/document/d/12jW-ycBkfivYL2pg7nrVvb9SF7_XmiglVGGnWAjp6uQ/edit |<font color="#CD004E"><b>Meeting Minute 17</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1pTivyZ9D3jSU1Kf5VoW4-Xl_C9Abg-fL_6SI6GP_hz0/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qbhow5u8GsE42hr9b8o1S2HNeJfG5PTX24W70ZHyCfI/edit |<font color="#CD004E"><b>Meeting Minute 18</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LTLnY5JN2EfiU9drp3d7zGmoCxsSYr1nL4UMvwfXDdU/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]]<br />
|[[https://docs.google.com/document/d/1fbnoWNTimFyUC01lgeblvVCLTySS8Ik2JU_wdZ656RU/edit |<font color="#CD004E"><b>Meeting Minute 19</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Nlo5hnsYbfh4dFSnfsV6Wyv5nxJsmDWF8ZMFKFA9Pac/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]]<br />
|[[https://docs.google.com/document/d/1o1zVXcdHaXCLNzS9rHq528rLEmXMFl3df3ffTFLMtho/edit |<font color="#CD004E"><b>Meeting Minute 20</b></font>]]<br />
|}<br />
<br />
===Supervisor Meeting Minutes===<br />
[https://docs.google.com/document/d/1iuSvaC9Wu-v7dToRp41IwmpdpQ0KtSTJIgpabmiolXQ/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1rXJuYE684ZpYbRyHknn4pmLpJZ9Y5o01QaJT34TD0gY/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1Gy7TOJr9aeyd8pcU_loabY1l3NByVm3nVKqOQnnJRbM/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1DGrSXaCTOtRL_iSOaOI_mHC2DOS7z4Vi6clzomkGkcI/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1VLEizDPdae_enbEtoHo9IGPM4-k9JXe7RFJ1hhiDTBA/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/13MyE--Ymz-dNiQPvgCjGutL23JZwotnoIPlYw7QqmXQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1UUDCW8YMttW2rwAxLJhSfqccBdedYoofVskc9qerIxU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/17QEpHsvitqzO9BO9MkB42umN3_9k6Useli4N2fYoCNU/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1masrY10EdoXrAdwmTnW-POF0RVEYGeHbOorf-0EEC-0/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1u2jcuwSkGqk4lGcGdF4UriFgzT9dNgNAb1ekERDvitQ/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1eHVDrzwLxkGhrElcgPUOWhcQBwLdGdXcmCVvT_u-Va8/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]<br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Testing</font></div>=<br />
==Test Cases==<br />
[https://dl.dropbox.com/u/56071797/Test%20Cases.docx |<font color="#CD004E"><b>Test Cases</b></font>]<br />
<br />
==Test Plans==<br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2001_17_10_2012.docx <font color="#CD004E"><b>Test Plan 1 ''on 17 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2002_28_09_2012.docx <font color="#CD004E"><b>Test Plan 2 ''on 28 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2003_19_10_2012.docx <font color="#CD004E"><b>Test Plan 3 ''on 19 October 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2004_01_11_2012.docx <font color="#CD004E"><b>Test Plan 4 ''on 4 November 2012''</b></font>]<br />
<br />
==User Testing==<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #728FCE; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing|<font color="#CD004E"><b>User Testing 1</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing|<font color="#CD004E"><b>User Testing 2</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing|<font color="#CD004E"><b>User Testing 3</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing|<font color="#CD004E"><b>User Testing 4</b></font>]]<br />
<br />
|}<br />
===User Testing 3===<br />
[[Image:6bituser-testing3.png]]<br />
<br />
====Test Description====<br />
The objective of User Test 3 is on functionality and usability testing of the system. The coverage of the test is focused on the key features of the system which is Private Message, Escrow, Gift Sharing and Mass Order. <br><br><br />
The purpose of the test is to test that the system is functioning according to design, and/or to spot any bugs or anomalies not detected by the team. The test also seeks to collect inputs on possible enhancements or improvements preferred by the sampled group of testers.<br />
<br />
====Testers Background====<br />
There are a total of 30 testers who attended the User Test, of which 70% (21) are male and 30% (9) are female, representing various schools in SMU with SIS students being the majority. It is also observed that most testers are users of Chrome and Firefox web browser.<br />
<br><br />
There is no significant difference between testers’ background in User Test 1, 2 and 3.<br />
<br><br />
[[Image:6bituser-testing3results.png|center]]<br />
<br />
====Test Groups====<br />
There are 2 test groups employed in this test.<br />
<br><br><br />
Group A consists of 15 testers who are guided by an instruction sheet on a series of tasks to be tested. The purpose of this group is to test the system by a set of test case based on the design of the system.<br />
<br><br />
Group B consists of 15 testers who are unguided, and encouraged to explore the full system seeking for any uncommon encounters in their experience. The purpose of this group is to test the system in the role of a random user who may explore use-cases or sequence of activities not intended by design but possible by usage.<br />
<br />
====Test Procedures====<br />
Testers are invited to attend the User Test session and required to bring their own laptops. They are informed on the purpose of the test and given a brief description of the system objective of Chapalang!. <br />
<br><br><br />
Only testers from Group A are provided with the instruction sheet. Thereafter, both groups of testers will fill in details in an open-ended form, should they encounter any bugs or suggestions for improvements.<br />
<br />
====Test Instruction====<br />
[https://dl.dropbox.com/u/56071797/User%20Testing%203%20Instructions.docx Click Here to Download User Testing 3 Instruction]<br />
<br />
====Test Results====<br />
There are also 19 reported bugs, and 32 recommendations for improvements received. The following are the top 10 bugs reported.<br />
<br><br />
[[Image: 6bituser-testing3bug.png|600px]]<br />
<br><br />
Most of the recommendations are repeated from User Test 1 and 2, and hence will not be published.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Milestones</font></div>=<br />
<br />
[[Image:6-bit_schedule.png|600px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule Metric</font></div>=<br />
Every iteration, schedule metric values are calculated to understand the project progress. They are broadly categorized into 5 different groups, where different action plans will apply. The acceptable range of value is within 90% to 110%, offering some buffer for natural inaccuracies between forecasting and execution.<br />
<br><br><br />
Total Schedule Metric Value = Planned no. of days taken (P) / Actual no. of Days Assigned (A) x 100%<br />
<br><br><br />
[[Image:6-bit_schedulemetric.png|center|600px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Bug Metric</font></div>=<br />
==Log==<br />
[[Image:6-bit_BugMetric.png|550px]]<br />
[[Image:6-bit_BugLog.png|600px]]<br />
<div style="text-align: right;"><br />
Bug Log: [https://docs.google.com/spreadsheet/ccc?key=0Aqd6IiSLbMwQdEI5TldNSEhpcVRjb1puYzU3ZHJOckE |<font color="#CD004E"><b>Click Here</b></font>]<br />
</div><br />
<br><br />
Bug logging for Chapalang! takes the direction of being practical and easily monitored from both macro and micro perspectives. Whenever a bug is found, a new row is entered with the following data:<br />
* Index number<br />
* Bug description<br />
* Found by<br />
* Found date<br />
* Expected solve-by date<br />
* Bug severity<br />
* Status<br />
* Owner of the function<br />
* Fixed date<br />
* Closed by (Tester)<br />
* Close date<br />
* Additional comments<br />
==Metric==<br />
Bugs are classified into 3 different categories of complexity, easy, moderate and hard. Each category is assigned points of 1, 5 and 10 respectively, lower is better.<br />
<br><br><br />
Total Points for Each Iteration = Σ Points of the Bugs in each iteration<br />
<br><br />
[[Image:6-bit_BugMetricFormula.png|500px|center]]<br />
<br><br />
After assigning each bug with points associated by its complexity, we will track the total bug scores at the end of each week before deciding if there should be any actions to be taken. The following is an action plan for our bug metric:<br />
<br><br />
[[Image:6-bit_BugMetricFormula2.png|500px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Risk & Mitigation</font></div>=<br />
<br><br />
[[Image:6-bit_RiskDiagram.png|600px]]<br />
<br><br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2&diff=114332IS480 Team wiki: 2012T1 6-bit Project Management UT22012-12-03T12:52:37Z<p>Huiling.ong.2010: /* Testers Background */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule</font></div>=<br />
==Planned Schedule==<br />
[[Image:6-bit_ScheduleDiagramOverview.png|left|750px|link=""]]<br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
==Meeting Minutes==<br />
===Team Meeting Minutes===<br />
{|<br />
|[[https://docs.google.com/document/d/1nHl51M2qzY4gynJ8tVR6wKqV_lWtJtncl3nbESSnQvU/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]]<br />
|[[https://docs.google.com/document/d/129JDPU8l7PbX-JjferJ-J83JXSIAo5-cXM4_Odw3o5c/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]]<br />
|[[https://docs.google.com/document/d/1BPn6a-XMMAN18TbdlDER27f8Eleb8sUJhcas1bgDOQI/edit |<font color="#CD004E"><b>Meeting Minute 21</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LtSANlI6pDyV_PpGDAVg85PjFVKmDmWWnYC5lXAHh68/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qx6hX462uQDEfwiB3r3ee71eTKaPXSArCZS7y1TOWA4/edit |<font color="#CD004E"><b>Meeting Minute 12</b></font>]]<br />
|[[https://docs.google.com/document/d/1IdjkCbomLgszePgImX2XsTeUHX54e54xRTIjjFoZM6g/edit |<font color="#CD004E"><b>Meeting Minute 22</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/11lQzKaddghH7FHACcTnPQDJnE6ZaScT8Q8nU2YvH8gU/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]]<br />
|[[https://docs.google.com/document/d/1HPdXr28aTDK-RmijqPYTLG1iCUv-JbpkIJ8zzgzTplg/edit |<font color="#CD004E"><b>Meeting Minute 13</b></font>]]<br />
|[[https://docs.google.com/document/d/1gMoTceQakeT42-FO0duVxRajea2hJAUVw8Eu1AfqtfY/edit |<font color="#CD004E"><b>Meeting Minute 23</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1gZuhKW-QMbhUR_oh6Ty8EE17JTYkTFkWCfG6UHrU7-c/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]]<br />
|[[https://docs.google.com/document/d/1ii-ZenbOTZR9drEQCFJ4hX8raXvpgufELaZY80M2GYI/edit |<font color="#CD004E"><b>Meeting Minute 14</b></font>]]<br />
|[[https://docs.google.com/document/d/12vYfm8jo9c2eZ3VwnL2z6vn6l__D6heDhCHdEWVPg4I/edit |<font color="#CD004E"><b>Meeting Minute 24</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1H-8fODLc79U6-IXScSfemjRLOyjvzC6_k0aig6BDcBY/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]]<br />
|[[https://docs.google.com/document/d/1I3qlvujdLVmY_L22VMsKrtISIFI5CnxmtZnMNdJdxfc/edit |<font color="#CD004E"><b>Meeting Minute 15</b></font>]]<br />
|[[https://docs.google.com/document/d/1jPIW-xe7p6kjzGF_YMmk0K2mPzWil1zUfBQOwGc8wRk/edit |<font color="#CD004E"><b>Meeting Minute 25</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Qx4jdRZoE8hXv3u1R4dWke5b-kyMxIc7ASzPIh4ShRQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]]<br />
|[[https://docs.google.com/document/d/1Pcd6ZADI7ZEuXzq3exrss4nJQhotxAq7-ENfy_OVs6o/edit |<font color="#CD004E"><b>Meeting Minute 16</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1uSkv_cux0PqnRTKS-w72wQLgL1ZKaCpXhzDm5uamfMU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]]<br />
|[[https://docs.google.com/document/d/12jW-ycBkfivYL2pg7nrVvb9SF7_XmiglVGGnWAjp6uQ/edit |<font color="#CD004E"><b>Meeting Minute 17</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1pTivyZ9D3jSU1Kf5VoW4-Xl_C9Abg-fL_6SI6GP_hz0/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qbhow5u8GsE42hr9b8o1S2HNeJfG5PTX24W70ZHyCfI/edit |<font color="#CD004E"><b>Meeting Minute 18</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LTLnY5JN2EfiU9drp3d7zGmoCxsSYr1nL4UMvwfXDdU/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]]<br />
|[[https://docs.google.com/document/d/1fbnoWNTimFyUC01lgeblvVCLTySS8Ik2JU_wdZ656RU/edit |<font color="#CD004E"><b>Meeting Minute 19</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Nlo5hnsYbfh4dFSnfsV6Wyv5nxJsmDWF8ZMFKFA9Pac/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]]<br />
|[[https://docs.google.com/document/d/1o1zVXcdHaXCLNzS9rHq528rLEmXMFl3df3ffTFLMtho/edit |<font color="#CD004E"><b>Meeting Minute 20</b></font>]]<br />
|}<br />
<br />
===Supervisor Meeting Minutes===<br />
[https://docs.google.com/document/d/1iuSvaC9Wu-v7dToRp41IwmpdpQ0KtSTJIgpabmiolXQ/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1rXJuYE684ZpYbRyHknn4pmLpJZ9Y5o01QaJT34TD0gY/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1Gy7TOJr9aeyd8pcU_loabY1l3NByVm3nVKqOQnnJRbM/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1DGrSXaCTOtRL_iSOaOI_mHC2DOS7z4Vi6clzomkGkcI/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1VLEizDPdae_enbEtoHo9IGPM4-k9JXe7RFJ1hhiDTBA/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/13MyE--Ymz-dNiQPvgCjGutL23JZwotnoIPlYw7QqmXQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1UUDCW8YMttW2rwAxLJhSfqccBdedYoofVskc9qerIxU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/17QEpHsvitqzO9BO9MkB42umN3_9k6Useli4N2fYoCNU/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1masrY10EdoXrAdwmTnW-POF0RVEYGeHbOorf-0EEC-0/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1u2jcuwSkGqk4lGcGdF4UriFgzT9dNgNAb1ekERDvitQ/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1eHVDrzwLxkGhrElcgPUOWhcQBwLdGdXcmCVvT_u-Va8/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]<br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Testing</font></div>=<br />
==Test Cases==<br />
[https://dl.dropbox.com/u/56071797/Test%20Cases.docx |<font color="#CD004E"><b>Test Cases</b></font>]<br />
<br />
==Test Plans==<br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2001_17_10_2012.docx <font color="#CD004E"><b>Test Plan 1 ''on 17 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2002_28_09_2012.docx <font color="#CD004E"><b>Test Plan 2 ''on 28 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2003_19_10_2012.docx <font color="#CD004E"><b>Test Plan 3 ''on 19 October 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2004_01_11_2012.docx <font color="#CD004E"><b>Test Plan 4 ''on 4 November 2012''</b></font>]<br />
<br />
==User Testing==<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #728FCE; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing|<font color="#CD004E"><b>User Testing 1</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing|<font color="#CD004E"><b>User Testing 2</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing|<font color="#CD004E"><b>User Testing 3</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing|<font color="#CD004E"><b>User Testing 4</b></font>]]<br />
<br />
|}<br />
===User Testing 2===<br />
[[Image:6bituser-testing2.png]]<br />
<br />
====Test Description====<br />
The objective of User Test 2 is on functionality and usability testing of the system. The coverage of the test is focused on forum and basic marketplace functions. <br><br><br />
The purpose of re-testing on forum function is to test for an experience improvement. Basic marketplace functions will consist of a complete product display to payment process. We will want to find out if the changes made after User Test 1 is offering an improved user experience to users, and whether the improvement is consistent between forum and marketplace functions.<br />
<br />
====Testers Background====<br />
There are a total of 46 testers who attended the User Test, of which 61% (28) are male and 39% (18) are female, representing various schools in SMU with SIS students being the majority. It is also observed that most testers are users of Chrome and Firefox web browser.<br />
There is no significant difference between testers’ background in User Test 1 and 2.<br />
<br><br />
[[Image:6bituser-testing2results.png|center]]<br />
<br />
====Test Groups====<br />
There are 2 test groups employed in this test.<br />
<br><br><br />
Group A (Control Group) consists of 17 testers who were testers from User Test 1. The purpose is to test if their return experience with the system has any improvements.<br />
<br><br />
Group B (Test Group) consists of 29 new testers who have not participated in any of our previous user tests. The purpose of their participation is for comparison, to find out if they have a different experience from the returning testers in Group A.<br />
<br />
====Test Procedures====<br />
Testers are invited to attend the User Test session and required to bring their own laptops. They are informed on the purpose of the test and given a brief description of the system objective of Chapalang!. <br />
<br><br><br />
Subsequently, they are provided with an instruction sheet for a guided test experience. Testers will be required to perform a series of system tasks based on a test case that will go through all the system features and use-case. Thereafter, testers will fill in details in an open-ended textbox appended after each question, should they encounter any bugs or suggestions for improvements.<br />
<br />
====Test Instruction====<br />
[https://dl.dropbox.com/u/56071797/User%20Testing%202%20Instructions.docx Click Here to Download User Testing 2 Instruction]<br />
<br />
====Test Results====<br />
[[Image: 6bituser-testing2resultsfigure.png|250px]]<br />
<br><br />
Based on the survey questions, the results are positive with most testers having a good level of comfort using our web application.<br />
<br> <br><br />
There are also 21 reported bugs, and 69 recommendations for improvements received. The following are the top 10 bugs reported.<br />
<br><br />
[[Image: 6bituser-testing2bug.png|600px]]<br />
<br><br />
<br><br />
The top 10 most frequently mentioned or important recommendations will be published and appended below.<br />
<br><br />
[[Image: 6bituser-testing2recommendation.png|600px]]<br />
<br />
====Click Data Analysis(User Test 1 vs. User Test 2 – Forum Functions Only)====<br />
Additionally, click data of each test session has also been collected and analysed. They are also being compared to that with the results of User Test 1.<br><br />
[[Image: 6bituser-testing2cda1.png]]<br />
<br><br />
The above box-plot represents 3 sets of data comparing the number of clicks per task, for discussion forum functions only. UT1 represents the results from User Test 1, UT2A represents the results from Group A testers of User Test 2, while UT2B represents the results from Group B testers of User Test 2. For the objective of fair comparisons, the results from User Test 2 has been drilled down to consists of data<br />
<br><br><br />
The median number of clicks it takes per tester to accomplish a forum-related task in User Test 2 ranges from 1 to 3 clicks with 2 clicks being the median, a decrement from the median of 3 clicks, as well as a smaller variance as compared to User Test 1. Additionally, it can also be observed that there is no significant difference in the results between Group A and Group B users.<br />
<br><br><br />
Preliminary, we can observe an improvement in the user experience for Group A users between the 2 tests. The improvement can be broadly attributed to the improvements made as well as the high learnability of the system interface design. However, this observation is not conclusive and more data is required.<br />
<br><br />
[[Image: 6bituser-testing2cda2.png]]<br />
<br><br />
Additional statistics were computer and observed that the median time spent to accomplish a forum-related task for Group A tester is 4 seconds, and Group B tester is 5 seconds. Again, this is a significant decrement in the time spent from User Test 1, where testers spent a median of 10 seconds between each task. <br />
Based on the finding, we can reasonably derive that there is an improved user experience between User Test 1 and User Test 2, attributing to the improvements made and high learnability of the system. In addition, the improved user experience is shared between both Group A and Group B users, possibly suggesting that the improved system does not require much training or high learning curve.<br />
====Click Data Analysis (Group A vs. Group B – Marketplace Functions)====<br />
Prospectively, we will also study the user experience difference between Group A and Group B testers on marketplace functions, based on the click data which measures the number of clicks involved per task and time taken in seconds between each task.<br />
<br><br><br />
In the box-plot diagram above, UT2A refers to User Test 2 Group A testers, while UT2B refers to User Test 2 Group B testers. Each box-plot is represented by data of a specific group of users, and the results computed based on the number of clicks of time pertaining to forum or marketplace functions.<br />
<br><br />
[[Image: 6bituser-testing2cda3.png]]<br />
<br><br />
Comparing marketplace functions, both Group A and Group B testers have made a median of 2 clicks to accomplish each task. While Group B testers have a wider variance of clicks of up to 4 clicks, it can be broadly attributed to outliers, user experiments or some learning curve involved in getting used to the functions or interface objects placements. <br />
<br><br />
[[Image: 6bituser-testing2cda4.png]]<br />
<br><br />
The result when comparing the time taken is consistent with the preliminary conclusion when comparing the number of clicks per task. The median time taken for Group A and Group B testers for forum and marketplace functions are within the range of 4 to 5 seconds. The difference between the median records is insignificant.<br />
<br><br><br />
Overall, the result is consistent across forums and marketplace functions, between testers from both User Tests and test groups. It is also consistent with our earlier preliminary conclusion that the improvements made between the two User Tests have resulted in improved user experience, and there is a good level of learnability in the interface design.<br />
<br><br><br />
While there are limitations in this test, where there are other externalities such as network performance, computing habits of testers and response time of each users, the macro results of the test provide a reasonable sampling on the objective of the test.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Milestones</font></div>=<br />
<br />
[[Image:6-bit_schedule.png|600px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule Metric</font></div>=<br />
Every iteration, schedule metric values are calculated to understand the project progress. They are broadly categorized into 5 different groups, where different action plans will apply. The acceptable range of value is within 90% to 110%, offering some buffer for natural inaccuracies between forecasting and execution.<br />
<br><br><br />
Total Schedule Metric Value = Planned no. of days taken (P) / Actual no. of Days Assigned (A) x 100%<br />
<br><br><br />
[[Image:6-bit_schedulemetric.png|center|600px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Bug Metric</font></div>=<br />
==Log==<br />
[[Image:6-bit_BugMetric.png|550px]]<br />
[[Image:6-bit_BugLog.png|600px]]<br />
<div style="text-align: right;"><br />
Bug Log: [https://docs.google.com/spreadsheet/ccc?key=0Aqd6IiSLbMwQdEI5TldNSEhpcVRjb1puYzU3ZHJOckE |<font color="#CD004E"><b>Click Here</b></font>]<br />
</div><br />
<br><br />
Bug logging for Chapalang! takes the direction of being practical and easily monitored from both macro and micro perspectives. Whenever a bug is found, a new row is entered with the following data:<br />
* Index number<br />
* Bug description<br />
* Found by<br />
* Found date<br />
* Expected solve-by date<br />
* Bug severity<br />
* Status<br />
* Owner of the function<br />
* Fixed date<br />
* Closed by (Tester)<br />
* Close date<br />
* Additional comments<br />
==Metric==<br />
Bugs are classified into 3 different categories of complexity, easy, moderate and hard. Each category is assigned points of 1, 5 and 10 respectively, lower is better.<br />
<br><br><br />
Total Points for Each Iteration = Σ Points of the Bugs in each iteration<br />
<br><br />
[[Image:6-bit_BugMetricFormula.png|500px|center]]<br />
<br><br />
After assigning each bug with points associated by its complexity, we will track the total bug scores at the end of each week before deciding if there should be any actions to be taken. The following is an action plan for our bug metric:<br />
<br><br />
[[Image:6-bit_BugMetricFormula2.png|500px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Risk & Mitigation</font></div>=<br />
<br><br />
[[Image:6-bit_RiskDiagram.png|600px]]<br />
<br><br />
<br></div>Huiling.ong.2010https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1&diff=114331IS480 Team wiki: 2012T1 6-bit Project Management UT12012-12-03T12:51:52Z<p>Huiling.ong.2010: /* Testers Background */</p>
<hr />
<div><div class="center" style="width:auto; margin-left:auto; margin-right:auto; >[[Image:6-bit_logo.png]]'''</div><br />
<div class="center" style="width:60%; margin-left:auto; margin-right:auto;">'''6-bit's Chapalang!''' is a social utility that connects people with friends and new friends <br> by offering a place for exchanging ideas and information on its public domain. <br> http://www.chapalang.com<br />
</div><br />
<font face="Calibri"><br />
<!--Navigation--><br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="1" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Final_Wikipage | <font color="#FFFFFF"><b>Final Wikipage</b></font>]]<br />
<br />
|}<br />
{| style="background-color:#ffffff; color:#000000" width="100%" cellspacing="0" cellpadding="8" valign="top" border="0" |<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit | <font color="#FFFFFF"><b>Home</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Technical_Overview | <font color="#FFFFFF"><b>Technical Overview</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Deliverables | <font color="#FFFFFF"><b>Project Deliverables</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Project_Management | <font color="#FFFFFF"><b>Project Management</b></font>]]<br />
<br />
| style="filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#FF0066', endColorstr='#FF0066'); background: -webkit-gradient(linear, left top, left bottom, from(#FF0066), to(#FF0066)); background: -moz-linear-gradient(top, #FF0066, #FF0066); font-size:110%; text-align:center; color:#ffffff" width="10%" | [[IS480_Team_wiki:_2012T1_6-bit_Learning_Outcomes | <font color="#FFFFFF"><b>Learning Outcomes</b></font>]]<br />
<br />
|}<br />
<br><br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule</font></div>=<br />
==Planned Schedule==<br />
[[Image:6-bit_ScheduleDiagramOverview.png|left|750px|link=""]]<br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
==Meeting Minutes==<br />
===Team Meeting Minutes===<br />
{|<br />
|[[https://docs.google.com/document/d/1nHl51M2qzY4gynJ8tVR6wKqV_lWtJtncl3nbESSnQvU/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]]<br />
|[[https://docs.google.com/document/d/129JDPU8l7PbX-JjferJ-J83JXSIAo5-cXM4_Odw3o5c/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]]<br />
|[[https://docs.google.com/document/d/1BPn6a-XMMAN18TbdlDER27f8Eleb8sUJhcas1bgDOQI/edit |<font color="#CD004E"><b>Meeting Minute 21</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LtSANlI6pDyV_PpGDAVg85PjFVKmDmWWnYC5lXAHh68/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qx6hX462uQDEfwiB3r3ee71eTKaPXSArCZS7y1TOWA4/edit |<font color="#CD004E"><b>Meeting Minute 12</b></font>]]<br />
|[[https://docs.google.com/document/d/1IdjkCbomLgszePgImX2XsTeUHX54e54xRTIjjFoZM6g/edit |<font color="#CD004E"><b>Meeting Minute 22</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/11lQzKaddghH7FHACcTnPQDJnE6ZaScT8Q8nU2YvH8gU/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]]<br />
|[[https://docs.google.com/document/d/1HPdXr28aTDK-RmijqPYTLG1iCUv-JbpkIJ8zzgzTplg/edit |<font color="#CD004E"><b>Meeting Minute 13</b></font>]]<br />
|[[https://docs.google.com/document/d/1gMoTceQakeT42-FO0duVxRajea2hJAUVw8Eu1AfqtfY/edit |<font color="#CD004E"><b>Meeting Minute 23</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1gZuhKW-QMbhUR_oh6Ty8EE17JTYkTFkWCfG6UHrU7-c/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]]<br />
|[[https://docs.google.com/document/d/1ii-ZenbOTZR9drEQCFJ4hX8raXvpgufELaZY80M2GYI/edit |<font color="#CD004E"><b>Meeting Minute 14</b></font>]]<br />
|[[https://docs.google.com/document/d/12vYfm8jo9c2eZ3VwnL2z6vn6l__D6heDhCHdEWVPg4I/edit |<font color="#CD004E"><b>Meeting Minute 24</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1H-8fODLc79U6-IXScSfemjRLOyjvzC6_k0aig6BDcBY/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]]<br />
|[[https://docs.google.com/document/d/1I3qlvujdLVmY_L22VMsKrtISIFI5CnxmtZnMNdJdxfc/edit |<font color="#CD004E"><b>Meeting Minute 15</b></font>]]<br />
|[[https://docs.google.com/document/d/1jPIW-xe7p6kjzGF_YMmk0K2mPzWil1zUfBQOwGc8wRk/edit |<font color="#CD004E"><b>Meeting Minute 25</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Qx4jdRZoE8hXv3u1R4dWke5b-kyMxIc7ASzPIh4ShRQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]]<br />
|[[https://docs.google.com/document/d/1Pcd6ZADI7ZEuXzq3exrss4nJQhotxAq7-ENfy_OVs6o/edit |<font color="#CD004E"><b>Meeting Minute 16</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1uSkv_cux0PqnRTKS-w72wQLgL1ZKaCpXhzDm5uamfMU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]]<br />
|[[https://docs.google.com/document/d/12jW-ycBkfivYL2pg7nrVvb9SF7_XmiglVGGnWAjp6uQ/edit |<font color="#CD004E"><b>Meeting Minute 17</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1pTivyZ9D3jSU1Kf5VoW4-Xl_C9Abg-fL_6SI6GP_hz0/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]]<br />
|[[https://docs.google.com/document/d/1Qbhow5u8GsE42hr9b8o1S2HNeJfG5PTX24W70ZHyCfI/edit |<font color="#CD004E"><b>Meeting Minute 18</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1LTLnY5JN2EfiU9drp3d7zGmoCxsSYr1nL4UMvwfXDdU/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]]<br />
|[[https://docs.google.com/document/d/1fbnoWNTimFyUC01lgeblvVCLTySS8Ik2JU_wdZ656RU/edit |<font color="#CD004E"><b>Meeting Minute 19</b></font>]]<br />
|-<br />
|[[https://docs.google.com/document/d/1Nlo5hnsYbfh4dFSnfsV6Wyv5nxJsmDWF8ZMFKFA9Pac/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]]<br />
|[[https://docs.google.com/document/d/1o1zVXcdHaXCLNzS9rHq528rLEmXMFl3df3ffTFLMtho/edit |<font color="#CD004E"><b>Meeting Minute 20</b></font>]]<br />
|}<br />
<br />
===Supervisor Meeting Minutes===<br />
[https://docs.google.com/document/d/1iuSvaC9Wu-v7dToRp41IwmpdpQ0KtSTJIgpabmiolXQ/edit |<font color="#CD004E"><b>Meeting Minute 1</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1rXJuYE684ZpYbRyHknn4pmLpJZ9Y5o01QaJT34TD0gY/edit |<font color="#CD004E"><b>Meeting Minute 2</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1Gy7TOJr9aeyd8pcU_loabY1l3NByVm3nVKqOQnnJRbM/edit |<font color="#CD004E"><b>Meeting Minute 3</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1DGrSXaCTOtRL_iSOaOI_mHC2DOS7z4Vi6clzomkGkcI/edit |<font color="#CD004E"><b>Meeting Minute 4</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1VLEizDPdae_enbEtoHo9IGPM4-k9JXe7RFJ1hhiDTBA/edit |<font color="#CD004E"><b>Meeting Minute 5</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/13MyE--Ymz-dNiQPvgCjGutL23JZwotnoIPlYw7QqmXQ/edit |<font color="#CD004E"><b>Meeting Minute 6</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1UUDCW8YMttW2rwAxLJhSfqccBdedYoofVskc9qerIxU/edit |<font color="#CD004E"><b>Meeting Minute 7</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/17QEpHsvitqzO9BO9MkB42umN3_9k6Useli4N2fYoCNU/edit |<font color="#CD004E"><b>Meeting Minute 8</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1masrY10EdoXrAdwmTnW-POF0RVEYGeHbOorf-0EEC-0/edit |<font color="#CD004E"><b>Meeting Minute 9</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1u2jcuwSkGqk4lGcGdF4UriFgzT9dNgNAb1ekERDvitQ/edit |<font color="#CD004E"><b>Meeting Minute 10</b></font>]<br />
<br><br />
[https://docs.google.com/document/d/1eHVDrzwLxkGhrElcgPUOWhcQBwLdGdXcmCVvT_u-Va8/edit |<font color="#CD004E"><b>Meeting Minute 11</b></font>]<br />
<div style="margin-bottom:30px;><br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Testing</font></div>=<br />
==Test Cases==<br />
[https://dl.dropbox.com/u/56071797/Test%20Cases.docx |<font color="#CD004E"><b>Test Cases</b></font>]<br />
<br />
==Test Plans==<br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2001_17_10_2012.docx <font color="#CD004E"><b>Test Plan 1 ''on 17 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2002_28_09_2012.docx <font color="#CD004E"><b>Test Plan 2 ''on 28 September 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2003_19_10_2012.docx <font color="#CD004E"><b>Test Plan 3 ''on 19 October 2012''</b></font>]<br />
<br><br />
[https://dl.dropbox.com/u/56071797/Test%20Plan%2004_01_11_2012.docx <font color="#CD004E"><b>Test Plan 4 ''on 4 November 2012''</b></font>]<br />
<br />
==User Testing==<br />
{| style="background-color:#ffffff; border-bottom: 3px groove #728FCE; color:#000000" width="100%" cellspacing="0" cellpadding="4" valign="top" border="0" |<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT1#User_Testing|<font color="#CD004E"><b>User Testing 1</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT2#User_Testing|<font color="#CD004E"><b>User Testing 2</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT3#User_Testing|<font color="#CD004E"><b>User Testing 3</b></font>]]<br />
<br />
| style="font-size:90%; text-align:center; color:#000000" width="10%" |[[IS480_Team_wiki:_2012T1_6-bit_Project_Management_UT4#User_Testing|<font color="#CD004E"><b>User Testing 4</b></font>]]<br />
<br />
|}<br />
===User Testing 1===<br />
[[Image:6bituser-testing1.png|400px]]<br />
<br />
====Test Description====<br />
The objective of User Test 1 is on functionality and usability testing of the system. The coverage of the test is focused on forum functions.<br />
<br><br><br />
The purpose of the test is to allow neutral testers to endorse that the system is functioning according to design, or spot any bugs or anomalies. Click data which collects data about a user’s number of clicks or time taken to achieve a task is also collected to understand the experience, and for comparison purposes for future tests.<br />
====Testers Background====<br />
There are a total of 20 testers who attended the User Test, of which 60% (12) are male and 40% (8) are female, representing various schools in SMU with SIS students being the majority. There is no stratification in the test users, and testers are selected without any intended bias. It is also observed that most testers are users of Chrome and Firefox web browser.<br />
<br><br />
[[Image:6bituser-testing1results.png|550px|center]]<br />
<br />
====Test Groups====<br />
There is no test grouping employed in this test.<br />
====Test Procedures====<br />
Testers are invited to attend the User Test session and required to bring their own laptops. They are informed on the purpose of the test and given a brief description of the system objective of Chapalang!. <br />
Subsequently, they are provided with an instruction sheet for a guided test experience. Testers will be required to perform a series of system tasks based on a test case that will go through all the system features and use-case. Thereafter, testers will answer Yes/No binary questions, and can fill in details in an open-ended textbox appended after each question, should they encounter any bugs or suggestions for improvements.<br />
While the primary method of testing is on direct user experience and feedback, we have also employed secondary method which collects results indirectly. The number of clicks that each user made, together with the click coordinates or link URL, as well as timestamp of each click is captured for analytical purposes.<br />
====Test Instruction====<br />
[https://dl.dropbox.com/u/56071797/User%20Testing%201%20Instructions.docx Click Here to Download User Testing 1 Instruction]<br />
<br />
====Test Results====<br />
[[Image: 6bituser-testing1resultsfigure.png|250px]]<br />
<br><br />
Based on the abovementioned set of results, it is reasonable to conclude that the system is above satisfactory on functionalities for most testers while there are some rooms for improvements especially on intuitiveness.<br />
<br> <br><br />
There are also 4 reported bugs, and 19 recommendations for improvements received. <br />
<br><br />
[[Image: 6bituser-testing1bug.png|650px]]<br />
<br><br />
<br><br />
The top 10 most frequently mentioned or important recommendations will be published and appended below.<br />
<br><br />
[[Image: 6bituser-testing1recommendation.png]]<br />
<br />
====Click Data Analysis====<br />
Additionally, click data of each test session has also been collected and analysed. <br />
<br><br />
[[Image: 6bituser-testing1cda1.png]]<br />
<br><br />
Based on the computed statistics illustrated in the box-plot above, the median number of clicks it takes per tester to accomplish a task ranges from 1 to 8 clicks, with 3 clicks being the median. For the purpose of understanding, we could take the measurement of 3 clicks per task as a benchmark, to be compared on subsequent test sessions and observe if there are any improvements.<br />
<br><br><br />
[[Image: 6bituser-testing1cda2.png]]<br />
<br><br />
More statistics were computed in the box-plot diagram above to understand the median time spent to accomplish a task and we observe that the time taken ranges from 4 seconds to 18 seconds, with 10 seconds being the median. We will also be taking the measurement of 10 seconds per task as a benchmark to compare with subsequent test sessions and observe if there are any improvements.<br />
<br />
====Additional Observations====<br />
Further drill down on the click data has identified an observation where most testers take more clicks to accomplish Step 4 of the instructions. In Step 4, testers are required to subscribe a forum. In this observation, we are able to relate that testers are unable to easily find the Subscribe to Forum button. This finding is aligned with a common feedback that we should consider replicating the subscription button to a more intuitive location on the webpage.<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Milestones</font></div>=<br />
<br />
[[Image:6-bit_schedule.png|600px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Schedule Metric</font></div>=<br />
Every iteration, schedule metric values are calculated to understand the project progress. They are broadly categorized into 5 different groups, where different action plans will apply. The acceptable range of value is within 90% to 110%, offering some buffer for natural inaccuracies between forecasting and execution.<br />
<br><br><br />
Total Schedule Metric Value = Planned no. of days taken (P) / Actual no. of Days Assigned (A) x 100%<br />
<br><br><br />
[[Image:6-bit_schedulemetric.png|center|600px]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Bug Metric</font></div>=<br />
==Log==<br />
[[Image:6-bit_BugMetric.png|550px]]<br />
[[Image:6-bit_BugLog.png|600px]]<br />
<div style="text-align: right;"><br />
Bug Log: [https://docs.google.com/spreadsheet/ccc?key=0Aqd6IiSLbMwQdEI5TldNSEhpcVRjb1puYzU3ZHJOckE |<font color="#CD004E"><b>Click Here</b></font>]<br />
</div><br />
<br><br />
Bug logging for Chapalang! takes the direction of being practical and easily monitored from both macro and micro perspectives. Whenever a bug is found, a new row is entered with the following data:<br />
* Index number<br />
* Bug description<br />
* Found by<br />
* Found date<br />
* Expected solve-by date<br />
* Bug severity<br />
* Status<br />
* Owner of the function<br />
* Fixed date<br />
* Closed by (Tester)<br />
* Close date<br />
* Additional comments<br />
==Metric==<br />
Bugs are classified into 3 different categories of complexity, easy, moderate and hard. Each category is assigned points of 1, 5 and 10 respectively, lower is better.<br />
<br><br><br />
Total Points for Each Iteration = Σ Points of the Bugs in each iteration<br />
<br><br />
[[Image:6-bit_BugMetricFormula.png|500px|center]]<br />
<br><br />
After assigning each bug with points associated by its complexity, we will track the total bug scores at the end of each week before deciding if there should be any actions to be taken. The following is an action plan for our bug metric:<br />
<br><br />
[[Image:6-bit_BugMetricFormula2.png|500px|center]]<br />
<br />
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Risk & Mitigation</font></div>=<br />
<br><br />
[[Image:6-bit_RiskDiagram.png|600px]]<br />
<br><br />
<br></div>Huiling.ong.2010