Architecture Patterns for Mobile Systems in Resource-Constrained Environments

Pattern-Based and Reuse-Driven Architecting of Mobile Cloud Software

“…This means that the patterns for traditional software development and architecture [9,10,11] cannot easily be applied to mobile cloud systems unless they support the abovementioned characteristics specific to mobile cloud architectures [7,8]. For example, a pattern that exploits context sensing for recommendations and decision support is only applicable to contextaware computing architectures.…”

“…For example, unlike the traditional architectures, mobile cloud based architectures are expected to serve context-aware multiple-tenants with each tenant having its own specific context and QoS requirement that can vary from performance and reliability to security aspects. Contextaware multi-tenant capabilities of MCC systems need to be considered not only at service but also at the platform and infrastructure [7,8] level not addressed in existing patterns.…”

“…In the context of community-driven pattern repositories, the work presented in [17,18] -Patterns for Mobile Computing Systems: In contrast to the research and development on cloud computing patterns, there is a lack of research patterns and pattern-based architecting of the mobile computing systems. In a recent research in [8], some architectural patterns are presented to support the operations of resource constrained mobile devices. Specifically, three architectural patterns namely data source integration, group-context awareness, and cyber foraging are presented for mobile computing systems in the context of tactical-edge resourceconstrained environments.…”

“…In this situation, software patterns and styles can provide reusable solutions and best practices to develop MCC systems. Specifically, software patterns focused on designing or architecting MCC can provide documented and well understood software design solutions to both the experienced and novice architects [6,7,8]. Software patterns have been proven successful in providing reusable packages of generic and repeatable solutions to recurring problems of software and system design [9].…”

“…This means that patterns as generic and reusable solutions create the software architecture -providing the system blueprint -that acts as a bridge between system requirements and system implementation as in Figure 1. It is vital to mention that, while architecting the MCC systems, one exploits dynamically composed services to develop systems that are portable, context-sensitive and efficient [7,8]. In comparison to the more traditional (object-oriented, component-based and service-driven) systems [10], patterns for mobile MCC architectures are characterized by specific requirements such as mobility, context-sensitivity for (front-end) mobile computing with service composition, and scalability of (back-end) cloud services [12].…”