Add unit tests for all implemented methods. TEAM 2

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

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

Add all methods visible in the diagram. GROUP TASK

Implement methods: TEAM 3
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)
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

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

Create a Book class in a separate .rb file. TEAM #1

Create MusicAlbum class in a separate .rb file.TEAM 2

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

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. GROUP TASK

The following options should be available: TEAM 1
List all books
List all labels (e.g. 'Gift', 'New')
Add a book
All data should be preserved by saving collections in .json files.
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 Game class properties visible in the diagram should be defined and set up in the constructor method. TEAM 3

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 an Author class with an association to the Item class (in a separate .rb file). TEAM 3

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.

Implement methods: TEAM 1
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

Add unit tests for all implemented methods. TEAM 3

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

The following options should be available: TEAM 3
List of games
List all authors (e.g. 'Stephen King')
Add a game
All data should be preserved by saving collections in .json files.
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 Genre class properties visible in the diagram should be defined and set up in the constructor method TEAM 2

Add unit tests for all implemented methods. TEAM 1

Create a Game class in a separate .rb file. TEAM 3

Create an Item class in a separate .rb file. GROUP TASK

Catalog of my things

In this project, we create a console app that will help you to keep a record of different types of things we own: books, music albums, movies, and games. Everything is based on the UML class diagram presented below. The data is stored in JSON files but we have also prepared a database with tables structure analogical to our program's class structure.

In this milestone @zakiyousufi, and @fullstop125 have added the Kanban board according to these requirements :

• Create an empty repository for your group project.
• Follow the steps described in curriculum-tools-copy-projects in order to copy the [TEMPLATE] Ruby Group Capstone Project board.
• Open the GitHub project (Kanban board) in your team repo.
• Open project requirements and read them carefully.
• Open project requirements divided by team member and compare it with the project requirements.
• Create tasks on your Kanban board based on the project requirements divided by team member.
• Each task should be a separate card that:

• Has a descriptive title.
• Has the number of points in the [Xpt] prefix. That number should indicate the number of points that show how complex the task is. 1 point = 1 hour of estimated work. You shouldn't change the points after dividing up cards, even if the actual work takes longer.
• Has a description of the task.

• Each of the team members should assign themselves to the cards as divided in the project requirements divided by team member (and time estimate distributions should be fair - no single person should be doing all of the most time-consuming tasks). Decide who will be the assignee for the cards marked as group tasks. All cards on your Kanban board should have assignees.

Find our Kanban board here
waiting for your feedback 👍

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

The following options should be available: TEAM 2
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.
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

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