Developing An Enterprise Level Architectural Description
Paramount to the enterprise architecture is the identification of the sponsor, his/her mission, vision and strategy and the governance framework to define all roles, responsibilities and relationships involved in the anticipated transition.
Enterprise architects use various methods and tools to capture the structure and dynamics of an enterprise. In doing so, they produce taxonomies, diagrams, documents and models, together called artifacts. These artifacts describe the logical organization of business functions, business capabilities, business processes, people, information resources, business systems, software applications, computing capabilities, information exchange and communications infrastructure within the enterprise.
A collection of these artifacts, sufficiently complete to describe the enterprise in useful ways, is considered by EA practitioners an 'enterprise' level architectural description, or enterprise architecture, for short. The UK National Computing Centre EA best practice guidance states
Normally an EA takes the form of a comprehensive set of cohesive models that describe the structure and functions of an enterprise.
- and continues
The individual models in an EA are arranged in a logical manner that provides an ever-increasing level of detail about the enterprise: its objectives and goals; its processes and organization; its systems and data; the technology used and any other relevant spheres of interest.
This is the definition of enterprise architecture implicit in several EA frameworks including the popular TOGAF architectural framework.
An enterprise architecture framework bundles tools, techniques, artifact descriptions, process models, reference models and guidance used by architects in the production of enterprise-specific architectural description. Several enterprise architecture frameworks break down the practice of enterprise architecture into a number of practice areas or domains.
See the related articles on enterprise architecture frameworks and domains for further information.
In 1992, Steven Spewak described a process for creating an enterprise architecture that is widely used in educational courses.
Read more about this topic: Enterprise Architecture
Famous quotes containing the words developing, enterprise, level and/or description:
“By contrast with history, evolution is an unconscious process. Another, and perhaps a better way of putting it would be to say that evolution is a natural process, history a human one.... Insofar as we treat man as a part of nature—for instance in a biological survey of evolution—we are precisely not treating him as a historical being. As a historically developing being, he is set over against nature, both as a knower and as a doer.”
—Owen Barfield (b. 1898)
“In enterprise of martial kind,
When there was any fighting,
He led his regiment from behind—
He found it less exciting.”
—Sir William Schwenck Gilbert (1836–1911)
“... when you do get a job everybody says, “Well, they wanted a black woman,” which necessarily puts you on a level where you have to prove yourself above being a woman and being black.... Now, I would say, in certain situations, it helped me simply because I was mildly attractive, not because I was black or a woman. That gets you more mileage than anything else.... God help you if you’re not an attractive woman.”
—Theresa Brown (b. 1957)
“Why does philosophy use concepts and why does faith use symbols if both try to express the same ultimate? The answer, of course, is that the relation to the ultimate is not the same in each case. The philosophical relation is in principle a detached description of the basic structure in which the ultimate manifests itself. The relation of faith is in principle an involved expression of concern about the meaning of the ultimate for the faithful.”
—Paul Tillich (1886–1965)