Skip to content

deco3500/adventure-time

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

16 Commits
 
 
 
 
 
 

Repository files navigation

adventure-time

Bargain Hunter group

Joel Achliles Matthew Chin Jairaldine Cruz Jaieden Girdler
42925550 43557293 43935118 42931953

Prototype

Please click the link to be directed to our working prototype. http://bh.jaieden.com/prototype/index.html

Our documentation may be found here: https://github.com/deco3500/adventure-time/blob/master/PrototypeDocumentation.pdf

Introduction

The project team Adventure Time is working on during Semester 2 2016 is “Bargain Hunter”, which is a website application made for students that want to save money by finding deals in their local area. Bargain Hunter allows users to set filters based on their particular interests and location. High quality posts attract more views/up-votes and can earn points which are used to earn a higher ranking within the Bargain Hunter community. With these features Bargain Hunter addresses the social journalism dilemma that news is distributed through multiple sources.

Concept

The idea behind the Bargain Hunter project is to acquire data from online social media, retailer websites, and user submitted information to direct them to one single news source. The data we are concerning ourselves with is “Bargains” or discounts. The purpose of this is to create a single source which people can turn to in order to find this information, rather than scanning several sources themselves, saving them time as well as money.

The concept is aimed mainly at students, aged from around 17-25. This target audience was chosen based on assumptions that the majority of students in this age category earn their own money (are not given free money from parents) and are on a relatively tight budget, consequently giving them the greatest benefit from using the application. Also, students are generally up to date with technology, and use social media often.

There are several current offerings which showcase discounts and bargains in Australia such as allthedeals.com.au, or ozbargain.com.au. However these sites do not crawl social media, or websites for information. As well as displaying user submitted deals, crawling multiple sources will allow Bargain Hunter to showcase discounts as soon as they are made visible online. Also, bargain hunter is unique because it tracks the user’s location and shows discounts in the area through the use of a map.

Team

Joel Achilles (Chief Design Officer)

Responsibilities

  • Interface design, graphics, front end coding

Contact Details

Matthew Chin (Chief User Experience Officer)

Responsibilities

  • Interface design, front end coding, user experience testing

Contact Details

Jairaldine Cruz (Chief Business Development Officer)

Responsibilities

  • Content management, sourcing discounts

Contact Details

Jaieden Girdler (Chief Information Technology Officer)

Responsibilities

  • Backend coding and data architecture design

Contact Details

Decision Making

Decisions for this project will be made by discussing the pro’s and con’s of concepts as a group. We are hoping this method should lead to a naturally resolved discussion where everyone agrees on the final decision and has had their fair share of input. However, in the case where the discussion does not naturally resolve, we will put the decision to a vote.

Performance

Team Adventure-Time will strive to achieve the best possible grade for the course. In the event of a poor/unsatisfactory grade the team will evaluate the processes undertaken for the assessment piece and revise a new strategy for obtaining the optimal grade for the next assessment.

Should the poor/unsatisfactory grade be obtained due to a member(s) of the team, the remaining members will seek advice from the tutors/lecturer to resolve the situation.

Conflict Resolution

####Reasons for conflict:

  • A team member is not contributing to the project.
  • A team member fails to attend team meetings.
  • Failed communication within the team.

Steps for resolution:

  • If a team member is not doing their part for the team, the team will meet to discuss the issue, and find the reason for the member not contributing to the project.

    • If the problem is beyond the team members control, then the task can be reassigned to another team member
    • If the member’s reason is not legitimate, they will be addressed and the problem will be discussed
    • If the problem is not solved, the team will consult a tutor, and if the problem persists, the team will contact the course coordinator
  • If a team member fails to attend team meetings without letting the group know first, they will firstly be informed that they missed a meeting, and they will be caught up on the information they missed.

    • If this happens frequently, the team member will be seen as not contributing to the project. A team meeting will be held and the team will find a solution. All members must be a part of this meeting.
    • If the problem still cannot be resolved, the team will consult the tutor, and if the problem persists the course coordinator will be contacted.
  • If there is a problem with communication between the team, or a specific member is failing to communicate, attempts will be made to restore the communication as soon as possible. These attempts will be made through:

    • Facebook Group
    • Emailing/texting/calling the team member/s directly
    • Discussion during the weekly face-to-face meeting.
    • If this fails, the team member/s will be considered as not contributing to the project. A meeting will be held and the team will find a solution to the problem. All members must attend this meeting.
    • If the conflict persists, a tutor or the course coordinator will be contacted.

Communications

