Architecture / 4+1 / View 01

/ARCHITECTURE /USER VIEW

The User View shows Intaliq as its actors see it, organized by the use cases in the SRS. End users track activities, set goals, book sessions, find partners and use the AI chatbox. Fitness coaches create sessions, admit members and post announcements. This (+1) view ties the other four views to these scenarios.

USE_CASE_DIAGRAM.UML
Intaliq use case diagram with User and Coach actors
FIG 1.0 Intaliq system boundary with its primary actors (End User, Fitness Coach) and supporting external services, covering booking, goals, partners, the AI chatbox, session creation, admissions and announcements.

Key Actors

End User
Primary

A participant who does outdoor running, cycling or hiking, from beginner to experienced. Logs activities, sets goals, browses and books group sessions, connects and chats with partners, and asks the AI chatbox for fitness advice.

Fitness Coach
Primary

Plans and runs outdoor group sessions. Creates sessions (type, date, time, location, capacity, intensity), reviews and admits join requests, and posts announcements to session members.

AI Recommendation Service
Secondary

External AI service behind the chatbox. Gives goal-setting advice, recovery suggestions, progress analysis and activity recommendations, and never gives medical diagnosis or treatment (SI-2).

Notification & Auth Services
System

External services for push notifications (session reminders, partner updates, announcements, goal reminders) and authentication (email login, verification codes, password reset, 2FA), as in SI-3, SI-4 and CI-3.

Use Case Realizations

UC-01: Book a Group Session

Actor
End User
Goal
Join a coach-led outdoor session (running, cycling or hiking) that matches their schedule and level.
Brief Flow
  1. User logs in and opens the Sessions tab
  2. Browses available sessions and selects one
  3. Reviews session and coach details (time, location, capacity, intensity)
  4. Submits a booking request; system confirms it was sent
  5. Coach accepts; system adds the user and sends a notification

UC-02: Create a Group Session

Actor
Fitness Coach
Goal
Publish a new outdoor session that users can discover and request to join.
Brief Flow
  1. Coach logs in and selects “Create Group Session”
  2. Enters activity type, date, time, location, capacity and intensity
  3. Submits; system validates the input (e.g. rejects past dates)
  4. System saves the session and confirms it is visible to users

UC-03: Admit Session Members

Actor
Fitness Coach
Goal
Decide which pending requests to accept, respecting session capacity and difficulty level.
Brief Flow
  1. Coach opens a session’s pending membership requests
  2. Reviews the user’s request and profile, then selects Accept or Reject
  3. System checks capacity and fitness-level match, updates the member list and notifies the user