TiyoouwBahasa IndonesiaStart a brief

← All work

Case study · Design · 2024

HEYBREW!

A web shop and back office designed for Dopy Coffee in Jember: customers find beans by how they taste, the owner manages stock, orders, recipes and sales in one place.

Client
Dopy Coffee, Jember
Context
Systems Analysis and Design course, Universitas Jember
Role
UI design and system specification, in a team of five
Platform
Website
Year
2024
HEYBREW!: Coffee-bean shop with a taste-based recommender, for a Jember roaster.

In short

Problem
Orders, stock and sales were handled by hand, and customers had no easy way to pick beans by taste.
What I did
Designed, with my team, a shop and an admin side, from business requirements and data model to the interface.

01The problem

Dopy Coffee sold its beans and recorded orders, stock and sales by hand. That took the owner hours every week and left room for mistakes. Customers outside the shop had to ask before they could buy, and nothing helped them find beans that suited their taste.

02My role

Our team of five took the brief from the owner through the whole design: business requirements, process and data-flow diagrams, the database and the interface for both customers and the owner. I designed the interface and worked on the system requirements specification (SRS).

03Team and credits

Team
Five Information Systems students, Universitas Jember

04What I built

  • Taste-based recommendations

    Customers set ranges for sweetness, bitterness, acidity and body, and the shop suggests beans that match.

  • Shop and checkout

    Catalogue with search and filters, product pages with reviews, cart, address check and an e-receipt.

  • Orders and reviews

    Order status from verification to delivery; reviews only from customers who received the product.

  • Owner's back office

    Product catalogue, order handling, chat with customers, a recipe book for the shop and sales reports.

05Design decisions

  1. Taste as the way in

    Every bean shows the same four taste scores, so comparing and recommending use one language.

  2. Rules from the business

    The flows follow the shop's own rules: orders wait for the owner's approval, unpaid orders can be cancelled, and reviews close 30 days after delivery.

06Stack

Design
Figma
Analysis
BPMN, DFD, ERD and data model

07Visuals

Customer side. The landing page, and the catalogue with taste-based recommendations.
Customer side. The landing page, and the catalogue with taste-based recommendations.
A product page with taste scores and reviews, and the owner's sales report.
A product page with taste scores and reviews, and the owner's sales report.

Coursework. The design was not built or launched.

Start a brief

Pick what's easiest. I usually reply the same day.