SOA and BPM Conference Thursday - Web Services Software Factory Modeling Edition (V3)

As I stated yesterday, this is an exciting session. This is the first time in the Microsoft stack that we have been given what us Service designers have wanted - Contract First (Christian Weyer's tool was a first step) because, as Christian says, "It's All About Agreements!" Its the Contract that matters, period.  The modeling capabilities go a long way in V3 and you DON'T have to wait 2-3 years for Oslo for this portion on it. I am sitting here next to my colleague David Pallmann, who of course helped build Indigo in Building 42 so it's kind of surreal :)

Live blog:

• Crazy week as Don as been trying to ship this week plus prepare for the conference

  Take-away's

  • Modeling services is here and here to stay

  • The Service Factory can be bent to your will

  Development tools and automation are continuing to gain popularity in the .NET community

  Software Factories

  •   Help you build a specific kind of application
  • Imply a process for the dev team
  •  Incorporate various content types of guidance
    • Readable's
    •  Reusable's
    • Executables
    • Actionable

   

  • Target Audiences
    •   Teams building Web Services
      •  Different team roles may have different tasks
      • Clear distinction between design and implementation
      • Encourages a layered service architecture
  • Teams building development tools
    •   A growing trend in .NET development
    •   Guidance: Captures and reuses the “rockstar”
    •  Code Gen: Isolate unit testing and increase predictability

  ·         Goals, Motivations and Scope

   For Web Service Developers

  •   Info should be saved in a place other than the code
  • Source code should be easy to generate from the info
  • A higher level of abstraction provides better productivity
  •  Implementation decisions should not have to be made first (delay decisions like ASMX/WCF!)

  ·         For the Web Service developer

  o   Three Models: Service Contract, Data Contract, and Host

  o   Hands-on lab: 8 brief exercises that illustrate usage

  o   Activity sequence and dependency diagrams

  o   Web service architecture topics

  o   Security Guidance Package

  ·         The 4 D’s Design, Decide, Develop, Deploy

DEMO - The Relationship Service - yes those kind of relationships :)

1. New Model Project - Metadata projects for Data Contract, Service Contract

Relationship Service

       RelationshipServiceContract

                 DefineCompatabilityParameter

                 PickTheLuckyWinner

                 WineDineAndImpress

                 PopTheQuestion

1. Create the messages (connectors flow in the direction of the message, yes!!)
2. Model the Data Contract, Add Data Contract Element Part
3. Also have Fault Contracts
4. Property - Pick WCF Implementation Technology - model "lights up" with WCF Settings! ("Decide")
5. VS Add New Project - WCF Implementation Project -> unfolds into "best practice" project layout - Business Entities, Business Logic, etc (encouraging a Layered Architecture pattern)
6. Generate Code

Modeling XSD "wicked hard" - didn't try it

Policy attribute (Class) allows applying Exception Shielding Pattern - cool!