Software Architectural Patterns Research Articles

Analysis of Different ORM Tools for Data Access Object Tier Generation: A Brief Study

The Data Access Tier, also known as the Data Access Layer (DAL), is a specific tier within the 3-tier architecture or other software architectural patterns. The interaction between the application's business logic and the underlying data storage or database is managed by it. This pattern provides an abstraction layer that encapsulates the logic required to access and manipulate data in a data storage system. This paper demonstrates the related work that happened in the past regarding the generation of the data tier in between the business layer and the actual Database of the MVC/MVT architecture for faster software development. This study will go further into the imbalance of impedance among programming languages that are object-oriented and relational databases. It also elaborates on many researchers' perspectives on this topic using the ORM tool to generate such an ORM tier. Also, this paper illustrates the different shortcomings of this ORM tier. Pointing out the various approaches to data access layer generation, from databases to programming languages. Pinpointing the pitfalls of the researcher's work and how the researcher has presented their research paper. This paper will also suggest one of the proposed modules to overcome the shortcomings of the ORM tier. The proposed module has two approaches to generating the Data Access tier: reverse engineering, which means mapping from table to code, and Forward engineering, which means generating code first and then creating databases from the code.

Inclusive Educational Review of Software Architectural Styles and Patterns for the Students of the College of Information and Computing Sciences of Cagayan State University

Inclusive Educational Review of Software Architectural Styles and Patterns for the Students of the College of Information and Computing Sciences of Cagayan State University

Multitenancy and Observability in Smart City Platforms

Smart City Platforms are complex Information and Communication (ICT) projects where information from the physical and virtual world converge with the ultimate goal to provide better living conditions to the city’s citizens. The architecture of these platforms has been approached as an evolution of similarly large ICT projects and as a consequence the already established architectural patterns have been reused. Among them is multitenancy, a software architecture pattern that emerged in an effort to optimize the use of compute resources and minimize the operational cost of large-scale deployments. At the same time, the size and complexity of Smart City Platforms makes observability one of the key capabilities a Smart City Platform must offer in order to ensure its operational requirements are met. From the perspective of system complexity in general and observability in particular, the applicability of the multitenancy architecture pattern in Smart City Platforms is debatable as the benefits it brings may not outweigh the challenges.

ETL Processes for Integrating Healthcare Data - Tools and Architecture Patterns.

Improving the interoperability of healthcare information systems is a crucial clinical care issue involving disparate but coexisting information systems. However, healthcare organizations are also facing the dilemma of choosing the right ETL tool and architecture pattern as data warehouse enterprises. This article gives an overview of current ETL tools for healthcare data integration. In addition, we demonstrate three ETL processes for clinical data integration using different ETL tools and architecture patterns, which map data from various data sources (e.g. MEONA and ORBIS) to diverse standards (e.g. FHIR and openEHR). Depending on the project's technical requirements, we choose our ETL tool and software architecture pattern to boost team efficiency.

Software Architecture Patterns for Extending Sensing Capabilities and Data Formatting in Mobile Sensing.

Mobile sensing—that is, the ability to unobtrusively collect sensor data from built-in phone and attached wearable sensors—have proven to be a powerful approach to understanding the behavior, well-being, and health of people in their everyday life. Different platforms for mobile sensing have been presented and significant knowledge on how to facilitate mobile sensing has been accumulated. However, most existing mobile sensing platforms only support a fixed set of mobile phone and wearable sensors which are ‘built into’ the platform’s generic ‘study app’. This creates some fundamental challenges for the creation and approval of application-specific mobile sensing studies, since there is little support for adapting the sensing capabilities to what is needed for a specific study. Moreover, most existing platforms use their own proprietary data formats and there is no standardization in how data are collected and in what formats. This poses some fundamental challenges to realizing the vision of using mobile sensing in health applications, since mobile sensing data collected across different phones and studies cannot be compared, thus hampering generalizability and reproducibility across studies. This paper presents two software architecture patterns enabling (i) dynamic extension of mobile sensing to incorporate new sensing capabilities, such as collecting data from a wearable sensor, and (ii) handling real-time transformation of data into standardized data formats. These software patterns are derived from our work on CARP Mobile Sensing (CAMS), which is a cross-platform (Android/iOS) software architecture providing a reactive and unified programming model that emphasizes extensibility. This paper shows how the framework uses the two software architecture patterns to add sampling support for an electrocardiography (ECG) device and support data transformation into the new Open mHealth (OMH) data format. The paper also presents data from a small study, demonstrating the robustness and feasibility of using CAMS for data collection and transformation in mobile sensing.

