Towards Architectural Styles for Android App Software Product Lines

Jun 12, 20170 likes73 views

"Towards Architectural Styles for Android App Software Product Lines" by Tobias Duurschmid, Matthias Trapp, and Jurgen Dollner" MobileSoft'17, Buenos Aires, Argentina, 2017

Tobias Dürschmid, Matthias Trapp, Jürgen Döllner
Hasso Plattner Institute, University of Potsdam
Potsdam, Germany
Towards Architectural Styles for Android
App Software Product Lines
Partially founded by BMBF

Case Study
• Image Stylization App SPL with six apps
• >60.000 lines of code
• Amout of reuse >90%
2Towards Architectural Styles for Android App Software Product Lines

Challenges for Android App SPLs
• No general reuse model for features
Fragments have to have a UI
• Inflexibility of feature models
Static preference entries
• Inapplicability of classical SPL techniques
Lack of tool support for AOP in Android
3Towards Architectural Styles for Android App Software Product Lines

Activity Extensions
• Problem: No general reuse model for activities
• Solution: Modularize concerns in reusable classes
with unique interface
4Towards Architectural Styles for Android App Software Product Lines

Activity Connectors
5Towards Architectural Styles for Android App Software Product Lines
• Problem: Provide custom workflow for each apps
• Solution: Create an activity state machine
Each app refines the activity state machine
SenderActivity×TransitionEvent → TargetIntent

Dynamic Preference Entries
6Towards Architectural Styles for Android App Software Product Lines
• Problem: In Android, user-visible settings are
statically defined in an XML file
• Solution:
– Define a class Preference Record managing preferences
(load / save / reset / set value)
– A Factory creates them conveniently

Separated Behavior Description
7Towards Architectural Styles for Android App Software Product Lines
• Problem: Common domain
but different use cases per
app
• Solution: inject the behavior
and the content of the
concrete apps by separately
defining it using a high-level
configuration language.

Feature Model using Android Resources
8Towards Architectural Styles for Android App Software Product Lines
• Problem: How to apply feature models to Android
apps?
• Solution:
– Define a configuration file in the Android
resources of the core asset module.
– Override the value in sub modules

Conclusion
9Towards Architectural Styles for Android App Software Product Lines
• Simplify developing Android app SPLs
• Tailor apps to different target groups
• High amount of reuse

This document proposes a concept called MobileTwin Peaks to improve communication between mobile app users and developers. It suggests apps incorporate an interactive channel where users can provide direct feedback to developers about app quality. Developers could then rapidly iterate based on this feedback. The goals are to better understand user needs, localize requirements, and evaluate communication effectiveness. Challenges include ensuring timely, aligned, and representative feedback across languages and platforms. Early ideas discussed include in-app analytics, quality ratings, and automated analysis tools to help seed a proof-of-concept for the MobileTwin Peaks approach.

Performance-based Guidelines for Energy Efficient Mobile ApplicationsMobileSoft

The document discusses research into applying performance-based optimizations to improve energy efficiency in Android applications. The researchers analyzed 6 open-source Android apps to identify code smells and refactored the apps to address issues like overdrawing, wake locks, view holders, and obsolete layout parameters. They then measured the impact on energy consumption and found that some optimizations like fixing view holders significantly improved battery life, while other practices like overdrawing had a negative impact. The research suggests that performance best practices can help improve energy efficiency but not all directly translate, and that real mature apps saw energy savings from the refactoring.

Towards Architectural Styles for Android App Software Product LinesMatthias Trapp

Software Product Lines by Dr. Indika KumaraThejan Wijesinghe

This document provides an overview of software product lines (SPL). It discusses the challenges of systematic software reuse that SPL aims to address. Key concepts covered include domain engineering to develop core reusable assets, application engineering to derive product variants, and managing variability across the SPL. The document also discusses adoption strategies and how SPL principles can be extended to dynamic domains with runtime product derivation through dynamic SPL approaches.

7 - Architetture Software - Software product lineMajong DevJfu

This document discusses software product lines and product line architectures. It defines a software product line as a set of software systems that share a common set of features addressing a particular market segment. Product lines are developed from a common set of core assets in a prescribed way to reduce costs and increase reuse. A product line architecture is a common framework that standardizes components and maximizes reuse potential. It specifies common functionality and identifies variation points across related products. Variability management is important for providing flexibility without compromising commonality.

Consistent UI Across Android DevicesIrene Duke

