Page $2$:

grams of sugar, total carbohydrates, and sweetener $($if any$)$ used in the beverage. The system you are helping with does not keep a record of which beverages are viewed or the searches performed. If a user tries a beverage that is listed in the BB app, they can add it to their $$drink list$.$ A drink list is simply the list of all the tracked beverages that the user has ever tried. When a user adds a beverage to their drink list, the date the beverage is added is also recorded. Users can mark beverages on their drink list as a $$favorite$,$ if they want. Users can connect with each other through the BB app by adding each other as friends. When a user requests to friend another user, the friendship is marked as $$requested$$ in the system. When the other user accepts the request, the friendship is marked as $$confirmed$$ in the system. When friends in the app, the date of the friendship is recorded. Friends in the app can see each other$$s drink lists and favorites. Users can $$friend$$ as many other users of the BB app as they wish, but users are not required to friend anyone. Venues can occasionally sponsor events. Venues are not required to sponsor any events, but some venues sponsor many events each year. The events are tracked in BB$.$ Each event has a name, start date, and end date. Some events have an admission fee associated with them, but some do not. Only events sponsored by venues appear in the BB app. Each event is sponsored by a single venue. Users can see upcoming events within the app. If the user plans to attend the event, they can sign up for the event through the app. The BB app does not handle payments so if the event has an admission fee, payments for the admission fee are not done or tracked within the app. If a user signs up for an event, the date that they sign up is recorded. Users do not always attend the events that they sign up for. If a user attends the event, then they can $$check in$$ at the event when they get there. Checking in at the event is simply indicating in the app that they actually attended the event. A user can, and hopefully will, sign up and attend many different events. An event will hopefully be attended by dozens of users. The event needs to be able to be entered in the system before the users can sign up for it$.$ Some users have never signed up or attended any events. For example, Aziz installs the Beverage Buddy app on his phone and registers as a user. He goes to a tea house named $$Topical Teas$$ after work one day. While there, he looks on BB for a black tea that has fewer than $3$ grams of sugar and fewer than $5$ total carbohydrates that is sold at this tea house. Looking through the results, he decides to try a beverage named $$Cabo Crisp$$ that is brewed by $$World Tea Market$($not to be confused with the $$Cabo Crisp$$ that is a cider brewed by $$Greenhouse Brewers$).$ After he orders with the waiter and the tea is brought to him, Aziz adds Cabo Crisp to his drink list in BB$,$ and marks it as a favorite. While he is drinking his tea, he looks for his friend Kayla on the system by her email address and sends a friend request. Almost immediately, Kayla accepts his request and they are now friends in BB$.$ Looking at Kayla$$s drink list, he sees that she has also tried Cabo Crisp and marked it as one of her favorites. Looking at her drink list, he sees that Kayla has tried over $50$ different drinks. Aziz notes that Kayla also marked the coffee drink named, $$Butter Blend,$$ as one of her favorites. Aziz finds that Butter Blend is not available at $$Tropical Teas$,$ but it is available at $$GrindHows$$ near his work. He can see that GrindHows is sponsoring a free book reading event next Tuesday from $4$pm until $7$pm with $50\%$ off all coffees. Aziz signs up to attend the book reading event. Note: to help protect user privacy, BB does not store data about any searches that users make.