Tackling some key misconceptions about Enterprise Architecture can ease fear, uncertainty, and doubt about its effectiveness. If there is any form that is essential, it is text, whether the text is annotating a diagram or fully describing a requirement, it must be used to document architecture. An example of an architecture documented in only text is the U.S. Constitution.
Architecture and engineering are different. The engineer makes the architecture a reality bringing material to bear, whereas the architect describes the desired reality bringing clarity to what is needed.
With the release of the ArchiMate 3.0 Specification in 2016, we now have a complete enterprise description language that has been adopted by architects worldwide in a wide range of organizations. It is now time for the ArchiMate Forum to reach out to users and better understand how the language is being used and how it should evolve. The ArchiMate modeling language supports architects in creating straightforward and understandable diagrams. Use of the ArchiMate notation helps architects understand each other’s architectures.
Making Standards Work® for Smart Cities was the theme of The Open Group Berlin 2017 event. The focus was on how an architecture framework such as TOGAF®, an Open Group standard, can help administrations govern the introduction of smart systems to enable their citizens and businesses to thrive and prosper.
Its focus will be on how an architecture framework such as TOGAF®, an Open Group standard, can help administrations govern the introduction of smart systems to enable their citizens and businesses to thrive and prosper.
The Open Group TOGAF® User Group meeting, held in San Francisco on January 30, 2017, focused on “Create vs. Reuse Architectures.” It addressed the question of whether Enterprise Architects need to be more involved in reusing existing architecture models than in creating new ones to meet their needs.