Story Driven Development
-
Upload
tmra -
Category
Technology
-
view
539 -
download
1
description
Transcript of Story Driven Development
1
Story Driven DevelopmentAn invitation to brainstorming
Benjamin Bock, Lutz Maicherhttp://rtm.rubyforge.orgTMRA 2008Leipzig, 2008-10-17
2
TM is about knowledge
• Describtion of Knowledge how it is• „Static“ perspective:
• Does model business knowledge• Does not model business processes
3
Very high level programming
• Allow to describe from a high level perspective
• Use an iterative top-down approach• Each step, get more granular using
• the same domain model• the same subjects
throughout the whole project• Bring behavior and interaction design
closer to humans
4
5
Story Driven Development
• If you ask people what they do, most people tend to tell a story.
• Try to catch the stories, identify them, modelize them
• Use the domain modell throughout
6
Layers of Abstraction
Knowledge
Information
Data
7
Layers of Abstraction
Knowledge
Information
Data
Story
Function Point
Algorithm
8
Similar approaches
• BPMN / BPEL• UML behaviour diagrams• UML interaction diagrams• Others?
9
Ideas?
• Did you do something similar already?
• Which things shouldn’t we miss?
10
kthxbai!
11
kthxbaiVariation of ‘kthxbye’– the internet bastardization of “OK, thank you, goodbye”.
source: http://www.urbandictionary.com/
see also:http://icanhascheezburger.com/
12
13
Grobe Idee:Topic Maps is about Data,
not about processesSame approach abstraction layers
(static) abstraction layers (dynamic) story Function Points algorithm vorgehensmodell? ontology?