Architecture /
4+1 View Model
The 4+1 Architectural View Model is a framework used to describe the architecture of software-intensive systems based on multiple, concurrent views. These views address the concerns of different stakeholders, from end-users to developers and system engineers, anchored by defining use cases.
User View
(+1 Anchor)Logical View
Process View
Dev View
Physical View
NODE_INSPECTION // DETAILS
User View (+1)
Represents Intaliq from the perspective of end users and fitness coaches. It defines the core scenarios the architecture must support: booking and creating group sessions, admitting members, setting goals, connecting with partners and using the AI chatbox. It ties the other four views together.
Logical View
Focuses on the functional requirements. It models the domain entities from the SRS data dictionary (User, Coach, Session, Goal, Activity and Partner) along with their attributes, constraints and relationships.
Process View
Addresses runtime behaviour: synchronous booking and admission requests, asynchronous push and email notifications, offline action sync, and concurrent access to session capacity, all against the SRS response-time and availability targets.
Development View
Shows how the software is organized for implementation: modules, packages and dependencies, starting from the prototype stack of JavaScript, HTML and CSS with Vite, Supabase, GitHub and Vercel.
Physical View
Maps the software onto hardware and cloud services: iOS/Android devices, frontend hosting, the Supabase backend and database, and external AI, notification and email services connected over HTTPS.