![](bg9.png)
3. Cook, M. (1996). Building Enterprise Information Architectures: Reengineering Informa-
tion Systems. Prentice Hall, New York.
4. Descartes, R. (1994). Discourse on Method. Everyman.
5. DoD (2007). Dod architecture framework version 1.5. Technical report, Washington DC.
6. Ernst, A. M., Lankes, J., Schweda, C. M., and Wittenburg, A. (2006). Tool support for
enterprise architecture management - strengths and weaknesses. In EDOC ’06: Proceedings
of the 10th IEEE International Enterprise Distributed Object Computing Conference, pages
13–22, Washington, DC, USA. IEEE Computer Society.
7. Gadamer, H.-G. (2005). Truth and Method. Continuum, New York.
8. Gigch, J. P. V. and Pipino, L. L. (1986). In search for a paradigm for the discipline of
information systems. Future Computing Systems, 1(1):71–97.
9. Harmon, P. (2003). Developing an enterprise architecture. Technical report,
www.Bptrends.com.
10. Heidegger, M. (2008). Being and Time. Harper Perennial Modern Classics, San Francisco.
11. Hirschheim, R. (1985). Information systems epistemology: an historical perspective, pages
13–35. North-Holland Publishers, Amsterdam.
12. Hume, D. (1962). On human nature and the understanding. Macmillan, New York.
13. Husserl, E. (2001). Logical Investigations. Routledge, London.
14. Kappelman, L. A. (2007). Enterprise architecture not just another management fad. Align
journal.
15. Kappelman, L. A. and Salmans, B. (2007). Information management practices survey 2007
preliminary report: The state of ea: Progress, not perfection.
16. Kuhn, T. S. (1996). The Structure of Scientific Revolutions. University Of Chicago Press,
Chicago, 3 edition.
17. Lankhorst, M. (2005). Enterprise architecture at work - Modelling, communication and
analysis. Springer-Verlag, Heilderberg.
18. Locke, J. (1994). An Essay Concerning Human Understanding. Prometheus Books, London.
19. Morville, P. and Rosenfeld, L. (2006). Information Architecture fot the Word Wide Web.
OReilly, Sebastopol.
20. open Group, T. (2009). Togaf - version 9 enterprise edition. Technical report, San Francisco.
21. Rood, M. (1994). Enterprise architecture: definition, content, and utility. In Third Workshop
on Enabling Technologies: Infrastructure for Collaborative Enterprises, pages 106–111, New
york. IEEE.
22. Rosenfeld, L. (2007). Enterprise information architecture: Because users do not care about
your org chart.
23. Ross, J. W., Weill, P., and Robertson, D. (2006). Enterprise Architecture As Strategy: Cre-
ating a Foundation for Business Execution. Harvard Business School Press, Boston.
24. Schekkerman, J. (2009). Enterprise architecture tool selection guide. Technical report.
25. Strano, C. and Rehmani, Q. (2007). The role of the enterprise architect. Information Systems
and E-Business Management, 5(4):379–396.
26. Vernadat, F. (1996). Enterprise Modeling and Integration: Principles and Applications.
Springer, New york.
27. Vernadat, F. (2007). Interoperable enterprise systems: Principles, concepts, and methods.
Annual Reviews in Control, 31(1):137–145.
28. Vernadat, F. B. (2002). Enterprise modeling and integration (emi): Current status and re-
search perspectives. Annual Reviews in Control, 26(1):15–25.
29. Vita, L. W. (1965). Introducao a filosofia. Editora Atlas, So Paulo, 2 edition.
30. Winter, R. and Schelp, J. (2008). Enterprise architecture governance: the need for a business-
to-it approach. In Proceedings of the ACM symposium on Applied computing, pages 548–
552, New York, NY, USA. ACM.
31. Zachman, J. (1987). A framework for information systems architecture. IBM Systems
Journal, 26(3).
15