1. http://www.cit.ie
Virtual CIT
Third Year Group Project
Stephen Murray
Ren Tam Kai
Peter Kovacik
25/04/2015

2. Introduction and Project Overview
 Team Members
 Kai Tam
 Peter Kovacik
 Stephen Murray
 Application purpose
2015-09-24 www.cit.ie 2

3. Requirements
 Functional:
 Interface to the myCIT portal
 Social Media
 Timetables
 College Tour
 Indoor Maps
 Society Timetable
 Non-Functional:
 Scalable
 Localized
2015-09-24 3

4. Tools
 Software Tools:
 Android studio
 Web Hosting (Hostgator)
 Development on both physical device and emulator
 Content Management System (Joomla)
2015-09-24 4
Software tools used

5. Design
 Development of diagrams to help plan project
 High level approach taken
 Project is agile – design done in iterations
2015-09-24 5

6. Demonstration
2015-09-24 6

7. Integration /Testing
 Manual Integration
 Testing
 Ongoing
 Final Testing
2015-09-24 7

8. Evaluation - Student Services
 Approach Taken
 Set up web server
 Decide what CMS to use
 Find responsive Joomla Template (Helix Framework)
 Design web pages
 Integrate in app
 Issues
 Ambiguity over requirements
2015-09-24 8

9. Evaluation - Student Handbook
 Approach Taken
 Set permissions in manifest file to allow downloading to Device
 Put student handbook PDFs on the web server
 Design the UI
 Issues
 Downloading PDF to emulator
2015-09-24 9

10. Evaluation - Timetable
 Approach Taken
 Design – mobile friendly
 Plan how to retrieve the data
 Use of JSoup library to scrape the web page
 Fragments used to give a more dynamic interaction
 Use of Google’s Sliding Tab Layout library
 Issues
 If the CIT change web code then timetable feature will break
 Amount to time to scrape and parse data
 What would we have done differently
 Easier to scrape by manipulating URL
2015-09-24 10

11. Evaluation - College Tour
 Approach Taken
 Research how to integrate Google Tour Builder
 Find solution to not being able to use Google Tour Builder
 Show map with markers and images
 Issues
 Tour builder would not work for Android
 No other free alternatives
2015-09-24 11

12. Evaluation - Indoor Maps
 Approach Taken
 Research how to integrate Google Tour Builder
 Find solution to not being able to use Google Tour Builder
 Show map with markers and images
 Issues
 Tour builder would not work for Android
 No other free alternatives
2015-09-24 12

13. Evaluation - Society Timetable
 Approach Taken
 Group discussed potential features
 Society Timetable chosen
 Create database on webserver
 Retrieve data using PHP script
 Display daily society activity to user
 Show more details upon selection of activity
 What we would have done differently
 Use a popup feature instead of launching new activity
2015-09-24 13

14. Evaluation - Facebook
 Approach Taken
 Researched how to access data
 Register app – get api token
 HTTP access vs using SDK
 Retrieve all relevant data
 Create custom ListView for array adapter
 Issues
 Image sizes
 Shares counter
 What we would have done differently
 Image caching
 Volley library
 LruCache Class
2015-09-24 14

15. Evaluation - Twitter
 Approach Taken
 Researched how to access data
 Register app – get api token
 Retrieve all relevant data
 Create custom ListView for array adapter
 Issues
 Favourite/Retweet counter
 What we would have done differently
 Image caching
 Social Media containing Facebook and Twitter
2015-09-24 15

16. Future Enhancement
 Indoor Maps
 Integrate the Society feature with the indoor maps feature
 Design
 Contacts Feature
2015-09-24 16

17. Conclusions
 Interesting Project
 Learned a lot
 Importance of requirements and design
2015-09-24 17

18. http://www.cit.ie
Thank you