Development of a new android application to remotely control a micro‐cogeneration system as e‐learning tool

This paper focuses on software quality assurance in android application development with focus on approaches to confirm software quality in android applications. In this work, we compare the waterfall model with agile-scrum methodologies to realize software quality assurance with special focus on mobile applications. This research allows us to answer, “Which process model and practices are available for android software development along with focus on quality assurance?” The other research focus in this paper is “How auditors, developers and testers play their defined roles to maintain quality in mobile application development?” Agility for software development has transformed into a preferred and favored method for mobile application development. The major aim of this research is to contribute for a better knowledge for mobile application development methodologies practiced by the organizations for the development of applications based on systematic literature review.

This paper proposes REINVENT, a software architectural solution to decouple the specificities of using vehicular network communication resources in Android smartphone applications. REINVENT provides a REST based message passing interface based on Android's content provider to abstract vehicular network communication services. Using REINVENT, Android applications can use transparently the communication resources avoiding network transport layer details. REINVENT was tested in both laboratory and real world scenarios in the road with WAVE/IEEE 802.11p technology, to assess its usefulness in two Android applications, (VNChat and iThere). The real experiments also assess how REINVENT supports a mobile application to log relevant parameters in typical vehicular networks testing in different network scenarios.

In the nowadays enterprise computerized context, there is a trend that shifts the business applications to the new mobile environments. In the light of this information, it is highly important to be knowledgeable about the software development methodologies available in order to make the right choice when it comes to developing a mobile application. The current research aims to presenting the methodological approaches regarding the development cycle of classic enterprise software versus mobile apps. In the first part of the paper a brief literature review regarding the mobile is made, for the purpose of justifying the current research theme. The most consistent part of the article puts face-to-face the classical and the new development methodologies adapted to the requirements of the new mobile environment trends. The paper also presents the challenges and limitations of mobile applications as well as few of the future trends in the researched domain.Keywords: Application 's Lifecycle Models, Agile Models, Mobile Environment, Mobile Apps1 Introduction to Mobile ApplicationsMobile applications, also referred to as mobile apps, are software applications that are usually designed to be ran on smart phones and tablet computers [1], The term apps had become extremely popular and, as a consequence, in 2010 was listed as Word of the Year by the American Dialect Society. Mobile applications are available through application distribution platforms, which are managed by mobile operating system developer.There are several major trends that we believe it contributes to the boost of using the today mobile applications:* the increased availability and options to Internet connection for mobile devices;* the shift to the new mobile environments for the business applications;* cloud application's development;* the newest research findings that identifies new technologies which increased the performance of mobile device while the price remained at the same level, allowed mobile devices to became available for a wider variety of users.Another important aspect, when it comes to mobile application development, is the number of users. Thus, the number of mobile worldwide workers in 2013 is over 1 billion and accounts for about 35% of the worldwide workforce. The structure of the above ratio shows that Asia/Pacific (including Japan) have the largest total number of mobile workers, 785 million, while the second place is taken by Western Europe whose mobile workforce reached 129.5 million in 2013 and accounts for about half of the Western European workforce population. The study [2] also highlights that US has the highest percentage of mobile workers in its workforce, with 75.5% by the end 2013 accounting to 119.7 million mobile workers. A quick glimpse to the future is displayed in the two most recent studies which predict that mobile worker population will reach 1.2 billion by 2014 (a VDC study [3]) and 1.3 billion by 2015 (an IDC study [4]).Every day, hundred thousands of mobile devices are sold and about the same number of applications is downloaded. By 2015, International Data Corporation (IDC) predicts [5] that 182.7 billion mobile will be downloaded. That's a 1600 % increase from the 10.7 billion downloaded in 2010. This information highlights the mobile user's appetite for a wide range of software applications.Cloud application development brings innovation [6] to mobile computing as mobile devices use clouds for a wide range of purposes, from data processing and data storage to other intensive data and information transactions. So far, there are few mobile cloud applications (like Google Maps, Gmail for iPhone and Cisco's WebEx on iPad and several others that use Software as a Service model) but the trend is highly increasing.The main purpose of the paper is to present the methodologies for developing classic enterprise application versus mobile applications. …

Mobile systems and mobile applications have gained a lot of attention both in research and industry over the last years. The market share of mobile devices is constantly growing. More and more, users expect their mobile devices to provide functionality similar to the one they know from their desktop computers, but also to provide additional, mobile device specific functionality, like location based services. However, software development for mobile devices is still cumbersome and a methodology geared towards supporting the development of such mobile applications is still lacking. While there is broad agreement that developing for mobile devices is more difficult than traditional software engineering, we lack a precise understanding that goes beyond anecdotic evidence of why this is the case and how the situation can be ameliorated. We do not precisely know where and how the development of mobile application differs from “normal” software development and where new methodologies are needed. Aspects that need to be addressed in this context are, among others, the questions of software architectures for mobile applications, approaches to the software design for mobile applications and how the consequences of being mobile, e. g., changing location, changing context, changing connectivity, heterogeneous software and platforms influence the software development process and what design approaches do reflect the specialties of mobile applications and systems appropriately. While this special issue cannot provide a definite or complete answer to these questions, it does provide answers to some important aspects. In the following, we will first try to get a more thorough understanding of some of the main differences between mobile and classical application development and will then discuss how the papers contained in this special issue address these differences.

In software testing process, test data generation represents an important step for high quality software, even for mobile devices. As proposed in previous works, a potential source for random data generation is represented by the UI layout files that are used for almost all mobile platforms (Android, iOS, Windows Phone/Mobile). This paper continues the previous work and presents a test data generation system based on Android layout files. The test data generator uses DSL files as input and generates test data that conform to several testing principles. The generated test data could be stored in XML files or any format required by the testing frameworks.

In this paper, a novel self-punishment based scheduling algorithm for a cooperative real- time content download application is designed. In the proposed protocol, selfish mobile devices autonomously form cooperative groups. For each formed group, the base station transmits the content to a selected mobile device designated as seed. Then, the seed shares the content with other mobile devices called sinks over device-to-device links. After analyzing the proposed protocol using a repeated game, new self-punishment mechanisms by revocation or by decreasing the bit rate, are proposed. Such self-punishment mechanisms enable the mobile devices in each cooperative group to autonomously punish selfish seeds without requiring any help from other mobile devices outside cooperative group. ‌Based on the proposed self-punishment mechanisms, a fair algorithm is designed to schedule the seeds in each cooperative group. Then, the designed scheduling algorithm is implemented using an Android application that is developed using Java in the Android Development Tool Bundle. The developed Android application does not depend on the operation system of mobile devices. Simulation results demonstrate that, on the average, the proposed protocol improves the energy efficiency of mobile devices to download real-time content of around 42 % compared to a traditional multicast scenario. Moreover, the proposed protocol does not let the energy efficiency of mobile devices degrade more than 11 %, on average, from the optimal solution even when all the mobile devises are selfish. The practical results show that the maximum difference in the run time of a real- time video over real-world smartphone screens is less than 500 milliseconds when the smartphones form a cooperative group using the developed Android application.

It is our great pleasure to welcome you to the proceedings of the workshop held as part of SPLASH 2014! This year's Workshop continues the tradition of allowing both graduate and undergraduate students to present their ongoing work and get productive feedback on their latest results. Workshop Overview Mobile application usage and development is experiencing exponential growth. According to Gartner, by 2016 more than 300 billion applications will be downloaded annually. The mobile domain presents new challenges to software engineering. Mobile platforms are rapidly changing, including diverse capabilities as GPS, sensors, and input modes. Applications must be omni-channel and work on all platforms. Activated on mobile platforms, modern applications must be elastic and scale on demand according to the hardware abilities. Applications often need to support and use third-party services. Therefore, during development, security and authorization processes for the dataflow must be applied. Bring your own device (BYOD) policies bring new security data leaks challenges. Developing such applications requires suitable practices and tools e.g., architecture techniques that relate to the complexity at hand; improved refactoring tools for hybrid applications using dynamic languages and polyglot development and applications; and testing techniques for applications that run on different devices. This workshop aims at establishing a community of researchers and practitioners to share their work and lead further research in the mobile software engineering. The workshop has several goals. First, we want to develop relationships to create a vibrant research community in the area of mobile software development. Second, we want to identify the most important research problems for mobile software development. Our program includes: Distinguished keynote by Dr. Daniel M. Yellin the Vice President, IBM Mobile Platform Development, and an IBM Distinguished EngineerInvited talksMarco Pistoia and Omer Trip Integrating Security, Analytics and Application Management into the Mobile Development LifecycleNikolai Tillmann Rapidly Prototyping Apps for Mobile Cloud-Connected DevicesLucas Brutschy, Pietro Ferrara and Mueller Peter. Static Analysis for Independent App DevelopersPanel: "How Mobile Affects Business Processes? : The Research Perspective"Activity: "Killer Apps for Mobile Opportunity and ChallengesResearch papers Mobile software engineering presents new challenges and directions. Among others, we observe the following five areas of interest: Management of the mobile applications. This refers to the technical capabilities to create, deploy, and manage a suite of applications for multiple heterogeneous devices (e.g., iOS, Android, BlackBerry, Windows) that connect securely to enterprise back-end servers.Hybrid applications versus native applications. A native application is an application designed to run in a specific environment written in a specific language. A hybrid mobile application, however, is developed using web technologies such as HTML, CSS, and JavaScript activated by a native wrapper. Building native applications requires comprehensive knowledge in the specific environment, such as Objective C (iOS), Java (Android), and C# (Windows mobile and BlackBerry). However, hybrid applications based on web technologies require more common knowledge.User experience. Applications must be developed that provide different user experiences depending on the target environment. For example, an iOS application provides a different user experience than an Android application, even though the functionality of the application must be the same.Battery life. How can developers write software that uses up as little battery life as possible?Migrations to mobile. As more users access and use mobile-based tools, developers need to enable and support migration from legacy software such as web applications to mobile.Mobile security. Mobile devices have strong networking capabilities. Hence security of ersonal information and businesses data become very important. Employees use their smartphones to access sensitive information. The operating system of those devices collects sensitive data that may be visible to third-party applications. Hence vulnerabilities from both the web browser and operating system must be considered. Moreover, the development of mobile applications includes the following aspects that extend existing software engineering practices: Software characteristics. 1) Software is distributed on several platforms that link between them over the network. For example, one part of an application could be on mobile phones browsers, another part might be on the cloud, and both of them are reading data from some legacy systems. 2) Mobile applications need to be elastic and scale on demand according to their environments' abilities. Functionalities need to be easily removed, added, or moved to or from the cloud. 3) Many hardware platforms exist for an application and the platforms are rapidly changing, including flexible capabilities such as GPS, sensors, and input modes. Development, however, should be for all platforms.Architecture. Mobile application development also includes several architectural challenges, such as how to support omni-channel communications and how to support new application data updates from the server, e.g., notifications about new mail or software updates. Applications must be able to easily communicate with new systems. Traditional solutions enable software to be easily designed and modified to communicate with new environments. However, the environments with which applications need to communicate are rapidly changing. As a result, traditional solutions do not fit modern software and we cannot modify applications using traditional architectural approaches to support all channels.Testing. Another aspect of mobile application development concerns software testing. How can applications be tested on arbitrary and unknown hardware? And how can we develop test-driven software without being able to run the test itself?

