Here it is

Should include tables that will be analogical to the structure of the classes that you created:

• music_albums table (add all properties and associations from the parent Item class as table columns)
• genres table

Should include 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

Should include 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

• 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

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)

• 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

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

• Add unit tests for all implemented methods.

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

https://github.com/devMunyi/catalog-of-my-things/projects/1

Team Members are:

• @devMunyi: assigned tasks labeled Team member #1
• @Zuhaib042: assigned tasks labeled Team member #2
• @kene-creator: assigned tasks labeled Team member #3

• Implement 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 a Book class in a separate .rb file.

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

• Create a Game class in a separate .rb file.

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

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

• Implement methods:
  • 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

• Create MusicAlbum class in a separate .rb file.

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

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

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

• Create a main.rb file that will serve as your console app entry-point.
• 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.

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

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

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 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.
• Implement methods:
  • 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
• Create a main.rb file that will serve as your console app entry-point.
• 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.

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