Difference between revisions of "SColutions Scope"
(27 intermediate revisions by 2 users not shown) | |||
Line 11: | Line 11: | ||
<th style="width: 21%; text-align: center; font-size:2em; padding-top:1.15em; letter-spacing:-0.1em; text-transform:uppercase; border-bottom:solid 4px #d29600; font-face:Century Gothic;"><span style="font-size:2em;">[[File:Scolutions-Pen.png|25px]] O</span>verview | <th style="width: 21%; text-align: center; font-size:2em; padding-top:1.15em; letter-spacing:-0.1em; text-transform:uppercase; border-bottom:solid 4px #d29600; font-face:Century Gothic;"><span style="font-size:2em;">[[File:Scolutions-Pen.png|25px]] O</span>verview | ||
</th> | </th> | ||
− | <th style="width: 23%; text-align: center; font-size:2em; padding-top:1.15em; letter-spacing:-0.1em; text-transform:uppercase; border-bottom:solid 4px #d29600; font-face:Century Gothic;"><span style="font-size:2em">[[File:Scolutions-Charts.png|30px]] P</span>roj <span style="font-size:2em">M</span>gmt | + | <th style="line-height: 40px;width: 23%; text-align: center; font-size:2em; padding-top:1.15em; letter-spacing:-0.1em; text-transform:uppercase; border-bottom:solid 4px #d29600; font-face:Century Gothic;"><span style="font-size:2em">[[File:Scolutions-Charts.png|30px]] P</span>roj <span style="font-size:2em">M</span>gmt |
</th> | </th> | ||
− | <th style="width: 28%; text-align: center; font-size:2em; padding-top:1.15em; letter-spacing:-0.1em; text-transform:uppercase; border-bottom:solid 4px #d29600; font-face:Century Gothic; "><span style="font-size:2em">[[File:Scolutions-Doc.png|33px]] D</span>ocumentation | + | <th style="line-height: 35px;width: 28%; text-align: center; font-size:2em; padding-top:1.15em; letter-spacing:-0.1em; text-transform:uppercase; border-bottom:solid 4px #d29600; font-face:Century Gothic; "><span style="font-size:2em">[[File:Scolutions-Doc.png|33px]] D</span>ocumentation |
</th> | </th> | ||
− | <th style="width: 28%; text-align: center; font-size:2em; padding-top:1.15em; letter-spacing:-0.1em; text-transform:uppercase; border-bottom:solid 4px #d29600;font-face:Century Gothic;"><span style="font-size:2em">[[File:Scolutions-Overview.png|32px]] T</span>eam <span style="font-size:2em">R</span>esource | + | <th style="line-height: 40px;width: 28%; text-align: center; font-size:2em; padding-top:1.15em; letter-spacing:-0.1em; text-transform:uppercase; border-bottom:solid 4px #d29600;font-face:Century Gothic;"><span style="font-size:2em">[[File:Scolutions-Overview.png|32px]] T</span>eam <span style="font-size:2em">R</span>esource |
</th> | </th> | ||
</tr> | </tr> | ||
Line 21: | Line 21: | ||
<td style="border-bottom:solid 2px #d29600; text-align: left; font-size:1.2em; line-height:0.8em; vertical-align:top;"> | <td style="border-bottom:solid 2px #d29600; text-align: left; font-size:1.2em; line-height:0.8em; vertical-align:top;"> | ||
<ul> | <ul> | ||
+ | <li>[[IS480_Team_wiki%3A_2014T1_SColutions|Project Dashboard]]</li> | ||
<li>[[SColutions_Team|Team SColutions]]</li> | <li>[[SColutions_Team|Team SColutions]]</li> | ||
<li>[[SColutions_Description|Project Description]]</li> | <li>[[SColutions_Description|Project Description]]</li> | ||
Line 31: | Line 32: | ||
<li>[[SColutions_Scope|Project Scope]]</li> | <li>[[SColutions_Scope|Project Scope]]</li> | ||
<li>[[SColutions Project Schedule|Project Schedule]]</li> | <li>[[SColutions Project Schedule|Project Schedule]]</li> | ||
− | <li>[[ | + | <li>[[Scolutions_Quality_Assurance|Quality Assurance]]</li> |
− | <li>Key Risks</li> | + | <li>[[Scolutions_Metrics Management|Metrics Management]]</li> |
+ | <li>[[Scolutions_Key Risks|Key Risks]]</li> | ||
</ul> | </ul> | ||
</td> | </td> | ||
<td style=" border-bottom:solid 2px #d29600; text-align: left; font-size:1.2em; line-height:0.8em;"> | <td style=" border-bottom:solid 2px #d29600; text-align: left; font-size:1.2em; line-height:0.8em;"> | ||
<ul> | <ul> | ||
− | + | <li>[[SColutions_System Architecture|System Architecture]]</li> | |
− | <li>[[ | + | <li>[[SColutions_Prototypes|Prototypes]]</li> |
− | <li>[[ | ||
− | |||
<li>[[SColutions_Meeting_Minutes|Meeting Minutes]]</li> | <li>[[SColutions_Meeting_Minutes|Meeting Minutes]]</li> | ||
</ul> | </ul> | ||
</td> | </td> | ||
<td style=" border-bottom:solid 2px #d29600; text-align: left; font-size:1.2em; line-height:0.8em;"> | <td style=" border-bottom:solid 2px #d29600; text-align: left; font-size:1.2em; line-height:0.8em;"> | ||
− | <ul> | + | <ul> |
− | <li>[[ | + | <li>[[SColutions_Diagrams|Diagrams]]</li> |
− | + | <li>[[SColutions_Midterm|Midterm Wiki]]</li> | |
− | + | <li>[[SColutions_Final|Finals Wiki]]</li> | |
− | |||
− | |||
− | |||
</ul> | </ul> | ||
</td> | </td> | ||
Line 57: | Line 54: | ||
</table> | </table> | ||
− | + | <br /> | |
<table width="100%"> | <table width="100%"> | ||
Line 67: | Line 64: | ||
<tr> | <tr> | ||
<td colspan="3" width="100%" style="text-align: center;"> | <td colspan="3" width="100%" style="text-align: center;"> | ||
− | [[File:Scolutions scope.png| | + | [[File:Scolutions scope.png|750px]] |
</td> | </td> | ||
</tr> | </tr> | ||
Line 90: | Line 87: | ||
<tr> | <tr> | ||
<td width="100%"> | <td width="100%"> | ||
− | Each | + | Each MyHubStore user will be able to manage their account at their own discretion. This includes the following: |
<ul> | <ul> | ||
<li>Manage Individual Account Particulars</li> | <li>Manage Individual Account Particulars</li> | ||
Line 107: | Line 104: | ||
<tr> | <tr> | ||
<td width="100%" style="text-align: justify;"> | <td width="100%" style="text-align: justify;"> | ||
− | + | For each store, a user is able to set up a physical store location for their store (Use | |
− | + | case meant for stores which have a physical location). Through the use of Google Maps | |
− | + | Javascript v3 API, users are able to plant markers to indicate and save their store | |
− | + | location. This will allow any potential buyer the ability to view it when they visit the | |
− | + | seller's store on MyHubStore. <br /><br /> | |
− | |||
− | |||
− | |||
− | |||
− | + | Additionally, under store management, a user can hold 1 to many stores under his account | |
+ | (To have and manage more than one account, a user has to sign up for a payment plan under | ||
+ | any one of the premium account plans). There are two separate types of user accounts to | ||
+ | cater to different segments of users: | ||
+ | <ul> | ||
+ | <li> | ||
+ | <Strong>Free Account</Strong><br /> | ||
+ | When MyHubStore users first create an account and join the web app, they | ||
+ | will be entitled to a free account which provides them with the full range | ||
+ | of services offered. However, this service is only valid for 3 months and | ||
+ | there is a maximum limit of 25 items to be listed for stores using this | ||
+ | account. | ||
+ | </li> | ||
+ | <li> | ||
+ | <Strong>Premium Account</Strong><br> | ||
+ | For users who have experienced and enjoyed the services provided by | ||
+ | MyHubStore, users can then seek greater benefits such as holding more | ||
+ | stores and selling more items by signing up for the premium account. Under | ||
+ | this section, there are sub segments which provide more functions such as | ||
+ | personalized analysis of their shops for users (Platinum Account). Users | ||
+ | who intend to sign up for the premium accounts have to make a yearly | ||
+ | payment through the use of Paypal which will be integrated into the | ||
+ | MyHubStore system. (Pricing has not been finalized with sponsor) | ||
+ | <ul> | ||
+ | <li> | ||
+ | <Strong>Gold Class</Strong><br /> | ||
+ | Gold class users are able to hold up to 10 stores under | ||
+ | their store management as well as sell up to 100 items per | ||
+ | store. | ||
+ | </li> | ||
+ | <li> | ||
+ | <Strong>Platinum Class</Strong><br /> | ||
+ | Platinum class users are able to hold up to 25 stores | ||
+ | under their store management and sell up to 1000 items per | ||
+ | user. Additionally, users will be able to have a | ||
+ | personalized dashboard on their store performance per | ||
+ | month. This analysis includes showing users which | ||
+ | items/stores are being visited. Comments from the Facebook | ||
+ | graph API will also provide analysis into what users are | ||
+ | talking about. | ||
+ | </li> | ||
+ | </ul> | ||
+ | </li> | ||
+ | </ul> | ||
+ | Going forward, the administrator will be provided the ability to create more Account types | ||
+ | using his administrator account. | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 128: | Line 166: | ||
<tr> | <tr> | ||
<td width="100%" style="text-align: justify;"> | <td width="100%" style="text-align: justify;"> | ||
− | + | As part of the store item management, MyHubStore users will be allowed to access their | |
+ | portfolio store items and manage them individually. This can be viewed in more detail at | ||
+ | the [[Medium_Fidelity|Medium Fidelity Section]]. The scope of managing each item | ||
+ | encompasses the following: | ||
<ul> | <ul> | ||
<li>Update of Item Details</li> | <li>Update of Item Details</li> | ||
<li>Track item views</li> | <li>Track item views</li> | ||
<li>View likes, comments and ratings of item</li> | <li>View likes, comments and ratings of item</li> | ||
+ | </ul> | ||
+ | Besides this, MyHubStore provides every user an overarching analysis of their store items | ||
+ | across 5 different transaction types: <br /> | ||
+ | <ul> | ||
+ | <li>Selling</li> | ||
+ | <li>Trading</li> | ||
+ | <li>Give aways</li> | ||
+ | <li>Renting</li> | ||
+ | <li>Make an Offer</li> | ||
</ul> | </ul> | ||
</td> | </td> | ||
Line 139: | Line 189: | ||
<tr> | <tr> | ||
<td width="100%" style="font-weight:bold; text-align: justify; border-bottom:solid 1px #000;"> | <td width="100%" style="font-weight:bold; text-align: justify; border-bottom:solid 1px #000;"> | ||
− | 4. | + | 4. Administrator Management |
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td width="100%" style="text-align: justify;"> | <td width="100%" style="text-align: justify;"> | ||
− | + | Our sponsor will be the acting administrator for the entire website. This module allows him to not require any technical knowledge of controlling and editing various components of the website. Key features of this module encompass the following: | |
+ | <ul> | ||
+ | <li><Strong>Content Management</Strong><br> | ||
+ | The administrator will be able to setup a blacklist of words to be omitted in the content of Item and Store Description. | ||
+ | </li> | ||
+ | <li><Strong>Notification Alerts Management</Strong><br> | ||
+ | The administrator will be able to control the different kind of notifications to be sent out the user and admin for specific events such as number of warnings before account is disabled for free accounts etc. | ||
+ | </li> | ||
+ | <li><Strong>Account Type Management</Strong><br> | ||
+ | The administrator will have control over the different account types offered to users and merchants on the website. This not only includes creating new account types for users to select but also editing the number of stores and items a user is able to play with for their specific account types. | ||
+ | </li> | ||
+ | <li><Strong>User Accounts Management</Strong><br> | ||
+ | There will be control over all user accounts created in MyHubStore. This control encompasses the ability to manually reset user password, suspend user accounts (Repeated offenders who post indecent material) and manually update user accounts. | ||
+ | </li> | ||
+ | <li><Strong>Manage Website Details</Strong><br> | ||
+ | The administrator will be able to modify simple website details such as the website logo and minor content information | ||
+ | </li> | ||
+ | </ul> | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 155: | Line 222: | ||
<tr> | <tr> | ||
<td width="100%" style="text-align: justify;"> | <td width="100%" style="text-align: justify;"> | ||
− | + | Leveraging on information provided by Social Network Platforms for example, Facebook Graph API | |
+ | (Comments, Likes, Share on Wall & Messages to Friends) as well as Twitter & Google+ APIs (To be | ||
+ | Explored After Acceptance), the administrator will be able to view a visual representation of | ||
+ | customer patterns & sales trends (Use of D3 tools to provide visual analysis on the data provided | ||
+ | by the social media platforms). <br /><br /> | ||
+ | |||
+ | Google Analytics tools will be used to generate analysis on the information | ||
+ | provided by twitter and the other social networks. Some key metrics to be used include identifying | ||
+ | main traffic sources. With these identified media traffic sources, more advanced segments include | ||
+ | how social networks compare against each other. This includes using Audience reports to identify | ||
+ | user behaviour and gauge how engaged they are on MyHubStore. This gives MyHubStore stakeholders a | ||
+ | rough gauge of where to concentrate their attention to. | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 189: | Line 267: | ||
<ul> | <ul> | ||
<li> | <li> | ||
− | < | + | <Strong>Facebook</Strong><br /> |
− | The Facebook platform will allow | + | The Facebook platform will allow MyHubStore users to interact with friends on their social network and share items or stores from MyHubStore with them. On a more technical level, the MyHubStore platform will leverage on Facebook Graph API to conduct the following activities: |
+ | <ul> | ||
+ | <li>Share On Own Wall</li> | ||
+ | <li>Post a Message to Friends</li> | ||
+ | <li>Like Item or Store on MyHubStore </li> | ||
+ | <li>Comment on Item or Store on MyHubStore</li> | ||
+ | </ul> | ||
+ | The Facebook platform is one of the three platforms which ought to allow | ||
+ | MyHubStore to capitalize on a large existing user base. With social | ||
+ | interactive features to increase user traffic, the web application will be | ||
+ | able to extend its reach to a wide range of audience and increase the | ||
+ | probability of more successful transactions.<br/> | ||
</li> | </li> | ||
<li> | <li> | ||
− | + | <Strong>Google+</Strong><br /> | |
− | + | Similar to Facebook, the connection with Google+ will allow for users to | |
+ | be share, shout-outs and discuss new items and stores on their account. | ||
+ | (APIs to be explored in greater detail after acceptance - as per schedule) | ||
+ | <br/> | ||
</li> | </li> | ||
<li> | <li> | ||
− | + | <Strong>Twitter</Strong><br /> | |
− | + | The Twitter platform takes on a different role from Facebook and Google+. | |
+ | As a social network which focuses on short, concise and impactful text, | ||
+ | this platform will allow users to share items and details efficiently. | ||
+ | Users are also able to post interesting new store items/stores to their | ||
+ | twitter account to increase web visibility.(APIs to be explored in greater | ||
+ | detail after acceptance - as per schedule)<br/> | ||
</li> | </li> | ||
</ul> | </ul> | ||
Line 206: | Line 303: | ||
<tr> | <tr> | ||
<td width="100%" style="font-weight:bold; text-align: justify; border-bottom:solid 1px #000;"> | <td width="100%" style="font-weight:bold; text-align: justify; border-bottom:solid 1px #000;"> | ||
− | 2. | + | 2. Payment Function (Google Wallet) |
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td width="100%" style="text-align: justify;"> | <td width="100%" style="text-align: justify;"> | ||
− | + | Users who intend to make payment to receive better service on MyHubStore will seamlessly make their | |
+ | payment (Please see premium account under store management functionality for more details on the | ||
+ | premium accounts). Through the use of Google Wallet API, users will not be required to be redirected | ||
+ | out of the website to make payment (All payments will be carried out from the same tab). When payment | ||
+ | has been confirmed to be received, a receipt detailing their order will be recorded and the allocated | ||
+ | services will automatically be released to the user for use. <br><br> | ||
+ | With MyHubStore running on a pay per month basis, users will be deducted a fee each month to maintain | ||
+ | their account with MyHubStore. Users can manage their payment subscriptions using Google Wallet. | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 222: | Line 326: | ||
<tr> | <tr> | ||
<td width="100%" style="text-align: justify;"> | <td width="100%" style="text-align: justify;"> | ||
− | + | As part of the e-commerce business, the search function allows users to be able to find | |
+ | information efficiently. The search function is broken down into three separate kinds of | ||
+ | search namely: | ||
+ | <ul> | ||
+ | <li> | ||
+ | <Strong>Search For Item</Strong><br /> | ||
+ | For every items posted and published on MyHubStore, they will be tagged to | ||
+ | special keywords associated with their Item Name and Description. This | ||
+ | will allow users to find their desired items more effectively and | ||
+ | efficiently. | ||
+ | </li> | ||
+ | <li> | ||
+ | <Strong>Search For Store Name / Owner</strong><br /> | ||
+ | Quite similar to Item Search, every store created by a user has a special | ||
+ | tag associated with it. In Store keyword's tagging case, it is associated | ||
+ | with the Store name, Store Description, Store Owner's name and Store | ||
+ | Owner's email. | ||
+ | </li> | ||
+ | <li> | ||
+ | <Strong>Search via Address</Strong><br /> | ||
+ | The last search is associated with location based finding. The user is | ||
+ | able to input a specific address anywhere in the world and through the use | ||
+ | of Google Maps API, stores within a 10km radius are picked up and | ||
+ | displayed (Ordered in the closest distance from the user). The search | ||
+ | distance is calculated using Haversine's Formula which calculates | ||
+ | distances between two points on a sphere from their longitudes and | ||
+ | latitudes. | ||
+ | </li> | ||
+ | </ul> | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 249: | Line 381: | ||
<tr> | <tr> | ||
<td width="100%" style="font-weight:bold; text-align: justify; border-bottom:solid 1px #000;"> | <td width="100%" style="font-weight:bold; text-align: justify; border-bottom:solid 1px #000;"> | ||
− | 1. | + | 1. Messaging Function |
</td> | </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td width="100%"> | <td width="100%"> | ||
− | A | + | A messaging function will be incorporated into the MyHubStore Web application where interested |
+ | buyers can communicate with sellers on a more personal level. When a message is sent through the | ||
+ | store, an automated email will be sent to the user's account to inform him/her about the new | ||
+ | message. Messages sent will be tagged to a particular store for easy archiving. When users log in | ||
+ | into their MyHubStore account, they will also have a notification informing them about the new | ||
+ | message. | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 265: | Line 402: | ||
<tr> | <tr> | ||
<td width="100%" style="text-align: justify;"> | <td width="100%" style="text-align: justify;"> | ||
− | + | MyHubStore users will be able to earn commission by selling other people’s products on their own social networks and earn a commission (% of sales price). By leveraging on a user's popularity on social networks, the more a user is able to carry out more transactions, the more commission money he/she will be able to earn. The commission % will be listed on each item's site. | |
</td> | </td> | ||
</tr> | </tr> |
Latest revision as of 15:01, 20 November 2014
Overview | Proj Mgmt | Documentation | Team Resource |
---|---|---|---|
Project Scope |
|||||||||||||||||
Primary Features |
|||||||||||||||||
|
|||||||||||||||||
Secondary Features |
|||||||||||||||||
|
|||||||||||||||||
Tertiary Features |
|||||||||||||||||
|