• Implement the add_item method in the Author class to take an instance of the Item class as input, add it to the collection of items that belong to the author, and add the author as a property of the item object.

• The following options should be available in console:
  List all books
  List all labels (e.g. 'Gift', 'New')
  Add a book

• Create a separate file for unit tests.
• Write tests for the add_item method in the Source class, ensuring it adds items correctly and sets the source as a property of the item.
• Write tests for the can_be_archived? method in the Movie class, covering different scenarios to ensure it returns the correct boolean value.

• Create a new Ruby class called Author in a separate file. This class will represent the authors of the items in your application. The Author class will have an association to the Item class, which means that an author can have many items associated with it.

• Write unit tests for all of the methods that you have implemented in the Game and Author classes. This will help to ensure that your code is working as expected

• Write unit tests for the add_item method in the Genre class and the can_be_archived? method in the MusicAlbum class.

Long Description:

• Create a separate file for unit tests.
• Write tests for the add_item method in the Genre class, ensuring it adds items correctly and sets the genre as a property of the item.
• Write tests for the can_be_archived? method in the MusicAlbum class, covering different scenarios to ensure it returns the correct boolean value.

• Create a new Ruby class called Game in a separate file. This class will represent the game entities in your application

• Implement functionality to save the state of Movie and Source instances in .json files.
• Ensure that the data is correctly written to the .json files and can be read back into the application.
• Test by creating instances, saving them to .json files, and then reading them back into the application.

• can_be_archived?() in the Book class
  should override the method from the parent class
  should return true if parent's method returns true OR if cover_state equals to "bad"
  otherwise, it should return false

• Create a main.rb file that will serve as your console app entry point.
• Implement startup actions:
  a). Present the user with a list of options to perform.
  b). Let users choose an option.
  c). If needed, ask for parameters for the option.
  d). Have a way to quit the app.

• In the source.rb file, implement the add_item method.
• The method should take an instance of the Item class as input.
• Add the input item to the collection of items.
• Set the source instance as a property of the item object.
• Test the method by adding an item and checking if it's added to the collection and if the source is set as a property of the item.

• Write unit tests for all of the methods that you have implemented in the Book and Label classes. This will help to ensure that your code is working as expected.

• In the movie.rb file, override the can_be_archived? method from the parent class.
• The method should return true if the parent's method returns true OR if silent equals true.
• Test the method with different scenarios to ensure it works as expected.

• In the main.rb file, implement the options to list all movies and sources.
• Implement the option to add a movie.
• Test the options by running the console app and selecting the implemented options to ensure they work as expected.

• - Create a separate .rb file for the MusicAlbum class.
• - Define and set up all properties visible in the diagram in the constructor method.

Long description:

• Create a new .rb file named music_album.rb.
• Define the MusicAlbum class.
• Inside the class, declare the properties visible in the diagram.
• Define a constructor method to initialize the properties.
• Test the class by creating an instance and accessing the properties.

• games table (add all properties and associations from the parent Item class as table columns)
  authors table Description: Create a SQL schema file that defines the tables that will be used to store the data for your application. The tables should be analogical to the structure of the Game and Author classes that you created.

• Create a new .rb file named source.rb.
• Define the Source class.
• Inside the class, declare the properties visible in the diagram.
• Define a constructor method to initialize the properties.
• Implement an association to the Item class.
• Test the class by creating an instance and accessing the properties and associations.

• Implement the Game class constructor method to define and set up all of the properties that are visible in the UML class diagram.

• List of games
• List all authors (e.g. 'Stephen King')
• Add a game Description: Implement the following options in your console app:
• A list of all games in the system
• A list of all authors in the system, filtered by name if desired
• An option to add a new game to the system

• 1. Create Item class in a separate .rb file.
  All Item class properties visible in the diagram should be defined and set up in the constructor method. Exception: properties for the 1-to-many relationships should NOT be set in the constructor method. Instead, they should have a custom setter method created.
• 2. Add all methods visible in the diagram.
  Implement methods:
  a). can_be_archived?() in the Item class
  should return true if published_date is older than 10 years.
  otherwise, it should return false
  b). move_to_archive() in the Item class
  should reuse can_be_archived?() method
  should change the archived property to true if the result of the can_be_archived?() method is true
  should do nothing if the result of the can_be_archived?() method is falsetion to be added

• Override the can_be_archived?() method in the Game class to return true if the parent class's method returns true AND if the last_played_at property of the game is older than 2 years. Otherwise, return false.

• Implement functionality to save collections in .json files to preserve data.

Long Description:

• Override the method from the parent class.
• It should return true if the parent's method returns true AND if on_spotify equals true, otherwise, it should return false.

Long Description:

• In the music_album.rb file, override the can_be_archived? method from the parent class.
• The method should return true if the parent's method returns true AND if on_spotify equals true.
• Test the method with different scenarios to ensure it works as expected.

• Create a new .rb file named movie.rb.
• Define the Movie class.
• Inside the class, declare the properties visible in the diagram.
• Define a constructor method to initialize the properties.
• Test the class by creating an instance and accessing the properties.

• Implement a way to save all of the data in your application to JSON files. This will allow you to load the data back into your application later.

• Create a separate .rb file for the Genre class.
• Define and set up all properties visible in the diagram in the constructor method.
• Implement association to the Item class.

Long Description

• Create a new .rb file named genre.rb.
• Define the Genre class.
• Inside the class, declare the properties visible in the diagram.
• Define a constructor method to initialize the properties.
• Implement an association to the Item class.
• Test the class by creating an instance and accessing the properties and associations.

• Implement options to list all music albums and genres, and to add a music album in the main.rb file.

Long description:

• In the main.rb file, implement the options to list all music albums and genres.
• Implement the option to add a music album.
• Test the options by running the console app and selecting the implemented options to ensure they work as expected.

• Create a Book class in a separate .rb file.
• Create a Label class with an association to the Item class (in a separate .rb file).

• Implement the Author class constructor method to define and set up all of the properties that are visible in the UML class diagram

• Create a new file named schema.sql.
• Define the movies and sources tables, including all properties and associations from the parent Item class as table columns.
• Ensure the SQL syntax is correct and the tables can be created in a database.

• Create tables music_albums and genres with all properties and associations from the parent Item class as table columns.

Long description:

• Create a new file named schema.sql.
• Define the music_albums and genres tables, including all properties and associations from the parent Item class as table columns.
• Ensure the SQL syntax is correct and the tables can be created in a database.

• Implement a way to save all of the data in your application to JSON files. This will allow you to load the data back into your application later.

• All Book class properties visible in the diagram should be defined and set up in the constructor method.
• All Label class properties visible in the diagram should be defined and set up in the constructor method.

• The method should take an instance of the Item class as input.
• It should add the input item to the collection of items and add self as a property of the item object.

Long Description

1. Update Professional Readme File.
2. Record a Video of App.

add_item method in the Label class

• should take an instance of the Item class as an input.
• should add the input item to the collection of items
• should add self as a property of the item object (by using the correct setter from the item object)

Here:

• Our kanban board project link.
• We are four people in this project.

1. Team member #1 is @MasumaJaffery
2. Team member #2 is @cancelei
3. Team member #3 is @Grandi0z
4. Team member #4 is @najibullahjafari

• Create a schema.sql file with tables that will be analogical to the structure of the classes that you created:
  1). Books table (add all properties and associations from the
  Parent Item class as table columns) labels table.