Mastering Component-Based Development: From Business Modeling to Integrated Architecture

Component-Based Development Overview

Component-based development refines system-level coarse-grained control to fine-grained component-level control, allowing each component to have independent versioning, compilation, packaging, and deployment.

It enables product configuration and sales by assembling independent components, simplifies configuration management, development, testing, packaging, and release, and isolates component upgrades from affecting other components.

Business Modeling and Business Component Phase

Business modeling focuses on business architecture and data architecture derived from end‑to‑end process analysis. Business components are high‑cohesion, low‑coupling groups of related business functions identified through process decomposition and CRUD matrix analysis.

Data modeling at this stage produces conceptual models that later become physical models and data entity components, defining core master data and business documents.

Software Requirement Phase

Business components are refined into system use cases, which are then detailed into system requirements. Interaction points between business components are described early, and data modeling progresses from conceptual to logical models, linking system operations to data objects.

System Modeling and Technical Component Phase

System modeling translates business components into technical components (UI, logic, data layers, etc.) while maintaining high cohesion and avoiding cross‑layer calls. Technical components are organized hierarchically (UI → Logic → Data) and laterally within the same layer.

Key deliverables include a mapping of business to technical components, component call and dependency diagrams, interface design documents, reusable component analysis, component package and deployment views, and an overall product structure view.

Implementation Phase

Implementation focuses on platform support for independent component packaging, testing, and deployment. Modern microservice and front‑back separation frameworks allow front‑end and back‑end components to be built and deployed separately, enabling automated unit testing and isolated version upgrades.

Business Architecture Design

Business architecture defines and identifies business components based on high cohesion and low coupling, often using IBM’s CBM component model. For example, a procurement domain can be split into bidding management, procurement management, master data management, and performance analysis components.

Logical Architecture Design

The logical architecture follows a three‑tier model: data layer (shared master data and component‑specific CRUD), business logic layer (service‑oriented implementation via platform services or visual BPEL tools), and front‑end presentation layer (JSP, HTML, Vue, React, etc.) that consumes logic layer services.

Technical Architecture Design

Technical architecture refines the traditional layered model with SOA and componentization, emphasizing the business logic layer (service components, data access, internal modules, service bus) and the web container layer implementing MVC patterns (e.g., Java Struts).

Integration Architecture Design

Business components expose interfaces as web services connected via an enterprise service bus. Internally, OSGi‑based soft bus modules provide dynamic loading and service registration, achieving loose coupling and high reusability.

Note: In contemporary microservice architectures, decentralized service registries often replace OSGi‑style internal buses.

Overall Component Framework Integration

Components integrate vertically with PaaS platform services and horizontally through business process‑driven collaboration, forming a complete enterprise application when combined with portal and outer‑layer frameworks.

Application Framework Integration

In private‑cloud PaaS environments, a reusable, configurable outer UI framework integrates with portals for single sign‑on, loads system parameters, and dynamically assembles platform technical components and business components based on configuration files.