Module 3.1: Detail the design

The team completes the detailed design work for the story and create the design resources to support development.

The team is ready to implement the new "Dividend allocation" story. They decide that the best technical solution is to expose a web service that provides the functionality to external customers. Al and other team members collaborate to create the Service Implementation Design model. The service model is key to specifying and documenting the design of the "Allocate Dividends" service.

Al also creates a logical deployment model to help the development team understand the target execution environment, and then initiates a review of the design for a set of key stakeholders to approve.

Help topic icon Configuring Rational Software Architect

Help topic icon Collaborating on models and designs using Rational Software Architect

Help topic icon Reviewing designs

Lab exercises

Complete the lab instructions for this exercise.

Help topic icon Accessing the lab instructions

Lab title: Refine the design to support implementation of user stories

Objectives: In this lab, you use Rational® Software Architect to access designs on the Design Management Server. As an architect, you refine and enrich the existing design and share your local changes on the server. You then create links between design resources to enable traceability.

Time required: Approximately 60 minutes

Lab title: Create and manage a formal review

Objectives: In this lab, you create a formal review to request feedback on a set of design resources. You assign participants to the review, you identify the design artifacts to consider, and you start the review. After participants provide their input, you finalize the review, which is stored on the Design Management Server for later reference.

Time required: Approximately 45 minutes

Lab title: Work with workspaces and deliver change sets

Objectives: In this lab, you experiment with parallel development. You examine the content of two different workspaces to verify that design information is different until the changes are delivered. You then deliver change sets from one child workspace to the parent workspace.

Time required: Approximately 30 minutes


Feedback