Dissertation Submitted to the Graduate Faculty of Auburn University in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy

Total Page:16

File Type:pdf, Size:1020Kb

Dissertation Submitted to the Graduate Faculty of Auburn University in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy Repatterning: Improving the Reliability of Android Applications with an Adaptation of Refactoring by Bradley Christian Dennis A dissertation submitted to the Graduate Faculty of Auburn University in partial fulfillment of the requirements for the Degree of Doctor of Philosophy Auburn, Alabama August 2, 2014 Keywords:Refactoring, Code Smells, Patterns, Non-functional Requirements, Verification Copyright 2014 by Bradley Christian Dennis Committee: David Umphress, Chair, Associate Professor of Computer Science and Software Engineering James Cross, Professor of Computer Science and Software Engineering Dean Hendrix, Associate Professor of Computer Science and Software Engineering Jeffrey Overbey, Assistant Research Professor of Computer Science and Software Engineering Abstract Studies of Android applications show that NullPointerException, OutofMemoryError, and BadTokenException account for a majority of errors observed in the real world. The technical debt being born by Android developers from these systemic errors appears to be due to insufficient, or erroneous, guidance, practices, or tools. This dissertation proposes a re- engineering adaptation of refactoring, called repatterning, and pays down some of this debt. We investigated 323 Android applications for code smells, corrective patterns, or enhancement patterns related to the three exceptions. I then applied the discovered patterns to the locations suggested by the code smells in fifteen randomly selected applications. I measured the before and after reliability of the applications and observed a statistically significant improvement in reliability for two of the three exceptions. I found repatterning had a positive effect on the reliability of Android applications. This research demonstrates how refactoring can be generalized and used as a model to affect non-functional qualities other than the restructuring related attributes of maintainability and adaptability. ii Acknowledgments As all journeys must come to an end, my decade long journey towards a doctorate is finally coming to a close. The many struggles, detours and failures were too great to overcome alone, and as such, I am eternally indebted and grateful to those that supported me on this effort. First, I would like to thank my wife, Katya, and son, Josey, their patience and tolerance has proven much greater than mine. Second, without the gracious support of my father, brother, and father-in-law, John “Dad”, Brian, and Vlad, and their wives, Brenda, Shannon, and Sasha, I never could have completed this work. I extend a special acknowledgement to my advisor, Dr. Umphress; his support for me never wavered and over the years he has become a valued mentor and role model. A warm thanks is also extended to my committee, Dr. Cross, Dr. Hendrix, and Dr. Overbey, as their insights and guidance have expanded and improved my research greatly. I would like to thank Hasanur Rahaman, who helped build and collect the initial application catalog, Dr. Paul Stermer who helped with the experimental design and methodology, and finally, Joseph Douglas (aka Sylvan Kills), for his many hours editing and proofreading my dissertation. iii Table of Contents Abstract ........................................................................................................................................... ii Acknowledgments.......................................................................................................................... iii List of Figures ............................................................................................................................... vii List of Tables ................................................................................................................................. vi Chapter 1 – Introduction ................................................................................................................. 1 1.1 Background ........................................................................................................................... 1 1.2 Framework ............................................................................................................................ 2 1.3 Statement of the Problem ...................................................................................................... 4 1.4 Purpose of the Study ............................................................................................................. 5 1.5 Limitations, Assumptions, and Delimitations ....................................................................... 6 1.6 Definition of Key Terms ....................................................................................................... 7 Chapter 2 – Literature Review ........................................................................................................ 9 2.1 Introduction ........................................................................................................................... 9 2.2 Android Mobile Operating System (MOS) and Application Architecture ......................... 10 2.3 Android Reliability Issues ................................................................................................... 13 2.4 Impact on the Developer of Failures ................................................................................... 20 2.5 Application Quality Guidance ............................................................................................. 21 2.6 Android Books .................................................................................................................... 29 2.7 Android Verification Tools ................................................................................................. 29 Chapter 3 – Research Description................................................................................................. 35 3.1 Introduction ......................................................................................................................... 35 3.2 Developer Perceptions......................................................................................................... 36 3.3 Developer Adoption ............................................................................................................ 37 3.4 Refactoring as Part of a Larger Process .............................................................................. 38 3.5 Bad Smells in Other Abstractions ....................................................................................... 40 3.6 Refactoring the Restructuring Activity ............................................................................... 40 3.7 Refactoring Limitations....................................................................................................... 42 3.8 Repatterning ........................................................................................................................ 45 3.9 Conclusion ........................................................................................................................... 47 Chapter 4 – Methods & Results .................................................................................................... 49 4.1 Introduction ......................................................................................................................... 49 4.2 Exploratory Studies Framework.......................................................................................... 50 4.3 Smell Study Methodology ................................................................................................... 54 iv 4.4 Smell Study Results ............................................................................................................ 55 4.5 Corrective Pattern Study Methodology ............................................................................... 61 4.6 Corrective Pattern Study Results ........................................................................................ 61 4.7 Enhancement Pattern Study Methodology .......................................................................... 69 4.8 Enhancement Pattern Study Results .................................................................................... 69 4.9 Reliability Experiment Methodology .................................................................................. 73 4.10 Reliability Experiment Results ......................................................................................... 81 Chapter 5 – Summary, Conclusions & Future Work .................................................................... 87 5.1 Summary ............................................................................................................................. 87 5.2 Conclusions ......................................................................................................................... 90 5.3 Future Work ........................................................................................................................ 96 References ................................................................................................................................... 100 Appendix A – Application Catalog............................................................................................. 109 Appendix B – Pre-test Results .................................................................................................... 131 Appendix C – Data Collection Instruments ...............................................................................
Recommended publications
  • Gmail Integration Technical Reference Since Its Initial Release
    PureConnect® 2020 R1 Generated: 18-February-2020 Gmail Integration Content last updated: 20-June-2019 See Change Log for summary of Technical Reference changes. Abstract CIC offers support for Gmail. This document describes how to configure IMAP and SMTP to integrate with Gmail in CIC using OAuth protocol authentication. For the latest version of this document, see the PureConnect Documentation Library at: http://help.genesys.com/cic. For copyright and trademark information, see https://help.genesys.com/cic/desktop/copyright_and_trademark_information.htm. 1 Table of Contents Table of Contents 2 Introduction to the CIC Integration with Gmail 3 About Gmail 3 About CIC 3 Requirements 3 Concepts and terminology 3 Configuration Overview 4 Re-run IC Setup Assistant 4 Configure the Google Domain 5 Configure Mail in Interaction Administrator 5 Configure a Mailbox in Interaction Administrator 6 Test the Integration 6 Change Log 7 2 Introduction to the CIC Integration with Gmail Integration of CIC with Gmail provides outsourcing of email capabilities and using OAuth with the integration provides a safer environment. About Gmail Gmail, part of Google Apps for Work, is a web-based hosted email application offering message threading, message labels, message search, and spam filtering. About CIC Customer Interaction Center (CIC) is a suite of contact center applications that has interactive voice response and IP/PBX capabilities. CIC supports several interaction management client applications. Starting with CIC 2015 R3, Interaction Desktop replaces Interaction Client .NET Edition as the primary CIC client. Requirements Starting with CIC 2015 R2, the integration supports OAuth 2.0. Following are the requirements for the CIC Integration with Gmail: Gmail with OAuth 2.0 CIC 2015 R2 or later Note: OAuth is only available for customers using Google Apps for Work.
    [Show full text]
  • Vulnerability Report Attacks Bypassing Confidentiality in Encrypted PDF
    Vulnerability Report Attacks bypassing confidentiality in encrypted PDF Jens M¨uller1, Fabian Ising2, Vladislav Mladenov1, Christian Mainka1, Sebastian Schinzel2, J¨orgSchwenk1 May 16, 2019 1Chair for Network and Data Security 2FH M¨unsterUniversity of Applied Sciences Abstract In this report, we analyze PDF encryption and show two novel techniques for breaking the confidentiality of encrypted documents. Firstly, we abuse the PDF feature of partially encrypted documents to wrap the encrypted part of the document within attacker-controlled content and therefore, exfiltrate the plaintext once the document is opened by a legitimate user. Secondly, we abuse a flaw in the PDF encryption specification allowing an attacker to arbitrarily manipulate encrypted content without knowing the cor- responding key/password. The only requirement is one single block of known plaintext, which we show is fulfilled by design. By using exfiltration channels our attacks allow the recovery of the entire plaintext or parts of it within an encrypted document. The attacks rely only on standard compliant PDF features. We evaluated our attacks on 27 widely used PDF viewers and found all of them vulnerable. 1 Contents 1 Background4 1.1 Portable Document Format (PDF) . .4 1.2 PDF Encryption . .6 1.3 PDF Interactive Features . .7 2 Attacker Model8 3 PDF Encryption: Security Analysis9 3.1 Partial Encryption . .9 3.2 CBC Malleability . 10 3.3 PDF Interactive Features . 12 4 How To Break PDF Encryption 14 4.1 Direct Exfiltration (Attack A) . 14 4.1.1 Requirements . 15 4.1.2 Direct Exfiltration through PDF Forms (A1) . 15 4.1.3 Direct Exfiltration via Hyperlinks (A2) .
    [Show full text]
  • Copyrighted Material
    33_754935 bindex.qxp 11/7/05 10:09 PM Page 345 Index Applications Menu, 42–43, 68–71 • Symbols • Applixware Office package, 15 appointments, tracking, 210 * (asterisk), 249, 251 archives, packing and unpacking (tar), 20, \ (backslash), 248 337–338 - (dash), 94 arguments, command line, 247 . (dot), 92 asterisk (*), 249, 251 ! (exclamation point), 252–253 Asymmetric DSL (ADSL), 108–109 / (forward slash), 79, 81 attachments, e-mail, 154 > (greater-than sign), 249 audio CDs, playing, 221–223 - (hyphen), 95 authentication, 292 < (less-than sign), 249 automatic command completion, 250 . (period), 96 automatic login, 40, 318–319, 325 | (pipe), 248 ? (question mark), 251 " (quotation marks), 247 ; (semicolon), 248 • B • [] (square brackets), 252 backdoor, 292 .. (two dots or dot-dot), 92 background, desktop, 73–74, 75–76 backing up files, 20 backslash (\), 248 • A • base station, 129 bash (Bourne Again Shell) access point, wireless LAN, 129, 131 automatic command completion, 250 Adobe Portable Document Format. See PDF combining commands, 248 ADSL (Asymmetric DSL), 108–109 described, 47–48, 246 AES (Advanced Encryption Standard), 129 error messages, saving to file, 249–250 aggregator, RSS, 185 file, command input from, 249 AIM (America Online instant messaging output, saving to file, 249 service), 54, 161–162 repeating previously typed commands, Akregator news reader, 54, 185–186 252–253 amaroK music player, 224 syntax, 247–248 Apache Web server, 16 wildcards, 251–252 applets, 68, 75 bastion host, 293 application gateway, 292 bit bucket, 250 applications Blam RSS reader, 54 controlling, 18–19 block device, 94 development, 17 Bluetooth wireless, 20, 271 e-mail, 152–153 bookmark field, 200 GNOME Desktop, illustrated,COPYRIGHTED 64 boot menu MATERIAL items, installing, 27–28 GNU, 343 boot process, starting and stopping services, installing at setup, 32 263–264 KDE Desktop, illustrated, 64 booting, 26–27, 39–40 Linux packages, 11 Bourne Again Shell.
    [Show full text]
  • Your Voice Assistant Is Mine: How to Abuse Speakers to Steal Information and Control Your Phone ∗ †
    Your Voice Assistant is Mine: How to Abuse Speakers to Steal Information and Control Your Phone ∗ y Wenrui Diao, Xiangyu Liu, Zhe Zhou, and Kehuan Zhang Department of Information Engineering The Chinese University of Hong Kong {dw013, lx012, zz113, khzhang}@ie.cuhk.edu.hk ABSTRACT General Terms Previous research about sensor based attacks on Android platform Security focused mainly on accessing or controlling over sensitive compo- nents, such as camera, microphone and GPS. These approaches Keywords obtain data from sensors directly and need corresponding sensor invoking permissions. Android Security; Speaker; Voice Assistant; Permission Bypass- This paper presents a novel approach (GVS-Attack) to launch ing; Zero Permission Attack permission bypassing attacks from a zero-permission Android application (VoicEmployer) through the phone speaker. The idea of 1. INTRODUCTION GVS-Attack is to utilize an Android system built-in voice assistant In recent years, smartphones are becoming more and more popu- module – Google Voice Search. With Android Intent mechanism, lar, among which Android OS pushed past 80% market share [32]. VoicEmployer can bring Google Voice Search to foreground, and One attraction of smartphones is that users can install applications then plays prepared audio files (like “call number 1234 5678”) in (apps for short) as their wishes conveniently. But this convenience the background. Google Voice Search can recognize this voice also brings serious problems of malicious application, which have command and perform corresponding operations. With ingenious been noticed by both academic and industry fields. According to design, our GVS-Attack can forge SMS/Email, access privacy Kaspersky’s annual security report [34], Android platform attracted information, transmit sensitive data and achieve remote control a whopping 98.05% of known malware in 2013.
    [Show full text]
  • Cisco SCA BB Protocol Reference Guide
    Cisco Service Control Application for Broadband Protocol Reference Guide Protocol Pack #60 August 02, 2018 Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Android (Operating System) 1 Android (Operating System)
    Android (operating system) 1 Android (operating system) Android Home screen displayed by Samsung Nexus S with Google running Android 2.3 "Gingerbread" Company / developer Google Inc., Open Handset Alliance [1] Programmed in C (core), C++ (some third-party libraries), Java (UI) Working state Current [2] Source model Free and open source software (3.0 is currently in closed development) Initial release 21 October 2008 Latest stable release Tablets: [3] 3.0.1 (Honeycomb) Phones: [3] 2.3.3 (Gingerbread) / 24 February 2011 [4] Supported platforms ARM, MIPS, Power, x86 Kernel type Monolithic, modified Linux kernel Default user interface Graphical [5] License Apache 2.0, Linux kernel patches are under GPL v2 Official website [www.android.com www.android.com] Android is a software stack for mobile devices that includes an operating system, middleware and key applications.[6] [7] Google Inc. purchased the initial developer of the software, Android Inc., in 2005.[8] Android's mobile operating system is based on a modified version of the Linux kernel. Google and other members of the Open Handset Alliance collaborated on Android's development and release.[9] [10] The Android Open Source Project (AOSP) is tasked with the maintenance and further development of Android.[11] The Android operating system is the world's best-selling Smartphone platform.[12] [13] Android has a large community of developers writing applications ("apps") that extend the functionality of the devices. There are currently over 150,000 apps available for Android.[14] [15] Android Market is the online app store run by Google, though apps can also be downloaded from third-party sites.
    [Show full text]
  • Living Without Google on Android
    Alternative for Google Apps on Android - living without Google on Android Android without any Google App? What to use instead of Hangouts, Map, Gmail? Is that even possible? And why would anyone want to live without Google? I've been using a lot of different custom ROMs on my devices, so far the two best: plain Cyanogenmod 11 snapshot on the Nexus 4[^1], and MIUI 2.3.2 on the HTC Desire G7[^2]. All the others ( MUIU 5, MIUI 6 unofficial, AOKP, Kaos, Slim, etc ) were either ugly, unusable, too strange or exceptionally problematic on battery life. For a long time, the first step for me was to install the Google Apps, gapps packages for Plays Store, Maps, and so on, but lately they require so much rights on the phone that I started to have a bad taste about them. Then I started to look for alternatives. 1 of 5 So, what to replace with what? Play Store I've been using F-Droid[^3] as my primary app store for a while now, but since it's strictly Free Software[^4] store only, sometimes there's just no app present for your needs; aptoide[^5] comes very handy in that cases. Hangouts I never liked Hangouts since the move from Gtalk although for a little while it was exceptional for video - I guess it ended when the mass started to use it in replacement of Skype and its recent suckyness. For chat only, check out: ChatSecure[^6], Conversations[^7] or Xabber[^8]. All of them is good for Gtalk-like, oldschool client and though Facebook can be configured as XMPP as well, I'd recommend Xabber for that, the other two is a bit flaky with Facebook.
    [Show full text]
  • Android Operating System
    Software Engineering ISSN: 2229-4007 & ISSN: 2229-4015, Volume 3, Issue 1, 2012, pp.-10-13. Available online at http://www.bioinfo.in/contents.php?id=76 ANDROID OPERATING SYSTEM NIMODIA C. AND DESHMUKH H.R. Babasaheb Naik College of Engineering, Pusad, MS, India. *Corresponding Author: Email- [email protected], [email protected] Received: February 21, 2012; Accepted: March 15, 2012 Abstract- Android is a software stack for mobile devices that includes an operating system, middleware and key applications. Android, an open source mobile device platform based on the Linux operating system. It has application Framework,enhanced graphics, integrated web browser, relational database, media support, LibWebCore web browser, wide variety of connectivity and much more applications. Android relies on Linux version 2.6 for core system services such as security, memory management, process management, network stack, and driver model. Architecture of Android consist of Applications. Linux kernel, libraries, application framework, Android Runtime. All applications are written using the Java programming language. Android mobile phone platform is going to be more secure than Apple’s iPhone or any other device in the long run. Keywords- 3G, Dalvik Virtual Machine, EGPRS, LiMo, Open Handset Alliance, SQLite, WCDMA/HSUPA Citation: Nimodia C. and Deshmukh H.R. (2012) Android Operating System. Software Engineering, ISSN: 2229-4007 & ISSN: 2229-4015, Volume 3, Issue 1, pp.-10-13. Copyright: Copyright©2012 Nimodia C. and Deshmukh H.R. This is an open-access article distributed under the terms of the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.
    [Show full text]
  • Atom-Feeds for Inspire
    ATOM-FEEDS FOR INSPIRE - Perspectives and Solutions for INSPIRE Download Services in NRW WWU Münster Institute for Geoinformatics Heisenbergstraße 2 48149 Münster Masterthesis in Geoinformatics 1. Supervisor: Hon.-Prof. Dr. Albert Remke 2. Supervisor: Dr. Christoph Stasch Arthur Rohrbach [email protected] November 2014 I Plagiatserklärung der / des Studierenden Hiermit versichere ich, dass die vorliegende Arbeit ATOM-Feeds for INSPIRE – Perspectives and Solutions for Download Services in NRW selbstständig verfasst worden ist, dass keine anderen Quellen und Hilfsmittel als die angegebenen benutzt worden sind und dass die Stellen der Arbeit, die anderen Werken – auch elektronischen Medien – dem Wortlaut oder Sinn nach entnommen wurden, auf jeden Fall unter Angabe der Quelle als Entlehnung kenntlich gemacht worden sind. _____________________________________ (Datum, Unterschrift) Ich erkläre mich mit einem Abgleich der Arbeit mit anderen Texten zwecks Auffindung von Übereinstimmungen sowie mit einer zu diesem Zweck vorzunehmenden Speicherung der Arbeit in eine Datenbank einverstanden. _____________________________________ (Datum, Unterschrift) II Abstract One proposed solution for providing Download Services for INSPIRE is using pre- defined ATOM-Feeds. Up to now the realization of ATOM-Feeds in NRW is still at the beginning. This master thesis will investigate possible solutions in order to help developing a methodology for the implementation of pre-defined INSPIRE Download Services in NRW. Following research questions form the basis of the thesis: What implementing alternatives for automatic generation of ATOM-Feeds based on ISO metadata exist? How do the identified solutions suit in order to fulfil the requirements of NRW? In the first step required technologies are introduced, including ATOM, OpenSearch and OGC standards.
    [Show full text]
  • ISCRAM2005 Conference Proceedings Format
    Yee et al. The Tablecast Data Publishing Protocol The Tablecast Data Publishing Protocol Ka-Ping Yee Dieterich Lawson Google Medic Mobile [email protected] [email protected] Dominic König Dale Zak Sahana Foundation Medic Mobile [email protected] [email protected] ABSTRACT We describe an interoperability challenge that arose in Haiti, identify the parameters of a general problem in crisis data management, and present a protocol called Tablecast that is designed to address the problem. Tablecast enables crisis organizations to publish, share, and update tables of data in real time. It allows rows and columns of data to be merged from multiple sources, and its incremental update mechanism is designed to support offline editing and data collection. Tablecast uses a publish/subscribe model; the format is based on Atom and employs PubSubHubbub to distribute updates to subscribers. Keywords Interoperability, publish/subscribe, streaming, synchronization, relational table, format, protocol INTRODUCTION After the January 2010 earthquake in Haiti, there was an immediate need for information on available health facilities. Which hospitals had been destroyed, and which were still operating? Where were the newly established field clinics, and how many patients could they accept? Which facilities had surgeons, or dialysis machines, or obstetricians? Aid workers had to make fast decisions about where to send the sick and injured— decisions that depended on up-to-date answers to all these questions. But the answers were not readily at hand. The U. S. Joint Task Force began a broad survey to assess the situation in terms of basic needs, including the state of health facilities. The UN Office for the Coordination of Humanitarian Affairs (OCHA) was tasked with monitoring and coordinating the actions of the many aid organizations that arrived to help.
    [Show full text]
  • History and Evolution of the Android OS
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Springer - Publisher Connector CHAPTER 1 History and Evolution of the Android OS I’m going to destroy Android, because it’s a stolen product. I’m willing to go thermonuclear war on this. —Steve Jobs, Apple Inc. Android, Inc. started with a clear mission by its creators. According to Andy Rubin, one of Android’s founders, Android Inc. was to develop “smarter mobile devices that are more aware of its owner’s location and preferences.” Rubin further stated, “If people are smart, that information starts getting aggregated into consumer products.” The year was 2003 and the location was Palo Alto, California. This was the year Android was born. While Android, Inc. started operations secretly, today the entire world knows about Android. It is no secret that Android is an operating system (OS) for modern day smartphones, tablets, and soon-to-be laptops, but what exactly does that mean? What did Android used to look like? How has it gotten where it is today? All of these questions and more will be answered in this brief chapter. Origins Android first appeared on the technology radar in 2005 when Google, the multibillion- dollar technology company, purchased Android, Inc. At the time, not much was known about Android and what Google intended on doing with it. Information was sparse until 2007, when Google announced the world’s first truly open platform for mobile devices. The First Distribution of Android On November 5, 2007, a press release from the Open Handset Alliance set the stage for the future of the Android platform.
    [Show full text]
  • Print Journalism's Framing of Female Candidates in The
    Joining the World of Journals Welcome to the nation’s first and, to our knowledge, only undergraduate research journal in communi- cations. We discovered this fact while perusing the Web site of the Council on Undergraduate Research, which lists and links to the 60 or so undergraduate research journals nationwide (http://www.cur.org/ugjournal. html). Some of these journals focus on a discipline (e.g., Journal of Undergraduate Research in Physics), some are university-based and multidisciplinary (e.g., MIT Undergraduate Research Journal), and some are university-based and disciplinary (e.g., Furman University Electronic Journal in Undergraduate Mathematics). The Elon Journal is the first to focus on undergraduate research in journalism, media and communi- cations. The School of Communications at Elon University is the creator and publisher of the online journal. The second issue was published in Fall 2010 under the editorship of Dr. Byung Lee, associate professor in the School of Communications. The three purposes of the journal are: • To publish the best undergraduate research in Elon’s School of Communications each term, • To serve as a repository for quality work to benefit future students seeking models for how to do undergraduate research well, and • To advance the university’s priority to emphasize undergraduate student research. The Elon Journal is published twice a year, with spring and fall issues. Articles and other materials in the journal may be freely downloaded, reproduced and redistributed without permission as long as the author and source are properly cited. Student authors retain copyright own- ership of their works. Celebrating Student Research This journal reflects what we enjoy seeing in our students -- intellectual maturing.
    [Show full text]