According to International Data Corporation (IDC), Android accounted for 81% of all smartphone shipments in the third quarter of 2013. With the increase in smartphones, mobile application installs from Google Play have reached more than 48 billion app installs as revealed by Sundar Pichai, senior vice president, Chrome and Apps at Google I/O 2013. Thus, Android application development has become increasingly popular with the need of an effective software solution for application development and testing. While most Android applications are developed in Java, the Android framework is quite different fromm typical Java frameworks. Thus, while development or testing of Android applications, the user needs to be aware of all the terms and concepts specific to the Android framework such as activity, views and the Android SDK in general.

To mitigate the risk of attacks to mobile applications, it is important for mobile application developers to develop secure mobile applications. There have been tools that statically analyze the mobile applications to determine whether there are data leakage or access control vulnerabilities The Software Engineering Institute at Carnegie Melon University published CERT Java secure coding rules applicable to developing android applications. This paper describes SACH (Secure Android Coding Helper) - a tool we implemented to help developers identify security vulnerabilities in Android application. The tool analyzes Android application source code to detect violations of CERT Java secure coding rules. This tool will help Android developers to write Android code that comply with CERT Java secure coding rules. It can also be used in the classroom to teach students about Android secure coding.

Study question Given the subjectivity of blastocyst grading and the challenge of performing routine competency assessments, how consistently do embryologists grade blastocysts when using an easily accessible phone application? Summary answer Grading agreement was fair to moderate for inner cell mass (ICM) and trophectoderm (TE), evidence that a mobile application can be used for quality assurance. What is known already Embryologists routinely perform external quality assessments (EQA), though the utility of EQA for quality improvement is limited, and more active, user-friendly tools are needed to improve quality assurance in embryology. Blastocyst grading is one of the most important and subjective tasks in clinical embryology, important for both blastocyst ranking and decision to freeze. Inter-user agreement is only fair for ICM (kappa 0.349) and TE grade (kappa 0.397; Storr et al., 2017). Fair agreement has also been reported for decision to freeze for a cohort of blastocysts that exhibited borderline morphology (kappa 0.301; Hammond et al., 2020). Study design, size, duration A prospective study of blastocyst grading consistency using ARTCompass, a mobile phone application designed to assess clinical decision making of laboratory staff for andrology and embryology competency. Two assessments, each with 100 images of expanded blastocysts in three planes, were performed by 42 embryologists from 9 clinics in 2 countries between April to July 2020. Survey 1 assessed ICM grading and survey 2 assessed TE grading using the same set of images for consistency. Participants/materials, setting, methods Blastocysts were of proportionally mixed grades (ranging from grade A to X) using a modified Gardner system that included “X” for non-viable ICM/TE. Embryologists were advised to complete the tests individually in one sitting. The Fleiss kappa coefficient (k) measured inter-rater agreement among embryologists when assigning blastocyst grade. Kappa value interpretation is as follows <0.20: poor; 0.21–0.40: fair; 0.41–0.60: moderate; 0.61–0.80: good and 0.81–1.00: very good. Main results and the role of chance Overall, agreement for ICM and TE grades was moderate among embryologists (kappa 0.47, 0.52, respectively). ICM grade B and C had the lowest agreement (0.37, 0.39), while ICM grade X (no, or degenerate ICM), and TE grade A showed the highest agreement (0.68, 0.62). These results illustrate that embryologists had difficultly classifying ICM grade when it was of moderate to poor quality (grade b or c), likely due to subjectivity in grading size and compaction level, but were good at classifying ICM grade when there was no apparent ICM (grade x). For TE grade, embryologists consistently identified a top-quality TE (grade a), which is reassuring as TE grade is the primary morphological feature used for blastocyst ranking. In general, this QA platform offers ease of use and shows agreement values for ICM and TE that are similar to other studies, suggesting that blastocyst grading with a mobile phone application is a viable option for quality assurance. Limitations, reasons for caution Only blastocyst grading was assessed, therefore additional competency assessments using a mobile device should be assessed for accuracy. Further studies are needed to determine if mobile applications can improve competency. Wider implications of the findings: Ease of use by 42 embryologists indicates mobile applications may provide a user-friendly and accessible platform for QA. Since effective and efficient assessment of competency and KPIs is an ongoing challenge for laboratories, a mobile application is a novel and effective tool to monitor QA parameters in the IVF laboratory Trial registration number Not applicable

