A Framework for Enterprise Operating Systems Based on Zachman ...

A Framework for Enterprise Operating Systems Based on Zachman Framework S. Shervin Ostadzadeh

Amir Masoud Rahmani

Computer Engineering Department, Faculty of Engineering, Science & Research Branch, Islamic Azad University, Tehran, Iran [email protected]

Computer Engineering Department, Faculty of Engineering, Science & Research Branch, Islamic Azad University, Tehran, Iran [email protected]

Abstract - Nowadays, the Operating System (OS) isn’t only the software that runs your computer. In the typical informationdriven organization, the operating system is part of a much larger platform for applications and data that extends across the LAN, WAN and Internet. An OS cannot be an island unto itself; it must work with the rest of the enterprise. Enterprise wide applications require an Enterprise Operating System (EOS). Enterprise operating systems used in an enterprise have brought about an inevitable tendency to lunge towards organizing their information activities in a comprehensive way. In this respect, Enterprise Architecture (EA) has proven to be the leading option for development and maintenance of enterprise operating systems. EA clearly provides a thorough outline of the whole information system comprising an enterprise. To establish such an outline, a logical framework needs to be laid upon the entire information system. Zachman Framework (ZF) has been widely accepted as a standard scheme for identifying and organizing descriptive representations that have prominent roles in enterprise-wide system development. In this paper, we propose a framework based on ZF for enterprise operating systems. The presented framework helps developers to design and justify completely integrated business, IT systems, and operating systems which results in improved project success rate. Keywords: Enterprise Operating System, Zachman Framework, Enterprise Architecture, Enterprise Architecture Framework.

I. INTRODUCTION Enterprises face a lot of challenges nowadays, however, fully utilizing and integrating rapid improvements of information technology remains one important challenge. This is due to the fact that proper development of information systems would have substantial impact on tuning activities in enterprises. An OS is an interface between hardware and user which simplifies development of applications. The dynamic nature of activities in an enterprise brings up changes in relevant information systems. Managements are hesitant to adopt the regular changes due to the huge costs of information systems development and maintenance; as a result, outdated systems form a barrier toward the enterprise evolvement. Enterprise Architecture (EA) is introduced to specifically address this problem by organizing business processes and information technology infrastructure reflecting the integration and standardization requirements of an enterprise operating model [1].

An enterprise operating system is the center of IT activities in an enterprise. It manages all resources; connects all devices; and provides a virtual platform for enterprise services. To have an overall understanding of an enterprise, one should perceive different views of components contained in that enterprise, including EOS. It should be noted that handling this large amount of information is quite challenging and needs a welldeveloped framework. To address this problem, various enterprise architecture frameworks have emerged, such as, FEAF [2], TEAF [3], and C4ISR [4]. Zachman framework [5] originally proposed by John Zachman, is often referenced as a standard approach for expressing the basic elements of enterprise architecture. In this paper we propose a framework for an enterprise operating system inspired by ZF. This is the first time that a framework is proposed for an enterprise considering operating system in it. However, using a framework in an enterprise is not a new term and has a long acquaintance. This resulted in a comprehensive structure for all aspects of EOS. ZF is widely accepted as the main framework in EA. Compared to other proposed frameworks, it has evident advantages to list [6]: (1) using well-defined perspectives, (2) using comprehensive abstracts, (3) normality, and (4) extensive usage in practice. They were the motivations for ZF adoption in our work. The rest of this paper is organized as follows. In Section 2, we introduce some basic concepts and principles. We present the proposed framework in section 3. Finally, we make conclusions and suggest some comments for future works. II. BASIC CONCEPTS In this section we briefly introduce some basic concepts and principles. We believe these remarks can help readers to clearly understand what we mean by the concepts that are used throughout the paper. A. Enterprise An enterprise consists of people, information, and technologies; performs business functions; has a defined organizational structure that is commonly distributed in multiple locations; responds to internal and external events; has a purpose for its activities; provides specific services and products to its customers [7]. An IT-related enterprise is an enterprise in which IT plays an important role in its activities.

533

T. Sobh, K. Elleithy (eds.), Innovations in Computing Sciences and Software Engineering, DOI 10.1007/978-90-481-9112-3_91, © Springer Science+Business Media B.V. 2010

534

OSTADZADEH AND RAHMANI

In this paper, we refer to an IT-related enterprise as an enterprise.

same as ZF. They are based on six basic interrogatives that are asked to understand an entity. The columns include:

B. Enterprise Architecture (EA) Enterprise architecture is the science of designing an enterprise in order to rationalize its activities and organization. EA shows the primary components of an enterprise and depicts how these components interact with or relate to each other. EA typically encompasses an overview of the entire information system in an enterprise; including the software [8], hardware, and information architectures. In this sense, the EA is a meta-architecture. In summary, EA contains views of an enterprise, including work, function, process, and information, it is at the highest level in the architecture pyramid. For details refer to [9].

•

