Topic
Reference architecture
About: Reference architecture is a research topic. Over the lifetime, 11062 publications have been published within this topic receiving 196475 citations.
Papers published on a yearly basis
Papers
More filters
Book•
01 Jan 1996TL;DR: This study uses design patterns to present platform independent architecture to help extend the usability of any software system and provide structural notations for anySoftware system.
Abstract: ion and object-oriented organization, Event-based, implicit invocation Pattern-Oriented Software Architecture, A System of Patterns Volume 1 – Frank. Format: pdf Pattern-Oriented Software Architecture Volume 1: A System of Patterns by Frank Buschmann, Regine Meunier, Hans Rohnert and Peter. Full Text: PDF Volume 40 Issue 1, January 2015 Service-Oriented Architecture is an architectural style where different heterogeneous components share Robert Hanmer, Patterns for Fault Tolerant Software, Wiley Publishing, 2007. 11. Pattern-Oriented Software Architecture Volume 1: A System of Patterns, Pattern,Oriented Pattern oriented software architecture pdf free download – i6fw9. Robert Hanmer, "Pattern-oriented Software Architecture For Dummies" 2013 / ISBN-10: 1119963990 / 384 pages / PDF / 31 MB Science, Engineering and Applications", volume 1 ed. by David C. Wyld, Jan Zizka, Dhinaharan Nagamalai Kumar Saurabh Singh 1,*, Dominique Thual 2, Roberto Spurio 1 and Nicola information management is important especially when a large volume of F., Meunier, R., Rohnert, H. Pattern-Oriented Software Architecture: A System. Pattern-Oriented Software Architecture Volume 2 Patterns for Concurrent and Networked Architecture Volume 2 Patterns for Concurrent and Networked Objects.pdf: Sponsored Link udp://tracker.coppersurfer.tk:6969/announce: 2 hours 0 1. extend the usability of any software system we have high degree of user Architectural patterns (1) provide structural notations for any software system. In spite of abundant tools and literature about mobile educational software, the lake of a This study uses design patterns to present platform independent architecture to support Enter the password to open this PDF file: Pattern-Oriented Software Architecture, Volume 1: A System of References (19), Cited In (1). What software architecture is and what it is not, Other points of view, Stal: Pattern-Oriented Software Architecture, A System of Patterns, Volume 1, John. Frank Buschmann: Pattern-Oriented Software Architecture Volume 4: A Pattern Language for Distributed Computing. Download PDF MOBi EPUB Kindle.
1,364 citations
TL;DR: This paper analyzes the MEC reference architecture and main deployment scenarios, which offer multi-tenancy support for application developers, content providers, and third parties, and elaborates further on open research challenges.
Abstract: Multi-access edge computing (MEC) is an emerging ecosystem, which aims at converging telecommunication and IT services, providing a cloud computing platform at the edge of the radio access network MEC offers storage and computational resources at the edge, reducing latency for mobile end users and utilizing more efficiently the mobile backhaul and core networks This paper introduces a survey on MEC and focuses on the fundamental key enabling technologies It elaborates MEC orchestration considering both individual services and a network of MEC platforms supporting mobility, bringing light into the different orchestration deployment options In addition, this paper analyzes the MEC reference architecture and main deployment scenarios, which offer multi-tenancy support for application developers, content providers, and third parties Finally, this paper overviews the current standardization activities and elaborates further on open research challenges
1,351 citations
Patent•
03 Nov 2000TL;DR: An execution architecture, a development architecture and an operations architecture for a netcentric computing system are described in this paper, where the purpose of the development environment is to support the tasks involved in the analysis, design, construction and maintenance of business systems, as well as the associated management processes.
Abstract: An execution architecture, a development architecture and an operations architecture for a netcentric computing system. The execution architecture contains common, run-time services required when an application executes in the netcentric computing system. The development architecture is the production environment for one or several systems development projects as well as for maintenance efforts. The purpose of the development environment is to support the tasks involved in the analysis, design, construction, and maintenance of business systems, as well as the associated management processes. It is important to note that the environment should adequately support all the development tasks, not just the code/compile/test/debug cycle. The operations architecture is a combination of tools and support services required to keep a production system up and running efficiently.
1,220 citations
01 Jan 2006
TL;DR: This Reference Model for Service Oriented Architecture is an abstract framework for understanding significant entities and relationships between them within a serviceoriented environment, and for the development of consistent standards or specifications supporting that environment, based on unifying concepts of SOA.
Abstract: This Reference Model for Service Oriented Architecture is an abstract framework for understanding significant entities and relationships between them within a serviceoriented environment, and for the development of consistent standards or specifications supporting that environment. It is based on unifying concepts of SOA and may be used by architects developing specific service oriented architectures or in training and explaining SOA. A reference model is not directly tied to any standards, technologies or other concrete implementation details. It does seek to provide a common semantics that can be used unambiguously across and between different implementations. The relationship between the Reference Model and particular architectures, technologies and other aspects of SOA is illustrated in Figure 1. While service-orientation may be a popular concept found in a broad variety of applications, this reference model focuses on the field of software architecture. The concepts and relationships described may apply to other "service" environments; however, this specification makes no attempt to completely account for use outside of the software domain.
1,216 citations
TL;DR: In this article, the authors propose a feature model that captures commonality as an AND/OR graph, where AND nodes indicate mandatory features and OR nodes indicate alternative features selectable for different applications, and it is used to define parameterized reference architectures and appropriate reusable components instantiatable during application development.
Abstract: Systematic discovery and exploitation of commonality across related software systems is a fundamental technical requirement for achieving successful software reuse By examining a class/family of related systems and the commonality underlying those systems, it is possible to obtain a set of reference models, ie, software architectures and components needed for implementing applications in the class FORM (FeaturedOriented Reuse Method) supports development of such reusable architectures and components (through a process called the “domain engineering”) and development of applications using the domain artifacts produced from the domain engineering FORM starts with an analysis of commonality among applications in a particular domain in terms of services, operating environments, domain technologies, and implementation techniques The model constructed during the analysis is called a “feature” model, and it captures commonality as an AND/OR graph, where AND nodes indicate mandatory features and OR nodes indicate alternative features selectable for different applications Then, this model is used to define parameterized reference architectures and appropriate reusable components instantiatable during application development Architectures are defined from three different viewpoints (subsystem, process, and module) and have intimate association with the features The subsystem architecture is used to package service features and allocate them to different computers in a distributed environment Each subsystem is further decomposed into processes considering the operating environment features Modules are defined based on the features on domain technology and implementation techniques These architecture models that represent an architecture at different levels of abstraction are derived from the feature hierarchy captured in the feature model Modules serve as basis for creating reusable components, and their specification defines how they are integrated into the application (eg, asdis integration of predcoded component, instantiation of parameterized templates, and fillingdin skeletal codes) Our experiences have shown that for the electronic bulletin board and the private branch exchange (PBX) domains, “features” make up for a common domain language and the main communication medium among application users and developers Thus, the feature model well represents a “decision space” of software development, and is a good starting point for identifying candidate reusable components
1,022 citations