a-card android app final presentation team simplicity

43
ACIT 4900 x Industry Project Practicum * Simplicity – Final Presentation

Upload: tratnayake

Post on 14-May-2015

109 views

Category:

Software


1 download

TRANSCRIPT

Page 1: A-Card Android App Final Presentation TEAM SIMPLICITY

ACIT 4900 x Industry Project Practicum

*Simplicity – Final

Presentation

Page 2: A-Card Android App Final Presentation TEAM SIMPLICITY

*Skills:

* Java

*PHP

*C#

*Web Dev (HTML,Graphics, CSS,JS,Jquery)

*Networking

*Cloud Computing

*AJAX

*XML/Tomcat

*ASP.NET

*Restful Services

*Database Management (MySQL, Schema Design, Maintenance)

*Project Management

*Software Processes

2

*Who we are

*4th Term BCIT Students

*ACIT 4900 Industry Projects Practicum

Page 3: A-Card Android App Final Presentation TEAM SIMPLICITY

3

Cecil Green Park House

6251 Cecil Green Park Road

Vancouver, BC

CANADA

*Our Client

Page 4: A-Card Android App Final Presentation TEAM SIMPLICITY

4

*University of British Columbia

*Est:1917

*Our Client: Who

Alumni Services Coordinator

Michael Duncan

Director,Operations and Planning:

Dianna DeBlaere

Page 5: A-Card Android App Final Presentation TEAM SIMPLICITY

5

*Our Client: What they do

*Goals:

* To link alumni with the University and with each other.

* To support the mission and activities of the University.

*Specific Projects:

* Trek Magazine

*Reunions

*Regional events

*Alumni Card (A-Card) Program

* Specific Projects:* Trek Magazine* Reunions* Regional events

Page 6: A-Card Android App Final Presentation TEAM SIMPLICITY

6

*Alumni Card (A-Card)

*Free for all UBC Alumni

*Discounts from several UBC Partners, Services and Venues

*UBC Library and Online Journals*

*Scanned at UBC locations (Robson Square , etc)

*Allows AlumniUBC to track usage.

* Our Client: What makes them different.

*A-Card Program

Quick Stats:• Uses a 14 digit codabar

format.• Average usage rate is

7000 new users per year.• What does 7000 users

look like?

Page 7: A-Card Android App Final Presentation TEAM SIMPLICITY

7

UBC IMAGINE DAY, approx 8000 people

Page 8: A-Card Android App Final Presentation TEAM SIMPLICITY

8*The System

1. Alumnus report to physical location to sign-up

2. User activates the Library Card function via A-Card website (or Library).

Page 9: A-Card Android App Final Presentation TEAM SIMPLICITY

*The Need

*The Need For The Project

1. Reduce the need for physical card *

2. Eliminate need for users to pick up the card in person @ UBC locations.

3. Increase usage of A-Card service.

9

Page 10: A-Card Android App Final Presentation TEAM SIMPLICITY

10*Our Project

To create an Android App that will

1. Allow Alumnus to sign-up for an A-Card digitally.

2. Display barcodes that will be able to be scanned at events/partner locations.

3. Display a list of current perks available to Alumnus.

Page 11: A-Card Android App Final Presentation TEAM SIMPLICITY

11

*Solution Components

*Mobile Application

*Cordova

*Back-end:Javascript

*Front-end: (HTML5,CSS,Bootstrap 3)Server-Side

*MySQL

*Webservice .php handlers

*Apache server on-site, Database server on-site

Page 12: A-Card Android App Final Presentation TEAM SIMPLICITY

12

*What is Phonegap / Cordova?

*Free and Open source framework that allows a developer to create mobile applications using standardized web APIs

*Technology Used

*HTML

*JavaScript

*CSS

*jQuery & AJAX are utilized by our team specifically to achieve the goals requested by the alumni UBC

Page 13: A-Card Android App Final Presentation TEAM SIMPLICITY

*Technical Architecture

*Single Page Application (SPA)

*Utilizes AJAX to interact with PHP Web Service

*PHP Web Service on Web server communicates with database server.

13

Page 14: A-Card Android App Final Presentation TEAM SIMPLICITY

* Technical Architecture II – 1. Assign Barcode Function

14

Page 15: A-Card Android App Final Presentation TEAM SIMPLICITY

*Security15

SSL: HTTPS

UBC Firewall

Page 16: A-Card Android App Final Presentation TEAM SIMPLICITY

*Implementation in Detail and The Process

16

Page 17: A-Card Android App Final Presentation TEAM SIMPLICITY

17

*Front End Team

David, Samir, Elton

*Layouts

*Views (Different resolutions)

*HTML5,CSS and Java Script

*Aesthetics

*HCI & Interface Design

*Validation

Page 18: A-Card Android App Final Presentation TEAM SIMPLICITY

18

*Back End Team*Anthony, T

*PHP Web Service / Web Service

*Client Admin Menu

*Database Management

*ERDs (Visio + MySQL workbench)

*Database Script’s (SQL)

