Modeling技術(shù)與程式實(shí)作

UMLModeling技術(shù)與程式實(shí)作Microsoft.NET技術(shù)代言人林耀珍Michael第三波資訊技術(shù)總監(jiān)2023/1/111林耀珍經(jīng)歷第三波資訊技術(shù)總監(jiān)育碁數(shù)位科技總經(jīng)理專業(yè)認(rèn)證與專長微軟.NET技術(shù)軟體開發(fā)流程，資訊系統(tǒng)規(guī)劃MicrosoftMCSD/MCSE/MCDBA物件導(dǎo)向技術(shù)，RationalOOAD認(rèn)證講師LotusNotesprincipleCLP/CLIJ2EE2目標(biāo)與對象對象技術(shù)平臺的決策人員軟體建構(gòu)師系統(tǒng)分析師專案經(jīng)理想要了解UMLModeling的軟體開發(fā)人員

目標(biāo)了解UMLModeling的流程與技術(shù)3Agenda時間主題主講人1:30–2:50UML與ModelingTechnology林耀珍2:50–3:10中場休息3:10–4:30運(yùn)用BorlandTogetherFor.NET進(jìn)行Modeling與程式實(shí)作Borland資深顧問4UML與ModelingTechnology大綱

BestPracticesUML介紹UMLDiagramsandExtensionsDesignpattern5BestPracticesFromIBMRational-RUPDevelopIterativelyManageRequirementsUseComponentArchitecturesModelVisually(UML)ContinuouslyVerifyQualityManageChange

ComponentarchitecturesisevolvedintoServiceOrientedarchitecture.6為什麼需要ModelingSimplevs.ComplexOnemanvs.TeamworkNon-Criticalvs.CriticalVS.7Model&Blueprint模型與藍(lán)圖是所有參與者的溝通根據(jù)BusinessModelRequirementModelAnalysisModel–PlatformIndependentModelDesignModel–Blueprintforimplementation8ALongTimeAgo…??&?LucasfilmLtd.9Ifyouonlyknew

thepowerofthedarkside.??&?LucasfilmLtd.10PreparationandRecommendationMindsetNotreligion,butrigorousIncrementaladoptionTrainingLearning&TrainingApprenticeshipMentorsToolsarerequiredAgileProcessStartSmall??&?LucasfilmLtd.11TheProcessBusinessModelRequirementModelUserExperienceModellook-Feel&InteractionAnalysisModelDesignModelArchitecturedesignDataModelImplementationModelTestModelDeploymentModelFromIBMRational-RUPRequirementanalysisSystemanalysisSystemDesignImplementationTestingDeployment12UML:UnifiedModelingLanguageTheUMListhestandardlanguageforvisualizingspecifying,constructing,anddocumentingtheartifactsofasoftware-intensivesystemFromIBMRational-RUP13UML發(fā)展過程14TheValueoftheUMLIsastandardSupportstheentiresoftwaredevelopmentlifecycleSupportsdiverseapplicationsareasIsbasedonexperienceandneedsoftheusercommunitySupportedbymanytools15Model,View,DiagramModelcontainsviewsfordifferentpurposes.Viewcontainsmultiplediagrams.ProcessViewDeploymentViewLogical

ViewImplementationViewProgrammers

Softwaremanagement

PerformanceScalabilityThroughput

SystemIntegratorsSystemtopology

Delivery,installationcommunicationSystemEngineeringUse-CaseViewStructure

Analysts/

