20090410 J Spring Pragmatic Model Driven Development In Java Using Smart

1<TITLE>© Copyright Capgemini 2008 All Rights Reserved

Sander Hoogendoorn, Capgemini

Rody Middelkoop, Avisi

Pragmatic model driven development in Java using Pragmatic model driven development in Java using

smart use cases and domain driven developmentsmart use cases and domain driven development

Sander HoogendoornSander Hoogendoorn

Capgemini

� Principal technology officer

� Capgemini agile thought leader

� Certified global software engineer (SE4)

� Chief architect Accelerated Delivery Platform

Other

� Author books (UML, agile) and articles

� Speaker at conferences



� Microsoft Partner Advisory Council .NET

� Columnist Software Release Magazine, SDN Magazine

� Editorial board Software Release Magazine

� Editorial board Tijdschrift IT Management

� Advisory board @Portunity

� Member expert panel Computable

Web

� www.sanderhoogendoorn.com

� www.accelerateddeliveryplatform.com

Rody MiddelkoopRody Middelkoop

Avisi

� Technical consultant

Hogeschool Arnhem Nijmegen (HAN)

� Lecturer Software Engineering

Other

� Sun Certified Java Programmer / Developer


� Author of several articles

� Contributor Livre


Web

� www.avisi.nl

� rodymiddelkoop.blogspot.com

AgendaAgenda

Introduction

� Model driven development

� Pragmatic model driven development

� Our approach

� Benefite

Smart use cases

� Modeling smart use cases

� Smart use cases in code


� Smart use cases in code

Domain driven design

� Domain objects

� Smart references

� Value objects

Generating code

� Text templating

� Using Tobago MDA

Demo’s


An introduction

Model driven developmentModel driven development

Model driven developmentModel driven development

Why?

� Bridge gap between design and code

� Improve quality of delivered software

� Raise productivity

� Achieve platform and framework independency

� Increase testability

How?

� Proprietary techniques

SH


� Proprietary techniques

� DSL’s (textual and graphical)

� UML

� Database

� India

What?

� Modeling tool code generation

� Development tool code generation

� Intermediate code generation


To model driven development

A A pragmaticpragmatic approachapproach

Forms

Use cases

Domain

Software Architecture

TobagoMDA Frameworks

Specifications

Existing

Applications

Domain

Smartuse cases

User interface

specification1. Map your 1. Map your

business processes business processes

to smart use casesto smart use cases

1. Map your 1. Map your

business processes business processes

to smart use casesto smart use cases

4. Generate 4. Generate

code using a code using a

text template text template

engineengine

4. Generate 4. Generate

code using a code using a

text template text template

engineengine

5. Finalize your 5. Finalize your

applicationapplication

5. Finalize your 5. Finalize your

applicationapplication


Domain

objects

Data / Serviceclasses

Databases

Test

scenario’s

Businessmodels

DomainModel

2. Create the 2. Create the

domain modeldomain model

2. Create the 2. Create the

domain modeldomain model3. Establish3. Establish

your software your software

architecture(s)architecture(s)

3. Establish3. Establish

your software your software

architecture(s)architecture(s)


What makes a use cases smart?

Smart use casesSmart use cases

Different levels of use casesDifferent levels of use cases

Cloud level

Kite level

High summary

Summary

MergeMerge

companiescompanies

MergeMerge

mortgage systemsmortgage systems

Place Place


Sea level

Fish level

Clam level

User goal

Sub-function

Too low

SelectSelect

productproduct

InsertInsert

orderlineorderline

Place Place

orderorder

Different levels of use casesDifferent levels of use cases

‘Regular’ use cases

� Only user goal level use cases

� Use cases ‘as they are intended’

� A single use case describesa single elementary business process

� Differ in granularity too much

� Law of Large Numbers does not apply

Smart use cases

UnifiedVery

differentGranularity

VisualTextualFormat

Smart

use case

Regular

use case


Smart use cases

� User goal and sub function level use cases

� Good unit of work and estimation

� A single elementary business process is modeledin a single use case diagram

� A single user goal level use case + auxiliary use cases at sub-function level

� Very similar granularity

NormalIncidentalRe-use

LikelyPossibleTraceability

in code

GoodLousyUnit of work

EasierHardEstimates


Modeling smart use casesModeling smart use cases


Approach

� Create a use case diagram for each

elementary business process

� Model a (user goal level) use case that

maps to the elementary business process

� Name it after the elementary business

process


process

� Identify the actors executing the use case

� Identify the sub-function level use cases

� Model include and extend relationships

� Identify supporting actors

Identifying subIdentifying sub--function level use casesfunction level use cases

Guidelines

� Identify re-use

� Model one form per use case

