IS480 Team wiki: 2014T1 Techne Logos Final

From IS480
Jump to navigation Jump to search



Techne Logos


Project Overview


Project Management


Project Documentation

Project Dashboard Acceptance Mid-Term Final

Project Deliverables

Check out our final presentation slides here!
Check out our CMS here!
Check out our mobile app here!

Project Aspect Document Type
Project Management Minutes and Bug Metrics
Design Prototypes and Diagrams
Testing User Tests

Project Highlights

Final Project Scope:

TL Final Scope.png

Summary of Changes:

Changes Acceptance Midterms Current
Functionality scope
No changes to functionalities
Reduced Scope:
  1. Login: Social Sign-in removed
  2. Notifications Module reduced- View notifications and user-triggered removed
  3. Lead Generation switched to tertiary functionality
Increased Priority:
  1. Coupons (Previously named as vouchers)
Reduced Scope:
  1. Tertiary functions dropped
Number of Functions
Primary Functions: 4
Secondary Functions: 4
Tertiary Functions: 3
Primary Functions: 4
Secondary Functions: 3
Tertiary Functions: 4
Primary Functions: 4
Secondary Functions: 3
Functions Completed
  1. Scan Product
  2. Account (Mobile)
  3. Account (CMS)
  4. Activity Feed/History
  5. Media Content
  6. Favourites
  7. Coupons (Mobile)
  8. Coupons (CMS)
  9. Tracking and Analysis

Changes in Requirements

Scope Changes:

Affected Functionality Acceptance Midterm Action Taken Current

Social Sign-in was first discussed with the sponsor as a convenient way for users to sign-in to the app

After some consideration and further discussions with our sponsor, we have decided that users might be uncomfortable with linking their social accounts.

This aspect of sign-in was eventually dropped as it has been decided that one form of login would be sufficient for the app.

Change made in midterm


Coupons(previously named vouchers) were initially planned as a tertiary function which is optional to the core functions of the application.

After some feedback from our sponsor, this function is understood to have a greater importance in the business process behind the app

Coupons were moved from tertiary to secondary scope, to be completed in Iteration 7

Change made in midterm


It was initially thought that notifications would be a sizable portion of the app arising from early discussions. Users can choose when to trigger notifications so that they only get notifications that they want.

As the project develop, the team realised that there was not much information that the app would need to push to users.

Scope for notifications significantly reduced to just system-level notifications, possibility of removing function from project scope

Notifications have removed from project scope as there it was decided that the workflow did not require pushing notifications

Lead Generation

Lead generation was intended as a way to encourage users towards greater brand engagement by directing them to sources where they can sign up with brands directly

Marketing campaigns for brands are overly varied and it would be too complex to cater for all types of campaigns

Scope has been changed to fix the form type to make information extraction and retrieval more streamlined

Functionality has been dropped from final implementation as it was decided that it is more of an add-on


Photo was intended as a way for users to take a photo of the image if it is not enabled for the advertisement

This was more of a reminder function

Function removed after midterms as it was decided that it was a non-essential function to the app


Social Sharing

Social sharing was intended as a way for users to share the advertisement with friends through social sites like Facebook, Google+ etc.


Function removed after midterms as it was decided that it was a non-essential function to the app and that it would be better to concentrate on improving the quality of the main functions


Project Management

Current Timeline

TL Slide5.PNG

Project Changes

TL Slide1.PNG

The project was rescoped after acceptance as the previous method of completely building the mobile app on Unity platform was too technically complex. The new changes reflect the use of a much smaller bridge module to enable communications between our third party image recognition engine and Unity for our mobile app.

TL Slide2.PNG

Closer to the midterms, the team had to perform a migration to a new version of the image recognition engine and hence, the current iteration at that time (Iteration 7) was extended to cater for the migration and any related testing.

TL Slide3.PNG

Due to time constraints, tertiary functionalities were removed to concentrate on the core functionaalities after migration to the new version of the image recognition engine. The analytics function was also pushed back to the last iteration. More internal testing rounds were added to the schedule as well to ensure that the core system is more robust, and the focus of user testing shifted to focus more on proof of concept.

TL Slide4.PNG

TL Slide5.PNG

Technical Complexity

TL technical complexity1.png
TL technical complexity2.png
TL technical complexity3.png
TL technical complexity4.png
TL technical complexity5.png
TL technical complexity6.PNG
TL technical complexity7.PNG
TL technical complexity8.PNG
TL technical complexity9.PNG

Project Challenges

Development in Unity 3D

Prior to this project, none of the team members had any experience with development in Unity 3D. The learning curve was steep and there were many things we came to understand when attempting to build our application using this engine:
- We had to familiarise ourselves with development in a 3D environment, using 3D-based build tools
- We had come to understand that adapting this engine for use in an application like ours would be too complex and rescoped our approach in building the application

Accommodating Team Schedules

