Enterprise Architecture - The Value Proposition. ISO/IEC 42010. ISO/IEC/IEEE 42010 Systems and software engineering — Architecture description is an international standard for architecture descriptions of systems and software. Overview[edit] ISO/IEC/IEEE 42010:2011 defines requirements on the description of system, software and enterprise architectures. It aims to standardise the practice of architecture description by defining standard terms, presenting a conceptual foundation for expressing, communicating and reviewing architectures and specifying requirements that apply to architecture descriptions, architecture frameworks and architecture description languages. Following its predecessor, IEEE Std 1471, the standard makes a strict distinction between Architectures and Architecture Descriptions.
The description of ISO/IEC/IEEE 42010 in this article is based upon the standard published in 2011.[1] Terminology[edit] ISO/IEC 42010 defines a number of terms: Conceptual Foundations[edit] The ISO/IEC/IEEE 42010 conceptual model utilizes the following concepts: Define:Enterprise architecture.
ArchiMate/OpenGroup. Enterprise architecture. Enterprise architecture (EA) is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a holistic approach at all times, for the successful development and execution of strategy. Enterprise architecture applies architecture principles and practices to guide organizations through the business, information, process, and technology changes necessary to execute their strategies.
These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes. "[1] Practitioners of enterprise architecture call themselves enterprise architects. An enterprise architect is a person responsible for performing this complex analysis of business structure and processes and is often called upon to draw conclusions from the information collected. Overview[edit] The MIT Center for Information Systems Research (MIT CISR) in 2007 defined enterprise architecture as the specific aspects of a business that are under examination:
GODS One PAge Business Architecture v3.gif (GIF Image, 960×720 pixels) Enterprise Architecture & TOGAF. A generic Business Architecture. What are the essential parts of an Enterprise? At the beginning of the '80es, Michael Porter suggested that any Enterprise consists of two categories of activities: Primary activities, which are the operational processes that deliver the product such as inbound logistics, Operations. Outbound logistics, Sales and Services And Secondary activities that are all other supporting activities , as for example Human Resources, Technology Development, Procurement etc. Taking into account the dynamics of today's economy, I concluded though that Development activities are worth a category in themselves since a great chunk of them, such as strategy and business development, new products and capabilities development or R&D ensure the competitive edge of the Enterprise and its continuity. In a world that spins faster and faster, more and more activities are outsourceable and outsourced, even Operations, once a core activity.
This is how the GODS Enterprise structure came into being.