Shankar, R. T., & McAfee, F. X., & Harris, M. S., & Behara, R. S. (2013, June), Smart Phone App Development: A Multi-College Approach  Paper presented at 2013 ASEE Annual Conference & Exposition, Atlanta, Georgia. 10.18260/1-2--22455

\bibitem{asee_peer_22455}
  Shankar, R. T., \& McAfee, F. X., \& Harris, M. S., \& Behara, R. S. (2013, June), \emph{Smart Phone App Development: A Multi-College Approach}
  Paper presented at 2013 ASEE Annual Conference \& Exposition, Atlanta, Georgia.
  10.18260/1-2--22455

Ravi T. Shankar, Francis Xavier McAfee, Michael S Harris, and Ravi S Behara.  "Smart Phone App Development: A Multi-College Approach".  2013 ASEE Annual Conference & Exposition, Atlanta, Georgia, 2013, June.  ASEE Conferences, 2013.  https://peer.asee.org/22455 Internet.  13 Dec, 2024

\bibitem{asee_peer_22455}
  Ravi T. Shankar, Francis Xavier McAfee, Michael S Harris, and Ravi S Behara.
  "Smart Phone App Development: A Multi-College Approach".
  \emph{2013 ASEE Annual Conference \& Exposition, Atlanta, Georgia, 2013, June}.
  ASEE Conferences, 2013.
  https://peer.asee.org/22455 Internet.  13 Dec, 2024

@INPROCEEDINGS{asee_peer_22455
author = "Ravi T. Shankar, Francis Xavier McAfee, Michael S Harris, and Ravi S Behara"
title = "Smart Phone App Development: A Multi-College Approach"
booktitle = "2013 ASEE Annual Conference \& Exposition"
year = "2013"
month = "June"
address = "Atlanta, Georgia"
publisher = "ASEE Conferences"
note = {https://peer.asee.org/22455}
number = {10.18260/1-2--22455}
}

TY  - CPAPER
AB  -             Smart Phone App Development: A Multi-College ApproachIntroduction: Smart Phone App development is exciting and timely, with potential for jobs andrevenue. Real world successful App teams bring together professionals in arts, engineering,business, etc., to create elegant and user-friendly engineering marvels. Over the past three years,we have worked towards creating a microcosm of this at our university. State-of-the-art courseson this topic have been offered in three colleges, synergistically & concurrently, with the aim toteam up faculty members & students from various colleges to work together towards this ideal.Background: Apple and Google have championed the seamless integration of functionality (anengineering focus) with aesthetics, user-friendliness, relevance, and empathy. It was ourobjective to develop project oriented courses that integrated these aspects at the university level.However, there are two types of variability that matter: (1) even within a college of engineering,it is difficult to institute multi-disciplinary efforts – the skill set and backgrounds of the studentsand faculty members alike limit the quality and completeness of the project; and (2) If we nowwish to bring students and faculty members from various colleges (arts, business, engineering,and content providers, such as nursing and urban planning) together, differences in discipline-specific behaviors, perspectives, and focus may undermine the vision.Approach: (1) We first focused on reducing variability within the engineering domain by the useof a priori component development and design reuse; use of prototyped Apps; access tosophisticated API (application programming interface) libraries; open source and local techcommunity support; and clear separation of summative (with exam and quizzes) and formativeevaluations (with the projects judged by a group of professionals). Graduate students helped withthe first goal, while the work of previous semesters by other undergraduate students provided theprototypes for the current group. The third was facilitated by Google’s release of Android APIsand a free SDK (software development kit). The fourth was a consequence of both Google’sAndroid effort and our own local effort to disseminate. The last one resulted from iterativeimprovement and the authors’ training in eLearning. (2) We then invited faculty members fromgraphics and social science to judge our engineering projects. This opened up discussions on therole of their expertise, and their desire to participate more actively, along with their students.Because of this two stage involvement, the expectations were better understood & managed.Outcomes: A total of 450 students from various disciplines and levels (high school students toprofessional engineers) have undergone our program. Twenty six marketable Apps have beendeveloped. Several of our students have started small businesses to refine and launch their Apps.Discussion: We extended our collaboration to include the college of business last spring, withoutthis two-stage process of due diligence. Apps developed clearly reached a higher plateau of realworld metrics; but personality conflicts were more prevalent at both students and faculty levelsalike. We will now go back to a two-staged process and develop guidelines for clear separationof roles and responsibilities.Conclusion: We have developed a repeatable and robust process to enable multi-collegecollaboration in developing real-world experiences for undergraduate students across differentcolleges.References:Android (2012). Android website for open source tools useful to build Smart Phone Apps.Retrieved September 21, 2012 from http://developer.android.com/index.html
AU  - Ravi T. Shankar
AU  - Francis Xavier McAfee
AU  - Michael S Harris
AU  - Ravi S Behara
CY  - Atlanta, Georgia
DA  - 2013/06/23
PB  - ASEE Conferences
TI  - Smart Phone App Development: A Multi-College Approach
UR  - https://peer.asee.org/22455
DO  - 10.18260/1-2--22455
ER  -