1

Rel’Event

A project report submitted to

Rajiv Gandhi Proudyogiki Vishwavidhyalaya, Bhopal
in partial fulfillment for the award of
the degree of
Bachelor of Technology
in
Information Technology

DEPARTMENT OF INFORMATION TECHNOLOGY

ACROPOLIS INSTITUTE OF TECHNOLOGY & RESEARCH

INDORE- 453771
2022 - 2023

TITLE OF PROJECT REPORT

 2

A project report submitted to

Rajiv Gandhi Proudyogiki Vishwavidhyalaya, Bhopal
in partial fulfillment for the award of
the degree of
Bachelor of Technology
in
Information Technology

PROJECT GUIDE SUBMITTED BY

PROF. VISHAL TRIVEDI NityaPathak 0827IT191080

Purva Wakode 0827IT191089
Rashi Jain 0827IT191093
Sachi Gupta 0827IT191098

DEPARTMENT OF INFORMATION TECHNOLOGY

ACROPOLIS INSTITUTE OF TECHNOLOGY & RESEARCH

INDORE- 453771

2022 - 2023
 3

ACKNOWLEDGEMENT

We thank the almighty Lord for giving me the strength and courage to sail out
through the tough and reach on shore safely.
Thereseveraler of people without whom this project's work would not have
been feasible. Their high academic standards and personal integrity provided
me with continuous guidance and support.
We owe a debt of sincere gratitude, a deep sense of reverence, and respect to
our guide and mentor Prof. Vishal Trivedi, AITR, Indore for his motivation,
sagacious guidance, constant encouragement, vigilant supervision, and
valuable critical appreciation throughout this project work, which helped us to
complete the project on time.
We express profound gratitude and heartfelt thanks to Prof. Prashant
Lakkadwala, HOD IT, AITR Indore for his support, suggestion, and
inspiration in carrying out this project. I am very much thankful to other
faculty and staff members of the IT Dept, AITR Indore for providing me with
all support, help, and advice during the project. We would be failing in our
duty if we do not acknowledge the support and guidance received from Dr. S
C Sharma, Director, AITR, Indore whenever needed. We are grateful to our
parents and family members who have always loved and supported us
unconditionally. To all of them, we want to say “Thank you”, for being the
best family that one could ever have and without whom none of this would
have been possible.

NITYA PATHAK-(0827IT191080),
PURVA WAKODE-(0827IT191082),
RASHI JAIN-(0827IT191093),
SACHI GUPTA(0827IT191098)

ACROPOLIS INSTITUTE OF TECHNOLOGY &

RESEARCH, INDORE, 453771
 4

CERTIFICATE
This is to certify that Nitya Pathak (0827IT191080), Purva

Wakode(0827IT191089), Rashi Jain(0827IT19193), Sachi Gupta(0827IT191090)

have completed their project work, titled “Rel’Event” as per the syllabus and have

submitted a satisfactory report on this project as a part of fulfillment towards the

degree of “BACHELOR OF TECHNOLOGY” (Information Technology) from

RAJIV GANDHI PROUDYOGIKI VISHWAVIDHYALAYA, BHOPAL.

HEAD OF THE DEPARTMENT PROJECT GUIDE

DIRECTOR

ACROPOLIS INSTITUTE OF TECHNOLOGY &

RESEARCH, INDORE, 453771
 5

CERTIFICATE

This is to certify that Nitya Pathak (0827IT191080), Purva

Wakode(0827IT191089), Rashi Jain(0827IT19193), Sachi Gupta(0827IT191090)

have completed their project work, titled “Rel’Event” as per the syllabus and have

submitted a satisfactory report on this project as a part of fulfillment towards the

degree of “BACHELOR OF TECHNOLOGY” (Information Technology) from

RAJIV GANDHI PROUDYOGIKI VISHWAVIDHYALAYA, BHOPAL.

INTERNAL EXAMINER EXTERNAL EXAMINER

ACROPOLIS INSTITUTE OF TECHNOLOGY &

RESEARCH, INDORE, 453771
 6

TABLE OF CONTENTS

1. Introduction

1.1. Purpose 8
1.2. Scope 8
1.3. Problem in existing system 8
1.4. Statement of Problem 9

2. System Requirement Analysis

2.1 Introduction

2.1.1 Purpose 9
2.1.2 Product Scope 10

