Database Reference
In-Depth Information
Business-driven and behavior-driven identifi cation of components and services are not yet
fully supported by the methods. Modeling from different viewpoints becomes an important
mechanism in managing system complexity by separating the concerns. The techniques
for the transformations of models that are at different levels of abstraction and their further
mapping to software code are not yet fully supported by the methods. All of the methods
provide an iterative and incremental development practice that becomes
de facto
standard
in software system development.
The way of controlling of the investigated methods should be further improved in the
spirit of CBD and WS. The ways of measurement of non-functional process parameters and
a proper process management approach must be defi ned in an improved way. Although most
of the investigated methods are accompanied with effective tools to support them, a more
sophisticated and comprehensive suite of tools is needed to support the variety of aspects of
component-based and service-oriented development process, defi ned well by the evaluation
framework's ways of thinking, working, modeling and controlling.
Business-driven and behavior-driven identifi cation of components and services are not yet
•
Business-driven and behavior-driven identifi cation of components and services are not yet
CBD Method Improvements
Current CBD methods and approaches do not defi ne the concepts of component and
service in a precise and implementation-independent way. Instead of making components
the focal point of the complete development process in order to gain the huge benefi ts of
the component way of thinking, the methods handle components at the implementation
and deployment phases, or just as another form of old-fashioned business objects. Methods
that have evolved from pure object-oriented backgrounds inherit diffi culties in recognizing
the fundamental nature of components, considering the componentization as a way of code
packaging. A more formal and systematic approach to component-based and service-oriented
development is needed covering the whole system life cycle with the component concepts
and principles integrated into each of the phases. Integration between the phases, such as
business, information, application and technology issues must be provided. This can be
done using general well-grounded component theory as the means to bridge the different
perspectives and viewpoints. A common CBD “language” used throughout the life cycle for
the integration of different principles, concepts and perspectives, and a smooth transition
among them must be ensured. In the framework for effective CBD methodology support
presented above, we have proposed guidelines towards a systematic and integrated approach
to component-based development. It has the potential to provide comprehensive, theoretical
and practical methodological support for the CBD and WS paradigms. The framework can
be seen as a fi rst step in arriving at truly component-based and service-oriented systems
development methodology engineering.
By following the requirements defi ned in the framework through the ways of thinking,
modeling, working, controlling and supporting, we can create a method that can be fully
applied in the new SOA and WS world. The most important elements of the next-genera-
tion CBD method are:
Standard defi nition of component and service concepts in consistent, contract-based,
and implementation-independent way.
•
Specifi cation of different component scope and granularity levels that are mutually
related by composition and collaboration relationships and used throughout the system
design and development.
•
