Claim Missing Document
Check
Articles

Found 2 Documents
Search
Journal : bit-Tech

Iterative Enhancement of Academic Information System UI/UX Through Prototype-Based and User Centered Design Methodology Vanessa Priscilia Wijaya; Mychael Maoeretz Engel
bit-Tech Vol. 8 No. 2 (2025): bit-Tech
Publisher : Komunitas Dosen Indonesia

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.32877/bt.v8i2.3143

Abstract

The Academic Information System serves as a core platform for managing academic activities, yet despite it being a core platform there are still many institutions face the same issues related to poor user experience (UX) and user interface (UI) design, which affect the operational efficiency and user satisfaction. While many studies have explored usability improvement in academic systems, few have focused on iterative prototyping combined with user-centered design methodologies in fully deployed university platforms. The goal of this study is to address these issues by redesigning the CIS interface through an iterative, prototype-based using Design Thinking and User-Centered Design (UCD) methodologies. It’s focus on improving system clarity, navigation, and user engagement. Online questionnaires and interviews with 50 students were used to gather data for the primary evaluation, which was based on the User Experience Questionnaire (UEQ). The UEQ was used both before and after the redesign to measure six experiential dimensions: Attractiveness, Perspicuity, Efficiency, Dependability, Stimulation, and Novelty. And the results show significant improvements across all categories with rated excellent, indicating it’s successfully enhanced usability, visual appeal, and workflow clarity. These improvements has made an increased to the user satisfaction during academic task completion. Practically, the redesigned CIS enables students to access critical academic information more efficiently, improving daily academic productivity and digital interaction quality. This study highlights the effectiveness of using iterative, and user-centered methodologies in transforming outdated academic systems into intuitive, human-centered platforms that promote both institutional efficiency and user well-being.
Comparative Analysis of Performance Aspects Between Chroma and Pgvector as a Vector Database Ali Zaenal Abidin; Mychael Maoeretz Engel
bit-Tech Vol. 8 No. 2 (2025): bit-Tech
Publisher : Komunitas Dosen Indonesia

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.32877/bt.v8i2.3198

Abstract

System architects face a critical choice between specialized vector databases like ChromaDB and general-purpose options like PostgreSQL with the PGVector extension. This decision profoundly impacts TCO and system viability, yet holistic performance data under resource constraints is scarce. We answer whether a specialized or generalized architecture provides superior operational efficiency and accuracy when resources are limited and providing an evidence based guide for navigating the trade offs between cost, speed, and accuracy. We conducted 119 tests on the Deep1M dataset within a resource-constrained 4GB RAM Docker, measuring latency, ingestion speed, storage overhead, and recall accuracy. The results reveal a stark architectural trade-off.  ChromaDB delivers highly consistent, low query latency, with only a 1.3-fold performance degradation as data scales. However, this speed comes with significant operational costs:-massive storage inefficiency averaging 395 times the raw data size and severe ingestion bottlenecks, showing a 491.7 fold slowdown. Conversely, PostgreSQL with PGVector demonstrates resource efficiency. Its storage overhead is minimal at 3-4 times the raw data size, and it provides 7.0 times better ingestion scalability. Crucially, it achieves statistically superior accuracy at production scale (≥250K vectors), delivering near-perfect 99.6-99.8% recall compared to ChromaDB's 91-95%. The trade-off is performance variability, where poorly tuned PostgreSQL queries can be up to 16.6 times slower than ChromaDB. We conclude that for dynamic production applications where TCO, scalability, and high accuracy are priorities, PGVector is more viable. ChromaDB's predictable latency is better suited for latency-critical applications with static data, but only if its high operational costs are acceptable.