모바일 앱 사용에 영향을 미치는 요인에 관한 연구: 앱 카테고리 간 상관관계를 중심으로

Introduction: The introduction of Clinical Information Systems (CIS) to manage and store patient information has deeply modified the workflow of caregivers. As the information is no longer stored on a physical medium, caregivers depend on the presence of a computer to access patient data. This constraint has built up an invisible barrier between the source of information and the place of its use. The popularisation of mobile devices offers an oportunity to break this barrier by providing a ubiquitous access to information. The use of a mobile platform merges the advantages of a modern CIS and the mobility offered by paper. We have developed an application on a mobile device that nurses can carry along on all their visits. It allows the information gathered during their visits to be entered directly into the system. Method: The tool we present aims to manage the daily interventions of nurses. The interventions concern all kinds of treatments provided by nurses to patients. In the current organisation, nurses start their day by printing out all the daily interventions and use it as a procedure to follow. Every time a nurse performs an intervention, she takes a note indicating that the task has been done properly. When they have some spare time, nurses enter all the gathered information in the CIS. Once nurses are equipped with mobile devices, paper becomes useless. Consequently, the process is simplified. Replacing the paper by a mobile device application is not straightforward. In order to access patient information, the tool must be linked to the existing CIS of the hospital without creating too strong dependencies. Moreover, the mobile interface must be adapted to the specificities of the mobile device such as a smaller display size, a reduced computational power, a tactile-based interaction and a real-time usage. Results: In order to link the mobile application to the existing CIS, we relied on a Service Oriented Architecture (SOA). It was mandatory to think of a software architecture that would not create a dependency with any legacy system. Thus, we defined a gateway server providing centralised access for the mobile application to any required information to or from the CIS. Integrating any mobile application would only require integrating this bridge. The gateway server also clearly separates the services that are available remotely from the ones proposed as usual Web services. The developed application not only allows the validation of the interventions and the input of measures, but it also offers a simple way to define the context in which nurses are working. This context is necessary to identify the specific list of interventions for the patients under the caregiver’s responsibility. The current CIS of the HUG includes a module that provides information concerning the interventions. Its interface is adjusted for a personal computer screen. Since caregivers are accustomed to this organisation of the information, we aimed to develop an interface on a mobile device that guarantees a certain level of homogeneity with the existing PC application. However, a mobile device’s screen is of limited size, therefore the interface has been completely rebuilt to be adapted to the new display. To deal with the limited display size, we rely on hierarchy and indexicality principles. For instance, based on the hypothesis that all tasks belonging to one category and planned at the same time can be regrouped under a single item; we regroup the interventions of similar top level in a common item. Moreover, to minimise user manipulations, relevant items are automatically moved to the top. Conclusion: The current daily workflow of nurses cannot be managed consistently using a unique tool. The need to switch from paper to computer induces work overload and is a source of errors. Therefore, we have developed a program running on a mobile device that nurses can carry during their visits. This program allows to manage nurses' daily interventions in real-time. The development of such a tool has required a complete reconstruction of the classical personal computer interface. This new interface takes into account a smaller display size, an innovative interaction paradigm, and real-time constraints.