Majority of group meetings will take place during the workshop sessions, to collaborate in person. If needed, the team will meet at at a group study room on campus at a time agreed on by the group. The team will communicate via Facebook for quick comments and discussions, but utilize the issues system on GitHub, and the comments feature on Google Drive for topics that are specific to a particular section or will contain information that we would like to keep.

Application files will be stored on GitHub, conforming to UQ’s Git guidelines of use. Documents and other relevant files will be stored in the shared Google Drive folder we have created. We will all strive to keep our work as updated as possible for the benefit of the other group members, however we must also be wary not to break the Git Repo.

Plan

Phase: Research

Proposal Documentation

Due: 23:59 Monday 5 Sep 2016

Upload this document to GitHub

Prepare Survey

Due: 18:00 Wednesday 7 Sep 2016

Goal:

Understand users of similar apps in the market and what design would attract users to use our application

Tasks:

Create a survey asking users of similar apps:

  • Why they use the application
  • What makes them come back to the application they use
  • Why do they prefer certain apps over others
  • What would the user change about the application they use

The survey will require specific questions so we are provided with useable feedback to create our interface design.

Launch Survey

Due: 18:00 Thursday 8 Sep 2016

Goal:

Gain as much feedback for the research as possible

Tasks:
  • Each team member will review survey questions then post the online survey link to their social networks, eg: Facebook, Google + Communities, friends and families
  • Post a photo with the url link + write a brief summary asking for feedback

Analysis of Survey

Due: 18:00 Tuesday 13 Sep 2016

Goal:

Understand the target user’s reasons for using a bargain hunting application to create a user interface

Tasks:
  • Analyse results from the survey and summarise the results from each question. Extract the key elements required for a basic bargain app.
  • Create summary graphical analysis of results for the standup

Survey results documentation on Github

Due: 23:59 Tuesday 13 Sep 2016

Goal:

Upload documentation on GitHub

Tasks:
  • Upload a project update documentation of progress on github
  • Write progress so far
  • Post google slides with results onto github page
  • Overview of what we’re doing next

Week 8 Stand Up

Due: 10:00 Wednesday 14 Sep 2016

Goal:

Present findings of survey to class, show github page

Tasks:
  • Prepare a google slides presentation of our progress so far.
  • Overview of what we planned to do
  • Showcase the questionnaire
  • Overview of Results
  • Summary of results
  • What we plan to do next
  • Documentation on github

Phase: Prototype #1

Prototype #1 Low fidelity wireframe

Due: 18:00 Thursday 15 Sep 2016

Goal:

Create an initial wireframe of the layout for the application

Tasks:
  • Extract information about layout from survey and adapt it to Bargain Hunter
  • Create a list of key elements to have on the application
  • Create a wireframe of the elements in paper form

Prototype #1 Wireframe with details

Due: 18:00 Sunday 18 Sep 2016

Goal:

Iterate over wireframe and add intensive details on hand-drawn paper

Tasks:
  • Make a more detailed version of the wireframe by adding specific writing and button names etc.
  • Establish non-changing elements of the app e.g. labels on the page, button names, placement of rating system etc.

Prototype #1 Low fidelity mockup

Due: 18:00 Tuesday 20 Sep 2016

Goal:

Have a final version of layout for the application

Tasks:
  • Figure out how the application would work by animating the wireframes on the paper prototype
  • Have a basic computer mockup print out of paper prototype ready for user testing

Prototype #1 Video explanation

Due: 18:00 Wednesday 21 Sep 2016

Goal:

Document the way that the application would work

Tasks:
  • Create a video explanation of the paper prototype, including the animation and look and feel of the application, and the reason behind why we chose to do it this way
  • User testing

Prototype #1 User testing and evaluation

Due: 18:00 Saturday 24 Sep 2016

Goal:

Get feedback on layout of application

Tasks:
  • Each team member should gather at least 1 friend and ask them if they are able to film a feedback session for our university project
  • Present the friend with the paper prototype and ask them to complete a task. (each member will be given one aspect to test, either through horizontal prototyping or vertical prototyping)
  • Film the testing session. Ask the friend to speak how they feel about completing certain tasks and talk through what they’re doing.
    • Does user know what the app is
    • Does user understand how app works
    • Is the app hard to navigate for user
    • Is the app appealing (visually and functionality)
    • Would the user use app again
    • Why is this app better/worse than existing apps in the market
    • What would the user change,etc)
  • Filming/recording the demonstration will allow the team to grasp where users are having trouble with the application and allow the team to alter the interface design where need be.

Prototype #1 Gather user testing results

