← All projects/ dynamic-reference-list

// ReliaQuest Labs · team project

Dynamic Reference List

A shared reference system for customers and internal engineers, developed during a four-week software engineering lab track.

JavaSpring BootPostgreSQLGitLab

Product screenshots and source code are not published here. The overview is limited to public information.

// 01

The problem

Reference information needs to stay consistent while serving different customers and internal engineering teams. The lab project explored a centralized place to search, organize, and manage that information.

// 02

My contribution

I participated as one of five student developers. The public team recap confirms our collaboration on the project, merge request reviews, and integration troubleshooting. It does not attribute particular features to individual teammates, so this case study describes the team scope rather than claiming sole ownership.

// 03

Architecture overview

  1. 01Customer & engineer interface
  2. 02Spring Boot application
  3. 03PostgreSQL reference data

High-level technology overview from the public team recap. This is not an internal deployment diagram; implementation boundaries and infrastructure are intentionally omitted.

// 04

Engineering decisions

Consistent data with customer-specific access

The team worked toward shared reference information that could adapt to different customers while managing access and permissions. The public description does not establish the exact authorization implementation.

Backend and database meet the user experience

Work spanned backend functionality, database design, and the user-facing application. Connecting these pieces required integration troubleshooting and collaboration.

A shared engineering workflow

GitLab and merge request reviews provided a process for discussing and integrating team changes with guidance from mentor Joshua Ryals.

// 05

Outcome & next steps

Completed the four-week lab track as part of the team that developed the Dynamic Reference List. No customer adoption or performance metrics are claimed.

A public case study can explain the purpose, stack, and collaboration without exposing proprietary code, customer records, or internal screenshots.

Source: Gavin Wilson’s public team recap, reposted on my LinkedIn. Individual feature ownership and exact lab dates are not independently documented here.

← Back to selected workTalk about the project ↗

Where would you like to go?

Search projects, experience, or contact. Use Tab or arrow keys to explore, Enter to open.