Using a combined SOA and TOGAF environment for increased productivity, Part 1: Introduction to the TOGAF Enterprise Continuum
From the developerWorks archives
Date archived: May 14, 2019 | First published: December 10, 2009
Service-oriented architecture (SOA) can transform organizational silos into functional groups, thereby measurably increasing productivity. At present, both the Open Group Architecture Framework (TOGAF) and SOA are unapproachable and poorly understood. To succeed, a technology must at minimum offer two things; a reference topology (the defining structure) and a reference implementation flow (the defining sequence). These artifacts must always be at hand before, during, and after a project, because they offer a primary point of reference for planning, design, implementation, maintenance, and optimization methods. Part 1 and Part 2 of this three-part series attempt to recreate the noted structures for TOGAF and SOA, respectively. Part 3 follows up with an agile process that projects both frameworks against the same wall and offers methods to exploit the unique features that TOGAF and SOA have to offer.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.