HeaderSIS.jpg

IS480 Team wiki: 2014T1 Techne Logos Final

From IS480
Jump to navigation Jump to search
Technelogos.png

Home

 

Techne Logos

 

Project Overview

 

Project Management

 

Project Documentation

 
Project Dashboard Acceptance Mid-Term Final

Project Deliverables

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

Project Highlights

Final Project Scope:

TL Final Scope.png



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
Account

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

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

Notifications

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

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

NA

Project Management

Technical Complexity

TL technical complexity1.png

TL technical complexity2.png

TL technical complexity3.png

TL technical complexity4.png

Project Challenges

Technical
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


Non-Technical
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

Testing

Pitch

<youtube>https://www.youtube.com/watch?v=phJKCH8RbCA&feature=youtu.be</youtube>

Poster


Download our poster here: * Our Team Poster

Reflections

“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