Corporations are faced with global competition and they need to become more agile and resilient. Enterprise Architects need to rethink how they deliver value more quickly to keep pace of change in need and change in technology. Builders are employing latest techniques in Agile and Dev-Ops. Architects and builders need to continuously think about risk mitigation.
While all four maturing digital trends – Mobile, Cloud, Delivery Optimization, Process Optimization — are interconnected, Cloud appears to be the one to make the technology c-suite (CISO, CTO and CDO) most nervous. But the potential upside of Cloud adoption brings tremendous synergy in operating costs and also helps propel innovation.
The aim of this event was to unite practitioners and industry experts to discuss achievements, lessons learned and looming issues in e-Government. The theme, “Making Standards Work® e-Government” looked at the e-Society, e-Technology and e-Management viewpoints –federal, provincial, municipal and NGOs. Emphasis was on how techniques such as Enterprise Architecture and Business Design and standards such as TOGAF® and ArchiMate® are acting as a foundational core for enterprise transformation.
Topics include: issues surrounding business transformation, business analysis, information sharing, e-health, privacy and cyber-security. In addition, the strategic execution and the application of emerging technologies and management techniques to e-Government will be the subject of presentations by global experts.
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.