Technology harmonization - developing a reference architecture for the ground segment software

The Internet of Things Architecture (IoT-A) approach of using viewpoints for the Reference Model and Architectures is consistent with most standard approaches for architecture — although there is little agreement on the specific viewpoints. OGC typically uses the viewpoints of RM-ODP (ISO/IEC, Reference Model for Open Distributed Processing) for many reasons including: RM-ODP is an international standard, and the five viewpoints defined by RM-ODP are manageable versus approaches using a larger number of viewpoints. Distributed systems can be very large and complex and the many different considerations which influence their design can result in a substantial body of specification, which needs a structuring framework if it is to be managed successfully. The purpose of the RM-IoT is to define such a approch. The Reference Model for IoT (RM-IoT) provides a framework within which support of distribution, inter-working and portability can be integrated. It defines: an Internet object model, architectural concepts and architecture for the development of IoT systems in terms of five viewpoints. However, RM-IoT is a meta-model. Indeed, the viewpoint languages are abstract in sense that they define what concepts should be supported and not how these concepts should be represented using the UML meta-modeling approach. In this paper, we report on the definition and address of the syntax and semantics for a fragment of IoT object concepts defined in the RM-IoTfoundations part and in the information language.

Interoperability between autonomous decentralized systems needs support of an information service that can provide dynamic knowledge about available service providers within the network. We describe trading service. Trading is an essential infrastructure function indicated by the ODP (open distributed processing) reference model, a meta model of heterogeneous distributed processing. The purpose of trading is to support location transparency of services: it hides the location of service providers, even if they are located in separate, autonomous domains. Cooperation between trading service providers (trader) supports federation transparency, i.e. hides differences of technology used in separate domains. In cooperation, the traders have to mediate service type differences, negotiate policy differences and tolerate technology differences between domains. Together with other fundamental functions trading offers a platform for open distributed computing between autonomous subsystems.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">&gt;</ETX>

The author explains what management of a distributed system is and why it is needed in an open distributed processing (ODP) environment. An ODP environment is characterized by very large numbers of computer systems which interact to support a diverse range of applications. The author defines the basic management concept of a managed object and introduces the domain as a means of grouping objects to specify management policy and structure the overall management to cope with the complexity of an ODP environment. Management is related to the five viewpoints (enterprise, information, computation, engineering, and technology) defined within the ODP reference model. Problems in using the open systems interconnection management framework for distributed systems are also discussed.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">&gt;</ETX>

Since the Internet of Things (IoT) will be entwined with everything we use in our daily life, the consequence of security flaws escalates. Smart objects will govern most of the home appliances and car engines yielding potential disaster scenarios. In this context, successful attacks could lead to chaos and scary scenarios (www.darkreading.com). Unprotected personal information may expose sensitive and embarrassing data to the public and attacks may threaten not only our computers and smart devices, but our intimacy and perhaps our lives too. Because persons and objects will be bonded with each other, user consent becomes critical. Therefore, thing, object, and user Identity will be the focus of future IoT security solutions, yielding a Trust, Security, and Privacy (TSP) paradigm, which may constitute the Achilles' heel of IoT. While security issues are quite straightforward, mainly from background knowledge, privacy issues are far more complex. Privacy constitutes a rather challenging task, even for the m...

A Reference Architecture for provisioning of Tools as a Service: Meta-model, Ontologies and Design Elements

Service-Oriented Architecture (SOA) is first introduced, and then the software architecture and development methods of information systems based on SOA are designed. Finally, the architecture and development methods are implemented in an enterprise information system, which can not only exchange and process a variety of information but also achieve real-time perception of information. The practice of the information system proves that systems based on SOA are of high reliability and security, good maintenance and expandability.

ContextDigital Twin-based predictive maintenance systems are frequently integrated into complex systems. The success of the integration depends on the design of the system. A Reference Architecture can be used as a blueprint to design Application Architectures rapidly and consistently for various application domains, resulting in a reduced time-to-market. ObjectiveThe main objective of this study is to develop and evaluate a Reference Architecture designed using renowned software architecture methods. MethodA domain analysis was performed to gather and synthesize the literature on Digital Twin-based predictive maintenance systems, which we used to model the key features. We applied UML diagrams to design the reference architecture based on the feature model. We evaluated the reference architecture using three case studies. ResultsWe derived three views for Digital Twin-based predictive maintenance systems. For the user's view, we developed a context diagram. We developed a package diagram for the structural view, and we designed a layered view to show the system's decomposition in layers. We designed an Application Architecture for each case study based on the study's features using each Reference Architecture view. Additionally, we designed a deployment view to describe the hardware and software and its environment. ConclusionWe demonstrated that the methods of creating a Reference Architecture could be used in the Digital Twin-based predictive maintenance domain and showed how an Application Architecture could be designed in this context.

A growing number of business process management systems is under development both in academia and in practice. These systems typically are based on modern system engineering principles, such as service-oriented architecture. At the same time, the advent of big data analytics has changed the scope of these systems, including functionality such as data mining. However, existing reference architectures for business process management systems date back 20 years and, consequently, are not up-to-date with these modern developments. To fill the gap, this article proposes an up-to-date reference architecture, called BPMS-RA, for modern business process management systems. BPMS-RA is based on analysis of recent literature and of existing commercial implementations. This reference architecture aims to provide a guideline template for the development of modern-day business process management systems by specifying functions and interfaces that need to be provided by these systems as well as a set of quality criteria that they need to meet.