In the context of modern Android application development, security issues and secure programming are considered unignorable aspects to ensure the safety of Android applications while still guarantee the development speed. The lack of attention to security factors in the software development process or the delay of traditional security assurance methods are the main causes of unsafe Android software. Those unsafe Android applications contain many vulnerabilities and a high risk of leaking user information, especially since Android applications are rapidly developed and published. Developers must adhere to a secure development process to counter Android application risks to avoid data leakage or access control flaws. Security has to be integrated throughout the application development process to secure the software development life cycle. This paper presents two main research contributions: summarizing common security issues in Android applications and developing a plug-in for Android Studio to support secure programming, 9Fix. The low-time-cost 9Fix plug-in can inspect your vulnerable code and instantly suggest an alternative secure code for developers in programming time that helps to improve the security and instruct the developers on how to write a secure code. Moreover, the developers can add their own security rules to 9Fix so 9Fix can adapt smoothly in a specific situation. We also demonstrate the effectiveness and the convenience based on the student feedback by experimenting with the 9Fix plugin.

India is one of the largest tribal countries in the world after Africa. According to the 2011 census of India, the tribal population is 8.6% of the total population of the country. They are all over the country in states like Jharkhand, Odisha Madhya Pradesh, Gujrat, Rajasthan, Andhra Pradesh, West Bengal, and Chhattisgarh. Tribal society is characteristically distinguished from the mainstream by its culture, lifestyle, occupation, and alienation. With the increase in the development of today's information technology and wireless telecommunication networks, mobile devices have proliferated rapidly and become important tools for Terrible people. The use of M-Services and applications (apps) on mobile devices has become commonplace in people's everyday lives. Mobile applications are the gateway to the transfer of human knowledge. Learning is a continuous process and now the focus has completely shifted to eLearning. Thanks to mobile phones and various function-oriented apps, students can learn at their own pace and take their time understanding things because everything is just a click away. The integration of mobile devices into the teaching-learning process heralded a new era in education. It has made the teaching-learning process more interactive and hands-on. Quality education can be provided to anyone, anywhere. In general, implementing mobile phone applications and technologies can provide many benefits for a quality educational environment. The provision of education for all in India remains a distant dream, despite the significant government investment expended on it. This document covers the use of mobile phone applications, how to help the Indigenous community, especially students and the community of Chhattisgarh, and what steps the Chhattisgarh government has taken to uplift the educational system and empower tribal students and community with various mobile phone apps to bring the underprivileged from darkness to light.

Today, the development of mobile applications becomes more important and increasingly popular in our environment due to the intensive use of applications in mobile devices. The diversity of mobile operating systems (iOS, Android, Windows Phone, etc.) makes software engineers facing a real challenge to develop the same applications for these different platforms. Given this development complexity, we directed our work to platforms using Model Driven Architecture (MDA) approach. This paper presents a methodology based on the MDA approach to develop mobile applications according to the principal ‘Develop Once, Use Everywhere’. Our approach exploits UML modeling and Acceleo to generate specific code in order to facilitate and accelerate the development of mobile applications. That is why we have developed two meta-models handling UML class diagrams and Android applications, then we have to set up transformation rules. The transformation rules defined in this paper can generate, from the class diagram, a classes Java files containing the necessary code of a mobile application.