Overview:
The Rose tool-specific portion of the training is a 1-day session that is about 80% hands-on lab work and is designed to be delivered:
- as part of the 5-day OOAD training in situations where attendees would not know what Rose would be used for
- in situations where attendees would like to be able to use the full spectrum of Rose capabilities and have previous OOAD training
- along with the additional 2-day Modeling Background training in situations where attendees would like a quick overview of what Rose might be used for ... this can be sufficient for attendees who have prior experience with object-oriented methods and programming, but in most cases, the OOAD training is a better choice
This workshop is focused upon the "mechanics" of Rose. Since it completely assumes that participants already know the "whats, whys, and hows" of the modeling concepts that Rose supports, this workshop provides almost zero background as to why Rose would be used.
As part of covering the "mechanics" of Rose, the course ensures that students understand not only the operational paradigms of Rose, but also some of the "quirks" and issues that you need to understand in order to use Rose effectively.
The optional Modeling Background module can be used in situations where attendees have some OOAD background but do not have all the required concepts. This will provide the minimum background necessary to understand what is to be modeled, but will not provide the background to understand why one does modeling or to know how one arrives at a model, particularly a good model.
In most situations, the extra investment for the 5-day OOAD training in conjunction with the Rose training will have a significantly better payback.
Available Modules::
Introduction to Rational Rose - 1 Day
Stand-alone or inserted when doing the exercises in the OOAD or Modeling Background modules
- The Rose Model, Model Elements and Diagrams
- basic concepts and configuration
- the model – modeling elements and diagrams
- creating and managing model elements
- model-element specifications
- actors, use cases and relationships
- sequence diagrams
- objects and messages
- focus of control
- interconnecting diagrams
- collaboration diagrams
- classes, operations and attributes
- class relationships
- understanding context
- controlling class presentation format
- editing operations and attributes
- editing relationship navigavility and multiplicity
- Activity and Statechart Diagrams
- Component Diagrams
- Deployment Diagrams
- Model Organization
- Publishing a Model
- Common Issues
Modeling Background - 2 Days
- The Rational Unified Process (RUP) : an assembly of industry best practices
- RUP Lifecycle Phases
- The UML Diagrams
- Use Case Fundamentals
- Additional Use-Case Concepts
- Objects
- Classes
- Operations
- Attributes
- Generalization
- Polymorphism
- UML Stereotypes
- UML Properties
- UML Notes
- UML Packages
- UML Interfaces
- UML Components
- UML Subsystems
- Subsystems and Components
- Strengths of Object Orientation
- Review/Quiz
- Relationships
- Association Relationship
- Multiplicity and Navigation
- Aggregation Relationship
- Composition Relationship
- Dependency Relationship
- Generalization (Inheritance) Relationship
- Single Inheritance
- Multiple Inheritance
- Constraints
- Review/Quiz
- Sequence Diagrams
- Collaboration Diagrams
- Use-Case Analysis and Design Steps
- Understanding the Relationships
- Creating an Initial Class Diagram
- Exercise
- UML's "4+1 Views" of Software Architecture
- The Logical View: Modeling Organized Class Structures
- The Implementation View: Modeling the Development Environment
- The Process View: Modeling Concurrency
- The Deployment View: Modeling Distribution and Configurations
- Class Refinement
- Utility Classes
- Defining States
- Refining Attributes
- Refining Multiplicity
- Parameterized Classes
- Refining Generalization
I'm interested, what's the next step?
Learn more about the process or simply contact us to let us know what you're currently thinking or what additional information you'd like and you'll get a reply, normally via email the same working day.
