A Tool for the Model-Based Specification of Open Distributed Systems

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.

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>

The Reference Model for Open Distributed Processing (RM-ODP) defines a framework for the development of Open Distributed Processing (ODP) systems in terms of five viewpoints. Each viewpoint language defines concepts and rules for specifying ODP systems from the corresponding viewpoint. However, the ODP viewpoint languages are abstract and do not show how these should be represented. We treat in this paper the need for formal notation for behavioural concepts in the enterprise language. Using the Unified Modeling Language and Object Constraints Language UML/OCL, we define a formal semantics for a fragment of ODP behaviour concepts defined in the RM-ODP foundations part and in the enterprise language. We mainly focus on time, action, behaviour constraints, and policies. These concepts are suitable for describing and constraining the behaviour of the ODP enterprise viewpoint specifications.

Fault tolerance (FT) is a topic of major concern in achieving dependable systems, for both real time as well as non real time systems. The paper provides a model of achieving fault tolerance, based on the ISO/ITU Reference Model for Open Distributed Processing (RM-ODP). This reference model provides a system software engineering methodology for fault tolerance, an object based model of fault tolerance, system requirements for achieving fault tolerance in an open manner, modeling constructs and rules to enable a proper system specification of fault tolerance, and business rules in terms of policies to achieve a well formed system specification. All these aspects are discussed at some depth, but the author primarily focuses on how certain behavior can be specified and achieved in an object based system, the constructs of the Unified Modeling Language (UML) and the Object Constraint Language (OCL).

The foundation of any network management systems is a database that contains information about the network resources relevant to the management tasks. A network information model is an abstraction of network resources, including both managed resources and managing resources. In the SNMP-based management framework, management information is defined almost exclusively from a "device" viewpoint, namely, managing a network is equivalent to managing a collection of individual nodes. Aiming at, making use of recent advances in distributed computing and in object-oriented analysis and design, the Internet management architecture can also be based on the Open Distributed Processing Reference Model (RM-ODP). The purpose of this article is to provide an Internet Network Resource Information Model. First, a layered management information architecture will be discussed. Then the Internet network resource information model is presented. The information model is specified using Object-Z.

In the network management area, management information models are based on a center of managed objects to denote the abstract of network resource. Internet management standards only tell how to access management variables. Aiming at making use of recent advances in distributed computing and in object oriented analysis and design, an Internet management architecture can also be based on the Open Distributed Processing Reference Model (RM-ODP). The purpose of the article is to provide an Internet object oriented information model. First, a layered management information architecture is discussed. Subsequent sections of the article present the generic object oriented information model. The information model is specified using Object-Z.

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>

Network interoperability may be achieved by a number of different means.This paper addresses the usage of management mechanisms to realize this goal.Where interoperability by means of management systems is concerned,standardization bodies like ITU are frequently associated with standardized network element (NE)models.This paper presents another option, interoperability on the network level.The network level view is more abstract and comprises fewer details,simplifying many management tasks considerably. A natural consequence of the proposal is the relaxation of the requirements for standardized NE models.The generic network model defined in the G.85x series is the core element of the proposal.The functionality of the current version as well as the planned extensions (access networks,connection-less networks including IP)are described and so are the underlying mechanisms,the generic network architecture defined in G.805,the Logical Layered Architecture in M.3010 and the enhanced Reference Model for Open Distributed Processing (RM-ODP)in G.851.1.

RM-ODP (Reference Model Open Distributed Processing) standard prescribes architectural viewpoint specifications, but does not address traceability with requirement expression. In this article, we propose a three-layer approach to requirements modeling, from the system high level goals, to the detailed business rules and nonfunctional requirements. Then, these descriptions are connected to key elements of the RM-ODP enterprise viewpoint. This appoach is illustrated by a case study.

Service trading in mobile environments

