Very useful, these mini-stories founded on the CTP10 desktop
- Walkthrough: Visualizing Interaction Sequences Between Service-Oriented Applications
- Walkthrough: Designing and Visualizing Classes and Their Interactions
- Walkthrough: Building Windows Communication Foundation Web Services Using Distributed System Designers and the Web Service Software Factory (WSSF)
From the "Stories"document [the interesting topics highlighted in red]:
In this CTP, you will find many new exciting features that help make design and development more productive. These features can be grouped in to two categories: factory integration and new integrated designers.
Factory integration starts with a base design experience in Visual Studio Team Edition for Software Architects, which applies to multiple application types. We then extend this experience for specific application types (Web client, smart client, and so on) using downloadable ‘factories’ supplied by the Patterns & Practices group at Microsoft. These factories provide a guided design experience based on best practices that accelerate enterprise design and development using the Microsoft platform. A pluggable architecture allows these factories to be shipped continuously on the Web so you can continue to receive the latest design guidance between major releases of Visual Studio. In this CTP, we’ve already downloaded and installed a factory for building Web-based applications based on WCF to demonstrate one specific application type (Web Services Software Factory).
To better enable a wider range of design experiences, in this CTP we have added two new designers “in the box.” The sequence designer allows you to model the interaction of services or objects in your application. This is very useful as a design tool to help you define how your application will fulfill the requirements of your solution. Using this designer, you can identify important classes and services and make sure that they have the correct operations to support your scenarios. In addition, we have added a logical class designer to complement the existing physical class designer. This designer lets you reason about class design before committing to an implementation and enables you to model relationships not possible just by using the physical class designer. Most importantly, these two designers are integrated so that changes in one designer naturally flow to the other to keep your models synchronized and support accurate code generation and discovery in future CTPs.
So I played with it [not heavy, still quite busy with Orcas], I recreated the models from our original project
First the application designer:
I still think to many shapes that don't belong there [the red ones].
The Application Explorer:
I really like it it's called "ServiceContractDiagramViewpoint"... see this post about viewpoints.
The Sequence Designer:
I have to play a little bit more with this one... looks / works create maybe the shapes should have the same color as they have on the Application Designer [not that important].
Anyway, more details will follow...