Software Development

 

https://notebooklm.google.com/notebook/aa90cb8a-990f-46a7-aa65-fdf54cf21e0c?artifactId=eac3296b-2923-4ed2-84c5-172a3f551baf

https://chatgpt.com/c/69911a01-4cb8-8324-a4e0-93730503d826

PROSES PENGEMBANGAN PERANGKAT LUNAK (END-TO-END SDLC)

Pengembangan perangkat lunak bukan sekadar coding, tetapi proses rekayasa sistem yang terstruktur dan terdokumentasi.

Secara umum mengikuti tahapan:

Problem Identification
↓
Requirement Engineering
↓
SRS
↓
System Analysis
↓
Architecture Design
↓
Database Design
↓
Backend & Frontend Design
↓
Integration
↓
Testing & Deployment

---

1️⃣ IDENTIFIKASI MASALAH

🎯 Tujuan

Memahami masalah bisnis sebelum menulis satu baris kode pun.

🔍 Aktivitas

• Observasi proses bisnis

• Interview stakeholder

• Identifikasi pain point

• Analisis gap sistem lama

📌 Output

• Problem statement

• Business objective

• High-level solution

⚠️ Prinsip Penting

Jangan langsung menawarkan solusi teknis sebelum memahami masalah bisnis.

---

2️⃣ REQUIREMENT GATHERING

Tahapan mengumpulkan kebutuhan sistem dari stakeholder.

🎭 Stakeholder

• User

• Owner

• Admin

• IT team

• Regulator

🛠 Metode

• Interview

• Workshop

• Kuesioner

• Prototyping

• Observasi lapangan

📌 Output

• Daftar kebutuhan sistem

• Prioritas kebutuhan

• Dokumen requirement awal

---

3️⃣ SRS (Software Requirements Specification)

SRS adalah dokumen formal yang menjelaskan apa yang harus dilakukan sistem, bukan bagaimana caranya.

---

📑 Struktur Umum SRS

1. Pendahuluan

• Tujuan dokumen

• Ruang lingkup sistem

• Definisi istilah

2. Deskripsi Umum

• Perspektif produk

• Karakteristik pengguna

• Batasan sistem

3. Functional Requirements

Contoh:

ID	Requirement
FR1	Sistem harus memungkinkan user login
FR2	Sistem harus menyimpan transaksi

---

4. Non-Functional Requirements

Kategori	Contoh
Performance	Response < 2 detik
Security	Enkripsi password
Availability	99% uptime
Scalability	10.000 user concurrent

---

5. Use Case Specification

Menjelaskan interaksi user dengan sistem.

---

📌 Output

Dokumen SRS lengkap (baseline kontrak antara client dan developer).

---

4️⃣ ANALISIS SISTEM

Tahapan menguraikan requirement menjadi model sistem.

🎭 Identifikasi Aktor

• Primary actor

• Secondary actor

🔄 Use Case Analysis

Menentukan:

• Main success scenario

• Alternate flow

• Exception flow

---

📊 Activity Diagram (Deskriptif)

User Login
↓
Validasi
↓
Akses Dashboard

---

⚠️ Constraint Analysis

• Budget

• Timeline

• Infrastruktur

• Regulasi

---

5️⃣ PERANCANGAN ARSITEKTUR SISTEM

Menentukan struktur teknis sistem.

---

📌 Pilihan Arsitektur

Arsitektur	Kapan digunakan
Monolith	Sistem kecil-menengah
MVC	Web application
Microservices	Enterprise & scalable
Clean Architecture	Maintainability tinggi

---

🏗 Client-Server Model

Client (Browser)
    ↓
Application Server
    ↓
Database Server

---

🌐 REST Architecture

Karakteristik:

• Stateless

• JSON-based

• HTTP method (GET, POST, PUT, DELETE)

---

☁ Deployment Model

• On-premise

• Cloud (AWS/GCP/Azure)

• Containerized (Docker)

• CI/CD pipeline

---

6️⃣ DESAIN DATABASE

Database design bertujuan memastikan:

• Konsistensi data

• Integritas relasi

• Efisiensi query

---

📊 ERD (Konsep)

User (1) ────< Order (1) ────< OrderDetail >──── (1) Product

---

📌 Normalisasi

1NF → Data atomic
2NF → No partial dependency
3NF → No transitive dependency

---

📌 Contoh Struktur Tabel

Users

• id (PK)

• name

• email (unique)

• password_hash

• role

---

7️⃣ DESAIN BACKEND

Backend bertanggung jawab pada:

• Business logic

• Validasi

• Data processing

• Security

---

📌 Pilihan Teknologi

• Node.js + Express

• Java Spring Boot

• PHP Laravel

• Python Django

---

📂 Struktur MVC

/controllers
/models
/routes
/middlewares
/config

---

📌 Contoh Endpoint

GET    /api/products
POST   /api/login
POST   /api/orders

---

🔐 Security Layer

• JWT authentication

• Password hashing (bcrypt)

• Role-based access control

• Input sanitization

---

8️⃣ DESAIN FRONTEND

Frontend bertanggung jawab pada:

• UI/UX

• Interaksi user

• Integrasi API

---

🎨 UI/UX Principle

• Simplicity

• Consistency

• Accessibility

• Responsive design

---

📌 Arsitektur Frontend

• Multi-page application

• SPA (Single Page Application)

Modern enterprise → SPA (React/Vue/Angular)

---

📦 Komponen

• Navbar

• Form

• Table

• Modal

• Dashboard

---

🔄 Integrasi API

fetch('/api/products')
.then(res => res.json())
.then(data => render(data));

---

9️⃣ INTEGRASI SISTEM

Menjamin komunikasi antar layer berjalan baik.

---

🔁 Alur Request-Response

Frontend → HTTP Request → Backend
Backend → Query DB → Response JSON
Frontend → Render UI

---

📦 Struktur JSON Standar

{
  "status": "success",
  "data": {},
  "message": ""
}

---

🔟 TESTING STRATEGY

Testing dilakukan berlapis.

---

🧪 1. Unit Testing

Mengujicoba fungsi secara individual.

Contoh:

• Validasi login

• Perhitungan total transaksi

---

🔗 2. Integration Testing

Mengujicoba antar modul:

• API ↔ Database

• Frontend ↔ Backend

---

👥 3. System Testing

Menguji sistem secara keseluruhan.

---

✔ 4. User Acceptance Testing (UAT)

Checklist berbasis requirement di SRS.