*Management (PHPMyAdmin)

Page 19: A-Card Android App Final Presentation TEAM SIMPLICITY

19

*Workflow

1. Scope And Mission

2. Research (Cordova/Android)

3. Interact with database

4. Code “Assign Barcode”

5. Repurpose “Assign Barcode” to other functions

6. *Simultaneous Back End and Front End dev

7. Continuous Testing

Page 20: A-Card Android App Final Presentation TEAM SIMPLICITY

20

*Communication

Team Client Supervisor

Primary Face To Face E-Mail/Face to face weekly

Face To Face

Alternate Google Hangouts

Phone Calls Email

Page 21: A-Card Android App Final Presentation TEAM SIMPLICITY

21

*Version Control

*Github

*3 Branches

*Reverts

*Google Drive (Backup)

Page 22: A-Card Android App Final Presentation TEAM SIMPLICITY

*Development Environment

*Text Editors

*Sublime Text

*PHPMyAdmin

*MySQLWorkBench

*Photoshop

*Personal Server

*Cordova CLI

22

Page 23: A-Card Android App Final Presentation TEAM SIMPLICITY

*Timeline 23

Page 24: A-Card Android App Final Presentation TEAM SIMPLICITY

24

*Timeline

Week 1• Team

Formation• Planning and

documentation

• Cordova/Phonegap research

Week 2• Set up

development environment

• Start back-end functions

• Front end UI research

Week 3• Back-End

complete• Multi Platform

testing (screen sizes)

Week 4• Testing• Google Play

store• Final

documentation

• Nice-To-Haves

Week 5• Presentation

Page 25: A-Card Android App Final Presentation TEAM SIMPLICITY

*Week 1Planning, Documentation & Research

25

Page 26: A-Card Android App Final Presentation TEAM SIMPLICITY

26

*Week 1

*Scope and Mission clarification

*Proposal

*Use Cases

*ANDROID or IOS? BOTH??

*Native ? Phonegap? Cordova? Titanium?

*Research

Page 27: A-Card Android App Final Presentation TEAM SIMPLICITY

Cordova/Phonegap

*Cross Platform

*HTML, CSS, JavaScript

* jQuery, AJAX

Native Android* Java

*Android platform only

*Can use jQuery Mobile and other frameworks to SKIN UI

*Cordova vs Native Android

27

Page 28: A-Card Android App Final Presentation TEAM SIMPLICITY

*Week 2Development Environment, UI and Assign

Barcode

28

Page 29: A-Card Android App Final Presentation TEAM SIMPLICITY

29

*Week 2

*Set-up Cordova

*Tutorials

* DB Planning

* DB Creation

*GENERATE THE BARCODE

*PHP Web Service testing.

* Fluid UI to create mockups.

Page 30: A-Card Android App Final Presentation TEAM SIMPLICITY

*Databases30

Page 31: A-Card Android App Final Presentation TEAM SIMPLICITY

*jQuery Barcode31

Page 32: A-Card Android App Final Presentation TEAM SIMPLICITY

*Interacting with the DB through a PHP Web

servce.32

Page 33: A-Card Android App Final Presentation TEAM SIMPLICITY

*Fluid UI33

Page 34: A-Card Android App Final Presentation TEAM SIMPLICITY

*Week 3Back-End complete, Front-end Design &

Testing34

Page 35: A-Card Android App Final Presentation TEAM SIMPLICITY

*Dynamic Barcode Size35

Page 36: A-Card Android App Final Presentation TEAM SIMPLICITY

*Week 4Testing & Nice To Haves

36

Page 37: A-Card Android App Final Presentation TEAM SIMPLICITY

37 *Week 4

*Google Play Store/ Google Plus Community

*Testing

*A-CARD ADMIN (nice to have)

*Icons (Graphic Designer)

Page 38: A-Card Android App Final Presentation TEAM SIMPLICITY

*Week 5

*Kept in contact with UBC IT

*Got HTTPS enabled

*Waiting on Signed certificate

*Presentation

38

Page 39: A-Card Android App Final Presentation TEAM SIMPLICITY

*Difficulties

39

Page 40: A-Card Android App Final Presentation TEAM SIMPLICITY

40

*Difficulties

*Determining Scope

*EMULATOR SPEED.

*Development Environment (Phonegap?Titanium?Native?)

*Generating Barcode

*Database integration

*Screen Sizing

*HTTPS

*Time crunch

Page 41: A-Card Android App Final Presentation TEAM SIMPLICITY

41

*Demo

Page 42: A-Card Android App Final Presentation TEAM SIMPLICITY

What we would do differently

*Testing (Murphys Law)

*ASSIGN DATES TO EVERYTHING

*Consider security early on.

*Research is a normal part of a project.

What Went Well*Stuck to a schedule

(Deadlines)

*Left slack time in schedule

*SAM CROFT TUTORIALS.

*Client was extremely easy to work with

42

*Conclusion

Page 43: A-Card Android App Final Presentation TEAM SIMPLICITY

*Questions?

43