Database Reference
In-Depth Information
table 10.1
Advantages of a Component-Based Development (CBD) Approach
Determining
Factor
Enterprise Challenge
Characteristics of the
Component-Based
Development (CBD) Approach
Quality
Consequences of software
application errors are often
catastrophic for enterprise systems.
Specification guidelines provide
rigor, assisted by a provisioning
process for engineering of quality
enterprise systems.
Cost savings
There is a need to reduce costs, be
competitive in providing functionality,
and exploit niche markets with
specialized requirements.
Component reuse results in
long-term cost savings.
Scalability
The requirements of responsiveness
vary across a group of users of the
enterprise systems.
Components can be implemented
and deployed in technology
corresponding to the envisaged
operational constraints and
requirements.
Consistency
The enterprise systems need to
adhere to a consistent architecture
that also enables flexibility and
innovation.
The enterprise system is organized
and developed based on the
consistency and constancy of the
components' interfaces.
Integration
There is a need to leverage on
existing investments in technology
and legacy applications.
This is enabled by
wrapping
of
legacy systems into components,
with consistent interfaces, which are
organized into an enterprise system.
Adaptability
Business processes change
dramatically especially because of
mergers and acquisitions (M&As).
This is enabled by loosely coupled
components with consistent
interfaces, which are organized into
an enterprise system.
Time to
market
There are rapidly reducing windows
of opportunity that need to be
exploited quickly.
An assembly, integration, and
implementation process is more
effective than redevelopment.
Business Fit
There is a need to constantly improve,
repurpose, and fine-tune the business
processes.
Components can be altered or
exchanged, while maintaining
consistent interfaces, which are
organized into an enterprise system.
is separated from its implementation; an implementation of a component may change, but as long
as its interface does not change, other components can continue to interact with this component
without experiencing any changes. Interfaces are mechanisms that enable enterprise applications
to be built as a constellation of cooperating components.
Enterprise components are classified according to where they reside, namely, client or server.
JavaBeans and ActiveX provide technologies for building reusable user interface client compo-
nents. The major advantage of client components is that they are downloadable to a client desktop
