Rationale and Design Considerations for a Semantic Mediator in Health Information Systems

1998 ◽  
Vol 37 (04/05) ◽  
pp. 518-526 ◽  
Author(s):  
D. Sauquet ◽  
M.-C. Jaulent ◽  
E. Zapletal ◽  
M. Lavril ◽  
P. Degoulet
Keyword(s):  
Information Systems ◽  
Software Engineering ◽  
Health Information ◽  
Rapid Development ◽  
Heterogeneous Systems ◽  
Health Information Systems ◽  
Semantic Interoperability ◽  
Point Of View ◽  
Current State ◽  
Engineering Environment

AbstractRapid development of community health information networks raises the issue of semantic interoperability between distributed and heterogeneous systems. Indeed, operational health information systems originate from heterogeneous teams of independent developers and have to cooperate in order to exchange data and services. A good cooperation is based on a good understanding of the messages exchanged between the systems. The main issue of semantic interoperability is to ensure that the exchange is not only possible but also meaningful. The main objective of this paper is to analyze semantic interoperability from a software engineering point of view. It describes the principles for the design of a semantic mediator (SM) in the framework of a distributed object manager (DOM). The mediator is itself a component that should allow the exchange of messages independently of languages and platforms. The functional architecture of such a SM is detailed. These principles have been partly applied in the context of the HEllOS object-oriented software engineering environment. The resulting service components are presented with their current state of achievement.

scholarly journals Towards Specific Software Engineering Practices for Early-Stage Startups

2020 ◽  
pp. 18-22
Author(s):  
Jorge Melegati ◽  
Rafael Chanin ◽  
Afonso Sales ◽  
Rafael Prikladnicki
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Early Stage ◽  
Position Paper ◽  
Market Driven ◽  
Engineering Practices ◽  
Software Development Practices

Abstract In this position paper, our goal is to argue the need for specific software development practices to early-stage startups. In order to reach this goal, we discuss the consequences of innovative and market-driven contexts, which are two of the key elements when describing software startups. We also argue that these practices could be applied to innovative initiatives within established companies since they share similar characteristics and challenges as those from startups.

Rhodes, a Process Component Centered Software Engineering Environment

2001 ◽  
pp. 173-182 ◽  
Author(s):  
Bernard Coulette ◽  
Tran Dan Thu ◽  
Xavier Crégut ◽  
Dong Thi Bich Thuy
Keyword(s):  
Software Engineering ◽  
Engineering Environment ◽  
Process Component
Sign in / Sign up

Export Citation Format

Share Document