HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2014T1 Team Epsilon Project Overview"

From IS480
Jump to navigation Jump to search
m
 
(8 intermediate revisions by 2 users not shown)
Line 25: Line 25:
 
<!-- Start of sub-header -->
 
<!-- Start of sub-header -->
 
{|style="background-color:#FFFFFF; color:#000000 padding: 5px 0 0 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0"  |
 
{|style="background-color:#FFFFFF; color:#000000 padding: 5px 0 0 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0"  |
| style="padding:0.4em; font-size:150%; background-color:#E0D1FF;  border-bottom:4px solid #000000; border-top:4px solid #000000; text-align:center; color:#828282" width="10%" | [[IS480 Team wiki: 2014T1 Team Epsilon Project Overview |<font color="#000000" size=2><b>Description</b></font>]]
+
| style="padding:0.4em; font-size:150%; background-color:#E0D1FF;  border-bottom:4px solid #000000; border-top:4px solid #000000; text-align:center; color:#828282" width="10%" | [[IS480 Team wiki: 2014T1 Team Epsilon Project Overview |<font color="#000000" size=2><b>Overview</b></font>]]
  
 
| style="border-bottom:4px solid #000000; border-top:4px solid #000000; background:none;" width="1%" | &nbsp;
 
| style="border-bottom:4px solid #000000; border-top:4px solid #000000; background:none;" width="1%" | &nbsp;
| style="padding:0.4em; font-size:150%; background-color:#FFFFFF;  border-bottom:4px solid #000000; border-top:4px solid #000000; text-align:center; color:#828282" width="10%" | [[IS480 Team wiki: 2014T1 Team Epsilon Motivation |<font color="#000000" size=2><b>Motivation</b></font>]]
+
| style="padding:0.4em; font-size:150%; background-color:#FFFFFF;  border-bottom:4px solid #000000; border-top:4px solid #000000; text-align:center; color:#828282" width="10%" | [[IS480 Team wiki: 2014T1 Team Epsilon Storyboard |<font color="#000000" size=2><b>Storyboard</b></font>]]
  
 
| style="border-bottom:4px solid #000000; border-top:4px solid #000000; background:none;" width="1%" | &nbsp;
 
| style="border-bottom:4px solid #000000; border-top:4px solid #000000; background:none;" width="1%" | &nbsp;
Line 35: Line 35:
 
| style="border-bottom:4px solid #000000; border-top:4px solid #000000; background:none;" width="1%" | &nbsp;
 
| style="border-bottom:4px solid #000000; border-top:4px solid #000000; background:none;" width="1%" | &nbsp;
 
| style="padding:0.4em; font-size:150%; background-color:#FFFFFF;  border-bottom:4px solid #000000; border-top:4px solid #000000; text-align:center; color:#828282" width="10%" | [[IS480 Team wiki: 2014T1 Team Epsilon Scope | <font color="#000000" size=2><b>Scope</b></font>]]
 
| style="padding:0.4em; font-size:150%; background-color:#FFFFFF;  border-bottom:4px solid #000000; border-top:4px solid #000000; text-align:center; color:#828282" width="10%" | [[IS480 Team wiki: 2014T1 Team Epsilon Scope | <font color="#000000" size=2><b>Scope</b></font>]]
 +
 +
| style="border-bottom:4px solid #000000; border-top:4px solid #000000; background:none;" width="1%" | &nbsp;
 +
| style="padding:0.4em; font-size:150%; background-color:#FFFFFF;  border-bottom:4px solid #000000; border-top:4px solid #000000; text-align:center; color:#828282" width="10%" | [[IS480 Team wiki: 2014T1 Team Epsilon Design Overview | <font color="#000000" size=2><b>Design</b></font>]]
  
 
| style="border-bottom:4px solid #000000; border-top:4px solid #000000; background:none;" width="1%" | &nbsp;  
 
| style="border-bottom:4px solid #000000; border-top:4px solid #000000; background:none;" width="1%" | &nbsp;  
Line 43: Line 46:
 
<!-- Start Content -->
 
<!-- Start Content -->
  
==How It Works==
+
== Motivation ==
<center>
+
Our motivation for this project stems from the desire to improve the current cumbersome system of resolving infrastructure issues. To raise such issues, the public would usually have to look for the relevant authorities and describe the issues over a call. The details of these issues would be logged by the agency before they begin to resolve it. This process is troublesome and time-consuming for both parties, which discourages the public from highlighting infrastructure issues. Such notifications are also restricted to the normal working hours. In addition, this system is inefficient because a verbal description may not be enough for the agency to fully grasp the issue. For such cases, they would have to expend additional effort in order to begin resolving them.
[[Image: How_it_works.png|900px]]
+
 
</center>
+
After our mid-terms presentation, we contacted various news publications and agencies (both government like MSO, NEA, LTA, and non-government) to try out our application. Eventually, we managed to meet up with Ramky, one of the sub-contractors working under NEA in-charge of cleaning parts of Singapore. While they found our app useful (especially for their own private use), the fact that MSO already has plans to release a similar app soon, and that they are under the government’s contract, means our app will not be their priority, but only an alternative means of reporting just like phone call and email.
 +
 
 +
Though we were unable to garner any commitment from agencies, we realized that there are users interested in voicing out their concerns about infrastructure/ cleanliness issues. As such, we decided to focus on the needs of these users and modified our application accordingly. This change in focus has been approved by both our sponsor, Mr. Low Chin Chau and supervisor, Mr. Chris Boesch. Note that while our target audience has changed, we would still be delivering the functions that we promised our sponsor.
  
 +
== Value To Sponsor ==
 +
* Delivery of requested feedback system (with all core functions, 70% secondary functions, 3 additional functions).
 +
* Proved that there is a desire for such a feedback system from general users and agencies.
 +
* Begun initial conversations with Ramky Cleantech Services Pte Ltd, which expressed interest in buying the system for their own private use, namely to connect all their cleaning departments which are currently working in silos.
  
==Technology==
+
== Our Journey ==
{| class="wikitable" style="text-align: center; height:50px"
+
[[Image: Epsilon_Journey_1.png|800px]]<br/>
|-
+
[[Image: Epsilon_Journey_2.png|800px]]<br/>
| style="background:#002266; color:#ffffff" | Programming Language || Objective-C, Ruby, Javascript, HTML5, LESS
+
[[Image: Epsilon_journey_3.png|800px]]<br/>
|-
+
[[Image: Epsilon_Journey_4.png|800px]]
| style="background:#002266; color:#ffffff" | Framework || Rails, Twitter Bootstrap
 
|-
 
| style="background:#002266; color:#ffffff" | Web Service || AJAX, JSON REST
 
|-
 
| style="background:#002266; color:#ffffff" | Database || PostgreSQL
 
|-
 
| style="background:#002266; color:#ffffff" | Repository || Github
 
|-
 
| style="background:#002266; color:#ffffff" | Server || Heroku
 
|-
 
| style="background:#002266; color:#ffffff" | Storage || Amazon S3
 
|-
 
| style="background:#002266; color:#ffffff" | Platform Supported || Web, iOS
 
|}
 

Latest revision as of 00:20, 23 November 2014

Team Epsilon Logo.png.png

Home   Project Overview   Project Management   Documentation   Team

Overview   Storyboard   Stakeholders   Scope   Design   X-Factor


Motivation

Our motivation for this project stems from the desire to improve the current cumbersome system of resolving infrastructure issues. To raise such issues, the public would usually have to look for the relevant authorities and describe the issues over a call. The details of these issues would be logged by the agency before they begin to resolve it. This process is troublesome and time-consuming for both parties, which discourages the public from highlighting infrastructure issues. Such notifications are also restricted to the normal working hours. In addition, this system is inefficient because a verbal description may not be enough for the agency to fully grasp the issue. For such cases, they would have to expend additional effort in order to begin resolving them.

After our mid-terms presentation, we contacted various news publications and agencies (both government like MSO, NEA, LTA, and non-government) to try out our application. Eventually, we managed to meet up with Ramky, one of the sub-contractors working under NEA in-charge of cleaning parts of Singapore. While they found our app useful (especially for their own private use), the fact that MSO already has plans to release a similar app soon, and that they are under the government’s contract, means our app will not be their priority, but only an alternative means of reporting just like phone call and email.

Though we were unable to garner any commitment from agencies, we realized that there are users interested in voicing out their concerns about infrastructure/ cleanliness issues. As such, we decided to focus on the needs of these users and modified our application accordingly. This change in focus has been approved by both our sponsor, Mr. Low Chin Chau and supervisor, Mr. Chris Boesch. Note that while our target audience has changed, we would still be delivering the functions that we promised our sponsor.

Value To Sponsor

  • Delivery of requested feedback system (with all core functions, 70% secondary functions, 3 additional functions).
  • Proved that there is a desire for such a feedback system from general users and agencies.
  • Begun initial conversations with Ramky Cleantech Services Pte Ltd, which expressed interest in buying the system for their own private use, namely to connect all their cleaning departments which are currently working in silos.

Our Journey

Epsilon Journey 1.png
Epsilon Journey 2.png
Epsilon journey 3.png
Epsilon Journey 4.png