Can you help me?

[iProgram]

Hello, I'm a college student and I've been given a pretty tricky homework problem. I'm great with SQL since I love code, but normalizing is not my forte. My professor said there is an issue with this relation aswell, but I beleive it has to do with the StationAdress, I'm still not sure though... Can you help me normalize the following relation and point out if another attribute is needed or what the tricky part is, I'd really appreciate it!

FIRE_REPORT(FireID, Alarms, Address, FiremanID, FiremanName, FiremanPhone, FiermanHomeStation, StationAdress, StationPhone, TruckID, License, TruckHomeStation)

Context: 
1.Each fire can have several firefighters assigned to it. 
2.Each fire can have several fire trucks assigned to it. 
3.Each firefighter can be assigned to several fires
4.Each fire truck can be assigned to several fires
5.Each firefighter has a single home station
6.Each fire truck has a single home station
7.Each station name is unique
8.Each station has a single phone number

Adress= Adress of the fire
FiremanPhone= personal phone number
Alarms= severity of the fire, example; 1 alarm fire, 2 alarm fire...

Example of a Truck Home Station/Fireman Home Station: LittleTown Station 5

 

[xenou]

I guess it's going to be a problem now that I look again. We know for sure that a fire report will have more than one fireman, but our Fire Report table as is only allows for 1 fireman ID. And I'm not sure we have a primary key in the Fire Report table itself.

What's the difference between a Fire_Report and a Fire? Conceptually, what's in those two tables? Is there a one - to - one relationship between a Fire and a Fire Report (every fire has one and only one fire report, every fire report is about one and only one fire?) Or does the Fire Report actually have some other purpose?

Also, what's the purpose here? Are you trying to build the table structure in a database? Is it an assignment? I don't see how we can avoid junction tables if that's the case - I mean, if we have to build the correct tables to handle the relationships between fires, fire reports, firemen, and so on.