The impact of the software architecture on the developer productivity

Abstract Distinct technological trends seriously influence the modern software architectures. In this paper, four different software architectures and framework combinations were generally compared. The basis for the analysis is the developer's productivity. In a 3 year-long research and development project, a real-world telemedicine application was efficiently implemented four times with various software architectures and architectural patterns. More than 5,000 person-hours were spent on carrying out them. At present, a unique dataset is available, which provides the opportunity to compare the cost of spent person-hours in different approaches. The goal of this research is to describe the measurement approach, the dataset and the applied architectures considering the software developer's productivity.

AN APPROACH TO ANALYSIS OF ARCHIMATE APPLICATION ARCHITECTURE MODELS USING THE SOFTWARE COUPLING METRIC

Applications architecture is the baseline of any organizational activity, which main goal is to provide the executional environment for businessprocesses in order to deliver products or services to satisfy customer needs and generate revenue. Nowadays, large software engineering projectsalways begin with the architecture design phase, despite the waterfall or agile methodology is used by a software development team. Applicationsarchitecture design is the most important and, at the same time, error-prone stage of the whole software engineering project. It is well-known thatdesign shortcomings made on the design phase may increase drastically to testing and maintenance phases. Further costs to defects fixing may behundred times higher in the later project stages in compare to the design stage on which applications architecture is defined. Common system designsolutions, which were proven on practice and used in many projects, are known as architectural patterns. Software architecture patterns are consideredas building block for system implementation. The most popular and efficient way to share architectural patterns are graphical models that used as anyother blueprints of engineering solutions. Applications architecture models are built to represent system design, whereas, such models are alreadybased on certain patterns as the industry best practices. Hence, in this paper we consider a relevant problem of applications architecture modelsanalysis, which relevance is defined by those fact that designed blueprints of information systems and other software solutions should be carefullychecked for all presumable inefficiencies in order to avoid extra efforts and related costs for defects fixing in the later project stages. It is proposed touse ArchiMate enterprise architecture modeling language, since it can be used not only to represent applications architecture, but is connection tobusiness and technology layers. In order to evaluate applications architecture models, respective ArchiMate metamodel is considered and representedas labeled directed graph, and coupling software metric is selected for analysis. Sample calculations are demonstrated, obtained results are discussed,conclusion and future work directions are formulated.

Microservices Software Architecture: A Review

Abstract: Architecting is an indispensable activity in all spheres and paradigms of Software Engineering. DevOps, a portmanteau of Development and Operations, has a major adoption challenge in context to Microservices Architecture. Architecture refers to the most important aspect of internal design of a software. Architecture must be good otherwise; it will become slow and much more expensive to add new proficiencies in future. This paper has presented a review of microservices architecture and implementation patterns. Microservice approach is a new concept in software architecture patterns and has leapt up over past few years for describing a certain method to design software applications as collections of individualistically deployable services. In this paper we are looking to discover the role of microservices software architecture in DevOps. It is found that adopting DevOps may carry many challenges/issues like organizational values, immaturity of the tools and infrastructural support with it for architecting with it. Keywords: Microservices Architecture, Microservice, Service Oriented Architecture (SOA), Software Architecture, DevOps

An empirical characterization of event sourced systems and their schema evolution — Lessons from industry

Event sourced systems are increasing in popularity because they are reliable, flexible, and scalable. In this article, we point a microscope at a software architecture pattern that is rapidly gaining popularity in industry, but has not received as much attention from the scientific community. We do so through constructivist grounded theory, which proves a suitable qualitative method for extracting architectural knowledge from practitioners.Based on the discussion of 19 event sourced systems we explore the rationale for and the context of the event sourcing pattern. A description of the pattern itself and its relation to other patterns as discussed with practitioners is given. The description itself is grounded in the experience of 25 engineers, making it a reliable source for both new practitioners and scientists. We identify five challenges that practitioners experience: event system evolution, the steep learning curve, lack of available technology, rebuilding projections, and data privacy. For the first challenge of event system evolution, we uncover five tactics and solutions that support practitioners in their design choices when developing evolving event sourced systems: versioned events, weak schema, upcasting, in-place transformation, and copy-and-transform.

