112 lines
2.1 KiB
Markdown
112 lines
2.1 KiB
Markdown
# Report Outline (BAB 1–4)
|
||
|
||
## BAB 1 - Pendahuluan
|
||
|
||
### 1.1 Latar Belakang
|
||
|
||
- Importance of structured server documentation and monitoring
|
||
- Need for a simple admin dashboard for managing private servers and hosted services
|
||
|
||
### 1.2 Rumusan Masalah
|
||
|
||
- How to manage server data, services, domains, and internal notes in one web app?
|
||
- How to check whether a domain resolves to the expected server IP automatically?
|
||
|
||
### 1.3 Batasan Masalah
|
||
|
||
- CRUD + monitoring dashboard only
|
||
- No SSH, no Docker orchestration, no real deployment automation
|
||
- DNS checking limited to A record / IPv4
|
||
- Single admin login
|
||
|
||
### 1.4 Tujuan
|
||
|
||
- Build a web-based dashboard for private server service management
|
||
- Provide simple DNS verification and summary monitoring
|
||
|
||
### 1.5 Manfaat
|
||
|
||
- Helps admins manage server and service records
|
||
- Helps students understand CRUD, relationships, and monitoring concepts
|
||
|
||
## BAB 2 - Tinjauan Pustaka
|
||
|
||
### 2.1 Web-Based Information Systems
|
||
|
||
### 2.2 CRUD Concept
|
||
|
||
### 2.3 Monitoring Dashboard Concept
|
||
|
||
### 2.4 DNS and A Record Resolution
|
||
|
||
### 2.5 Technologies Used
|
||
|
||
- React
|
||
- TanStack Router
|
||
- tRPC
|
||
- PostgreSQL
|
||
- Drizzle ORM
|
||
- better-auth
|
||
- Effect
|
||
|
||
## BAB 3 - Analisis dan Perancangan Sistem
|
||
|
||
### 3.1 Analisis Kebutuhan
|
||
|
||
- Functional requirements
|
||
- Non-functional requirements
|
||
|
||
### 3.2 Perancangan Sistem
|
||
|
||
- Use case diagram
|
||
- Class diagram
|
||
- Activity diagram
|
||
- State chart
|
||
- Sequence diagram
|
||
- Collaboration diagram
|
||
|
||
### 3.3 Perancangan Database
|
||
|
||
- Server table
|
||
- Service table
|
||
- Domain table
|
||
- Note table
|
||
- Auth tables
|
||
|
||
### 3.4 Perancangan Antarmuka
|
||
|
||
- Login page
|
||
- Dashboard page
|
||
- Server list/detail/form
|
||
- Service list/detail/form
|
||
- Domain list/detail/form
|
||
- Note list/detail/form
|
||
|
||
## BAB 4 - Implementasi dan Pengujian
|
||
|
||
### 4.1 Implementasi Sistem
|
||
|
||
- Backend implementation
|
||
- Frontend implementation
|
||
- Authentication implementation
|
||
- DNS check implementation
|
||
|
||
### 4.2 Pengujian
|
||
|
||
- Login test
|
||
- CRUD server test
|
||
- CRUD service test
|
||
- CRUD domain test
|
||
- CRUD note test
|
||
- DNS check test
|
||
- Dashboard summary test
|
||
|
||
### 4.3 Hasil Pengujian
|
||
|
||
- Tables/screenshots of successful scenarios
|
||
|
||
### 4.4 Evaluasi
|
||
|
||
- Strengths of the system
|
||
- Current limitations
|
||
- Suggested future improvements
|