In the past ten years, EA has become an important method for modeling the relationship between the
overall image of corporate and individual systems. In ISO/IEC/IEEE42010:2011, architecture
framework is defined as "conventions, principles, and practices for the description of architecture
established within a specific domain of application and/or community of stakeholders." Furthermore,
in the TOGAF (2011) technical literature, it is defined as "a conceptual structure used to develop,
implement, and sustain an architecture." In addition, EA visualizes the current corporate IT
environment and business landscape to promote a desirable future IT model (Buckl et al. 2010). EA is
required as an essential element of corporate IT planning; it is not a simple support activity (Alwadain
2013), and it offers many benefits to companies, such as coordination between business and IT,
improvement in organizational communication, information provision, and reduction in the
complexity of IT (Tamm et al. 2011). In order to continue to deliver these benefits, EA frameworks
need to embrace change in ways that adequately consider the emerging new paradigms and
requirements that affect EA, such as the paradigm of Cloud computing or enterprise mobility
(Alwadain et al. 2014).