Software Architecture and Software Design

Software architecture is defined as the strategic design of an activity concerned with global requirements. Its solution is implemented in programming paradigms, architectural styles, component-based software engineering standards, architectural patterns, security, scale, integration, and law-governed regularities. Functional design, also described as tactical design, is an activity concerned with local requirements governing a solution such as algorithms, design patterns, programming idioms, refactoring, and low-level implementation. In this paper, I would like to introduce some concepts of software architecture and software design, as well as the relationship between them

Smart Node Networks Orchestration: A New E2E Approach for Analysis and Design for Agile 4.0 Implementation.

The field of cyber-physical systems is a growing IT research area that addresses the deep integration of computing, communication and process control, possibly with humans in the loop. The goal of such area is to define modelling, controlling and programming methodologies for designing and managing complex mechatronics systems, also called industrial agents. Our research topic mainly focuses on the area of data mining and analysis by means of multi-agent orchestration of intelligent sensor nodes using internet protocols, providing also web-based HMI visualizations for data interpretability and analysis. Thanks to the rapid spreading of IoT systems, supported by modern and efficient telecommunication infrastructures and new decentralized control paradigms, the field of service-oriented programming finds new application in wireless sensor networks and microservices paradigm: we adopted such paradigm in the implementation of two different industrial use cases. Indeed, we expect a concrete and deep use of such technologies with 5G spreading. In the article, we describe the common software architectural pattern in IoT applications we used for the distributed smart sensors, providing also design and implementation details. In the use case section, the prototypes developed as proof of concept and the KPIs used for the system validation are described to provide a concrete solution overview.

Introduction to Containerization

Are you a software engineer/developer/coder or maybe even a tech enthusiast who is thinking of agility, parallel development and reducing cost. In the early twentieth century, we witnessed the rise of Service Oriented Architecture (SOA), which is a software architecture pattern that allows us to construct large-scale enterprise applications that require us to integrate multiple services, each of which is made over different platforms and languages through a common communication mechanism, where we write code and multiple services talk to each other’s for a business use case, but sometimes we end up with one big monolithic code base whose maintenance becomes difficult. Nowadays clients are using cloud and paying for on-demand services without effectively utilizing resources. These problems invite micro-services. In this paper, I am going to discuss how one should use scale application in a production environment and local machine

A Systematic Review on Software Architectures for IoT Systems and Future Direction to the Adoption of Microservices Architecture

The Internet of Things-based systems and software allow computations anywhere at any time by interconnecting individuals, networks, services, computers and artefacts that allow autonomous systems to form digitized communities. As the blueprint for software-intensive applications, and software architecture that precise the complexity of a network’s planning, development, and changing phases to effectively and efficiently build complex IoT-driven applications. In any case, there exists no comprehensive analysis in the state of the research on the adoption of MSA for IoT systems. This study effort is needed to explore architectural concepts and practices for designing and developing IoT software to excel state-of-the-art for IoTs along with suggestions and recommendations for IoT software to the adoption of MSA to fulfil the identified gaps. A systematic analysis was coordinated, covering up the literature on existing IoT solutions by studying 140 qualitatively selected articles performed between 2005 and Jan 2020. One hundred forty articles were comprised in this SLR. The findings of this study demonstrated different research topics including software architectural styles, patterns, and models to build IoT software. This research presents cloud-based computing environments, autonomous, software-defined networking, and responsive applications, and IoT-driven agent-based systems, (1) thirteen MSA architectural and design patterns for IoTs and classification of patterns, (2) classification of software architectures for IoTs into nine main categories and their sub-categories, (3) twenty-three most investigated IoT challenges, and (4) mapping of IoT challenges with software architectural solutions. The study revealed the innovative work on IoT software architecture and trends that help in the creation and dynamic adaptation of IoT software for reusability, automation and human decision-making. The outputs of this SLR are useful in revealing many recommendations to the software industry, software engineering community, and computer sciences community with over the past 15 years of research into the adoption of MSA. This study reflects a distilled awareness of architectural practices and principles to assist researchers and practitioners in promoting information sharing software architectural roles and responsibilities for the Internet of Things software.

