Project Overview

Aligned with the plan to replace legacy measuring devices with new ones, the periodic replacement management system was rebuilt. The new system supports the attributes and control items of the new devices and adds Web-based functions for inventory, search, and reference, replacing phone/email/paper-driven operations. In parallel, to address the planned retirement of the current server, the operating platform was reviewed and adjusted, improving operational efficiency and reducing human error.

Technology Stack & Development Tools Used

• Programming Language: Java
• Full-stack Framework: Client’s in-house framework
• Database: PostgreSQL
• Cloud/Server/Infrastructure: WildFly Server
• Task Management Tool: Excel
• Communication Tool: Email (Outlook)

Client Challenges

• The current system cannot manage the new devices, blocking the migration.
• The running server is scheduled for retirement, making the platform hard to maintain.
• Inventory and data retrieval rely on phone and email, causing information fragmentation and person-dependence.
• Approval flow and status control are manual and paper-based, limiting progress visibility and governance.

Client Requirements

Given the above challenges, the client requested that the system be rebuilt to manage the new devices, improve operational efficiency, and prevent errors.

• Rebuild the system to fully manage the new measuring devices.
• Add Web-based functions for inventory, search, and reference to replace manual/paper processes and reduce mistakes.

Proposal & Approach

The project was executed in two clear phases.

Phase 1: Design Systematization

• Receive the basic design, analyze deltas, and create the detailed design.
• Apply the client’s sample documents and rules to standardize structure and format across the system.
• Submit the detailed design for client review prior to development.

Phase 2: Implementation & Verification

• Implement according to the approved detailed design.
• Create test cases from the detailed design and execute them in the client-specified test environment.
• Compile test evidence (screen hardcopies) and defect logs to make quality transparent.
• Prepare a quality summary report in the prescribed format to support acceptance decisions.