As far as I can see it enterprise architecture is just another systematic approach to do certain task. As a systematic approach I expect each enterprise architecture work to be based on four main pillars: Ontology, Methodology, Repository and Tool: - Ontology: Formal language that defines set of concepts and the relationships between those concepts. - Methodology: A proven method to define product architecture - Repository: Central storage for all product architecture definitions. - Tool: Modeling tool that supports the Ontology, Methodology and Repository While you find methodology, repository and tool in most of the enterprise architecture teams it is rare to find ontology. It doesn’t matter if it’s a small team or a global EA team; it is hard to find single ontology that is being used by all of the group members, if ontology at all. I believe that ontology should be one of the first pillars that enterprise architect should pour. Without one formal language that defined all the concepts I find hard to see how group of people will manage to reach their tasks effectively.
