Integrated Business and IT Modelling

LECTURE 4: Integrated Business and IT Modelling in ArchiMate IIAB401 Enterprise ArchitectureCRICOS No. 00213JDr.ReihanehBidarFaculty of ScienceQueensland University of Technology1 Unit Plan 2Week 2:Business capability modelling IWeek 3:Business capability modelling IIWeek 4:ArchiMate modelling IWeek 6:ArchiMate modelling IIWeek 5:Guest LectureWeek 7:UML IWeek 8:UML IIWeek 9:IT solution architecture IWeek 10:IT solution architecture IIWeek 11:IT physical sys architectureWeek 13:Unit summary and Quiz preparationWeek 12:Guest lectureWorkshops: week 2-13Week 7: Assignment 1 dueWeek 13: Assignment 2 dueQuiz Assignment 1 releaseAssignment 2 releaseWeek 1:Intro to EA BusinessStrategyBusiness ArchitectureEnterprise ArchitectureIT Solution and Software ArchitectureOperational ArchitectureBusiness ModelsBusiness Capability MapBusiness and IT integrated modelsTarget operating models, business process models and resource modelsSolution design models, software architecture, task and workflow modelsStrategic planning: what the business does at the highestlevel Ta c t i c a l p l a n n i n g : w h a t t h e b u s i n e s s d o e sas translated from business strategyand aligned to operations Operational planning: “blueprint” of what both business and IT doDetailed operational planning:focussedon set of operations, assigned to different projectsTe c h n i c a l o p e r a t i o n a lplanning: IT development orProcurementArchitecture in the organisational layersStrategicTacticalOperational3 BUSINESS PLANNING:Val u e Stream sBusiness Capability Map Infrastructure External infrastructure services Application components and services Roles and actors External application services External business services Damage claiming process Client Insurant Insurer ArchiSurance Registration Payment Valuation Acceptance Customer information service Claims payment service Customer administration service Payment service CRM system Financial application Customer information service Claim registration service Claim registration service Claims administration service Policy administration Claim files service zSeries mainframe DB2 database Financial application EJBs Customer files service Sun Blade iPlanet app server Claim information service EA Business-to-IT Models:ArchimateSolution design and implementationData modelsProcess modelsSoftwareDesign/configEnterprise ArchitectureSolution ArchitecturesHigh-levelProcessmapIntegratedscenariosDetaileddataanalysisDetailedprocessanalysisTechnicalanalysisArchitecture to solutions journey BusinessArchitectsSolutionArchitectsBusinessAnalystsEnterpriseArchitectsBusiness ArchitectureTechnicalArchitectsBusiness StrategyBusiness modelThe Board4 Lecture 4 objectives•Understand how enterprise architecture is structured to support business and IT planning –based on layered architecture•Focus is on translating business capabilities and value streams into high-level EA models•Understand a specific EA method: Archimate (used as part of TOGAF)•Be able to apply EA modelling at•Business•IT application•and IT infrastructure layersthrough Archimate5 1.M. Lankhorstet al. Enterprise Architecture at Work: Modelling, Communication and Analysis (2ndEd). Springer-Ve r l a g, 20092.The Archimate3.0 Specification http://www.opengroup.org/archimate/downloadsReading6 AgendaAspects and layers of enterprise architecture Modeling business operationsModelling organizational context using ArchiSurance case study 7 Challenge of aligning business and IT through EABusinessInformationApplicationTe c h n o l o g yTOGAF EA elementsInfrastructureOther applicationsBusiness ProcessesBusiness ObjectsSOA Business and Information ServicesIntegration ServicesOperational ResourcesApplication Reference Architecture123Va l u e S t re a mCapabilitiesISISISISISISISHigh-levelcapabilityto VS map??Detailedcapabilityto VS stage map8 EA layers use inTOGAF Architecture development Method (ADM)9 TOGAF EA layers through ArchiMate Infrastructure External infrastructure services Application components and services Roles and actors External application services External business services Damage claiming process Client Insurant Insurer ArchiSurance Registration Payment Valuation Acceptance Customer information service Claims payment service Customer administration service Payment service CRM system Financial application Customer information service Claim registration service Claim registration service Claims administration service Policy administration Claim files service zSeries mainframe DB2 database Financial application EJBs Customer files service Sun Blade iPlanet app server Claim information service Business layerApplication layerTe c h n o l o g y l a y e r10 EA modelling method: ArchiMate•An Open Group EA method supported by tool vendors, consulting firms and businesses•ArchiMate is a graphical language that provides a uniform representation for models to support the complete architecture development cycle.•Enables modeling throughout the TOGAF Architecture Development Method–ArchiMate Core corresponds with the three main architectures as addressed in phases B, C & D in the TOGAF® ADM–The extensions to the Core closely correspond with the main aspects to be addressed in the Preliminary phase, Phase A and the Central Requirements management repository, as well as Phases E, F, G and HSeveral examples illustrating Archimatein this presentation have been drawn from: M. Lankhorstet al. Enterprise Architecture at Work: Modelling, Communication and Analysis (2ndEd). Springer-Ve r l a g, 200911 AgendaAspects and layers of enterprise architecture 12Modeling business operationsModelling organizational context using ArchiSurance case study Organisational context•Organisationalstructure –actors, roles, hierarchy•Collaborations with partners inside and outside organization•Key business functions and information flow13 ArchiSurancecase study14 Business layer modelling: org. contextOrganisational structureBusinessactor15 Explanation of model•ArchiSuranceis an organisation, modelled as an actor•It consists of 5 first-level organisational units modelled as actors:–Front Office, Back Office, Document Processing SSC, Finance, Product Development and HRM•Two of these organisational units each consist of other, second-level organisational units:–Front Office: Customer relations, Intermediary relations–Back Office: Home & Away, Car and Legal Aid16 Business layer: Business actoroHuman resource entity delivering value to customers and internal parts of the organisation, and collaborating with partners and stakeholdersoPermanent or long-term status within organisationoCorresponds to person or groupoHieratically composed to reflect org. structureoCapture for “end-point” delivery –directly associated with services and products, not processes (unlike BPM techniques) 17 Business layer: Business roleoResourcing need for product and service delivery, focussed on the nature of involvement of actors –i.e. functional designation or responsibilityoA business actor acts in a business role, i.e. business actor has assignsrelationship with business roleoAllows operational planning without direct reference to org. structure –roles change less than actorsoA business actor can be assigned multiple roles and a role can have multiple actors assigned to itoBusiness role usage in operations:ØBusiness role uses a business serviceØBusiness role used in business process typically via business service18 Relationship between Roles and Actors 19 AssignsBusinessroleBusinessactorBusinessCollaboration –specific area ofInteractions between rolesUses, but doesnot containOrganisational collaborations Business layer: Business collaborationoPossibly temporary combination of two or more roles resulting in collective behaviour (interactions) in a particular context20 Explanation of model•The “big picture” of collaborations between a number ofbusiness partners and customers on the basis ofthe roles they play•ArchiSurance assigned as an Insurer role and other roles Customer, Customer’s Bank and Intermediary without the actors they’re assigned to•Customer and Intermediary collaborate for Negotiations (for insurance offers from different insurers)•Customer, Intermediary and Insurer collaborate for Contracting (for the customer to obtain a specific insurance offer from an insurer)•The Customer, Insurer and Customer’s Bank collaborate for Premium Collection (for setting up the process regular payments from the customer to the insurer for the insurance offer)•The Customer, Insurer and Customer’s Bank collaborate for Claim Fulfillment (for the customer to get money for a specific claim)21 Business layer: Business function•Business functions describe what the organization actually does; they are explicitly managed, andare more closely aligned to the organization structure.•Main use is grouping business processes and activities for required skills, knowledge, resources•Can used as basis for organisation capability map alignment with operations. Multiple business functions may (together with other elements) contribute to the realization of a capability. •Functions can be composed of other functions22 Capability vs Business Functions23 Business layer: process and functionIntegration scenarios -aligning business process to business functionsThis model showshow businessfunctions can bealigned to businessprocesses24 Explanation of model•The alignment of business processes with business functions•Business functions (Managing Customer Relations, Claims processing, and Financial Handling) are aligned across different processes (Handle Request and Handle Claim):–The Managing Customer Relations business function is aligned to Receive Request from Handle Request process and Receive Claim from Handle Claim process–The Claims Processing business function is aligned to Judge claim from Handle Claim process–The Financial Handling business function is aligned to Collect premium from Handle Request process and Pay compensation from Handle Claim process25 Business layer: Business interface •Business interface: the (logical or physical) locations where the services that a role offers to the environment can be accessed (services are assigned to interfaces). oThe way a business role interacts internally or externally in an organisation, otherwise known as a communication channeloExamples include mail, telephone, Web or mobile channel26 AgendaAspects and layers of enterprise architecture 27Modeling business operationsModelling organizational context using ArchiSurance case study Business operations–Key services and processes•Captures value stream maps (process blocks)•integration scenarios (services, processes, events and other details)–Key partners and stakeholder interactions–Key business objects used Business operations AccessBusiness objectRepresentationBusinesseventBusinessprocessJunctionin processBusiness actorBusiness roleUsesAssignsBusinessserviceRealisesVa lu e stre a m m a p –integrated scenarios 29 Explanation of model•A part of a value stream broken down into an integrated scenario•The value stream part being analysedis: Handle Claim•The Handle Claim is broken into the following process flow: Register, Accept, Value and Pay/Reject)•An event triggers the process: Damage•The process supports three services: Claim registration Service (supported by Register), Claim information service (supported by Accept), and Claim payment service (supported by Pay)•The three services are used by an Insurant role which is assigned to a Customer actor•The process produces a Notification business object sent through a Letter30 Business layer: Business objectoA collection of data that logically represents an information artefact of interest (e.g. purchase order, bank account)oAccessed by a business process, service, interaction or eventoCan either be an administrative(used internally) or messageobject (used to exchange information with external parties)oOften forms the basis for structuring core parts of business service and application servicesoHas one or more perceptible forms that apply to different contexts, i.e. has a Representation31 Business layer: Structural concept •Business Objects represent important concepts in which the business thinks about the domain and are manipulated by behaviors. 32 Products –Tangible or intangible artefact which can be offered to the market which satisfies consumer needs or wants (consumable)–Material, service, idea, method or information that serves a need or want. It has a combination of tangible and intangible attributes (benefits, features, functions, uses) that a seller offers a buyer for purchase.–Products can be combined into bundles to improve value for market–Does not expose processes, applications, infrastructure details33 Business layer: Business product (process context)oCoherent collection of services or other products offered as a whole internally or externallyoServices could be business, application or technology servicesoBuying product gives customer a right to use associated its bundled services and productsoAgreements between provider and consumer are drawn up in a business contract associated with the productoPortfolio management of product types is important factor in organisational planning and enterprise architectures, as products are more stable than services, processes, functions34 Business layer: process contextBusinessproductProduct bundling 35 Explanation of model•A typical insurance product of ArchiSurance. The value to the customer of an insurance is typically the added security it provides.•Theinsuranceproductconstitutessixservices(Insuranceapplicationservice,Premiumpaymentservice,Customerdatamutationserviceandetc.)36 •Thenotionof‘service’isimportantfororganisingmanagementandaccesstobothbusinessandITsystemsbecauseitprovidesanencapsulated(‘black-box’)viewoffunctionalitythataconsumerisinterestedin,withoutrevealingdetailsoftheproviderwhattheproviderdoestodeliverthefunctionality.•Serviceorientationsupportscurrenttrendsrangingfromtheservice-basednetworkeconomytoICTintegrationwithWe bservices.Services –key to linking EA layers37 Business layer: process context•Business service :provides an encapsulated (‘black-box’) view of functionality that a consumer is interested in, without revealing details of the provider what the provider does to deliver the functionality oFocus on key capabilities -value delivered, typically conveyed through information, goods and other physical artefactsoSubject to delivery constraints, e.g. time, place, price, rewards, rights, penalties –service level agreements between providers and consumersoDelivered through roles –a business role uses one or more services38 Services –key to linking EA layersConsumersBusiness servicesBusiness processesApplication servicesApplication componentsPlatform/infrastructure servicesPlatforms/infrastructurePrimary applicationcomponentsInternal applicationservicesSupporting applicationcomponentsArchimate[M. Lankhorst et al. Enterprise Architectureat Work: Modelling, Communication andAnalysis (2ndEd). Springer-Verlag, 2009]Business layerApplication layerTe c h n o l o g y layer39 Business layer: process context•Business process : A flow of activities with one or more clear starting points and leading to clearly defined results. oA collection of causally related internal behaviour –how organisations plan and execute their internal operationsoAimed at supporting the delivery of products and services through realizerelationship oCan be aggregated of other business processes and activities (elementary forms)Events Process 40 Business layer: process contextIntegration scenarios -Realisation41 Explanation of model•The model shows the realisationof business services by ArchiSurance business processes•There are five business services that constitute the travel insurance product, and they are realisedby business processes–Insurance application service is realisedby Close Contract.–Claim registration service and Claims payment service is realisedby Handle Claim–Customer information service is realisedby Inform Customer–Premium payment service is realisedby Collect Premium42 Business layer: process context•Business eventoSomething that happens internally or externally and influences an organisation’s operations (business processes, functions and interactions)oUsed for capturing triggers (to start processes), although other types of events have different effects, e.g. interrupting a process (note not modelled at in business process in a vertical EA)oEvents can integrate a number of business processes –causal dependency which trigger processes and arise from them43 Example of Business layerModel integrated scenarios 44 ConceptDescriptionNotationBusiness actorAn organizational entity that is capable of performing behavior.Business roleThe responsibility for performing specific behavior, to which an actor can be assigned.Business collaborationAn aggregate of two or more business roles that work together to perform collective behavior.Business interfaceA point of access where a business service is made available to the environment.Business processA behavior element that groups behavior based on an ordering of activities. It is intended to produce a defined set of products or business services.45 ConceptDescriptionNotationBusiness functionA behavior element that groups behavior based on a chosen set of criteria (typically required business resources and/or competences).Business interactionA behavior element that describes the behavior of a business collaboration.Business eventSomething that happens (internally or externally) and influences behavior.Business serviceA service that fulfills a business need for a customer (internal or external to the organization).Business objectA passive element that has relevance from a business perspective.46 Exercise47Joe, a construction worker injured at work, calls his disability insurance company. He speaks to a Contact CenterRepresentative , who connects him to Mary, an insurance company Claim Intake Specialist. Joe works with Mary to initiate a disability claim. As Joe speaks with Mary, she uses her company's Claim Intake System (Application Component realizing an Application Service called Claim Initiation) to begin the intake process. Mary enters basic information about Joe's claim. (business actor)(business role)(business role )(business collaboration ) (Business objects) (Business process)(business role: claimant) Exercise48Contact centerContact centerrepresentativeClaim intake specialistClaim intakeConstruction workerClaimant(business role)(business role)(business role)(business actor)(business actor)(business process) Dr.ReihanehBidar|Associate LecturerSchool of Information SystemsScience Faculty Queensland University of TechnologyEmail: [email protected]://staff.qut.edu.au/staff/r.bidarThanks!Any Questions?49