How to Design Effective Business Architecture: Principles, Methods, and a Coupon Case Study

Introduction

Business architecture is often overlooked by developers who chase new technologies, yet technology must serve business. A well‑designed business architecture isolates business domains, separates business from the platform, and reveals overall workflow, capabilities, and domain objects. The next two articles will focus on business architecture.

1. What Is Business Architecture

Business architecture is a type of system architecture. According to the encyclopedia, a business involves “more than one organization, a common goal, and a series of processes achieved through information exchange, each with a clear purpose and lasting over time.” Key concepts are organization, goal, and process.

Organization : the people or groups involved (e.g., sales, finance, product, R&D, support).

Goal : the purpose and value of the business.

Process : the series of steps, such as coupon creation, issuance, usage, and refund.

From these we derive stakeholders (beneficiaries) and business processes (fixed workflows that can be broken into sub‑processes).

Business Architecture = Business Goal + Business Process + Business Elements . The most important task is to identify the processes and the elements within them, i.e., the relationships among business elements.

2. Characteristics of Business Architecture

Business architecture should reflect two characteristics: flow and hierarchy.

Flow : the lifecycle of a business, from creation to usage.

Hierarchy : typically modeled as scene layer, product‑function layer, domain‑model layer, and dependency layer.

3. Methods for Business Architecture

The four steps are systematic thinking, decomposition, abstraction, and pattern.

Systematic Thinking : analyze relationships among business components (e.g., coupon business involves audience selection, risk control, activities, venues, discounts, transactions, vouchers).

Decomposition : break the overall workflow into major processes and then into finer sub‑processes to uncover business elements.

Abstraction : group related elements into domain objects, reducing complexity.

Pattern : draw the architecture diagram using the four layers mentioned above.

4. Example: Coupon Business Architecture

4.1 Vision and Goals

The vision is to let users enjoy more discounts; the goal is to attract users and increase GMV.

4.2 Systematic Thinking for Coupons

Using reverse engineering, identify participants and processes:

User: holds coupons, uses them during order placement.

System: coupon creation, issuance, redemption, refund.

Issuance involves targeting, algorithmic recommendation, and marketing activities.

Redemption defines usage conditions (e.g., spend ¥100 get ¥10 off).

Refund decides whether the coupon is returned.

4.3 Business Process

The stable lifecycle consists of creation, issuance, usage, and refund.

4.4 Decomposition and Abstraction

Further break each process into sub‑steps and identify artifacts: coupon batch, coupon instance, usage detail, refund detail.

Abstract the artifacts: batch contains type and threshold; usage and refund details are unified as coupon detail; coupons are tightly linked to promotional activities.

4.5 Hierarchical Structure

The final diagram shows business flow (blue area) and product functions across the four layers, with “one core, two wings” – the core layers plus operational and data platforms.

5. Summary

This article defined business architecture, its characteristics, and methods, emphasizing the identification of business elements and their relationships, and demonstrated how to draw a business architecture diagram using a coupon‑service example. The next article will cover capability view and business monitoring.