Rational Software Modeler TutorialOutlineRSM EnvironmentActivity DiagramComponentsStepsUse-Case DiagramSlide 8Slide 9Class DiagramSlide 11Slide 12Sequence DiagramSlide 14ArchivingSlide 16Questions?University of Southern CaliforniaCenter for Systems and Software EngineeringRational Software ModelerTutorialPongtip AroonvatanapornUniversity of Southern CaliforniaCenter for Systems and Software EngineeringOutline•Setting up RSM environment•Activity Diagram•Use-case Diagram•Class Diagram•Sequence Diagram•ArchivingUniversity of Southern CaliforniaCenter for Systems and Software EngineeringRSM Environment•Built on Eclipse environment–Workspace–Modeling perspective•Comes with Eclipse 3.2•Or installed as Eclipse plug-in–Note: on Windows 7, use your own version of Eclipse and JDK/JRE–Download Eclipse 3.2.2 and latest JDK/JRE–Choose “Extend Eclipse”University of Southern CaliforniaCenter for Systems and Software EngineeringActivity Diagram•Captures a sequence of activities and actions•In CSCI577, used to model business workflow or business processUniversity of Southern CaliforniaCenter for Systems and Software EngineeringComponents•Partitions•Actions•Control node (i.e. decision node)•Control flow–Transfer of action•Object node (i.e. data)•Object flow–Transfer of objectUniversity of Southern CaliforniaCenter for Systems and Software EngineeringSteps•Create a new model called “Activity Model”•Right click on the model–Add Diagram Activity Diagram•On the right panel, select the following–Partition–Actions–Control node (decision node)–Control flowUniversity of Southern CaliforniaCenter for Systems and Software EngineeringUse-Case Diagram•Captures the interaction between actors and system•Shows the possible capabilities/functionalities the system can perform•Association –Roles and multiplicities do not applyUniversity of Southern CaliforniaCenter for Systems and Software EngineeringComponents•Actor–Show the hierarchy of users•Use-case–The actions that user can perform•Relationships–Association–Dependencies•“Includes”–invocation of a use case by another one•“Extends”–Ultimately an alternate course of action–Should avoid as it complicates the modelUniversity of Southern CaliforniaCenter for Systems and Software EngineeringSteps•Create “System Analysis” model•Right click on the model–Add Diagram Use-case Diagram•Add an actor•Add a few use-cases–Association from actor to use-case–“Include” relationship from 1 use-case to another –Right vs. wrong–User inheritance (super user)University of Southern CaliforniaCenter for Systems and Software EngineeringClass Diagram•Detailed designs of the classes •Contains–Attributes–Operations–Relations between classesUniversity of Southern CaliforniaCenter for Systems and Software EngineeringComponents•Classes–Boundary: pages, view–Controller: logic–Entity: model, data•Relationships–Association: “Has-a” –Aggregation: “Part-of”–Composition•Stronger aggregation•Lives and dies with parentUniversity of Southern CaliforniaCenter for Systems and Software EngineeringSteps•Create a new model called “Design Model”•Create a package called “Design Classes”•Add new classes:–<<boundary>> VolunteerPage–<<controller>> TimeController–<<entity>> Time–<<entity>> TimeSheet–<<entity>> VolunteerProfile•Create relationships–Composition–Specialization–AssociationUniversity of Southern CaliforniaCenter for Systems and Software EngineeringSequence Diagram•Captures the detailed sequence of operations when a use-case takes place•Includes:–Actors–Components–Classes–Hardware–SoftwareUniversity of Southern CaliforniaCenter for Systems and Software EngineeringSteps•Create a package called “Sequence”•Right click on the model–Add diagram Sequence diagram•Sequence diagrams are part of “collaboration”. Each collaboration should be named according to the use-case•Different ways of creating “life-line” entity–Select from existing–Create new object–Unspecified (defined later by drag and drop)University of Southern CaliforniaCenter for Systems and Software EngineeringArchiving•Archiving the model to be transferred to different computers–Share among team members–Submission•Export as a RAS AssetUniversity of Southern CaliforniaCenter for Systems and Software EngineeringSteps1. Go to File -> Export2. Choose RAS -> RAS Asset3. Choose the location to save the file4. Choose the project to export–Make sure that the option “Export as complete Eclipse project” is checkedUniversity of Southern CaliforniaCenter for Systems and Software
View Full Document