Mobile Technologies In Higher Education

794 views

Published on

Presentation about standards and requirements for mobile development and mobile portals for higher educational institutes

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
794
On SlideShare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Important information's for prospective students
  • Identify most important functionalities based on client requirements
  • OnLine Class Schedule, Emergency ContactsBus Shuttles Schedule, University DirectoryUniversity building Map and Location Guiding System
  • 1. Augmented Reality2. Localization and Routing3. Computer Vision Systems
  • Mobile Technologies In Higher Education

    1. 1. Study Case <br />American University in Cairo<br />By<br />Student Service Online <br />Mobile Technologies in Higher Education<br />
    2. 2. Stakeholders (Students, Admins, faculty … etc)<br />Mobile Design Layers & Standards<br />Existing Services & Products<br />Technologies & Infrastructure<br />Service Oriented Architecture<br />Agenda<br />
    3. 3. Students<br /> Calendar, Class Schedule, Bus Schedules, Announcements…<br />Faculty<br /> E-Learning, Student2Faculty Communication …<br />Administrators<br /> Remote Administration, Security …<br />Stakeholders<br />
    4. 4. Understanding users<br /> Fits in your pocket<br />More personal than the PC<br />Consistency across modes<br />Localization is intensified<br />Integrated devices, modes, products<br />Mobile Six Layers Design & StandardsAccording to Google …<br />
    5. 5. "Repetitive now“<br />User is someone checking for the same piece of information over and over again, like checking the same stock quotes or weather. [Using RSS Feed]<br />"Bored now“<br />Users who have time on their hands. People on trains or waiting in airports or sitting in cafes. For Entertaining and Surfing<br />"Urgent now”<br />Users who needs to find something specific fast 1 or 2 clicks tops, like the location of a Class or directions to the certain building. [ Location-Aware ] [prospective students]<br />Mobile User Types<br />
    6. 6. Fit on a small screen and no complicated text input.<br />Layout has to be clean, simple, but maintain the basic usability of the parent desktop application.<br />The "density of information" changes on a mobile phone, requiring designers to identify only the most essential parts of any given application. <br />Fits in your pocket<br />
    7. 7. Different functionalities, Different layouts and needs<br />If mobile applications are to be universal, it have to maintain patterns and designs across all screens.<br />Consistency<br />
    8. 8. The need to optimize for different devices, browsers, languages, countries and cultures.<br />Localization is intensified<br />
    9. 9. Few links and Less choice, more structure, but drill down further.<br />OR <br />As many links as possible but be shallower so users<br />get to their destination faster? <br />Finding that right balance sometimes means dropping as much functionality as possible. Once you have identified who will be using your site<br />Depth vs Breadth<br />
    10. 10. NCSU Libraries Mobile<br />http://www.lib.ncsu.edu/m/about.html<br />http://m.ncsu.edu/<br />UoMobile: University of Ottawa <br />http://m.uottawa.ca<br />http://www.fairchoicesystems.com/uomobile.php<br />Existing Services & Products<br />
    11. 11. Helping Booth or a Kiosk <br /> for information provding<br />Student2Faculty Virtual Office hours <br /> ( virtual meeting )<br />Mobile Health Care Services, keeping track of students and faculty health and dietary.<br /> A lot More <br />Other Services<br />
    12. 12. Java, JSP, .NET Languages<br />SharePoint Should Provide MobileView<br /> ( not good Idea though)<br />UoMobile, 3rd Party Services and Softwares<br />No Significant changes to infrastructure, Good Architecture and bunch of hardware.<br />Technologies & InfraStructure<br />
    13. 13. But All this is not feasible with out a solid and reliable Architecture.<br />Service Oriented Architecture<br />
    14. 14. Students & Faculty can contribute to the digital campus.<br />Forget Ordinary Database Applications. <br /> Think Intelligent, Decision Making & Multi-Agent Systems and Applications.<br />All we need is layout the platform (SandBox ) and let people play<br />This … What I Came to See<br />Made By AUC ... For AUC<br />
    15. 15. http://www.informationweek.com/blog/main/archives/2007/04/google_lays_out.html;jsessionid=NFBUVPZOERHX1QE1GHPSKHWATMY32JVN<br />References<br />

    ×