Implementation of Model-View-ViewModel (MVVM) Architecture Pattern in the Sistem Informasi Akademik UNIDA Gontor Mobile Application

Software architecture primarily tuned for moderating the rising software complexities and changes. Model-View-ViewModel (MVVM) is a software architectural pattern that facilitates a separation of development of the graphical user interface from the development of the back-end logic (the data model). University of Darussalam Gontor (UNIDA Gontor) is having an Academic System called Sistem Informasi Akademik (SIAKAD) which supports the management of its college’s data administration. Currently, the SIAKAD UNIDA Gontor’s performance is still far from optimal, mainly because some of its features aren’t user-friendly yet, especially when the SIAKAD UNIDA Gontor accessed from the mobile devices. Therefore, this research aims to implement the MVVM architecture pattern in the SIAKAD UNIDA Gontor mobile application, to increase its user-friendly aspect, especially for Android device users. This research is carried out with Waterfall development method, using Kotlin programming language and utilising Android Jetpack. Results from the app testing with Black Box method show that the application is running well and have no error. Next, results from the questionnaire distributed to the users (students, lecturers and BAAK staffs) show that the application run well and satisfying. From those trial results, show that the implementation of MVVM on SIAKAD UNIDA Gontor Android application has been successful according to the scenario and ready to be applied in the even semester of 2019/2020 campus’ academic year and so on (https://play.google.com/store/apps/details?id=com.amoled.sidago). Further research and development, can be directed to the addition of new features and can support another mobile operating system, such as iOS, Tizen, Harmony OS, etc.

Efficient Software Architecture Pattern for Accelerator Based Computing

Graphics Accelerators are increasingly used for general purpose high performance computing applications as they provide a low cost solution to high performance computing requirements. Intel also came out with a performance accelerator that offers a similar solution. However, the existing application software needs to be restructured to suit to the accelerator paradigm with a suitable software architecture pattern. In the present work, master-slave architecture is employed to convert CFD grid free Euler solvers in CUDA for GPGPU computing. The performance obtained using master-slave architecture for GPGPU computing is compared with that of sequential computing results.

Development of a Graphic Information System Applied to Quality Statistic Control in Production Processes

One of the advantages that organizations have when using an Information System is the control of their activities. This article develops an Information System that will allow an organization to graphically obtain the real results of a production process by applying Nelson's eight rules to determine if any measured variable is out of control. The software architecture pattern used is the Model View Controller (MVC) to keep the functionality of the application separate. The front-end, that is, the part that interacts with the users, was developed in ASP.NET as a web platform to provide the required services, JavaScript, HTML 5, Razor and Bootstrap. The back-end, which is the part that processes the entry of the front-end and performs the calculations, operations, communication with the database and reading of files, was developed with the C sharp programming language, the SQL Server database management system and the entity framework. As a result, the system sends an e-mail as an alarm with an explanation of what has happened when it detects that some measured variable is out of control by applying Nelson's rules. This allows the organization to make effective decisions in the processes involved.

Software architectural patterns in practice: an empirical study

Software architecture involves a series of decisions based on many factors in a wide range of software development. Architects face recurring issues in different software architecture design, and to reduce huge cost and risks, software architecture decisions can rely on a set of idiomatic patterns commonly named architectural styles or patterns. Architectural pattern determines the vocabulary of components and connectors that are used in instances of the pattern together with a set of constraints to combine the two. Little contemporary data exists to document actual practices used by software professionals when selecting and incorporating architectural patterns for their projects in industry. Therefore, a comprehensive survey of software professionals was conducted to attempt to discover these practices. This exploratory survey and its quantitative results offer opportunities for further interpretation and comparison. Data from this survey are presented in this paper and include characteristics of projects, practices, organizations, and practitioners related to the usage of architectural patterns. Some of the notable findings include that architectural patterns are widely used in software projects with the Model–View–Controller being the most common. Despite reported difficulties in incorporating architectural patterns, the majority of the software professionals revealed that patterns were the most essential for completing the projects. The most difficult pattern to implement and the most expensive to adopt was the peer-to-peer, while the easiest was the client–server.

Software architecture pattern selection model for Internet of Things based systems

The entire world is moving towards the era of smart technology. Internet of Things (IoT) is the key factor behind this revolutionary change. IoT converts real-world objects into interactive smart systems which can be controlled from remote locations. These physical real-world objects tagged as ‘Things’ in IoT should have a unique identity. These ‘things’ can be remotely controlled and monitored from anywhere in the world through Internet. Due to this feature it has been applied in various domains like home automation, patient health monitoring, agricultural sector, environment surveillance and so on. Due to the increased use of IoT-based system, there arises a need for a well-defined software architecture. Though various IoT developers follow their own design strategies for IoT architecture, there is a need for domain specific architecture for IoT applications. The authors propose a software architecture pattern selection model which can be followed in designing IoT systems. Non-functional requirements such as scalability, availability, reliability, security and heterogeneity determine the decision making of the proposed model. Analytical results prove that this model can be used as a reference model, for IoT developers in choosing a suitable software architecture pattern for their IoT system.

Generic platform for registration and online offering of assistance-on-demand (AoD) services in an inclusive infrastructure

An increasing percentage of the population needs assistance services for a wide range of activities related to their independent living, which can be delivered either by humans or by machines. While cloud computing and emerging ICT solutions have introduced new types of services and service delivery paradigms, it remains costly and difficult to set up and market assistance services addressing the needs of very narrow end-user groups. The current work presents the design of a novel open-source infrastructure (web-based platform) which enables diverse stakeholders to easily set up web-based assistance-on-demand platform instances. Each of these AoD instances can be used by service providers to register and offer assistance-on-demand (AoD) services for catering individual needs of persons with disabilities. In this way, narrow end-user groups can be reached and enjoy a gamut of assistance services. The AoD platform is implemented in the context of a larger Global Public Inclusive Infrastructure (GPII), which is being developed in the context of the Prosperity4All project. The functional requirements for the design of the AoD infrastructure were iteratively fine-tuned through the definition and analysis of representative use models (sets of personas and use cases). The AoD platform architecture consists of two major components: front-end (GUI) and back-end (service infrastructure). Their implementation is mainly based on the Django framework which enables a Model–Template–View (MTV) software architectural pattern with highly configurable and flexible components. The evaluation of a demonstration instance of the AoD platform with end-users identified its advantages and pointed out additional functionality needed: multi-language, multi-modality, embedded social media feeding, dedicated menu for highly flexible service, etc. The overall perceived usefulness of the specific demonstration AoD platform instance that underwent evaluation was higher than 80%. The proposed AoD platform provides a flexible and sufficiently generic web-based infrastructure for the cost-effective setup, registration and web publication of services that can accommodate a highly diverse range of assistance needs. Furthermore, it is suitable for use by a wide range of different stakeholder/user groups interested in addressing the needs of persons with disabilities or otherwise at risk of exclusion.

Privacy by designers: software developers’ privacy mindset

Privacy by design (PbD) is a policy measure that guides software developers to apply inherent solutions to achieve better privacy protection. For PbD to be a viable option, it is important to understand developers' perceptions, interpretation and practices as to informational privacy (or data protection). To this end, we conducted in-depth interviews with 27 developers from different domains, who practice software design. Grounded analysis of the data revealed an interplay between several different forces affecting the way in which developers handle privacy concerns. Borrowing the schema of Social Cognitive Theory (SCT), we classified and analyzed the cognitive, organizational and behavioral factors that play a role in developers' privacy decision making. Our findings indicate that developers use the vocabulary of data security to approach privacy challenges, and that this vocabulary limits their perceptions of privacy mainly to third-party threats coming from outside of the organization; that organizational privacy climate is a powerful means for organizations to guide developers toward particular practices of privacy; and that software architectural patterns frame privacy solutions that are used throughout the development process, possibly explaining developers' preference of policy-based solutions to architectural solutions. Further, we show, through the use of the SCT schema for framing the findings of this study, how a theoretical model of the factors that influence developers' privacy practices can be conceptualized and used as a guide for future research toward effective implementation of PbD.