scholarly journals Applying Agile Methodology in Mobile Software Engineering: Android Application Development and its Challenges

Author(s):  
Shakira Banu Kaleel ◽  
Ssowjanya Harishankar

Applying Agile Methodology in Mobile Software Engineering: Android Application Development and its Challenges

2021 ◽  
Author(s):  
Shakira Banu Kaleel ◽  
Ssowjanya Harishankar

Applying Agile Methodology in Mobile Software Engineering: Android Application Development and its Challenges


Author(s):  
Varun Gupta ◽  
D. S. Chauhan ◽  
Kamlesh Dutta

Mobile software application development process must be matured enough to handle the challenges (especially market related) associated with the development of high quality mobile software development. Ever increasing number of both mobile users and mobile applications had presented software engineers with the challenge of satisfying billions of users with high quality software applications to be delivered within deadline and budgets. Always there had been a lot of pressure to develop complex software categorized by thousands of requirements, under resource constrained environment. Requirement prioritization is one of the activities undertaken by software engineer to deliver partial software product to its customers such that most important requirements are implemented in the earliest releases. During next releases some changed and pending requirements are implemented, an activity that generates ripple effects. Such ripple effects need to be tested by executing modified source code against test cases of previous releases (regression testing). Regression testing is a very effortful activity that requires a software tester to select test cases that have high fault detection capability, execute the modified code against selected test cases and performing debugging. This regression testing activity can be lowered to the maximum extend by considering dependencies between requirements during the time of requirement prioritization. Thus requirement prioritization will be carried out not only against aspects like cost, time, risks, business values etc but against dependencies also. The aim is to implement almost all dependent highest priority requirements in current release so that implementation of new requirements is unlikely to have ripple effects. Changes in requirements might not be related to variable usage and definition and might not involve a change in functionality. In such cases there is no need to select already executed test cases of previous versions. Module dependencies can lead to test case selections of previous versions if changes of requirement lead to ripple effects. This paper aims to implement highest priority requirements such that regression testing is performed to minimum thereby improving development process of mobile applications. The proposed technique had been successfully evaluated on Android based notification software application that meets the specification of Aakash tablets.


2021 ◽  
Vol 47 (05) ◽  
Author(s):  
NGUYỄN THỊ PHƯƠNG GIANG ◽  
TRẦN THỊ MINH KHOA

Continuous Integration (CI) is the most common practice among software developers where they integrate their work into a frequent baseline. The industry 4.0 is facing huge challenges while developing Software at multiple sites and tested on multiple platforms. Today, so many CI tools widely used for software development as CircleCI, Jenkins, Travis. CircleCI is one of the CI tools that can helps in automating the complete process, reducing the works of a developer and check the development at each and every step of Software evolution. In this paper, we discuss the implementation of CircleCI for android application development. Firebase Test Lab will be used for some additional automation testing.


Author(s):  
Zaidoun Alzoabi

The term Agile Method of software development was coined in the 2001.This approach is characterized with creativity, flexibility, adaptability, responsiveness, and human-centricity. Researchers have suggested that the complex, uncertain, and ever-changing environment is pushing developers to adopt agile methods rather than traditional software development. Agile methodologist claim that their Agile methods is the answer for the software engineering chaotic situation, in which projects are exceeding their time and budget limits, requirements are not fulfilled, and consequently ending up with unsatisfied customers. In this chapter we will explain agile methodology, its general characteristics, and quick description of the famous agile methods known in the industry and research.


Author(s):  
Rajeev K Bali ◽  
Nilmini Wickramasinghe

Rapid Application Development (RAD) is promising to bring many benefits and state-of-the-art uses to the discipline of software engineering. The plethora of low cost RAD tools, together with the claims made by advocates of this methodology, has lead to an explosion in the use of this technique across the field. Unfortunately, however, there has been comparatively little regard in context to the project management issues of adopting RAD methodologies on which this paper will focus.


Sign in / Sign up

Export Citation Format

Share Document