AI PROJECT LOGBOOK

Resource for Students

(Adapted from “IBM EdTech Youth Challenge – Project Logbook” developed by IBM
in collaboration with Macquarie University, Australia and Australian Museum)

KEY PARTNERS

INDIA IMPLEMENTATION PARTNERS

GLOBAL PARTNERS

1
 AI Project Logbook

PROJECT NAME: TICKET ALARM

SCHOOL NAME: KOLA PERUMAL CHETTY VAISHNAV SSS

YEAR/CLASS: 2023-2024 (12th)

TEACHER NAME: Murugan@Prakasam.S

TEACHER EMAIL: Muruganprakasam181@kpcvs.co.in

TEAM MEMBER NAMES AND GRADES:

1. THARUN.A (TEAM LEADER)

2. KAMALESH.M

3. VIVAAS.S

4. SANTHOSH KUMAR.A.L

5. VISHALMANIKANDAN.P

2
 Introduction
Introducing a ticket alarm using AI is an interesting project that involves leveraging artificial intelligence
techniques to monitor and notify users about the availability of tickets for events, flights, or any other time-
sensitive bookings. Explain the overall purpose and goals of the project.

"The Ticket Alarm using AI project aims to streamline the ticket booking process by employing artificial
intelligence to monitor and notify users about the availability of tickets for various events, flights, or other time-
sensitive bookings. The system will provide a proactive solution for users to secure tickets promptly."

2.Team Roles
2.1 Who is in your team and what are their roles?

Role Role description Team Member

Name

 Schedules and allocates tasks among the

team
 Ensures tasks are completed on time
Project Leader  Acts as the point of contact between the
team and the teacher, users and
stakeholders
 Resolves team issues Tharun

 Works with the team and the user to create

Designer a process flow for the new user experience
 Plans the user interface for the prototype

 Collects questions from the team that need

Information Researcher
answers
 Identifies where answers can be located
(source)
 Searches for answers, writes up a report and
passes information to the project reporter

Kamalesh

 Decides on type of data needed to train an

Data expert AI model
 Collects data
 Ensures data is ethically sourced and unfair
bias is eliminated
 Works with prototype builder to train the
AI model

3
  Works with data expert to train/teach
computer
Prototype builder/coder  Creates the prototype and codes if
necessary

Vivaas
 Works with users to tests the prototype Gets
Tester feedback from users and user sign-off when
they prototype has met user requirements
Creates an action plan on what needs to be
fixed and prioritizes requests for future
improvements

 Films the activities of the team and edits

Video Producer these into a presentation for submission Santhoshkumar

 Collates the team Project Logbook

Communication leader submission and creates the content for the Vishalmanikandan
video pitch Selects spokespeople within the
team for various matters relating to the
project.

4
 2.2 Project plan

The following table is a guide for your project plan. You may use this or create your own version using
a spreadsheet which you can paste into this section. You can expand the ‘Notes’section to add reminders,
things that you need to follow up on, problems that need to be fixedurgently, etc.

Phase Task Planned Planned Planned Actual Actual Actual Who is Notes/Remarks
start date end date duration start end date duration responsible
(hours, date (hours,
minutes) minutes)
Preparing for Coursework,
the project readings 1-8-23 7-8-23 5 hrs 1-8-23 7-8-23 3 hrs Prototype builder
Set up a
team folder Project leader
on a shared 7-8-23 7-8-23 10 min 7-8-23 7-8-23 10 min
drive

Defining the Background Project leader

