انتقل إلى المحتوى
أمين أبوزيد
ARC-032

التكامل مع أنظمة المؤسسة

  • 6 درس
  • 4 ساعة تدريب (تقدير)
في هذه الصفحة 9 موضوعات

نص الدروس والتمارين باللغة الإنجليزية، بينما تبقى واجهة الموقع وعناوين الدروس بالعربية.

نظرة عامة

الموضوعات

  • ERP
  • CRM
  • بوابات الدفع
  • مزودو الهوية

تعلّم أولًا

4 ساعة تدريب (تقدير)

مخرجات التعلم

  1. Integrate with an ERP (products, prices, stock, financial postings) respecting it as the system of record.
  2. Integrate with a CRM for customer profiles, service cases, and marketing consent.
  3. Integrate payment gateways and identity providers with correct failure handling and reconciliation.
  4. Use anti-corruption layers to keep enterprise-system models out of the new platform's domain.

الدروس

  1. 01العمل مع أنظمة السجلات الرسمية
  2. 02التكامل مع ERP
  3. 03التكامل مع CRM
  4. 04بوابات الدفع ومزودو الهوية
  5. 05عرض عملي: طبقة مضادة للإفساد (Anti-corruption Layer) بين المنصة وERP
  6. 06عرض عملي: مطابقة المدفوعات بين البوابة والمنصة وERP

المختبر والتمارين

Lab

ARC-032-LAB1 · Larkspur enterprise integration

Outcomes: 1–4 · Time: ~4 h

  1. Define the system of record for each shared data set (products, prices, stock, orders, customers, consent, payments, identities).
  2. Design the ERP integration (products, prices, stock, financial postings) with rate limiting and queueing.
  3. Design the CRM integration (profiles, service cases, consent) and the identity-provider integration.
  4. Design the payment gateway integration with idempotency, timeout handling, and reconciliation.
  5. Define the anti-corruption layer for the ERP.
  6. For every flow write what happens when the other side is down.

Acceptance: every flow defines the system of record and what happens when the other side is down.

Exercises (case-based; six exercises)

IDOutcomeTask
ARC-032-EX011Product prices live in the ERP but marketing wants to change web prices daily. Decide the system of record and flow.
ARC-032-EX021The platform shows availability; the ERP holds the stock book. Design the stock flow and the behavior when the ERP is down.
ARC-032-EX032A customer withdraws marketing consent in the app. Design propagation to the CRM, email tool, and analytics, and how you prove it.
ARC-032-EX043A payment authorization times out. Write the handling rules, including the webhook and a reconciliation step.
ARC-032-EX053The identity provider is unavailable for 20 minutes. Decide what customers and staff can still do.
ARC-032-EX064The ERP names customer orders "SO documents" with status codes 10, 20, 30. Design the anti-corruption layer and list what must not appear in the platform's API.
أظهر الحلول
  • EX01 The ERP stays the record for base price; a pricing service on the platform holds approved web price overrides with effective dates; changes governed by the price owner; overrides posted to the ERP for finance. Alternatively move web promo pricing ownership to a pricing system and sync to the ERP. Decision recorded with owner.
  • EX02 Events or CDC from the ERP into an availability store; reservations on the platform; periodic reconciliation. ERP down: sell from last-known availability with safety buffer; queue reservations; reconcile on recovery.
  • EX03 Preference center is master; publish a consent-withdrawn event; consumers acknowledge; sync check daily; audit entry with timestamps; target time agreed with legal; failures alert an owner.
  • EX04 Treat the result as unknown; use an idempotency key; do not retry blindly or tell the customer failed; query the provider; process verified webhook; mark order pending; reconcile nightly.
  • EX05 Existing sessions continue within validity; token verification with cached keys; new logins blocked or fall back to a limited path; staff via a separate break-glass process; message the customers; alert and escalate to the provider.
  • EX06 An adapter translating SO documents to Order, mapping codes to named statuses in a dictionary, translating errors; the platform API must not expose ERP codes, document numbers as keys, or field names; contract tests guard it.

Workplace evidence: an ERP, CRM, or payment integration you designed and its operational results.

الاختبار

Outcomes: O1 ERP and systems of record · O2 CRM integration · O3 payments and identity providers · O4 anti-corruption layers.

اختبار ذاتي لك: لا توجد درجات، ولا يُحفظ أو يُرسل أي شيء. اختر إجابة ثم تحقق منها، ويمكنك المحاولة مرة أخرى كما تشاء.

  1. 1A system of record is:O1
  2. 2To write an order posting into the ERP you should:O1
  3. 3Queueing postings to the ERP mainly:O1
  4. 4In CRM integration the urgent direction for consent changes is:O2
  5. 5For a single service-agent view you should:O2
  6. 6A payment call times out. The state is:O3
  7. 7Payment reconciliation compares:O3
  8. 8If the identity provider is down, the design should:O3
  9. 9The main purpose of an anti-corruption layer is to:O4
  10. 10An ERP upgrade changes field names. With a good ACL:O4

الجزء العملي

Integration design defense of the lab design plus exercises ARC-032-EX01 to EX06. Pass: quiz at least 8/10, at least five of six exercises correct, and a lab where every flow names the system of record and the behavior when the other side is down.

أخطاء شائعة

Letting ERP data models leak into the platform; no reconciliation for money flows.

التقييم

Integration design defense.

دليل من بيئة العمل

An ERP, CRM, or payment integration you designed and its operational results.

الصلة بالمسار الوظيفي

Enterprise-system integration is the core of most solution architect roles.

اكتب للبحث في المستويات والمراحل والوحدات والدروس.