The document discusses building a consistent user experience across Android devices by leveraging XML resources, styles, themes, and layouts that adapt to different screen sizes. It emphasizes using density-independent pixels (dp) and scale-independent pixels (sp), providing alternate resources for different configurations using qualifiers, and employing the Android support libraries to ensure backwards compatibility. The document also recommends evaluating open source libraries to implement Material Design components not fully supported by the official libraries and frameworks.

What’s new for Android Developers in 2015 - Material Design, Android Studio, ...Deepu S Nath

Rapid application developmentDhruvSamant1

The RAD (Rapid Application Development) model was proposed in the early 1990s to overcome the rigidity of the waterfall model. In RAD, prototypes are constructed and incrementally improved features are delivered to customers for feedback. Development occurs in short iterative cycles where a prototype for some functionality is developed, evaluated by customers, and refined based on their feedback. This decreases development time and costs while increasing flexibility to incorporate changes requested by customers. RAD is applicable for customized software, non-critical software, or projects with constrained schedules, but not for generic products, situations without similar existing products, or software that cannot be easily divided into incremental parts.

ppt_se.pdfarpitlamba32599

This document outlines the topics covered in five units of a Software Engineering course. Unit I introduces software engineering paradigms like waterfall and spiral models. Unit II covers software design concepts like abstraction and modularity. Unit III discusses software testing and maintenance. Unit IV covers software metrics and quality assurance. Unit V focuses on software configuration management. Key concepts covered include software development lifecycles, risk analysis, requirements engineering, and project planning techniques.

ppt_se.bdfhrfykjyftiktgdukhydiyiuoyu8otrfutubashaikh26

This document outlines the topics covered in a software engineering course across 5 units: introduction, software design, software testing and maintenance, software metrics, and software configuration management. The introduction unit discusses software engineering paradigms like waterfall and spiral models. Software design covers concepts like abstraction, modularity, and design notations. Software testing and maintenance examines strategies, tools, and maintenance. Software metrics focuses on process and product measurement. Software configuration management needs and version control are also introduced.

[2016/2017] Modern development paradigms Ivano Malavolta

7 SPL.pptx spl ppt in software engineeringMuhammadAbubakar114879

10 Things You Should Know About MDDJohan den Haan

Model-driven development (MDD) differs from model-based development and asks for agile development practices. It requires a standardized architecture to guide modeling and implementation, and specialized tools for defining modeling languages, transformations, and generating code. MDD leads to new roles for meta teams who build modeling tools and project teams who use these tools to develop applications. It has the potential to better align business and IT but also faces resistance due to the costs of learning and maintaining modeling tools.

Rad modelDyanara Pritz Menia

Rapid Application Development (RAD) is an agile software development methodology that focuses on rapid prototyping through workshops and iterative testing with customers. It involves business modeling to identify information flows, data modeling to define necessary data objects, and process modeling to convert data objects into business processes. Automated tools are then used to generate code from the models. The RAD model aims to reduce development time through reusability, early customer feedback, and short iteration cycles enabled by powerful modeling and code generation tools. However, it relies on strong individual performances, is only suitable for modularized systems, and requires high modeling and development skills.

Cnpm bkdnAnkit yadav

The document provides an introduction to software engineering and discusses the software development process, including project management. It describes various software development models like the waterfall model and iterative development. Key aspects of project management are also covered, such as feasibility studies, requirements definition, scheduling techniques, and the role of the project manager.

Domain specific modelling (DSM)PG Scholar

DSM is a higher level of CASE process, a way to model data structures and logic in domain concepts independent from programming languages and thus also include syntax details. The final source code in a desired programming language is derived automatically from these high concept models by using exact language generators.The whole process of Meta-modeling in the MetaEdit+ tool rotates around the Meta types represented together as GOPPRR

Kevin Whinnery: Best Practices for Cross-Platform Mobile DevelopmentAxway Appcelerator

Kevin Whinnery, Appcelerator Evangelist, shares best practices for creating mobile apps for cross-device deployment. Titanium Mobile is not a "write once, run everywhere" technology solution. Because Titanium provides the platform-specific APIs necessary to create best of breed native applications, the way in which you approach user interface development on one platform might differ significantly for another platform. It is, however, very possible to "write once, adapt everywhere" - to provide rich native experiences while achieving maximum code reuse. In this presentation, we will cover real world techniques for maximizing code reuse while leveraging platform-specific APIs in Titanium applications. Come with questions, and leave with multiple projects and code examples showing techniques Titanium developers use today to deliver sophisticated and performant cross-platform applications.

Configuring in the Browser, Really!Tim Geisler

