JSEA  Vol.5 No.1 , January 2012
Pattern-Oriented Approach for Enterprise Architecture: TOGAF Framework
ABSTRACT
Design pattern suggests that developers must be able to reuse proven solutions emerging from the best design practices to solve common design problems while composing patterns to create reusable designs that can be mapped to different types of enterprise frameworks and architectures such as The Open Group Architecture Framework (TOGAF). Without this, business analysts, designers and developers are not properly applying design solutions or take full benefit of the power of patterns as reuse blocks, resulting in poor performance, poor scalability, and poor usability. Furthermore, these professionals may “reinvent the wheel” when attempting to implement the same design for different types of architectures of TOGAF framework. In this paper, we introduce different categories of design patterns as a vehicle for capturing and reusing good analyses, designs and implementation applied to TOGAF framework while detailing a motivating exemplar on how design patterns can be composed to create generic types of architectures of TOGAF framework. Then, we discuss why patterns are a suitable for developing and documenting various architectures including enterprise architectures as TOGAF.

Cite this paper
M. Taleb and O. Cherkaoui, "Pattern-Oriented Approach for Enterprise Architecture: TOGAF Framework," Journal of Software Engineering and Applications, Vol. 5 No. 1, 2012, pp. 45-50. doi: 10.4236/jsea.2012.51008.
References
[1]   Institute for Enterprise Architecture Developments, 2011. http://www.enterprise-architecture.info/

[2]   R. E. Giachetti, “Design of Enterprise Systems, Theory, Architecture, and Methods,” CRC Press, Boca Raton, 2010.

[3]   P. Weill, “Innovating with Information Systems: What Do the Most Agile Firms in the World Do?” 6th e-Business Conference, Barcelona, 2007.

[4]   Enterprise Architecture Center of Excellence, 2011. http://eacoe.org/index.shtml

[5]   J. W. Ross, P. Weill and D. C. Robertson, “Enterprise Architecture as Strategy,” Harvard Business Press, Boston, 2006.

[6]   J. A. Zachman, “A Framework for Information Systems Architecture,” IBM Systems Journal, Vol. 26, No. 3, 1987, G321-5298. doi:10.1147/sj.263.0276

[7]   Open Group, 2008. http://pubs.opengroup.org/architecture/togaf9-doc/arch/index.html

[8]   C. Alexander, S. Ishikawa, M. Silverstein, M. Jacobson, I. Fiskdahl-King and S. Angel, “A Pattern Language,” Oxford University Press, New York, 1977.

[9]   F. Buschmann, “What is a Pattern?” Object Expert, Vol. 1, No. 3, 1996, pp. 17-18.

[10]   J. Tidwell, “Common Ground: A Pattern Language for Human-Computer Interface Design,” 1997. http://www.mit.edu/~jtidwell/common_ground.html

[11]   T. Coram and J. Lee, “Experiences—A Pattern Language for User Interface Design,” 1998. http://www.maplefish.com/todd/papers/experiences

[12]   M. V. Welie, “The Amsterdam Collection of Patterns in User Interface Design,” 1999. http://www.cs.vu.nl/~martijn/patterns/index.html

[13]   E. Gamma, R. Helm, R. Johnson and J. Vlissides, “Design Patterns: Elements of Reusable Object-Oriented Software,” Addison-Wesley, Reading, 1995.

[14]   Dave Hornford, SOA/TOGAF Tutorial, 2010. https://www.opengroup.org/conference-live/uploads/40/22062/hornford.pdf

[15]   F. J. Budinsky, M. A. Finnie, J. M. Vlissides and P. S. Yu, “Automatic Code Generation from Design Patterns,” IBM Systems Journal, Vol. 35, No. 2, 1996, pp. 151-171. doi:10.1147/sj.352.0151

 
 
Top