Architecture英文课件

Architecture,ArnonRotem-Gal-OzProductLineArchitectarnon,Agenda,WhySoftwareArchitecture?WhatsSoftwareArchitecture?Architecturetypes?Levels?IntroductiontoArchitectureDocumentation,Discussion,WhatsSoftwareArchitecture,CanbebuiltbyonepersonRequiresMinimalmodelingSimpleprocessSimpletools,Architectingadoghouse,Kruchten,Architectingahouse,BuiltmostefficientlyandtimelybyateamRequiresModelingWell-definedprocessPowertools,Kruchten,Architectingahighrise,Kruchten,Differences,ScaleProcessCostScheduleSkillsanddevelopmentteamsMaterialsandtechnologiesStakeholdersRisks,Agenda,WhySoftwareArchitecture?WhatsSoftwareArchitecture?Architecturetypes?Levels?IntroductiontoArchitectureDocumentation,Architecturedefined,Softwarearchitectureiswhatsoftwarearchitectsdo,Beck,ArchitecturedefinedFormalDefinition,IEEE1471-2000Softwarearchitectureisthefundamentalorganizationofasystem,embodiedinitscomponents,theirrelationshipstoeachotherandtheenvironment,andtheprinciplesgoverningitsdesignandevolution,IEEE1471-2000,SoftwarearchitectureencompassesthesetofsignificantdecisionsabouttheorganizationofasoftwaresystemSelectionofthestructuralelementsandtheirinterfacesbywhichasystemiscomposedBehaviorasspecifiedincollaborationsamongthoseelementsCompositionofthesestructuralandbehavioralelementsintolargersubsystemsArchitecturalstylethatguidesthisorganization,Booch,Kruchten,Reitman,Bittner,andShaw,ArchitecturedefinedAnotherGo,PerryandWolf,1992Asetofarchitectural(ordesign)elementsthathaveaparticularformBoehmetal.,1995AsoftwaresystemarchitecturecomprisesAcollectionofsoftwareandsystemcomponents,connections,andconstraintsAcollectionofsystemstakeholdersneedstatementsArationalewhichdemonstratesthatthecomponents,connections,andconstraintsdefineasystemthat,ifimplemented,wouldsatisfythecollectionofsystemstakeholdersneedstatementsClementsetal.,1997Thesoftwarearchitectureofaprogramorcomputingsystemisthestructureorstructuresofthesystem,whichcomprisesoftwarecomponents,theexternallyvisiblepropertiesofthosecomponents,andtherelationshipsamongthem,/architecture/definitions.html,ArchitecturedefinedFewMore,Commonelements1/2,ArchitecturedefinesmajorcomponentsArchitecturedefinescomponentrelationships(structures)andinteractionsArchitectureomitscontentinformationaboutcomponentsthatdoesnotpertaintotheirinteractionsBehaviorofcomponentsisapartofarchitectureinsofarasitcanbediscernedfromthepointofviewofanothercomponent,Commonelements2/2,Everysystemhasanarchitecture(evenasystemcomposedofonecomponent)ArchitecturedefinestherationalebehindthecomponentsandthestructureArchitecturedefinitionsdonotdefinewhatacomponentisArchitectureisnotasinglestructure-nosinglestructureisthearchitecture,ArchitectureisEarly,ArchitecturerepresentsthesetofearliestdesigndecisionsHardesttochangeMostcriticaltogetrightArchitectureisthefirstdesignartifactwhereasystemsqualityattributesareaddressed,ArchitectureDrives,Architectureservesastheblueprintforthesystembutalsotheproject:TeamstructureDocumentationorganizationWorkbreakdownstructureScheduling,planning,budgetingUnittesting,integrationArchitectureestablishesthecommunicationandcoordinationmechanismsamongcomponents,Architecturevs.Design,non-functionalrequirements(“ilities”),functionalrequirements(domains),Important:thisisageneralguidelinesometimesthebordersareblurred,Architecture:wherenon-functionaldecisionsarecast,andfunctionalrequirementsarepartitionedDesign:wherefunctionalrequirementsareaccomplished,architecture,design,SystemQualityAttribute,PerformanceAvailabilityUsabilitySecurity,MaintainabilityPortabilityReusabilityTestability,EndUsersview,Developersview,TimeToMarketCostandBenefitsProjectedlifetimeTargetedMarketIntegrationwithLegacySystemRollbackSchedule,BusinessCommunityview,AlistofqualityattributesexistsinISO/IEC9126-2001InformationTechnologySoftwareProductQuality,Agenda,WhySoftwareArchitecture?WhatsSoftwareArchitecture?SoftwareArchitecturetypes?Levels?IntroductiontoArchitectureDocumentation,BusinessArchitecture,Concernedwiththebusinessmodelasitrelatestoanautomatedsolution.E-businessisagoodcandidateStructuralpartofrequirementsanalysis.DomainSpecific,TechnicalArchitecture,Specifictotechnologyandtheuseofthistechnologytostructurethetechnicalpoints(TechnologyMapping)ofanarchitecture.NETJ2EEHardwarearchitects,SolutionsArchitecture,Specifictoaparticularbusinessarea(orproject)butstillreliantonbeingatechnicalfocalpointforcommunicationsbetweenthedomainarchitect,businessinterestsanddevelopment.,EnterpriseArchitecture,TheorganizinglogicforafirmscorebusinessprocessesandITcapabilitiescapturedinasetofprinciples,policiesandtechnicalchoicestoachievethebusinessstandardizationandintegrationrequirementsofthefirmsoperatingmodel.Concernedwithcrossproject/solutionarchitectureandcommunicationbetweendifferentpracticesinarchitecture.,ProductLineArchitecture,CommonArchitectureforasetofproductsorsystemsdevelopedbyanorganization,ProductLine-Initiation,EvolutionaryProductlinearchitectureandcomponentsevolvewiththerequirementsposedbynewproductlinemembers.RevolutionaryProductlinearchitectureandcomponentsdevelopedtomatchrequirementsofallexpectedproduct-linemembers,Agenda,WhySoftwareArchitecture?WhatsSoftwareArchitecture?Architecturetypes?Levels?IntroductiontoArchitectureDocumentation,IEEE1471-Recap,RecommendedPracticeforArchitecturalDescriptionofArchitecturalDescriptionofSoftware-IntensiveSystemsDefinetheRelationsbetweenStakeholdersConcernsViewsViewpointModelsArchitecturalDescription,DocumentationConceptualModel,IEEE1471-2000,Stakeholdersserver.receive-requesttorpc.callee,ADL-Pros,ADLsrepresentaformalwayofrepresentingarchitectureADLsareintendedtobebothhumanandmachinereadableADLssupportdescribingasystematahigherlevelthanpreviouslypossibleADLspermitanalysisofarchitecturescompleteness,consistency,ambiguity,andperformanceADLscansupportautomaticgenerationofsimulations/softwaresystems,ADL-Cons,ThereisnotuniversalagreementonwhatADLsshouldrepresent,particularlyasregardsthebehaviorofthearchitectureRepresentationscurrentlyinusearerelativelydifficulttoparseandarenotsupportedbycommercialtoolsMostADLstendtobeveryverticallyoptimizedtowardaparticularkindofanalysisMostADLworktodayhasbeenundertakenwithacademicratherthancommercialgoalsinmind,UML2.0,13diagramtypes,UML,DSL,Services,Messages,Applications,Endpoints,XML,Projects,DBs,Classes,Code,LogicalDataCenter,Physicalservers&segments,DeploymentUnits,Abstraction/Refinement,Constraints,packagedinto,deployedon,BusinessProcessesan