2.2 Overall Description

2.2.1 Product Perspective 10

2.2.2 Product Functions 11
2.2.3 Design and Implementation Constraints 11

2.3 External Interface Requirements

2.3.1 Hardware Interfaces 12

2.3.2 Software Interfaces 12

2.4 Functional Requirement

2.4.1 System Feature 1 13

2.4.2 System Feature 2 (and so on) 14

2.5 Nonfunctional Requirements

2.5.1 Performance Requirements 14

2.5.2 Safety Requirements 14
2.5.3 Security Requirements 15

2.6 Project Plan

2.6.1 Team Members 15

2.6.2 Division of Work 15
 7

3. Analysis

3.1. Methodology Used 16

3.2. Use Case diagram 17
3.3. ER Model 21
3.4. Sequence Diagram 22
3.5. Activity Diagram 25

4. Design

4.1. Architectural Design

4.1.1. System Architecture Diagram 30
4.1.2. Description of Architectural Design
4.2. Component Design
4.2.1. Flow Chart 31
4.3. Interface Design 32
4.3.1. Screenshots

5. Implementation

5.1. Language and database system used for the implementation 35

5.2. Features of language and database used for the project 37

6. Testing

6.1. White Box Testing 39

6.1.1. Test Cases and results 39
6.2. Black Box Testing 40

7. Future Scope and Limitations 40

8. Conclusion 41

9. Reference 42
 8

1. Introduction

1.1. Purpose

With the most recent developments and changes due to covid and digitalization, data and
information must be effectively gathered, managed and stored in order to keep pace and
compete in the event industry.
Thus, Rel’Event is an application to efficiently reach the information to the target audience
and they will not miss out on any opportunities.
In this era of digitalization, the information regarding all events is being spread using digital
platforms like WhatsApp, Emails etc. Sometimes it becomes very messy and unmanageable.
We all have some time or the other face a common issue of missing an event because there is
always a group of information we receive.

1.2. Scope

Clubs and organizations are a big part of college life. All students should be strongly
encouraged to pursue club and organizational membership opportunities to help them enrich
their personal and professional skills.
The objective of this application is to develop a system that effectively manages all the data
related to the various events that take place in an organization. The purpose is to maintain a
centralized database of all event related information. The goal is to support various functions
and processes necessary to manage the data efficiently
.

1.3. Problem in existing system

This existing system is not providing secure registration and profile management of all the
users properly. This system is not providing on-line help. This system doesn’t
provide tracking of users activities and their progress. This manual system gives us very less
security for saving data and some data may be lost due to mismanagement. This system is
not providing
 9

event management through the internet. This system is not providing proper events
information. The System is giving manual information through the event management
executer.

1.4. Statement of Problem

Students during their college time often miss out on important events and opportunities.
They find difficulty in finding college annual events, campaigns, hackathons, inter college
events and competitions details. This happens due to insufficient information shared to
students or sometimes details do not reach to students at all.

Available applications like mailing, WhatsApp or Google calendar do not provide users
efficient help or lack in excess features like direct register or website link, checkout event
related pictures and get detailed and relevant information regarding events.

The excess features may seem minimal but, the students who are actually interested in
attending those events or want to take part in it. They can have their active participation in
college and increase their productivity.

2. System Requirement Analysis

2.1 Introduction

2.1.1 Purpose

The arrival of the pandemic COVID 19 brought in this world a big change. When we were
put in a situation where everything we could only do online, we have now become used to
it. Like this only is the case of our Events regarding universities, colleges, schools,
professional institutions etc. Every detail about the same use to come on online platforms
like WhatsApp, Email etc. But we all have faced a common problem of missing any event
or ignoring any event just because it is not that attractive.

2.1.2 Product Scope

Rel’Event is an Online event management software project that serves the functionality of an
event manager. The system allows only registered users to login and new users are allowed
 10

to register on the application. The project provides most of the basic functionality required
for an event. It allows the user to select from a list of event types. Once the user enters an
event type eg(Marriage, Stage Show etc), the system then allows the user to select the date
and time of event, place and the event equipment. All this data is logged in the database and
the user is setting up his username and password while registering . The data is then sent to
administrator (website owner) and they may interact with the client as per his requirements
and this contact data is stored in the database.

2.2 Overall Description

2.2.1 Product Perspective

