Towards an Enterprise Software Component Ontology

The paper describes an ontology of enterprise software components (ESCO). Its purpose is to reduce the conceptual gap between component specifications and their corresponding business descriptions, i.e., business processes and business entities. To this end, the different types of enterprise components and their semantic relationships are analyzed. The ontology axioms are formally expressed in description logics. ESCO contributes to a shared understanding of key concepts in application system development

Semantic Component Composition

Building complex software systems necessitates the use of component-based architectures. In theory, of the set of components needed for a design, only some small portion of them are "custom"; the rest are reused or refactored existing pieces of software. Unfortunately, this is an idealized situation. Just because two components should work together does not mean that they will work together. The "glue" that holds components together is not just technology. The contracts that bind complex systems together implicitly define more than their explicit type. These "conceptual contracts" describe essential aspects of extra-system semantics: e.g., object models, type systems, data representation, interface action semantics, legal and contractual obligations, and more. Designers and developers spend inordinate amounts of time technologically duct-taping systems to fulfill these conceptual contracts because system-wide semantics have not been rigorously characterized or codified. This paper describes a formal characterization of the problem and discusses an initial implementation of the resulting theoretical system.Comment: 9 pages, submitted to GCSE/SAIG '0

Towards an aspect weaving BPEL engine

This position paper proposes the use of dynamic aspects and the visitor design pattern to obtain a highly configurable and extensible BPEL engine. Using these two techniques, the core of this infrastructural software can be customised to meet new requirements and add features such as debugging, execution monitoring, or changing to another Web Service selection policy. Additionally, it can easily be extended to cope with customer-specific BPEL extensions. We propose the use of dynamic aspects not only on the engine itself but also on the workflow in order to tackle the problems of Web Service hot deployment and hot fixes to long running processes. In this way, composing aWeb Service "on-the-fly" means weaving its choreography interface into the workflow

Flexible Framework For A Web Transactional Application

Software development project becomes difficult because of the complexity in the business requirements, rigid framework and unpredictable performance. These cause difficulties to deliver the software on time, to maintain it and to adapt to new requirements. This research proposes a Web-Based Transactional Application Architecture Framework (WTBF) to simplify the development of a complex software project by using template approach that contains assembled pieces of reusable software components. The framework provides a generalized component-based architectural template that can be reused by the users (software developer and an independent software vendor) to develop multi-tier transactional applications within a specific domain or for a new software project. One of its significant benefits is that users can concentrate on their business components development tasks instead of spending time on redeveloping basic software infrastructure from the scratch. The WTBF framework is developed by using the Java 2 Technology and the Model View Controller (MVC) is used for the architectural model

Secure telemedicine system for home health care

This thesis describes a low-cost telemedicine system that provides home based patient care by linking patients with skilled nurses at the home care agency. The system employs compact vital signs sensors and a two-way real-time video conference over telephone lines. It stores the patient\u27s medical records, still images and enforces clinical pathways during the televisits. Physicians, paramedics, and nurses can then have access to these records from anywhere, securely, through a Web browser.;This document discusses the underlying technologies, the features implemented in the prototype, and the methodologies used in developing the software. The prototype uses the Enterprise Java Bean [EJB] architecture and emphasizes security and scalability. Preliminary experience of its use is presented. A performance analysis of the system\u27s behavior if it were scaled up has also been done