DesignersEnd-userFunctionality16UML12DiagramsBehavior:UseCaseActivitySequenceCollaborationStateChartStructural:ClassComponentDeploymentObjectModelManagement:Packages(classdiagramcontainspackages)Subsystems(classdiagramcontainssubsystems)Models(classdiagramcontainsmodels)17ModelDiagram使用ModelDiagram描述所要執(zhí)行的Modeling工作18Use-CaseDiagramActors需求模型：Use-CaseModelUsecasemodel描述系統(tǒng)功能，是與客戶溝通的工具UseCases:系統(tǒng)行為或功能Actors:系統(tǒng)的各種使用者UseCasesDiagramsUse-CaseReportsorUse-CaseSpecificationsActors19網(wǎng)路購物系統(tǒng)的需求模型Usecases:BrowsecatalogSearchproductsMaintainshoppingcartLogonMaintainaccountCheckoutorderActorsUserCustomer201.Name:BrowseProductCatalog2.FlowofEvents2.1Basicflow:顯示所有的次類別及促銷產(chǎn)品使用者開啓首頁系統(tǒng)顯示所有的次類別,與當(dāng)時的促銷產(chǎn)品使用者選取次類別系統(tǒng)顯示該類別的全部產(chǎn)品簡介使用者選擇產(chǎn)品系統(tǒng)顯示該產(chǎn)品的資訊UsecasereportThisisrequirementmodelversion.21Activitydiagram描述Businessprocess或usecase的操作流程22BusinessModelingFindClientsFindEmployees

Deliver

ServiceCollectReceivablesDisbursePayablesEstablishMarketsReportFinancialsPayDividends23UserExperienceModelUIPrototypeNavigateflow:useUIclasswithscreenstereotype241.Name:BrowseProductCatalog2.FlowofEvents2.1Basicflow:顯示所有的次類別及促銷產(chǎn)品使用者開啓首頁系統(tǒng)在畫面的右側(cè)顯示所有的次類別系統(tǒng)在畫面的上方顯示pickoftoday的促銷產(chǎn)品簡介使用者選取次類別系統(tǒng)在畫面的內(nèi)容區(qū)顯示該類別的全部產(chǎn)品簡介使用者選擇產(chǎn)品系統(tǒng)在畫面的內(nèi)容區(qū)顯示該產(chǎn)品的資訊，並顯示AddToCart按鈕MoreDetailedUseCaseThisisUserExperienceModelversion,Optional.25AnalysismodelPlatformIndependentModel找出完成usecases所需要的類別Analysisclasses規(guī)劃Classes的relationship指派use-casebehaviors給適當(dāng)?shù)念悇e找出Operations找出每個class的attributes26AnalysisClassesClassname,operations,attributes27ClassdiagramFindRelationships,becareofbeingtoocomplex28ArchitecturedesignArchitecturedesign處理較高層次的設(shè)計元件，包括package,Subsystem,Interface。使用Package組織設(shè)計元件。Subsystem包含多個classes,透過Interfaces展現(xiàn)功能。29PackagediagramPackagediagramisaclassdiagramwhichcontainspackages.CommonglobalIntegration<<layer>>Presentation<<layer>>BusinessServices<<layer>>30SubsystemdiagramSubsystem可以realize兩個以上的介面一個介面可以被二個以上的子系統(tǒng)realizeInterfaceZX()Y()<<Interface>>SubsystemA<<subsystem>>SubsystemB<<subsystem>>ClassA1A()B()ClassA2X()Y()ClassB1W()Y()ClassB2X()ClassB3Z()InterfaceAA()B()<<Interface>>31UseCaseDesignWalkthruflowofeventsinusecasebysequencediagram32SequenceDiagrams1:PerformResponsibility

ClientObjectSupplierObjectMessage:Client:SupplierFocusofControlThisisasamplescript.ReflexiveMessageLifeline1.1:PerformAnother

