Search Knowledge Base Articles

STANDARD SOP Software Development

📘 STANDARD SOP

Software Development Team

Company: SV Trucking Co., Ltd.
Department: Software Development
Version: 1.0
Owner: Software Development Manager (Sothea KHET)

🎯 1️⃣ PURPOSE

To ensure:

  • Clean code quality

  • Structured workflow

  • Clear responsibility

  • On-time delivery

  • Financial & operational alignment

  • Integration with Logistics, Finance, and HR systems

🏗 2️⃣ TEAM STRUCTURE & ROLES

👨🏻‍💼 Software Development Manager

  • Define architecture

  • Approve design

  • Review code

  • Approve production deployment

  • Coordinate with OPS / Finance / HR

👨🏻‍💻 Backend Developer (Spring Boot / .NET)

  • Design API

  • Create DTO

  • Implement business logic

  • Database migration

  • Unit testing

🎨 Frontend Developer (Angular / Web)

  • UI/UX implementation

  • API integration

  • Responsive design

  • Form validation

📱 Mobile Developer (Flutter – Driver App)

  • API integration

  • Offline support

  • GPS integration

  • Upload proof image/signature

🧪 QA / Tester

  • Test all flows end-to-end

  • Validate business logic

  • Verify finance lock rules

  • Prepare bug report

🔁 3️⃣ DEVELOPMENT LIFECYCLE (MANDATORY FLOW)

All features must follow this lifecycle:

1. Requirement
2. Analysis (SA)
3. Design
4. Development
5. Internal Testing
6. UAT
7. Production Release
8. Monitoring

No skipping steps.

📌 4️⃣ FEATURE IMPLEMENTATION SOP

Step 1 – Requirement Collection

  • Gather from OPS / Finance / HR

  • Clarify:

    • Who uses it?

    • What problem?

    • What output required?

    • Is it billable?

    • Does it affect finance?

Deliverable:
✔ Written Requirement Summary

Step 2 – System Analysis (SA)

Must include:

  • Workflow Diagram

  • Status Lifecycle

  • Approval Chain

  • Database Fields

  • Integration Points

Example:
Expense → Dispatch → Invoice → Payment

Deliverable:
✔ SA Document approved by Manager

Step 3 – Database Design Rules

  • Use ENUM for statuses

  • Use audit log table

  • Use foreign keys properly

  • Use created_at / updated_at

  • No hardcoded logic

Step 4 – Backend Rules

Must include:

  • DTO separation

  • Service layer logic

  • Repository layer clean

  • No business logic in Controller

  • Validation annotation

  • Exception handling

Status must be controlled like:

SUBMITTED → VERIFIED → APPROVED → INVOICED → PAID

No direct skipping allowed.

Step 5 – Frontend Rules

  • Form validation required

  • No empty critical fields

  • Display status badge

  • Display audit history

  • Use consistent UI color

Example:
Green = Approved
Red = Rejected
Yellow = Awaiting

Step 6 – Code Review SOP

Before merge:

✔ Code readable
✔ No duplicate logic
✔ API secured
✔ No exposed secret
✔ Role-based access validated

Manager must approve before production.

Step 7 – Testing SOP

Must test:

  • Happy flow

  • Invalid input

  • Role restriction

  • Financial lock

  • Duplicate prevention

  • Multi-user scenario

No production without QA sign-off.

🔐 5️⃣ SECURITY STANDARD

  • All APIs must require authentication

  • Role-based access control

  • Audit trail for:

    • Status change

    • Amount change

    • Approval

  • No direct database modification in production

📊 6️⃣ PROJECT MANAGEMENT STANDARD (Perfex Usage)

Every project must:

  • Have clear description

  • Have milestone

  • Have minimum 5 tasks (not 1)

  • Each task must have:

    • Assignee

    • Due date

    • Priority

    • Status

No vague task like:
❌ "Fix system"

Use:
✔ "Implement expense approval status lifecycle"

🚦 7️⃣ STATUS MANAGEMENT STANDARD

Allowed Task Status:

  • Not Started

  • In Progress

  • Testing

  • Awaiting Feedback

  • Complete

No skipping directly to Complete.

📦 8️⃣ RELEASE & DEPLOYMENT SOP

Before release:

✔ Backup database
✔ Tag version
✔ Confirm migration script
✔ Confirm rollback plan
✔ Notify OPS team

After release:

✔ Monitor logs
✔ Validate finance data
✔ Confirm no production error

📈 9️⃣ KPI FOR DEV TEAM

Track monthly:

KPI Target
On-time delivery 90%
Bug rate after release < 5%
Approval delay < 2 days
Rework rate < 10%
Code review compliance 100%

🧠 🔥 10️⃣ CULTURE RULES

  • No ego in code review

  • Respect architecture

  • Always think integration impact

  • Write scalable code

  • Document before implementing

  • Improve system, not patch system

🏆 11️⃣ LONG TERM STRATEGY

Your dev team must build systems that:

  • Integrate Dispatch + Finance

  • Integrate Driver App + TMS

  • Enable cost intelligence

  • Enable performance tracking

  • Reduce manual work

Because SV is not small trucking anymore.
It is becoming a logistics ecosystem.

Did you find this article useful?