Pragmatic agile model driven development using smart use cases

@aahoogendoorn
Sander Hoogendoorn
Principal Technology Officer, Global Agile Thought Leader Capgemini
PRAGMATIC AGILE MODEL DRIVEN DEVELOPMENT USING SMART USE CASES

UML AND SMART USE CASES ©2001 -2014 Sander Hoogendoorn. All Rights Reserved
@aahoogendoorn
2
Sander Hoogendoorn
Me
Dad (3)
Programmer, trainer, coach, architect
Books (3)
Articles (+250)
International conferences (+100)
Capgemini
Principal technology officer
Global design authority agile
Web
www.sanderhoogendoorn.com
www.smartusecase.com
www.speedbird9.com
@aahoogendoorn

@aahoogendoorn

@aahoogendoorn
4
On being a developer...

@aahoogendoorn
5
Agenda
Agile. How does it work?
Agile requirements and modeling?
The backlog. Where does it come from?
User stories. An agile requirements anti-pattern
Smart use cases
Different levels of use cases
Standardizing and stereotypes
Estimating smart use cases
The backlog revisited. Where does it come from?
Automating test design
Generating code from agile requirements
In retrospective

@aahoogendoorn
6
Agenda. Demo’s
Agile. How does it work?
Agile requirements and modeling?
The backlog. Where does it come from?
User stories. An agile requirements anti-pattern
Smart use cases
Different levels of use cases
Standardizing and stereotypes
Estimating smart use cases
The backlog revisited. Where does it come from?
Automating test design
Generating code from agile requirements
In retrospective

@aahoogendoorn
AGILE. HOW DOES IT WORK?

@aahoogendoorn
8
Agile. Backlog

@aahoogendoorn
9
Agile. Iterations

@aahoogendoorn
10
Agile. In iteration

@aahoogendoorn
11
Agile. Iteration backlog

@aahoogendoorn
12
Agile. Working in iterations

@aahoogendoorn
13
Agile. New work items

@aahoogendoorn
14
Agile. Remaining work items

@aahoogendoorn
WHAT ABOUT AGILE REQUIREMENTS AND MODELING?

@aahoogendoorn
16
Scrum

@aahoogendoorn
THE BACKLOG. WHERE DOES IT COME FROM?

@aahoogendoorn
AND ON THE SEVENTH DAY KEN CREATED THE BACKLOG

@aahoogendoorn
19
The automagical backlog

@aahoogendoorn
20
The automagical backlog

@aahoogendoorn
21
Agile. Where does the backlog come from?

@aahoogendoorn
22
Preliminary iterations

@aahoogendoorn
23
Preliminary iterations

@aahoogendoorn
24
SmartCreateproject proposalWriteproject planDeliverworkingsoftwareStabilizesoftware

@aahoogendoorn
An agile requirements anti-pattern
USER STORIES

@aahoogendoorn
26
User stories

@aahoogendoorn
27
User stories. The approach

@aahoogendoorn
28
User stories in complex system landscapes
Often too unstructured
Unsuitable in complex environments

@aahoogendoorn
Part I. From scope to smart use cases
SMART USE CASES

@aahoogendoorn
30
Levels of requirements

@aahoogendoorn
31
Agile requirements. Approach
D
E
F
SmartUse Cases
A
ProjectScope
D
Use Cases
A
B
C
HierarchicalProcesses
B
D
D
HierarchicalProcesses
ChronologicalProcesses
Cloud Level
Kite Level
Sea Level
Fish Level
C

@aahoogendoorn
32
Identifying scope at cloud level

@aahoogendoorn
33
Cloud level

@aahoogendoorn
34
Kite level

@aahoogendoorn
35
Modeling smart use cases. Sea and fish level

@aahoogendoorn
Modeling at different levels of granularity
SMART USE CASES

@aahoogendoorn
37
Different levels of use cases
User goal
Sub function

@aahoogendoorn
38
Different levels of use cases
Traditionaluse cases
Smartuse cases
Format
Textual
Visual
Granularity
Different
Unified
Estimate
Hard
Easy
Unit of work
Lousy
Good
Reuse
Incidental
Normal
Traceability
Possible
Normal
Testability
Poor
Good

@aahoogendoorn
39
Identifying sub-function level use cases
Guidelines for identifying sub-function level use cases
Identify re-use
Model one form per use case
Model one use case per functional web part
Isolate unknown functionality
Identify complex functionality
Show reporting
Model complex calculations
Isolate interaction with others
Avoid low level (database) interaction

@aahoogendoorn
41
Smart use cases. Stereotyped