This chapter presents a possible reference technological architecture for eGovernment projects, based on the service-oriented architecture (SOA) paradigm and related technologies and approaches. Such a reference architecture leverages the Italian experience called SPCoop (in Italian Sistema Pubblico di Cooperazione, possible English translation as “nationwide cooperative system”), which was designed recently and subsequently developed and used in ongoing Italian projects. It is a refinement of the reference architecture introduced in Chap. 9 and introduces technological details and software elements for modern eGovernment infrastructures. In particular, Sect. 10.1 provides some organizational and strategic guidelines that the governments and other political bodies should consider when setting up a reference architecture for eGovernment. Section 10.2 introduces basic concepts and definitions which are useful in the following of the chapter. Section 10.3 provides an overview of the reference architecture, whereas Sects. 10.4, 10.5, 10.6, and 10.7 provide technical insights on the different elements of the reference architecture. Finally Sect. 10.8 compares the presented architecture with similar initiatives currently undertaken in Europe.

In this chapter, we present an industrial case study for the creation and usage of architectural knowledge. We first introduce the business domain, service portfolio, and knowledge management approach of the company involved in the case. Next, we introduce a Service-Oriented Architecture (SOA) infrastructure reference architecture as a primary carrier of architectural knowledge in this company. Moreover, we present how we harvested architectural knowledge from industry projects to create this reference architecture. We also present feedback from early reference architecture users. Finally, we conclude and give an outlook to future work.

The current approach to the design, maintenance, and governance of service-oriented architecture (SOA) solutions has focused primarily on flow-driven assembly and orchestration of reusable service components. The practical application of this approach in creating industry solutions has been limited, because flow-driven assembly and orchestration models are too rigid and static to accommodate complex, real-world business processes. Furthermore, the approach assumes a rich, easily configured library of reusable service components when in fact the development, maintenance, and governance of these libraries is difficult. An alternative approach pioneered by the IBM Research Division, model-driven business transformation (MDBT), uses a model-driven software synthesis technology to automatically generate production-quality business service components from high-level business process models. In this paper, we present the business entity life cycle analysis (BELA) technique for MDBT-based SOA solution realization and its integration into service-oriented modeling and architecture (SOMA), the end-to-end method from IBM for SOA application and solution development. BELA shifts the process-modeling paradigm from one that is centered on activities to one that is centered on entities. BELA teams process subject-matter experts with IT and data architects to identify and specify business entities and decompose business processes. Supporting synthesis tools then automatically generate the interacting business entity service components and their associated data stores and service interface definitions. We use a large-scale project as an example demonstrating the benefits of this innovation, which include an estimated 40 percent project cost reduction and an estimated 20 percent reduction in cycle time when compared with conventional SOA approaches.

Peer-to-peer (P2P) applications are extremely popular on the Internet because they allow users to share information in a decentralized manner. Internet users use file-sharing applications (e.g., BitTorrent, KaZaA) to share and exchange files and collaboration applications (e.g., Jabber, Groove) to exchange chat messages and work on shared documents. A reference architecture for a domain provides an architecture template which can be used as a starting point for designing the software architecture of a system in that domain. Despite the popularity of P2P applications there is no reference architecture for the P2P domain. This paper presents a reference architecture for the P2P domain. The reference architecture has been designed to satisfy the concerns that a P2P application needs to address. The reference architecture takes a service-centric view of the P2P domain. The reference architecture can be used to describe the structure of existing P2P applications and middlewares. The paper validates the reference architecture by describing the structure of some of the existing P2P applications and middlewares using the reference architecture

With the convergence of information and telecommunication technologies, the vision of the `Smart City' is fast becoming a reality. City governments in a growing number of countries are capitalizing on these advances to enhance the lives of their citizens and to increase efficiency and sustainability. In this paper, we elaborate on smartCityRA, a reference architecture for Smart City projects, which serves as the design language for creating smart cities blueprints. Such a blueprint caters for diverse stakeholders, devices, platforms, and technologies. We report on our experience in carrying out a proof-of-concept use case with a major telecommunication provider in the UAE. In doing so, we refined our multiple-view model of the initial smartCityRA reference architecture. We show that Data in smart city applications drive the entire development lifecycle and should be considered early in the development cycle. In addition, Data affects all the other views in the smartCityRA and hence the Data View needs to be at the heart of the entire smartCityRA. Realizing the Data view using a component like a Data Hub helped in creating a central integration location for disparate data from different sources, thus reliving developers from dealing with several entities individually. Finally, we show that any smart city reference architecture, like smartCityRA, should be at the right level of abstraction to enable the flexibility of adoption and adaptation by different stakeholders and components.

In general, a common reference architecture can be derived for Software as a Service (SaaS). However, while designing particular applications one may derive various application design alternatives from the same reference SaaS architecture specification. To meet the required functional and nonfunctional requirements of different enterprise applications it is important to model the possible design so that a feasible alternative can be defined. In this paper, we propose a systematic approach and corresponding tool support for guiding the design of SaaS application architectures. The approach defines a SaaS reference architecture, a family feature model and a set of reference design rules. Based on the business requirements an application feature model is defined using the family feature model. Selected features are related to design decisions and a SaaS application architecture design is derived.

Large-scale distributed system, such as educational system, are difficult to develop due to their complex and decentralized nature. service oriented architecture (SOA) is a new form of distributed software architecture. The service oriented architecture facilitates the development of such systems by supporting modular design, application integration and interoperation, and software reuse. With open standards, such as XML, SOAP, WSDL and UDDI, the service oriented architecture supports interoperability between services operating on different platforms and between applications implemented in different programming languages. In this paper, In this paper, we propose software architecture for design and develop for a distributed e-education system in the way of service oriented architecture. We will explain what this e-education system concerns, how it is developed, and what services it provides.