Difference between revisions of "SColutions Scope"
(10 intermediate revisions by 2 users not shown) | |||
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 39: | Line 40: | ||
<ul> | <ul> | ||
<li>[[SColutions_System Architecture|System Architecture]]</li> | <li>[[SColutions_System Architecture|System Architecture]]</li> | ||
− | <li>[[SColutions_Prototypes|Prototypes]]</li> | + | <li>[[SColutions_Prototypes|Prototypes]]</li> |
<li>[[SColutions_Meeting_Minutes|Meeting Minutes]]</li> | <li>[[SColutions_Meeting_Minutes|Meeting Minutes]]</li> | ||
</ul> | </ul> | ||
Line 46: | Line 47: | ||
<ul> | <ul> | ||
<li>[[SColutions_Diagrams|Diagrams]]</li> | <li>[[SColutions_Diagrams|Diagrams]]</li> | ||
− | + | <li>[[SColutions_Midterm|Midterm Wiki]]</li> | |
− | + | <li>[[SColutions_Final|Finals Wiki]]</li> | |
− | |||
− | |||
− | |||
</ul> | </ul> | ||
</td> | </td> | ||
Line 56: | Line 54: | ||
</table> | </table> | ||
− | + | <br /> | |
<table width="100%"> | <table width="100%"> | ||
Line 66: | 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 126: | Line 124: | ||
</li> | </li> | ||
<li> | <li> | ||
− | <Strong>Premium Account</Strong> | + | <Strong>Premium Account</Strong><br> |
For users who have experienced and enjoyed the services provided by | For users who have experienced and enjoyed the services provided by | ||
MyHubStore, users can then seek greater benefits such as holding more | MyHubStore, users can then seek greater benefits such as holding more | ||
Line 191: | 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 217: | Line 228: | ||
by the social media platforms). <br /><br /> | 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 290: | 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 | + | 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 | |
− | make payment. When payment has been confirmed to be received | + | 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. | + | 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> |
Latest revision as of 15:01, 20 November 2014
Overview | Proj Mgmt | Documentation | Team Resource |
---|---|---|---|
Project Scope |
|||||||||||||||||
Primary Features |
|||||||||||||||||
|
|||||||||||||||||
Secondary Features |
|||||||||||||||||
|
|||||||||||||||||
Tertiary Features |
|||||||||||||||||
|