What so unique about EA "views"?

[mse]

I noticed that EA has this unique concept called Views as the top-level organizational folders. For example, if you try to create a package under the root Model, you get presented with view options such as "Simple", "Use Case", "Class", etc. The icon also looks different. After creating the view, only then can you insert packages. Now there is a workaround whereby one can simply move packages to the root Model node, but I want to know what this whole view concept is about.

I am thinking about creating views for the typical silos such as software team, systems team, hardware team, etc. I'm not sure that is what it is for however.

What benefits do I get from using views?

[Geert Bellekens]

Views are packages (at the level below root) with an icon in the project browser that can be changed.

Nothing more, nothing less.

Whether you consider this a benefit is up to you.

Geert