Very little work exists on the use of naming conventions in shared modeling environments. Peter Harrad gives an insightful contribution into the importance of their use, along with some best practices. Avoid the risk of communication, confusion and other potential pitfalls in your modeling initiative, and achieve clear navigation, clarity and consistency with the advice he offers. Examples relatable to each business layer of ArchiMate are included.
Models are a way for people to understand a complex situation, and to communicate it. They are good for achieving this purpose. However, one of the decisions that any effort to establish a shared modeling effort faces is that of naming conventions – what should you call a business service? What should you call an application?
Now, it’s possible to create models without any kind of naming convention whatsoever. This is true whether the models are standalone, or in a shared repository, but in both cases doing so runs into the same pitfall – one of miscommunication.
Avoid the risk of communication, confusion and other potential pitfalls in your modeling initiative, and achieve clear navigation, clarity and consistency with the advice he offers. Examples relatable to each business layer of ArchiMate are included.
Login to continue reading or register now to download the ebook.
