HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T1 Eureka Final Wiki"

From IS480
Jump to navigation Jump to search
 
(13 intermediate revisions by the same user not shown)
Line 32: Line 32:
  
 
| style="padding:0.1em; font-size:100%; border-top:0px solid #F5F5F5; background-color:#FFFFFF; text-align:center; color:#F5F5F5" width="25%" |  
 
| style="padding:0.1em; font-size:100%; border-top:0px solid #F5F5F5; background-color:#FFFFFF; text-align:center; color:#F5F5F5" width="25%" |  
[[<font color="#000000" size=2 face="Century Gothic"><b><u>MID TERM WIKI</u></b></font>]]
+
[[IS480 Team wiki: 2016T1 Eureka Mid Term Wiki|<font color="#318ba2" size=2 face="Century Gothic"><b><u>MIDTERM WIKI</u></b></font>]]
  
 
| style="padding:0.1em; font-size:100%; border-top:0px solid #F5F5F5; background-color:#FFFFFF; text-align:center; color:#F5F5F5" width="25%" |  
 
| style="padding:0.1em; font-size:100%; border-top:0px solid #F5F5F5; background-color:#FFFFFF; text-align:center; color:#F5F5F5" width="25%" |  
Line 41: Line 41:
 
<!--Content Start-->
 
<!--Content Start-->
 
<br>
 
<br>
 +
=Project Progress Summary=
 +
