TREEAD - A Tool that Enables the Re-use of Experience in Enterprise Architecture Description

Paulo Tomé, Luís Amaral, Ernesto Costa

Abstract

Enterprise Architecture (EA) is an important organization issue. The EA, resulting from a development process, is an important tool in different situations. It is used as a communication tool between the systems stakeholders. It is an enabler of changes. More importantly, the EA definition allows the build of unifying or coherent forms or structures. There has been growing interest in this topic topic area in recent years. Several authors have proposed methods, frameworks, languages with the aim of helping organizations in the process of EA definition. This paper proposes a software tool that can be used to re-use experience in EA definition processes. The tool proposed is independent of the framework, method, language or software tool used in the EA description process.

References

  1. Aamodt, A. and Plaza, E. (1994). Case-based reasoning: Foundational issues, methodological variations and systems approaches. AI-Communications, 7(1):39- 52.
  2. Agilense (2007). Agilense enterprise architecture frameworks.
  3. Ahmed, M., Garret, C., FairCloth, J., and Payne, C. (2002). ASP.NET Web Developers's Guide. Syngress Publishing.
  4. Alamos, L. (1994). Information architecture: The foundation. Technical report, Los Alamos National Laboratory.
  5. Amdahl, G. M., Blaauw, G. A., and Brooks, F. P. (1964). Architecture of the ibm system/360. IBM Journal, 8(2):87-101.
  6. Barker, R. (1995). Case*Method - Entity Relationship Modelling. Addison-Wesley.
  7. Barker, R. and Longman, C. (1992). Case*Method - Function and Process Modelling. Addison-Wesley.
  8. Bernus, P., Mertins, G., and Schmidt, G. (1998). Handbook On Architectures of Information Systems. SpringerVerlag.
  9. Boar, B. H. (1999). Constructing Blueprints for Enterprise IT Architectures. John Wiley & Sons, Inc.
  10. Capgemini (2006). Architecture and the integrated architecture framework. Technical report, Capgemini - Consulting, Technology, Outsourcing. www.capgemini.com, Consulted in October 2007.
  11. Chaiyasut, P. and Shanks, G. (1994). Conceptual data modelling process: A study of novice and expert data modellers. In Halpin, T. and Meersman, R., editors, First International Conference on Object-Role Modelling, pages 310-323, Brisbane - Queensland.
  12. Chapin, N. (1970). Flowcharting with the ansi standard: A tutorial. Computing Surveys, 2(2).
  13. Chen, P. P.-S. (1976). The entity-relationship model - toward a unified view of data. ACM Transactions on Database Systems, 1(1):9-36.
  14. CIO (1999). Enterprise architecture conceptual framework. Technical report, CIO Council. Federal Conceptual Model Subgroup.
  15. Earl, M. J. (1989). Management Strategies For Information Technology. Prentice Hall.
  16. EE (2005). Repository-centric enterprise architecture. white paper.
  17. Eertink, H., Janssen, W., and Luttighuis, P. O. (1999). A business process design language. In World Congress on Formal Methods in Development of Computing Systems, pages 708-727, Toulose - France. Springer.
  18. Gane, C. and Sarson, T. (1979). Structured Systems Analysis: Tools and Techniques. Prentice-Hall.
  19. GAO (2006). Enterprise architecture: Leadership remains key to establishing and levearing architectures for organizational transformation. Technical report, Chairman, Committee on Governmentm Reform, House of Representatives.
  20. Garlan, D., Allen, R., and Ockerbloom, J. (1995). Architectural mismatch: Why resuse is so hard. IEEE Software, 12(6):17-26.
  21. Gore, M. (2003). Thoughs on the information system architect role. In ITC'03, pages 706-710. IEEE - Computer Society.
  22. Group, O. (2002). The open group architectural framework. Technical report, The Open Group. Verso 8.
  23. Handler, R. (2007). Closing the gap between architecture and model-driven development. In Gartner Enterprise Architecture Summit, London, UK. Gartner.
  24. IBM (1984). Business Systems Planning: Information Systems Planning Guide. IBM Corperation.
  25. IBM (1995). Information Framework (IFW) Description. IBM, 1.02 edition.
  26. IEEE (2000). IEEE Recommended Practice for Architectural Description of Software-Intensive Systems. IEEE.
  27. IFEAD (2005). Trends in enterprise architecture 2005: How are organizations progressing.
  28. IFEAD (2007). Enterprise architecture tools review. www.enterprise-architecture.info/EA tools.htm, Consulted at 27-12-2007.
  29. Isaac, J. C. and Leroy, D. (1994). The amos study: Toward a user validation of the cis architecture design. In BRG Symposium on C2 Research, California.
  30. Isaac, J. C. and Leroy, D. (1995). Architecture modeling for better requirements and system specification. In First International Symposium on Command and Control Research and Technology, Washington D. C.
  31. ISO/IEC (1998). Information technology - open distributed processing - reference model: Overview.
  32. Kim, Y. G. and Everest, G. C. (1994). Building an is architecture collective wisdom from the field. Information & Management, 26:1-11.
  33. Lankhorst, M., Iacob, M., Jonkers, H., Torre, L., Proper, H., Arbab, F., Boer, F., Bonsangue, M., Hoppenbrouwers, S., Zanten, G., Groenewegen, L., Buuren, R., Slagter, R., Campschoer, J., Arbab, F., Steen, M., Stam, A., Wieringa, R., Eck, P., Krukkert, D., Doest, H., Leeuwen, D., Fennema, P., Bosma, H., Cuvelier, M., Penders, P., Bekius, S., and Janssen, W. (2005).
  34. Lankhorst, M., Jonkers, H., Buuren, R., Leeuwen, D., and Doest, H. (2004). Enterprise architecture modelling - the issue of integration. Advanced Engineering Informatics, 18(4):205-216.
  35. Lloyd-Williams, M. (1994). Expert system support for object-oriented database design. International Journal of Applied Expert Systems, 1(3).
  36. Maier, M. W. (1996). Systems architecting: An emergent discipline? In IEEE Aerospace Applications, volume 3, pages 231-246.
  37. McDavid, D. W. (1999). A standard for business architecture description. IBM Systems Journal, 38(1):12-31.
  38. Medvidovic, N. and Taylor, R. N. (2000). A classification and comparison framework for software architecture description languages. IEEE Transactions on Software Engineering, 26(1):70-93.
  39. Microsoft (1999). Microsoft solutions framework. White Paper.
  40. NIH (2007). Nih enterprise architecture framework. Technical report, National Institutes of Health.
  41. NIST (1989). Information management directions: The integration challenge. Technical report, Institute of Standards and Technology.
  42. Nolan, R. L. and Mulryan, D. W. (1987). Undertaking an architecture program. Stage By Stage, 7(2).
  43. OMG (2004). Business process modeling notation specification. Technical report, Object Management Group.
  44. OMG (2007). Unified modeling language: Superstructure. Technical report, Object Management Group.
  45. Opdahl, A. L. (1996). A model of the is-architecture alignment problem. In Lind, M., Axelsson, K., Goldkuhl, G., and Hedberg, P., editors, VITS Autumn.
  46. Oracle (2007). www.oracle.com.
  47. Panet, G. and Letouche, R. (1994). Merise / 2: Modles et Techniques Merise Avancs. Les ditions D' Organisation.
  48. Rechtin, E. (1991). Systems Architecting: Creating & Building Complex Systems. Prentice Hall.
  49. Rechtin, E. (1999). Systems architecting of organizations: why eagles can't swim. CRC Press.
  50. Rechtin, E. and Maier, M. W. (1997). The Art of Systems Architecting. CRC Press.
  51. Rood, M. A. (1994). Enterprise architecture: Definition, content, and utility. In Third Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises, pages 106-111, Morgantown, USA. IEEE.
  52. Ryan, H. and Santucci, J. (1993). Building an enterprise information architecture. Infoworld, pages 57-58.
  53. Scheer, A.-W. (1998). ARIS - Business Process Frameworks. Springer-Verlag, 2l edition.
  54. Scheer, A.-W. (1999). ARIS - Business Process Modeling. Springer-Verlag, 2l edition.
  55. SEI (2003). How do you define software architecture - www.sei.cmu.edu/architecture/definitions.html. Consulted in 1-07-2003.
  56. Shah, H. and Kourdi, M. E. (2007). Frameworks for enterprise architecture. IT PrO, September - October:36- 41.
  57. Spewak, S. H. and Hill, S. C. (1995). Enterprise Architecture Planning, Developing a Blueprint for Data, Applications and Technology. John Wiley & Sons, Inc.
  58. Stecher, P. (1993). Building business and application systems with retail application architecture. IBM Systems Journal, 32(2):278-306.
  59. Sybase (2006). www.sybase.com/products/.
  60. Sykes, J. B. (1991). The Concise Oxford Dictionary. Oxford University Press.
  61. Tan, P. N., Steinbach, M., and Kumar, V. (2006). Introduction to Data Mining. Pearson Education.
  62. Tandon, R. (2007). The role of solution architects in systems integrations. IT PrO, March, April:26-33.
  63. Tapscott, D. and Caston, A. (1993). Paradigm Shift: The New Promise of Information Technology. McGrawHill.
  64. Targowski, A. S. (1996). Global Information Infrastructure: the Birth, Vision and Architecture. Idea Group Publishing.
  65. Tauzovich, B. (1990). An expert system for conceptual data modelling. In 8th International Conference on the Entity-Relationship Approach, Toronto, Canada.
  66. TEAF (2000). Treasury enterprise architecture framework. Technical report, Department of Treasury.
  67. Technology, N. I. S. (1993). Integration Definition for Function Modeling (IDEF0). Federal Information Processing Standards Publications.
  68. Wilhelm, R. and Maurer, D. (1996). Compiler Design. Addison-Wesley.
  69. Zachman, J. A. (1987). A framework for information systems architecture. IBM Systems Journal, 26(3):276- 292.
  70. Zachman, J. A. and Sowa, J. F. (1992). Extending and formalizing the framework for information systems architecture. IBM Systems Journal, 31(3):590-616.
  71. Zwegers, A. (1998). On Systems Architecting - a study in shop floor control to determine architecting concepts and principles. Ph.d thesis, Technische Universiteit Eindhoven. ISBN 90-386-0699-4.
Download


Paper Citation


in Harvard Style

Tomé P., Amaral L. and Costa E. (2010). TREEAD - A Tool that Enables the Re-use of Experience in Enterprise Architecture Description . In Proceedings of the 12th International Conference on Enterprise Information Systems - Volume 2: ICEIS, ISBN 978-989-8425-05-8, pages 332-343. DOI: 10.5220/0002975003320343


in Bibtex Style

@conference{iceis10,
author={Paulo Tomé and Luís Amaral and Ernesto Costa},
title={TREEAD - A Tool that Enables the Re-use of Experience in Enterprise Architecture Description},
booktitle={Proceedings of the 12th International Conference on Enterprise Information Systems - Volume 2: ICEIS,},
year={2010},
pages={332-343},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0002975003320343},
isbn={978-989-8425-05-8},
}


in EndNote Style

TY - CONF
JO - Proceedings of the 12th International Conference on Enterprise Information Systems - Volume 2: ICEIS,
TI - TREEAD - A Tool that Enables the Re-use of Experience in Enterprise Architecture Description
SN - 978-989-8425-05-8
AU - Tomé P.
AU - Amaral L.
AU - Costa E.
PY - 2010
SP - 332
EP - 343
DO - 10.5220/0002975003320343