The characteristics of the systems demanded the specification of the architecture to be based in a framework for distributed systems. The framework adopted, based in on the RM-ODP (reference model for open distributed processing) standard and on the RASDS (reference architecture for space data systems) initiative, was customized in order to follow the current service oriented architecture (SOA) technological trend. This framework has been applied to the ground systems software with the support of an UML modelling tool. In this process, four viewpoints were used to describe the reference architecture. The model created provides various advantages in new system developments. It enables a better interoperability and completeness of the systems being designed and developed and also greatly benefits the systems' maintainability namely the modularity, changeability and portability. Future developments and enhancements to this architecture include namely the specification of interfaces of key components, which enforces the compliance of new products with the reference architecture. The architecture is bringing direct benefits to harmonization process, especially by allowing true interoperability between European space segment initiatives

ODP RM reflections on open service ecosystems

BackgroundPredicting protein complexes from protein-protein interaction (PPI) networks has been studied for decade. Various methods have been proposed to address some challenging issues of this problem, including overlapping clusters, high false positive/negative rates of PPI data and diverse complex structures. It is well known that most current methods can detect effectively only complexes of size ≥3, which account for only about half of the total existing complexes. Recently, a method was proposed specifically for finding small complexes (size = 2 and 3) from PPI networks. However, up to now there is no effective approach that can predict both small (size ≤ 3) and large (size >3) complexes from PPI networks.ResultsIn this paper, we propose a novel method, called CPredictor2.0, that can detect both small and large complexes under a unified framework. Concretely, we first group proteins of similar functions. Then, the Markov clustering algorithm is employed to discover clusters in each group. Finally, we merge all discovered clusters that overlap with each other to a certain degree, and the merged clusters as well as the remaining clusters constitute the set of detected complexes. Extensive experiments have shown that the new method can more effectively predict both small and large complexes, in comparison with the state-of-the-art methods.ConclusionsThe proposed method, CPredictor2.0, can be applied to accurately predict both small and large protein complexes.

The precursor infiltration and pyrolysis (PIP) method for preparation of BN/SiO2 composites was used to improve mechanical properties, dielectric properties and feasibility of high temperature dielectric parts with large dimensions and complex shapes. In the processing procedure, the porous BN ceramic matrix was first successfully prepared by compacting the mixed powders of B and BN and then sintering them at a certain temperature under normal pressure of N2. The polycarbosilane (PCS) solution was vacuum infiltrated into porous BN ceramics at the room temperature and then at 800 °C in the air to depolimerize out amorphous SiO2, and sintered further at 1 300 °C in N2 to get BN/SiO2 composites. The microstructure of materials was studied by means of X-ray diffraction and electron probe micro analysis. The thermo-decomposition mechanism of PCS was investigated by a TG-DTA and infrared (IR) spectrum analysis. The flexural strengths were measured by the three-point bending method. The dielectric constant and the loss tangent were measured by the wave-guide method. The results show BN/SiO2 composites were fabricated. The obtained composites posses a flexural strength of 61.96–93.31 MPa, the dielectric constant in the range of 3.50–3.78 and the order of magnitude of the loss tangent at 10−3, which are good for the high temperature dielectric parts with large size and complex shapes.

RM-ODP (Reference Model of Open Distributed Processing) is a reference model for open information processing systems. Conformance is one of the key aspects of open systems. Conformance ensures the interworking in a multi-vendor information processing environment that may evolve over the time. An essential partitioning concept for open system is that of reference points (RPs). RPs consist of a set of interfaces together with potential interactions at these interfaces. RP specifications define conformance requirements, so that they can be used to determine the conformance of a system. However, the testing of RPs of real systems is restricted as their functionality is often very complex. Refinement of the RP structure is required to ease both their realization and also their testability. In particular, the incremental development of RPs that allows both the evolution of the system architecture and the step-by-step implementation by vendors should be supported. A new concept — that of an RP-facet — has been recently defined to structure RPs and to improve their testability. The focus of this paper is on structuring principles and dependence relations used by the RP-facet concept. They serve as a basis for incremental and efficient testing at RPs. An example taken from use scenarios on service access in open systems is elaborated in the paper.