<center><div >
 +
{| class="wikitable" style="background-color:#FFFFFF;"
 +
| [[Image:Eureka Slides Upload.png|200px|link=https://drive.google.com/open?id=0B_2v7xKJtsR9aHVzMFZWaXZfMEk]]
 +
| [[Image:Eureka_Video_Upload.png|200px|link=https://drive.google.com/open?id=0B7tqsNgf6rjRMUszNUdiWF9fdDA]]
 +
| [[Image:Eureka_Poster_Upload.png|200px|link=https://drive.google.com/open?id=0B7tqsNgf6rjROThTc0I5VlBrWVE]]
 +
|}
 +
</div></center>
 +
 
=Project Highlights=
 
=Project Highlights=
 
[[Image:Eureka Finals Highlights.png|center|950px]]
 
[[Image:Eureka Finals Highlights.png|center|950px]]
  
 +
=Project Challenges=
 +
<br>
 +
<center>Besides sponsor, our team had to independently liaise with the client, Eastman Chemical.
 +
As the company was located on Jurong Island, a secure location which requires security clearance to visit, we faced some degree of difficulty when arranging face-to-face meetings. As a result of this, most of the communication were done via e-mail and text messages and calls.
 +
 +
Although we were fortunate to receive upper management’s support for implementing our proposed solution, they delegated the task of coordinating our project to a lower level administrative staff. As a result of the lack of influence and commitment of the administrative staff to improve efficiency within the organisation, we faced several problems.
 +
 +
Our team has striven to mitigate these challenges by having having greater engagement of both the upper management and our sponsor as well frequently encouraging the administrative staff.</center>
 +
<br>
 
=Project Management =
 
=Project Management =
 
[[Image:Eureka Finals Management.png|center|400px]]
 
[[Image:Eureka Finals Management.png|center|400px]]
Line 67: Line 85:
  
 
===Technical Complexity===
 
===Technical Complexity===
 +
<table rules="all" width="87%" cellpadding="6" cellspacing="3" style="margin: 1em auto 1em auto; font-weight: normal">
 +
<tr style="background-color:#318ba2;"><th>Scalability & Flexibility</th></tr>
 +
<tr><td width="30%" border="1">
 +
As our aim is to come out with a new business initiative, one of the primary aim for our application is scalability. We must not only be able to cater to the current clients, but also the potential future companies who may join and use LunchTime. So scalability and flexibility are our key considerations when developing our application.
 +
 +
We noted that although LunchTime is targeted to help employees order their lunch, different companies may wish to order their foods at different timings, like 11am, 12noon etc. Or perhaps in the future, LunchTime could even extend further allowing companies the option to order Tea Break for their employees. This meant that our application needs to be flexible enough to handle orders from different timings, different companies and different canteens. So our approach to resolving this kind of many different association problems is to create an entity called Order Period.
 +
</td></tr>
 +
</table>
 +
<table rules="all" width="87%" cellpadding="6" cellspacing="3" style="margin: 1em auto 1em auto; font-weight: normal">
 +
<tr style="background-color:#318ba2;"><th>Order Period</th></tr>
 +
<tr><td width="30%" border="1">
 +
An Order Period is a time period in which employees of a particular company can log onto LunchTime to order food from the specified canteen. So, an Order Period is linked directly to one company and one canteen. This allows us to easily mix and match and track which company is ordering from which canteen for a given time period. So for instance, today, Company A is ordering food from Canteen A, Company B is ordering food from Canteen C; and tomorrow Company A is ordering from Canteen B, Company B is ordering food from Canteen A. Order Period also allows us to link additional features like company-wide discounts and reminders easily. This is to complement existing events at the client company whereby they offer $4 discounts to their employees when they order food on Fridays.
 +
</td></tr>
 +
</table>
 +
<table rules="all" width="87%" cellpadding="6" cellspacing="3" style="margin: 1em auto 1em auto; font-weight: normal">
 +
<tr style="background-color:#318ba2;"><th>Cloud Solution</th></tr>
 +
<tr><td width="30%" border="1">
 +
Next, in anticipation that our user base could grow substantially in the future, we decided to host our application on a cloud platform called eApps. Cloud services are well suited in our case as being a small company, we are extremely cost sensitive. Having servers running round the clock can add up to quite a substantial cost. Cloud solutions allow us to pay just what we use, and turn it off when there is zero utilization. In addition, as more users use LunchTime in future, we are able to respond to the rise in traffic quickly. With just a click of a button, we can determine the amount of server resources we want and scale up. We could also plan scheduled times such as lunch hours to scale up our application to handle the higher traffic. During weekends and non-meal hours, we can scale down to the bare minimum to save cost. Cloud solutions have helped our idea reap better returns by paying for only what we require.
 +
</td></tr>
 +
</table>
 +
<table rules="all" width="87%" cellpadding="6" cellspacing="3" style="margin: 1em auto 1em auto; font-weight: normal">
 +
<tr style="background-color:#318ba2;"><th>Data Analytics</th></tr>
 +
<tr><td width="30%" border="1">
 +
Lastly, we created some data analytics features to aid decision making for the admin using LunchTime. For example, Koh Bus currently has to fork out a capital in order to pay for the employees first, before they pay him at the end of the week. Setting aside more than enough money would mean wastage as these funds can be invested elsewhere, and setting aside too little would result in the driver not having enough cash to pay for the meals. As such, we used jfreechart to display each company’s spending pattern, helping us to get better visualization and insights. Currently, drawing the insights from the data, we can estimate that Koh Bus needs to set aside at least $50 per week to pay for all the meals in LunchTime.
 +
</td></tr>
 +
</table>
  
 
=Quality of Product=
 
=Quality of Product=
Line 125: Line 169:
 
|-
 
|-
 
|rowspan="1"|Trial Implementation
 
|rowspan="1"|Trial Implementation
|| [[IS480 Team wiki: 2016T2 Eureka User Testing 2| Trial (P)]]
+
|| [[IS480 Team wiki: 2016T2 Eureka Trial Implementation| Trial]]
 
|-
 
|-
  
Line 160: Line 204:
 
<center><div >
 
<center><div >
 
{| class="wikitable" style="background-color:#FFFFFF;"
 
{| class="wikitable" style="background-color:#FFFFFF;"
| [[Image:Eureka_Mid_terms_slides.png|170px|link=https://drive.google.com/a/smu.edu.sg/file/d/0B_2v7xKJtsR9ZjlGaEtmbnZSdWM/view?usp=sharing]]
 
 
| [[Image:Eureka Mid terms Employee.png|170px|link=http://bit.ly/lunchtimeEmployee]]
 
| [[Image:Eureka Mid terms Employee.png|170px|link=http://bit.ly/lunchtimeEmployee]]
 
| [[Image:Eureka Mid terms Admin.png|170px|link=http://bit.ly/lunchtimeAdmin]]
 
| [[Image:Eureka Mid terms Admin.png|170px|link=http://bit.ly/lunchtimeAdmin]]
Line 204: Line 247:
 
[[IS480 Team wiki: 2016T2 Eureka_User_Testing_1|<u>Eureka User Testing 1</u>]]<br>
 
[[IS480 Team wiki: 2016T2 Eureka_User_Testing_1|<u>Eureka User Testing 1</u>]]<br>
 
</center>
 
</center>
 +
</td></tr>
 +
</table>
 +
<div style="background: #318ba2; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:18px; font-family:helvetica"><font color= #FFFFFF>Trial Implementation</font></div>
 +
<table rules="all" width="87%" cellpadding="6" cellspacing="3" style="margin: 1em auto 1em auto; font-weight: normal">
 +
<tr style="background-color:#318ba2;"><th>Objectives</th></tr>
 +
<tr><td width="30%" border="1">
 +
- Assess the usability of our application in the day-to-day lunch ordering process<br>
 +
- Gather sponsor, pilot implementation company and relevant users’ feedback with regards to the heuristics and design of the existing functions of the current application<br>
 +
- Identify any usability issues that persist in the application<br>
 +
- Improvement on our application based on the results<br>
 +
- Managing of expectations<br>
 +
</td></tr>
 +
</table>
 +
 +
<table rules="all" width="87%" cellpadding="6" cellspacing="3" style="margin: 1em auto 1em auto; font-weight: normal">
 +
<tr style="background-color:#318ba2;"><th>Number of Users</th></tr>
 +
<tr><td width="30%" border="1">
 +
<center><b>Admin (2 Participants)</b></center>
 +
- Admin: 1 Participant<br>
 +
- Employee: 14 Participants<br>
 
</td></tr>
 
</td></tr>
 
</table>
 
</table>
  
 +
<table rules="all" width="87%" cellpadding="6" cellspacing="3" style="margin: 1em auto 1em auto; font-weight: normal">
 +
<tr style="background-color:#318ba2;"><th>Date</th></tr>
 +
<tr><td width="30%" border="1">
 +
<center>25th January 2016 to 26th February 2016
 +
</center>
 +
</td></tr>
 +
</table>
 +
<table rules="all" width="87%" cellpadding="6" cellspacing="3" style="margin: 1em auto 1em auto; font-weight: normal">
 +
<tr style="background-color:#318ba2;"><th>Full Documentation</th></tr>
 +
<tr><td width="30%" border="1">
 +
<center>Full Documentation of Trial Implemenation can be found in
 +
[[IS480 Team wiki: 2016T2 Eureka_Trial_Implementation|<u>Eureka Trial Implementation</u>]]<br>
 +
</center>
 +
</td></tr>
 +
</table>
 
<div style="background: #318ba2; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:18px; font-family:helvetica"><font color= #FFFFFF>User Testing 2</font></div>
 
<div style="background: #318ba2; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:18px; font-family:helvetica"><font color= #FFFFFF>User Testing 2</font></div>
 
<table rules="all" width="87%" cellpadding="6" cellspacing="3" style="margin: 1em auto 1em auto; font-weight: normal">
 
<table rules="all" width="87%" cellpadding="6" cellspacing="3" style="margin: 1em auto 1em auto; font-weight: normal">
Line 240: Line 318:
 
<center>Full Documentation of User Testing 2 can be found in  
 
<center>Full Documentation of User Testing 2 can be found in  
 
[[IS480 Team wiki: 2016T2 Eureka_User_Testing_2|<u>Eureka User Testing 2</u>]]<br>
 
[[IS480 Team wiki: 2016T2 Eureka_User_Testing_2|<u>Eureka User Testing 2</u>]]<br>
 +
</center>
 +
</td></tr>
 +
</table>
 +
 +
<div style="background: #318ba2; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:18px; font-family:helvetica"><font color= #FFFFFF>User Testing 3</font></div>
 +
<table rules="all" width="87%" cellpadding="6" cellspacing="3" style="margin: 1em auto 1em auto; font-weight: normal">
 +
<tr style="background-color:#318ba2;"><th>Objectives</th></tr>
 +
<tr><td width="30%" border="1">
 +
- Assess the usability of our application in the day-to-day lunch ordering process<br>
 +
- Gather sponsor, pilot implementation company and relevant users’ feedback with regards to the heuristics and design of the existing functions of the current application<br>
 +
- Identify any usability issues that persist in the application<br>
 +
- Improvement on our application based on the results<br>
 +
- Managing of expectations<br>
 +
</td></tr>
 +
</table>
 +
 +
<table rules="all" width="87%" cellpadding="6" cellspacing="3" style="margin: 1em auto 1em auto; font-weight: normal">
 +
<tr style="background-color:#318ba2;"><th>Number of Users</th></tr>
 +
<tr><td width="30%" border="1">
 +
<center><b>Admin (2 Participants)</b></center>
 +
            -2 Lunch In-Charge from pilot implementation company (Eastman Chemical)<br>
 +
<center><b>Employee (10 Participants)</b></center>
 +
            -10 Employees from pilot implementation company (Eastman Chemical)
 +
</td></tr>
 +
</table>
 +
 +
<table rules="all" width="87%" cellpadding="6" cellspacing="3" style="margin: 1em auto 1em auto; font-weight: normal">
 +
<tr style="background-color:#318ba2;"><th>Date</th></tr>
 +
<tr><td width="30%" border="1">
 +
<center>16 March 2016
 +
</center>
 +
</td></tr>
 +
</table>
 +
<table rules="all" width="87%" cellpadding="6" cellspacing="3" style="margin: 1em auto 1em auto; font-weight: normal">
 +
<tr style="background-color:#318ba2;"><th>Full Documentation</th></tr>
 +
<tr><td width="30%" border="1">
 +
<center>Full Documentation of User Testing 3 can be found in
 +
[[IS480 Team wiki: 2016T2 Eureka_User_Testing_3|<u>Eureka User Testing 3</u>]]<br>
 
</center>
 
</center>
 
</td></tr>
 
</td></tr>
Line 246: Line 362:
 
=Reflection=
 
=Reflection=
 
===Team Reflection===
 
===Team Reflection===
[[Image:Eureka Mid terms Reflection.png|center|900px]]
+
[[Image:Eureka Finals Reflection.png|center|1000px]]

Latest revision as of 10:21, 14 April 2016

Eureka Team Logo.png


Eureka Meaning.png


Eureka bulb logo.png   HOME

Eureka bulb logo.png   OUR TEAM

Eureka bulb logo.png   PROJECT OVERVIEW

Eureka bulb logo.png   PROJECT MANAGEMENT

Eureka bulb logo.png   DOCUMENTATION

MAIN WIKI

MIDTERM WIKI

[[FINAL WIKI]]


Project Progress Summary

Eureka Slides Upload.png Eureka Video Upload.png Eureka Poster Upload.png

Project Highlights

Eureka Finals Highlights.png

Project Challenges


Besides sponsor, our team had to independently liaise with the client, Eastman Chemical.

As the company was located on Jurong Island, a secure location which requires security clearance to visit, we faced some degree of difficulty when arranging face-to-face meetings. As a result of this, most of the communication were done via e-mail and text messages and calls.

Although we were fortunate to receive upper management’s support for implementing our proposed solution, they delegated the task of coordinating our project to a lower level administrative staff. As a result of the lack of influence and commitment of the administrative staff to improve efficiency within the organisation, we faced several problems.

Our team has striven to mitigate these challenges by having having greater engagement of both the upper management and our sponsor as well frequently encouraging the administrative staff.


Project Management

Eureka Finals Management.png
Eureka Finals Management2.png


Project Scope

Eureka Finals Scope.png


Eureka Scope Description.png


Project Metrics

Eureka Schedule metrics graph.png
Eureka Schedule Metrics Explanation.png
Eureka Finals Effort Metrics.png
Eureka Bug Count Graph.png Bug Score Graph.png


Project Risk

Eureka Finals project risk.png


Technical Complexity

Scalability & Flexibility

As our aim is to come out with a new business initiative, one of the primary aim for our application is scalability. We must not only be able to cater to the current clients, but also the potential future companies who may join and use LunchTime. So scalability and flexibility are our key considerations when developing our application.

We noted that although LunchTime is targeted to help employees order their lunch, different companies may wish to order their foods at different timings, like 11am, 12noon etc. Or perhaps in the future, LunchTime could even extend further allowing companies the option to order Tea Break for their employees. This meant that our application needs to be flexible enough to handle orders from different timings, different companies and different canteens. So our approach to resolving this kind of many different association problems is to create an entity called Order Period.

Order Period

An Order Period is a time period in which employees of a particular company can log onto LunchTime to order food from the specified canteen. So, an Order Period is linked directly to one company and one canteen. This allows us to easily mix and match and track which company is ordering from which canteen for a given time period. So for instance, today, Company A is ordering food from Canteen A, Company B is ordering food from Canteen C; and tomorrow Company A is ordering from Canteen B, Company B is ordering food from Canteen A. Order Period also allows us to link additional features like company-wide discounts and reminders easily. This is to complement existing events at the client company whereby they offer $4 discounts to their employees when they order food on Fridays.

Cloud Solution

Next, in anticipation that our user base could grow substantially in the future, we decided to host our application on a cloud platform called eApps. Cloud services are well suited in our case as being a small company, we are extremely cost sensitive. Having servers running round the clock can add up to quite a substantial cost. Cloud solutions allow us to pay just what we use, and turn it off when there is zero utilization. In addition, as more users use LunchTime in future, we are able to respond to the rise in traffic quickly. With just a click of a button, we can determine the amount of server resources we want and scale up. We could also plan scheduled times such as lunch hours to scale up our application to handle the higher traffic. During weekends and non-meal hours, we can scale down to the bare minimum to save cost. Cloud solutions have helped our idea reap better returns by paying for only what we require.

Data Analytics

Lastly, we created some data analytics features to aid decision making for the admin using LunchTime. For example, Koh Bus currently has to fork out a capital in order to pay for the employees first, before they pay him at the end of the week. Setting aside more than enough money would mean wastage as these funds can be invested elsewhere, and setting aside too little would result in the driver not having enough cash to pay for the meals. As such, we used jfreechart to display each company’s spending pattern, helping us to get better visualization and insights. Currently, drawing the insights from the data, we can estimate that Koh Bus needs to set aside at least $50 per week to pay for all the meals in LunchTime.

Quality of Product

Intermediate Deliverables

Stage Specification Modules
Project Management Minutes Team, Supervisor & Sponsor
Metrics Schedule Metrics
Bug Metrics
Risk Management Risk Management
Change Management Change Management
Requirements Problems [Video]
Market Research Market Research
Analysis and Design Use Case, ER Diagram & Architectural Diagram]] Diagrams
Prototype Prototype
Technology Used Technologies
Testing User Test Plan Test Plan
User Testing 1 UT1
User Testing 2 UT2
User Testing 3 UT3
Trial Implementation Trial
Handover User Guide Video [Admin] [Employee]
Business Proposal Click Here
Deployment Guide Click Here
Handover Signoff [Click Here]

Quality

HIbernate Data Query


Eureka Mid terms Hibernate.png


Cloudinary


Eureka Mid terms Cloudinary.png


Quartz


Eureka Mid terms Quartz.png


Deployment

Eureka Mid terms Employee.png Eureka Mid terms Admin.png

Testing

User Testing 1
Objectives

-Gather sponsor, pilot implementation company and relevant users’ feedback with regards to the heuristics and design of the existing functions of the current application
-Identify any usability issues that persist in the application
-Improvement on our application based on the results
-Managing of expectations

Number of Users
Admin (6 Participants)
            -1 Sponsor
-2 Employees from pilot implementation company (Eastman)
-3 Office workers
Employee (16 Participants)
            -1 Sponsor
-2 Employees from pilot implementation company (Eastman)
-13 Office workers
Date
15 Dec 2015 to 30 Dec 2015
Full Documentation
Full Documentation of User Testing 1 can be found in

Eureka User Testing 1

Trial Implementation
Objectives

- Assess the usability of our application in the day-to-day lunch ordering process
- Gather sponsor, pilot implementation company and relevant users’ feedback with regards to the heuristics and design of the existing functions of the current application
- Identify any usability issues that persist in the application
- Improvement on our application based on the results
- Managing of expectations

Number of Users
Admin (2 Participants)

- Admin: 1 Participant
- Employee: 14 Participants

Date
25th January 2016 to 26th February 2016
Full Documentation
Full Documentation of Trial Implemenation can be found in

Eureka Trial Implementation

User Testing 2
Objectives

- Assess the usability of our application in the day-to-day lunch ordering process
- Gather sponsor, pilot implementation company and relevant users’ feedback with regards to the heuristics and design of the existing functions of the current application
- Identify any usability issues that persist in the application
- Improvement on our application based on the results
- Managing of expectations

Number of Users
Admin (2 Participants)
            -1 Sponsor
-1 Employee from pilot implementation company (Eastman)
Date
17 Feb 2016
Full Documentation
Full Documentation of User Testing 2 can be found in

Eureka User Testing 2

User Testing 3
Objectives

- Assess the usability of our application in the day-to-day lunch ordering process
- Gather sponsor, pilot implementation company and relevant users’ feedback with regards to the heuristics and design of the existing functions of the current application
- Identify any usability issues that persist in the application
- Improvement on our application based on the results
- Managing of expectations

Number of Users
Admin (2 Participants)
            -2 Lunch In-Charge from pilot implementation company (Eastman Chemical)
Employee (10 Participants)
            -10 Employees from pilot implementation company (Eastman Chemical)
Date
16 March 2016
Full Documentation
Full Documentation of User Testing 3 can be found in

Eureka User Testing 3

Reflection

Team Reflection

Eureka Finals Reflection.png