Hello,
1. In Data Architecture which ARIS object is methodologically correct to use for representation of "Business directory"? For example "Employee", "Wharehouse", etc.
2. Is it correct to add "Level of maintenace" attribute (central, local) for "Entity type" ARIS object?
Hello,
if "Glossary" could be a synonym for your term "business directory", in the sense of a collection of definitions in the context of your enterprise, you would use the "Technical term" object in "Technical terms models". That also provides connection types you might want to use to explain relationships between different terms.
"Level of Maintenance" (central, local) for entity types: It's up to you, if you find it useful and to what extent you want to document your data and information landscape. E. g. you might want to create data models for every application or message type you have. In this scenario the "same" entity types may occur in different applications with diverse sets of attributes. While it is good to relate them to some central taxonomy you should not go and make just one central entity type. Rather relate an object from a central business object model to the entity types in the data models of the applications.
Hello,
this question is hard to answer without a bit more context. See the dismbiguation page for the term "directory" on Wikipedia. https://en.wikipedia.org/wiki/Directory
It would help if you could provide a few details about the relationships you want to model for your "directory" objects.
Thank you, M. Zschuckelt. Added some context to the question.
Hello,
if "Glossary" could be a synonym for your term "business directory", in the sense of a collection of definitions in the context of your enterprise, you would use the "Technical term" object in "Technical terms models". That also provides connection types you might want to use to explain relationships between different terms.
"Level of Maintenance" (central, local) for entity types: It's up to you, if you find it useful and to what extent you want to document your data and information landscape. E. g. you might want to create data models for every application or message type you have. In this scenario the "same" entity types may occur in different applications with diverse sets of attributes. While it is good to relate them to some central taxonomy you should not go and make just one central entity type. Rather relate an object from a central business object model to the entity types in the data models of the applications.