is it reasonable to use NoSQL for my project
Given that you say you believe this data model screams "relational" the thought that comes to mind is, "I have a nail and I would really like to use a crescent wrench.... Can you?  Yes.  Are you aware of the tradeoffs?  Doubtful."

The basic point about NoSQL is that it makes sense when your data use cases are fairly simple and you have encapsulated that behind a full-featured API.  The example I give for an area where NoSQL would generally be very good would be the backplane of an LDAP directory forest.

For the application you mention your big issue is likely to be flexibility in reporting.  You would have to purpose build your reports in advance and that's the major cost.  For an application like this, that is a very big cost.

One other point I would make is that you may find that there are opportunities to use NoSQL along side the RDBMS.  For example you could implement a caching system for the web app using it.