C. Enterprise Operating System Architecture Enterprise Operating System Architecture is a view of the operating system used by an enterprise to accomplish its duty. It contains descriptions of various operating system layers integrated with other enterprise architecture views. D. Zachman Framework (ZF) The Zachman framework is a framework for enterprise architecture, which provides a formal and highly structured way of defining an enterprise. In 1987, the initial framework, titled "A Framework for Information Systems Architecture", was proposed by John A. Zachman [10]. An update of the 1987 original work was extended and renamed to the Zachman framework in the 1990s. In essence, the framework is a two dimensional matrix consisting of 6 rows and 6 columns. Each row represents a total view of the enterprise from a particular perspective. These rows starting from the top include: Planner's View (Scope), Owner's View (Enterprise or Business Model), Designer's View (Information Systems Model), Builder's View (Technology Model), Subcontractor's View (Detail Representation), and Actual System View (The Functioning Enterprise). The columns describe various abstractions that define each perspective. These abstractions are based on six questions that one usually asks when s/he wants to understand an entity. The columns include: The Data Description (What?), The Function Description (How?), The Network Description (Where?), The People Description (Who?), The Time Description (When?), The Motivation Description (Why?). Further information and cell definitions of ZF can be found in [11]. III. A FRAMEWORK FOR EOS As mentioned earlier, currently there are some frameworks for EA. However, none of them considers OS. In this section, we introduce our framework proposal based on ZF intended to support all aspects of enterprise operating system as a whole. Figure 1 depicts the proposed framework schema. Similar to ZF, it is a two dimensions matrix. The columns are the

• • • • •

Data (What is it made of?): This focuses on the material composition of the information. In the case of EOS, it focuses on data that can be used for operating system. Function (How does it work?): This focuses on the functions or transformations of the information used for operating system. Network (Where are the elements?): This focuses on the geometry or connectivity of the data used for operating system. People (Who does what work?): This focuses on the actors and the manuals and the operating instructions or models one uses to perform their services. Time (When do things happen?): This focuses on the life cycles, timings and schedules used for operating system. Motivation (Why do things happen?): This focuses on goals, plans and rules that prescribe policies and ends that guide an organization for operating system.

The rows represent various perspectives of the OS framework. These perspectives, starting from the top, are: • Scope: This is the highest level of abstraction in the framework. It refers to the boundaries of the enterprise from the operating systems view. This row is the perspective of chief enterprise's managers. • Services: This row stands beneath the Scope layer. In this row, the services that the operating system should provide in the enterprise will be addressed. This is the perspective of an enterprise's expertise. • Kernel: This row stands below the services, and focuses on operating system behaviors to support operating system services. This is the perspective of the operating system development team. • Core: This is the lowest level of abstraction in the framework. It focuses on basic management that an operating system should provide to support kernel layer. This row is the perspective of system programmers. The framework contains 24 cells. Each cell describes a model that an organization might document to describe the enterprise operating system. Each of the cells in the framework is primitive and thus, each can be described or modeled independently. All of the cells on a given row make up a given perspective. All of the cells in a column are related to each other since they focus on the same type of elements. Organizations may not keep all of the models described by the EOS framework. Some organizations do not formally define some of the cells; however, since all of the cells are logically necessary for a complete description of an organization, if they aren’t formally described, they are implicit in assumptions made by people in the organization. Following sections present the framework's cells definitions.

535

A FRAMEWORK FOR ENTERPRISE OPERATING SYSTEMS EOS Framework

Data

Function

Network

People

Time

Motivation

Scope Services Kernel Core Figure 1. A framework for EOS based on Zachman Framework

A. Data Column Scope-Data cell is simply a list of important operating system entities (or objects, or assets) that the enterprise is interested in. It is probably adequate that this list is at a fairly high level of aggregation. It defines the scope, or boundaries, of the rows 2- 4 models of entities that are significant to the enterprise. Service-Data cell is a model of the actual operating system entities (objects, assets) that are significant to the enterprise. It typically would be at a level of definition that it would express concepts (terms and facts) used in the significant business objectives/strategies that would later be implemented. Kernel-Data cell is a model of the kernel operating system entities (objects, assets) that are significant to the data of OS services. Core-Data cell would be the definition of all the data specified by the Physical Data Model and would include all the data definition language required for OS implementation in the supervisor mode. B. Function Column Scope-Function cell is simply a list of important operating system processes (or functions) that the enterprise performs. It is probably adequate that this list is at a fairly high level of aggregation. It defines the scope, or boundaries, of the rows 24 models of processes that the enterprise performs. Service-Function cell is a model of the actual operating system processes (or functions) that the enterprise performs. It can be represented as a model expressing the business transformations (processes) and their inputs and outputs. Kernel-Function cell is a model of the kernel operating system processes (or functions) that are significant to support the function of OS services. Core-Function cell would be the algorithms specifications for the OS implementation in the supervisor mode. C. Network Column Scope-Network cell is simply a list of locations in which the enterprise operates. It is probably adequate that this list is at a fairly high level of aggregation. It defines the scope, or boundaries, of the models of locations that are connected by the enterprise and are found in rows 2- 4. Service-Network cell is a model of the actual operating system locations (or nodes) and their connections that are

significant to the enterprise. It would include identification of the types of facilities at the nodes and connections. Kernel-Network cell is a model of the kernel operating system locations (or nodes) and connections that are significant to the locations of OS services. Core-Network cell is the specific definition of the node addresses and the lines required for OS implementation in the supervisor mode. D. People Column Scope-People cell is simply a list of important operating system organizations to which the enterprise assigns responsibility for work. It is probably adequate that this list is at a fairly high level of aggregation. It defines the scope, or boundaries, of the models of organization that are responsible to the enterprise and depicted on rows 2- 4. Service-People cell is a model of the actual operating system allocation of responsibilities and specification of work products. Kernel-People cell is a model of the kernel operating system responsibilities that are significant to the work of OS services. Core-People cell is the physical expression of work flow of the OS including the specific individual and their requirements and the presentation format of the work product required for OS implementation in the supervisor mode. E. Time Column Scope-Time cell is simply a list of important operating system events to which the enterprise responds. It is probably adequate that this list is at a fairly high level of aggregation. It defines the scope, or boundaries of the models of time that are significant to the enterprise and found in Rows 2- 4. Service-Time cell is a model of the actual operating system business cycles that is comprised of an initiating event and an elapsed time (or cycle). It typically would be at a level of definition that it would express sequence, or relative time. Kernel-Time cell is a model of the kernel operating system time (events, cycles) that are significant to the time of OS services. This model describes the system events that trigger the state to transition from one valid state (point in time) to another and the dynamics of that transition cycle. Core-Time cell is the definition of interrupts and machine cycles required for OS implementation in the supervisor mode.

536

OSTADZADEH AND RAHMANI

F. Motivation Column Scope-Motivation cell is simply a list of major operating system goals (or objectives, or strategies, or critical success factors) that are significant to the enterprise and defines the relative to motivation. It is probably adequate that this list is at a fairly high level of aggregation. It defines the scope, or boundaries, of the models of goals (etc.) that are embraced by the enterprise and found in the constructs of Rows 2- 4. Service-Motivation cell is a model of the business objectives and strategies (the "ends" and "means") of the enterprise that constitute the motivation behind Enterprise Operating System. Kernel-Motivation cell is a model of the operating system rules of the enterprise in terms of their intent ("ends") and the constraints ("means"). Core-Motivation cell would be the specification of the operating system rules required for OS implementation in the supervisor mode. IV. CONCLUSIONS Business and IT integration is a critical challenge faced by IT industry. An EOS can be considered as the center of IT in an enterprise provided a virtual platform for enterprise services. In this paper, a framework for EOS based on ZF is proposed. Compared to other frameworks, ZF has some evident advantages. These advantages have caused its extensive usage as the basic framework of enterprise architecture. This research can be an initial step to demonstrate how the models in an EOS can be made coherent in order to avoid inconsistencies within the framework. In general, our proposed method is expected to increase the success rate of the projects in enterprises. In order to develop an EOS, defining a methodology based on the proposed framework will unleash the full support of the presented framework, which should be considered in future work.

REFERENCES [1] Peter Weill, "Innovating with Information Systems: What do the most agile firms in the world do?," Presented at the 6th e-Business Conference, Barcelona, Spain, March 2007. http://www.iese.edu/en/files/6_29338.pdf [2] Chief Information Officers (CIO) Council, Federal Enterprise Architecture Framework, Version 1.1, September 1999. [3] Department of the Treasury, Treasury Enterprise Architecture Framework, Version 1, July 2000. [4] C4ISR Architecture Working Group (AWG), C4ISR Architecture Framework, Version 2.0, U.S.A. Department of Defense (DoD), December 1997. [5] J. A. Zachman, The Zachman Framework: A Primer for Enterprise Engineering and Manufacturing, 2003. [6] S. S. Ostadzadeh, F. Shams, S. A. Ostadzadeh, "A Method for Consistent Modeling of Zachman Framework," Advances and Innovations in Systems, Computing Sciences and Software Engineering, Springer, pp. 375-380, August 2007. (ISBN 9781-4020-6263-6) [7] M.A. Rood, "Enterprise Architecture: Definition, Content, and Utility," IEEE Trans., 1994. [8] L. Bass, P. Clements, and R. Kazman, Software Architecture in Practice, 2nd Edition, Addison-Wesley, 2004. [9] C.M. Pereira, and P. Sousa, "Enterprise Architectures: Business and IT Alignment," Proceedings of the 2005 ACM symposium on Applied computing, Santa fe, New Mexico, 2005. [10] J. A. Zachman, "A Framework for Information Systems Architecture," IBM Systems Journal, Vol. 26, No. 3, 1987. [11] J. A. Zachman, "The Framework for Enterprise Architecture – Cell Definitions," ZIFA, 2003.