Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 7,187 papers for “Architectural pattern”

The MVVM Architectural Pattern

Abhishek Mishra · Apress eBooks · 2017

Well over a billion apps have been developed for the iOS platform since its inception. Most of the early apps were rather simple and often developed by a single developer. Over the years, iOS apps have become increasingly complex pieces of software that often involve large, distributed teams of developers working in Agile environments with complex build and release pipelines.

Cited by 3

Architectural pattern for service collaboration

Agon Memeti, Betim Çiço · International Journal of Informatics and Communication Technology (IJ-ICT) · 2022

The aim of this paper is to propose a modeling framework, tailored to build efficient, elastic and autonomous applications from tasks and services. It includes integrated services to develop the software products, reusing on demand in-house services with specific requirements and flexible the representational state transfer (REST) services. The idea is to decouple authorization for reduced service dependency and to provide a possibility for developing the whole application by increasing the existing application flexibility. Based on the fact that there are different web application platforms that serve to offer services to users but they are not integrated; we propose a framework with high flexibility degree, especially integrating the most used services such: e-learning, administrative, and library services, as University services are concern.

Cited by 0Open access

The Reflective Blackboard Architectural Pattern

Otavio Rezende da Silva, Alessandro Fabricio Garcia, Carlos José Pereira de Lucena · 2007

Software architectures of large multi-agent systems (MASs) are inherently complex and have to cope with an increasing number of system-wide properties and their corresponding control policies. With the openness and increasing size and complexity of these systems a more sophisticated software architectural approach becomes necessary. In this context, we propose the Reflective Blackboard architectural pattern, which is the result of the composition of two other wellknown architectural patterns: the Blackboard pattern and the Reflection pattern. The proposed pattern provides, early in the architectural design stage, the context in which more detailed decisions related to systemic properties and associated policies can be made in late stages of MAS development. The pattern allows a better separation of concerns, supporting the separate handling of control strategies by means of the computational reflection technique. Moreover these control activities are handled independently from the application data and agents, providing a better architecture for real-life multi-agent systems. An electronic marketplace architecture, with the goal of interconnecting providers and consumers of goods and services to find one another and transact business electronically, is assumed as a case study through the paper to clarify all the expressed concepts and to show the applicability of our proposal.

Cited by 0

Pluggable Systems as Architectural Pattern

M. M. Mahbubul Syeed, Alexander Lokhman, Tommi Mikkonen et al. · 2015

In this paper we review the use of plug-in architectures as a technological platform for software ecosystems. Our observation is that the software community has viewed and used plug-ins as powerful extension mechanisms offering a wide range of quality properties. Looking beyond such low-level technical interpretation, we argue that pluggable systems should be perceived and treated as a higher level architectural pattern. In order to back our perspective we present the pattern following widely adopted documentation scheme, we show example usage of the pattern in the Eclipse ecosystem, and we discuss different implementation options of the pattern when building new technical solutions for ecosystems.

Cited by 8

Intent Peer: an Architectural Pattern ∗

M. Amoretti, M. Reggiani, F. Zanichelli et al. · 2008

Virtual Organizations (VOs) are transitory communities made of individuals and institutions coupled together by advanced communications technologies. Today’s VOs are more and more demanding in terms of efficiency and flexibility of the technological infrastructure. Envisioning VOs in which all participants are both resource providers and consumers, in a peer-to-peer fashion, seems to be an appropriate solution. This paper proposes a structure for programmed elements, i.e. Peers, sharing resources through a peer-to-peer network. Publishing and discovery of resource provision services are managed by the routing and communication modules. The first one creates publication/query messages and computes their destination, which is then used by the communication service to transport the message to the destination Peer. The Peer pattern enables Virtual Organizations whose participants collaborate to deploy, publish, discover, and consume heterogeneous resources (CPU, storage, bandwidth, applications). Example Community support systems is gaining more and more attention in application areas ranging

Cited by 0

Architectural pattern for service collaboration

International Journal of Informatics and Communication Technology (IJ-ICT) · Bulletin of Miscellaneous Information (Royal Gardens Kew) · 2023

The aim of this paper is to propose a modeling framework, tailored to build efficient, elastic and autonomous applications from tasks and services. It includes integrated services to develop the software products, reusing on demand in-house services with specific requirements and flexible the representational state transfer (REST) services. The idea is to decouple authorization for reduced service dependency and to provide a possibility for developing the whole application by increasing the existing application flexibility. Based on the fact that there are different web application platforms that serve to offer services to users but they are not integrated; we propose a framework with high flexibility degree, especially integrating the most used services such: e-learning, administrative, and library services, as University services are concern.

Cited by 0

