Create a Book 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.

Create App Methods for Game

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

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 the parent's method returns true OR if cover_state equals "bad". Otherwise, it should return false
• Add unit tests for all implemented methods.

Create a schema.sql for Music

• 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

• Add linters and configuration files
• Install external dependencies
• Set up file structure

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.

Define App methods for books

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

Set up and assigned tasks regarding the development of the current project.

We're a team of 3 passionate developers. Our distribution goes like this:

• Team member # 1 @zhadier
• Team member # 2 @JohnFTitor
• Team member # 3 @Sahar-AbdelSamad

You can find a link to the kanban board here

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.

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.

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

Define app methods to efficiently store data in JSON files.

The data corresponds to Books, MusicAlbum, Games, Genres, Labels, Authors

Let's have fun!

Create App Methods for Music

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

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.

Create a schema.sql for Game

• 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

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

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

Define Schema.sql tables for Books

• 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