We present an approach for tackling common problems in configuration frameworks: - It is often difficult to map a conceptual model of a configurable product into the restricted capabilities of configuration engines. For the end user this leads to suboptimal UIs. - The communication between a custom UI front-end and the configuration engine is cumbersome to implement. For the end user the need for round-trips between the UI and the configuration server can cause a sluggish user experience. With HTML5 and JavaScript-based UI frameworks such as React.js browsers have advanced into a powerful application platform. This allows to run not only the UI but also the configuration logic in the browser. This benefits the work of various stakeholders: - Modelers are provided with powerful data structures and the ability to define their own concepts. - Gradually extending the standard UI with custom features becomes easy and is based on standard technologies. - End users will enjoy the user experience of modern web applications. - End users can even use configurators in offline mode, without access to a server. - There is no need to run and maintain a server-side configuration engine. We will demonstrate this approach with concrete products and discuss the integration with an SAP back end. Presented at 2015 CWG Prague - SAP Configuration Workgroup Conference by Heribert Schütz and Tim Geisler

Google IO 2018Vishal Nayak

Software engineering.pptxJAGADEESWARIS6

The document summarizes the emergence and evolution of software engineering approaches from the 1950s to modern times. It describes early exploratory programming using assembly languages. It then discusses the introduction of high-level languages and increased focus on control flow-based design. Subsequently, the complexity of software led to data-flow oriented design using data flow diagrams. Object oriented design revolutionized the field by enabling reuse through concepts like encapsulation and inheritance. Finally, it briefly outlines evolutionary, RAD, spiral models for iterative development.

Unit iitamizh arthanari

This document discusses human-computer interaction (HCI) and usability engineering. It covers HCI in the software development process, including design rules, evaluation techniques, and universal design. Specific topics covered include the software life cycle, usability engineering, iterative design and prototyping, design rationale, and evaluation methods. Prototyping techniques like storyboards and simulations are also discussed. The goal of the document is to provide an overview of how usability and user experience is incorporated into the software engineering process.

Introduction to oop (Lect 1).ppt object oriented programmingnungogerald

e3-chap-06.pptMonjurRayhan

This document discusses human-computer interaction in the software engineering process. It describes the typical activities in the software life cycle including requirements specification, design, coding, and testing. It emphasizes that usability engineering must be integrated into all stages of development. Iterative design and prototyping methods are recommended to overcome incomplete requirements, using simulations, animations, and other prototypes. Design rationale involves documenting design decisions and trade-offs to support communication, reuse, and improving future iterations.

btech-final year-human computer interaction-hci.pptSandhya Gandham

HCI-in-sw-process.pptGaneshpatil499846

This document discusses human-computer interaction in the software development process. It describes the typical stages of the software life cycle and how usability engineering fits in. Iterative design and prototyping are emphasized to allow for user feedback and adjustments. Design rationale techniques are presented for documenting key design decisions and issues to support communication, reuse, and improving future iterations.

Pluggable patternsCorey Oordt

This document discusses making Django applications more "pluggable" by designing them to be focused, self-contained, and easily adaptable. It describes several types of pluggable applications including data apps, utility apps, and decorator apps. It then addresses 10 common situations where pluggability could be improved, such as making templates, URLs, options and views configurable. The goal is to create reusable apps that can be flexibly adapted to different projects and uses.

HCI chapter 3 notes on how students work with software process in designSarita Balshetwar

Predicting Android Application Security and Privacy Risk With Static Code Met...MobileSoft

This document presents research on using static code metrics to predict security and privacy risk levels in Android applications. The researchers collected a dataset of 4,416 Android apps with code metrics and risk levels. They found that support vector machines (SVM) achieved the best prediction performance when trained on lines of code, complexity, and bad coding practices metrics. The researchers conclude that static code metrics can help predict risk levels but are not comprehensive on their own for security and privacy assessments.

A Framework for Regression Testing of Outdoor Mobile ApplicationsMobileSoft

The document proposes a capture and replay framework to automate regression testing of outdoor mobile applications using noisy sensor data. The framework captures real sensor data streams during outdoor use and replays them in the lab, simulating the application's execution. It also allows editing replay sequences and comparing new outputs to gold standards to evaluate quality metrics and detect regression errors in updated applications. An example use case is given for the PeakLens mountain peak identification app.

More Related Content

Similar to Towards Architectural Styles for Android App Software Product Lines (20)

Rapid application developmentDhruvSamant1

ppt_se.pdfarpitlamba32599

ppt_se.bdfhrfykjyftiktgdukhydiyiuoyu8otrfutubashaikh26

[2016/2017] Modern development paradigms Ivano Malavolta

