Enterprise Architecture Requirement Management: Full Process & Core Mechanisms

Full Process of Enterprise Architecture Requirement Management

Stage 1: Requirement Collection

Requirements originate from business department pain points, market changes, or strategic mandates. For example, a sales department may report frequent customer complaints about order delivery delays, or finance may struggle with data integration during quarterly reconciliation. These inputs arrive via meetings, emails, ticketing systems, or periodic reports. The first step is to record and organize them, understand the background—why the requirement exists and which business processes are broken—and clarify details through repeated communication with the requester to avoid rework. A case in point: a request for a "new order management system" may actually stem from flawed supply-chain scheduling logic rather than a simple system replacement.

Stage 2: Requirement Planning

Collected requirements must be planned and categorized from a global perspective:

Categorization : urgent (e.g., production incident fixes), efficiency-improvement (e.g., process automation), and strategic-support (e.g., new business enablement).

Priority Assessment : using ROI or similar standards to calculate value output. If a requirement saves 30% of monthly labor costs for a business unit, its priority is high.

Diversion Channels : different categories follow different paths. Type A and B enter regular workflows; Type C (complex) undergoes special assessment; Type D (innovative) may require a pilot.

Huawei's practice illustrates this: a "lighthouse requirement" mechanism selects several globally significant requirements each quarter for dedicated resource allocation.

Stage 3: Requirement Analysis and Design

This stage transforms requirements into executable solutions:

Process owners organize deep analysis—current-state research, data collection—to pinpoint root causes. Example: customer complaints about order delays may actually be caused by opaque inventory management, not sales inefficiency.

Solution design weighs importance and technical feasibility, often comparing multiple options (e.g., modifying existing systems vs. introducing a new ERP).

Business and IT teams co-create design deliverables: business process designs, system architecture plans.

A common pitfall is "kicking the ball" between business and IT—business thinks IT doesn't understand the domain, IT thinks requirements are unclear. Effective cross-department communication and clear responsibility assignment are critical.

Stage 4: Requirement Review and Confirmation

Completed designs enter a three-track review:

Business Review : does the solution truly meet actual business needs and solve the root problem?

Technical Review : IT assesses feasibility, development cycle, and technical risks.

Budget Review : management decides on resource commitment.

Approved requirements are formally initiated; rejected ones are returned for revision or shelved.

Stage 5: Requirement Implementation and Delivery

Requirements move from blueprint to reality:

Product Design & Development : IT builds while maintaining continuous communication with business to prevent divergence.

Version Testing : rigorous functional, stress, and other tests ensure operability.

Phased Rollout : complex needs may use staged deployment—pilot in one department, verify, then expand company-wide.

Southern Power Grid's digital transformation exemplifies this: development teams held regular check-ins with business during trial runs to optimize in real time.

Stage 6: Requirement Acceptance and Closure

Post-launch, business verifies:

Functional compliance with requirements.

Performance against expectations.

Usability and user feedback.

Failed acceptance triggers a return to implementation for fixes; passed acceptance leads to formal closure and archiving of background, solution, and outcomes for future reference.

Core Mechanisms of Enterprise Architecture Requirement Management

1. Closed-loop Mechanism

From proposal to final acceptance, a complete loop ensures every stage has a clear owner and defined process.

2. Dynamic Adjustment Mechanism

Priorities and strategies adapt to changing conditions. During the COVID-19 pandemic, many enterprises urgently escalated remote-work requirements, dramatically raising their priority.

3. Value-driven Mechanism

The core goal is business value creation. Every stage evaluates whether a requirement genuinely delivers benefits, avoiding waste on "seemingly important but actually ineffective" demands.