Database Reference
In-Depth Information
Way of Working
The underlying way of working of a CBD method should focus on:
•
Full component/service lifecycle.
• The full component lifecycle should be provided including the activities of business
component modeling, component architecture design and specifi cation, acquisition of
components, component discovering and identifi cation, modifi cation, binding, wrap-
ping, assembling, testing, execution and maintenance.
•
Traceable component and service concepts.
• Make a component concept traceable and consistent throughout the system develop-
ment life cycle, i.e., each phase in the component life cycle should transfer concepts
to the corresponding development process phase.
•
Business-driven identifi cation of components and services.
• Services and components must be identifi ed and defi ned in a business-driven way as
larger-grained, loosely coupled system units that can communicate synchronously, as
well as asynchronously. They should correspond to real business activities and add a
measurable business value to their consumers. In this way, business requirements and
needs are seamlessly mapped to fi rst-cut component-based, service-oriented system
architecture.
•
Integration of different views and viewpoints.
• The method should provide techniques for integrating multiple views and perspec-
tives on the component, e.g., specifi cation vs. implementation components, business
vs. technical components, and entity vs. process components in the context of different
phases in the development process.
•
Providing model transformations and code generation.
• The method should provide effective ways for transformation of Computational
Independent Model (CIM) into Platform Independent Model (PIM) and further into
Platform Specifi c Model (PSM) according to the chosen technology platform, as well
as software code generation for that platform from PSM (or directly from PIM) (OMG,
2003). The defi ned models should be kept in synchronization with the generated code,
according to the principles of round-trip engineering.
•
Iterative and incremental development practice.
• CBD naturally supports iterative and incremental development, by breaking the
complex problem down into smaller parts, and defi ning possible phases, increments
and opportunities for parallel work inside a development process. Furthermore, a rigor-
ous, repeatable refi nement process through all presented component-based lifecycle
phases should be provided to arrive at a software solution that meets original business
requirements using an easily traceable pathway.
Way of Controlling
The underlying way of controlling of a CBD method should focus on:
Support for the measurement of non-functional process parameters.
•
• The method should defi ne quantitative and qualitative measures based on non-func-
tional parameters and associating proper control points in the lifecycle phases. CBD
targets a market-driven application assembly model, where non-functional issues,
