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

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.

[1]  John A. Zachman,et al.  A Framework for Information Systems Architecture , 1987, IBM Syst. J..

[2]  Gui Peng.  On the Building of Enterprise Information , 2007 .

[3]  Terry A. Kuykendall,et al.  Systems Architecting–Creating & Building Complex Systems , 2001 .

[5]  Graeme G. Shanks,et al.  Conceptual Data Modeling Process: A Study of Novice and Expert Data Modellers , 1994, ORM.

[6]  Michael J. Earl,et al.  Management Strategies for Information Technology , 1989 .

[7]  John F. Sowa,et al.  Extending and Formalizing the Framework for Information Systems Architecture , 1992, IBM Syst. J..

[8]  Marc M. Lankhorst,et al.  Enterprise architecture modelling--the issue of integration , 2004, Adv. Eng. Informatics.

[9]  Peter Stecher,et al.  Building Business and Application Systems with the Retail Application Architecture , 1993, IBM Syst. J..

[10]  Young-Gul Kim,et al.  Building an IS architecture: Collective wisdom from the field , 1994, Inf. Manag..

[11]  Richard N. Taylor,et al.  A Classification and Comparison Framework for Software Architecture Description Languages , 2000, IEEE Trans. Software Eng..

[12]  Branka Tauzovich.  An Expert System for Conceptual Data Modelling , 1989, ER.

[13]  Marilyn Gore.  Thoughts on the information system architect role , 2003, Proceedings ITCC 2003. International Conference on Information Technology: Coding and Computing.

[14]  M. W. Maier.  Systems architecting: an emergent discipline? , 1996, 1996 IEEE Aerospace Applications Conference. Proceedings.

[15]  Ned Chapin,et al.  Flowcharting With the ANSI Standard: A Tutorial , 1970, CSUR.

[16]  Elizabeth N. Fong,et al.  Information management directions: the integration challenge , 1989, SGMD.

[17]  Frederick P. Brooks,et al.  Architecture of the IBM System/360 , 1964, IBM J. Res. Dev..

[18]  Andrew S. Targowski,et al.  Global Information Infrastructure: The Birth, Vision, and Architecture , 1996 .

[19]  Charles R. Thomas.  Information Architecture: The Data Warehouse Foundation. , 1997 .

[20]  Sharon A. White.  Business Process Modeling Notation Specification (Version 1.2, OMG Final Adopted Specification) , 2009 .

[21]  H. Shah,et al.  Frameworks for Enterprise Architecture , 2007, IT Professional.

[22]  Rakesh Tandon.  The Role of Solution Architects in Systems Integration , 2007, IT Professional.

[23]  Marc M. Lankhorst,et al.  Enterprise Architecture at Work - Modelling, Communication and Analysis, 2nd Edition , 2005, The Enterprise Engineering Series.

[24]  David Garlan,et al.  Architectural Mismatch: Why Reuse Is So Hard , 1995, IEEE Softw..

[25]  Melody A. Rood.  Enterprise architecture: definition, content, and utility , 1994, Proceedings of 3rd IEEE Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises.

[26]  D. W. McDavid,et al.  A Standard for Business Architecture Description , 1999, IBM Syst. J..

[27]  John A. Zachman,et al.  A Framework for Information Systems Architecture , 1987, IBM Syst. J..

[28]  Bernard H. Boar,et al.  Constructing Blueprints for Enterprise IT Architectures , 1998 .