Experiences with enterprise architecture using togaf and ibm rational system architect at dn b nor
Upcoming SlideShare
Loading in...5
×
 

Experiences with enterprise architecture using togaf and ibm rational system architect at dn b nor

on

  • 1,422 views

 

Statistics

Views

Total Views
1,422
Views on SlideShare
1,422
Embed Views
0

Actions

Likes
0
Downloads
58
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Tool acquisitionInitial TrainingDeploymentPilot projectsStartup InfrastructureFormalization/Packaging of material for quick enablement of further projectsTailoring the metamodel to the organizationTool tailoringOrganization changes to support the EA effort
  • TO SUMMARIZE:It’s not about each project trying to adapt to other related projects. Typical for project mandates are that they list which projects they have a relation to. But then each project will have its own viewpoint of the totalityNot to coordinate at group level. In DnB NOR we have tried this with an Architecture Board. Of course you need an architecture board, but it is not sufficient to support proper evolvment of an EAWhere I think the TOGAF ADM cycle reallty contributes, is because it focuses on EA being a holistic, top-down approach to implement the business strategy.
  • Communication: shows how things are tied together.Is basis for: reports, constraints.
  • So if we go back to where we started. Where EA was in the centre of business architecture, Information Architecture and Technical architecture. In the same way that EA is not about all aspects within these areas, the EA metamodel should neither model everything – but only those parts where these areas intercept.We don’t model everything – only those parts “relevant” to our EA view
  • Not as pretty as PPT.Diagrams & Analytics Strengths of SA, can extend to new diagram types.Different views on one diagram (after analytics applied). How to manage this when template changes?
  • Now as pretty as PPT.Diagrams & Analytics Strengths of SA, can extend to new diagram types.Different views on one diagram (after analytics applied). How to manage this when template changes?
  • Now as pretty as PPT.Diagrams & Analytics Strengths of SA, can extend to new diagram types.Different views on one diagram (after analytics applied). How to manage this when template changes?
  • SA: cannot show analytics dynamically
  • No out of the box metamodeling language support, so chose class diagramNeed proper tool support.

