Skip to content

radkinz/searching-for-satisfaction

Repository files navigation

SEARCHING-FOR-STATISFACTION

HSE Final Project by Ruby, Jack Dev., Jack Doz., and Liam

ORIGINAL PLAN

Description:

Our product, Searching for Satisfaction (or Lyric Search), allows people to discover music that best caters to their desires and musical tastes. All data will derive from the database millionsongdataset.com/musixmatch/ and will match with the user’s inputted wants. Our project will index lyrics to allow a user to search based on select inputs to be interpreted by our program. We will take, as our minimum viable product, a few words to match the “vibe” (or lyrics) of a specific song. Lyrics will be stemmed, as to make searching (in regards to tenses) more seamless.

Common nouns:

“Listener” or “User”: a person who uses software derived from this project. “Song” or “Lyrics”: content derived from the Million Song Dataset. “Input”: a strand of words to connect wants with products.

Functional Requirements:

  • It should run without large-scale errors.
  • It should take in multiple user inputs, which it can use to search.
  • It should provide the user with a song that aptly matches their inputs.
  • It should utilize the inputs to search the index.
  • It should count the number of times that a page has been visited.
  • It should have a ranking algorithm, which can help a user determine which song might be most appropriate for their desired vibe.
  • It could be able to have search filters such as “exact phrasing,” which looks through the index for the exact line that has been searched.
  • It could include a video/ audio that is associated with the song on its “page.”

Non-Functional Requirements:

  • It should satisfy the user.
  • The UI should be easy to understand.
  • The product should be easily accessible.

OUTCOME AND REFLECTION

Functional Requirements:

  • It should run without large-scale errors.
  • It should take in multiple user inputs, which it can use to search.
  • It should provide the user with a song that aptly matches their inputs.
  • It should utilize the inputs to search the index.
  • It should count the number of times that a page has been visited.
  • It should have a ranking algorithm, which can help a user determine which song might be most appropriate for their desired vibe.
  • It could be able to have search filters such as “exact phrasing,” which looks through the index for the exact line that has been searched.
  • It could include a video/ audio that is associated with the song on its “page.”

Non-Functional Requirements:

  • It should satisfy the user.
  • The UI should be easy to understand.
  • The product should be easily accessible.

Reflection

These past three weeks have been an enjoyable, informative time. Throughout the process, the entire Searching for Satisfaction team has had a chance to test their respective CS skills leading into the end of the academic quarter. In the beginning, we had very ambitious plans and were able to meet most of our goals. Some additions that were not defined in the descriptions.

About

A search engine that gives you songs!

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published