Skip to main content
Back to Projects

University team project · 8 people · 2023 - 2024

Software Technology Internship

A browser-based beverage, inventory, and billing system built with Spring Boot by an eight-person Scrum team.

  • Java 17
  • Spring Boot 3
  • JavaScript
  • Thymeleaf
  • H2 and MySQL
  • Git
8 Members
Team
Scrum
Methodology

A university team project that replaced office drink lists and handwritten payment records with one web application. The system covers purchases, personal balances, stock, suggestions, orders, statistics, and user administration across employee, manager, and administrator roles.

Problem

The client managed office drinks with paper lists, which made purchases, outstanding balances, stock, and repeat orders difficult to track. The replacement had to stay quick enough for everyday use while separating employee, manager, and administrator permissions.

Approach

We built a Spring Boot and Salespoint application using Scrum. The backend separates shop, stock, suggestions, statistics, and user management into focused packages; Thymeleaf renders the interface, and Spring Security enforces role- and office-specific access.

Outcome

Delivered a working prototype and its supporting requirements, architecture diagrams, tests, and developer documentation. My work included implementation, unit testing, and design documentation within the shared codebase.

Architecture

A classic Spring Boot Model-View-Controller structure, with Spring Data JPA for object-relational mapping and Spring Security for granular access control across employee, manager, and administrator roles.

Highlights

Purchases and Balances

One-click drink purchases update personal balances and can be reversed when entered by mistake.

Suggestions and Orders

Employees suggest products; managers review them, build orders, and retain an order history.

Role-Based Access

Authentication that separates administrative duties from standard staff operations.

Financial Logging

Accounting features tracking procurement costs against internal usage and sales.

Timeline

  1. Requirements

    Analyzed the existing workflow and mapped the logistics processes to model.

  2. Backend

    Implemented domain models and workflows for stock, orders, purchases, and user management.

  3. UI and Testing

    Integrated the server-rendered Thymeleaf views and completed the JUnit suites.

  4. Delivery

    Completed the prototype, tests, cross-team review, and developer documentation.