Distributed Object Computing and UMLObjectiveSystem Use Case DescriptionBehavioral Modeling System Use CaseDeployment Diagram DescriptionArchitectural Modeling Deployment DiagramStructural Modeling Logical and Component ViewsInitial Logical View of ClientInitial Local Server Simulator and Client Comp ModelInitial Logical View of the Server SimulatorBehavioral Modeling Sequence Diagram of Log InBehavioral Modeling Sequence Diagram of Log OutFinal Application Models and DeploymentFinal Development Applet and ConnectionFinal Development Main Client ApplicationRMI StructureRMI Flow of EventsServer - GoalsServer - Transaction ObjectsServer - Transaction InterfacesServer at Runtime - LoginServer - Login MethodServer - DatabaseServer - HierarchyServer - The Big PictureApplication FunctionalityServer Application HierarchySample CodeSlide 29Slide 30Slide 31Slide 32Distribution Issues Relating to OOMUML Support For DOCSoftmodeler - A Next Generation UML Modeling ToolFeatures Supporting DOCComponent Design and DistributionComponent NotationComponent Diagram - An Extension to the UML NotationClass Diagram - An Enhancement to UMLSoftModeler vs. Rational RoseComponent CreationObjecTime Developer™ObjecTime Developer™ - FeaturesSlide 45UML-RT componentsSlide 47Research Of UML Tools -Paradigm PlusParadigm Plus - Business Process ModelParadigm Plus - Physical Database ModelingParadigm Plus - Component Based DevelopmentParadigm Plus And Uml - Class DiagramParadigm Plus And Uml - Use Case, State, and Object DiagramsParadigm Plus And Uml - Sequence And Component DiagramParadigm Plus And Uml - Phys Database And Collaboration DiagramParadigm Plus And Uml - Project And Deployment DiagramsParadigm Plus Enhancements To UML for DocTogether®Together® - FeaturesTogether - ScreenshotCSE333DOC/UML.1Distributed Object Computing and UMLResearch and Work By:Hector N. EchegoyenOliver Scheck Gowri [email protected]@[email protected]/UML.2ObjectiveObjectiveExplore UML Modeling Techniques/Constructs Explore UML Modeling Techniques/Constructs and Identify Support to DOCand Identify Support to DOCEmploy Rational ROSE to Model and Develop a Employ Rational ROSE to Model and Develop a Distributed Banking Application (using RMI)Distributed Banking Application (using RMI)Identify Key Distribution Issues Relating to OOMIdentify Key Distribution Issues Relating to OOMExplore a Select Set of UML Modeling Tools to Explore a Select Set of UML Modeling Tools to Identify DOC SupportIdentify DOC SupportCSE333DOC/UML.3System Use Case System Use Case DescriptionDescriptionHard Concept to Grasp InitiallyHard Concept to Grasp InitiallyAlmost Self-Explanatory - Focus on Functionality Almost Self-Explanatory - Focus on Functionality of System With Interaction of Actorsof System With Interaction of ActorsIdentified Four Major ActorsIdentified Four Major ActorsMajor Functionality and Relations to Actors Also IdentifiedDrew Clear Definitions of Operations for Each ActorHelped to Identify the Need for Some Sort of Role Based Security (I.e., Customer Actor Doesn’t Perform Audits)Actors Directly Linked to Roles?Wrote Case Scenarios of Major FunctionsWrote Case Scenarios of Major FunctionsCSE333DOC/UML.4Behavioral Modeling Behavioral Modeling System Use CaseSystem Use CaseProcess TransactionsDistributed CommunicationPersistent StorageReport GenerationPrintingAuditingClerkBANKING SYSTEMThe CustomerManager<<uses>><<uses>><<uses>><<uses>><<uses>>THE CLERKTHE CUSTOMERTHE MANAGERTheServerTHE SERVERCSE333DOC/UML.5Deployment Diagram Deployment Diagram DescriptionDescriptionTo Get an Idea of How the System Would Be To Get an Idea of How the System Would Be DistributedDistributedConcept of More Than One Type of Bank ServerConcept of More Than One Type of Bank ServerQuestions: Questions: What Kind of Functionality is Distributed Where? Where is Security, Servers or Clients, Both?Where Should We Deploy Objects, and Which Where Should We Deploy Objects, and Which Object?Object?Servers Handling Multiple Clients And/or Server Servers Handling Multiple Clients And/or Server Transactions at the Same TimeTransactions at the Same TimeAttempt to Make Our System Generic So That We Attempt to Make Our System Generic So That We Can Run All Possible ScenariosCan Run All Possible ScenariosCSE333DOC/UML.6Architectural Modeling Architectural Modeling Deployment DiagramDeployment DiagramBranch ServerTerminal1Terminal 2Terminal XBranch ServerTerminal 1Terminal 2Terminal XCentral BankATM 1ATM 2ATM XHubCSE333DOC/UML.7Structural Modeling Structural Modeling Logical and Component ViewsLogical and Component ViewsClientServerGuiUTheServerUClientServerGuiUTheServerUCLASS CLASS DIAGRAMDIAGRAMCOMPONENT COMPONENT DIAGRAMDIAGRAMCSE333DOC/UML.8Initial Logical View of ClientInitial Logical View of ClientThis is Where The Applet GUI Goes. To be Added To The Model Later.RMI HereCustomerProfileForm(from TheServer)Serializable(from io)<<Interface>>CustomerAccountForm(from TheServer)Vector(from util)TransactionInterface<<Interface>>TellerInterface<<Interface>>BankConnection1+BankTransaction11+TellerTransaction1CSE333DOC/UML.9Initial Local Server Simulator and Client Initial Local Server Simulator and Client Comp ModelComp ModelFunnyMoneySerializableSerializableTransactionInterfaceTransactionInterfacermiBankConnectionRemoteBankServerserverutilSessionInterfaceSessionInterfaceTransactionByRoleAtmTransTellerTransMgrTransTellerInterfaceTellerInterfaceCSE333DOC/UML.10Initial Logical View of the Server Initial Logical View of the Server SimulatorSimulatorFunnyMoneyamount : intSerializable(from io)<<Interface>>Remote(from rmi)<<Interface>>This is Where The Applet GUI Goes. To be Added To The Model Later.RMI HereTransactionInterface<<Interface>>UnicastRemoteObject(from server)SessionInterface<<Interface>>Hashtable(from util)AccountAccount()SessionHandlerTransactionByRole$ GOOD_CONN : int = 0RemoteBankServeraccounts1+TheAccount11+TheSessionHandler1+TheTransactionHandlerAtmTransTellerTransMgrTransTellerInterface<<Interface>>CustomerProfileForm(from TheServer)CustomerAccountForm(from TheServer)CSE333DOC/UML.11Behavioral Modeling Behavioral Modeling Sequence Diagram of Log InSequence Diagram of Log InClient 1 ServerEnter UName And PasswdSend UName And PasswdVerify UName And PasswdSend Connection StatusPrompt User For Transaction InfoAllocate Memory And Resources For
View Full Document
Unlocking...