Item Class

• Create an 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

Implement UI

• The following options should be available:
  • List of games
  • List all authors (e.g. 'Stephen King')
  • Add a game
• All data should be preserved by saving collections in .json files.

For this Kanban board we accomplish the changes below:

• Linke for the GitHub project: https://github.com/adel-gu/Catalog-of-my-thingshttps://github.com/adel-gu/Catalog-of-my-things
• There are 04 members assigned to this project.
• Team member 1: @Baayeh
• Team member 2: @adel-gu
• Team member 3 @RichardChileya
• Team member 4 @j-tee

Movie Class

• Create Movie class in a separate .rb file.
• All Movie class properties visible in the diagram should be defined and set up in the constructor method.
• Implement methods:
  • can_be_archived?() in the Movie class
    • should override the method from the parent class
    • should return true if parent's method returns true OR if silent equals true
    • otherwise, it should return false
• Add unit tests for all implemented methods.

Implement UI

• The following options should be available:
  • List all music albums
  • List all genres (e.g 'Comedy', 'Thriller')
  • Add a music album
• All data should be preserved by saving collections in .json files.

Database Schema

• Create a schema.sql file with 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

Database Schema

• 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

Database Schema

• 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

Database Schema

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

Game class

• 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.
• Implement methods:
  • can_be_archived?() in the Game class
    • should override the method from the parent class
    • should return true if parent's method returns true AND if last_played_at is older than 2 years
    • otherwise, it should return false
• Add unit tests for all implemented methods.

App Entry point

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

Source Class

• Create a Source class with an association to the Item class (in a separate .rb file).
• All Source class properties visible in the diagram should be defined and set up in the constructor method.
• Implement methods:
  • add_item method in the Source 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)
• Add unit tests for all implemented methods.

Label Class

• Create a Label class with an association to the Item class (in a separate .rb file).
• All Label class properties visible in the diagram should be defined and set up in the constructor method.
• 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)
• Add unit tests for all implemented methods.

Book Class

• Create a book class in a separate .rb file.
• All Book class properties visible in the diagram should be defined and set up in the constructor method.
• Implement methods:
  • 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 "bad"
    • otherwise, it should return false
• Add unit tests for all implemented methods.

Implement UI

• The following options should be available:
  • List all movies
  • List all sources (e.g. 'From a friend', 'Online shop')
  • Add a movie
• All data should be preserved by saving collections in .json files.

MusicAlbum class

• Create MusicAlbum class in a separate .rb file.
• All MusicAlbum class properties visible in the diagram should be defined and set up in the constructor method.
• Implement methods:
  • 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
• Add unit tests for all implemented methods.

Genre Class

• Create 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.
• 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)
• Add unit tests for all implemented methods.

Implement UI

• The following options should be available:
  • List all books
  • List all labels (e.g. 'Gift', 'New')
  • Add a book
• All data should be preserved by saving collections in .json files.

Code Refactor and Documentation

• Implement SOLID principles
• Improve User Interface
• Update README file
• Record a video presenting the features of the project you built. It is a video with a maximum length of 5 minutes. The content of the video should include:
  • A description of the project.
  • A demo of the project features.
  • You should also highlight some interesting piece of code or something you built that you are very proud of.
  • You all should appear in the video and talk about the project.

Author Class

• Create an Author class with an association to the Item class (in a separate .rb file).
• All Author class properties visible in the diagram should be defined and set up in the constructor method.
• Implement methods:
  • add_item method in the Author 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)
• Add unit tests for all implemented methods.