Dasturiy ta’minot hayotiy sikli va tendensiyalar
OmborPro himoyadan keyin 5 yil ishlasa, eng ko‘p vaqt va pul qaysi bosqichga ketadi?
Ishlab chiqishgami yoki undan keyingi hayotigami? Taxmin qiling va asoslang.
Bu ma’ruza oxirida siz quyidagilarni bajara olasiz...
Hayotiy sikl va texnik xizmat
Hayotiy sikl — himoyadan keyin ham davom etadi
Ishlab chiqish
Qo‘llab-quvvatlash
TCO
Ishdan chiqarish
SDLC bosqichlari va OmborPro dagi natijalar
| Bosqich | Asosiy natija | OmborPro da (mavzu) |
|---|---|---|
| Talablar | User stories, backlog | Loyiha xartiyasi (1) |
| Loyihalash | Arxitektura, ER-sxema, ADR | Qatlamlar, modellar (2–3) |
| Ishlab chiqish | Kod, PR, code review | Servislar, UI, API (4–11) |
| Testlash | Pest testlari, qamrov | Testlash (12) |
| Joriy etish | Docker, CI/CD, VPS | DevOps (14) |
| Qo‘llab-quvvatlash | SLA, monitoring, relizlar | Kuzatuvchanlik (13), bugun (15) |
| Ishdan chiqarish | Ma’lumot ko‘chirish, arxiv | Yangi tizimga migratsiya |
Texnik xizmatning to‘rt turi
Har bir o‘zgarish so‘rovi shu to‘rt turdan biriga kiradi — bu rejalashtirish va byudjet uchun asos.
1Tuzatuvchi (corrective)
2Moslashtiruvchi (adaptive)
3Takomillashtiruvchi (perfective)
4Oldini oluvchi (preventive)
1-bo‘lim yakuni: Hayotiy sikl va texnik xizmat
Hujjatlashtirish
Kim uchun, nima va qayerda
| Hujjat | Kim uchun | Tarkibi | Qayerda |
|---|---|---|---|
| README | Dasturchi | Maqsad, ishga tushirish, testlar, .env | README.md |
| ADR | Jamoa, kelajakdagi dasturchi | Kontekst, qaror, oqibatlar | docs/adr/ |
| OpenAPI | Integratorlar (1C, mobil) | Endpointlar, sxemalar, xatolar | Scribe → /docs |
| Qo‘llanma | Admin, menejer, omborchi, buxgalter | Jarayonlar, skrinshotlar | docs/user-guide/ |
| CHANGELOG | Hamma | Versiyalar va o‘zgarishlar | CHANGELOG.md |
| Runbook | Navbatchi dasturchi | Hodisalarda tayyor buyruqlar | docs/runbook.md |
Arxitektura qarori yozuvi (Nygard formati)
# ADR-0004: Modulli monolit arxitekturasi Holat: Qabul qilingan (2026-11-20) ## Kontekst Jamoa 4 kishi, bitta PostgreSQL, 15 haftalik muddat. Rezerv va hisob-faktura bitta tranzaksiyada bo'lishi shart. ## Qaror Bitta Laravel ilovasi; Sales, Inventory, Billing modullari bir-biriga faqat servis interfeyslari orqali murojaat qiladi. ## Oqibatlar + bitta deploy, ACID tranzaksiyalar, oddiy CI - modul chegaralarini code review da nazorat qilish kerak - Billing ni ajratish kerak bo'lsa — yangi ADR yoziladi
docs/adr/0004-modulli-monolit.md — PR orqali qabul qilinadi Keyin o‘zgarmaydi; yangi qaror → ADR-0007 (supersedes 0004)
0004 — ketma-ket, qayta ishlatilmaydiScribe: hujjat koddan generatsiya qilinadi
/** * Mahsulotlar ro'yxati * * Faol mahsulotlarni sahifalab qaytaradi. * * @group Mahsulotlar * @authenticated * @queryParam category_id integer Kategoriya filtri. Example: 3 * @queryParam per_page integer Sahifa hajmi. Example: 20 */ public function index(Request $request): AnonymousResourceCollection { $products = Product::query() ->where('is_active', true) ->paginate($request->integer('per_page', 20)); return ProductResource::collection($products); }
$ php artisan scribe:generate → HTML hujjat (type = laravel bo‘lsa: /docs) → OpenAPI spetsifikatsiyasi + Postman kolleksiyasi
Example: qiymatirules() dan avtomatik olinadi2-bo‘lim yakuni: Hujjatlashtirish
Qo‘llab-quvvatlash va texnik qarz
P1–P4: javob va tiklash muddatlari (namuna)
| Daraja | Mezon | Javob | Tiklash |
|---|---|---|---|
| P1 — kritik | Tizim ishlamaydi yoki to‘lovlar to‘xtagan | 15 daqiqa | 4 soat |
| P2 — yuqori | Muhim funksiya ko‘pchilik (≥ 50) uchun ishlamaydi | 1 soat | 24 soat |
| P3 — o‘rta | Kichik guruhga ta’sir, aylanma yo‘l bor | 4 soat | 72 soat |
| P4 — past | Kosmetik xato, taklif | 1 ish kuni | Keyingi reliz |
Ustuvorlik va tiklash muddatini hisoblash
function priority(bool $down, bool $money, int $users): string { return match (true) { $down || $money => 'P1', $users >= 50 => 'P2', $users >= 5 => 'P3', default => 'P4', }; } $hours = ['P1' => 4, 'P2' => 24, 'P3' => 72, 'P4' => 240]; $tz = new DateTimeZone('Asia/Tashkent'); $opened = new DateTimeImmutable('2026-12-14 09:30', $tz); $cases = [[false, true, 3], [false, false, 60], [false, false, 1]]; foreach ($cases as $c) { $p = priority(...$c); $due = $opened->modify("+{$hours[$p]} hours"); echo $p, ' -> ', $due->format('d.m.Y H:i'), PHP_EOL; }
P1 -> 14.12.2026 13:30 P2 -> 15.12.2026 09:30 P4 -> 24.12.2026 09:30
DateTimeImmutable yangi obyekt qaytaradi, asl sana o‘zgarmaydiSignaldan postmortemgacha
Aniqlash
/up monitoringi yoki foydalanuvchi murojaatiTriage
Yumshatish
Tuzatish
1.4.3)Postmortem
Paketlarni muntazam tekshirish va yangilash
# 1. Eskirgan to'g'ridan-to'g'ri bog'liqliklar composer outdated --direct # 2. Ma'lum zaifliklar (CI da ham ishga tushiring) composer audit # 3. Minor/patch yangilash - composer.json chegarasida composer update sentry/sentry-laravel --with-dependencies # 4. Major yangilash - alohida branch, ADR va to'liq testlar git switch -c upgrade/laravel-12 composer require laravel/framework:^12.0 -W php artisan test
$ composer audit No security vulnerability advisories found.
composer.json dagi paketlar, ichki bog‘liqliklarsiz--with-all-dependencies: bog‘liq paketlarni ham yangilashga ruxsat3-bo‘lim yakuni: Qo‘llab-quvvatlash va texnik qarz
composer outdated va composer audit nimasi bilan farq qiladi?1-topshiriq: Hodisa ustuvorligi va SLA muddati
Qo‘llab-quvvatlash xizmatiga murojaat keldi: ['down' => bool, 'payments' => bool, 'users' => int, 'opened' => 'Y-m-d H:i']. Ustuvorlikni aniqlang: tizim ishlamasa (down) yoki to‘lovlar to‘xtagan bo‘lsa (payments) — P1; aks holda users ≥ 50 — P2; users ≥ 5 — P3; qolganlari — P4. Tiklash muddati: P1 — 4 soat, P2 — 24 soat, P3 — 72 soat, P4 — 240 soat (kalendar soatlari). users manfiy bo‘lsa yoki sana formati noto‘g‘ri bo‘lsa — InvalidArgumentException.
Imzo: function incident_sla(array $i): array
Qaytaradi: ['priority' => 'P1'|'P2'|'P3'|'P4', 'due' => 'Y-m-d H:i'] — kalitlar aynan shu tartibda.
incident_sla(['down' => true, 'payments' => false, 'users' => 0, 'opened' => '2026-12-14 09:30'])
{"priority":"P1","due":"2026-12-14 13:30"}O‘zgarishlarni boshqarish
MAJOR.MINOR.PATCH — versiya bu va’da
MAJOR (2.0.0)
MINOR (1.5.0)
PATCH (1.4.3)
Pre-release / build
1.0.0-rc.1 < 1.0.0; +build.7 tartibga ta’sir qilmaydi.0.y.z — boshlang‘ich bosqich: istalgan o‘zgarish bo‘lishi mumkin. Himoya relizi — v1.0.0.Keyingi versiya va version_compare
function bump(string $v, string $change): string { [$major, $minor, $patch] = array_map('intval', explode('.', $v)); return match ($change) { 'breaking' => ($major + 1) . '.0.0', 'feature' => "$major." . ($minor + 1) . '.0', 'fix' => "$major.$minor." . ($patch + 1), }; } echo bump('1.4.2', 'fix'), PHP_EOL; echo bump('1.4.2', 'feature'), PHP_EOL; echo bump('1.4.2', 'breaking'), PHP_EOL; $list = ['1.10.0', '1.2.0', '1.0.0-rc.1', '1.0.0']; usort($list, 'version_compare'); echo implode(' < ', $list), PHP_EOL;
1.4.3 1.5.0 2.0.0 1.0.0-rc.1 < 1.0.0 < 1.2.0 < 1.10.0
2.0.0, 2.1.0 emas1.10.0 > 1.2.0version_compare semver bilan to‘liq mos emas: 1.0.0-alpha.beta ni 1.0.0-alpha.1 dan kichik deb hisoblaydi'1.10.0' > '1.9.0' satr sifatida false — xato manbaiCHANGELOG.md toifalari
| Toifa | Nima yoziladi | OmborPro misoli |
|---|---|---|
| Added | Yangi imkoniyat | Debitorlik hisobotini Excel ga eksport |
| Changed | Mavjud xatti-harakat o‘zgardi | Buyurtma raqami formati BY-2027-... |
| Deprecated | Tez orada olib tashlanadi | /api/v1/stocks — v2 ga o‘ting |
| Removed | Olib tashlandi | Eski PDF shabloni |
| Fixed | Xato tuzatildi | Chegirmada QQS yaxlitlash |
| Security | Zaiflik yopildi | Eksportda ruxsat tekshiruvi qo‘shildi |
## [Unreleased]; relizda u ## [1.1.0] - 2026-12-21 ga aylanadi va yangi bo‘sh [Unreleased] ochiladi.Feature flag: deploy va release ni ajratish
// app/Providers/AppServiceProvider.php - boot() Feature::define('invoice-pdf-v2', function (User $user) { return match (true) { $user->hasRole('admin') => true, $user->hasRole('buxgalter') => Lottery::odds(1, 10), default => false, }; }); // Controller da - joriy (autentifikatsiyadan o'tgan) foydalanuvchi if (Feature::active('invoice-pdf-v2')) { return $this->pdfV2->render($invoice); } // Navbatdagi job da - foydalanuvchi aniq ko'rsatiladi $on = Feature::for($invoice->order->creator)->active('invoice-pdf-v2');
admin → true (har doim)
buxgalter → ~10 % hollarda true; natija features jadvalida saqlanadi
menejer → false
O‘chirish: Feature::deactivateForEveryone('invoice-pdf-v2')User)@feature('invoice-pdf-v2') ... @endfeatureQo‘llangan migratsiyani o‘zgartirish kerak bo‘lsa
Noto‘g‘ri: eski faylni tahrirlash
create_invoices_tablegacurrencyustuni qo‘shib, faylni qayta saqlash- Production da u allaqachon bajarilgan —
migrateuni qayta ishga tushirmaydi - Lokal, test va production sxemalari ajralib ketadi
migrate:freshbilan “tuzatish” — barcha ma’lumot yo‘qoladi
To‘g‘ri: yangi migratsiya
php artisan make:migration add_currency_to_invoices_table- Avval nullable yoki default qiymatli ustun (expand)
- Ma’lumotni ko‘chirish, kodni yangi ustunga o‘tkazish (migrate)
- Eski ustunni keyingi relizda olib tashlash (contract)
4-bo‘lim yakuni: O‘zgarishlarni boshqarish
2.3.1 versiyasida orqaga mos bo‘lmagan o‘zgarish qilindi. Keyingi versiya qanday?Feature::active() nima uchun kutilgan natija bermasligi mumkin?2-topshiriq: Conventional Commits bo‘yicha keyingi versiya
Joriy versiya MAJOR.MINOR.PATCH (faqat raqamlar, masalan 1.4.2) va oxirgi relizdan keyingi commit xabarlari ro‘yxati berilgan. Sarlavha formati: tur(soha)!: tavsif — (soha) va ! ixtiyoriy. Qoidalar: ! bor yoki xabarda BREAKING CHANGE: uchrasa — MAJOR; feat — MINOR; fix yoki perf — PATCH; boshqa turlar (docs, chore, refactor...) va formatga mos kelmaydigan xabarlar versiyani o‘zgartirmaydi. Eng katta o‘zgarish hal qiladi. Versiya formati noto‘g‘ri bo‘lsa — InvalidArgumentException.
Imzo: function next_version(string $current, array $commits): string
Qaytaradi: Keyingi versiya satri, masalan '1.5.0'; hech qanday ta’sirli commit bo‘lmasa — joriy versiyaning o‘zi.
next_version('1.4.2', ['fix: QQS yaxlitlash', 'docs: README'])"1.4.3"
Tendensiyalar: mikroservislar, low-code, AI yordamchilar
Modulli monolit va mikroservislar
Modulli monolit
- Bitta deploy, bitta CI, bitta monitoring
- ACID tranzaksiya: rezerv + hisob-faktura birga
- Modul chegaralari — interfeyslar va code review
- Kichik jamoa (3–10 kishi) uchun mos
- Kamchilik: butun ilova birga masshtablanadi
Mikroservislar
- Mustaqil deploy va masshtablash
- Har bir servisning o‘z bazasi va jamoasi
- Saga, retry, eventual consistency kerak
- Tarmoq, kuzatuvchanlik va versiyalash narxi yuqori
- Ko‘p jamoali yirik tashkilotlar uchun mos
Sales moduli Inventory ga faqat interfeys orqali murojaat qiladi
// Inventory modulining "eshigi" interface StockReservation { /** @param array<int, int> $items product_id => miqdor */ public function reserve(int $warehouseId, array $items): void; public function release(int $orderId): void; } // StockService implements StockReservation - stocks jadvali // faqat Inventory ichida o'qiladi va yoziladi final class OrderService { public function __construct( private StockReservation $stock, ) {} }
Sales → StockReservation::reserve() ✓
Sales → DB::table('stocks')->update() ✗ (code review da rad etiladi)StockService ni bog‘laydi (bind)Low-code qayerda o‘rinli, qayerda xavfli
1O‘rinli
2Admin panellar
3Vendor lock-in
4Murakkab qoidalar
5Soya IT
Tashqi AI servisiga yuborishdan oldin niqoblash
function maskForAi(string $text): string { $rules = [ '/\b\d{9}\b/' => '[STIR]', '/\+998(?:[\s-]?\d){9}/' => '[TELEFON]', '/[\w.+-]+@[\w-]+\.[\w.]+/' => '[EMAIL]', '/\b\d{4}(?:\s?\d{4}){3}\b/' => '[KARTA]', ]; return preg_replace(array_keys($rules), $rules, $text); } $msg = 'Mijoz STIR 301234567, tel +998 90 123-45-67, ' . 'e-mail ali@example.uz, karta 8600 1234 5678 9012.'; echo maskForAi($msg), PHP_EOL;
Mijoz STIR [STIR], tel [TELEFON], e-mail [EMAIL], karta [KARTA].
audit_logs ga yoziladi5-bo‘lim yakuni: Tendensiyalar: mikroservislar, low-code, AI yordamchilar
3-topshiriq: AI servisiga yuborishdan oldin niqoblash
Matnni tashqi AI servisiga yuborishdan oldin shaxsga doir ma’lumotlar niqoblanadi. Qoidalar shu tartibda qo‘llanadi: (1) e-mail (belgilar@domen.zona) → [EMAIL]; (2) +998 va undan keyin 9 ta raqam (raqamlar orasida bitta bo‘sh joy yoki - bo‘lishi mumkin) → [TELEFON]; (3) aynan 9 xonali alohida son (oldi va ketida raqam yo‘q) — STIR → [STIR]. Jami almashtirishlar sonini ham qaytaring.
Imzo: function mask_pii(string $text): array
Qaytaradi: ['text' => string, 'count' => int] — niqoblangan matn va almashtirishlar soni.
mask_pii('STIR 301234567, tel +998 90 123-45-67'){"text":"STIR [STIR], tel [TELEFON]","count":2}Loyiha himoyasiga tayyorgarlik
Himoyagacha reja
Code freeze (−10 kun)
fix: PR lar; yangi imkoniyatlar v1.1 backlog igaHujjatlar (−7 kun)
Reliz (−5 kun)
[1.0.0], v1.0.0 teg, GitHub Release, production deployMashq (−3 kun)
Zaxira (−1 kun)
v1.0.0: tekshirish, teg va GitHub Release
git switch main && git pull --ff-only composer audit ./vendor/bin/pint --test ./vendor/bin/phpstan analyse php artisan test # CHANGELOG: [Unreleased] -> [1.0.0] - 2026-12-21 git commit -am "chore(release): 1.0.0" git tag -a v1.0.0 -m "OmborPro 1.0.0" git push origin main --follow-tags gh release create v1.0.0 --title "OmborPro 1.0.0" \ --notes-file docs/release-1.0.0.md
To github.com:jamoa/omborpro.git * [new tag] v1.0.0 -> v1.0.0 https://github.com/jamoa/omborpro/releases/tag/v1.0.0
Komissiya ko‘p beradigan savollar
1Arxitektura
2Ma’lumotlar
3Sifat
4Xavfsizlik
5Ekspluatatsiya
6Jamoa
OrderService::confirm, 42-qator, OrderFlowTest”.6-bo‘lim yakuni: Loyiha himoyasiga tayyorgarlik
Asosiy xulosalar
1Qo‘llab-quvvatlash — eng uzun bosqich
2Hujjat — kod bilan birga
3SLA va hodisalar jarayoni
4Versiya — bu va’da
5Deploy ≠ release
6Tendensiyalarga ehtiyotkorlik bilan
Yakunlashdan oldin sakkizta savol
2.3.1 da orqaga mos bo‘lmagan o‘zgarish — keyingi versiya?15-amaliy mashg‘ulot: 5 ta PHP topshiriq va loyiha bosqichi
Reliz cheklistini tekshirish
Feature flag: kimga yoqilgan?
ADR holatlari mashinasi
CHANGELOG: [Unreleased] bo‘limini tahlil qilish
SemVer bo‘yicha tartiblash (pre-release bilan)
Darsni tark etishdan oldin
Javoblaringizni yozing (✎ Javob yozish) yoki qog‘ozga yozib topshiring.
1.2.0 dan keyin bitta feat: va ikkita fix: commit bo‘lsa, keyingi versiya qanday bo‘ladi?