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.
The ArchiMate language should address only what is necessary to model architecture and leave the other areas to appropriate modeling languages, such as BPMN™ for business process models and UML® for software models. Each profession has its own optimal terminology, languages, and tools. The ArchiMate language should not challenge languages designed for disciplines beyond architecture. It is better to ensure traceability between different model types to maintain consistency. If there is a desire for a modeling language for other areas, do not just add them to the ArchiMate language but make a related new language.
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.
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.
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.
At The Open Group Shanghai 2016 summit, we invited Dr. Giovanni Traverso, Chief Business Architect of HUAWEI Service Strategy and Architecture Practice, to give a