@aahoogendoorn
42
Smart use cases. Service orientation

@aahoogendoorn
43
Identifying reuse

@aahoogendoorn
Thinking in stereotypes
SMART USE CASES

@aahoogendoorn
45
Smart use case stereotypes

@aahoogendoorn
Using www.speedbird9.com
DEMO THE BACKLOG REVISITED. WHERE DOES IT COME FROM?

@aahoogendoorn
47
Filling the backlog (www.speedbird9.com)

@aahoogendoorn
48
www.speedbird9.com

@aahoogendoorn
ESTIMATING SMART USE CASES

@aahoogendoorn
50
Estimating smart use cases

@aahoogendoorn
51
Estimating smart use cases
4
3
2
3
8
4
3
3

@aahoogendoorn
52
Standardizing estimation
Estimating smart use caseswhile modeling

@aahoogendoorn
Using Enterprise Architect, Tobago MDA
DEMO GENERATINGYOUR ESTIMATES

@aahoogendoorn
Part II. Implementing smart use cases
SMART USE CASES

@aahoogendoorn
55
The smart use case life cycleDefine work on use caseWritetest casesGenerateand builduse caseRuntest casesAdjustuse caseDescribeuse caseAcceptuse case

@aahoogendoorn
56
Analysis & Design. Writing use cases

@aahoogendoorn
57
Test Design. Test scenarios for smart use cases

@aahoogendoorn
58
Test Design. Testing smart use cases

@aahoogendoorn
59
Test Design. Test cases for smart use cases

@aahoogendoorn
Using Sparx’ Enterprise Architect
DEMO AUTOMATING SMART USE CASE TEST DESIGN

@aahoogendoorn
62
Writing smart use cases. Using Enterprise Architect

@aahoogendoorn
63
Writing smart use cases. Using Enterprise ArchitectAlternative flowsException flowsBasic flow

@aahoogendoorn
64
Writing smart use cases. Using Enterprise ArchitectFields on formwith smart use casesSmart use casespecific business rulesand validations

@aahoogendoorn
65
Test scenarios for a smart use case

@aahoogendoorn
66
Testing a smart use case. Using Enterprise Architect

@aahoogendoorn
CAN WE GENERATE CODE FROM (AGILE) REQUIREMENTS?

@aahoogendoorn
68
Can we generate code from (agile) requirements?
Why generate code?
Higher productivity?
Higher quality?
Get rid of repetitive work?
Prototyping?
Prerequisites to generating code
Standardize, standardize, standardize
A decent and pragmatic model
A simple code generator
A straightforward templating language
Templates!
Clear and present software architecture
Frameworks to back up your software architecture

@aahoogendoorn
Presentation
Process
Domain
Data / Services
Outside world
PagesUserControlsPanels
Use casesWorkflow
Domain objects / Entities
Factories / Repositories
Enums / Value objects / Smart references
Data / Service gateways
Service locators
[Mapping]
DatabasesServices / ESB
Exact
SAP
BizTalk
Java

@aahoogendoorn
70
Using Tobago MDA

@aahoogendoorn
71
Model driven development -Templates

@aahoogendoorn
Forms
Use cases
Domain
objects
Data / Serviceclasses
Databases
Software Architecture
TobagoMDA
Testscenario’s
Frameworks
Specifications
ExistingApplications
Businessmodels
DomainModel
Smartuse cases
User interfacespecification1. Mapbusiness processes to smart use cases2. Set up domain model3. Refinesoftware architecture(s) 4. Generate code using a text template engine5. Finalize application

@aahoogendoorn
73
Generated code in ASP.NET

@aahoogendoorn
74
Generated code Windows 8

@aahoogendoorn
75
Generating code. Twitter Bootstrap & JSF

@aahoogendoorn
Using Enterprise Architect, Tobago MDA, Visual Studio 2013
DEMO GENERATING CODE FROM SMART USE CASES

@aahoogendoorn
IN RETROSPECTIVE?

@aahoogendoorn
www.sanderhoogendoorn.comwww.smartusecase.comwww.speedbird9.com
sander@ditisagile.nl
@aahoogendoorn
REFERENCES AND QUESTIONS

Pragmatic agile model driven development using smart use cases

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Andere mochten auch

Andere mochten auch (7)

Ähnlich wie Pragmatic agile model driven development using smart use cases

Ähnlich wie Pragmatic agile model driven development using smart use cases (20)

Mehr von Sander Hoogendoorn

Mehr von Sander Hoogendoorn (17)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Pragmatic agile model driven development using smart use cases