2018 IEEE International Conference on Software Architecture Companion (ICSA-C) 2018
DOI: 10.1109/icsa-c.2018.00034
|View full text |Cite
|
Sign up to set email alerts
|

An Efficient Mobile-Based Middleware Architecture for Building Robust, High-Performance Apps

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
5
0

Year Published

2019
2019
2019
2019

Publication Types

Select...
2
2
1

Relationship

4
1

Authors

Journals

citations
Cited by 5 publications
(5 citation statements)
references
References 5 publications
0
5
0
Order By: Relevance
“…The user may then describe his problems and converse with the crowd to figure out which rules to create (the workers converse by text, and the user, may either use text or voice). Once the rule is created, it is sent back to the user's phone, where a Decision Rule Engine component (Tomazini et al, 2017;Romero and Akoju, 2018) will store, validate and process that rule. Currently, the system is implemented and tested on the Android OS 6.0.1 and the server is implemented in Java.…”
Section: Conversational Agent For the End-usermentioning
confidence: 99%
“…The user may then describe his problems and converse with the crowd to figure out which rules to create (the workers converse by text, and the user, may either use text or voice). Once the rule is created, it is sent back to the user's phone, where a Decision Rule Engine component (Tomazini et al, 2017;Romero and Akoju, 2018) will store, validate and process that rule. Currently, the system is implemented and tested on the Android OS 6.0.1 and the server is implemented in Java.…”
Section: Conversational Agent For the End-usermentioning
confidence: 99%
“…NLSC was architected to be deployed on distributed environments and to support different kind of client applications (e.g., standalone, web, mobile, etc.). This requirement, along with dynamicity, low-latency, high-performance, modularity, and support to Android Runtime Environment (ART), were the main architectural significant requirements we took into consideration over its implementation [29]. Extending our initial definition of "service", we consider that an Androidbased service can be a device sensor, a local service (installed on the Android device), or an app, hence, we avoid making the assumption that only a web service model should be applicable to NLSC.…”
Section: Service Development Processmentioning
confidence: 99%
“…Given the previous example we focus on five challenges, so service composition should: (1) consider preferences from multiple users; (2) coordinate the interaction between services hosted by different service providers; (3) consider resource scarcity in smart devices [21]; (4) perform dynamic adaptation to unpredictable changes occurring in the environment; (5) deal with both short-term and long-term user's goals. Performing service composition while taking into account a myriad of variable factors as described above (e.g., users, services, service providers, QoS values, context, etc.…”
Section: Introductionmentioning
confidence: 99%