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:
“It makes little sense to spend a month teaching decimal fractions to fourth-grade pupils when they can be taught in a week, and better understood and retained, by sixth-grade students. Child-centeredness does not mean lack of rigor or standards; it does mean finding the best match between curricula and children’s developing interests and abilities.”
—David Elkind (20th century)
“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)
“Adults understandably assume that the level of verbal proficiency a five-year-old displays represents his level of proficiency in all areas of functioning—if he talks like an adult, he must think and feel like one. However, five-year-olds,... belie the promise of adult-like behavior with their child-like, impulsive actions.”
—Dorothy H. Cohen (20th century)
“It is possible—indeed possible even according to the old conception of logic—to give in advance a description of all ‘true’ logical propositions. Hence there can never be surprises in logic.”
—Ludwig Wittgenstein (1889–1951)