759 research outputs found
A Comparison between EJB and COM+ Business Components, Case Study: Response Time and Scalability
Most distributed system architectures are designed as a three-tier systems consisting of a thin-client, middleware and a database. The overall performance of such systems depends on the performance of each tier individually and the overhead incurred by the collaboration between these three tiers. Nowadays, the two most popular middleware systems are: Microsoft’s .NET platform and Sun’s Java 2 Enterprise Edition (J2EE) platform. In J2EE, the middle tier infrastructure is called Enterprise JavaBeans (EJB) and in the .NET framework, it is called Component-Oriented Middle-Tier (COM+). Usually, the middle tier provides the business logic (any code that is not specifically related to storing and retrieving data, or formatting data for display to the user) and the performance of this tier is crucial to the overall performance of the distributed system
An architecture and execution environment for component integration rules
The Integration Rules (IRules) project at Arizona State University
(http://www.eas.asu.edu/~irules) is developing a declarative event-based
approach to component integration. Integration rules are based on the concept
of active database rules, providing an active approach for specifying event-
driven activity in a distributed environment. The IRules project consists of a
knowledge model that specifies the IRules Definition Language and an execution
model that supports integration rule execution. This research focuses on the
execution model and the architectural design parts of the IRules project. The
main objective of this research is to develop a distributed execution
environment for using integration rules in the integration of black-box
components. In particular, this research will investigate the design of an
architecture that supports the IRules semantic framework, the development of
an execution model for rule and transaction processing, and the design of a
rule processing algorithm for coordinating the execution of integration rules.
This research will combine the distributed computing framework of Jini, the
asynchronous event notification mechanism of the Java Message Service (JMS),
and the distributed blocking access functionality of JavaSpaces to support
active rule processing in a distributed environment. The limitations of the
underlying Enterprise JavaBeans (EJB) component model pose transaction
processing challenges for the integration process. This research will develop
a suitable transaction model and processing logic to overcome the limitations
of the underlying EJB component model. Furthermore, the architectural design
will allow an easy extension of the system to accommodate other component
models. This research is expected to contribute to nested rule and transaction
processing for active rules that have not been previously addressed in
distributed rule processing environments. The development of the IRules
execution environment will also contribute to the use of distributed rule-
based techniques for eventdriven component integration
Attribute based component design: Supporting model driven development in CbSE
In analysing the evolution of Software Engineering, the scale of the components has increased, the requirements for different domains become complex and a variety of different component frameworks and their associated models have emerged. Many modern component frameworks provide enterprise level facilities and services, such as instance management, and component container support, that allow developers to apply if needed to manage scale and complexity. Although the services provided by these frameworks are common, they have different models and implementation. Accordingly, the main problem is, when developing a component based application using a component framework, the design of the components becomes tightly integrated with the framework implementation and the framework model is embedded in the component functionality, and hence reduces reusability. Another problem arose is, the designers must have in-depth knowledge of the implementation of a component framework to be able to model, design and implement the components and take advantages of the services provided. To address these problems, this research proposes the Attribute based Component Design (AbCD) approach which allows developers to model software using logical and abstract components at the specification level. The components encapsulate the provided functionality, as well as the required services, runtime requirements and interaction models using a set of attributes. These attributes are systemically derived by grouping common features and services from light weight component frameworks and heavy weight component frameworks that are available in the literature. The AbCD approach consists of the AbCD Meta-model, which is an extension of the บML meta-model, and the Component Design Guidelines (CDG) that includes core Component based Software Engineering principles to assist the modelling process for designers. To support the AbCD approach, an implementation has been developed as a set of plug-ins, called the AbCD tool suite, for Eclipse IDE. An evaluation of the AbCD approach is conducted by using the tool suite with two case studies. The first case study focuses on abstraction achieved by the AbCD approach and the second focuses on reusability of the components. The evaluation shows that the artefacts produced using the approach provide an alternative architectural view to the design and help to re-factor the design based on aspects. At the same time the evaluation process identified possible improvements in the AbCD meta-model and the tool suite constructed. This research provides a non-invasive approach for designing component based software using model driven development
Recommended from our members
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
An overview to Software Architecture in Intrusion Detection System
Today by growing network systems, security is a key feature of each network
infrastructure. Network Intrusion Detection Systems (IDS) provide defense model
for all security threats which are harmful to any network. The IDS could detect
and block attack-related network traffic. The network control is a complex
model. Implementation of an IDS could make delay in the network. Several
software-based network intrusion detection systems are developed. However, the
model has a problem with high speed traffic. This paper reviews of many type of
software architecture in intrusion detection systems and describes the design
and implementation of a high-performance network intrusion detection system
that combines the use of software-based network intrusion detection sensors and
a network processor board. The network processor which is a hardware-based
model could acts as a customized load balancing splitter. This model cooperates
with a set of modified content-based network intrusion detection sensors rather
than IDS in processing network traffic and controls the high-speed.Comment: 8 Pages, International Journal of Soft Computing and Software
Engineering [JSCSE]. arXiv admin note: text overlap with arXiv:1101.0241 by
other author
A Framework For Dynamic Updating In Component-based Software Systems
Setiap sistem perisian (software) perlu dikemas kini setiap masa bagi pelbagai alasan seperti penetapan pepijat (fixing bugs)
Every software system needs to be updated over time for different reasons such as fixing bugs, upgrading its components, or adapting the system in response to its
environment's changes
Towards implementing integrated building product libraries
Electronic product catalogues and brochures are gaining
popularity but there is little agreement on content, format and
searching methods. This limits their usability and integration with
existing construction software tools. This paper examines a productmodelling
approach to delivering building product information and
describes a proposed multi-tier client-server environment. ISO/STEP
and IAI/IFC building product models are considered to facilitate
representation, exchange and sharing of product information. The
proposed architecture incorporates scalability with middleware
components that would provide single or few points of entry to
integrated product information. This paper is part of a research
project, which builds on the results of related projects including
ConstructIT Strategy, PROCAT-GEN, Active Catalog, COMBINE and ARROW,
towards implementing the required software components
- …