C l e m e n s

Introduction, see the About Me page, still have to update this.

Beside introduce my self also setting the stage. TAP project, this project: “Public Case Study Visual Studio 2008 Team Architect and Software Factories ” ] and the focus during this session “I talked more about the technical details around the DSL implementations than the real project”.

The structure of the session: The ideas, tools, solutions, lessons and what’s next.

The ideas, as always.. Enabling ALM with Automation.
Introducing [Microsoft] Application Lifecycle Management, ALM Definitions
Viewpoint Models -Small models helping different stakeholders to work together within their own languages and usefull view on the application[s]. Not only generating code but also other artifacts necessarily for the application [for example confg items] and for the different stakeholders to do their job better [for example testcases]…
It’s all about Viewpoints.. DSI – ALM – DFO -SDM and Communication..!

The Tools, with first some background on Microsoft’s modeling strategy DSI and where Team Architect fits.
See this post: DSI, OSLO and Models in the Lifecycle. Get Prepared..!

A walkthrough the default functionality of Team Architect 2008, the diagrams.
A Visual Studio Team Edition for Software Architects Orcas Project Walkthrough

How Do I- Use the Retooled System Designer in Visual Studio Team System 2008 Architecture Editio

The pros and cons in using Team Architect 2008…
Pros: Top-Down design [Top-Down System Design by Delegating Behavior] and deployment validation
Cons: Implement Application
(haven’t post much about this… strange, will do for Rosario ;-)

Change the implement application feature with the service factory:
Service Factory @ Application Designer
The Greenfield
I still like this example: Amazon Services, the Service Model.

Challenges in the implementation of Service Factory @ Application Designer:
Mainly who is responsible for which data and how to re-generate lower level models:
Service Factory Modeling Edition Extensibility, Regenerate Service Model
How To Fire a Guidance Package Recipe from the Implement Application Feature of Team Architect
How To Collect Data from the Application Diagram to create WSSF Service Models

There is more knowledge in the diagram which we can use… for example, we could generate service agents.
Model Service Agents with the Service Factory

I still like the idea to call it “Lifecycle Portfolio Management” [something like that] instead of ALM, just because we [or customers] are not developing just one application, but a large amount of applications, components, services and for sure legacy systems. Visual Studio is hard to use when modeling this large environments. Putting all the projects in one solution isn’t an option. Their needs to something like solution linking, responsibility between different solutions, references… anyway a workaround is this:
Autonomous Develop Services for SOA Projects with Team Architect and Service Factory

While the service consumer and service provider modeling solutions are lower level, we generate them from the higher level Application Diagram, this solution is at the same level as the application diagram… the security model.
Creating Secure Services, with Visual Studio Team Architect and the Web Service Software Factory
see also this post for the Design For Operations ideas: It’s all about Viewpoints.. DSI – ALM – DFO -SDM and Communication..!

After some discussion the session continued with some Rosario things…

the UML Diagrams
UML, the Most Wanted Feature in Team Architect
Rosario - Create Sequence Diagram from Existing Code
Rosario - Create Sequence Diagram from Binary

Beside this a little bit about the backplane and progresion…

Conceptual design upgrade it to physical design and code. In this example Logical Class Diagram for some idea gathering and when you find something interesting enough “upgrade” it to physical level…
I like this idea: start drawing ideas on the surface with the business guy [classes, sequences] and upgrade it when it’s good enough…  
Anyway, there are more interesting scenarios also with DSL’s using a hybrid approach that combines UML and DSL’s
See this post from Steve Cook: I’ve got a new job working on DSLs and UML! and from Cameron Skinner DSL+UML = Pragmatic Modeling and this article UML versus Domain-Specific Languages article in Methods & Tools

Beside using UML with DSL you also can use UML with some kind of methodology… for example the “Tmap Process Cycle Test Approach” to generate TestCases…
Testing in the Lifecycle [ALM]... a focus on automation
Rosario Video - Generate TestCases from ActivityDiagram