Skip to main content

UBS Product Requirement Document (UBS:PRD)

1. Introduction​

1.1 Overview​

  • Product Category: Personal Efficiency / Calendar / Task management
  • Purpose:
  • Target Audience:
    • Individuals managing personal schedules / All who wants to keep affairs in order
    • Freelancers who balance multiple clients/projects.
    • Team Leads of Independent professionals' groups

1.2 Goals and Objectives​

  • Provide users with the ability to take control of their tasks based on GTD principles.
  • Enable flexible planning horizon selection, ranging from a single day to lifetime planning.
  • Allow clustering of all available personal time to help establish work-life balance fundamentals.
  • Support habit formation and continuous improvement management and tracking based on Kaizen principles.
  • Maximize efficiency through keyboard shortcuts and command-line interface options.
  • Enable creation of rules for appropriate automatic task rescheduling.
  • Provide convenient task progress tracking tools (including Pomodoro technique) and time expenditure reporting.
  • Create functionality for convenient sharing of partial or full schedule access based on tags.
  • Enable task delegation, meeting invitations, task status updates and other service messages via Telegram, WhatsApp, and email.
  • Allow users to create their own unified Master Calendar with integration capabilities for other calendars (Google, Microsoft, etc.).
  • Provide the ability to create multiple different booking pages with anonymous access.

2. Scope​

2.1. Features In Scope​

  • TBD

2.2. Features Out of Scope​

  • TBD

3. Functional Requirements​

3.1. User Roles​

  • Non-authorized User
  • Authorized User

3.2. Core Functionalities​

3.2.1. EPIC-00 :: Unique User Interface and User Experience​

3.2.2. EPIC-01 :: Advanced Task and Event Management​

3.2.3. EPIC-02 :: Selected Planning Horizon​

3.2.4. EPIC-03 :: Hot Keys Control Ability​

3.2.5. EPIC-05 :: The Public Booking Page​

3.2.6. EPIC-06 :: UBS API​

4. Non-Functional Requirements​

  • Performance: Responsive interface, optimized for quick task addition.
  • Scalability: Designed for single users and small groups.
  • Availability: Reliable access across devices with cloud sync.
  • Security: Basic data encryption and secure login options (e.g., OAuth).

5. User Interface (UI/UX) Requirements​

  • Адаптивный Web-дизайн -- в первую очередь Desktop + Modern Tablet (> 1023px)
  • ViewType: Days
    • Range/Count: 1-14 days
    • Vertical Zoom: 1/2day, 1h, 30min, 15min, 10min
  • ViewType: Weeks
    • Range/Count: 1-6 weeks
    • Vertical Zoom: 1/2day, 1h, 30min, 15min, 10min
  • ViewType: Months
    • Range/Count: 1-12 months
    • Vertical Zoom: week / day
  • ViewType: Years
    • Range/Count: 1-5,10,20,50,100 years
    • Vertical Zoom: quarter / month
  • ViewType: TimeLine
    • Range/Count/Zoom - 1h-days-weeks-months-quarters-years-life
  • Адаптивный интерфейс умеет изменять для отображения начиная со small mobile (>= 360px)
  • Drag-and-Drop

6. Technical Requirements​

  • Кросплатфоменность за счёт web технологий и JS
  • Упор реализации на Front-end с целью дальнейшей более-лёгкой реализации мобильного приложения на базе ReactNative, а также десктопного приложения на базе проектов типа Electron (предстоит ещё выбрать)
  • Front-end должен быть реализован на React.js + MobX
  • Front-end использует для обработки дат dayjs
  • Front-end использует для DnD: DnD Kit или ReactDnD
  • Back-end должен быть реализован на Node.js + Express.js или на Metarhia
  • DB: PostgreSQL
  • Front-end и Back-end должны быть оформлены в виде docker контейнера

7. Milestones and Timeline / Road map​

  • Versio 0.1: MVP

8. Therms, Constraints, Risks and Dependencies​

  • Limited adoption due to competition with established tools. - User data privacy concerns without robust security measures.
  • Google API for integration
  • Push notification services (на начальном этапе только e-mail и IM)
  • WhatsApp API for integration

9. Glossary​

10. User Stories / Uses Cases​