problem reading 13-8-23 14-8-23 2 hrs 14-8-23 15-8-23 2.5 hrs
Research ` Information
issues in our 15-8-23 17-8-23 6 hrs 15-8-23 18-8-23 8 hrs researcher
community
Team
meeting to
discuss
issues and 18-8-23 20-8-23 5hrs 18-8-23 20-8-23 4hrs Project leader
select an
issue for the
project
Complete
section 3 of 20-8-23 16-8-23 3 hrs 20-8-23 16-8-23 2hrs Information
the Project researcher
Logbook
Rate
yourselves
Understanding Identify users Prototype builder
the users 17-8-23 17-8-23 1 hr 17-8-23 17-8-23 1 hr
Meeting with Communication
users to 24-8-23 25-8-23 2 hrs 24-8-23 25-8-23 2.5 hrs leader
observe Prototype builder
them
Interview Communication
with user (1) 26-8-23 27-8-23 2 hrs 26-8-23 27-8-23 2 hrs leader
Interview Video producer
with user (2), 28-8-23 29-8-23 2 hrs 28-8-23 29-8-23 2.5 hrs
etc…
Complete
section 4 of Information
the Project 30-8-23 24-8-23 4 hrs 30-8-23 24-8-23 3.5 hrs researcher
Logbook
Rate
yourselves
Brainstorming Team
meeting to
generate 25-8-23 07-9-23 15 hrs 25-8-23 07-9-23 13 hrs Project leader
ideas for a
solution
Complete
section 5 of 08-9-23 31-8-23 3 hrs 08-9-23 31-8-23 3.5 hrs Communication
the Project leader
Logbook
Rate
yourselves
Designing Team
your solution meeting to 01-9-23 17-9-23 10 hrs 11-9-23 18-9-23 11 hrs Project leader
design the
solution
Complete
section 6 of 18-9-23 09-9-23 2 hrs 09-9-23 10-9-23 2.5hrs Video producer
the logbook
Rate
yourselves
5
Collecting and Team
preparing data meeting to 10-9-23 16-9-23 8 hrs 10-9-23 16-9-23 9 hrs Video producer
discuss data
requirements
Collecting and Data
preparing data collection 17-9-23 30-9-23 5 hrs 17-9-23 30-9-23 4.5 hrs Prototype builder
Prototyping

Data
preparation 01-10-23 03-10-23 3 hrs 01-10-23 03-10-23 3.5 hrs Communication
and labelling leader
Complete
Section 6 of Communication
the Project 03-10-23 04-10-23 2 hrs 03-10-23 04-10-23 2 hrs leader
Logbook
Team
meeting to
plan 04-10-23 24-9-23 3 hrs 04-10-23 24-9-23 2.5 hrs Project leader
prototyping
phase
Prototyping Train your
Testing model with 25-9-23 24-9-23 3 hrs 25-9-23 08-10-23 2.5 hrs Project leader
input dataset
Test your
model and
keep training
with more data 08-10-23 24-9-23 3 hrs 07-10-23 10-10-23 4 hrs Information
until youthink researcher
your
model is
accurate
Write a
program to
initiate actions
based on the 09-10-23 09-10-23 6 hrs 10-10-23 10-10-23 5.5 hrs Information
result of your researcher
model

Complete Communication
section 8 of 10-10-23 10-10-23 2 hrs 10-10-23 10-10-23 2 hrs leader
the Project
Logbook
Rate Communication
yourselves leader
Team
meeting to 02-10-23 02-10-23 1.5 hrs 02-10-23 02-10-23 1 hrs Prototype builder
discuss
testing plan
Testing Invite users Prototype builder
Creating the to test your 03-10-23 03-10-23 1 hr 03-10-23 03-10-23 1 hr
video prototype
Conduct
testing with 03-10-23 03-10-23 3 hrs 03-10-23 03-10-23 4 hrs
users Communication
leader
Complete
section 9 of
the Project 03-10-23 03-10-23 1.5 hrs 03-10-23 03-10-23 1 hr Video producer
Logbook
Rate
yourselves
Team
meeting to
discuss 09-10-23 09-10-23 1 hr 09-10-23 09-10-23 1 hr Communication
video leader
creation
Write your Prototype builder
script 09-10-23 09-10-23 1 hr 09-10-23 01-10-23 1 hr
Film your Communication
video 09-10-23 09-10-23 2 hrs 09-10-23 09-10-23 2 hrs leader
Edit your Communication
video 10-10-23 10-10-23 1 hr 10-10-23 10-10-23 1 hr leader
Completing Reflect on
the logbook the project 10-10-23 10-10-23 1.5 hrs 10-10-23 10-10-23 1.5 hrs Project leader
with your
team

6
 Complete
sections 10
and 11 of the 10-10-23 10-10-23 2 hrs 10-10-23 10-10-23 2 hrs Video producer
Project
Logbook
Review your
Project 10-10-23 10-10-23 1.5 hrs 10-10-23 10-10-23 2 hrs Information
logbook and researcher
video

Sumit your 14-10-23 14-10-23 1 hr 15-1023 15-10-23 30 mins Project leader

Submission
entries on
IBM

2.3 Communications plan

Will you meet face-to-face, online or a mixture of each to communicate?

 Both online and offline
 How often will you come together to share your progress?
 Thrice in a week (atleast)
 Who will set up online documents and ensure that everyone is contributing?
 Data Analyst and Team Leader
 What tools will you use for communication?
 Google meet / Whatsapp / Gmail / Zoom , etc

2.4 Team meeting minutes (create one for each meeting held)

Meeting 1:

Date of meeting: 31/7/2023

Who attended: Tharun, Kamalesh, Santhosh Kumar,Vishalmanikandan,Vivaas
Who wasn’t able to attend: Nil

Purpose of meeting: preparing the project.

Items discussed:
1. Major issues faced by the users.

Things to do (what, by whom, by when)

1. Collect solutions used now by the users to solve the issue. By Santhosh, by 2/8/23
2. Collect data on currently used technologies to solve the issue. By Vivaas, by 2/8/23

7
Meeting 2:

Date of meeting:16/8/23
Who attended: Tharun, Kamalesh,Santhosh Kumar,Vishalmanikandan, Vivaas
Who wasn’t able to attend: nil

Purpose of meeting: To understand the user

Items discussed:
1. The target users , will they get benefited , if yes in what way.
2. Questions needed to be asked in the interview with the target user.

Things to do (what, by whom, by when)

1. Make a list of questions needed to be asked in the interview with the target user.
By Santhosh kumar, Vivaas

Meeting 3:
Date of meeting: 24/8/23
Who attended: Tharun, Kamalesh, Santhosh Kumar, Vishalmanikandan, Vivaas
Who wasn’t able to attend: Kamalesh, Vivaas

Purpose of meeting: Brainstorming

Items discussed:
1. What are the devices used to monitor the climate how it can be integrated with AI
2. how we can create a AI model with the devices used for climate predict

Things to do (what, by whom, by when)

1. Find the methods used to notify the users , by Santhosh Kumar , by 26/8/22.
2. Create AI model/Ideas for creating the notification/alarm system from the data given by
Santhosh Kumar , by Tharun 26/8/23

Meeting 4:
Date of meeting:1/9/23
Who attended: Tharun, Kamalesh,Santhosh Kumar,Vishalmanikandan,Vivaas
Who wasn’t able to attend: Nil

Purpose of meeting: To design solution.

Items discussed:
1. types of prototype used for ticket alarm app

Things to do (what, by whom, by when)

1. Give a basic design of the app to by Tharun, By Kamalesh , By 2/9/23

8
 Meeting 5:

Date of meeting: 20/9/23

Who attended: : Tharun, Kamalesh,Santhosh Kumar,Vishalmanikandan,Vivaas
Who wasn’t able to attend: nil

Purpose of meeting: To collect and prepare data.

Items discussed:
1.over view the project

Things to do (what, by whom, by when)

1. editing work done by Vivaas

Meeting 6:

Date of meeting: 25/9/23

Who attended: : Tharun, Kamalesh,Santhosh Kumar,Vishalmanikandan,Vivaas
Who wasn’t able to attend: nil

Purpose of meeting: Prototype testing

Items discussed:
1.over view the project

Train app and keep training -designer,

prototype tester

1. editing work done by Vivaas

9
3.Problem Definition
3.1 List important local issues faced by your school or community

 Users often encounter frustration when tickets for a popular event or travel are limited,
leading to quick sell-outs

 Technical issues such as website crashes or slow loading times can hinder the
reservation process.

 Users may miss notifications about ticket availability due to various reasons.

 Users may struggle to find assistance when facing issues or have questions during the
reservation process

3.2 Which issues matter to you and why?

I. Missed notifications as users are unaware of the ticket availability –

Users who haven't completed the registration process or provided accurate contact information
may not receive notifications

II. Limited customer support. Users struggle to find assistance for their queries
If customer support operates within restricted hours, users in different time zones or those with
urgent issues outside regular hours may find it challenging to get timely assistance

III. Reservation confirmation delays. Users may experience delays in receiving confirmation of their
reservations.
Delays may occur in sending confirmation emails if there are issues with the email delivery
system, such as server outages, spam filters, or email routing problems.

IV. Slow response time

Compatibility issues with certain browsers or devices may cause slow response times.

3.3 Which issue will you focus on?

 Notifying the users

 Ensuring availability of tickets

10
4.The Users
4.1 Who are the users and how are they affected by the problem?

User – travelers, event enthusiasts, conference attendees, leisure travelers

not receiving notifications about ticket availability affects users by limiting their choices,
causing stress, introducing uncertainty, and potentially leading to missed opportunities.
Providing an efficient and proactive notification system can enhance user satisfaction and
contribute to a positive overall experience with the ticket reservation platform.

4.2 What have you actually observed about the users and how the
problem affects them?

1. Event enthusiasts
Event enthusiasts often plan their schedules, travel arrangements, and accommodations well
in advance. Not receiving timely notifications on ticket availability disrupts their planning
process and makes it challenging to coordinate attendance.

2. Travelers

Individuals planning to book tickets for flights, trains, buses, or other modes of
transportation. Not receiving timely notifications can disrupt travelers' plans, especially if
they have already made arrangements for accommodations, activities, or connecting
flights based on specific travel times.

3. Conference attendees
Conferences often have multiple sessions or workshops, and attendees may need to register
or secure tickets for specific sessions. Not being notified about ticket availability can result in
attendees missing out on the opportunity to attend popular or limited-capacity sessions.

4. Leisure travelers

People looking to book tickets for leisure activities, such as theme parks, tourist
attractions, or recreational events. Travelers often plan trips around special events,
festivals, or seasonal attractions. Lack of notification on ticket availability may prevent
them from participating in these events, limiting their overall travel experience.

11
4.3 Record your interview questions here as well as responses from users.

Q1. How often users encounter issues with not receiving notifications about ticket
availability?
R1: Users may have different preferences for notification channels and frequencies. Some
users may prefer frequent notifications, while others may opt for less frequent updates.

Q2 How important is the timing of notifications for users when it comes to ticket
availability?
R2: Users often want to be notified well in advance of the event or ticket release to have
sufficient time to plan and take action

Q3. Would users prefer to have more control over the frequency and types of notifications
they receive?
R3: Users have diverse preferences, and customization allows them to tailor their
notification experience based on their individual needs and priorities.

Q4. Do you use third-party aggregators or apps to stay informed about ticket availability?
If yes, how satisfied are you with their notification services?
R4: Third-party aggregators offer a convenient way for users to access information from
multiple sources in one place, eliminating the need to visit individual event or ticketing
websites.

Q5. Are there specific features or functionalities you believe would address the issue of
not getting notified about ticket availability?
R5: Provide users with the option to receive notifications through various channels, such
as email, SMS, in-app alerts, and push notifications.

12
4.4 Empathy Map
Map what the users say, think, do and feel about the problem in this table
What our users are saying
 Users may express frustration about
missing out on ticket opportunities due
to not receiving timely notifications
 Users might be confused about the
reasons for not receiving notifications
and may seek clarity on whether it's a
technical issue, a platform limitation, or
a user-specific setting.
 Users may express a desire for the
ticketing platform to improve its
notification system.
 Users may offer suggestions on how the
platform can enhance its notification
features, such as introducing new
notification channels, improving
customization options, or optimizing the
timing of alerts.
What our users are doing
 Users may first check the notification
settings within the ticketing platform to
ensure that they have opted in to
receive alerts.
 If the issue persists, users might reach
out to the customer support team of the
ticketing platform
 Users may search for troubleshooting
guides or FAQs provided by the
ticketing platform.
What our users thinking
 Users may express concerns about
missing out on tickets for events they
were interested in.
 Users might question the reliability of
the ticketing platform, wondering
whether the notification system is
effective and trustworthy
 Users may express a desire for the
ticketing platform to improve its
communication channels.
 Users might think about the importance
of personalized notifications tailored to
their preferences.
How our users feel
 A satisfactory solution to ticket
availability issues can positively shape
users' perception of the event, organizer,
or platform. Users are more likely to
view the resolution process as a sign of
professionalism and customer-
centricity.
 With the availability issue resolved,
users are likely to feel eager to proceed
with their plans, whether it involves
purchasing tickets, making travel
arrangements, or participating in the
event.
 A prompt and satisfactory resolution
can enhance users' trust in the event
organizers or the ticketing platform.
13
4.5 What are the usual steps that users currently take related to the
problem and where are the difficulties?

Manually Checking Event Websites:

 Many users regularly visit the official websites of events, airlines, or other ticket
providers to manually check for updates on ticket availability. They navigate
through event calendars, flight schedules, or other booking platforms.

Email Subscriptions:

 Users often subscribe to newsletters, mailing lists, or notifications through the

official websites or platforms. They provide their email addresses to receive
updates on upcoming events, promotions, or ticket availability.

Mobile Apps:

 Users may use dedicated mobile apps provided by ticketing platforms, airlines, or
event organizers. These apps often include features for setting preferences,
receiving notifications, and checking real-time updates on ticket availability.

Social Media Monitoring:

 Social media platforms play a significant role in spreading information about

events and ticket availability. Users follow official accounts, event pages, or
hashtags to stay informed about announcements and updates.

Third-Party Aggregator Websites:

 Users may turn to third-party websites or apps that aggregate information from
various sources. These platforms provide a consolidated view of upcoming events,
flights, or activities, allowing users to check availability across multiple providers.

7.

8.

9.

10.

14
5.Brainstorming
5.1 Ideas

How might you use the power of AI/machine learning to solve the users’ problem by increasing
their knowledge or improving their skills?

AI Idea #1
User Preference Learning:
 Implement machine learning algorithms to analyse user behaviour, preferences,
and historical interactions with the platform. By understanding individual
preferences, the system can tailor notifications to specific events, genres, or
artists that align with each user's interests.

AI Idea #2 Predictive Analytics:

 Utilize predictive analytics to forecast user preferences for upcoming events. By
analysing patterns in user behaviour and historical data, the system can predict
which events a user is likely to be interested in and send timely notifications.

AI Idea #3 Natural Language Processing (NLP):

 Implement NLP algorithms to analyse user feedback, reviews, and comments
related to ticket availability. This can help the system understand user sentiments,
identify issues, and extract valuable insights for continuous improvement.

AI Idea #4 Dynamic Notification Timing:

 Incorporate AI algorithms to dynamically adjust notification timing based on user
engagement patterns. The system can learn the optimal times to send
notifications, considering factors such as user activity, time zones, and historical
response rates.
.
AI Idea #5 Event Popularity Scoring:
 Develop a scoring system using AI to assess the popularity of upcoming events.
This can help prioritize notifications for high-demand events, ensuring that users
receive timely alerts for tickets that are likely to sell out quickly.

AI Idea #6 Multi-Channel Notification Optimization:

 Use AI to optimize multi-channel notifications (e.g., email, push notifications,
SMS) based on user preferences. The system can learn which channels are most
effective for each user and adjust the delivery strategy accordingly.

AI Idea #7 Enhancing User Experiences through Advanced Technologies

 Implement machine learning algorithms to analyse user behaviour, preferences,
and historical interactions with the platform.
 Utilize predictive analytics to forecast user preferences for upcoming events.
 Implement NLP algorithms to analyse user feedback, reviews, and comments
related to ticket availability.
 Develop a scoring system using AI to assess the popularity of upcoming events.
 Use AI to optimize multi-channel notifications (e.g., email, push notifications,
SMS) based on user preferences.

15
 5.2 Priority Grid

Evaluate your five AI ideas based on value to users and ease of creation and implementation.

High value to users, easy to create High value to users, hard to create

Allow users to create a personalized watchlist of Event Popularity Scoring helps prioritize
events, artists, or genres they are interested in. notifications for events that align with current
Users can easily add or remove items from their trends and user preferences.
watchlist through the platform. Implement a smart Users gain insights into the popularity of events,
notification system that sends timely alerts to users helping them make informed decisions about
based on their watchlist preferences. Notifications ticket availability.
VALUE TO USERS

can be sent when tickets become available, prices Users benefit from receiving notifications through
drop, or when there is high demand for specific their preferred channels, whether it's through
events. mobile apps, email, SMS, or other communication
channels

Low value to users, easy to create Low value to users, hard to create

Poorly implemented dynamic notification timing

may lead to notifications being perceived as
intrusive. Users may feel overwhelmed if
notifications are sent at inappropriate times or too
frequently.
Poorly implemented dynamic notification timing
may lead to notifications being perceived as
intrusive. Users may feel overwhelmed if
notifications are sent at inappropriate times or too
frequently.

16
 5.3 Based on the priority grid, which AI solution is the best fit for your
users and for your team to create and implement?

Briefly summarize the idea for your solution in a few sentences and be sure to identify the toolthat
you will use.

Based on the priority grid, the AI solution that strikes a balance between value to users and
feasibility for implementation is the "Smart Reminder Service." This solution allows users to
create a personalized watchlist, set manual reminders, and receive notifications on ticket
availability. The key features include manual reminder setting, reminder options, multi-channel
reminders, event updates, and integration with calendar apps. The tool utilized for not getting
notified on ticket availability is a simplified recommendation engine and a notification system,
ensuring quick implementation and user adoption. This solution provides immediate value to
users while being relatively easy to create, making it a practical choice for both users and the
development team. Also, "Notification Reminder Service" appears to be the best fit for users
not getting notified on ticket availability. This solution allows users to manually set reminders
for specific events, choose their preferred notification channels, and receive updates on ticket
availability. The implementation involves a simple reminder setting interface, a basic
notification system, and integration with calendar APIs. This solution prioritizes quick
adoption, user empowerment, and minimal learning curve, making it a practical choice for both
users and the development team.

17
6.Design

6.1 What are the steps that users will now do using your AI solution
to address the problem?

 Access the Platform:

o Log in to the ticketing platform or application where the Notification
Reminder Service is implemented.
 Navigate to Events:
o Explore the events, genres, or artists they are interested in to find the ones
they want to monitor for ticket availability.
 Set Manual Reminders:
o Use the straightforward reminder setting interface to manually input event
details, including the event name, date, and time.
 Choose Reminder Options:
o Customize their notification preferences by selecting reminder options such
as daily, weekly, or other intervals based on their preferences.
 Select Notification Channels:
o Choose their preferred notification channels (e.g., email, push notification)
where they want to receive reminders.
 Sync with Calendar Apps:
o Optionally, sync their reminders with external calendar applications by
utilizing integration with calendar APIs. This ensures a visual
representation of their schedule.
 Receive Updates:
o Wait for the Notification Reminder Service to send updates and reminders
based on the user-defined settings.
 Adjust Preferences (Optional):
o Modify reminder settings, notification channels, or event details as needed
by accessing the reminder service preferences.
 Monitor Reminders:
o Regularly check their reminders or alerts to stay informed about ticket
availability, price changes, or other updates for the monitored events.
 Take Action:
o Act on the received reminders by purchasing tickets, exploring availability,
or adjusting plans based on the notifications.

18
7. Data
What data will you need to train your AI solution?

 Manual Reminders: Data related to how users manually set reminders,

including the events they choose, frequency preferences, and notification
channels.
 User Feedback: Any feedback provided by users regarding the reminders,
preferences, or overall experience.
 Notification Channel Preferences: Data on users' preferred notification
channels for receiving reminders (e.g., email, push notification).

 Reminder Frequency Preferences: Insights into how often users prefer

to receive reminders (e.g., daily, weekly).

8.Prototype
8.1 Which AI tool(s) will you use to build your prototype?

Pytorch, Natural language toolkit, spaCy

8.2 Which AI tool(s) will you use to build your solution?

Tensorflow, spaCy, Scikit learn, Amazon personalize

19
 8.3 What decisions or outputs will your tool generate and what further
action needs to be taken after a decision is made?

Natural Language Processing (NLP) for Event Extraction:

Decision: Automatically extract event details from unstructured user inputs, such as event
names, dates, and times.
Output: Structured data representing event details for accurate scheduling.
Further Action: Implement error handling mechanisms for cases where NLP may misinterpret
user inputs. Allow users to review and confirm extracted details before finalizing reminders.

Sentiment Analysis for User Feedback:

Decision: Use sentiment analysis to evaluate user feedback regarding the effectiveness and
satisfaction with the notification reminders.
Output: Categorized user feedback as positive, negative, or neutral sentiments.
Further Action: Identify areas of improvement based on sentiment analysis. Address any
negative feedback and implement enhancements to improve user satisfaction.

\ Time Series Analysis for User Engagement Patterns:

Decision: Analyse time series data to identify patterns in user engagement with the notification
reminders over different days and times.
Output: Insights into peak engagement periods and user responsiveness.
Further Action: Schedule notifications during peak engagement times. Continuously analyse
time series data to adapt notification schedules based on evolving user behaviour.
.

9.Testing
9.1 Who are the users who tested the prototype?

 Ride-Sharing users
 Travellers
 Public transit users
 Event attendees

20
9.2 List your observations of your users as they tested your solution.

Satisfied attendees are more likely to share their positive experiences, contributing to word-
of-mouth promotion for future events.

Observations from user behavior during ticket availability notifications can provide valuable
data for future event planning, helping organizers understand user preferences and optimize
their strategies.

A well-implemented notification system contributes to a positive brand perception,

demonstrating that the event organizers value their attendees' time and interest.

Usability: User friendly app, Quick Ticket Access, Real-Time Updates, In-App Guidance.

Effectiveness: Accuracy of Information, Personalization and User Preferences, Multi-Channel

Notification Optimization

Satisfaction: Ease of Use, additional features, customization options.

9.3 Complete the user feedback grid

What works? What needs to change?

Smooth and easy navigation. Some users report issues with push notifications.

Timely notifications aligned with user preferences. More clarity needed on how third-party data is used.

Flexible options for setting and modifying reminders. Occasional slowdowns during peak usage times.

Seamless integration with external calendars. Improved error messages needed for better guidance.

Personalized event recommendations are helpful.

Questions Ideas

How do I set up a new reminder? Provide a step-by-step tutorial or a guided tour for
new users to easily understand the process of
Is my data secure? creating reminders.

What types of notifications can I receive? Include a detailed privacy policy and security
measures on the platform. Consider using
encryption for sensitive user data.

Offer a variety of notification options (email, push

notifications) and allow users to customize their
preferences based on event types.

21
9.4 Refining the prototype: Based on user testing, what needs to be acted on
now so that the prototype can be used?

 Update on Notification Timing Optimization.

 Update on all algorithms to give more faster and accurate results.

 Checking all the technical issues that were found during the testing by the users and see
to that the prototype is ready to use.

9.5 What improvements can be made later?

 We can develop more app.

 We can provide in world wide.
 And can be accessible at any situation.
 Easy to handle.
 Another development can be made in the classification part. We can use better
classification algorithms to speed up the process and improve the accuracy.

Rate yourself

Testing

point – A concept for a prototype shows how it will be tested.

points - A prototype has been tested with users and improvements have been identified to meet
user requirements.
points - A prototype has been tested with a fair representation of users and all tasks in this section
have been completed.

22
10.Team collaboration
10.1 How did you actively work with others in your team and with stakeholders?

• Clear and effective communication is key to working effectively

as a team. We made sure to keep our team members and
stakeholders informed about the progress of the project and any
challenges or issues that arise.
• We encourage collaboration and idea-sharing within the team. By
working together and sharing different perspectives, we generated
new ideas and solutions that can improve the device.
• We regularly seeked feedback from team members and
stakeholders to get their input and ideas on the project. This can
help to ensure that the device meets the needs and expectations of
all stakeholders.
• We made sure to delegate tasks and responsibilities to team
members based on their strengths and expertise. This can help to
ensure that everyone is able to contribute effectively to the
project.
• We addressed any conflicts or issues that arise within the team
promptly and effectively to keep the project on track.

Rate yourself

Team collaboration

point – There is some evidence of team interactions among peers and stakeholders.
points - Team collaboration among peers and stakeholders is clearly documented in this section.
3 points - Effective team collaboration and communication among peers and stakeholders is clearly
documented in this section.

23
11.Individual learning reflection
11.1. Team Reflections

A good way to identify what you have learned is to ask yourself what surprised you during the
project. List the things that surprised you and any other thoughts you might have on issues in
your local community.

Kamalesh (Information researcher):

•One of the biggest challenges we faced was getting the accurate reach time and availability of
tickets and notifying it to users. We spent a lot of time testing and adjusting the algorithm and
eventually we were able to get them to work reliably

•One of the things that we learned during the project is that it's important to be flexible and
open to change. There were a few times when we had to pivot our approach or make changes to
the design, and being able to adapt quickly helped us to stay on track

Vishalmanikandan (Communication leader):

•I was really impressed by how we all did the project, We were able share our perspective for
problems and find solutions easily.

•While recording the video for the presentation , I saw how well the project came out and how
are public transit users affected and how can they be helped

Vivaas (Prototype builder):

•One of the things we learned during the project is that it's important to get user feedback early
on. We made a few design choices that we later realized were not ideal, and getting user
feedback earlier could have saved us some time.

•One of the things that I think we did well as a team was staying organized and on track. We
used project management software and had regular team meetings to stay updated on the
progress of the project.

24
Santhosh Kumar (Video producer):

•One of the things I enjoyed most about working on this project was the opportunity to learn
new skills and technologies.

•We ended up making some changes that helped to the public transit users but it was still an
area that we could improve on.

Tharun (Project leader):

•I was really impressed with how well our team worked together. We were able to divide the
work effectively and everyone contributed valuable ideas and insights.

•One of the things that I appreciated about working on this project is that we were able to
involve users in the design process. Their feedback and insights were really valuable and
helped us to create a device that was more user-friendly and effective.

25
12.Video link

Enter the URL of your team

video:Enter the password (if any):

26
Appendix
Recommended Assessment Rubric (for Teachers)
LOGBOOK AND VIDEO CONTENT
Steps 3 points
Problem A local problem which has not
definition been fully solved before is
explained in detail with
supporting research.
The Users Understanding of the user group
is evidenced by completion of all
of the steps in Section 4 The
Users and thorough
investigation.
Brainstorming A brainstorming session was
conducted using creative and
critical thinking. A compelling
solution was selected with
supporting arguments from
Section 5 Brainstorming.
Design The use of AI is a good fit for the
solution. The new user
experience is clearly
documented showing how users
will be better served than they
are today.
Data Relevant data to train the AI
model have been identified as
well as how the data will be
sourced or collected. There is
evidence that the dataset is
balanced, and that safety and
privacy have been considered.
Prototype A prototype for the solution has
been created and successfully
trained to meet users’
requirements.
Testing A prototype has been tested
with a fair representation of
users and all tasks in Section 9
Testing have been completed.
Team Effective team collaboration and
collaboration communication among peers
and stakeholders is clearly
documented in Section 10 Team
collaboration.
Individual Each team member presents a
learning reflective and insightful account
of their learning during the
project.
Total points
2 points
A local problem which has not
been fully solved before is
described.
Understanding of the user
group is evidenced by
completion of most of the
steps in Section 4 The Users.
A brainstorming session was
conducted using creative and
critical thinking. A solution was
selected with supporting
arguments in Section 5
Brainstorming.
The use of AI is a good fit for
the solution and there is some
documentation about how it
meets the needs of users.
Relevant data to train the AI
model have been identified as
well as how the data will be
sourced or collected. There is
evidence that the dataset is
balanced.
A prototype for the solution
has been created and trained.
A prototype has been tested
with users and improvements
have been identified to meet
user requirements.
Team collaboration among
peers and stakeholders is
clearly documented in Section
10 Team collaboration.
Each team presents an
account of their learning
during the project.
1 point Points
Given
A local problem is
described
The user group is
described but it is unclear
how they are affected by
the problem.
A brainstorming session
was conducted. A solution
was selected.
The use of AI is a good fit
for the solution.
Relevant data to train the
AI model have been
identified as well as how
the data will be sourced or
collected.
A concept for a prototype
shows how the AI model
will work
A concept for a prototype
shows how it will be
tested.
There is some evidence of
team interactions among
peers and stakeholders.
Some team members
present an account of their
learning during the project.
27
VIDEO PRESENTATION
Points Given
3 – excellent
Criteria 2 – very good
1 – satisfactory

Communication The video is well-paced and communicated, following a clear

and logical sequence.

Demonstrations and/or visuals are used to illustrate

Illustrative
examples, where appropriate.

Accurate The video presents accurate science and technology and

language uses appropriate language.

The video demonstrates passion from team members about

Passion
their chosen topic/idea.

Sound and
image quality
The video demonstrates good sound and image quality.

The content is presented in the video within a 3-minute

Length
timeframe.

Total points

28
SUPPORT DOCUMENT

29
 SUPPORT DOCUMENT

Stages in a project lifecycle model,

1. Problem Scoping
2. Data acquisition
3. Data exploration
4. Modelling (Design, prototype)
5. Evaluation (Testing)

Problem Scoping
Problem scoping refers to understanding a problem , finding out various factors which affect
the problems , define the goal and aim of the project.

Major problems faced by users:

Missed Opportunities:
Users may miss out on important opportunities if they are not promptly notified about ticket availability. This
could be especially critical for time-sensitive events or limited-seat scenarios.

Decreased User Satisfaction:

Users who do not receive timely notifications may experience frustration and decreased satisfaction with the
ticketing system. This could impact their overall perception of the service.

30
Inefficient Planning:
Without timely notifications, users may struggle to plan and organize their schedules effectively. This can be
particularly problematic for events or activities that require advance planning.

Loss of Revenue:
In cases where tickets are associated with revenue generation, such as in the case of ticket sales for events, the
organization may face financial losses if users are not notified and, as a result, do not purchase tickets.

Negative Impact on Event Attendance:

Events may experience lower attendance if potential attendees are not aware of ticket availability. This can
affect the atmosphere of the event and, in some cases, the success of the event itself.

Reputation Damage:
Users who consistently experience issues with not receiving notifications may share their negative experiences,
leading to reputation damage for the ticketing system or the organization hosting the events.

Increased Support Requests:

Users who are not receiving notifications may contact customer support or helpdesk services more frequently,
creating an additional workload for support teams and potentially leading to dissatisfaction among users.

Trust Issues:
Lack of reliable notifications can erode user trust in the ticketing system. Users may question the system's
reliability and may be hesitant to use it for future events or purchases.

Confusion and Uncertainty:

Users may become confused and uncertain about the status of their ticket availability if they do not receive
notifications. This lack of clarity can lead to a less-than-optimal user experience.

31
To understand more about the problem 4'W canvas is followed,
Who? What? Where? Why?

WHO:
The travelers, event enthusiasts, conference attendees, leisure travelers are the ones who are mostly affected by
these factors.

WHAT:
The problem is the difficulty of determining the accurate availability of tickets, Users might be confused about
the reasons for not receiving notifications and may seek clarity on whether it's a technical issue, a platform
limitation, or a user-specific setting.

WHERE:
The problem can arise in any location where users planning to travel are not able to proceed due to the
insufficient information of ticket details.

WHY:
It offers a convenient and effective solution for users to plan their bookings according to the ticket availability.

32
Data Acquisition
Data Acquisition is the process of collecting accurate and reliable data to work with. Data can be in the format
of text, video, images, audio and so on and it can be collected from various source like the interest, journals,
newspapers.
To make the Al model to predict the output we need to train it first using data which is relevant and authentic.
The data needs to relevant cause if the data is irrelevant the predicted output will also be wrong.

Data features:

 Event Information:
Include details about the event, such as name, date, time, and venue.

 Ticket Availability:
Provide real-time updates on ticket availability for specific events or flights.

 User Preferences:
Allow users to set preferences for the types of events or tickets they are interested in receiving
notifications for.

 Price Alerts:
Implement a feature to notify users when ticket prices fall within their preferred budget range.

 Location-based Notifications:
Enable location-based notifications to inform users about events in their preferred or nearby
locations.

33
Data Exploration

Data exploration refers to the initial step in data analysis in which data analysts use data visualization and
statistical techniques to describe dataset characterizations, such as size, quantity, and accuracy, in order to
better understand the nature of the data.

Modelling
Modelling is the process in which different models based on the visualized data can be created and even checked
for the advantages and disadvantages of the model.

There are 2 ways to approach an AI Model,

- Rule based approach

- Learning based approach

34
In our project we are using Learning based approach,
A learning-based approach refers to a method of solving a problem by using machine learning algorithms to
automatically learn from data. In this approach, the system is not given a set of explicit rules, but instead, it
uses algorithms to find patterns and relationships within the data that can be used to make predictions or
decisions.

Personalization:
Learning algorithms can analyze user behavior and preferences over time. By understanding individual
preferences, the notification system can personalize alerts, providing users with information about events or
tickets that are more relevant to their interests.

Adaptability:
A learning-based system can adapt to changes in user behavior and preferences. If a user's interests evolve, the
system can dynamically adjust the types of notifications sent, ensuring that users receive information that aligns
with their current preferences.

Optimization:
Learning algorithms can optimize the timing and frequency of notifications based on historical data. For example,
the system can learn the best times to send notifications to maximize user engagement and response rates,
avoiding periods of low user activity.

Prediction and Forecasting:

Machine learning models can be employed to predict ticket availability trends and user demand. This enables the
system to anticipate when certain events or ticket categories are likely to be in high demand, allowing for
proactive notification strategies.

Reducing Notification Fatigue:

Learning-based approaches can help in avoiding notification overload for users. By understanding user behavior,
the system can avoid sending excessive or irrelevant notifications, which helps prevent user fatigue and
annoyance.

35
Feedback Loop:
Learning systems can incorporate user feedback to continuously improve the notification process. If users provide
feedback on the relevance or timing of notifications, the system can use this information to refine its algorithms
and enhance the overall user experience.

Enhanced User Engagement:

By providing users with timely and relevant information, a learning-based notification system can increase user
engagement. Users are more likely to appreciate and respond positively to notifications that align with their
interests and preferences.

Improved Customer Satisfaction:

A learning-based approach can contribute to overall customer satisfaction by delivering a more personalized and
efficient notification experience. Satisfied customers are more likely to continue using the platform and
recommend it to others.

Evaluation
Evaluation is the method of understanding the reliability of an API Evaluation and is based on the outputs
which is received by the feeding the data into the model and comparing the output with the actual answers.
Once we Model is trained, we proceed to testing stage so that we can calculate the accuracy of efficiency and
performance of the model.

Testing:
Its techniques include the process of executing a program or application with the intent of finding failures, and
verifying that the model (product) is fit for use. While testing the Ai model we came across few errors which
we resolved by adding few more rules to the model.

Validation:
Validation is the process of establishing documentary evidence demonstrating that a procedure, process, or
activity carried out in testing and then production maintains the desired level of compliance at all stages.

36
 BIBLIOGRAPHY

Artificial Intelligence - CBSE Al Hand Book

Artificial Intelligence - CBSE Al Log Book & Log Book Guide

Artificial Intelligence - Goyal Brothers Prakashan Book.

Informatics Practices with Python - Preeti Arora.

Computer Science with Python - Sumitha Arora.

Computer Science with Python - Preeti Arora.

ulttps://in.coursera.org/

37