The rise of networking form the 1980’s onward may be considered the main driving force of the invention of enterprise architecture, itself a follow-up on what was until then known as system architecture. On the eve of the rise of the ‘softwarification’ of infrastructure (software defined data centers, software defined networks) and the ongoing impact of Cloud-architecture, it is time to look into the modelling of networking infrastructure some more.
ArchiMate has two specific concepts for networking: Network and Communication Path. Network is the element that represents physical networking, as the standard explains, and it gives the following example:
Actually, the standard displays it differently, with the middle Network element and both Associations replaced by an arrow on two sides, but my (ArchiMate-compliant) modelling tool does not support that notation (though I can trick it graphically, see below). Probably no user of that (leading) tool ever has used that notation, which tells us already something. Continue reading
A short post today. I’ve been asked to write a regular column on enterprise architecture for the Enterprise Architecture Professional Journal. The column title is On Slippery Ice and the side bar of that column explains why.
The first column in that series is called Are you an Enterprise Architect? Really? and it is about the role of principles and guidelines in architecture. Have fun.
Note: I will not make a habit out of posting just an announcement on this blog, which should contain posts on ArchiMate. But this is an exception as it is the initial column for EAPJ. I will post announcements of future EAPJ columns on the Chess and the Art of Enterprise Architecture blog only (next to separate posts on EA), as that blog is about enterprise architecture in general.
This post is about two related things: modelling actual detailed architectures of large homogenous landscapes and the class versus instance issue in ArchiMate. Both are closely related. But before I start out, for those unacquainted with Object-Orientation, or Classes and Instances (the notions are strongly related but not perfectly identical) I will give a very short primer on the underlying concepts.
And if you are new to ArchiMate, please skip this post, it contains non-standard ideas for ArchiMate and it will probably only confuse you; the language is really not that confusing if you learn it first (e.g. by reading the book). Continue reading
The site for the next book “Chess and the Art of Enterprise Architecture” has gone live. It will take some time still before the book is available, but I will already start blogging a bit about the subject.
A welcome message has been posted on the blog. It explains why the new blog has been started.
Just a short note today. The Open Source Archi Tool used to be supported by a UK University. It isn’t anymore. The university has stopped its sponsoring and Archi’s developer (Phil Beauvoir) has left the university and started an initiative to keep Archi thriving (it is widely used in the world). But he also needs a living. He won’t be able to keep Archi alive unless he is paid in some way. As I have experienced with Edition I, it is difficult to get people to pay/donate for something that is (or in my case ‘looked like’) a free download). So, if you use Archi, please donate an amount that reflects the importance of Archi for your work. And if you use Archi seriously as a business, take out a sponsorship. Remember, in the end “there is no such thing as a free lunch”.
In Plato’s ‘Socratic Dialogue’ Protagoras, Socrates and Protagoras (the great ‘Sophist’) have a discussion on what knowledge and skill is and how people acquire these. I am reminded of that discussion as I am thinking about how to explain my reasoning on the issue of Stakeholder versus Role. More about that at the end. Continue reading