<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>System Overview on sumicare-blog</title><link>https://neoboi76.github.io/system-overview/</link><description>Recent content in System Overview on sumicare-blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://neoboi76.github.io/system-overview/index.xml" rel="self" type="application/rss+xml"/><item><title>Booking Subsystem (semi-outdated)</title><link>https://neoboi76.github.io/system-overview/booking-subsystem-semi-outdated/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/system-overview/booking-subsystem-semi-outdated/</guid><description>&lt;ol>
&lt;li>The booking system is divided into two main &lt;em>views&lt;/em>: &lt;a href="Booking%20Subsystem%20%28semi-outdated%29.md#receptionist-view">receptionist&lt;/a> and &lt;a href="Booking%20Subsystem%20%28semi-outdated%29.md#staff-view">staff&lt;/a> views and systems.&lt;/li>
&lt;/ol>
&lt;h1 id="receptionist-view">Receptionist View&lt;/h1>
&lt;ol start="2">
&lt;li>
&lt;p>The receptionist view is concerned with the following functions: assigning clients to rooms, assigning therapists to clients, producing a treatment slip with necessary info (the receipt shown), &amp;ldquo;skipping&amp;rdquo; a therapist, adjusting time set if in case therapist and/or client is late for their appointment, set if a therapist has been specially &amp;ldquo;requested&amp;rdquo;, and request for back up therapists.&lt;/p></description></item><item><title>complete_overview</title><link>https://neoboi76.github.io/system-overview/complete_overview/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/system-overview/complete_overview/</guid><description>&lt;h3 id="introduction">Introduction&lt;/h3>
&lt;p>SumiCare is a web-based spa operations management platform used for managing the day-to-day operations of a spa, such as but not limited to: client appointment scheduling, task completion monitoring, reports generation, therapist and room allocation, and end-to-end transaction management. This platform can be utilized and customized by the target consumers of this product (who are predominantly enterprises operating in the wellness industry, such as spas) to suit their own particular needs. For the duration of this project, testing and implementation of SumiCare will be focused on the particular characteristics and needs of New Lasema Spa Jjimjilbang. Thus, in the creation and testing of SumiCare, the developers will cater to the needs of the aforementioned spa to shape the general platform, which can be implemented by other spas. Thus, there may be said to be a general and New Lasema Spa version of SumiCare. However, this documentation will be focused primarily on the features and structure of the general version.&lt;/p></description></item><item><title>Frontend Online Booking Subsystem</title><link>https://neoboi76.github.io/system-overview/frontend-online-booking-subsystem/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/system-overview/frontend-online-booking-subsystem/</guid><description/></item><item><title>Genesis</title><link>https://neoboi76.github.io/system-overview/genesis/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/system-overview/genesis/</guid><description>&lt;p>SumiCare is divided into three main parts: The &lt;a href="Booking%20Subsystem%20%28semi-outdated%29.md">Booking (assignment and reassignment) subsystem&lt;/a>, the Frontend online booking system (which includes the personalized recommendation system), and the End-to-End Transaction Management subsystem. The booking subsystem is the most significant and, therefore, the most labor-intensive.****&lt;/p></description></item><item><title>List of what I need from Franz</title><link>https://neoboi76.github.io/system-overview/list-of-what-i-need-from-franz/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/system-overview/list-of-what-i-need-from-franz/</guid><description>&lt;p>What I need:&lt;/p>
&lt;ul>
&lt;li>Exact font style use. If N/A, give the closest equivalent&lt;/li>
&lt;li>Exact color scheme. Preferrable if color codes or hex values are used to accurately reproduce the color on the UI.&lt;/li>
&lt;li>Official La sema logo&lt;/li>
&lt;li>Text for consent/data privacy clause for public booking website.&lt;/li>
&lt;/ul></description></item><item><title>system_architecture</title><link>https://neoboi76.github.io/system-overview/system_architecture/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/system-overview/system_architecture/</guid><description>&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>SumiCare is a web-based spa operations management platform designed to computerize the previously paper-based operational workflows of wellness enterprises such as New Lasema Spa Jjimjilbang. The platform encompasses two interconnected surfaces: a public-facing client booking website and a role-restricted internal operations system. Given this dual-surface structure, the complexity of its business rules (therapist decking, shift-based scheduling, multi-tier reporting, role-based access), and the constraints of an academic development timeline, SumiCare&amp;rsquo;s architecture has been deliberately designed to balance domain expressiveness, developer ergonomics, security, and deployability.&lt;/p></description></item><item><title>Tech Stack (tentative)</title><link>https://neoboi76.github.io/system-overview/tech-stack-tentative/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/system-overview/tech-stack-tentative/</guid><description>&lt;h1 id="frontend">Frontend&lt;/h1>
&lt;ul>
&lt;li>Angular Framework
&lt;ul>
&lt;li>Typescript&lt;/li>
&lt;li>Javascript&lt;/li>
&lt;li>HTML&lt;/li>
&lt;li>CSS (Tailwind css with ui component libraries)&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;h1 id="backend">Backend&lt;/h1>
&lt;ul>
&lt;li>Java Springboot
&lt;ul>
&lt;li>Java&lt;/li>
&lt;li>Spring Security&lt;/li>
&lt;li>Sprint Data JPA&lt;/li>
&lt;li>. . .&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;h1 id="database">Database&lt;/h1>
&lt;ul>
&lt;li>Using PostgreSQL with PgAdmin4 (for local hosting and testing)&lt;/li>
&lt;li>Use supabase as production database&lt;/li>
&lt;/ul>
&lt;h1 id="deployment">Deployment&lt;/h1>
&lt;ul>
&lt;li>Docker (and/or kubernetes)&lt;/li>
&lt;li>If using on-premise server
&lt;ul>
&lt;li>Either Local installation or Docker&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>If using local cloud server (either in one server or separate)
&lt;ul>
&lt;li>Docker and/or Kubernetes&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>If using mixed
&lt;ul>
&lt;li>Most likely frontend would be hosted on the cloud, while backend and db be hosted on the on premise server, Or&lt;/li>
&lt;li>Backend and frontend hosted on the cloud (as well as all microservices), while database would be hosted locally.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul></description></item><item><title>UI Stuff</title><link>https://neoboi76.github.io/system-overview/ui-stuff/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://neoboi76.github.io/system-overview/ui-stuff/</guid><description>&lt;p>What I need:&lt;/p>
&lt;ul>
&lt;li>Exact font style use. If N/A, give the closest equivalent&lt;/li>
&lt;li>Exact color scheme. Preferrable if color codes or hex values are used to accurately reproduce the color on the UI.&lt;/li>
&lt;li>Official La sema logo&lt;/li>
&lt;/ul>
&lt;p>'&lt;/p>
&lt;h3 id="five-main-user-types">Five main user types&lt;/h3>
&lt;ul>
&lt;li>
&lt;ul>
&lt;li>Superadmin (IT Manager)
&lt;ul>
&lt;li>Superadmin basically has unrestricted access to the system (all other functions below, including the ability to manage admins)&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>admin (IT)
&lt;ul>
&lt;li>Admin has all access to the system as mentioned below, but can also manage users below its tier, as well as access to the logs of the system (for non-repudiation purposes). Admin cannot manage other admins.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Manager
&lt;ul>
&lt;li>Manager has all the functionalities of receptionists and staff, but can manage them, as well as see and utilize a reports page detailing the projected revenue of la sema. They also have a comprehensive view of the transactions made encoded by the receptionist.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Receptionist
&lt;ul>
&lt;li>Receptionists can only do one thing, and that is to schedule sessions by assigning a therapist, a massage, and a room to a client, all while recording the whole transaction, producing a treatment slip manually (other reports, such as the cut-off report, are produced automatically).&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>Staff
&lt;ul>
&lt;li>The staff view needs no account. In fact, it is merely a view or interface where staff can view tasks assigned to them and acknowledge their task. Shown on one big TV, the view is merely there to inform them, and their interactions with the system are very limited. Hence, very limited permissions.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;h3 id="entry-pages">Entry pages&lt;/h3>
&lt;p>Sign in page&lt;/p></description></item></channel></rss>