WIXLIB

Development and maintenance ofcomplex software systemsFrom enterprise architectures todevelopment and maintenance28. jan. 20211ITLED 4340

ArchitecturenArchitecture is a term that lots of people try to definennArchitecture providesnnnnthere is not just one way to state a system’s architecturemanaging complexitylayers of abstractionseparation of concernsArchitecture coversnnnbreakdown of a system into its partsthe relationship between the parts (static and dynamic)decisions about the design of a system that are hard to change18. feb. 20212ITLED 4340

ArchitectureHoidn & Schwidder explain thatan architecture can be seen as:a subjective mapping from one of many possible humanperspectives to the elements or components of some kind ofstructure or system, which preserves the relationships among the elementsor -5459-4cd7-a7ce-42408641d554/Day02 Pres UniZH HS2016 StandardsKeyWorkProducts.pptx.pdf]18. feb. 20213ITLED 4340

Zachman FrameworknZachman Frameworknnhttps://www.zachman.comontology and meta-model for business architecturennnnot a methodologyno specific tools or processesno structuring of stepsnassigns roles and promotes to think within one’s rolenontological structurennnreflect about the intersection between two classificationsWhat, How, When, Who, Where, Whynprovide concise, targeted descriptions of complex ideasIdentification, Definition, Representation, Specification, Configuration, Instantiationntransform an abstract idea into an instantiation18. feb. 20214ITLED 4340

Zachman s antiationsOperationInstances18. feb. ngMotivationRepresentation Representation Representation Representation Representation Representation5SystemLogicITLED 4340

OMG’s Model Driven Architecturennnnnderive value from models and architecture in supportof the full life cycle of physical, organizational and ITsystemsrepresent and support everything from requirementsto business modeling to implementationdefine the structure, semantics, and notations ofmodels using industry standardsuseful for the production of documentation, acquisition specifications,system specifications, technology artifacts and executable systemscapabilitiesnnnnnrepresent and exchange models in a variety of modeling languagestransform modelproduce documentationexecute modelsrepresent systems at any level of abstractionnranging from enterprise architectures to technology implementations18. feb. 20216ITLED 4340

TOGAFThe Open Group Architecture Framework (TOGAF)PARTSI - introductionII - step-by-step approach todevelop an enterprisearchitectureIII - collection of guidelines andtechniquesIV - content framework including ametamodel for architecturalartifactsV - taxonomies and toolsVI - selection of architecturalreference modelsVII - organization, processes, skills,roles, and responsibilities18. feb. 20217ITLED 4340

Architecture FrameworksnZachman FrameworknnnOMG MDAnnnnis an ontology and a meta-modelis not a methodologyintegrates the OMG standards: MOF, UML, BPMN, .specify and build systems – by OMG standard integrationfull lifecycle: A&D, implementation, deployment, maintenance, andevolutionTOGAFnnnis an architecture development method (ADM)provides a model for structuring a repository of architectural assetsprovides concrete resources18. feb. 20218ITLED 4340

Architecture development cycleTOGAFPreliminaryniterative eVisionfor each ArchitecturesnFMigrationPlanningEOpportunitiesand SolutionsDTechnologyArchitecturen18. feb. 20219breadth of coveragelevel of detailtime allowedassets to be leveragednincluding reusenincluding externalframeworks andmodelsbase decisions onnnbetween and within phasesavailable resources andcompetencyexpected valuetailor model to your needsITLED 4340

Architecture development ntsManagementnote the cyclic nature of ofthis enterprise modelmain msArchitecturesnfurther assumptionsnnFMigrationPlanning18. feb. 2021EOpportunitiesand SolutionsnDTechnologyArchitecturen10there is an existing system withsystem valuea transition to something new isrequiredstakeholders must be involvedand kept in the looptransitions can faildesigns are rarely perfect in thefirst attempttechnologies will change fasterthan requires capabilitiesITLED 4340

Preliminary ementEOpportunitiesand logyArchitecturen18. feb. 202111review organizational contextidentify stakeholder todetermine their requirementsand prioritiesensure commitmentidentify affected elements ofthe organizationidentify actors to performarchitecture workdefine framework andmethodologiesselect infrastructure tosupport the architectureactivitydefine architecture principlesITLED 4340

Phase A: Architecture ystemsArchitecturesnnFMigrationPlanning18. feb. 2021EOpportunitiesand SolutionsDTechnologyArchitecture12ensure endorsement frommanagementdefine and organize thedevelopment cycleidentify and prioritize thecomponents of thearchitecturearticulate an architecturevision and formalize thevalue propositioncreate a comprehensive planunderstand the impact onother ongoing developmentITLED 4340

Phase B: Business architecturenPreliminaryndescribe the baselinearchitecturedevelop a target overnanceFMigrationPlanning18. feb. 2021RequirementsManagementEOpportunitiesand SolutionsCInformationSystemsArchitecturesndescribe the product strategydescribe the organizational,functional, process, information,and geographic aspects of thebusiness environmentanalyze the gaps betweenthe baseline and targetselect and develop relevantarchitectureDTechnologyArchitecture13ITLED 4340

Phase B: Business architectureMain tationGovernanceFMigrationPlanning18. feb. 2021RequirementsManagementEOpportunitiesand Solutionsrefined architecture visiondraft architecture definitiondocumentdraft architecturerequirements specificationbusiness uresDTechnologyArchitecture14ITLED 4340

Phase B: Business architectureDraft architecturerequirements specificationnnnnnnnnnnTypes of requirementssuccess measuresarchitecture requirementsbusiness service contractsapplication service contractsimplementation on standardsinteroperability requirementsconstraintsassumptions18. feb. 2021nnnnnnnnn15functional requirementsnon-functional requirementsassumptionsconstraintsdomain-specific businessarchitecture sITLED 4340

