27.06.2013 Views

Information and Knowledge Management using ArcGIS ModelBuilder

Information and Knowledge Management using ArcGIS ModelBuilder

Information and Knowledge Management using ArcGIS ModelBuilder

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Thanos Magoulas, Aida Hadzic, Ted Saarikko <strong>and</strong> Kalevi Pessi<br />

It also bears mentioning that the Sc<strong>and</strong>inavian school of thought carries with it explicit consideration<br />

of alignment between the hard & soft aspects (please see figure 2) of design in general <strong>and</strong> EA in<br />

particular. Yet practical examples of architectures that align hard <strong>and</strong> soft aspects can also be found<br />

within international companies such as Xerox (Howard 1992).<br />

Figure 2: The hard & soft aspects of the architecture<br />

5. Conclusions<br />

The primary aim of this inquiry has been: How are the various forms <strong>and</strong> aspects of architectural<br />

alignment treated by the investigated approaches to Enterprise Architecture? This issue has been<br />

investigated with respect to socio-cultural, socio-structural, functional, infological <strong>and</strong> contextual<br />

alignment. Our study has provided us with the following conclusions:<br />

Firstly, our investigation clearly demonstrates that approaches to Enterprise Architecture provide<br />

guidance for socio-structural <strong>and</strong> functional alignment, but less so for infological or socio-cultural<br />

alignment. A possible explanation may be that investigated approaches follow a paradigm that<br />

dem<strong>and</strong>s the independence of information <strong>and</strong> information systems from, cognitive, organizational<br />

<strong>and</strong> technological aspects, (as explained by Brancheau, J.C <strong>and</strong> Wetherbe, J.C, (1986)). Another<br />

interpretation of the same issue is that investigated approaches are derived from a tradition of<br />

engineering design rather than architectural design. This would account for the focus on requirements<br />

<strong>and</strong> constraints found in the “hard” aspects of the enterprise, rather than the “softer” aspects such as<br />

goals <strong>and</strong> decision making that characterizes architectural design.<br />

Secondly, the area of contextual alignment is described by all investigated approaches as being free<br />

from barriers in general <strong>and</strong> functional barriers in particular. Some – but not all – forms of contextual<br />

alignment are established through contractual agreements. This is presumably in response to the<br />

heterogeneity inherent to most environments. Some approaches explicitly mention the requisite to<br />

respect regulations <strong>and</strong> laws.<br />

Finally, none of the investigated approaches discuss the mutual interdependence that exists between<br />

the various forms of alignment. However, the architectural patterns of the enterprise are the result of<br />

organizational forces rather than rationality. This follows previous research by Mintzberg (1989).<br />

References<br />

Ackoff, R. L. (1967) <strong>Management</strong> Misinformation Systems. <strong>Management</strong> Science,Vol. 4, No. 4.<br />

Argyris, C. (1980) Some Inner Contradictions in <strong>Management</strong> <strong>Information</strong> Systems. I H. Lucas, F. L<strong>and</strong>, T.<br />

Lincoln och K. Supper, red. The <strong>Information</strong> Systems Environment, North-Holl<strong>and</strong>.<br />

329

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!