Standards for Application System Classes

NB: I do understand that maybe I should think quite differently - but I am uncertain on how :-)

Hello Lars,

I understand your meta-model like this:

1. You have ASTs aggregated to ASCs - fair enough.

2. You have Policies applying to ASCs - also fair.

I have not checked in the standard ARIS method, if there is a connection type between "Policy" object and "ASC" object or even, if there is a model type that can hold both object types and the connection envisioned. But if that is what you need and the standard should not allow it, you can surely adapt the method so you get exactly what you need. The first relationship is the classic one for AST diagram. If you need the AST diagram for different things as well, maybe derive an "AST classification diagram" from it.

For the second relationship take the "Access diagram" and derive an "Application class policy diagram" from it. Make sure you can assign it to "ASC" object and make it look somewhat similar to the Function allocation diagram with your policy objects arranged around the ASC object.

Check back with your stakeholders who will maintain which of the diagrams.

I have difficulty imagining your second use case: Policies for an ASC without ASTs. What's the point of having that ASC then? Maybe an ASC "Spreadsheet applications" with policies like "Do not use macros"? Maybe in that case you do not want to maintain the list of all spreadsheet applications in the AST classification diagram, but rather let the business department classify their spreadsheet in the Access diagram of each spreadsheet AST. Then it is useful to be able to jump from the ASC to the Application class policy diagram via assignment.