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:
“Every society consists of men in the process of developing from children into parents. To assure continuity of tradition, society must early prepare for parenthood in its children; and it must take care of the unavoidable remnants of infantility in its adults. This is a large order, especially since a society needs many beings who can follow, a few who can lead, and some who can do both, alternately or in different areas of life.”
—Erik H. Erikson (1904–1994)
“Every diminution of the public burdens arising from taxation gives to individual enterprise increased power and furnishes to all the members of our happy confederacy new motives for patriotic affection and support.”
—Andrew Jackson (1767–1845)
“Preschoolers sound much brighter and more knowledgeable than they really are, which is why so many parents and grandparents are so sure their progeny are gifted and super-bright. Because children’s questions sound so mature and sophisticated, we are tempted to answer them at a level of abstraction far beyond the child’s level of comprehension. That is a temptation we should resist.”
—David Elkind (20th century)
“Everything to which we concede existence is a posit from the standpoint of a description of the theory-building process, and simultaneously real from the standpoint of the theory that is being built. Nor let us look down on the standpoint of the theory as make-believe; for we can never do better than occupy the standpoint of some theory or other, the best we can muster at the time.”
—Willard Van Orman Quine (b. 1908)