7 SPL.pptx spl ppt in software engineeringMuhammadAbubakar114879

10 Things You Should Know About MDDJohan den Haan

Rad modelDyanara Pritz Menia

Cnpm bkdnAnkit yadav

Domain specific modelling (DSM)PG Scholar

Kevin Whinnery: Best Practices for Cross-Platform Mobile DevelopmentAxway Appcelerator

Configuring in the Browser, Really!Tim Geisler

Google IO 2018Vishal Nayak

Software engineering.pptxJAGADEESWARIS6

Unit iitamizh arthanari

Introduction to oop (Lect 1).ppt object oriented programmingnungogerald

e3-chap-06.pptMonjurRayhan

btech-final year-human computer interaction-hci.pptSandhya Gandham

HCI-in-sw-process.pptGaneshpatil499846

Pluggable patternsCorey Oordt

HCI chapter 3 notes on how students work with software process in designSarita Balshetwar

Rapid application developmentDhruvSamant1

ppt_se.pdfarpitlamba32599

ppt_se.bdfhrfykjyftiktgdukhydiyiuoyu8otrfutubashaikh26

[2016/2017] Modern development paradigms Ivano Malavolta

7 SPL.pptx spl ppt in software engineeringMuhammadAbubakar114879

10 Things You Should Know About MDDJohan den Haan

Rad modelDyanara Pritz Menia

Cnpm bkdnAnkit yadav

Domain specific modelling (DSM)PG Scholar

Kevin Whinnery: Best Practices for Cross-Platform Mobile DevelopmentAxway Appcelerator

Configuring in the Browser, Really!Tim Geisler

Google IO 2018Vishal Nayak

Software engineering.pptxJAGADEESWARIS6

Unit iitamizh arthanari

Introduction to oop (Lect 1).ppt object oriented programmingnungogerald

e3-chap-06.pptMonjurRayhan

btech-final year-human computer interaction-hci.pptSandhya Gandham

HCI-in-sw-process.pptGaneshpatil499846

Pluggable patternsCorey Oordt

HCI chapter 3 notes on how students work with software process in designSarita Balshetwar

More from MobileSoft (20)

Predicting Android Application Security and Privacy Risk With Static Code Met...MobileSoft

A Framework for Regression Testing of Outdoor Mobile ApplicationsMobileSoft

Who Changed You? Obfuscator Identification for AndroidMobileSoft

Mobile App Development and Management: Results from a Qualitative InvestigationMobileSoft

Leafactor: Improving Energy Efficiency of Android Apps via Automatic RefactoringMobileSoft

Same App, Different App Stores: A comparative StudyMobileSoft

Performance-based Guidelines for Energy-efficient Mobile ApplicationsMobileSoft

Towards Native Code Offloading Platforms for Image Processing in Mobile Appli...MobileSoft

Assessing the Impact of Service Workers on the Energy Efficiency of Progressi...MobileSoft

Leafactor: Improving Energy Efficiency of Android Apps via Automatic RefactoringMobileSoft

Leafactor is a tool that automatically refactors Android app code to improve energy efficiency. It analyzes over 140 open source Android apps, applying refactorings like removing unnecessary wake locks and sensor listeners. The refactorings were validated and pull requests were submitted for 15 apps, with the goal of helping developers write more energy efficient code through automatic refactoring.

IFMLEdit.org: Model Driven Rapid Prototyping of Mobile AppsMobileSoft

CheckDroid: A Tool for Automated Detection of Bad Practices in Android Applic...MobileSoft

Authoring Tool for Location-based Learning ExperiencesMobileSoft

ACCUSE: Helping Users to minimize Android App Privacy ConcernsMobileSoft

ACCUSE is a tool that analyzes Android apps and assigns them risk levels related to their permissions and data access. It extracts metadata on over 11,000 apps from the Google Play Store, including permissions, downloads, and ratings. It then clusters apps based on their permissions and calculates three risk levels - normal, dangerous, and system - related to different permission types. ACCUSE also factors in app popularity and ratings to dampen the assigned risk for preloaded apps and highly rated apps. The tool allows analyzing apps with similar functions to see variations in their risk assessments and compares its risk model to others from previous research.

Automatically Locating Malicious Packages in Piggybacked Android AppsMobileSoft

From reactive toproactive mobile securityMobileSoft

Processing in Mobile Applications: A Case StudyMobileSoft

Rethinking the Mobile Code Offloading Paradigm: From Concept to PracticeMobileSoft

Generating Predicate Callback Summaries for the Android FrameworkMobileSoft

MobileSoft2017 OpeningMobileSoft