This software is designed to organize the college events like campaigns, club activities, club
recruitments etc. According to the user’s requirement they can allow push notification. And
also give their feedback in the form of photos and comments as well as get to check others'
feeds.

The software will be a new independent product. It is intended for the event organizing
committees and other concerned users who want to participate. The product will import its
database from firebase with its integrated development environment.

This information can only be accessed by the staff members and the manager/supervisor
aside from the developers. All the forms used in the product follow a clear and logical
structure. Errors will be minimized through the use of bottom navigation bar and command
buttons to eliminate the excessive use of text input. Management of data includes filtering
events date wise, creating events and uploading feedback.

2.2.2 Product Functions

As described in Problem Domain. We have proposed the additional features all together
which would increase the efficiency of the event orientation app which current applications
lack. It will make the students and faculties check events easily and information will reach
the users effectively.

Through Event Orientation App:

 11

● Students can check past and future events in the app.

● Maintained event related records.
● Students and faculties will be at ease as event details are shared correctly.
● Direct link for registration and event website is provided.
● Anyone with this app can get notification whenever a new event is launched.
● Check the schedule day wise.
● Improves accuracy and timeliness

2.2.3 Design and Implementation Constraints

Design is the first step in the development phase for any techniques and principles for the
purpose of defining a device , a process or system in sufficient detail to permit its physical
realization. Once the software requirement have been analyzed and specified the software
design involves three technical activities-Design, Coding, Implementation, Testing that are
required to build and verify the software.The design activities are of main importance in this
phase, because in this activities decisions ultimately affecting the success of the software
implementation and its ease of
maintenance is made. This decision has the final bearing upon the reliability and
maintainability of the system. Design is the only way to accurately transfer the customers
requirements into finished software or system .Design is the place where quality is fostered
in development. Software design is the process through which requirements are translated
into a representation of software. Software requirement is conducted in two steps.
Preliminary design is concerned with the transformation of requirements into data

2.3 External Interface Requirements

2.3.1 Hardware Interfaces

For Desktop;

● Hardware Components: Processor – Intel Pentium 4

● Hard Disk – 50 GB
● Memory – 2GB RAM
● Mouse – Any Standard
 12

● Keyboard – Any Standard

● Monitor – Any color monitor
● Local Area Network Preferable

For Mobile Phones:

● ROM – 32 GB
● Memory – 2GB RAM
● Local Area Network Preferable

2.3.2 Software Interfaces

This application only uses the internet in order to work on smartphones and Web browsers.

The interface of the software will provide options for relatively easy data input processes
text-boxes that will be properly labeled. It will also have a user-friendly view of the whole
system with simple and easy undertaking of action-driven processes as command buttons
are functionally labeled. With all these, target users of this software will relatively find it not
difficult to use it.

The organizers have respective accounts with a password that enables only the organizer/s to
login onto the system. Passwords are required so that no one else can access the system or
database. In the case of the administrator, he/she needs to have adequate knowledge about
maintaining databases should the system encounter problems. Because the participants and
suppliers themselves provide the information entered into the database, there should be very
little problems about the information entered. However, the organizer should always triple
check every information given.

2.4 Functional Requirement

Functional requirement defines a function of a software system or its component.

A function is described as a set of inputs, the behavior, and outputs. Functional
 13

requirements may be calculations, technical details, data manipulation and processing and
other specific functionality that define what a system is supposed to accomplish.
Behavioral requirements describing all the cases where the system uses the functional
requirements are captured in use cases.

NUMBER OF MODULES
The system after careful analysis has been identified to be presented with the
following modules:
The Modules involved are:

Event Management Module :

The employees who can use the application their personal information, contact
information and other information etc…
This module consists of event information. All the information like type of the event,
incharge of the event. All information is maintained here.
Here in this module application is maintaining the total information of the event and the
resources. Like the type of the resource, resource details and resource management.

Event Task Manager Module :

The module has the information of the events and their task manager details.
Events task are maintained here, the total details of the events and incharge details
maintained. In this module the information of the event and their details like, what are the
events are there and from which event and to which event the movement is going on ,
which date , status of the event etc.

Scheduling :

This module consists of event information. All the information like type of the
event, in charge of the event. All information is maintained here.

Security & Authentication Module :

Security & Authentication module is main module which can provide security for
entire processing of the system by using username, password, login, password
modifications etc.
 14

