University of Southern California Center for Systems and Software Engineering Rational Software Modeler Tutorial Pongtip Aroonvatanaporn.

Slides:



Advertisements
Similar presentations
Visio 2007 for UML Tutorial. Overview The tutorial demonstrates how to use Visio 2007 to create UML diagrams. We will focus on five most widely used UML.
Advertisements

System Modelling System modelling helps the analyst to understand the functionality of the system and models are used to communicate with customers. Different.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System modeling 2.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Activity, Collaboration, and Component Diagrams Philip Liew
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
© Copyright Eliyahu Brutman Programming Techniques Course.
Lecture a: Additional UML Models: Package, Activity, Deployment Lecture b: Generalization, Aggregation and Additional Domain Model Notation Copyright W.
Sharif University of Technology1 Design and Use-case Realization Software Engineering Laboratory Fall 2006.
Use Case Analysis – continued
PRJ566: PROJECT PLANNING AND MANAGEMENT Class Diagrams.
Unified Modeling Language
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 5 Analysis Model. Analysis model (AM) The first step in describing how the system will implement the requirements specification The first step.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
Software Engineering Chapter 8 Fall Analysis Extension of use cases, use cases are converted into a more formal description of the system.Extension.
University of Southern California Center for Systems and Software Engineering Approaching the Design Stages Pongtip Aroonvatanaporn November 25, /25/20091.
Unified Modeling Language, Version 2.0
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
Object-Oriented Modeling Chapter 10 CSCI CSCI 1302 – Object-Oriented Modeling2 Outline The Software Development Process Discovering Relationships.
Object-Oriented Software Development F Software Development Process F Analyze Relationships Among Objects F Class Development F Class Design Guidelines.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 Object-oriented and Structured System Models.
IBM Software Group ® Overview of SA and RSA Integration John Jessup June 1, 2012 Slides from Kevin Cornell December 2008 Have been reused in this presentation.
Chapter 7 System models.
System models l Abstract descriptions of systems whose requirements are being analysed.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Programming Logic and Design Fourth Edition, Comprehensive Chapter 15 System Modeling with the UML.
Domain Modeling Part2: Domain Class Diagram Chapter 4 pp part 2 1.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
Actors and Use Case Diagrams Month Day, Year. Agenda Training Plan Overview Review Detailing Requirements with Requisite Pro Concepts Setting Up XDE Integration.
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
TAL7011 – Lecture 4 UML for Architecture Modeling.
Unified Modeling Language. Object Oriented Methods ► What are object-oriented (OO) methods?  OO methods provide a set of techniques for analyzing, decomposing,
Identifying & Creating Use Cases – Part 1 Month Day, Year.
University of Southern California Center for Systems and Software Engineering Approaching the Design Stages Pongtip Aroonvatanaporn CSCI577 Fall 2010 November.
Introduction to OOAD & Rational Rose cyt. 2 Outline RUP OOAD Rational Rose.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Slide 1 Classes and Objects. Slide 2 Messages and Methods.
1 Unified Modeling Language, Version 2.0 Chapter 2.
CPSC 871 John D. McGregor Process – an introduction Module 0 Session 3.
Analysis Yaodong Bi. Introduction to Analysis Purposes of Analysis – Resolve issues related to interference, concurrency, and conflicts among use cases.
CPSC 372 John D. McGregor More EPF Module 2 Session 4.
University of Southern California Center for Systems and Software Engineering Configuration Management: Concepts and Tools Pongtip Aroonvatanaporn CSCI.
UML - Development Process 1 Software Development Process Using UML.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
® IBM Software Group © 2007 IBM Corporation Module 3: Creating UML Diagrams Essentials of Modeling with IBM Rational Software Architect, V7.5.
OOD OO Design. OOD-2 OO Development Requirements Use case analysis OO Analysis –Models from the domain and application OO Design –Mapping of model.
1 Using Rational Rose ® to construct UML diagrams.
1 SWE Introduction to Software Engineering Lecture 14 – System Modeling.
Introduction to UML and Rational Rose UML - Unified Modeling Language Rational Rose 98 - a GUI tool to systematically develop software through the following.
Unified Modeling Language. What is UML? Standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems,
PAPYRUS Tutorial CSOS 손 태 용.
UML (Unified Modeling Language)
UML Diagrams: Class Diagrams The Static Analysis Model
UML(Unified Modeling Language)
UML Diagrams By Daniel Damaris Novarianto S..
Systems Analysis and Design With UML 2
UML Diagrams Jung Woo.
Online Shopping APP.
面向对象分析与设计 Use of starUML By Wang Meihong.
Domain Class Diagram Chapter 4 Part 2 pp
Unified Modeling Language
Subversion Basics Guide
Analysis models and design models
Software Design Lecture : 15.
PPT4: Requirement analysis
Presentation transcript:

University of Southern California Center for Systems and Software Engineering Rational Software Modeler Tutorial Pongtip Aroonvatanaporn

University of Southern California Center for Systems and Software Engineering Outline Setting up RSM environment Activity Diagram Use-case Diagram Class Diagram Sequence Diagram Archiving

University of Southern California Center for Systems and Software Engineering RSM 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 and latest JDK/JRE –Choose “Extend Eclipse”

University of Southern California Center for Systems and Software Engineering Activity Diagram Captures a sequence of activities and actions In CSCI577, used to model business workflow or business process

University of Southern California Center for Systems and Software Engineering Components Partitions Actions Control node (i.e. decision node) Control flow –Transfer of action Object node (i.e. data) Object flow –Transfer of object

University of Southern California Center for Systems and Software Engineering Steps 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 flow

University of Southern California Center for Systems and Software Engineering Use-Case Diagram Captures the interaction between actors and system Shows the possible capabilities/functionalities the system can perform Association –Roles and multiplicities do not apply

University of Southern California Center for Systems and Software Engineering Components 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 model

University of Southern California Center for Systems and Software Engineering Steps 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 California Center for Systems and Software Engineering Class Diagram Detailed designs of the classes Contains –Attributes –Operations –Relations between classes

University of Southern California Center for Systems and Software Engineering Components Classes –Boundary: pages, view –Controller: logic –Entity: model, data Relationships –Association: “Has-a” –Aggregation: “Part-of” –Composition Stronger aggregation Lives and dies with parent

University of Southern California Center for Systems and Software Engineering Steps Create a new model called “Design Model” Create a package called “Design Classes” Add new classes: – > VolunteerPage – > TimeController – > Time – > TimeSheet – > VolunteerProfile Create relationships –Composition –Specialization –Association

University of Southern California Center for Systems and Software Engineering Sequence Diagram Captures the detailed sequence of operations when a use-case takes place Includes: –Actors –Components –Classes –Hardware –Software

University of Southern California Center for Systems and Software Engineering Steps 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 California Center for Systems and Software Engineering Archiving Archiving the model to be transferred to different computers –Share among team members –Submission Export as a RAS Asset

University of Southern California Center for Systems and Software Engineering Steps 1.Go to File -> Export 2.Choose RAS -> RAS Asset 3.Choose the location to save the file 4.Choose the project to export –Make sure that the option “Export as complete Eclipse project” is checked

University of Southern California Center for Systems and Software Engineering Questions?