Responsibility HierarchicalMessageNumberingXDestroyobjectAsequencediagramdisplaysobjectinteractionsarrangedinatimesequence33CollaborationDiagramAcollaborationdiagramdisplaysobjectinteractionsorganizedaroundobjectsandtheirlinkstooneanother34CollaborationDiagrams與SequenceDiagrams的比較CollaborationDiagramsSequenceDiagramsShowrelationshipsinadditiontointeractionsShowtheexplicitsequenceofmessagesBetterforvisualizingpatternsofcollaborationBetterforvisualizingoverallflowBetterforvisualizingalloftheeffectsonagivenobjectBetterforreal-timespecificationsandforcomplexscenariosEasiertouseforbrainstormingsessions35ImplementationModelandComponentDiagramForsmallsystem,weuseBusinessfa?adecomponent,Businessrulecomponent,andDataaccesscomponent.36元件設(shè)計與VS.NET專案規(guī)劃37DeploymentDiagramApplicationserverSQLServerClientBrowserClientMailServerServerSMTPServerLANLANLANWANWAN38WhatwelearnaboutUMLDiagrams?Behavior:UseCaseActivitySequenceCollaborationStateChartStructural:ClassComponentDeploymentObjectModelManagement:Packages(classdiagramcontainspackages)Subsystems(classdiagramcontainssubsystems)Models(classdiagramcontainsmodels)39擴(kuò)充UML的描述能力StereotypeNoteTagStereotypecanbeusedonlinksandclasses,intext/iconformats.40DesignPatternApatternisasolutiontoaprobleminacontext,itdocumentsinanabstractandcompactformtheproblemthecontextinwhichitoccursagoodsolutionanditembodieswisdomabouthowthesolutionaddressestheproblem.Differentlevelsbasicbuildingblocksdesignpatternsarchitecturepatterns41Fa?adeDesignPatternFa?ade:definesaclean,high-levelinterfacetoasubsystem.Context:buildingeasy-to-useandmaintainsubsystemsProblem:Eachclassinthesubsystemprovidespartofthesubsystem’sfunctionality,clientshastoknowtheinside,changestothesubsystemmayrequirechangestotheclients.Solution:Addaninterfaceclass(thefa?adeclass)thatknowsthestructureofthesubsystemandforwardsrequests…Consequences:noorlessdependencyofclientfromstructureofsubsystem,idealforlayeredsubsystemsFacade42總結(jié)LearnUMLFollowaprocessTryamodelingtoolsFindsupportsTime,Budget,MentoringMayForceWithYou!!43Agenda時間主題主講人1:30–2:50UML與ModelingTechnology林耀珍2:50–3:10中場休息3:10–4:30運(yùn)用BorlandTogetherFor.NET進(jìn)行Modeling與程式實(shí)作Borland資深顧問44WhatisModelDrivenArchitecture?ANewWaytoSpecifyandBuildSystems2001年由OMG制定的新開發(fā)架構(gòu)以UML塑模為基礎(chǔ)支援完整開發(fā)週期:analysis,design,implementation,deployment,maintenance,evolution&integrationwithlatersystems內(nèi)建協(xié)同運(yùn)作性及跨平臺性降低開發(fā)初期成本及提高ROI可套用至你所使用的任何環(huán)境:Programminglanguage NetworkOperatingsystem Middleware45ModelDrivenArchitecturePlatform-

IndependentModel(PIM)Platform-SpecificModel(PSM)MDAtoolappliesanstandardmappingtogeneratePlatform-SpecificModel(PSM)fromthePIM.Codeispartiallyautomatic,partiallyhand-written.46開發(fā)流程AnalysisModelDesignModelArchitecturedesignDataModelUserExperienceModellook-Feel&InteractionImplementationModelPlatform-

IndependentModel(PIM)Platform-SpecificModel(PSM)47UseCaseModel48架構(gòu)設(shè)計49系統(tǒng)設(shè)計50BusinessLogicnamespaceBusinessLogic{publicclassTriangle:Shape{ publicoverridedoubleCalculateArea(){ this.Area=this.m_Base*this.m_Height/2; return(this.Area);}privatedoublem_Height;privatedoublem_Base; publicdoubleHeight{get{return(m_Height);}set{m_Height=value;}51PresentationLayertheRectangle.Base=RectB;theRectangle.Height=RectH; theTriangle.Base=TriB;theTr