Reports Module :

In this module system can generate different types of reports.

Payment Module:

In this module users can pay the amount.

2.5 Nonfunctional Requirements

2.5.1 Performance Requirements

● the system needs to be reliable
● if unable to process the request then appropriate error message should be generated
● application should load without any issue

2.5.2 Safety Requirements

● the details need to be properly maintained

● users must be authenticated
● the database must be kept backed up

2.5.3 Security Requirements

● After entering the password and user id the user can access his profile
● the details of user must be safe and secure
● there should be no sharing of personal data

2.6 Project Plan

2.6.1 Team Members

1. NITYA PATHAK
2. PURVA WAKODE
3. RASHI JAIN
4. SACHI GUPTA
 15

2.6.2 Division of Work

Nitya Pathak: I worked on the frontend using a flutter . Flutter is designed to support
mobile apps that run on both Android and iOS, as well as interactive apps that you want to run on
your web pages or on the desktop. I also worked upon the documentation and was on the creative
side of the project.

Purva Wakode: I worked on the backend and database and was on the functional side of
the project. Google Firebase is a Google-backed application development software that enables
developers to develop iOS, Android and Web apps.

Rashi Jain: I worked upon the frontend using flutter. Flutter allows the unification of app
developers into a single mobile, web, and desktop app team, building branded apps for multiple
platforms out of a single codebase. I also worked upon the documentation and was on the creative
side of the project.

Sachi Gupta: I worked on the backend and database and been on the functional side of the
project. Firebase lets you export your mobile app data (iOS and Android) to BigQuery and, by
matching on UserID, gives you a complete picture of app engagement across channels and
devices.

3. Analysis

3.1 Methodology Used

This software is designed to organize the college events like campaigns, club activities, club
recruitments etc. According to the user’s requirement they can allow push notification. And
also give their feedback in the form of photos and comments as well as get to check others'
feeds.

The software will be a new independent product. It is intended for the event organizing
committees and other concerned users who want to participate. The product will import its
database from firebase with its integrated development environment.

This information can only be accessed by the staff members and the manager/supervisor
 16

aside from the developers. All the forms used in the product follow a clear and logical
structure. Errors will be minimized through the use of bottom navigation bar and command
buttons to eliminate the excessive use of text input. Management of data includes filtering
events date wise, creating events and uploading feedback.

3.2 Use Case Diagrams

 17

3.2.1 Sign Up

Use case name Sign Up

Actor Admin/Participant

Pre-condition User must be new

Post-condition Can Register

Flow of events Open app, see events, etc

3.2.2 Login

Use case name Login

Actor Admin/Participant

Pre-condition User must be registered

Post-condition Login successfully

Flow of events Open the app, view events etc.

3.2.3 Logout

Use case name Logout

Actor Admin/Participant

Pre-condition User should be logged-in

Post-condition Logout successfully

Flow of events Click on logout

 18

3.2.4 Create Event

Use case name Create Event

Actor Admin

Pre-condition Event Creator should be logged in

Post-condition Event Created

Flow of events Create Event, Enter details

3.2.5 View Event Details

Use case name View Event Details

Actor Admin/Participant

Pre-condition Audience/Event Creator should be logged in

Post-condition Item removed from cart successfully

Flow of events Open app, event name

3.2.6 Register for Event

Use case name Register for Event

Actor Participant

Pre-condition Audience should be logged in

Post-condition Registered for event

Flow of events Open app, View event details, Register

3.2.7 Feedback

Use case name Feedback

 19

Actor Participant

Pre-condition Audience should be logged in

Post-condition Feedback given

Flow of events Open app, view events, submit feedback 

3.2.8 View List of Events

Use case name View List of Events

Actor Admin/Participant

Pre-condition Admin/Participant must be logged in

Post-condition List of events

Flow of events Login

3.2.9   Delete Event

Use case name Delete Event

Actor Admin

Pre-condition Administrator have access to the database

Post-condition Event deleted successfully

Flow of events Through database

3.2.10View Profile

Use case name View Profile

Actor Admin/Participant
 20

Pre-condition Admin/Participant should be logged in

Post-condition Profile view

Flow of events Open app, login, profile icon

3.3 ER Diagram
 21

3.4 Sequence Diagram

3.4.1 Sequence diagram for signup

 22

3.4.2 Sequence diagram for Create Event

 23

