The Enterprise Systems Approach

The Enterprise Systems Approach

Andrew Targowski (Western Michigan University, USA)
DOI: 10.4018/978-1-60566-856-7.ch001


The enterprise system approach is defined by its evolution and major milestones of architectural planning. The ES architectures are multi-faceted solutions, hence it is defined in the scope of the enterprise organization architecture (EOA), enterprise functional architecture (EFA), enterprise processive architecture (EPA), enterprise information architecture (EIA), enterprise software architecture (ESA), enterprise network architecture (ENA), enterprise service architecture (ESA), business component architecture (BCA), enterprise information infrastructure (EII), and enterprise configurations. A composite ES architecture is presented as a transitional architecture, which is currently practiced by most enterprises. The near future of the ES approach will be rather limited to the ways of delivering ES’ applications within a framework of service-oriented architecture (SOA) and the cloud computing, which satisfies effective large-scale operations. The progressive process of organization/business virtualization and the urgent need for more sustainable enterprise development should lead to new development of enterprise systems.
Chapter Preview


The purpose of this study is to define the Enterprise Systems approach, its evolution, and major milestones of its architectural planning. The former is done mostly in a graphic manner and based on graphic models, which should be self-explanatory. The ES architectures are multi-faceted solutions, hence they will defined in the scope of the Enterprise Organization Architecture (EOA), Enterprise Functional Architecture (EFA), Enterprise Processive Architecture (EPA), Enterprise Information Architecture (EIA), Enterprise Software Architecture (ESA), Enterprise Network Architecture (ENA), Enterprise Service Architecture (ESA), Business Component Architecture (BCA), Enterprise Information Infrastructure (EII), and Enterprise Configurations. Such enterprise architectures concerning hardware and data have been left undefined due to the limits of this chapter.

The ES approach became necessary in the 1990s when the complexity of enterprise systems became the major issue in systems development and was integrated into thousands of IT solutions. It was necessary to provide a general, well-modeled map of IT systems and services thatcould help in understanding the rising enterprise complexity, which had to be contained and explored for the sake of enterprise operations.

Complete Chapter List

Search this Book: