Article Review: Understanding Information Systems Architecture

Pages: 6 (1959 words)  ·  Bibliography Sources: 6  ·  Level: Master's  ·  Topic: Business - Management  ·  Buy This Paper

Information System Management, Zachman's Approach

In 70s and 80s, research in relation to information system management was centered in examining how technology was affecting management. However, the need for reinstating the implication of information system management to a contemporary organization is essential. This research will attempt to prove that the previous approach in relation Information System Management lacks validity, and largely it can be applied in responding to today's demand. The research will borrow heavily from Zachman's enterprise architecture planning (EAP) and later contest it with a contemporary approach Data Modeling by Greamae Simsion.

Zachman's Central Point

Zachman attempts to reveal various complex factors relating to information systems. Ideally, he takes a broad view on various issues, and his ideas appear in a detailed manner. At some point, he examines the various levels involved in the development of each perspective. Ideally, several perspectives should be considered including management, technology, and business. While the business scope illuminates the administrative infrastructure, the technology scope seeks to clarify further on the architectures (Bowman, Godfrey, & Holt, 2000). Therefore, it is imperative to examine the model based on the nature of competencies that each model enforces. Zachman explores the physical architecture model and its application in responding to different answers within a given framework. The central processes in relation to internal business and internal IT section and the mainstream IT processes must be integrated in order to achieve a single hybrid system. Bowman et al. (2000, pp. 92) supports this approach in what the journals consider as elegance and symmetry that lead to the development of formalized structures.

In addition, an information system depends on the nature of administrative infrastructure ensures that decisive approach is geared towards establishing a coherent management. Raeesi, and Sadeghi-Niaraki (2013, pp. 321) join this argument in presenting how management necessitated the development of a coherent information system management. This journal is a good application of Zachman attributes. At each stage, he believed that decisions would have to be made about the nature of materials that will comprise of the product. In addition, each stage of decision development harbors a parallel material that comprises of the product. The management's role is to determine the decisions to be made and ways of realizing them (Bowman, Godfrey, & Holt, 2000).

Again, Zachman attempts to defragment building processes into five main perceptions, with each of the stages adding extract clarification to the detailed methodology. Huysman (2000, pp. 84) argues that one must work closely with interacted system model (one that has adopted Zachman five stages model). Zachman's five stages model consists of planner, owner, designer, builder, and subcontractor. Through this approach, the development of a simple graphical map will be applied to process several attributions to maximize different capabilities (Solotruk & Kristofi?, 1980).

Literature and Suggestions

It is notable that Zachman's approach is geared towards achieving a hybrid factor. Zachman text is inspired by Wesley Publishing Co, which seeks to focus on the subsequent role management in an information system. In this article, the Airforce Labs must integrate a coherent system approach that is not dependent on technology alone, but a hybridism factor of information system management and technology. In this regard, there is a derivative necessity to compare the current and present situations' factors affecting them. Zachman's BSP approach is based on the knowledge that, by that time, there lacked a collective methodology to merge Information System Management and Business Enterprise (Huysman 2000).

Zachman research is based on the incoming indifferences between data design and traditional design and functional design. In the corporate approach, a competitive need ensures that the cheapest means possible can be achieved at a minimum process collectively. In fact, Zachman's research is based on the knowledge that firms lack the inability to change the systems quickly. Data is not adequately managed in methodologies fostering derivative flexibility. Besides, the total change in the infrastructure approach to managerial approach is more flexible and is decisive in all methods possible. This analysis is supported by Chen's approach that seeks to enroll an entity-relationship application in assessing the possible remedies to system design (Bigot et al. 2006).

While providing editions for Zachman's strategy, a common approach is engineered. For instance, a common criticism of Zachman approach is that the model is that it is hard to define a relative business scope, which is suitable to I.T expectations. In fact, in most cases, the business scope will be naturally concerned in enhancing the establishment of influencers in a collective effort to minimize the organizational problems. Unno and Hosaka (1994, pp. 402) suggests that a business scope defines who, what, and when to address the organizational questions on spheres located within the reach of assets and operations.

Significance of Zachman's approach