Experiences with enterprise architecture using togaf and ibm rational system architect at dn b nor Experiences with enterprise architecture using togaf and ibm rational system architect at dn b nor Presentation Transcript

  • June 5–9 Orlando, FloridaExperiences with EnterpriseArchitecture using TOGAF 9 andIBM Rational System Architect atthe Norwegian Bank DnB NORJames Dzidek, Ph.D.IT Consultant, Enterprise Architecturejames.dz@gmail.comEAM-1528Lars JørgensenEnterprise Architect at DnB NORlars.jorgensen@dnbnor.no
  • The Premier Event for Software and Systems Innovation2 © 2011 IBM CorporationOutline Short background on DnB NOR DnB NOR’s expectations for Enterprise Architecture Progress Status FrameworkHow we explain our objectives and contributionWhere do we fit in the organization and existing processes? MetamodelWhat are we actually documenting, why and how? ToolHow we use IBM Rational System Architect Practical Challenges & Advice Summary & Next Steps
  • The Premier Event for Software and Systems Innovation3 © 2011 IBM CorporationCurriculum Vitae CosmopolitanPoland, Italy, Canada, Norway, …? (somewhere warm) EducationB. Eng. in Computer SystemsM. Eng. in Software QualityPh. D. in Software Engineering @ Simula Research Laboratory -Thesis on the costs and benefits of using modeling techniques and tools PositionsSystems Engineer @ Nortel NetworksTechnical Presales @ TelelogicTechnical Presales @ IBMIndependent Consultant – Enterprise Architecture
  • The Premier Event for Software and Systems Innovation4 © 2011 IBM CorporationNorways leading financial services group Total combined assets > 2 100 billion NOK More than 2.3 million retail customers Norways largest Internet banks, dnbnor.no and postbanken.no,with more than 1.5 million users More than 200 000 corporate customers Norways most extensive distribution network for financial services Norways largest life and pension insurance company with around1 000 000 customers Norways largest asset management operation with more than 600000 mutual fund customers in Norway and 283 institutional clientsin Norway and Sweden Norways largest capital markets operation Norways leading real estate broker More than 14 000 full-time positions (incl. DnB NORD)
  • The Premier Event for Software and Systems Innovation5 © 2011 IBM Corporation….and the most international Partner for Norwegian companies abroad andfor large international companies in Norway International network of 13 branches andrepresentative offices Private banking in Luxembourg Operations in Poland and the Baltic statesthrough DnB NORD Presence in North-East Russia through DnBNOR Monchebank Norways leading foreign exchange bank One of the worlds foremost shipping banks A major international player in the energysector
  • The Premier Event for Software and Systems Innovation6 © 2011 IBM CorporationManeuvered well through the financial crisisSource: J.P.MorganNo. 38No. 22
  • The Premier Event for Software and Systems Innovation7 © 2011 IBM CorporationA History of Mergers & AcquisitionsMerger1990Acquisition1996Merger1999Acquisition2002Acquisition2003Acquisition1992Merger1990Merger 2003GjensidigeNOR ASADnCDnCBergen BankBergen BankFour largesavings banksFour largesavings banksSparebankenABCSparebankenABCDnBForenedeForsikringForenedeForsikringVitalVitalDnBDnBPostbankenDnBSkandia AMSkandia AMDnBGjensidigeLivGjensidigeLivNordlands-bankenNordlands-bankenDnBSparebankenNORSparebankenNORDnBGjensidige NORSparebankenNORDen norskeHypotekforeningGjensidige Bank/ Elcon FinansGjensidige NORSparebankSparebankenOslo/AkershusSparebankenOslo/AkershusFellesbankenFellesbankenMerger1985Real KredittRealkredittAcquisition1992Gjensidige NORSpareforsikringGjensidige NORSpareforsikringAcquisition1992Merger2002Acquisition1993Acquisition1999De-mutualisationDe-mutualisationAquisition2005/2010Aquisition2005
  • The Premier Event for Software and Systems Innovation8 © 2011 IBM CorporationDnB NOR’s Expectations for Enterprise Architecture See the various IT initiatives in context Ability to translate business strategies in into optimal IT solutions Help deal with frequently changing customer and business requirements Expectation of faster completion of analysis since individual projects can utilizealready-available data Commitment to this effort:o Process governed and owned by the chief architecto Involvement all the way from business decision-makers, via business architects, tosolution architects and developerso Team: project manager, subject matter experts, enterprise architects, consultantso Dedicated Enterprise Architecture Tools
  • The Premier Event for Software and Systems Innovation9 © 2011 IBM CorporationProgress StatusToolAcquisitionProjectReplanningPilot Phase Phase 1 Phase 2•Initial Screening•RFP•Vendor negotiations•Vendor Selection•Tool Deployment•Initial EA Training(selected resources)•Pilot Project Search•1 Pilot Project•Metamodel v 0.9•Tool customization•Gain experience•EA Ground work(EA infrastructure)•+2 pilot projects•Metamodel 1.0•Tool customization•Plan “steady state”•Metamodel 2.0•Tool customization•General frameworkfor accepting newprojects•Setting up reportingand publishinginfrastructure
  • The Premier Event for Software and Systems Innovation10 © 2011 IBM CorporationThe Enterprise Architecture trinityFramework Metamodel Tool EA trinity
  • The Premier Event for Software and Systems Innovation11 © 2011 IBM CorporationFramework Metamodel Tool EA trinity
  • The Premier Event for Software and Systems Innovation12 © 2011 IBM CorporationTechnology is an increasingly important competitiveness driverMobile ServicesCollaboration & MobilityCRM & Business IntelligenceSourcingArchitectureStandardized Processes
  • The Premier Event for Software and Systems Innovation13 © 2011 IBM CorporationDnB NOR – Software dev. method
  • The Premier Event for Software and Systems Innovation14 © 2011 IBM CorporationProject2Project1Project4Project3E.Opportunities & SolutionsProject-DrivenArchitectureProject3Project2Project1Architecture-DrivenProject Development
  • The Premier Event for Software and Systems Innovation15 © 2011 IBM CorporationThe TOGAF model in a system engineering modelProject 1Project 2Project 3Project 4
  • The Premier Event for Software and Systems Innovation16 © 2011 IBM CorporationTOGAF in the DnB NOR organization• Enterprise architecture• Long term perspective; 3-10 years• Defines constraints, principles and goals for theblueprint groupsEA• Portfolio different business areas with0-3 years perspective• TOGAFs segment architecture• Defines required projects and theirscope• Secure that projects deliver inaccordance to target blueprintsPortfolioBlueprint Group• Deliver in accordance tospecified scope andpremises• Projects are followed upby blueprint group withrespect to definedconstraints, goals etc.Projects
  • The Premier Event for Software and Systems Innovation17 © 2011 IBM CorporationOur message to the solution architects EA is not about each project “looking at its neighbors” It is not about coordinating project initiatives and governingthem at group level It is a holistic, top-down approach to implement the businessstrategy
  • The Premier Event for Software and Systems Innovation18 © 2011 IBM CorporationFramework Metamodel Tool EA trinity
  • The Premier Event for Software and Systems Innovation19 © 2011 IBM CorporationDnB NOR’s Approach to Metamodeling1. Start with usage scenarios – which questions do we need to answer in ourEnterprise Architecture work?2. Analyze which common information elements contribute to answering the usagescenarios3. Seek to find the proper elements in the TOGAF 9 content metamodel or the built-in elements in the tool (Rational System Architect)4. If not found – create a new element on basis of existing knowledge/resources5. Specify the definition or adapt the default definition to our own organization6. Define the associations between the elements
  • The Premier Event for Software and Systems Innovation20 © 2011 IBM CorporationDnB NOR Metamodel<<internal>>ApplicationPOS IDPOS NameSubject Matter ExpertSystem OwnerMaintenance ResponsibleIT UnitLast Update<<togaf>>Organization UnitColor Legend<<togaf>>Technology ComponentPlatform Services<<togaf>>BusinessProcess<<togaf>>Business Function<<internal>>Integration<<togaf>>Business ServiceSLA<<internal>>Application Service<<internal>>Message<<togaf>>Principle<<internal>>InformationSystemProcess<<togaf>>ConstraintInformationSystemProcessDiagram<<internal>>TechnologyPlatform<<togaf>>InformationSystem ServiceBusinessProcessDiagram<<internal>>Manual Activity<<internal>>FunctionGroup<<internal>>FunctionDomain<<internal>>ArchitectureBlueprint<<internal>>AutomatedActivity<<togaf>>Role<<togaf>>Actor<<togaf>>Data Entity<<togaf>>ProductPhysical Service modelBlue Association: Transcends Business/ ITBordersupported byhas particluar importance forconstrains / directsbased on1..*deployed ondeployed on 0..*built up bydepends oninteracts viatravels across1 1..*provides and receives via an interface1 1..*depicted by1 1belongs to**supported by**performed bycontainscontainsconceptually depicted byrefined byconceptual associationsparticipates inownsorchestrates0..*producescomposed ofsupportscan supportcomposed of0..*produces & distributes containsparticipates inimplemented byserves/handlesinvolvesinvolvesis supported byexecuted by1..*composed ofofferssupportscalls0..*A Function Group canbelong to one and onlyone Function Domain.
  • The Premier Event for Software and Systems Innovation21 © 2011 IBM CorporationBusinessArchitecture(Process / Org)InformationArchitecture(Data / App)TechnicalArchitecture(Middleware / Platform / Network)The Metamodel in ContextColor Legend<<togaf>>Organization Unit<<togaf>>Business ServiceSLA<<internal>>ApplicationPOS IDPOS NameSubject MatterExpertSystemOw nerMaintenance<<togaf>>Function<<togaf>>Information SystemService<<internal>>ApplicationUsage Profile<<internal>>Function Group<<internal>>ApplicationService<<internal>>FunctionDomain<<togaf>>Actor<<togaf>>Process<<togaf>>Product<<togaf>>Role<<togaf>>Data EntityLight Grey: Ternary associationPhysical Service modelBlue Association: Transcends Business / IT Borderinterfaces associationsparticipates inownsdistributesorchestrates0..*producescomposed ofsupportssupportscomposed of0..*producescontainsparticipates inimplemented byserves/handlesinvolvesinvolvesis supported byexecuted by1..*composed ofofferssupportscalls0..*
  • The Premier Event for Software and Systems Innovation22 © 2011 IBM CorporationAdvantages of having an explicit metamodel Greatly aids understanding Greatly aids communication Forms the basis for reports Forms the basis for constraints
  • The Premier Event for Software and Systems Innovation23 © 2011 IBM CorporationPrinciples The metamodel will never be “complete”o Start with the most important projects and their analytical needso Projects can extend the metamodel for specific needso Harvest experience from the projects to corporate metamodel Simplicity and maintainability over absolute truth Minimize ambiguity and inconsistency Base it on TOGAF 9’s content metamodel Involve the customer (i.e. the projects)If a repository should at the same time contain data at conceptual, logicaland physical levels, there will be inconsistencies. In particular, models willnot be perfect for all stakeholders, for all points of view, at all points in time.
  • The Premier Event for Software and Systems Innovation24 © 2011 IBM CorporationFramework Metamodel Tool EA trinity
  • The Premier Event for Software and Systems Innovation25 © 2011 IBM CorporationInternational IT AS-IS203 IBISASAP-LC!Zenit921 TBI405 Liquidity modul580 DnB NOR Online238 GL 161Local reportingReportingNorkom AMLKalkmotor711KVHClassify& indexLocal printingStorQMArchiveserviceDocArcPrangCross-key789 Msg HUB/EPP523 Merva479 WBI-FN794 ProPay406 Exchange rate234 WallStreet 221 Wallis890 Limit exposure039 Input023 Customer/004 Account075/6 Acc.hier.821 Limit check255 IMEX381 AegisFelix811 Telebank893BlueBoxBranches CustomerCorp.LendingFinanceTrade FinanceCashPoolFX/MMPayments-internationalInternetbankPayments-localArchive /doc. productionDataWarehouseComplianceReporting183 ProSwitchBACS UKBEC DenmarkInter bank transferSwedenBGC SwedenPostgirot SwedenLZB GermanyFinlandACH SingaporeACH (Wachovia) USACH USACH ChileACH ChinaICPFX/MM
  • The Premier Event for Software and Systems Innovation26 © 2011 IBM CorporationInternational IT TO-BEInt. HUBASAP-LC!Zenit580 DnB NOR Online238 GLLocal reportingReportingNorkom AMLKalkmotor KVHClassify& indexArchiveserviceDocArcPrangCross-key789 Msg HUB/EPP523 Merva479 WBI-FN794 ProPay406 Exchange rate234 WallStreet 221 Wallis890 Limit exposure039 Input023 Customer/004 Account075/6 Acc.hier.821 Limit check255 IMEX381 AegisFelix811 TelebankDLAOnDemandDialogueBranches CustomerCorp.LendingFinanceTrade FinanceCashPoolFX/MMPayments-internationalInternetbankPayments-localArchive /doc. productionDataWarehouseComplianceReporting542 C2B183 ProSwitchFLEXCUBE UBSFinArch?BACS UKBEC DenmarkInter bank transferSwedenBGC SwedenPostgirot SwedenLZB GermanyFinlandACH SingaporeACH (Wachovia) USACH USACH ChileACH ChinaICP
  • The Premier Event for Software and Systems Innovation27 © 2011 IBM Corporation“Architecting” in PowerPoint Advantageso Quick and Easy: almost no training necessaryo Availabilityo Flexibility That’s great, but…o Alterations are difficult to performo Analysis are very difficult to perform: various views (dimensions)o Inconsistencyo Ambiguityo Version Controlo Collaborationo Reuse of assets
  • The Premier Event for Software and Systems Innovation28 © 2011 IBM CorporationICPMetamodel: What are we actually trying to model?Int. HUBASAP-LC!Zenit580 DnB NOR Online238 GLLocal reportingReportingNorkom AMLKalkmotor KVHClassify& indexArchiveserviceDocArcPrangCross-key789 Msg HUB/EPP523 Merva479 WBI-FN794 ProPay406 Exchange rate234 WallStreet 221 Wallis890 Limit exposure039 Input023 Customer/004 Account075/6 Acc.hier.821 Limit check255 IMEX381 AegisFelix811 TelebankDLAOnDemandDialogueBranches CustomerCorp.LendingFinanceTrade FinanceCashPoolFX/MMPayments-internationalInternetbankPayments-localArchive /doc. productionDataWarehouseComplianceReporting542 C2B183 ProSwitchFLEXCUBE UBSFinArch?BACS UKBEC DenmarkInter bank transferSwedenBGC SwedenPostgirot SwedenLZB GermanyFinlandACH SingaporeACH (Wachovia) USACH USACH ChileACH China<<internal>>ApplicationLandscapeAssociation<<internal>>ApplicationPOS IDPOS Name<<internal>>Scenariocontainscontainsconceptual associations
  • The Premier Event for Software and Systems Innovation29 © 2011 IBM Corporation
  • The Premier Event for Software and Systems Innovation30 © 2011 IBM CorporationAssociating Scenarios with ApplicationInterface toGL161
  • The Premier Event for Software and Systems Innovation31 © 2011 IBM CorporationApplication Landscape: The Template
  • The Premier Event for Software and Systems Innovation32 © 2011 IBM CorporationApplication Landscape: Baseline
  • The Premier Event for Software and Systems Innovation33 © 2011 IBM CorporationApplication Landscape: Target
  • The Premier Event for Software and Systems Innovation34 © 2011 IBM CorporationManagement of Scenarios
  • The Premier Event for Software and Systems Innovation35 © 2011 IBM CorporationMetamodeling<<internal>>ApplicationPOS IDPOS NameSubject Matter ExpertSystem OwnerMaintenance ResponsibleIT UnitLast Update<<togaf>>Organization UnitColor Legend<<togaf>>Technology ComponentPlatform Services<<togaf>>BusinessProcess<<togaf>>Business Function<<internal>>Integration<<togaf>>Business ServiceSLA<<internal>>Application Service<<internal>>Message<<togaf>>Principle<<internal>>InformationSystemProcess<<togaf>>ConstraintInformationSystemProcessDiagram<<internal>>TechnologyPlatform<<togaf>>InformationSystem ServiceBusinessProcessDiagram<<internal>>Manual Activity<<internal>>FunctionGroup<<internal>>FunctionDomain<<internal>>ArchitectureBlueprint<<internal>>AutomatedActivity<<togaf>>Role<<togaf>>Actor<<togaf>>Data Entity<<togaf>>ProductPhysical Service modelBlue Association: Transcends Business / ITBordersupported byhas particluar importance forconstrains / directsbased on1..*deployed ondeployed on 0..*built up bydepends oninteracts viatravels across1 1..*provides and receives via an interface1 1..*depicted by1 1belongs to**supported by**performed bycontainscontainsconceptually depicted byrefined byconceptual associationsparticipates inownsorchestrates0..*producescomposed ofsupportscan supportcomposed of0..*produces & distributes containsparticipates inimplemented byserves/handlesinvolvesinvolvesis supported byexecuted by1..*composed ofofferssupportscalls0..*
  • The Premier Event for Software and Systems Innovation36 © 2011 IBM CorporationThe Metamodel in SA Publisher
  • The Premier Event for Software and Systems Innovation37 © 2011 IBM CorporationMessage Sequence Diagram<<internal>>ApplicationPOS IDPOS NameSubject Matter ExpertSystem OwnerMaintenance ResponsibleIT UnitLast Update<<internal>>Application Service<<internal>>MessagePhysical Service modelprovides and receives via an interface1 1..*offerscalls0..*App Service 2App Service 1Get Customer Details Message
  • The Premier Event for Software and Systems Innovation38 © 2011 IBM CorporationWorkspace StrategyBaseline v1ArchitectureDevelopmentv1.1ArchitectureDevelopmentv1.2ArchitectureDecided v1.1Projects AProject BProduction External DataSystemDevelopmentBaseline v2ArchitectureDevelopmentv2.1ProductionExternal DataSystemDevelopmentProject B(Decided v1.1)
  • The Premier Event for Software and Systems Innovation39 © 2011 IBM CorporationPractical Challenges & Advice The EA repository will never be the only source of documentation. The metamodelmust take this into account, by, for example, specifying where the documentation“master data” resides.o To have control, one must have a single metamodel that describes where all informationresides.o Strategies for synchronization with those repositories must be put in place. It is very difficult to guess what the corporate metamodel should be. It is better toestablish a skeleton and then work with real projects. Both, top-down and bottom-up approaches should be used when populating therepository. EA must acquire a critical mass before clear benefits can be observed, firstprojects may not see all benefits Must have a strategy for keeping content up to date Avoid the tool-secretary trap! Instead create a framework where project membersare trained and supported to use the tool themselves.
  • The Premier Event for Software and Systems Innovation40 © 2011 IBM CorporationSummary & Next Steps Short background on DnB NOR DnB NOR’s expectations for Enterprise Architecture Practical Challenges & Advice Next StepsSA XT: Highly customized lightweight interface allowing passive users to update therepository.IBM Cognos Business Intelligence: Audit ReportsFramework Metamodel Tool EA trinity
  • The Premier Event for Software and Systems Innovation41 © 2011 IBM Corporationwww.ibm/software/rational
  • The Premier Event for Software and Systems Innovation42 © 2011 IBM Corporation© Copyright IBM Corporation 2011. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty ofany kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to,nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governingthe use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product releasedates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitmentto future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of theInternational Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.www.ibm/software/rational
  • The Premier Event for Software and Systems Innovation43 © 2011 IBM CorporationContact InformationLars JørgensenEnterprise Architect at DnB NORlars.jorgensen@dnbnor.no+47 9525 7514James DzidekIndependent Consultant, Enterprise Architecturejames.dz@gmail.com+47 4889 4576
  • The Premier Event for Software and Systems Innovation44 © 2011 IBM CorporationDaily iPod Touch giveaway Complete your session surveys online each dayat a conference kiosk or on your Innovate 2011 Portal! Each day that you complete all of that day’s sessionsurveys, your name will be entered to win the dailyIPOD touch! On Wednesday be sure to complete your full conference evaluationto receive your free conference t-shirt!SPONSORED BY
  • The Premier Event for Software and Systems Innovation45 © 2011 IBM Corporationwww.ibm/software/rational
  • The Premier Event for Software and Systems Innovation46 © 2011 IBM Corporationwww.ibm/software/rational