IBM SG24-7368-00 Preparing the Workbench

110 Model Driven Systems Development with Rational Products

In this first section, you will:

򐂰Explore and become familiar with the Workbench.

򐂰Customize the Workbench to hide multiplicity and roles from UML diagrams.

򐂰Install the MDSD plug-in to support model-driven systems development.

Preparing the Workbench

In this task you are customizing the environment so that multiplicity and role

information is not displayed on the diagrams:

򐂰Launch Rational Systems Developer3 by selecting Start→ IBM Rational

Systems Developer.

򐂰Create a new workspace by typing C:\Workspaces\MDSD into the Workspace

field (replacing anything that might already be there) (Figure 6-17).

Figure 6-17 Workspace Launcher

򐂰If it appears that RSD is hung, look for the Workspace Launcher dialog behind

the RSD window.

򐂰When the Workbench starts up, close the Welcome window if it is displayed

(Figure 6-18).

3 This example assumes Rational Systems Developer Version 7

Contents

Main Page Page Page Contents Page Page Page Page Page Notices x Trademarks Preface The team that wrote this book Thank you Become a published author Comments welcome Page The challenges of systems development The changed context for systems development Management of complexity Creative/dynamic and transactional complexity Overview of model-driven systems development The benefits of modeling Central problems MDSD addresses Managing complexity by managing levels of abstraction and levels of detail Multiple views to address multiple concerns Integration of form and function Two analogies Project management Restaurant ownership Scalability: Isomorphic composite structures and recursion Benefits of model-driven systems development Reduction of risk Enhanced team communication Explicit processes for reasoning about system issues Early detection of errors Integration as you gobetter architecture Traceability Well defined semantics Core processes of model-driven systems development Defining context Defining collaborations Distributing responsibilities Prerequisites/required foundational concepts/languages UML SysML How the book is organized and key concepts Definitions System Service implementation Requirement Artifact Use case Operation Actor Locality Connection Connections Design points Four basic principles Separation of concerns Integration System decomposition Additional design points Apply the RUP framework to systems development Page Employ the appropriate semantics and modeling languages Provide tool assets Maintain all model levels as program assets Key concepts Model levels Context level Analysis level Design level Implementation level Viewpoints Page Views Transformation methods System of systems decomposition system Operations analysis Joint realization Requirement derivation Summary: The core MDSD process Page Page Page The importance of understanding context Context and description How The system in context An important context: Usage Usage-driven versus feature-driven system design Page MDSD Step 1: Define the system context system Actors and boundaries MDSD Step 2: Finding actors Primary and secondary actors Questions to discover actors Actors and value Actors and the system boundary MDSD Step 3: Create a context diagram I/O entities MDSD Step 4: Finding I/O entities Use cases Page MDSD Step 5: Finding use cases Page Writing a brief description Actor involvement in use cases Use case flows of events MDSD Step 6: Write use case flows of events Level of detail in use case flows Initiation of the use case Using activity diagrams Understanding collaboration from a black-box perspective Identifying operations MDSD Step 7: Operation identification Page Requests: The key to operations vacuum Specifying request signatures Information in the MDSD model information Message naming: A quiz Toward better requests Page Identifying operations from the sequence diagram Page Page Refactoring operations MDSD Step 8: Refactoring and consolidating enterprise operations More about operations Page Summary Page Understanding collaboration Operation realization MDSD Step 9: Operation realization The logical viewpoint MDSD Step 10: Creating element context diagrams Operation analysis Page Page Page Flowdown to further levels MDSD Step 11: Create use case models at levels below the enterprise Page of responsibility Localities MDSD Step 12: Developing a locality model Localities and systems engineering Locality semantics Connection semantics contr ol Localities and nodes Localities, services, and interfaces Design trades Design trades Page Sequence diagrams with localities Joint realization Page Joint realization tables Page Page Page Page Page Model structure Organizing an MDSD model Level 0 model organization Page MDSD UML Profile Page Page Levels of decomposition Actors Logical entities Page Page Use cases and operations Page Distribution entities integration of concerns Automation Creating MDSD artifacts UML diagrams for systems modeling Preparing the environment Preparing the Workbench Create a new UML Modeling Project Page Page Installing the MDSD plug-in Page Page Page Modeling the system as a black box Create the system model Page Create the context diagram Page Page Page Page Page Page Page Page Create black-box sequence diagram Page Page Page Summary Modeling the system at level 1 Identify systems that will collaborate at L1 Realize a system operation Page Page Page Creating a localities diagram Page Page Page Page Page Introduction MDSD (RUP SE) as contributor to SysML MDSD with SysML Basics of SysML Areas of focus of SysML ConstraintProperty and are typed by ConstaintBlocks. A constraint block defines Requirements modeling Page Page Page Block semantics Block definition diagram Page pr ocess r equir ement r elated Internal block diagram Ports Atomic Port Page Page Constraints ConstraintBlocks ConstraintPr o perty Parametrics Page Behavior modeling MDSD with SysML Blocks as basic structural units Understanding context Using blocks to stand for systems Page Requirements and understanding context Understanding collaborations Page Understanding distribution of responsibilities Parametrics Page Page Page Page Summary of SysML basics Page Page Page Why we build systems Systems engineering Systems concerns How does MDSD fit in? Page Page A specification template Page Revision History Document Approval Table of Contents Use-Case Specification: <Use-Case Name> 1 Brief Description 2 Actor Catalog 3 Preconditions 3.1 < Precondition One > 4 Postconditions 4.1 < Postcondition One > 5 Basic Flow of Events Page 6 Alternative Flows 6.1 <Area of Functionality> 6.1.1 < <n><a> First Alternative Flow > 6.1.2 < <n><b> Second Alternative Flow > 6.2 <Another Area of Functionality> 6.2.1 < <nn><x> Another Alternative Flow > 7 Subflows 7.1 <S1 First Subflow > 7.2 < S2 Second Subflow > 8 Extension Points 8.1 <Name of Extension Point> 9 Special Requirements 9.1 < First Special Requirement > 10 Additional Information Page B Locating the Web material Page Abbreviations and acronyms Page Related publications IBM Redbooks publications Other publications Online resources How to get IBM Redbooks Help from IBM Index A B C D E F G I J M N O 202 P R S T U V W Page Page Page Page INTERNATIONAL TECHNICAL SUPPORT ORGANIZATION For more information: ibm.com/redbooks Model Driven Systems Development with Rational Products Back cover