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

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

Add unit tests for all implemented methods.

• Create MusicAlbum class in a separate .rb file.
• Create Genre class with an association to the Item class (in a separate .rb file).
• All MusicAlbum class properties visible in the diagram should be defined and set up in the constructor method.
• All Genre class properties visible in the diagram should be defined and set up in the constructor method.

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

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

• add_item method in the Genre 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)
• can_be_archived?() in the MusicAlbum class
  should override the method from the parent class
  should return true if parent's method returns true AND if on_spotify equals true
  otherwise, it should return false

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

• Create a Game class in a separate .rb file.
• Create an Author class with an association to the Item class (in a separate .rb file).
• All Game class properties visible in the diagram should be defined and set up in the constructor method.
• All Author class properties visible in the diagram should be defined and set up in the constructor method.

• Link to Github project: https://github.com/sumon766/my-things/projects/1
• There are only 2 members in our group
• sumon766 has been assigned the tasks of Team Member 1 and dieum512 has been assigned the tasks of Team member 2. Also, as we have only 2 members in our group, we have equally divided the tasks of team member 3 to contribute equally and collaboratively.

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.

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

• Create a Game class in a separate .rb file.
• Create an Author class with an association to the Item class (in a separate .rb file).
• All Game class properties visible in the diagram should be defined and set up in the constructor method.
• All Author class properties visible in the diagram should be defined and set up in the constructor method.

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

All data should be preserved by saving collections in .json files.

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

All data should be preserved by saving collections in .json files.

Add unit tests for all implemented methods

• 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)

• 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 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.
• Add all methods visible in the diagram.

• can_be_archived?() in the Item class should return true if published_date is older than 10 years otherwise, it should return false
• 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 false

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

The following options should be available:
List of games
List all authors (e.g. 'Stephen King')
Add a game

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

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

Present the user with a list of options to perform.
Let users choose an option.
If needed, ask for parameters for the option.
Have a way to quit the app.

All data should be preserved by saving collections in .json files.

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

• The following options should be available:
  List all music albums
  List all genres (e.g 'Comedy', 'Thriller')
  Add a music album

• Implement startup actions:
  Present the user with a list of options to perform.
  Let users choose an option.
  If needed, ask for parameters for the option.
  Have a way to quit the app.

• 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).
• 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.

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

Add unit tests for all implemented methods.