Multiple dsv's in the same solution

Hello,

We have a solution with several cubes which share dimensions across them. However, I find it better to manage if we have just one dsv where define all the connections between these different tables and then create different cubes from this one dsv.  Recently I was asked why not to create a separate dsv for every single cube (note, its the same database, hence one ds). Can you please tell me the positive and negative impacts of having separate dsv's for every single cube (where many dimensions are shared)? 

Thanks.