The schedules of team members varied widely due to the different course that each member was undertaking and weekly team meetings alone were not enough to move the project along at a faster pace
- We took a more flexible approach and split the team up into even smaller groups to allow for greater flexibility in meeting scheduled deadlines
- We provided updates more constantly through our communication channels so that face-to-face meetings can be more effective when in session

Project Rescoping

As it was overly complex for the team to build the entire application in Unity 3D, the project had to be rebuilt with a different approach:
- A 'bridge' was built to communicate with Unity 3D and our 3rd party software so that the app can now be built natively
- Tertiary functionalities were removed to better enhance the core functions of the app


This section of testing contains the results from our latest test. To view earlier tests, please click here
The specifications for this second test is to verify the business idea and concept of the system as a viable proof of concept. The tests for the mobile system and the CMS were performed in separate sessions and the findings for these sessions were enlightening for the team.

The demographics of the participants found for this second test remain similar to those found in the first user test.
The testing of the mobile app continued to target mobile device users, and the CMS with advertisers/ media owners

Study Design Document (Mobile)
Study Design Document (CMS)

Mobile Application Study Result

The mobile application study was mainly focused on finding out if consumers would prefer scanning images of the advertisement themselves as compared to QR codes.

From the testing performed, we have discovered that most people find that scanning an advertising image was more aesthetically pleasing than scanning a QR code, with a score of 1 being the most unappealing and a score of 5 being the most appealing. The average scores were then compared, with advertising images gaining a higher average score than QR codes.

TL Mobile UT2.png
Appealingess of QR Codes and Advertising Images

In the second half of the test, users were assessed on which media they found more preferable to scan. The results this time were more balanced, with the preference for scanning the image directly being slightly higher.

TL Mobile2 UT2.png
Preference in Scanning QR Code vs. Advertising Image

It is worth noting that some of the comments received for the preference for QR codes were that they are more distinct to recognise so that they are more obvious to users that they should be scanned while those who prefer scanning the image like that they can essentially scan any image and it is perceived to be more high-tech to scan the image directly.

CMS Web Application Study Result

The CMS web application study was mainly focused on finding out if participants (advertisers/media owners) would find it more preferable to use scanning of the advertisement image and hence, the CMS than using QR codes to get product/ digital advertising information to their consumers.

The participants were first introduced to the CMS and the mobile companion app at the start of the study, where the workflow and business process behind the two systems will be explained. After the explanation of the workflow and business process, the participants are then asked to tasked with creating an advertisement to be that will be published to the mobile app. This is done so that the participants can gain a more hands-on experience with the business process behind the concept of the systems.

The findings from our study denote that in general, the participants found that the CMS was straightforward in its use, with the CMS obtaining an average score of 3.42 for its effectiveness in helping the participants to design mobile advertisement content.

TL CMS1.png
Effectiveness in Designing Content

In addition to the effectiveness of the CMS, the study also questioned participants on their preference to use QR codes or to directly use the advertisement image for their consumers to scan. The general preference was for the scanning the advertising app directly, one particular point that we noticed during the study was the participants who work with more high-end brands tended towards scanning the image directly, while those who did more everyday brands tended towards QR codes. When questioned further, it was because high-end brands tended to place more emphasis on the creative content and would prefer not to have QR codes on the advertising image as they are regarded not to be aesthetically pleasing.

TL CMS2.png
Preference of Using Scanning QR Code vs. Advertising Image

TL CMS3.png
Preference of Using Scanning QR Code vs. Advertising Image (Detailed)

This leads us to the next portion of our findings, which is that participants for the CMS also found that using the advertising image was more aesthetically pleasing, noting that while QR codes scan rather quickly, the overall look and feel of the advertisement would be different.

TL CMS4.png
Average Aesthetic Perception


“I learnt how to adapt to these new requirements and to manage these changes more effectively in addition to handling delays. I also learnt to consider factors more comprehensively into scheduling to ensure that the team is on schedule”
- Clarissa Goh

“Through interacting with our sponsors regularly, I learnt how to manage their expectations and was able to improve my communication and negotiation skills. I was also able to gain greater insight into how the advertising industry functions.”
- Paige Lim

“I learnt how to use new frameworks such as Slim that can ensure better security of the system and to leverage on external tools and frameworks that can help to enhance development.”
- Muhammad Mustaqim

“I learnt how to build effectively in a mobile Android environment. In addition, I learnt the intricacies of building systems that connect to different platforms.”
- Gerald Tan

“I gained deeper insights on quality control and testing design, having facilitated various internal testings and UTs. The key to a good testing design is to ensure that users are able to test the app smoothly without external impedance.”
- Wang Hao Bo

“I learnt a lot about UX and UI design in addition to those taught in IDP which has provided me with greater insights on building interfaces from the users' point of view.”
- Cheng Kam Him


Team Technelogos Small-page-001.jpg