3.4.3 Sequence diagram for viewing specific event information

 24

3.5 Activity Diagram

3.5.1 Activity diagram for login

 25

3.5.2 Activity diagram for creating event

 26

3.6 Class Diagram

 27

4. Design

4.1 Architectural Design

42.1.1. System Architecture Diagram
 28

4.2 Component Design

4.2.1 Component Diagram

4.3 Interface Design

42.3.1. Screenshots
 29

Screenshot 1: App icon Screenshot 2: Splash screen

Screenshot 3: Login page. Screenshot 4: Sign Up page

 30

Screenshot 5: Home Page Screenshot 6: My Profile page

Screenshot 7: Create Event page Screenshot 8: Event Details Page

 31

Screenshot 9: Forgot Password Screenshot 10: Feedback

5. Implementation

5.1 Language and database system used for the implementation

1. Android studio (v2021.1.1):

Android Studio is the official Integrated Development Environment (IDE) for android application
development. Android Studio provides more features that enhance our productivity while building
Android apps.
We require this technology to run our avd or android virtual device to see the output of the user
interface. The Android Emulator simulates Android devices on your computer so that you can test
your application on a variety of devices and Android API levels without needing to have each
physical device.

2. GitHub:
GitHub is an online software development platform used for storing, tracking, and collaborating on
software projects. It enables developers to upload their own code files and to collaborate with fellow
developers on open-source projects. GitHub essentials are:
● Repositories
● Branches
● Commits
● Pull Requests
● Git (the version control software GitHub is built on)

3. Visual studio code (v1.164.2):

VS Code is a free, easy-to-use, and lightweight code editor that provides excellent support for
Flutter; this support for Flutter is provided via an extension for VS Code.

4. Flutter:
Flutter is an open-source Software Development Kit (SDK) by Google, for creating
high-performance, high-fidelity mobile apps for iOS, Android and Web. The Flutter SDK makes it
easy for developers to develop user interfaces that interact smoothly in the app while reducing the
 32

amount of code required to synchronize and update the app’s view.

1. Hot Reload
The changes made by the developers can be seen instantaneously with Hot Reload. This feature is
super-handy for developers as it makes the changes visible in the app itself. As the changes made are
visible within seconds, developers can fix the bugs in no time.

2. Cross-Platform Development
CPD saves time, energy and money. With Flutter, you need to write the code once, maintain and can
use that for two apps. The need has gone for developing a different code for a different platform.

3. Accessible Native Features and SDKs

Your app development process gets easy and delightful through Flutter’s native codes, third-party
integrations, and platform APIs. Therefore, you can easily access the native features and SDKs on
both Android and iOS platforms and reuse the widely-used programming languages such as Kotlin
and Swift.

4. Minimal Code
Flutter is developed using Dart programming language. Dart uses JIT and AOT compilation that
helps improve the overall startup time, functioning and accelerates the performance. JIT enhances
the development system with the hot reload function. It refreshes the UI without putting in the effort
to build a new one.

5. Widgets
In Flutter, the widgets are given an upper hand. It is capable of developing customizable and
complex widgets. Most importantly, Flutter has all the sets of widgets from Material Design and
Cupertino pack and it helps to provide a glitch-free experience in this case over and above all the
other platforms.

6. Native Feel and Features

Flutter enables you to use your existing code Java, Obj-C and Swift to gain the key to native features
which are platform specific. Camera and Geolocation are features connected with the use of native
languages and offers you the convenience of working in the native language and, it provides access
to the native features of both iOS and Android platforms.
 33

5. Firebase:
Google Firebase is a Google-backed application development software that enables developers to
develop iOS, Android and Web apps.

Firebase Features:
● Real-time Database − Firebase supports JSON data and all users connected to it receive live
updates after every change.
● Authentication − We can use anonymous, password or different social authentications.
● Hosting − The applications can be deployed over secured connection to Firebase servers.

5.2 Features of language and database used for the project

1. Features of Android Studio:

● It has a flexible Gradle-based build system.

● It has a fast and feature-rich emulator for app testing.
● Android Studio has a consolidated environment where we can develop for all Android
devices.
● Apply changes to the resource code of our running app without restarting the app.
● Android Studio provides extensive testing tools and frameworks.
●
2. Firebase Advantages:

● It is simple and user friendly. No need for complicated configuration.