Zachman's approach in relation to Enterprise architecture planning (EAP) is collective in modern business environment. In today's corporate world, focus is significantly shifting from EAP represents a distinct departure from the technically oriented architectures formally practiced in previous years. According to Zachman (1999), the information system can be approached from several perspectives applicable in addressing the complexity of system planning, design, and configuration. It is appropriate to consider Zachman's approach imperative since the author applied the aircraft and construction industry to enroll a comprehensive and intuitive approach of documenting the entire information systems architecture (Solotruk & Kristofi?, 1980).

In this regard, Zachman's ISA framework provides the development of a composite product. The approach seeks the application of relational database that seeks to examine artifacts of line managers. These are how, what, who, when and why. Zachman's approach is relative and realistic since it has managed to influence a number of different EA frameworks and writings on the EA, to include the development of a framework and textbook. The basic ISA approach seeks to integrate the concept of I.T security and implicit on each of the named artifacts. This approach is relevant to any industry since it addresses traditional and contemporary I.T management problems (Bowman, Godfrey, & Holt, 2000).

However, Zachman's approach lacks consistent validity. Several critics have argued that Zachman approach lacks proper consistency between business and technology as a subsequent problem. However, Simsion (2005) argues that the system lacks elegance and generality in how it deals with different data models. Simsion further introduces a parallel system from that one of Zachman's.

The model attempts to look at the possibility of warranting the imminent application of the assumption. In addition, examining the nature of correctness and the nature of the framework is essential. Secondly, this analysis looks on the ability of building metaphors or plausibility. Ideally, Zachman's system has been criticized because of the high chances of failure. In vital situations, it is imperative to acknowledge that there is a derivative necessity to ensure that data management among practitioners is successful (Unno and Hosaka, 1994).

Simsion Research Design (Data modeling)

In response to Zachman's approach, Simsion proposes the application of data modeling and research design and attempts to justify why this approach in responsive to business challenges. Simsion concludes that it is an implicit assumption compared to the previous system. In fact, Simsion is compelled by the knowledge that data modeling is responsive since it integrates the concept of discipline in the general analysis. Simsion seeks to respond to general assumptions of modeling research and data development design, rather than limiting an approach to business-oriented technology model (Bigot et al. 2006).

It should be noted that although Zachman's approach sought to apply business and management approach in treating data modeling, a relative impetus limiting the application of design lacking relative solutions is evident. In a nonprofessional approach, one might mistake Simsion's approach to base itself on a software engineering principle. However, it should be noted that the later development of software development ultimately triggered a more coherent approach in dealing data management. While the top organization provides limelight on what should be done to deal with data management, it should be noted that the patterns being discussed in by Simsion are near maturity. For example, common organizations naturally pursue the usage of Business Enterprise Systems, which are large software. Recently, (many years after Zachman) it has become a tradition to apply I.T software management in almost all sections of management. The application of software tablets and the recent the personal cloud computing tops the list. It is better to consider Simsion's approach as the appropriate strategy than Zachman (Unno and Hosaka, 1994).

As part of the validation, Simson suggests the application of quality data models as those based on the theoretical base of the data-management framework. Simson combined the application of field and laboratory research methodologies to reengineer application development build quality analysis and investigate the relative differences between data produced by experts and novices. In one of Simsion experiment, it should be noted that the experiments were passed by usage single right answer assumption. There is an unusual but practical framework practice incorporating a holistic approach measuring subjective judgments and retaining data quality.

Further research

While developing later editions in relation to… [END OF PREVIEW]

Four Different Ordering Options:

Which Option Should I Choose?

1.  Buy the full, 6-page paper:  $28.88


2.  Buy + remove from all search engines
(Google, Yahoo, Bing) for 30 days:  $38.88


3.  Access all 175,000+ papers:  $41.97/mo

(Already a member?  Click to download the paper!)


4.  Let us write a NEW paper for you!

Ask Us to Write a New Paper
Most popular!

Information Systems and Digital Workplace Essay

Managing Information Systems Introduction in the Contemporary Case Study

Information Systems Have Changed Essay

Net Centric Computing and Information Systems Case Study

Architecture H-Project Dome of Florence Cathedral Research Paper

View 463 other related papers  >>

Cite This Article Review:

APA Format

Understanding Information Systems Architecture.  (2014, May 9).  Retrieved June 17, 2019, from

MLA Format

"Understanding Information Systems Architecture."  9 May 2014.  Web.  17 June 2019. <>.

Chicago Format

"Understanding Information Systems Architecture."  May 9, 2014.  Accessed June 17, 2019.