Can you elaborate a bit more what you try to accomplish here?
If "star" refers to a star-join operation, then the question can be easily answered.
It doesn't really matter.
Designing views (and that's true for all cases) consists of two aspects:
- designing the consumption interface (the columns that the view exposes)
- designing the query that produce the view's output
The star join is a modelling tool that applies to the second aspect.
For the output of the view it makes no difference whatsoever how you model it.
For the query it does of course matter. There you want to leverage the de-composition options that a virtual data model can provide.
Any entity that you define can be re-used over and over in many different contexts.
That's what you want to have because it makes your solution understandable and maintainable.