While we are more than willing to help those that are stuck, that doesn't mean that we are here to do it all for you! We can't do all the work, you are either getting paid for this, or it's part of your grades and it wouldn't be at all fair for us to do it all for you.
So we need you to do the work, and we will help you when you get stuck. That doesn't mean we will give you a step by step solution you can hand in!
Start by explaining where you are at the moment, and what the next step in the process is. Then tell us what you have tried to get that next step working, and what happened when you did.
Read the whole question, and look at what the columns it needs in each table are: then decide what types the columns should be: NVARCHAR for text; INT, DECIMAL, or FLOAT for numbers that you might do maths with (i.e. not phone numbers - they are text); DATE, DATETIME, or DATETIME2 for date based info.
Remember, if you want to identify specific rows, you will need unique information, so adding an ID field to each table (INT and IDENTITY is a good start) is a good idea and one I do for every table I create.
Think about the relationships between the tables: do they have "common elements"? For example, if you have Books, you probably have Authors as well, and the Books table should refer to an Author (by the ID column) so you don't have to enter the author data for each separate book.
Then think about the application you are to create, and what it needs to do with the database: we have no idea as we can't even see the full question! Then try your DB design on paper and see if it works to do what you need: tweak the design until all required operations are pretty simple. A little time spent here will really make your life easier later when you come to use the DB data!
If you are having problems getting started at all, then this may help: How to Write Code to Solve a Problem, A Beginner's Guide