In thefirst blogof this series,I explained how important it is to raise your digital change capability to become an adaptive enterprise. I also highlighted therole of effective communication,as well as approaches to categorize and visualize enterprise architecture descriptionsbased on the TOGAF and ArchiMate standards. In this series, I also includedguidance on which approach to select for modeling Architectureand Solution Building Blocks (both are types of logical or physical components). To round out this series,I will end by discussing the connection to Deployed Solutions.
TOGAFdescribesthe physicalapplicationcomponentas “deployable component, e.g. a deployed instanceof an ERP”(TOGAF 34.5).As explained earlier,the Architecture(ABBs)and Solution Building Blocks(SBBs)refer to types of objects.Youcan use this to distinguish physical application components into types as SBBs and instances as DeployedSolutions.The Deployed Solutions areinteresting whendocumentingexisting solutions,managingthem (e.g. in an applicationportfolio)orreusing that information in architecture development.In terms of modeling them in ArchiMate, you can usethe sameconceptson solutions and deployed solutions levels todifferentiatetypes and instances.Often,it is helpful to add asuffix to the nameof the instancesas a naming convention (e.g. “SAP ERP P123”).Ifyouwant to relate solution types and deployed solution instances, I recommend using the specialization relation in ArchiMate. That wayyou candescribe something of the same kind, but with different parameters / configurations.The picture below showshowyou canmodelthe Enterprise Continuum inArchiMateusing the first approachdescribedhere.
Adding the business & technology layer
The TOGAF Architecture Development Method (ADM) names dedicated phases for thedevelopment ofbusiness and technology architectures.For explanation purposes, the mapping shown aboveisbased on the application layer, but you can transferitto the business and technology layer, too.
Usually,the instances oftechnologiesare notofinteresttoenterprise architecture development (e.g. Windows Version 20XX License Number ABCXYZ), so I don´t model them inthiscontext. A candidate to modelat thisdeploymentlevelis a nodecomposingthe different technology solutionsthat shouldbe implementedin a projector importsof existing serversfrom CMDBs. Since I used the internal ArchiMate active structureconceptofapplication componentfor the physical application component, this approach uses theconcepts ofsystem software or(hardware)device to model the technology pendant. The function concept also exists at the technology layer, so this isa straightforwardmapping.
Thebusinesslayer can also bedescribedwith the same approach.The business architectureoftencontainsbusiness processesto describe the behavior assigned todepartments (orroles), so I explicitly include themnext to business functionsfor the business layerhere.Small ArchiMateexcursion:Both, businessprocessesand the business functionsdescribeinternalbusinessbehavior. The difference is that the business processgroupsbehavior according to a specific order of activities, while the business functiongroups behavioraccording to a set of characteristics (e.g. knowledge).As you know, the term“business function”is sometimesalso used for department-like entitieswhich represent active structure elements in the ArchiMate frameworkthat is performing behavior(e.g. business processes).Being ArchiMate-strict,departmentsare usuallymodeledas business actors,which is then the pendant to the physical application,whilefunctions/ processesarethe pendant to the logical/functional aspect.
What is the take awayof this blog series?Inthe first blogIraisedtheneedto become anadaptive enterpriseinafaster-changing environmentandexplained howlanguage plays a critical role in communication.Proper tooland methodologysupportarealsoimportant ingredientsindigitizing your change capability!At the same time,theenterprise architecture function provides aholistic viewon impactsfor strategic transformationsacrossinitiatives. When talking about strategy and change projects,there is also a need to describe different types of architectures.Youhave seenhow toclassifyarchitecturesbased on the TOGAF standard andhow to visualizethem by using ArchiMate standard.I will nowtake all that we’ve covered in this series toprovide a practical example of thewholeTOGAF Enterprise Continuum.
As you see, the foundation architectures are mainly modeled withinthe technology layer,while the other more specific architectures areusuallymodeled with the application and business layer. This makes sense since youmainlybuild your applicationarchitecture ona foundation/ technologythat you don´t developyourself,butratherbuy and configure(e.g. MS SQL).The example does also reflect thatTOGAFand ArchiMate havethe ability to describe business and IT for a better alignmentto support strategictransformations.
I hope you enjoyedreadingthisseriesandfoundthe application of the ArchiMate framework to the TOGAF Enterprise Continuumhelpful.For more in-depth discussions, checkoutour trainingoffersforArchiMate, TOGAFand more. You can also learnhow Enterprise Studio andHoriZZoncansupportthesestandards.
SUBSCRIBE TO BIZZDESIGN'S BLOG
Join 10.000+ others! Get BiZZdesign's latest articles straight to your inbox. Enter your email address below: