How to create an ArchiMate model?

[Tarja]

Hi all!
How can I create an ArchiMate model WITHOUT any viewpoint?
Viewpoints are not simply used by enterprise architects - they are too restrictive. I need a model that contains all layers and aspects from Motivation, Strategy, through core layers to Implementation and Migration in one model.
And that creating the model would create the standard folder structure for all elements.

Or that I could create a model of Business layer without any viewpoints?

I know that Sparx EA is not accredited tool by Open Group. But I was hoping some proper features would be in place...

I have created ArchiMate models without viewpoints with version 13 but now it seems that it is impossible?

[Geert Bellekens]

That is still certainly possible.

Just create a diagram (of any type really) and use the ArchiMate toolbox of your choice to create the elements you need on the diagram.

You can even mix ArchiMate with non-ArchiMate elements on the same diagram.

Just make sure you don't restrict yourself in the perspective you select (you can select All to make sure you can do anything)

Geert

[Eve]

By default the ArchiMate technology offers 5 diagram types corresponding to each layer. If you don't select a view (expanding the diagram node in the diagram dialog) the toolbox will offer all the elements and relationships in that layer. If you select a view all it's doing is clearing the clutter to help express a limited aspect of the model. On top of the default views that ArchiMate describes you can also create your own views to assist in expressing the architecture in ways not covered by the default views.

What "standard folder structure" are you referring to? From my reading of the specification there is no description of folder structure. EA is much more flexible in that regard because it supports arbitrary structure. If you're just looking for a list of your elements by type, maybe the Model Views window (in the Portals in 15) will help. With that you can have folders that perform searches on your model. One possible use of that would be to list all ArchiMate elements in your model by type.

[Glassboy]

By default the ArchiMate technology offers 5 diagram types corresponding to each layer. If you don't select a view (expanding the diagram node in the diagram dialog) the toolbox will offer all the elements and relationships in that layer. If you select a view all it's doing is clearing the clutter to help express a limited aspect of the model. On top of the default views that ArchiMate describes you can also create your own views to assist in expressing the architecture in ways not covered by the default views.

I didn't bother answering the OP, but I think it's worth pointing out that EA doesn't have any ArchiMate viewpoints.  A diagram isn't a viewpoint, unless you have a custom tool box that limits the palette to the elements included in that viewpoint.  Anyway a model with no visualization is just daft.

What "standard folder structure" are you referring to? From my reading of the specification there is no description of folder structure. EA is much more flexible in that regard because it supports arbitrary structure. If you're just looking for a list of your elements by type, maybe the Model Views window (in the Portals in 15) will help. With that you can have folders that perform searches on your model. One possible use of that would be to list all ArchiMate elements in your model by type.

I suspect he means "like wot Archi does".  I have my own folder structure that I use as a template for each ArchiMate model.

[Eve]

I didn't bother answering the OP, but I think it's worth pointing out that EA doesn't have any ArchiMate viewpoints.  A diagram isn't a viewpoint, unless you have a custom tool box that limits the palette to the elements included in that viewpoint.  Anyway a model with no visualization is just daft.

Yes, it does. In the new diagram dialog the viewpoints are available as nodes under the base diagram types. By default EA comes with all the viewpoints that the ArchiMate specification defines in Appendix C. Custom metamodel views allow you to define any of your own. They limit the toolbox to the specified types and optionally allow filtering the diagram to only show matching elements (if you've added them before or dropped them from somewhere else)

I suspect he means "like wot Archi does".  I have my own folder structure that I use as a template for each ArchiMate model.

Yes, I suspected something similar. Which is why I suggested the model view window. It allows you to have that kind of structure regardless of what you actual package structure is.

[Glassboy]

Yes, it does. In the new diagram dialog the viewpoints are available as nodes under the base diagram types. By default EA comes with all the viewpoints that the ArchiMate specification defines in Appendix C. Custom metamodel views allow you to define any of your own. They limit the toolbox to the specified types and optionally allow filtering the diagram to only show matching elements (if you've added them before or dropped them from somewhere else)

Some of us are still stuck on old versions due to the hells of software distribution and licencing in large organisations :-)

[Eve]

If I keep spruiking new EA features maybe over time you'll have sufficient evidence to convince someone you do need the upgrade. 

[Glassboy]

If I keep spruiking new EA features maybe over time you'll have sufficient evidence to convince someone you do need the upgrade. 

We're being split off under new owners so I'm hoping that when we have our own IT it might become easier.

[adepreter]

Have a look at Labnaf: www.labnaf.one

[Eve]

Have a look at Labnaf: www.labnaf.one

Why would labnaf help with the problem of not being able to update or install new software? In that scenario they won't be able to install the labnaf add-in

PS. The reference to ArchiMate on your website links to a file on your computer: file:///C:/Users/Alain%20De%20Preter/OneDrive/LABNAF/Solution/Doc/$inet:/http:/pubs.opengroup.org/architecture/archimate3-doc/toc.html

[Glassboy]

Have a look at Labnaf: www.labnaf.one

"One single"  ROTFLMAO

[qwerty]

One ring to rule them all. Looks like Powerpoint on speed xD

q.

[Tarja]

Thanks Eve for your answer 
I noticed that it is possible to create a diagram simply under the layer.

My question about the folder structure refers to that many ArchiMate tools create automatically folders for different kind of elements. F.ex. for business layer objects separate folders for business actors, business roles, business processes etc. So it is easy to find suitable object / element from the Browser (model) to be reused in diagrams.
But maybe I have to do myself to make it easier to find suitable existing elements when there are hundreds of elements in the model.

[KP]

My question about the folder structure refers to that many ArchiMate tools create automatically folders for different kind of elements. F.ex. for business layer objects separate folders for business actors, business roles, business processes etc. So it is easy to find suitable object / element from the Browser (model) to be reused in diagrams.
But maybe I have to do myself to make it easier to find suitable existing elements when there are hundreds of elements in the model.

Check out "Model Views". This is a browser window that you can add searches to, for example separate searches for business actors, business roles, business processes etc.

https://www.sparxsystems.com/enterprise_architect_user_guide/15.1/user_interface/model_views.html

[Sunshine]

Because the elements can appear in many different viewpoints we structure our model into views and catalogues such as;
Business
   Views
       Organisation
       Process Cooperation
       Product
       etc
   Catalogues
      Products
      Services
      Processes
      Actors
      Roles
      Events
      etc
Application
   Catalogues
      Services
      Components
      Events
      etc
   Views
      Application Cooperation
      etc

If we create new elements on a diagram we have to move them from where the diagram is to the appropriate catalogue package which is a little inconvenient but it works.