Tool Mentor: Designing Use Cases Using Rational XDE Developer










var backPath = './../../../';
var imgPath = './../../../images/';
var nodeInfo=[{view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_gpYSoAILEdq-_NKqZM1EhA", "_qS-iwAIOEdqTna4sZVFRow", "{303A82D2-E3AB-4501-8563-0D4D43782AF9}", "{89CA76CF-37A6-4590-B9B5-90942D2B50E8}"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_zRigkAILEdq-_NKqZM1EhA", "_U5tiUAISEdqTna4sZVFRow", "{303A82D2-E3AB-4501-8563-0D4D43782AF9}", "{89CA76CF-37A6-4590-B9B5-90942D2B50E8}"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_AUv4MAIMEdq-_NKqZM1EhA", "_5ZuQsAIUEdqEutyfYo0quQ", "{303A82D2-E3AB-4501-8563-0D4D43782AF9}", "{89CA76CF-37A6-4590-B9B5-90942D2B50E8}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_jD8dUAIbEdqEutyfYo0quQ", "_F1OgYAIbEdqEutyfYo0quQ", "{303A82D2-E3AB-4501-8563-0D4D43782AF9}", "{89CA76CF-37A6-4590-B9B5-90942D2B50E8}"]}];
contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);










Tool Mentor: Designing Use Cases Using Rational XDE Developer















This tool mentor describes how to perform Designing Use Case with Rational XDE Developer.


Tool: Rational XDE Developer






Relationships



Related Elements


Use-Case Design






Main Description



Overview This tool mentor supports Designing Use Case with Rational XDE Developer - Java Platform Edition. The steps in this tool mentor match those in the corresponding task. Links to topics in XDE online Help are marked with . The following steps are performed in this tool mentor: Describe Interactions Between Design Objects Simplify Sequence Diagrams Using Subsystems (optional) Describe Persistence-Related Behavior Refine the Flow of Events Description Unify Design Classes and Subsystems Evaluate the Results Describe Interactions Between Design Objects For each use-case realization, you should illustrate the interactions between its participating design objects by creating one or more sequence diagrams. You might have created early versions of these diagrams, the analysis use-case realizations, during Task: Use-Case Analysis. These analysis use-case realizations describe interactions between analysis classes. They must be evolved to describe interactions between design elements. One approach is to create a new use-case realization and sequence diagrams by following these steps: Navigate to the Design-Model package in which the new use-case realizations are to be created. See Rational XDE Model Structure Guidelines. Create a use-case diagram. See Adding Diagrams . Add the use-case realization (a collaboration instance) to the diagram. (See Adding Shapes to Diagrams .) Give it the same name as the use case. Drag and drop the use case that it realizes onto the diagram. See Adding Shapes to Diagrams . Add a realization relationship from the use-case realization to the use case. See Adding Realization Relationships . For each independent sub-flow (scenario) create one or more interaction instances. (In the Model Explorer, right-click the collaboration instance, and then click Add UML > Interaction Instance.) Consider naming the interaction instance "<use-case name> - <flow type>." Create a sequence diagram for this interaction instance. See Adding Diagrams . Type a brief description of the scenario that the sequence diagram depicts. See Documenting Model Elements . Drag and drop actors, classes, and interfaces onto the diagram to create objects for interaction. See Adding Shapes to Diagrams . Add messages between the objects. See Adding Messages or Stimuli . Describe each message. See Documenting Model Elements . To describe how the object behaves when it receives the message, assign an operation to the message. See Assigning Operations to Messages or Stimuli . Alternatively, if you are not maintaining a separate Analysis Model, you may decide to modify your existing sequence diagrams to reflect the evolution of the design elements. Reference: Working with Interaction (Sequence) Diagrams . Simplify Sequence Diagrams Using Subsystems (optional) See the previous step for guidance on working with sequence diagrams. Describe Persistence-Related Behavior Persistence mechanisms are ideally described using patterns. See the following topics in the Rational XDE online Help: Rational XDE Design Patterns Benefits of Using Patterns Understanding J2EE Pattern-Driven Development J2EE Pattern-Driven Development Supported J2EE Patterns Defining Relationships for EJBs Persistence Relationships Creating Persistence Relationships Between EJBs Refine the Flow of Events Description Additional description can be added to the sequence diagrams for clarification. Text can be added anywhere on the diagram. Notes can be added and attached to shapes on the diagram. Consider using the RUP-provided template for Work Product: Use Case Realization. Reference: Attaching Notes to Shapes , Documenting Model Elements , Linking External Files to Model Elements Unify Design Classes and Subsystems As use cases are realized, you must unify the identified design classes and subsystems to ensure homogeneity and consistency in the Design Model. Part of unifying the design is identifying common patterns that can be factored out and reused. See the following topics in the Rational XDE online Help: Implementing Design Patterns Rational XDE Design Patterns Benefits of Using Patterns Evaluate the Results There is no Rational XDE specific guidance for this step.





©  Copyright IBM Corp. 1987, 2006.  All Rights Reserved.







contentPage.onload();