8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 1/26
TEAM “R”
Chris Mowforth
Killian Polley
John McDermott
Daragh McSweeney
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 2/26
Panda Overview
To help promote awareness of the top 10most endangered animals worldwide.
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 3/26
The application itself will provide a list of thetop 10 animals under threat of extinction.
This will give the user a various amount of information about each animal.
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 4/26
The App will also have information on wildlifeorganisations and a guide on how to sponsor
an animal.
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 5/26
DevelopmentHow we did it, how it went
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 6/26
What we needed
from a latform
• Mobile app
• Easily accessed- viral?
• Rapid development
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 7/26
Options
• iPhone
• Android
• Windows Phone? Symbian?
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 8/26
iPhone•User-friendly
•Cool
•Expensive
•Difficult to distribute•Easy transition for developers?
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 9/26
Nokia?Symbian?
•HUGE number of handsets
•[Relatively] user-friendly
•Smart-phones for last decade
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 10/26
But...
• Handsets not what they were
• Developer’s nightmare
• Small community
•Few apps
• Nokia? Microsoft? WTF?
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 11/26
Android•Slick interface
•Suits our team (Java-based)
•Free [as in beer]
•Free [as in speech]•Rapid development
•Easy to ship
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 12/26
PandaBecause we couldn’t think of a better codename.
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 13/26
Overview
• Distributed team of 4
• Test-driven, extreme[ish] methodology
•Multi-platform
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 14/26
Android Dev wtf
• Native app
• Deliberately simple
•Easily deployed
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 15/26
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 16/26
Task management
• Based on WBS
• Used Pivotal Tracker to assign & track stuff
•Sometimes it worked!
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 17/26
Solution:
Pivotal•Transfer tasks from WBS
•Assigns them to peoplebased on how fast they
work, workload...
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 18/26
Change management-
roblems
• Fluid architecture
• Different people producing code
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 19/26
Change management-
solutions
• Use an SCM system
• XP- don’t commit anything that breaks the
build
• Use TDD (as much as possible)
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 20/26
Solution:
Git / Github•Undo button on
steroids
•See who did what
•Roll back bad design
decisions
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 21/26
Solution:
Testing•Write a test
•Let it fail
•Write the bare minimum code
needed to let it pass
•Sometimes restrictive?
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 22/26
Development Problems
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 23/26
New Platform
The Android system is a relatively newsoftware which means it is constantly evolving.
This meant that there was very few tutorialsout there to get help when developing theApp.
There was limited documentation on gettingstarted. This included APIs.
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 24/26
Slow
The process of designing the actual App wasextremely time consuming.
The emulator was very slow to use whichcaused our team a lot of frustration.
Just launching the App simulator itself took a
considerable amount of time
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 25/26
No one had a clue
After jumping straight into the decision of designing an android application, the generalconcern was “Ehhh has anyone any idea aboutdesigning apps”
No one on our team had ever worked withanything related with Android Apps. This
meant is was a huge learning curve.
8/7/2019 Team 'R' Final Presentation
http://slidepdf.com/reader/full/team-r-final-presentation 26/26
The finished product