Pragmatic Model Driven Development In Java Using Smart Use Cases

Pragmatic model driven development in Java using
smart use cases and domain driven development
Sander Hoogendoorn, Capgemini
Rody Middelkoop, Avisi

TWO GUYS TRYING TO TALK REALLY FAST AND BUILD AN APP IN 45 MINUTES 1
© Copyright Capgemini2008 All Rights Reserved

Sander Hoogendoorn

Capgemini
 Principal technology officer
 Capgemini agile thought leader
 Certifiedglobal 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 Middelkoop

Avisi
 Technical consultant
Hogeschool Arnhem Nijmegen (HAN)
 Lecturer Software Engineering
Other
 Sun Certified Java Programmer / Developer
 Author of severalarticles
 ContributorLivre
 Speaker at conferences
Web
 www.avisi.nl
 rodymiddelkoop.blogspot.com


Agenda

Introduction
 Model driven development
 Pragmatic model driven development
 Ourapproach
 Benefite
Smart use cases
 Modeling smart use cases
 Smart use cases in code
Domain driven design
 Domain objects
 Smart references
 Value objects
Generating code
 Text templating
 Using Tobago MDA
Demo’s


Model driven development
An introduction


Model driven development SH

Why?
 Bridge gap between design and code
 Improvequality of delivered software
 Raiseproductivity
 Achieve platform and framework independency
 Increasetestability
How?
 Proprietarytechniques
 DSL’s (textual and graphical)
 UML
 Database
 India
What?
 Modeling tool code generation
 Development tool code generation
 Intermediate code generation


A pragmaticapproach
To model driven development


User interface Software Architecture
specification
1. Map your 5. Finalize your
business processes application
to smart use cases
Existing
Applications Smart
use cases
Forms

Use cases
4. Generate
code using a
Tobago
text template Frameworks
MDA
engine
Specifications
Domain
Domain
objects
Model

Data / Service
Business
classes
models

2. Create the Test
3. Establish
scenario’s
domain model your software
Databases
architecture(s)


Smart use cases
What makes a use cases smart?


Different levels of use cases
Merge
companies

Cloud level High summary

Merge
mortgage systems
Kite level Summary

Place
order
Sea level User goal

Fish level Sub-function
Select
product

Clam level Too low
Insert
orderline

Different levels of use cases

‘Regular’ use cases
Regular Smart
 Only user goal level use cases use case use case
 Use cases ‘as they are intended’
 A single use case describes Format Textual Visual
a single elementary business process
 Differ in granularity too much Very
Granularity Unified
different
 Law of Large Numbers does not apply
Smart use cases Estimates Hard Easier
 User goal and sub function level use cases
 Good unit of work and estimation Unit of work Lousy Good
 A single elementary business process is modeled
in a single use case diagram
Re-use Incidental Normal
 A single user goal level use case
+ auxiliary use cases at sub-function level
 Very similar granularity Traceability
Possible Likely
in code


Modeling 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
 Identify the actors executing the use case
 Identify the sub-function level use cases
 Model include and extend relationships
 Identify supporting actors


Identifying sub-function level use cases

Guidelines
 Identify re-use
 Model one form per use case
 Model one use case per functional web
part
 Isolate unknown functionality
 Identify complex functionality
 Show extensive reporting
 Model complex calculations
 Isolate interaction with others
 Avoid low level (database) interaction


Smart use case stereotypes
Decorating the model


Smart use case stereotypes RM

What?
 Classify model elements
 Do notaddmeaning to model
 Definecustom stereotypes
Why?
 Speed up analysis and design
 Map design to software architecture
 Generatelots of code!
 Standardizefunctional testing


Adding stereotypes SH


Adding stereotypes


Smart use case stereotypes


Mapping to software architecture
Smart use cases and domain design


Pages
UserControls
Presentation
Panels

Use cases
Process Workflow

Domain objects / Entities
Factories / Repositories
Domain
Enums / Value objects / Smart references
[Mapping]

Table Gateways
Queries
Data / Services
[Mapping]

Outside world Database


Pages
UserControls
Presentation
Panels

Use cases
Process Workflow

Domain
[Mapping]

Service gateways
Service locators
Data / Services
[Mapping]

Exact SAP BizTalk Java
Outside world Services / ESB


Service contracts
Presentation Operation contracts
Data contracts

Use cases
Process Services

Domain
[Mapping]

TableGateways / Service Gateways
Data / Services Queries / Service Locators
[Mapping]

Exact SAP BizTalk Java
Database
Outside world
Services / ESB


A brief introduction



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
 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
 Factory
 Service
Additional vocabulary
 Enumeration
 Smart reference


Example – Class diagram


Defining classes
Properties and property types


Properties and property types RM

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
 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 object


Value object - Implementing


Value object – In use


Smart reference


Smart reference - Table


Smart reference - In entity


Smart reference – In use


Text templating


Model driven development – Template engines SH

How?
 Define project
 Define patterns
 Import model
 Generate deliverable
 Finalize code
Additional features
 Combine model elements
 Combine types of model elements
 Remember location
Changing the model withourlosing code
 Partial classes
 Inherited classes
 Marking code


Tobago MDA – www.accelerateddeliveryplatform.com


Tobago MDA


Model driven development - Template engines RM

Properties can
be used in
templates
Template engine
knows (part of)
the UML meta
model


Freemarker
Sitemesh
Presentation
DisplayTag

Struts2
Process XWorkActions

Spring
EJB3 Services
EJB3 DataAccessObjects
Data / Services

Spring
JPA Domain objects
Enums
Domain
Value objects
Smart references

Outside world MySQL


Model driven development - Templates


Generate many things e.g. Table create scripts


FAQ
You


FAQ SH

Yes
No
I don’t know
I am not allowed to go
into details about this


Generating code
Demo!


www.accelerateddeliveryplatform.com SH


References and questions
www.accelerateddeliveryplatform.com

sander.hoogendoorn@capgemini.com
r.r.middelkoop@avisi.nl

Twitter: aahoogendoorn LinkedIn: aahoogendoornrodym


Pragmatic Model Driven Development In Java Using Smart Use Cases

Pragmatic Model Driven Development In Java Using Smart Use Cases

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados(15)

Destaque

Destaque(20)

Similar a Pragmatic Model Driven Development In Java Using Smart Use Cases

Similar a Pragmatic Model Driven Development In Java Using Smart Use Cases(20)

Mais de Rody Middelkoop

Mais de Rody Middelkoop(11)

Último

Último(20)

Pragmatic Model Driven Development In Java Using Smart Use Cases