Capturing Application System Version Numbers

Hi Megan,

just a suggestion. Assuming the application versions are important to you, because you want to document your application landscape or plan future scenarios of it with future versions.

Then you should consider the different versions of the applications as different application system types between one version and the next. Generate multiple objects "MyApp 1.0" and "MyApp 2.0". It enables you to define the specific capabilities of each version by assigning capabilities to each object.

When you want to look at "MyApp" from a controlling point-of-view, define an object of type "Application system class" for it and assign all known versions in (potentially future) use to it. The connection is "Application system type" "belongs to class" "Application system class".

And if otherwise you are sure, you rather want an attribute - define a custom attribute. There are many available for renaming and you can also create your own. You need to be able to change the server configuration to edit the method for that purpose.

Regards, M. Zschuckelt

Thank you M. Zschuckelt, I like that idea.

Megan

You definitely want to have them as separate objects with the version in the name, at the detail level, otherwise it can very confusing to work with objects. I generally use the Application System Type object for both the generic and specific objects. You can also create a model that shows all of different versions in use (and projected to be in use) of a specific app and other software that they use.

And another thought: When you have different objects for the versions you can maintain the lifecycle attributes on each version and do some nice support maps - provided you have IT Architect/IT Designer licenses (7.2) or the EA extension pack (ARIS 9.x)