An Architectural Pattern for Developing Renting Systems An Architectural Pattern for Developing Renting Systems

Haitham Hamza, Mohamed E. Fayad · 2008

Despite the fact that renting is, to some extend, an application dependent activity, it is still possible to extract many fundamental common aspects that if captured in an appropriate conceptual level, a stable renting model can be developed and reused to build a wide range of renting systems. In this paper we propose an architectural pattern that model the renting problem. This pattern aims to provide a model that captures the core aspects of the renting problem independent of any specific application or domain. We demonstrate, through illustrated examples, the usage of the proposed pattern under different renting scenarios in different applications. 1. SOFTWARE STABILITY AND STABLE ANALYSIS PATTERNS: BRIEF BACKGROUND The pattern proposed in this paper is based on the concept of Stable analysis patterns introduced in [2,3,4]. The idea behind stable analysis patterns is to analyze the problem under consideration in terms of software stability concepts [7]. Software stability stratifies the classes of the system into three layers: the Enduring Business Themes (EBTs) layer (contains classes that present the enduring and basic knowledge of the underlying industry or business, and hence, they are extremely stable), the Business Objects (BOs) layer (contains classes that map the EBTs of the system into more concrete objects. BOs are tangible and externally stable, but they are internally adaptable), and the Industrial Objects (IOs) layer (contains classes that map the BOs of the system into physical objects.). Figure 1 depicts the three layers of software stability model. The detailed characteristics of EBTs, BOs, and IOs and useful heuristics and examples of identifying these concepts in real applications can be found in [5,8,9]

Cited by 0

Towards Pattern Based Architectural Conformance Checking

Tobias Olsson · KTH Publication Database DiVA (KTH Royal Institute of Technology) · 2016

Patterns are a source of knowledge when architecting software systems. They provide abstract and time-tested solutions that show how a system should be structured to achieve needed qualities. However, when developing software there is a chance that small mistakes are introduced in the source code. Over time, these mistakes can accumulate and break the structure of the pattern and its qualities are lost. There are methods that can help find such errors, but none of these provide a pattern abstraction. In this work, we describe a method that raises the level of abstraction from checking individual dependencies to checking key dependencies in the pattern. We implement our method, apply it to check the Model-View-Controller pattern. We show that the method can find architectural problems in real source code and examine how removal of detected erosions affects the source code. We conducted an experiment in a software project setting to determine if using the method affects the number of architectural problems. Some project teams were randomly assigned to use a software service that automated our method. It checked how well their implementation conformed to Model-View-Controller every time they updated the source code. The experiment showed that developers that used the tool had significantly fewer detected architectural problems during the course of the project. Our method makes conformance checking easier to use. This might help increase the adoption of conformance checking in industry.

Cited by 0Open access

Architectural Patterns Revisited - A Pattern Language

Paris Avgeriou, Uwe Zdun · 2005

Architectural patterns are a key concept in the field of software architecture: they offer well-established solutions to architectural problems, help to document the architectural design decisions, facilitate communication between stakeholders through a common vo-cabulary, and describe the quality attributes of a software system as forces. Regrettably, finding and applying the appropriate architectural patterns in practice still remains largely ad-hoc and unsystematic. This is due to the lack of consensus in the community with respect to the “philosophy ” and granularity of architectural patterns, as well as the lack of a coherent pattern language. In this paper we attempt to establish common ground in the architectural patterns community by proposing a pattern language that acts as a super-set of the existing architectural pattern collections and categorizations. This language is particularly focused on establishing the relationships between the patterns and performs a categorization based on the concept of “architectural views”. 1

Cited by 186

APEP - An Architectural Pattern Evaluation Process

2019

A pattern describes a solution to a recurring problem in a given context.When writing such a pattern, the author faces several challenges.The first writing attempts are often vague and not clearly formulated and do not sufficiently describe the pattern.Other software engineers do not understand the pattern well enough and cannot use it to solve their problems.In this paper, we introduce APEP, an Architectural Pattern Evaluation Process.It allows conducting a review of an architectural pattern draft based on adaptations of sophisticated methods for architectural evaluation.In this paper, we design and present the Review of Intermediate Architectural Patterns (RIAP) as a method.To prove feasibility and applicability, we conducted two case studies based on an exemplary architectural pattern.

Cited by 0Open access

Architectural pattern detection and modeling in images

Quan, Long, Zhao, Peng · Rare & Special e-Zone (The Hong Kong University of Science and Technology) · 2015

Systems and methods are provided to facilitate architectural modeling. In one aspect, repetitive patterns are automatically detected and analyzed to generate modeled structural images such as building facades. In another aspect, structural symmetry is analyzed to facilitate architectural modeling and enhanced image generation.

Cited by 0