Phase C: Information Systems ArchitecturesnPreliminarydevelop target nGovernanceFMigrationPlanning18. feb. 2021RequirementsManagementEOpportunitiesand SolutionsCInformationSystemsArchitecturesdata domainapplication systems domainidentify and define theapplications and dataconsiderationsdefine views that relate toinformation, knowledge,application services, etc.DTechnologyArchitecture16ITLED 4340

Phase C: Information Systems Architecturesdata ionSystemsArchitecturesnFMigrationPlanning18. feb. 2021EOpportunitiesand Solutionsdefine the major types andsources of datanunderstandable bystakeholdersncomplete and consistentnstablerestrict the definition torelevant data entities, avoidactual logical or physicalstorage systemsdemonstrate limitationsDTechnologyArchitecture17ITLED 4340

Phase C: Information Systems Architecturesapplication lementationGovernanceFMigrationPlanning18. feb. 2021RequirementsManagementEOpportunitiesand ogyArchitecture18define major applicationdefine kinds of applicationnto manage to datanto interact with humanand computer actorsdescribe as capabilitiesapplications described in thisway are stable over timeavoid specific technologiesntechnologies will changeover timencapabilities to achievegoals will remainITLED 4340

Phase C: Information Systems ArchitecturesMain itiesand SolutionsDTechnologyArchitecturenn18. feb. 202119statement of architectureworkbaseline data architecturetarget data architecturebaseline applicationarchitecturetarget applicationarchitecturedata architecture viewsapplication architectureviewsdraft architecture definitiondraft technical requirementspecificationITLED 4340

Phase C: Information Systems ArchitecturesRequirements in dataarchitectureRequirements inapplication architecturefunctional requirementsnon-functional requirementsassumptionsconstraintsdomain-specific datadomain-specific applicationarchitecture principlesarchitecture s18. feb. 202120ITLED 4340

Phase D: Technology ionSystemsArchitecturesnnFMigrationPlanning18. feb. 2021EOpportunitiesand SolutionsDTechnologyArchitecturenn21map application componentsinto a set of technologycomponentsnplatformsnsoftware and hardwarecomponentsbe aware of link toimplementation (G) andmigration (F)define baseline and targetviewsdefine the roadmapidentify key work packagessupports cost assessmentITLED 4340

Phase D: Technology ArchitectureMain ImplementationGovernanceFMigrationPlanning18. feb. rtunitiesand rchitecturesDTechnologyArchitecturen22refined and updated versionsof the architecture visiondraft architecture definitionntechnology componentsntechnology platformsnenvironments andlocationsnexpected workloadsnnetwork communicationsnhardware and networkspecificationsdraft architecturerequirementsITLED 4340

Phase D: Technology ArchitectureSteps in developing atechnology architecturennnnnnReview selectedtechnology’s impactdefine a taxonomy ofservices and componentsidentify locationscreate inventory of existingtechnologycheck whether technologysolves functional and nonfunctional requirementsdetermine configurationdetermine impactnnnnnnnperformancemaintainabilitylocation and latencyavailabilityReview requirementsnidentical to Phase Ccostcapacityimplementation, governance,migration impacts18. feb. 202123ITLED 4340

Phase E: Opportunities & onSystemsArchitecturesnFMigrationPlanning18. feb. 2021EOpportunitiesand SolutionsDTechnologyArchitecture24review target objectives andcapabilitiesconsolidate gaps fromphases B to Dorganize groups of buildingblocks to address capabilitiesderive transitionarchitectures that work forbusiness while moving frombaseline to targetgenerate an outlineimplementation andmigration strategyITLED 4340

Phase E: Opportunities & SolutionsMain tationGovernanceFMigrationPlanning18. feb. 2021RequirementsManagementEOpportunitiesand SolutionsnCInformationSystemsArchitecturesrefined and updated versionsarchitectureconsolidated architectureroadmapcapability assessmenttransition architectureimplementation andmigration planDTechnologyArchitecture25ITLED 4340

Phase F: Migration tationGovernanceFMigrationPlanning18. feb. 2021RequirementsManagementEOpportunitiesand SolutionsCInformationSystemsArchitecturesnensure co-ordination withmanagementprioritize work packages,projects and building blocksnbased on their businessvaluefinalize architecture visionand definitioncreate, evolve, and monitorthe detailed implementationand migration planDTechnologyArchitecture26ITLED 4340

Phase F: Migration PlanningMain outputsnPreliminarynimplementation andmigration ntEOpportunitiesand logyArchitecturenn18. feb. 202127architecture definition documentarchitecture requirementsspecificationarchitecture roadmaptransition architecturere-usable architecturebuilding blocksrequests for architectureworkarchitecture contractsimplementation governancemodelchange requestsITLED 4340

Phase G: Implementation ionSystemsArchitecturesnnFMigrationPlanning18. feb. 2021EOpportunitiesand SolutionsDTechnologyArchitecture28formulate recommendationsfor implementationgovern and manageimplementation anddeployment processensure successfuldeploymentensure conformance withother projectsensure conformance withtarget architecturemobilize supportingoperationsITLED 4340

Phase G: Implementation GovernanceMain ure contractcompliance assessmentschange requestssolutions ionPlanning18. feb. 2021EOpportunitiesand SolutionsDTechnologyArchitecturenn29implemented systemarchitecture repositorycompliance recommendationsand dispensationsservice delivery requirementsperformance metricsService Level Agreements(SLAs)updated documentsoperating modelsITLED 4340