� Model one use case per functional web

part

� Isolate unknown functionality


� Isolate unknown functionality

� Identify complex functionality

� Show extensive reporting

� Model complex calculations

� Isolate interaction with others

� Avoid low level (database) interaction




Decorating the model

Smart use case stereotypesSmart use case stereotypes


What?

� Classify model elements

� Do not add meaning to model

� Define custom stereotypes

Why?

� Speed up analysis and design

RM


� Speed up analysis and design

� Map design to software architecture

� Generate lots of code!

� Standarize functional testing

AddingAdding stereotypesstereotypes SH


AddingAdding stereotypesstereotypes





Smart use cases and domain design

Mapping to software Mapping to software architecturearchitecture

Presentation

Process

Domain

Pages

UserControls

Panels

Use cases

Workflow

Domain objects / Entities

Factories / Repositories

Enums / Value objects / Smart references


Data / Services

Outside world


[Mapping]

Table Gateways

Queries

[Mapping]

Database

Presentation

Process

Domain

Pages

UserControls

Panels

Use cases

Workflow





Exact SAP BizTalk Java

Data / Services

Outside world


[Mapping]

Service gateways

Service locators

[Mapping]

Services / ESB

Presentation

Process

Domain

Service contracts

Operation contracts

Data contracts

Use cases

Services





Data / Services

Outside world


[Mapping]

Table Gateways / Service Gateways

Queries / Service Locators

[Mapping]

Database

Services / ESB

Exact SAP BizTalk Java


A brief introduction

Domain driven designDomain driven design


Definition

� Base complex domain designs on the model

� Primary focus is on the domain and domain logic

In practice

� Model the domain

� Apply the extended domain driven vocabulary

� Build the domain layer


� Build the domain layer

� Hook in process layer

� Plug in data / services layer

Useful when

� The domain of your application is core

� Two tier is not (never?) desirable

� Application needs to function independent of back office, data sources or services


Vocabulary

� Entity / Domain object

� Association

� Value object

� Aggregate

� Repository


� Repository

� Factory

� Service

Additional vocabulary

� Enumeration

� Smart reference

Example Example –– Class diagramClass diagram



Properties and property types

DefiningDefining classesclasses

Properties and property typesProperties and property types

Basic types

� string, integer, DateTime

� Include nullable wrapping

Enumerations

� Set up at design time, unchangeable at run-time

� Genders, Categories

Value objects

� No specific instances

RM


� No specific instances

� Isbn, Email, Url, Money

Smart references

� Changeable at run-time, such as ContractType

Associations

� Cached domain objects such as Country, Nationality

� First level citizens such as Customer, Product


Value objectValue object

Value object Value object -- ImplementingImplementing


Value object Value object –– In useIn use



Smart referenceSmart reference

Smart reference Smart reference -- TableTable


Smart Smart referencereference -- In In entityentity


Smart reference Smart reference –– In useIn use



Text templatingText templating

Model driven development Model driven development –– Template enginesTemplate engines

How?

� Define project

� Define patterns

� Import model

� Generate deliverable

� Finalize code

Additional features

SH


Additional features

� Combine model elements

� Combine types of model elements

� Remember location

Changing the model withour losing code

� Partial classes

� Inherited classes

� Marking code

Tobago MDA Tobago MDA –– www.accelerateddeliveryplatform.comwww.accelerateddeliveryplatform.com


Tobago MDATobago MDA


Tobago MDATobago MDA


Model driven development Model driven development -- Template enginesTemplate engines

Template engine Template engine knows (part of) knows (part of) the UML meta the UML meta

modelmodel

Template engine Template engine knows (part of) knows (part of) the UML meta the UML meta

modelmodel

Properties can Properties can be used in be used in templatestemplates

Properties can Properties can be used in be used in templatestemplates

RM


Presentation

Process

Data / Services

Freemarker

Sitemesh

DisplayTag

Struts2

XWork Actions

EJB3 Services

EJB3 DataAccessObjects

Spring


Outside world MySQL

Domain

JPA Domain objects

Enums

Value objects

Smart references

Spring

Model driven development Model driven development -- TemplatesTemplates


Generate many things e.g. Table create scriptsGenerate many things e.g. Table create scripts


Generate many things e.g. Table create scriptsGenerate many things e.g. Table create scripts



Demo!

Generating codeGenerating code

www.accelerateddeliveryplatform.comwww.accelerateddeliveryplatform.com SH



www.accelerateddeliveryplatform.com

[email protected]

[email protected]

Twitter: aahoogendoorn LinkedIn: aahoogendoorn rodym

References and questionsReferences and questions

Technology

20090410 J Spring Pragmatic Model Driven Development In Java Using Smart