Due: 18:00 Sunday 25 Sep 2016

Goal:

Gather results and extract points of improvement

Tasks:

Extract key points individually from video sessions

Collate feedback together and analyse key aspects to improve upon and translate into things to do for the prototype iteration

Prototype #1 User testing documentation on GitHub

Due: 23:59 Tuesday 27 Sep 2016

Goal:

Upload documentation on GitHub

Tasks:

Upload a project update documentation of progress on github

  • Show wireframe progress
  • Show video of paper prototype
  • Show videos of user testing
  • Show results of user test
  • Overview of what we’re doing next

Phase: Prototype #2

Prototype #2 Week 10 Stand Up

Due: 10:00 Wednesday 28 Sep 2016

Goal:

Present findings of wireframe and user testing to class

Tasks:
  • Talk through gitHub documentation of progress

Prototype #2 Redesign Interface

Due: 23:59 Wednesday 28 Sep 2016

Goal:

Take on user feedback for improvement

Tasks:

Adapt feedback from user testing and stand up to re-design the current prototype

Prototype #2 Digital Prototype basic mockup

Due: 23:59 Friday 30 Sep 2016

Goal:

Create base for digital prototype

Tasks:
  • Decide on official layout
  • Decide on official colour scheme
  • Convert the paper prototype to a digital platform

Prototype #2 Digital Prototype with content

Due: 23:59 Sunday 2 Oct 2016

Goal:

Iterate over digital prototype and add content

Tasks:

Collect information about one shop

  • Discounts
  • Cheap items at or under $5
  • Opening times
  • Location
  • Photos Upload content to basic mockup

Create filler words for mockup

Prototype #2 User testing

Due: 10:00 Wednesday 5 Oct 2016

Goal:

Test the user experience and user flow of the application

Tasks:
  • Use the justinmind digital prototype creator to test usability
  • Record feedback on video
  • Collate and summarise information on feedback
  • Apply feedback to content

Prototype #2 Content curation

Due: 23:59 Thursday 6 Oct 2016

Goal:

Fill in more content

Tasks:

Collect information about 2 - 5 more shops

  • Discounts
  • Cheap items at or under $5
  • Opening times
  • Location
  • Photos Upload content to digital mockup

Prototype #2 Stretch goal - Digital website layout

Due: 23:59 Friday 7 Oct 2016

Goal:

Create a working digital prototypes layout

Tasks:

Create a website with the basic layout of the application

  • Backend database for login
  • Front end html + css for layout

Prototype #2 Stretch goal - Digital website creation

Due: 23:59 Sunday 9 Oct 2016

Goal:

Create a working digital prototype ready for testing

Tasks:
  • Web server with mysql, phpmyadmin, web hosting, php
  • Database of pictures and items for sale

Prototype #2 Final user testing

Due: 23:59 Tuesday 11 Oct 2016

Goal:

Test the overall usability of the application

Tasks:

User test on website or justinmind application

  • Does user know what the app is
  • Does user understand how app works
  • Is the app hard to navigate for user
  • Is the app appealing (visually and functionality)
  • Would the user use app again
  • Why is this app better/worse than existing apps in the market
  • What would the user change,etc)

Prototype #2 User testing documentation on GitHub

Due: 23:59 Tuesday 11 Oct 2016

Goal:

Upload documentation on GitHub

Tasks:

Upload a project update documentation of progress on github

  • Show digital prototype progress
  • Show video of justinmind prototype
  • Show video of website
  • Show videos of user testing
  • Show results of user test
  • Overview of what we’re doing next

Prototype #2 User testing documentation on GitHub

Due: 23:59 Tuesday 11 Oct 2016

Goal:

Upload documentation on GitHub

Tasks:

Phase: Showcase and Reflection

Promotional material

Due: 10:00 Wednesday 12 Oct 2016

Goal:

Create highly creative and engaging promotional material that effectively explains your project and exhibits high production values

Tasks:
  • Digitally design a brochure and flyer for the application
  • Print designs to a high quality
  • Create a promotional video of application with live action shots and graphics
  • Link to website / justinmind prototype embedded into website

Week 12 standup

Due: 10:00 Wednesday 12 Oct 2016

Goal:

Present whole project to class

Tasks:
  • Talk through gitHub documentation of progress
  • Show promotional material

Tags

Social and mobile key concepts

  • #Collaboration
  • #Correlation
  • #Social
  • #Discounts
  • #PotentialNews

####Journalism and News key concepts

  • #CollateInformation
  • #Community
  • #LocalNews

About

Bargain Hunter group

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published