● The data is real-time, which means that every change will automatically update
connected clients.
● Firebase offers a simple control dashboard.
● There are a number of useful services to choose from.

3. Dart

1. Open Source
Dart is an open-source programming language, which means it is freely available. It is developed by
 34

Google, approved by the ECMA standard, and comes with a BSD license.

2. Platform Independent
Dart supports all primary operating systems such as Windows, Linux, Macintosh, etc. The Dart has
its own Virtual Machine which is known as Dart VM, that allows us to run the Dart code in every
operating system.

3. Object-Oriented
Dart is an object-oriented programming language and supports all oops concepts such as classes,
inheritance, interfaces and optional typing features. 

4 Extensive Libraries
Dart consists of many useful inbuilt libraries including SDK (Software Development Kit),
core, math, async, math, convert, html, IO, etc. It also provides the facility to organize the Dart code
into libraries with proper namespacing. It can be reused by the import statement.

5. Objects
The Dart treats everything as an object. The value which assigns to the variable is an object. The
functions, numbers, and strings are also an object in Dart. All objects inherit from the Object class.

6. Testing

6.1 White Box Testing

It is also called Structural testing or Glass box testing. This method is based on close examination of
procedural details White box testing is the process of giving the input to the system and checking
how the system processes that input to generate the required output. White box testing is considered
as a security testing method that can be used to validate whether code implementation follows
intended design, to validate implemented security functionality, and to uncover exploitable
vulnerabilities.

There are 3 types of White box testing: 38

• Condition Testing
 35

• Loop Testing

• Path Testing

6.1.1 Test Cases and results

A test case is a document, which has a set of test data, preconditions, expected results and post
condition, developed for a particular test scenario in order to verify compliance against a specific
requirement. Test Case acts as the starting point for the test execution, and after applying a set of
input values; the application has a definitive outcome and leaves the system at some end point or
also known as execution post condition.

S. No. Test Case Test Data Expected Actual Status

Outcome Outcome

1 Successful Username: owner Successful Successful PASS

Login Loggedin
Password: owner Login

2 Incorrect Username: owner Email id Email id or PASS

username or password
Password: owner
password didn’t match
doesn’t
matched

3 Incorrect Username: owner Email id Email id or PASS

Password or password
Password: owner
password doesn’t
doesn’t matched
match

4 Successful Username: owner Successful Successfully PASS

Logout Logout Logged Out
Password: owner

6.2 Black Box Testing

 36

It is also called behavioral testing. This method focuses on the functional requirements of the
software. Test cases are derived that fully exercise all functional requirements. Black box testing is
testing software based on output requirements and without any knowledge of the internal structure or
coding in the program. This testing uncovers errors like incorrect or missing functions, Interface
errors, performance errors, errors in data structures, initialization or termination errors.

7. Future Scope and Limitations.

● Will have personalized notifications

● Payment gateway will be added

8. Conclusion

Clubs and organizations are a big part of college life. All students should be strongly encouraged to
pursue club and organizational membership opportunities to help them enrich their personal and
professional skills.

That can be achieved by taking active participation in the relevant field in which students are
interested. Also enhances their career networking opportunities. It will be easy for event organizing
committees to reach the participants effectively.

This document aims to provide the readers and users information about the system and its functions
and specifications. It will explain the purpose and features of the application, the interfaces of the
application, what the application will do, the constraints under which it must operate and how the
application will work.

This software is designed to organize the college events like campaigns, club activities, club
recruitments etc. According to the user’s requirement they can allow push notification.

The software will be a new independent product. It is intended for the event organizing committees
and other concerned users who want to participate. The product will import its database from
firebase with its integrated development environment.
 37

This information can only be accessed by the staff members and the manager/supervisor aside from
the developers. All the forms used in the product follow a clear and logical structure. Errors will be
minimized through the use of bottom navigation bar and command buttons to eliminate the excessive
use of text input. Management of data includes filtering events date wise, creating events.

9. Reference

1. https://flutter.dev

2. https://firebase.google.com/docs/buildfirebase

3. https://docs.flutter.dev/get-started/

4. https://firebase.google.com/docs/flutter/setup?platform=ios

5. https://youtu.be/9XMt2hChbRo

6. https://youtu.be/x0uinJvhNxI

7. https://lucid.app/documents#/dashboard