TOGAF 9.1 Quick Start Guide for IT Enterprise Architects Wolfgang Keller
© 2009 Wolfgang W. Keller – all rights reserved
ii
Copyright and License Copyright©2009-2012byWolfgangW.Keller.Allrightsreserved The content of this book is protected under “AttributionNonCommercial NonCommercial-NoDeriv -NoDerivs3.0Unported”license s3.0Unported”license.Forthefulltextsee .Forthefulltextsee http://creativecommons.org/licenses/by-nc-nd/3.0/legalcode .
Disclaimer Whil While e the the auth author or used used his his best best effo effort rts s in prepa prepari ring ng this this book, book, he makesnorepresentat makesnorepresentationsorwarrant ionsorwarrantieswithresp ieswithrespecttotheaccur ecttotheaccuracy acy or compl complet eten eness ess of the the conte content nts s of this this book book and speci specifi fical cally ly disdisclai claims ms any impl implie ied d warr warrant antie ies s of merch merchan anta tabi bili lity ty or fitn fitness ess for for a particularpurpose.Theadviceorstrategiescontainedhereinmaynot besuitableforyoursituati besuitableforyoursituation.Youshould on.Youshouldconsultwithaprofe consultwithaprofessional ssional whereappropriate.Theauthorshallnotbeliableforanylossofprofit oranyothercommercialdamages,includingbutnotlimitedtospecial,incidental,consequentialorotherdamages.
Cover Picture By Wolfga Wolfgang ng Keller Keller © 2009 2009 – all rights rights reserve reserved. d. Locati Location: on: Berlin; Berlin; Hacke’scherMarkt;ReflectionofBerlinTVTower.
Version History D a te
State and Purpose
2012-04-19 thru 24
First Version for TOGAF 9.1 based on version for
2012-12-13
TOGAF 9.0
© 2009-2012 Wolfgang W. Keller – all rights reserved
iii
Preface Why Why woul would d anybo anybody dy need need a60 pagesshor pagesshort t book book on TOGAF TOGAF 9.1 9.1 if TOGA TOGAF F itse itself lf is a 690 690 page pages s arch archit itec ectu ture re fram framew ewor ork, k, writ writte ten n by renownedexpertsfrom300topITcompanieswhosureknowtheir stuffand stuffand willprovid willprovide e youwith anythin anything g you need asan enterpr enterprise ise architect? Theansweris:YES–TOGAF9.1providesyouwit Theansweris:YES–TOGAF9.1providesyouwithveryhelpf hveryhelpful,very ul,very soundand soundand extensi extensivelists velists ofWHATto doin Enterpri EnterpriseIT seIT Archite Architeccture.TheadvicefromvariouspeopleworkinginEnterpriseITArchitectureis:UseTOGAF!There’snoreasonnottouseit. But TOGAF does not yet provide you with a QuickStart and Acceleratorstha AcceleratorsthatgiveanExper tgiveanExpertafasttoreadbal tafasttoreadballpark lparkviewofwhich viewofwhich itemsof itemsof anIT enterpr enterprisearch isearchite itect’ ct’stasklistarecovere stasklistarecoveredby dby TOGAF TOGAF andwhicharenot.Andasyouwillalsosee,thereareareasofanIT EnterpriseArchitect’stasklistwhicharenotcoveredbyTOGAFatthe moment.Thismakesitarewardingtasktogivepeopleinterestedin TOGAFanideaofwhattheycanexpectandwhattheyhavetofind elsewhere.
© 2009-2012 Wolfgang W. Keller – all rights reserved
iv
About the Author WolfgangKellerisafreelanc WolfgangKellerisafreelanceconsultan econsultant t who who has has Enterp Enterpri rise se IT Archi Archite tect ctur ure e as his his prof profes essi sion onal al hobb hobby. y. Unti Until l 2006 2006 he usedtoworkforoneofthetop5insurersworldwideas ersworldwideas aChiefArchite aChiefArchitectfirst ctfirst fortheirAustrianandCEEbusinessand laterfortheirGermanbusinessgeneratingaround 13BillionEuro 13BillionEuro ininsurance ininsurance premiums. Wolfganghasdoneworkinthefield of softwar software e archite architectu cture re since since the term term wascoined wascoined bythe CMU SEI inthe early early 1990ti 1990ties. es. Besides Besides softwar software e archite architectu cture re he was was alwa always ys in larg large e scal scale e soft softwa ware re project project managem management ent.. Atthe momenthe momenthe worksas worksas aprojectmanage aprojectmanagerdoing“honrdoing“honest est work work” ” ;-) ;-) whic which h has has noth nothin ing g to do withmethodsbuteverythingwithdelivery. Wolf Wo lfga gang ng hold holds s a Dipl Diplom om (M.S (M.S.) .) in compu compute ter r scien science ce from from Tech Technic nical al UniUnivers versit ity y Munic unich h (Ger (Germa many ny). ). He is the auth author or of numer numerou ous s arti articl cles es in Engli English sh andGermanlanguagetradejournalsand hasauthoredtwoGermanbooks:Oneon Enterpri Enterprise se Applicat Application ion Integra Integratio tion n and another another one on Enterpr Enterprise ise IT Archite ArchitecctureManagement. Website: http://www.objectarchitects.biz/ E-Mail:
[email protected] E-Mail:
[email protected]
© 2009-2012 Wolfgang W. Keller – all rights reserved
v
Table of Contents 1
Introduction
1
1.1
What is TOGAF 9.1?
1
1.2
This Book is most useful for two Groups of Readers
2
1.3
Your Feedback Welcome
3
2 2.1
What is Enterprise IT Architecture?
4
ThePragmaticBusinessApproachtoEnterpriseIT Architecture
5
2.2
WorkBre WorkBreakd akdown ownSt Struc ructur turef efor orEnte Enterpri rpriseI seITA TArchi rchitec tectur ture e
7
2.3
The TOGAF 9.1 Approach
9
3
TOGAF and IT Strategy
12
3.1
What is an IT Strategy?
12
3.2
What needs to be described
13
3.3
How do you get there?
15
3.3.1 Strategic Dialog
15
3.3.2 IT Maxims from Business Maxims
16
3.3.3 Reengineering the Business Strategy
17
3.4
What support will you find in TOGAF?
18
3.5
Further Reading
18
4
TOGAF and IT Portfolio Management
20
4.1
What is IT Portfolio Management
20
4.2
What is Application Portfolio Management?
21
4.3
Putting it together: From Chaos to a Master Plan
24
4.4
WhatdoyoufindaboutApplicationPortfolioManagementin TOGAF? 26
4.5
Infrastructure Portfolio Management
4.6
WhatdoyoufindaboutInfrastructurePortfolioManagementin TOGAF? 27
4.7
Further Reading
5
TOGAF and Developing Architectures
26
28 30
5.1
Part II: TOGAF ADM
31
5.2
Part III: ADM Guidelines and Techniques
32
5.3
Further Reading
32
© 2009-2012 Wolfgang W. Keller – all rights reserved
vi
6
TOGAF and Architecture Governance
33
6.1
What do you find about it in TOGAF?
34
6.2
Further Reading
35
7
TOGAF and Basic Tasks
36
7.1
TOGAFandfindingtherightMeta-ModelforyourNeeds
36
7.2
TOGAF and finding Tool Support
37
7.3
TOGAFandImmersionPathsforEnterpriseITArchitectures 38
8
What else will you find in TOGAF?
40
8.1
FoundationArchitecture/TechnicalReferenceModel(TRM)40
8.2
TheIntegratedInformationInfrastructureReferenceModel (III-RM) 41
9
Wrap Up: TOGAF for You
42
9.1
A Collection of Useful Stuff
42
9.2
The Two Strongest Points
42
9.3
TOGAF Certification
43
9.4
Future
44
10
References
45
© 2009-2012 Wolfgang W. Keller – all rights reserved
1 Introduction
1
1.1
1
Introduction
What is TOGAF 9.1?
AtthepresenttimeTOGAF,theOpenGroupArchitectureFramework is a very popular framework for Enterprise IT Architecture (EITA) worldwide. Version9.1–theVersionreleasedinlate2011–isamaintenance Releaseofversion9.Version9,whichisaroundsince2009constitutedmajorreworkofVersion8.1.1.TOGAFVersion8.1.1wasthelatest update of the version 8 family which has been around since 2002, when the extensions for Enterprise IT Architecture were added to version7intheformofthesocalledenterprisecontinuum. LikemanyotherframeworksintheITarchitectureandmanagementarenaTOGAF9.1isnota“useitrightoutoftheboxitem”.Ithas some690pagesandisfirstofallamajorchallengetoread. Also,likemanyotherIT frameworks, TOGAF will tell you more aboutWHATtodothanHOWtodoit.Hence,whenyoustarte.g.a newjobasanEnterpriseArchitectandsomebodypassesyouacopy ofTOGAF9.1youmightnotreallyknowwhattodo,unlessyouhave hadsomeotherworkexperiencebesidesTOGAFandhavereadafew otherbooks. ThereisalsothecriticismthatTOGAFdoesnotprovideyouwith working examples, document templates and other quickstart tools. Providing such material would indeed be very tough,as processes, documentsand other material will differ depending on the kind of enterpriseforwhichyouhavetodevelopanarchitecture.Thegood newsisthatTOGAFprovidesyouwithveryusefulchecklistsandvery extensivemetamodels.Thebadnewsis,thatTOGAFwillnotprovide you with an idiot’s guide to Enterprise IT Architecture. Even with TOGAF you are still allowed and required to think. Such an idiot’s guidedoesnotyetexistanditisveryunlikelythatitwilleverexist. Anyapproximationtoitwouldconsistofthousandsofpages,would not be manageable and would be outdated by the time it was published. © 2009-2012 Wolfgang W. Keller – all rights reserved
1 Introduction
1.2
2
This Book is most useful for two Groups of Readers
Experienced EA Professionals who are not yet “deep into TOGAF”:WillgetaquickoverviewonwheretofindwhatinTOGAF 9.1 andwhereTOGAF 9.1 hasstillgapsifcomparedtoa tasklistof dailyEnterpriseITArchitecturework.Peoplefromthisgroupshould beabletoreadthebookinacursorystyleinsomethinglikeanhour. Whereveryouneeddetails,youcandiveintothemandifthisbookis notenoughyouwillgetapointerintotherespectiveTOGAFcontent. Tomakealongstoryshortforsuchreaders:TOGAFissoldtoyouasa framework for Enterprise IT Architecture or even Enterprise Architecture.Itisvery strongondevelopingarchitecturesbutitcan still be improvedif it comes to Enterprise IT Architecture Management (EAM). If you are an EAM expert and you know e.g. TOGAF 8.1.1 in detail, you are done here. TOGAF 9.1 is not much betterat ITEAManagamentthanTOGAF8.1.1usedto be–butitis stronger onEA Development than 8.1.1 used to be. You can goon flipping through the book in order to draw some hints from the checklistsandfurtherreadingsectionsthatyoumightnothavecome acrossbefore. People new to Enterprise IT Architecture and interested in TOGAF:WillgetaballparkviewofwhattoexpectfromTOGAFand whatnottoexpectfromTOGAF.Youwillbeguidedthroughaprocess frameworkfordaytodayarchitecturalworkprovidingyouwithan overview of architectural work as a whole and you will get informationonwhichoftheseprocessesaresupportedbyTOGAF9.1. Thebenefitforbothoftheabovegroupsofreadersisthattheyshould getanideaofhowtheycan profitfromTOGAFwayfasterthanby reading the full original text. But they will still not get real world examples and all the supporting materials that would pile up to anotherthousandormorepages. IfyouareanexperiencedTOGAFexpert thenyouwillfindthat this bookisnotwrittenwithyouasthetargetaudience inmind. A short note on TOGAF certification: Havingworkedthroughthis short book you will have learned that TOGAF certification can be useful toprove thatyoudid work throughTOGAFandthatyouunderstood the documents. TOGAF certification does not certify that youareaprofessionalEnterpriseITArchitect.EventhoughsomeHR departmentsmaybemadetobelievethisandeventhoughtheremay © 2009-2012 Wolfgang W. Keller – all rights reserved
1 Introduction
3
bevendorsforTOGAFcoursesouttherewhotellyouthis.Henceyou canalsousethisbooktofindoutquicklywhatTOGAFcouldgiveyou andwhetherornotyouthinkthatitworthtakingtheexam.
1.3
Your Feedback Welcome
Theauthoracknowledgesthatthisbookmightattractsomecritique fromexperiencedTOGAFacolytesandalsofrompeoplewhohavea marketingpitchthatsellsTOGAFasthe“onesizefitsall”solutionfor EnterpriseITArchitecture. AlsosomelessexperiencedEnterpriseITArchitectureprofessionals mightbelookingforthe“thousandpagestart-upmaterial”. Yourfeedbacktoimprovethisbookisverywelcome.Theversion youarecurrentlyreadinghasbeenwrittenwiththeintentionofsavingalotofpeoplealotofreadingtimeandalsotoconfirmforthem thattheystillhaveanappropriatenotionofEnterpriseITArchitecture Management even though they have the feeling that there is somethingmissingfromTOGAF. This book will be distributed free of charge over the Internet whileitisplannedthatthebookwilllaterbeusedaspartofaregular book.Feelfreetocontactmewithyoursuggestionsforimprovement.
© 2009-2012 Wolfgang W. Keller – all rights reserved
2 What is Enterprise IT Architecture?
2
4
What is Enterprise IT Architecture?
As with building architecture there are many many defintions of EnterpriseITArchitecture.Inthischapteryouwilllearntorecognise afewaccesspathstoEnterpriseITArchitectureandwewillgivea deeperexplanationofapragmaticaccesspaththatseesanEnterprise Architect as a very important aide to the CIO who is in charge, amongst other things, of strategic planning for the enterprise’s IT assets.We will call this the Pragmatic Business Approach. It will becomeclearer,onceweoutlinethetasksofanEnterpriseArchitect astopaidetotheCIO. Theothertwoapproachesare: TheIT-ArchitectureApproach:Thisapproachmainlyhasitsroots inITsystemsarchitecture.Thesystemsarchitectsoftengettobein chargeofasystemclusterorevenofawholeITlandscapeandhave triedtoevolvetheirsystemsarchitects’methodsforuseattheenterprise level. You will learn that both the Zachman Framework and TOGAFhavebeengreatlyinfluencedbythisapproach. TheAcademicApproach: Thisapproachfirstasks“whatisarchitecture of an enterprise” and then looks formethods for modeling an enterprise, constructing meta-models for an arbitrary enterprise, evolutionofmeta-modelsandsimilarquestions.Suchquestionsfocus onhowtomodelanenterprisefromtoptobottom. Inthischapterwewillexplainthethreeapproachesandwillposition TOGAF 9.1 with respect to their viewpoints. In the section on the PragmaticBusinessApproachyouwillbecomefamiliarwithalistof topleveltaskswhichwillbeusedlatertogiveyouanideaofwhich tasksaresupportedbyTOGAF9.1–andwhichareNOTsupportedby TOGAF9.
© 2009-2012 Wolfgang W. Keller – all rights reserved
2 What is Enterprise IT Architecture?
2.1
5
The Pragmatic Business Approach to Enterprise IT Architecture
The Pragmatic Business Approach to Enterprise IT Architecture startsbyasking“whatneedstobedonetomakethemostoftheenterprise resource IT”. In more educated circles this is called “IT / BusinessAlignment”.IT/Businessalignmentisnotafullydeterministictask.Thewayyoutrytopursueitdependsonthematuritylevel ofyourorganization.
Figure1:LevelsofIT/BusinessAlignment.
ThereisapredictablesetoftasksinaCIOofficethatservetogovern theexpensiveresourceITinanenterprise.Thedegreetowhichsuch aCIOofficehasimplementedthesedependsontheimportanceofthe productionfactorITfortheenterprise n
n
Anenterprise whichdeals with commoditygoodsand does not seeITassomekindoffactorrelevantforitsstrategicpositioning incompetitionwillseldom ever have a complex CIO office. Ifit evenhasaCIO. Amulti-billionbusinessrunninganITbudgetofseveralhundred millionEurosa yearwillhave all the functionsthat willbe outlinedhere–maybeevenmore.
InatypicalCIOofficeyouwillfindmoreorlesstheblocksoftasks outlinedin Figure 2. Only two ofthesehavesomething todo with EnterpriseITArchitecture.
© 2009-2012 Wolfgang W. Keller – all rights reserved
2 What is Enterprise IT Architecture?
6
Figure2:TaskblocksforaCIOOffice.Darkshadedtopicsarenotsub jectofEAMandwillhencenotbediscussedinthisbook
n
n
n
n
ITStrategy:Somebodyhastodefineastrategyforthemanagementoftheenterprise’sresourceIT. Project Portfolio Management: Budgets for IT have been aroundmuchlongerthanITprojectarchitectureorevenEnterprise IT Architecture.That’s why a manager like a CIOused to have somebody incharge ofhis ITbudget and the balancingof budgetanddemandsthatresultsinthelistofdemandswhichare tobeimplementedeachyear. EnterpriseITArchitecture: WewillexplainthetasksanEnterpriseITArchitecthastoperforminsection2.2. IT Audit: Asthe ITfunctionis crucial tothe success and sheer existenceofmostenterprisestoday,ITissubjecttoauditsinmost organizations.HencethereisatasktoauditITfunctions.Today’s defactostandardforauditingITisCOBIT.Wewillnotdrillinto thisanydeeperasitwillnothelpyoutoomuchinunderstanding TOGAF.
© 2009-2012 Wolfgang W. Keller – all rights reserved
2 What is Enterprise IT Architecture?
n
n
7
IT Security: is crucial today for the reputation, integrity and security of your enterprise. Hence a CIO will have people in chargeof ITsecurity. There’s also a broad arrayof frameworks thatwillhelp youmanageIT security.Wewillalsoskip thisaspectforthetimebeing Provider Management: Most ITorganizations todayoutsource orouttaskalotoftheirwork.Thiscanapplytoalmostalltasksan IT organization performs, except the core management tasks. Thesecoretasksare,bytheway,describedhereforaCIOoffice.
IntheremainderofthisbookwewillbedealingwiththeITStrategy andtheEnterpriseITArchitectureblocks.VeryoftentheEnterprise ITArchitect,asaCIO’stopaide,willhelphimdefinetheenterprise’s ITStrategy.Inanycase,EnterpriseStrategyandhenceITStrategyare the most important influences for you as an Enterprise Architect, evenifyourCIOdoesnotconsultyouaboutformulatingthem. This and the elements of EnterpriseArchitectural work will be described in section2.2. The structure explained here will be used laterin chapters3 thru 7 toexplain what isin TOGAFto help you accomplishyourtasksasanEnterpriseArchitect.
2.2
Work Breakdown Structure for Enterprise IT Architecture
ThetasksofEnterpriseITArchitecturecanbesplitintothreemain blocksasoutlinedinFigure Figure3 . n
StrategicTasks:OftentheEnterpriseITArchitectsarethepeople who help a CIO develop his IT Strategy . But besides this therearemorestrategictasks–meaningtasksthathaveaplanninghorizonof more than3-5years. ITPortfolioManagement willdeliverthebasicdataneededfor Strategic Planning, which brings together the goals from strategy and the as-is situation fromportfoliomanagementinordertodevelopato-besituation. Thiswillbeunderpinnedbyastrategicroadmapthatisacoarse programplanforamajorpartoftheprojectportfolio.
© 2009-2012 Wolfgang W. Keller – all rights reserved
2 What is Enterprise IT Architecture?
8
Figure3:EnterpriseArchitectsProcessMap n
n
OperationalTasks: formthedaytodayworkofEnterpriseIT Architects. Strategies are nice – but you need to communicate themand you also haveto makesurethatthey are appliedand implemented.Thisisthefieldof Architecture Governance .First ofallyouwill need tofind critical projects– the ones thathave thepotentialtochangeyourarchitecture.Thisis donebyMonitoringtheProjectPortfolio .Onceyouhaveidentifiedthe10%or so interesting strategic projects, you will set up an architects teamto accompanythem . As they run through the enterprises normalITProjectProcess . BasicTasks: In orderto get Enterprise ITArchitecture upand runningyouwillneedtocreateafewfoundations.Inmanycases itwillbeusefulto runanEAtool inordertohaveachanceto trackwhatyouhaveinyourapplicationandinfrastructureportfolios. Inorder to do thisyou will need to findor develop the right metamodel f orthepurposesandin ordertoreduce complexity by standardization you willfirst haveto developstandardsthatwillbevalidinthescopeofyourenterprise.Thereare morebasictasks–butthesearethemostprominentones.
Thefollowingwillexplaineachofthetaskslistedaboveandinchapters3thru7youcanfindwhatmaterialisavailableinTOGAFtohelp youperformthem.
© 2009-2012 Wolfgang W. Keller – all rights reserved
2 What is Enterprise IT Architecture?
2.3
9
The TOGAF 9.1 Approach
Let’shave a look athow TOGAF sees its approach toEnterprise IT Architecture.BestletTOGAFspeakforitself: TOGAF as an EAM Framework (From TOGAF 8.1. (Enterprise Edition) TOGAF in its Enterprise Edit ion remains what it has always been, namely an architecture framework - a set of methods and tools for developing a broad range of different IT architectures. It enables IT users to design, evaluate, and build the right architecture for their organization, and reduces the costs of planning, designing, and implementing architectures based on open systems solutions. The key to TOGAF remains a reliable, prac tical method - the TOGAF Archit ecture Development Method (ADM) - for defining business needs and developing an architecture that meets those needs, utilizing the elements of TOGAF and other architectural assets available to the organization. Source TOGAF 8.1. [TOGAF8.1.1] (Also valid for TOGAF 9.x)
SowhatdoesthistelluswithregardstoEnterpriseITArchitecture tasks as described in section 2.2? The emphasis of TOGAF is on developingconcreteITarchitectures :Beitforasystem,beitfora clusterofsystemsandmaybealsobeitforato-bearchitectureofan enterpriseasawhole.Hencetheemphasisisontheconcretetaskof developingarchitecture.
© 2009-2012 Wolfgang W. Keller – all rights reserved
2 What is Enterprise IT Architecture?
10
Figure4:EvolutionofTOGAFfromVersion7toVersion9.Source:Own Research.
TheemphasisofTOGAFisnotontaskssuchas n
DevelopinganITStrategybasedonaBusinessStrategy
n
Application Portfolio Management: Dealing with thousands of existingapplicationsandjudgingwhichhaveafuture,whichneed changeandwhichneedtobereplaced ArchitectureGovernance:Thisismentionedbutnottreatedasa mainitem
n
The ADM (Architecture Development Method) is still the kernel of TOGAFandisTOGAF’sbiggestasset.Youcanalsoseethisconcentrationon the ADMyourselfif you studytheevolution ofTOGAF from e.g.Version7(publishedinDec.2001)thruvariousversionsofTOGAF8(whichwasintroducedasthe“EnterpriseVersionofTOGAF7” andfirstfeaturedthe“EnterpriseContinuum”)toTOGAF9whichwas publishedinFebruary2009. © 2009-2012 Wolfgang W. Keller – all rights reserved
2 What is Enterprise IT Architecture?
11
Figure4 canbereadsothatPartII–theADM–hasbeenratherstable throughouttheevolutionshowninFigure4.Themajornewfeatures ofVersion9.xoverVersion8.xaretheArchitectureContentFramework and the material added in Part III: The ADM Guidelines and Techniques.Version9.1asamaintenancereleasehasachapterstructureidenticaltoTOGAF9. Soitcanclearlybeseenfromthis,thatTOGAFworkeditswayup from a framework for project architecture and major development projectstotheenterpriselevel.TOGAFwillcontinuetogrowtowards theenterpriselevelbutithasnotbeendesignedfromthebeginning withtheEnterpriseLeveloraPragmaticBusinessOrientedApproach inmind.ButletTOGAF(again8.1.)speakforitselfagain: A number of Enterprise Architecture frameworks already exist and are widely recognized, each of which has its particular advantages and disadvantages and relevance - for Enterprise Architecture. They are discussed in Part IV (of TOGAF 8): Resource Base, Other Architectures and Framewor ks. Although a number of enterprise frameworks exist, there is no accepted industry standard method for developing Enterprise Architecture. The goal of The Open Group with TOGAF is to work towards making the TOGAF ADM just such an industry standard method, which is neutral towards tools and technologies, and can be used for developing the products associated with any recognized enterprise framework - such as the Zachman Framework, Federal Enterprise IT Architecture Framework (FEAF), Treasury Enterprise Architecture Framework (TEAF), and C4ISR/DoD Framework - that the architect feels is appropriate for a particular architecture. …. With the migration of TOGAF to an Enterprise Architecture framework, this flexibility becomes even more important. TOGAF is not intended to compete with these other frameworks; rather, it is intended to perform a unique role, in distilling what these other frameworks have to offer, and providing a generic ADM that can be adapted for use with any of these other frameworks. The Open Group's vision for TOGAF is as a vehicle and repository for pract ical, experience-based information on how to go about the process of Enterprise Architecture, providing a generic method with which specific sets of deliverables, specific reference models, and other relevant architectural assets, can be integrated. Source TOGAF 8.1. [TOGAF8.1.1]
© 2009-2012 Wolfgang W. Keller – all rights reserved
3 TOGAF and IT Strategy
3
12
TOGAF and IT Strategy
IntheearlyreactionstoTOGAF9.0bloggerscommentingonthenew releasehavecriticizedTOGAFforfallingshortofprovidinghelpfor thestrategicplanningtasksinITmanagement.Thethreemainstrategictaskshavealreadybeenoutlinedinsection2.1andITstrategyis thefirstoneofthem. A first check is quite simple: Just take the TOGAF 9.1 pdf file, whichisavailableatamodestchargefromtheOpenGroupandhave theoccurrencesoftheterm“ITstrategy”countedinit.Youwillfind the termthree timesin the textandthismakes itclearthatTOGAF doesnotprovideyouwithamethod,todevelopone. Ifyoujustwantedtoknow,whetherTOGAFprovidesyouwitha closedsetoftoolsandmethodstodevelopanITstrategy,you’redone forthemoment.SkipthischapterandGOTOchapter4onpage20in ordertoseewhatTOGAFhastoofferyouforportfoliomanagement. IfyouwanttoknowwheretofindmaterialonhowtowriteanIT strategy and what TOGAF still has to offer besides obvious spots markedwithITstrategy,hangon.
3.1
What is an IT Strategy?
In order totalk aboutIT strategy itis first necessary totalk about strategy in general. In order toavoidcopyright problems weuse a Wikipediadefinition A strategy is a plan of action designed to achieve a particular goal.
You could also use the more militaristic version by Clausewitz [Clausewitz98]butthere’snorealdifference. Firstofallyouneedagoal.Thenyouneedmorethanonepossible waytogetthereandformulatingyourstrategyisaboutchoosingone ofthepossiblewaystogoandturningitintoaplan. Youmightask,whetheroneway(oroptionforattainingtheobjective) isn’tenough? Manystrategiesdo not pass thetrivialitytest where you ask whether the opposite of the way you chooseis still © 2009-2012 Wolfgang W. Keller – all rights reserved
3 TOGAF and IT Strategy
13
somethingthatmakessense.E.g.ifyoudonotholdamonopoly(you areinacompetitivemarket)andyoustate“CustomerOrientation”as your strategy, then the contrary “being non-customer oriented” would lead straight into bankruptcy. Hence for this example enterprise“CustomerOrientation”asastrategywouldnotpassthetrivialitytestbecausethere’snoalternativetoit. Youshouldfindsomeindicationsofthestrategyofyourenterprisein its business strategy. We will also deal with the case where your enterprise doesn’t have one. But let’s postpone that one for a moment.Thatcasewillbecoveredinsection3.3.Youalsoneedtoknow somethingaboutthematurityofyourITorganization.IfITistreated asapurenon-strategiccost-centerinyourorganization(remember Figure 1 forthe different steps of IT/ Business alignmentof anIT organization) then you will have a tougher time influencing your enterprise’sstrategy.WhenITisseenasanenablerincompetition, youshouldhavelesstroubleenteringintoatruestrategicdialog.
3.2
What needs to be described
NomatteratwhatlevelyourITorganizationfindsitself–thebasics thatneedtobedescribed(strategyelements)arealwaysthesame.
Figure5:MainPillarsofanITStrategy Theabovefigurecanuseabitofexplanation.Itisalsoreflectedinthe strategy matrix (see Figure 6) to follow. No matter what else you haveinanITstrategy.Youwillalwaysneedtomakedecisionsabout thefollowing:
© 2009-2012 Wolfgang W. Keller – all rights reserved
3 TOGAF and IT Strategy
n
n
n
n
n
14
Application Strategy:NomatterwhatelseyouplaninyourIT strategy,youneedanapplicationstrategy–astrategythatcontainsguidelinesonhowyouwanttodealwiththeITapplications in your company and how you want to support your business strategiesusingITapplications. IntegrationStrategy:Inmostcasesyoudon’thaveoneperfectly integrated applicationbut youhave a major set of applications thatneedtobeintegratedwitheachotherinordertobeableto perform business processes. These apps also might need to be connectedtotheoutsideworld.SOAorEAIstrategiesareforms ofintegrationstrategies.Buttherearealsomoreprimitiveones. InfrastructureStrategy: Youalsocannotevadehavinganinfrastructure strategy. Even if you outsource your complete infrastructure,youstillhaveastrategyhowtodealwithit:inthiscase “Outsourcing”. Other factors that determine your infrastructure strategyisyourglobalscope,yourneedsforsecurityandspecial solutionsandmanyotherfactorsthatyouwouldcheckifyouuse amatrixliketheoneinFigure6. Service Strategy: If you want to beperceived asa provider of services, you will end up having a service strategy, that determineshowyourcustomerswillgetwhichservicesatwhichservicelevels. SourcingStrategy:EvenifyoushoulddecidethatyouwillproduceallyourITassetsverticallyintegratedstartingwithdevelopingyourownoperatingsystem:youstillhaveasourcingstrategy. Normallyyouwillmakedecisionshereonwhattooutsource,and whattoproduceyourself.Youwillalsodecidewhetheryouwant to work together with a single provider, multiple providers, whetheryouwanttosourceinanopportunisticfashionorrelying ona few strategicpartnersto name a few ofthe decisions that needtobemadehere.
Ifyoudefinewhatyouwanttodoandachieveinthose5fieldsandif youcanexplainwhythisenablesyourbusinesstopursueitsBusiness Strategy,youarewelloff.Inordertohelpyouthinkaboutyourdecisions systematically and even deeper than that, you can apply key questions to each pillar the likes of “how do I govern that specific area?”; “how do I finance it?”, and a few more. As an example see Figure 6 below. This will force you to reflect onwhat you will do aboutcertain general concerns, such asthe regional distribution of yourbusiness.
© 2009-2012 Wolfgang W. Keller – all rights reserved
3 TOGAF and IT Strategy
15
Figure6:SampleITStrategyMatrix Thismatrixislikeachecklist.Ifyouareabletoanswerthequestions inthematrixthenyoucanbesuretoacertaindegreethatyoudidnot missamajorissuethatyoushouldhavetakenintoconsideration. Youcanthenwritedownyourfivestrategyelements.Ifyou’regood atit,youshouldhaveashortdocumentofmaybelessthan20pages that informs your IT people about the strategic directions in each columnandfield.
3.3
How do you get there?
The next question is:Whatis the processin whichyou need toinvolveBusinessthatleadsyoutosuchastrategydocument?
3.3.1
StrategicDialog
ThebestwaywouldbeifyourCIOandafewkeyITpeoplemeetwith key Business people in order to discuss and decide on a Business StrategythatalsoincludestheITStrategy. This stateof affairs issomewhatrare.Analystsstate that about 90% of enterprises do not have a written business strategy. Often CxOsdo not spent the time for a proper strategic dialog orfind it annoyingtotalktoITunderlingsaboutbusinessstrategies.Insuch casesyouwillneedtofindotherwaystoextracttheinformationyou needinordertoformulateaproperITstrategy,whichwillleadyou totheMaximProcess. © 2009-2012 Wolfgang W. Keller – all rights reserved
3 TOGAF and IT Strategy
3.3.2
16
ITMaximsfromBusinessMaxims
The Maxim Process is described by Broadbent and Kitzis in [Broadbent+05] as a pragmatic way to extract enough information foragoodenoughITstrategywhilenotinvestingmorethanaday’s workshopwithsenior management. The CIO willorganize aworkshopwithCxOs,whichwillleadtodocumenting2kindsofso-called Maxims: n n
BusinessMaxims, AndasaresultITMaxims
Maximsarea few conciseprinciplesthatareusedto document the strategic direction of an enterprise.A Maxim workshop willusually notproducemorethanaround5businessmaxims.Foreachofthose, managementwillderive4-5maximsfortheITfunctionthatwillhelp tosupportthem.
Figure7:MaximProcessbyBroadbent[ Broadbent+05 ]
AtypicalMaximWorkshopwillbesplitupintotwoparts: n n
Part1:FindingtheBusinessMaxims, Part2:DerivingtheITMaxims
An external facilitatorshould moderate theworkshop day and process. Togiveexamplesimagineanoldeconomyfinancialserviceprovider likeabiginsurancecompanythatrunsmorethanonebrandnameon themarket.Forsuchanenterpriseyoucouldfindthefollowingbusinessmaxim: Create synergies in back office and service functions wherever brand identity is not compromised
IT maxims that could be deducted from such a business strategy couldbe: (1) Define standard architectures and platforms used by all of the group’s companies in order to leverage synergies and to reduce IT cost (2) Harmonize the IT application systems for the group’s companies wherever there is a business case for this. © 2009-2012 Wolfgang W. Keller – all rights reserved
3 TOGAF and IT Strategy
17
(3) Support the business by providing harmonized business processes for all brands of the group.
Suchasynergisticstrategy(oranyotherstrategy)willhaveimplicationsonone’sITgovernanceprinciples.YoursetofITmaximsdefines the ITobjectives and the chosenways for reaching them. (See also Figure 7 ) You will need to install a system of IT governance that matchesyourITmaxims. Youmightsay:Easyandstraightforwardprocess.Thereshouldbeno problem tohold a meeting, define a few IT maximsand off you go withausableITstrategy.Lifeisnotalwaysthateasy.Therearemore thanafewthingsthatcangowronghere: n
n
Onewementionedalreadyabove:IftheCxOsseeITasabunchof underlingsandnotasanimportantproviderofbusinessopportunities,theywillnoteveninvestthetimeinsuchaworkshop. Anotherpotentialthreatislessevident.IftheboardofCxOshasa cultureofhidingconflictsandiftheydonotagreeonacommon strategytheywillnotbetoointerestedthattheirinternalbrawl becomes known throughout the enterprise. In such a case you willnevergetthemaximworkshopforwhateverreasons.
Thiswillleadyoutothenextlevel.YouwillneedtoreengineeranIT strategyfromthebehaviorsyouobserveindailybusiness.Whichwill bringustothenextsection.
3.3.3
ReengineeringtheBusinessStrategy
IfyourmanagementdoesnotwanttospendthetimetodiscussBusinessStrategyandITstrategywithyou,itstimeforyoutoreengineer thestrategyfromwhatyouexperience.Thereareenterprisesaround whoareverysuccessfulandhaveastrategyorcallitaverysuccessful way ofoperating: But it’s neither written down norcould anybody explainitexplicitly. Insuchacaseyouneedtoreengineerorfindthebusinessmaxims by applying analogies withknown strategy patterns. Literature willprovideyouwithanamplebodyofknowledgeonBusinessStrategy and will enable you to identify the patterns comprising your enterprise’sstrategy. HereagainamatrixliketheonepresentedinFigure6isuseful. Youcanaskquestionslike“whatisthegeographicdistributionofmy enterprise”and“whatarebestpracticepatternstodealwithjustthat kind of geographic distributionwhen it comes to services, applications,infrastructuresorsourcing.Thatwayyoucanagaingothrough thematrix(Figure6). © 2009-2012 Wolfgang W. Keller – all rights reserved
3 TOGAF and IT Strategy
3.4
18
What support will you find in TOGAF?
As you can see from the TOGAF summary picture 1, TOGAF treats BusinessStrategyandalsoITStrategyasanitemoutsideofthescope ofTOGAF. PhaseA(ArchitectureVision)oftheADM[TOGAF9.1,Chapter7]tells youthatyoushouldgetholdofthebusinessdriversbeforeyoustart anarchitectureprojectofsomekind.TOGAFalsoproposesacapabilityanalysis.StillthecombinationofBusinessStrategyandITStrategy seemstobeconsideredassomethingoutsidethescopeofatleastthe TOGAFADM.
3.5
Further Reading
GartnerMaterialonITStrategies Gartner usually has some interesting material on IT strategies. We cannotcite the stuff here because theirIntellectual Property policy prohibitscitationsofmaterialolderthanoneyear.Havealookatthe Gartner Research databases if you happen to have a relation with them. MarianneBroadbentused tobe a Senior Vice Presidentat Gartner, andalsoservedasaprofessoratMelbourneBusinessSchool.Shehas consulted and interviewed a four-digit number of CIOs for various panels by Gartner. Her book “New CIO Leader: Setting the Agenda andDeliveringResults”[Broadbent+05]isstillaclassiconITstrategy; MITSloanSchoolMaterialonITStrategies GartnerisalsoconnectedtotheMIT’sCenterforInformationSystems Research(CISR)headedbyPeterWeill.Averyinterestingbookis “EnterpriseITArchitectureasStrategy:CreatingaFoundationfor BusinessExecution”[ Ross+06]byJeanneRossandPeterWeill.The bookwillalsopointyoutofurtherMITresourcesorchecktheMIT websiteathttp://mitsloan.mit.edu/cisr/.
FortherespectiveTOGAFpicturesee http://www.opengroup.org/architecture/togaf9-doc/arch/Figures/01_structure.png Theauthorhastoaskforpermissionbeforereprintingthematerial. 1
© 2009-2012 Wolfgang W. Keller – all rights reserved
3 TOGAF and IT Strategy
19
ConsultingTools Ifyoudevelopstrategiesitveryhelpfultohaveaworkingknowledge ofmethodsandtoolsthatweredevelopedbythelikesofBCG,McKinseyandotherwellrenownedconsultingfirms.Aconvenientwayto getsuchinformationistogetyourselfbooksonconsultingtoolkits, strategyconsultingorjustacompactMBAbookforstarters.There’s toomuchsuchliteraturearoundtobecounted.
© 2009-2012 Wolfgang W. Keller – all rights reserved
4 TOGAF and IT Portfolio Management
20
4 TOGAF and IT Portfolio Manag ement
TOGAF has almost nothing to offer for IT portfolio management. HencewewillgiveashortsummaryofApplicationandInfrastructure Portfolio Management andwill set pointers tothefew spots inTOGAF,whichareofsomehelpforthesetasks.
4.1
What is IT Portfolio Management
ITPortfolioManagementcomesinatleastthreeflavors.Twoofthem are relevant for Enterprise Architects. And the third flavor is also present ina CIOoffice and henceEnterprise Architects willat least haveaninterfacetoit.Theflavorsare: n
n
n
Project Portfolio Management: Of all the flavors of portfolio management,thisisthemostwidespreadone.Evenifcompanies don’tcareaboutarchitecturetheyusuallycareabout,howtheir moneyisspent.Itisquiteacommonsituationthatacompanyhas twoorthreetimesmorebudgetproposalsforprojectsthanithas moneytospendonprojects.Thisexplainswhyamechanismfor project prioritization is installed in almost any enterprise. As stated above, Project Portfolio Management has an interfaceto EnterpriseITArchitecturebutisusuallynotseenapartofit.This iswhythissubjectisnottreatedanydeeperinthisbook. Application Portfolio Management: Most Enterprises have a considerablenumberofapplicationsthatsupporttheirbusiness processes.Belowyouwilllearnwhyitisimportanttohaveaninventoryofapplicationsandwhatgoals“managing”thempursue. Application Portfolio Management is usually seen as a part of strategic Enterprise IT Architecture Management. Therefore it willbetreatedbelowinsomemoredetail. InfrastructurePortfolioManagement: OftenEnterprisesdonot haveaproperITinventory.Neverthelesssomeofthosewhodo not have a 99% accurate IT inventory still manage their Infra© 2009-2012 Wolfgang W. Keller – all rights reserved
4 TOGAF and IT Portfolio Management
21
structurePortfolio.Thereasonbehindthisisinmostcasescost savingsbystandardization.Whichcanbetranslatedto:Theless technologiesyou own, the lower your maintenance andadministrationcosts.FormostcompaniesITinfrastructureisnotamatterofcompetitiveadvantage.Thereforetheycanaffordtomanageitasacommoditywherethecheapersolutions(fewertechnologies,fewerlocations)areoftenthebettersolutions. TherestofthischapterwillexplainApplicationPortfolioandInfrastructurePortfolioManagement.WewillstartwithApplicationPortfolios,justbecausethisishandiertoexplain.InfrastructurePortfolio canoftenbeevenmorerewardingasEnterprisesusuallyspendmuch moremoneyonITinfrastructuresthantheyspendonapplications.
4.2
What is Application Portfolio Management?
In order to understand why you would like to deal with portfolio management,itissomewhathelpfultoexplaintheterms Let’sstartwiththetermportfolio.Aportfolioisacollectionofinvestmentsheldbyaninstitutionoraprivateindividual. This means,in a “normal”enterprise you have anIT infrastructureportfolioandalsoanITapplicationportfolio,becauseyousimply possessasetofinfrastructurecomponentsandalsoasetofITapplications.Andusuallyyouhaveheavilyinvestedinthem. Nextlet’shavealookatportfoliomanagementinfinance.Aportfoliomanagerwill(intheory)optimizehisportfoliosothatityieldsa maximumreturnatagivenlevelofrisk.Usually:Thehighertherisk thehigherthepotentialgain.Andthisisabouttheendoftheanalogy forseveralreasons: n
MeasuringReturns: Forfinancialassetsitiscomparativelyeasy tomeasureamonetaryreturn.Yougetdividends,interestorother forms of payments and also the value of your asset may change.ForanITapplicationitistoughtomeasurethereturn, because itis tough todetermine which part of your company’s successcanbeattributedtotheITapplicationandwhichtoother factors.
n
NoExchange:UsuallythereisnostockexchangeforITapplications.Investmentsin a financialportfolio canusuallybe traded onastockexchangeorsomeotherexchange.Therearebrokers whodealinusedITinfrastructure.Butforindividualusedapplicationsthereisnothingsimilartoastockexchangeorothermarkets.CustommadeITapplications,whichoftenmakeupthelion’s © 2009-2012 Wolfgang W. Keller – all rights reserved
4 TOGAF and IT Portfolio Management
n
22
shareofyourITinvestmentinapplicationsystems,tendtohavea low(ifnotzero)fungibility. Covariance:HaveyouevertriedtoselltheAustrianITapplication forthecadastral land register tolet’s saytheChinese government? You will experience problems that stem from use of otherapplicationsthatyourcadastrallandregisterapplicationis interfacedwithorisbasedon.Forexample,maybe,thelocalauthority’s register of residents. Often an enterprise application needsawholeecosystemofotherapplicationsitworkswith.In aninvestmentportfolioyoucansellXYstockandreplacebyYZ stock.Inanapplicationportfoliosuchaswitchusuallyresultsin expensiveandlong-termprojects.
Thenwhywouldpeoplestillcallmanagingtheirapplications“Application Portfolio Management” if the analogies are limited? The answer is becausea lot of the techniques used toanalyze application portfolios use 4-quadrant matrices in the style of the famous BCG matrix.
Figure 8: BCG-style Matrix used to analyze Application Portfolios – SimilarmatricescanbefoundinWard/Peppard[ Ward+02 ] © 2009-2012 Wolfgang W. Keller – all rights reserved
4 TOGAF and IT Portfolio Management
23
Thecategoriesgivenby Figure8 arejustoneofmanymanywaysto look at your collection of applications –though it is a particularly commonandpopularone.Theapplicationsyoufindineachquadrant requireadistincttreatmentthatiscommonforalltheapplicationsin aquadrant. Dogs (a.k.a. Support Applications): These are those applications thathaveacomparablylowcontributiontotoday’sbusinessresults andalsoalowcontributiontofuturebusinessresults.E.g.ageneral ledgersystemisnotacriticalsuccessfactorformostcompaniesand itwillneverbeone.Henceitisacommonstrategytoidentifysuch systems and make an analysis whether the company gets a better dealifyououtsourcesuchsystemscompletely.Notonlydevelopment butalsooperations. Cows(a.k.a.KeyOperationalApplications): Thesearetheprocesses your current bottom line relies upon. In many companies these wouldbe largeindividualsoftwaresystemswithaheavyinvestment bound in them and very conservative procedures to change them. Downtimeinsuchsystemsusuallyhasadirecteffectonthebottom line. The company usually could not afford that and hence has to concentratealotofattentiononkeepingthesesystemsupandrunning.Outsourcingthewholesystemisseldomanoption. QuestionMarks(a.k.a.HighPotentialApplications): Typicallyyou have a research department (or a similar organization) that takes careofyouproductinnovations.Ifyouinventnewproducts,thesystems that come along with them need not be extra stable but only needtobedemonstratorsthatallowyourmanagementorcustomers toassessthepossibilitiesinaproductorsystem.Usuallyyouwould havemanysuchtestsystems,asmaybe1outof10innovationreally makesittothemarket. Stars(a.k.a.StrategicApplication): Thesearetheapplicationsthat belong to products that have been selected to be the future cash cows.Suchproductsshould bein a heavygrowth phasewithsmall absolutenumberssoldbuthighgrowthrates,ofteninverycompetitive and also growing markets. The emphasis here is typically on speed and features and less on an absolutely minimal number of production problems. In many cases you would want to keep the systemsthatsupportsuchproductsapartfromthesystemsthatsupportthecashcows.ButtherearealsoindustrieslikeTelecomswhere youhavetotest-driveyourinnovationswiththebigironsystems,as thereisonlyonesystemthatallowsyoutodobilling–forallkindsof products. Usingsuchanalysesleadstosomeinterestingotherviewsonaportfolioe.g.whichquadrantsdoesyourprojectmoneygoto?Theanti© 2009-2012 Wolfgang W. Keller – all rights reserved
4 TOGAF and IT Portfolio Management
24
patternsaresoinstructivethatmostanalysishereisstraightforward. E.g.ifyouspend60%ofyourwholeprojectbudgetinthe“question marks”quadranton three hugeprojects, experienceshould tellyou thatsomethingiswrong,asspendingintheQuestionMarkquadrant shouldberelativelymoderate.Orifyouhaveamajornumberofprojectsin the Dogs quadrantthenyoushould ask yourself,whetherit makessensetonurturethe“poordogs”byadditionalprojectsinstead ofoutsourcingthem.
4.3
Putting it together: From Chaos to a Master Plan
Ifyougetassignedtothenewjobof“ChiefEnterpriseArchitect”,you willoften find noinventoryandno analysis.Thequestioninsucha situationis:HowdoIconstructaproperTo-Bestateofmyapplication landscapeand how doI produce the masterplanthatgets me from my As-Is state toa properTo-Bestate. Figure 9 gives you an overviewoftheanalysiselementsthatareoftenapplied.
Figure9:ElementsofanApplicationPortfolioAnalysis n
n
Application Handbook:Inmostcasesyoustartbycreatingan inventoryofallyourapplications.Oftenyouwillalsodraw processsupportmapsthatshowyouhowyourbusinessprocesses aresupportedbyapplications.Thiswillgiveyouanoverviewof whatyouhave.Butitdoesnotyetreallyhelpyoutoassesswhat isgoodandwhatisbadwithrespecttoyourbusiness’goals. HeatMapping:Afurtherstepisoftenaso-calledHeatMapping. This is also availableas a serviceoffering called “Motion” from Microsoftforamajorityofindustries.Anexpertwillbringalistof potentialcapabilitiesforyourindustryand,togetherwithateam ofexperts,youmirrorpotentialcapabilitiesagainstyourbusiness strategiesandyouwillfindoutwhicharethecriticalcapabilities © 2009-2012 Wolfgang W. Keller – all rights reserved
4 TOGAF and IT Portfolio Management
n
n
25
thatyouneedtospeciallylookafterinordertoimplementyour strategy.Youcanthenassesstheactualqualityofthecapabilities asprovidedbyyourapplicationportfolioandwillgetapercapabilityheatmapthatissuitedtodemonstratetheareasforpotentialactionquiteintuitively. ReferenceModels:Oftenitisveryinstructivetomapyourapplicationlandscapeagainstdomainspecificreferencemodels.Often youwillfindabunchofareasforimprovement Portfolio Analysis: And you can also use PortfolioAnalysis to cluster yourapplications intoclasses thatusuallydeserve some kind of standard treatment like “outsource”, “stabilize”, “renovate”andothertreatments.
Ifyoucombinetheresultsfromthosefourstreamsofanalysisitisin mostcasesstraightforwardtocomeupwithideasforaction,like n
n
Youfindthatforacriticalcapabilityyouhave5differentsystems in9locationsthatsupportit.Insuchacaseyoumightwantto consolidatetheappsandreplacethemwiththeonethatbestor bettersupportsyourcriticalcapability. Youfindthatarelativelyhugesystemsupports8capabilities,3of themcriticaland5ofthemnon-criticalcommodities.Youmight wantto comeup withideasonhow toseparate the commodity part from the critical part and construct better-suited system supportatlowercosts.
Theadvicehereisrathergeneric.Thereasonforthisisthatyoucan describeagenericmethodlikeheatmappingoruseofprocesssupportmaps–butitisdifficulttoforeseetheoutcomeforeachpossible enterpriseanddescribeadeterministiccookbookthatshowshowto attackanyproblemtheworldofapplicationplanninghastooffer. Your“To-Be”architecturewillbeanarrayoftransformationsapplied toyour“As-Is”architecture.Thechoiceandquantityisdeterminedby your total budget and also priorities. The selection process can be copiedfromordinaryprojectportfoliomanagement. Figure10showsrepresentativesforthetwoadditionalartifactsthat yourmasterplanwillcontain: n
n
You willhave“To-Be” application maps (e.g.againprocesssupportmaps)ofyourtargetapplicationlandscape Andyouwillhaveamasterplanshowingthe“operations”ofthe applicationlandscapee.g.asprojectplansorintervalmapsthat showwhichsystemistobereplacedbywhichothersystemand when. © 2009-2012 Wolfgang W. Keller – all rights reserved
4 TOGAF and IT Portfolio Management
26
Youcouldalsoaddtheplannedstateofyourheatmapsyourto-be stateortheplannedstateofyourportfolios.
Figure10:ElementsoftheMasterPlan
4.4
What do you find about Application Portfolio Management in TOGAF?
TheansweristhatApplicationPortfolioManagement,asatermdoes notappearatallinTOGAF.Asmentionedabove,TOGAFisnotreally intended to help you with strategic IT management and therefore TOGAFisnottheprimesourcetouseifyouneedtolearnsomething aboutstrategicITmanagement.
4.5
Infrastructure Portfolio Management
Justasyoucanmanageapplicationsyoucanalsomanageyourinfrastructurecomponents,mostlikelyconsistingof: YournetworkinfrastructureconsistingofWANs,LANsandother networkcomponents; Servers(fromPCserverclusterstomainframecomputers); n And all kinds of infrastructure services, like operating system n services (bethey virtual orreal) and many otherbasicservices likearchiving,orprinting Thereareatleasttwodifferencesheretoapplicationportfoliomanagement: n
n
You will most likely manage classes of devices and services insteadofsingleinstances(applications).ItisnotthetargetofinfrastructureportfoliomanagementtoreplaceaCMDB(configura© 2009-2012 Wolfgang W. Keller – all rights reserved
4 TOGAF and IT Portfolio Management
n
27
tionmanagementdatabase).YoumaythereforeworkonaclusteredextractofaCMDBandyourportfoliowillmostlikelyconsistofanumberofservicesandheterogeneousimplementations thereof.Inshort,youwillfindtoomanyimplementationsforthe sameservice,toomanyoperatingsystemsandvariants,toomany softwareproductsforthesametaskandyourjobwillmostlikely betosavemoneybyreducingheterogeneity. As most infrastructure components in most enterprises are commodities your main interest in them will be cost reduction while guaranteeing a given level of service. Hence you will in mostcasesskipalotofthedimensionsthatyouwoulddealwith inApplicationPortfolioManagementandgoprimarilyfordimensionssuchascost,homogeneityandsimplicityofaportfolio.
So the most likely form of report or architectural artifact in Infrastructure Portfolio Management is a simplelist, which lets you see how many implementationsof service X youprovideand whichallowsyoutoworkouthowtoreducethecomplexityofyourportfolio.
4.6
What do you find about Infrastructure Portfolio Management in TOGAF?
Thestraightansweris:Ifitcomestothemanagementaspectyouwill findalmostnothing.WhatyoucanuseisTOGAFterminologyoninfrastructure,as described in the Technical Reference Model. This willgiveyoutermsandtaxonomyofclassesofinfrastructureandalso infrastructureservices.Forthetoplevelofthisseee.g. Figure11 .If you say“trivial” then pleasedo not forget the last time consuming discussionsyouhadwhentryingtoagreeonsuchapictureandthe termsbehindit.So the valueofsucha de-factonormshouldnotbe underestimated.
© 2009-2012 Wolfgang W. Keller – all rights reserved
4 TOGAF and IT Portfolio Management
28
Figure11:TopLevelViewoftheTOGAFTechnicalReferenceModel. Therearedeeperlevelstothisandalsotaxonomies.RelevantLayersfor InfrastructurePortfolioManagementareApplicationsPlatformsand alsoCommunicationsInfrastructure.ForthesimilarfigureinTOGAF 9.1seefigure43-1. http://www.opengroup.org/architecture/togaf9-doc/arch/Figures/43_trm.png(Link checked2012-04-24)
YoucanalsousetheTOGAFContentMetamodel 2inordertomodel yourinfrastructure.Youwillfindmetamodelsnippetsfor n n n
PlatformServices, LogicalTechnologyComponents,andalso PhysicalTechnologyComponents,
Whichwillhelpyouwithafirstcutofasetofentitiesandattributes youcanuseforyourowninfrastructureportfoliomanagement.
4.7
Further Reading
Itissomehowtoughtofindahands-onguidetoApplicationandInfrastructure Portfolio Management. What you will get is fragments butyouwillhavetointegratethemyourselfatthemoment,starting fromthequestionsyouandyourmanagementwantanswersforand thendesigningtheanalysisinstrumentstoanswerthem. TheclassicforApplicationPortfolioManagementisthebookbyWard and Peppard “Strategic Planning for Information Systems” [Ward+02] which has appeared in different editions even with changes inthe author’s team overtheyears.The book isnot easy reading but a classic and worth owningif you have concrete tasks aroundApplicationPortfolioManagement.
2
See e.g. TOGAF 9; Figure 33-3 © 2009-2012 Wolfgang W. Keller – all rights reserved
4 TOGAF and IT Portfolio Management
29
Kaplan’s book on Strategic IT Portfolio Management [Kaplan05] hassomekindoffocusonProjectPortfolioManagement,butisoneof thefewbooksonthemarkettodaythatdealswithITPortfolioManagementatthetitlelevel. TUMEAM Pattern Catalog: A group atthe Technical University of Munich (Germany) collects so-called EAM patterns. Here you find management procedures, viewpoints used for them and also metamodel snippets that support them. You could also start from the questions, look forrightpatterns and then integrate your personal version of a portfolio management from them. Just have a look at http://wwwmatthes.in.tum.de/wikis/sebis/eampc. Looking at the site yourselfis much faster than reading a thirdparty text like this one. GermanBooks:If youreadGermanyouwillan arrayofbooksthat emphasize the management aspect of Enterprise IT Architecture Managementlike[Dern09,Keller12].Ifyouareespeciallyinterested inapplicationportfoliomanagement,itisworthhavingalookatthe MS thesis work by Riege [Riege05]. A relatively new book by Inge HanschkeisespeciallyfocusedonapplyingZoningMapstostrategic planningofapplicationlandscapes[Hanschke10].
© 2009-2012 Wolfgang W. Keller – all rights reserved
5 TOGAF and Developing Architectures
30
5 TOGAF and Developing Architectures
FromtimetotimeevenEnterpriseArchitectsneedtodeveloparchitectures.Thosecanhavesuchdifferentscopesas n
n
n
n
An architecture for a single system that consumes an effort of maybeonlyafewpersonyears Clustersofsystemsthatsupportasinglebusinessprocess,spanningmaybe5–7ITsystems.Suchprojectsmayconsume10to50 personyears. Architecture for the applicationlandscape of a whole company. Thiswillneverbeimplementedinasingleprojectamaytakealmostadecadetocomplete. TemplateArchitecturesandarchitecturesforapplicationframeworksthatserveasthetemplateforafamilyofapplications,like e.g. all customer facingweb applications of an enterprise. Such BluePrintsaretypicallyreused5–10times.
SuchtasksarethecorecompetenceofTOGAF–andthisisalsowhy this chapter will beshort –because wewillforwardyou toTOGAF afterashortlookatwhatTOGAFoffersyou.TheTOGAFADM(ArchitectureDevelopmentMethod). IfyouknowaTOGAFversionthelikesof7.0or8.xyou’redonehere withthischapter.HavealookathowTOGAFhasimprovedtheADM byfactoringoutafewthingsandsplittingitintotwoparts:PartIIand PartIII. IfyouhappentobeaTOGAFnewbiehangonfor2pages.
© 2009-2012 Wolfgang W. Keller – all rights reserved
5 TOGAF and Developing Architectures
5.1
31
Part II: TOGAF ADM
TOGAFproposes a cyclicprocess for architecture development(see Figure12).Whatyouhavetodohereisquitestraightforwardforany softwarearchitectureprofessional.
Figure12:CyclicADMProcess.ForthesimilarfigureinTOGAF9.1see figure5-1. http://www.opengroup.org/architecture/togaf9-doc/arch/Figures/adm.png(Link checked2012-04-24)
Youcanseethestepsasofferingsorasachecklist.Ifyouwoulde.g. makea minoradjustmentto afewsystems within agivenBusiness ArchitectureyouwhathavealookatthechecklistforPhaseBinthe cycleandwouldskipit,ifyoucometotheconclusionthatwhatyou would have to do here isalready clear orhas beendone byother colleagues.EachofthePhasesatthetoplevelisdepictedin Figure12 Eachphaseissplitupinvariousstepsthatmakeaveritablechecklist forthephase.TOGAFprovidesinformationondocumentsthatshould gointoastepandshouldbeproducedineachstep.
© 2009-2012 Wolfgang W. Keller – all rights reserved
5 TOGAF and Developing Architectures
5.2
32
Part III: ADM Guidelines and Techniques
With TOGAF Version 9 a lot of complementing material has been factoredoutofthecoreADMcycle.ThereforePartIIIcontainsallthe additionalmaterialthat isthere tohelpyouusing the ADM suchas informationon: n n
n
HowtousetheADMasacyclicprocess(chapter19) Applying the ADM at different levels of granularity (smaller or largerprojects)(chapter20) Andsuchaspectsasdoingsecurityengineering,usingTOGAFfor aSOA(chapter22),stakeholdermanagement(chapter24),architecture patterns(chapter25), and a few more usefulthings for architectstoknow.
PartIIIisthereforemorelikeacollectionofusefulstuffthanachecklistoraprocesslikePartII–thecoreADM
5.3
Further Reading
EventhoughTOGAFisaveryextensiveandusefulchecklistforsoftware architectsit is more ofa checklist than training material. For example,ifyouwanttoapplyrequirementsmanagement(thecentral iteminthemiddleofthecycle)youneedtohaveknowledgeofrequirementsmanagementanditshouldbemoreknowledgethancan befoundinTOGAF–asthemoreextensivebooksonRequirements Managements have their own 500+ pages – compared to the 780 pagesTOGAFhasaltogether. Ortakechapter 25on architecturepatterns.You will get a few referencestothelikesoftheIBMeBusinessPatternsorotherpattern sourcesandwillgetanideaofwhatapatternisandwhatitisuseful for. But you cannotexpect a fullcatalog ofallpatternsan architect could–orshould-know. LuckilyTOGAFhassome3pagesofreferencesandlinkstoliterature,sothatitdoesnotmakesensetociteanotherpageofreferences foreachofthechapters5thru32.Stillafewarchitecturebooksare quitehelpfulasthereferencescontainmorepointerstootherstandardsandframeworksthantogoodintroductorytext. Whichcanbetranslatedas:TheADMisnotanintroductorytext to software architecture for beginners but TOGAF is a condensed checklistforarchitectureprofessionals .
© 2009-2012 Wolfgang W. Keller – all rights reserved
6 TOGAF and Architecture Governance
6
33
TOGAF and Architecture Governance
If you remember Figure 3: The Enterprise Architect’s Process Map thenyouwillrememberthatanEnterpriseITArchitectureGrouphas threebiggroupsoftasks: ThestrategicTaskshavebeendiscussedaboveinchapters3and 4. The architecture development tasks have been be discussed in chapter5.Whatremainsisthequestionofhowtoenforcethestrategiesandarchitecturesthatyouhavedeveloped.ThisiscalledArchitectureGovernance.Forthefurtherdiscussionwewilluseapartof Figure3
Figure13:ArchitectureGovernanceOverview
SoinordertoexercisepracticalArchitectureGovernanceyouneedto dothefollowing: n
Firstofallyouneedanactualoverviewoftheprojectportfolioof yourenterprise.Youarenotinterestedinthoseprojectsthatperformsimplemaintenancetasksorarethefifthimplementationof astandardblueprint.Youareinterestedinthoseprojectsthatdo thingsthatchangeyouroverallarchitectureandthathaveanimpactonyourfutureITlandscape.Soyourfirsttaskis,tofindexactlythoseinterestingprojects.
© 2009-2012 Wolfgang W. Keller – all rights reserved
6 TOGAF and Architecture Governance
n
n
34
Thenextimportantpointistogetanideaofwhethertheteam thatisassignedtotheprojectthatyoufoundinteresting,iscapableofperformingaproperjob.Ifyoufindthataninexperienced architectwasassignedtoverydifficultjob,theprojectwillneed farmoreattentionandinvestmentfromyourside,thanitwould haveneededifyourcounterpartwereahighlyprofessionaland well-educatedarchitect. Afterscreeningtheproject,andaftergettinganideaofwhatyou havetoexpectfromtheteam,youwouldagreeonanauditplan fortheproject.Dependingonthedegreeofdifficulty,youcanset upthefrequencyofmeetingsnecessarytogoverntheproject.In thosemeetingsyouwilldiscussprogresswiththeproject’sarchitectsandyouwillalsodiscussdeviationsfromthecompanyarchitecturepolicy.
Asyoumaysee,allthishasalottodowithcommunicationandthe abilitytojudgeyourcolleagues’capabilitiestocomeupwiththeright solutionsthefirsttime.
6.1
What do you find about it in TOGAF?
InTOGAFyouwillfindallthetechnicaldefinitionsforITgovernance and alsofor architecturegovernance. You willnot find the tips and tricksyouneedtodealwithyourcolleagues,thetechniquesforeffectivereviews,orwhatyouhavetodoincasesofdeviations. TOGAFhastwospotsthatdealwitharchitecturegovernance: n
First, there is a dedicated chapter, chapter 50, on architecture governance. This chapter contains mostlythe scope and definitions needed to perform architecture governance beyond what wasoutlinedabove. TOGAFalso seesenforcing compliance as a taskforarchitecturegovernanceactivities.
n
Second,phaseGoftheTOGAFADM(chapter15ofTOGAF)covers Implementation Governance. Here you find a more or less detailedrecipeonstepsneededtoperformanarchitectureaudit.
Soinadditiontoafewtricksonhowtohandlereviewsyoualsofind sufficientinformation.
© 2009-2012 Wolfgang W. Keller – all rights reserved
6 TOGAF and Architecture Governance
6.2
35
Further Reading
Besides the more formal advice on architecturegovernance, audits, andreviews,thereisalotofusefuladviceonhowtoimprovepracticalarchitectureworkinthepatterncommunity.Youcan,forexample, usetheso-calledwriters’workshopinordertoimprovealmostany kindofdocumentationonarchitecturework.Foraguideonhowto conduct the writer’s workshop consult work by Jim Coplien [Coplien96,Coplien97].
© 2009-2012 Wolfgang W. Keller – all rights reserved
7 TOGAF and Basic Tasks
7
36
TOGAF and Basic Tasks
TOGAF offers some help, if it comes to other architecture routine tasks.Asanarchitectyouwillsoonerorlaterwanttostoretheinformationyouacquiredinsomeformofautomaticdatabase,insteadof in a bunch ofExcelsheets andPowerPoint presentations. For this youmightneedeitherasoftwaretoolorameta-model.Inmostcases youwouldneedboth.Sections7.1and7.2willdealwithhowtodesignameta-modelforuseinEnterpriseITArchitectureandalsowhat youcanexpectfromTOGAFifitcomestoselectingtherighttoolsfor EnterpriseITArchitectureManagement. Apartfromthatwewillgiveyouaquickoverviewinsection7.3of whatyoucanexpectfromTOGAFifyouwanttosetupanEnterprise ITArchitecturefunction.
7.1
TOGAF and finding the right Meta-Model for your Needs
InEnterpriseITArchitectureManagementyousoonerorlatercome toa pointwhereyou want tohavea databaseof your ITPortfolio, yourITassetsandyourapplicationlandscape(tonameafewitems) inordertoperformmanagementonthesetsofrealworlditemsyou havemodeledinyourEnterpriseITArchitectureDatabase. Youcangetreadytousemeta-modelsinsizesbetween50metaentitiesuptofarmorethan500meta-entities.Itshouldbesomewhat straightforward to see that 50 is somewhat limited andmore than 500mightbeabittoocomplexifnotcoveredbyaverywellintegrateduserinterfaceofanEAMTool. Inmanycasesyouwillnottrytoanswerallpossiblequestionsin EAMatatime.Itismorelikelythatyoumanagementhasfocusedits interestsoncertainpointslikee.g.costmanagementforyourinfrastructure,justtonameanarbitraryexample. Startsmall:Insuchcasesitisimportanttostartwithasmallsolution that is driven by the question you have to answer without havingtodealwiththefullcomplexityofa500+itemmeta-model. © 2009-2012 Wolfgang W. Keller – all rights reserved
7 TOGAF and Basic Tasks
37
Youcanstillendupbig:TOGAFarchitecturecapabilityframework offers you a meta-model, which is split or modularized into small areas of interest. If you are interested in a certain area, you needtoreadtherespectivesectionsandcandrawfromthelistsof predefinedTOGAFmeta-objects.Thetop-levelpictureoftheTOGAF ArchitectureContentFrameworkgivesyouanoverviewoftheareas forwhichyoucanexpectsupport.
Figure14:TopLeveloftheTOGAFContentMetamodel.FormoredetailsseeTOGAF9,figure33-3. http://www.opengroup.org/architecture/togaf9-doc/arch/Figures/34_contentfwk5.png (Linkchecked2012-04-24)
Thisisaboutwherewewillendwiththisbookandthistopic.Itisnot our aim toduplicateTOGAF textsinotherwords.Herewecanonly recommendreferringtoTOGAFchapters33thru37inordertogetan ideawhattheArchitectureContentFrameworkcanofferyouin case youneedaMetamodelasabasistostartstoringinformationabout yourarchitecture.
7.2
TOGAF and finding Tool Support
Mostorganizationssoonerorlaterarriveatapointwheretheywant toputallrelevantinformationfromtheirEnterpriseITArchitecture effortsintosomeformofrepositoryandwheretheywanttoeditthe viewpoints of their architectures in a single architecture tool. Let’s havealookwhatTOGAFhastoofferyou,ifyouwanttoselectatool. Therearetwochapters,whicharefocusedontherepositoryandtool matter:
© 2009-2012 Wolfgang W. Keller – all rights reserved
7 TOGAF and Basic Tasks
n
n
38
Chapter 41 (Architecture Repository): Here you get 7 pages (pages 559 thru 565) of information of what TOGAF thinks shouldbeinanArchitectureRepository.Therearereferencesto theTOGAFADM(ArchitectureDevelopmentMethod)which–as wehave already demonstrated– doesnot really coverstrategic ITplanning.Asaconsequence,therecommendedcontentlisted in TOGAF Chapter 41 also does not cover much of strategic IT planning. Chapter42(ToolsforArchitectureDevelopment): givesyoua 4-pagelistofevaluationcriteriaforarchitecturetools.Ifyouhave everdonea similar toolevaluation you know thatcriteriacatalogsfortoolevaluationsarewaylongerinmostpracticalcases. Andagain–thelistdoesnotcoverstrategicITplanning.
Therefore,ifyouplantoacquireanEnterpriseITArchitecturemanagementtoolhavealookattheevaluationdonebyTechnicalUniversity of Munich in 2008 (you find pointer to the material at http://wwwmatthes.in.tum.de/wikis/sebis/eamts2008). The study has a broader approach from the functional side. It also contains aspectsofstrategicITplanning.Andthelistofcriteriausedisbyfar moreextensivethantheoneprovidedbyTOGAFchapter42.
7.3
TOGAF and Immersion Paths for Enterprise IT Architectures
AnotherthingonewouldliketofindinanArchitectureFrameworkis helpwithsettingupanEnterpriseITArchitectureManagementOperation(orcallittheEAMdepartment,orprocessesifyouwanttobe moremodern). TOGAF offers you a so-called “Architecture Capability Framework”.ThisFrameworklistsasetofinstancesyouneedforasuccessfulEAMoperation.Andagain:StrategicITplanningisnotinthecenterofit–soyouwillnotreadanythingaboutITStrategyorITportfoliomanagement– butyouwillgetadviceonhowto use theTOGAF ADMtodevelope.g.thesystemssupportforthearchitecturepractice. Whatyouwillfindisadviceon: n
Establishing an Architecture Capability (Chapter 46): This tellsyou how toapply the ADM toan Information Systems and TechnologyArchitecture–nottheoneforyourcompanybutfor thearchitecturepractice.Itismoreorlessalistofactionitems.If you look atthisfrom a management perspectivethentoolsupport comes very late in establishing a successful architecture © 2009-2012 Wolfgang W. Keller – all rights reserved
7 TOGAF and Basic Tasks
n
n
n
n
n
n
39
practice.HencetheorderofthingsinTOGAFchapters45thru52 isdebatable. Architecture Board (Chapter 47):DescribeswhatanArchitectureBoarddoesandhowtosetitup(4pagesallinall). ArchitectureCompliance(Chapter48):Containsachecklistfor architecturereviews–howtoplanthemandwhattocheck. ArchitectureContracts(Chapter 49):Givesafewhintsonhow tomakeagreementsonarchitecturebetweentheenterprisethat sourcessomepieceofsoftwareandthecontractors. Architecture Governance (Chapter 50):Giveshintsonhowto enforce theenacted architecture guidelines.Has beendiscussed inmoreextentaboveinChapter6ofthisbook. ArchitectureMaturityModels(Chapter51): Appliestheideaof CMMI and other Capability Maturity Models to TOGAF. Rather briefandalreadyreferringtofutureeditions. ArchitectureSkillsFramework (Chapter52):Definesasetof rolesandskillsneededintheopinionofthecreatorsofTOGAFto fillouttheroles.
BrowsingthroughthismaterialyoumightconcludethatTOGAFhasa somewhat technology- and model-centric view ofEnterprise IT Architecture.Thechaptersstartwithestablishingtherighttoolsupport fortheEnterpriseITArchitecturePractice;yougetsomeinformation onGovernanceandArchitectureGovernanceBodies–butyoudonot getabusinessdrivenimmersionpaththatpushesyoutowardsmaximizingbusinessbenefitfromdayzero.
© 2009-2012 Wolfgang W. Keller – all rights reserved
8 What else will you find in TOGAF?
8
40
What else will you find in TOGAF?
ThischapterwillexplainthepartsofTOGAFthathavenotyetbeen mentioned.Youwillbegivenashortsummaryforeachitem.
8.1
Foundation Architecture / Technical Reference Model (TRM)
InthiscaseitiseasiesttohaveTOGAFspeakforitself: The TOGAF Foundation Architect ure is an architectur e of generic services and functions that provides a foundation on which more speci fic architectures and architectural components can be built. This Foundation Architecture is embodied within the Technical Reference Model (TRM), which provides a model and taxonomy of generic platform services. The TRM is universally applicable and, therefore , can be used to build any system architecture. Source [TOGAF9.1; Chapter 43]
BeforewewastetimeexplainingwhatthesubjectmatteroftheTRM is about, webetter use one picture ( Figure 15 ), which explains the subject area much fasterthana verbaldefinition.TRMis aboutthe servicesanytechnologystackneedstooffer.
© 2009-2012 Wolfgang W. Keller – all rights reserved
8 What else will you find in TOGAF?
41
Figure15:SimplifiedviewupontheTOGAFTRMOverview.Forthe analogousfigureinTOGAF9.1seeFigure43-2. http://www.opengroup.org/architecture/togaf9-doc/arch/Figures/43_trm_detail.png (Linkchecked2012-04-24)
AsintheIII-RM (seenextsection) the mainuseof such areference modelisterminologyandchecklists.Youdon’targueabouttheterms and you cancheck for yourself whetheryou need the services enumerated in the reference model andwhether youhave all services youneedpresentinyourtechnologystack.
8.2
The Integrated Information Infrastructure Reference Model (III-RM)
TheIII-RMgivesyoua20pagetaxonomyforallkindsofapplication softwareinanenterprisethathasthegoalofsocalledboundary-less informationflow,meaninganenterprisewhichisintegratedwiththe outside world’s logistics chains via buying and selling circles. The benefitof the chapteris thatyou get avocabularyfor talking about enterprises integrated with the outside world via electronic data exchange. WewillnotreprintanyOpenGroupdrawingshere.Mainlyforcopyrightreasons.BesthaveashortlookatTOGAFChapter44
© 2009-2012 Wolfgang W. Keller – all rights reserved
9 Wrap Up: TOGAF for You
42
9 Wrap Up: TOGAF for You
9.1
A Collection of Useful Stuff
Throughout this book wehave demonstrated that TOGAF is a very usefulcollectionofmanymethodsandtoolsthatanenterprisearchitectmightneedforhiswork. Neverthelesswecouldalsosee,thatTOGAFismorea growncollectionofveryusefulitemsthananintegratedpieceofwork,planned inadvanceonadrawingboard.TheArchitectureDevelopmentMethodissomewhat“closedinitself”–soistheContentFramework.But manyotherthingsarecollectionsoftoolsandadditionstotheADM: Whichis NOTnegative!But aswe assumed intheintroduction and couldnowkindofprove:TOGAFisnotan“EnterpriseITArchitecture for Dummies” Cookbook. TOGAF has a clear focus on developing architectures: Be it single systems or subsystems, be it clusters of applicationssystemsorbeitablueprintforthetoplevelarchitecture ofanenterprise.Thelastofthesewillhardlyeverbedesignedona drawingboardbutwillbea resultoforganic growthpluseitheran explicitorimplicitstandardforanindustry.
9.2
The Two Strongest Points
ThetwoareasinTOGAFthatmakethekerneloftheframeworkare: n
n
ADM: TheArchitecture DevelopmentMethod is a really mature and extensivemethod,checklist and guide that you canemploy whenyouwanttodesignanypartofyourITarchitecture. Architecture Content Framework: This Framework lets you bringordertoyourarchitecturalartifactsevenifitdoesnottell youhowtocreateallofthem.Themeta-modelpartgivesyouan extensive library of meta-objects that youcan at least consider usingwhenyouhavetoconstructthespecificmeta-modelthatis abletoanswerthequestionsyourmanagementhasfortheirEnterpriseArchitectsinthecontextoftheirenterprise. © 2009-2012 Wolfgang W. Keller – all rights reserved
9 Wrap Up: TOGAF for You
43
Besidesthatwealreadylistedalotofotherusefulstuffthatyoucan findinTOGAF.
9.3
TOGAF Certification
Ifyoustudyjobadverts,there’sarecenttendencytomentionTOGAF certification whenever an Enterprise Architect is wanted. In this bookwehavedemonstratedthatTOGAFisnotreallystrongatstrategicEnterpriseITArchitectureManagement.TOGAFisstrongatprojectarchitecturesofallscalesandsomeofthetasksofstrategicEnterpriseITArchitectureManagement. As withany certification, TOGAFcertification is for surebeneficialtothose who offerthecoursesandexams.If itcomestoHR departments and senior management, the ones who oftenhire Enterprise IT Architects, it can be doubted, whether they have deep knowledgeofthedifferencesbetweenStrategicITManagementand thekindofEnterpriseITArchitecturethattheTOGAFADMisgoodat. SoifyouwanttohiresomebodywhoisabletoperformEnterpriseIT Architecture Management a TOGAF certificate covers maybe 30% percent ofthe job– andto the authors regret – the less important 30% because the important part is about business strategies and businessmanagement. So for manyEnterprise Architects the TOGAFcertificate willbe justanotherdriverslicense.Thelicensesaysthatyouareentitledto drive–itdoesnotsaythatyouareagooddriver.Neverthelessyou haveto takethe testif the public (representedby the government) makesitmandatorytohavethelicense.Orifthemajorityofcompanies require a TOGAF certificate people will need one as an entry ticketforcertainjobs.
© 2009-2012 Wolfgang W. Keller – all rights reserved
9 Wrap Up: TOGAF for You
9.4
44
Future
Predictions are hard tomakeand makingpredictionsby looking at thepastoftendoesnotmaketoomuchsense.Thefirstversionofthe TOGAFADMwasderivedfromTAFIM2.0around1995.Today’sADM hasalonghistoryandnorootsinstrategicarchitecturemanagement. In 2009 the Architecture Content Framework was added from the CapgeminiIAF(IntegratedArchitectureFramework).Thiswasmade possible because Capgeminiinvested a lot in supportingthe OpenGroup and TOGAF. In late 2011 TOGAF 9.1 has been released – no groundbreakingnewversionbutamaintenancerelease. WhetherTOGAFwillbecomeafullframeworkforthemorestrategicpartsofEnterpriseITArchitectureManagementishardtopredict–ifnotunpredictable.Inanycaseitisveryusefulfordeveloping architectures in concrete projects no matter whether they have a smalloraverylargescope.
© 2009-2012 Wolfgang W. Keller – all rights reserved
10 References
45
10 References
[Alexander79a]ChristopherAlexander: TheTimelessWayofBuilding. OxfordUniversityPress,NewYork,1979. [Alexander79b]ChristopherAlexander:APatternLanguage.OxfordUniversityPress,NewYork,1979. [Bass+98]LenBass,PaulClements,RickKazman:SoftwareArchitecture inPractice.Addison-Wesley,1998. [Broadbent+05]MarianneBroadbent,EllenS.Kitzis:TheNewCIOLeader.HarvardBusinessSchoolPress,2005. [Brooks75]FrederickP.Brooks,Jr.:TheMythicalMan-Month.Essayson SoftwareEngineering.Rea-ding,Mass.etal.:Addison-Wesley1975. [Buschmann+96]FrankBuschmann,RegineMeunier,HansRohnert,PeterSommerlad,MichaelStal:PatternOrientedSoftwareArchitecture,ASystemofPatterns,Wiley1996. [Clausewitz98]CarlvonClaussewitz:VomKriege.UllsteinTaschenbuch 1998. [Coplien96]JimCoplien:SoftwarePatterns.SIGSPublishing,NewYorket al.1996. [Coplien97]JimCoplien:APatternLanguageforWriters’Workshops; availableathttp://www.riehle.org/community-service/hillsidegroup/europlop-1997/p2final.pdf (linkchecked2009/03/25) [Dern09]GernotDern:ManagementvonIT-Architekturen.3 rdEdition, ViewegVerlag,EditionCIO,2009. [Gamma+95]ErichGamma,RichardHelm,RalphJohnson,JohnVlissides: DesignPatterns,ElementsofReusableObject-orientedSoftware, AddisonWesley1995. [GarlanShaw96]DavidGarlan,MaryShaw:SoftwareArchitecture:PerspectivesofanEmergingDiscipline;PrenticeHall1996.
© 2009-2012 Wolfgang W. Keller – all rights reserved
10 References
46
[Hanschke10]IngeHanschke::StrategischesManagementderITLandschaft.EinpraktischerLeitfadenfürdasEnterpriseITArchitectureManagement;2.AuflageHanserVerlag2010. [ITIL02]OGC;OfficeofGovernmerntCommerce:BestPracticeforICTInfrastructureManagement.PublishedbyTSO–TheStationeryOffice, 2002. [Kaplan05]JeffreyKaplan:StrategicITPortfolioManagment;Governing EnterpriseTransformation;PittiglioRabinTodd&McGrath(PRTM) Publishing2005. [Keller12]WolfgangKeller:IT-Unternehmensarchitektur,2.Auflage, dpunktVerlag2012. [Longepe03]ChristopheLongepe:TheEnterpriseITArchitectureItProject:TheUrbanisationParadigm;KoganPageScience;2003 [Riege05]ChristianRiege:MethodenfürdasManagementvonAnwendungsportfolios–einevergleichendeUntersuchung.Diplomarbeit, UniversitätLeipzig,2005. [Ross+06]JeanneRoss,PeterWeil,DavidC.Robertson:EnterpriseITArchitectureasStrategy:CreatingaFoundationforBusinessExecution.Mcgraw-HillProfessional2006 [Schekkerman04]JaapSchekkerman:HowtoSurviveintheJungleofEnterpriseITArchitectureFrameworks.VerlagTrafford,Victoria,Canada,2004. [sebis08]sebis:EnterpriseITArchitectureManagementToolSurvey 2008.AvailablefromTechnicalUniversityMunich,ChairofFlorian Matthes;http://wwwmatthes.in.tum.de/wikis/sebis/eampc(link checked2009/03/25) [Shaw+96]MaryShaw,DavidGarlan:SoftwareArchitecture–PerspectivesonanEmergingDiscipline.PrenticeHall,1996. [Sowa+92]J.F.Sowa,J.A.Zachman:ExtendingandFormalizingthe FrameworkforInformationSystemsArchitecture.IBMSystems Journal,Volume31,No.3,1992.IBMPublicationG321-5488. [Starke05]GernotStarke:EffektiveSoftwarearchitekturen.3.Erweiterte Auflage,HanserVerlag,2008. [TOGAF8.1.1]TheOpenGroup:TOGAFEnterpriseEdition.Version8.1.1: availableathttp://www.opengroup.org/architecture/togaf8doc/arch/.TheOpenGroup,2007. [TOGAF9.1]TheOpenGroup:TOGAFVersion9.1;availableat http://www.opengroup.org/architecture/togaf9-doc/arch/;The OpenGroup,2011.
© 2009-2012 Wolfgang W. Keller – all rights reserved