使用UML分析与设计软件

Page1ΡAnalysisandDesignwithUMLCopyright?1997byRationalSoftwareCorporationPage2ΡAgenda„BenefitsofVisualModeling„HistoryoftheUML„VisualModelingwithUML„TheRationalIterativeDevelopmentProcessCopyright?1997byRationalSoftwareCorporationPage3ΡWhatisVisualModeling?ComputerSystemBusinessProcessOrderItemShipviaModelingcapturesessentialpartsofthesystem.Dr.JamesRumbaughVisualModelingismodelingusingstandardgraphicalnotationsCopyright?1997byRationalSoftwareCorporationPage4ΡVisualModelingCapturesBusinessProcessUseCaseAnalysisisatechniquetocapturebusinessprocessfromuser뭩perspectiveCopyright?1997byRationalSoftwareCorporationPage5ΡVisualModelingisaCommunicationToolUsevisualmodelingtocapturebusinessobjectsandlogicUsevisualmodelingtoanalyzeanddesignyourapplicationCopyright?1997byRationalSoftwareCorporationPage6ΡVisualModelingManagesComplexityCopyright?1997byRationalSoftwareCorporationPage7ΡVisualModelingDefinesSoftwareArchitectureUserInterface(VisualBasic,Java)BusinessLogic(C++,Java)DatabaseServer(C++&SQL)ModelyoursystemindependentofimplementationlanguageCopyright?1997byRationalSoftwareCorporationPage8ΡVisualModelingPromotesReuseMultipleSystemsReusableComponentsCopyright?1997byRationalSoftwareCorporationPage9ΡWhatistheUML?Copyright?1997byRationalSoftwareCorporation„UMLstandsforUnifiedModelingLanguage„TheUMLcombinesthebestofthebestfrom–DataModelingconcepts(EntityRelationshipDiagrams)–BusinessModeling(workflow)–ObjectModeling–ComponentModeling„TheUMListhestandardlanguageforvisualizing,specifying,constructing,anddocumentingtheartifactsofasoftware-intensivesystem„Itcanbeusedwithallprocesses,throughoutthedevelopmentlifecycle,andacrossdifferentimplementationtechnologiesPage10ΡHistoryoftheUMLNov?7UMLapprovedbytheOMGCopyright?1997byRationalSoftwareCorporationPage11ΡUMLSupportsApplicationDevelopmentRelationshipsObjectsBusinessObjectslargescalesystemORDBMSOracleClassesapplicationpartitioningComponentsMicrosoftScenariosCORBAOMGUseCasesActiveX/COMMicrosoftBusinessProcessCopyright?1997byRationalSoftwareCorporationPage12ΡUMLConcepts„TheUMLmaybeusedto:–Displaytheboundaryofasystem&itsmajorfunctionsusingusecasesandactors–Illustrateusecaserealizationswithinteractiondiagrams–Representastaticstructureofasystemusingclassdiagrams–Modelthebehaviorofobjectswithstatetransitiondiagrams–Revealthephysicalimplementationarchitecturewithcomponent&deploymentdiagrams–ExtendyourfunctionalitywithstereotypesCopyright?1997byRationalSoftwareCorporationPage13ΡPuttingtheUMLtoWork„TheESUUniversitywantstocomputerizetheirregistrationsystem–TheRegistrarsetsupthecurriculumforasemester•Onecoursemayhavemultiplecourseofferings–Studentsselect4primarycoursesand2alternatecourses–Onceastudentregistersforasemester,thebillingsystemisnotifiedsothestudentmaybebilledforthesemester–Studentsmayusethesystemtoadd/dropcoursesforaperiodoftimeafterregistration–Professorsusethesystemtoreceivetheircourseofferingrosters–UsersoftheregistrationsystemareassignedpasswordswhichareusedatlogonvalidationCopyright?1997byRationalSoftwareCorporationPage14ΡActors„AnactorissomeoneorsomethingthatmustinteractwiththesystemunderdevelopmentRegistrarProfessorStudentBillingSystemCopyright?1997byRationalSoftwareCorporationPage15ΡUseCases„Ausecaseisapatternofbehaviorthesystemexhibits–Eachusecaseisasequenceofrelatedtransactionsperformedbyanactorandthesysteminadialogue„Actorsareexaminedtodeterminetheirneeds–Registrar--maintainthecurriculum–Professor--requestroster–Student--maintainschedule–BillingSystem--receivebillinginformationfromregistrationMaintainScheduleMaintainCurriculumRequestCourseRosterCopyright?1997byRationalSoftwareCorporationPage16ΡDocumentingUseCases„Aflowofeventsdocumentiscreatedforeachusecases–Writtenfromanactorpointofview„Detailswhatthesystemmustprovidetotheactorwhentheusecasesisexecuted„Typicalcontents–Howtheusecasestartsandends–Normalflowofevents–Alternateflowofevents–ExceptionalflowofeventsCopyright?1997byRationalSoftwareCorporationPage17ΡMaintainCurriculumFlowofEvents„ThisusecasebeginswhentheRegistrarlogsontotheRegistrationSystemandentershis/herpassword.Thesystemverifiesthatthepasswordisvalid(E-1)andpromptstheRegistrartoselectthecurrentsemesterorafuturesemester(E-2).TheRegistrarentersthedesiredsemester.Thesystempromptstheprofessortoselectthedesiredactivity:ADD,DELETE,REVIEW,orQUIT.„IftheactivityselectedisADD,theS-1:AddaCoursesubflowisperformed.„IftheactivityselectedisDELETE,theS-2:DeleteaCoursesubflowisperformed.„IftheactivityselectedisREVIEW,theS-3:ReviewCurriculumsubflowisperformed.„IftheactivityselectedisQUIT,theusecaseends.„...Copyright?1997byRationalSoftwareCorporationPage18ΡUseCaseDiagram„UsecasediagramsarecreatedtovisualizetherelationshipsbetweenactorsandusecasesStudentRegistrarProfessorMaintainScheduleMaintainCurriculumRequestCourseRosterBillingSystemCopyright?1997byRationalSoftwareCorporationPage19ΡUsesandExtendsUseCaseRelationships„Astheusecasesaredocumented,otherusecaserelationshipsmaybediscovered–Ausesrelationshipshowsbehaviorthatiscommontooneormoreusecases–Anextendsrelationshipshow