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

العمارة على نطاق واسع

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

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

نظرة عامة

الموضوعات

  • العمارة التنظيمية
  • حدود المنصات
  • العمارة التطورية

تعلّم أولًا

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

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

  1. Describe an organization's architecture as platforms, product domains, and shared capabilities, and explain how each evolves.
  2. Draw platform boundaries that reduce coordination between product teams.
  3. Apply evolutionary architecture principles (incremental change, guided by fitness functions, last responsible moment).
  4. Identify where architecture and organization are misaligned.

الدروس

  1. 01من عمارة النظام إلى العمارة التنظيمية
  2. 02المنصات والمجالات والقدرات المشتركة
  3. 03رسم حدود المنصات
  4. 04العمارة التطورية
  5. 05قراءة عدم التوافق بين الفرق والأنظمة
  6. 06عرض عملي: رسم خريطة مشهد Commerce 2030
  7. 07عرض عملي: نقل قدرة واحدة من فرق المنتج إلى منصة

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

Lab

SRA-001-LAB1 · Landscape map

Outcomes: 1–4 · Time: ~2 h

  1. Gather the service catalog, team list, on-call rotas, and a quarter of change history for Commerce 2030 (use the case materials).
  2. Draw the map: systems grouped by product domain, owning teams, platforms, and shared capabilities; classify each shared item honestly.
  3. Overlay dependencies and cross-team change from the history.
  4. Mark the five worst coordination hot spots, each with evidence and a proposed boundary or ownership change.
  5. Review with role-played team leads and revise.

Acceptance: reviewed by role-played team leads who agree the hot spots are real.

Exercises (case-based; six exercises)

IDOutcomeTask
SRA-001-EX011Given a list of twelve Commerce 2030 components, classify each as product domain, shared capability, or platform and justify the three hardest calls.
SRA-001-EX022Three teams each integrate a carrier API. Decide whether to build a platform; write a one-page case with interface, owner, and service level.
SRA-001-EX032Redraw a boundary: a shared "common" library edited by eight teams. Propose where the boundary should go and how teams would cope during transition.
SRA-001-EX043For three marketplace decisions, decide now, at the last responsible moment, or keep open; name the trigger for each deferred one.
SRA-001-EX053Write two fitness functions (one for coupling, one for platform adoption) and state how each runs in CI or reporting.
SRA-001-EX064Given a pull-request heat map and team list, identify three misalignments and the smallest change that would reduce each.
أظهر الحلول
  • EX01 Examples: checkout and seller onboarding are domains; identity and notifications are platforms if run as products, otherwise shared capabilities; a shared utility library is shared coupling. Check each against "customer, self-service, roadmap, owner".
  • EX02 Yes if the need is stable and repeated: one carrier platform team, a versioned API, an SLO, a support channel, and a migration plan one team at a time. Record the risk of a bottleneck and how self-service reduces it.
  • EX03 Split the library: stable pieces move to an owned platform with versioning; domain-specific code returns to its domain. Transition: freeze new features, deprecate gradually, keep a compatibility layer.
  • EX04 Example: seller identity model decide now (hard to change, many dependents); payout provider decide at last responsible moment when volume and countries are known; search engine keep open behind an interface. Triggers: first seller contract signed, second-country launch, listing volume threshold.
  • EX05 Coupling: a build-time check that fails if a service imports another domain's internals (ArchUnit-style or dependency rules). Adoption: a weekly report of teams still calling the provider directly versus the platform API.
  • EX06 Typical: a service touched by many teams (split by capability), a team owning unrelated systems (rebalance ownership), a system with no owner (assign one). Smallest change first: owner or interface before reorganization.

Outcome 1 is also covered by the lab map and quiz; outcome 4 by the lab hot-spot review.

Workplace evidence: an architecture landscape you produced that leadership used for planning.

الاختبار

Outcomes: O1 platforms, domains, capabilities · O2 platform boundaries · O3 evolutionary architecture · O4 organization and architecture misalignment.

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

  1. 1A shared library used by ten teams with no owner or roadmap is best called:O1
  2. 2Which test best separates a platform from a shared capability?O1
  3. 3Seller onboarding with its own goals and metrics is a:O1
  4. 4When should a capability become a platform?O2
  5. 5A good boundary has:O2
  6. 6A fitness function is:O3
  7. 7"Last responsible moment" means:O3
  8. 8For a likely-to-change choice such as a payout provider, a good approach is to:O3
  9. 9The strongest evidence of team and system misalignment is:O4
  10. 10A system with no clear owner is:O4

الجزء العملي

Six case exercises SRA-001-EX01 to EX06 plus the lab, defended as a landscape map to role-played team leads. Pass: at least five of six exercises correct, quiz at least 8/10, and a landscape map whose five hot spots the reviewers accept as real.

أخطاء شائعة

Maps of systems without teams; "platform" for anything shared.

التقييم

Landscape map defense.

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

An architecture landscape you produced that leadership used for planning.

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

Platform strategy (STF-004) and business architecture (ARC-002).

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