Story-driven modeling: Difference between revisions

Revision as of 13:19, 14 August 2019

Revision as of 16:15, 10 June 2020

Line 1:

{{Multiple issues|{{more footnotes|date=February 2014}}{{essay-like|date=February 2014}}}}

'''Story-driven modeling'''<ref name=SDMBook>{{cite book|lastlast1=Norbisrath |last2=Zündorf |last3=Jubeh|firstfirst1=Ulrich |first2=Albert |first3=Ruben|title=Story Driven Modeling|year=2013|publisher=Amazon Createspace|isbn=9781483949253|pages=333|url=https://www.amazon.de/Story-Driven-Modeling-Ulrich-Norbisrath/dp/1483949257}}</ref><ref name=ZSW99>{{cite journal|lastlast1=Zündorf|firstfirst1=Albert|author2first2=A. |last2=Schürr |author3first3=A. J. |last3=Winter |title=Story Driven Modeling|journal=University of Paderborn|year=1999|volume=Technical Report|issue=tr-ri-99-211}}</ref><ref name=DGZ04>{{cite journal|lastlast1=Diethelm|firstfirst1=Ira|author2first2=L. |last2=Geiger |author3first3=A. |last3=Zündorf |title=Systematic story driven modeling: a case study|journal=Third International Workshop on Scenarios and State Machines|date=January 2004|pages=65–70}}</ref> is an [[object-oriented modeling]] technique.<ref>{{cite journal|last=van Gorp|first=Pieter|title=Evaluation of the Story Driven Modeling Methodology: From Towers to Models|journal=Technical Report University of Antwerp|year=2008}}</ref><ref name=EGHZ12>{{cite journal|lastlast1=Eickhoff|firstfirst1=Christoph|author2first2=N. |last2=Geiger |author3first3=M. |last3=Hahn |author4first4=A. |last4=Zündorf |title=Developing Enterprise Web Applications Using the Story Driven Modeling Approach|journal=Current Trends in Web Engineering|year=2012|series=LNCS|issue=7059|pages=196–210}}</ref> Other forms of object-oriented modeling focus on [[class diagram]]s.

Class diagrams describe the static structure of a program, i.e. the building blocks of a program and how they relate to each other.

Class diagrams also model data structures, but with an emphasis on rather abstract concepts like types and type features.

Instead of abstract static structures, story-driven modeling focuses on concrete example scenarios<ref>{{cite journal|lastlast1=Ryser|firstfirst1=J.|author2first2=M. |last2=Glinz |title=Improving the Quality of Requirements with Scenarios|journal=Proceedings of the Second World Congress on Software Quality. Yokohama|date=2000|pages=55–60}}</ref> and on how the steps of the example scenarios

may be represented as [[object diagram]]s and how these object diagrams evolve during scenario execution.

Line 55:

== Summary ==

Story driven modeling has proven to work very well for the cooperation with non IT experts.<ref>{{cite journal|lastlast1=Zündorf|firstfirst1=Albert|author2first2=J. |last2=Leohold |author3first3=D. |last3=Müller |author4first4=R. |last4=Gemmerich |author5first5=C. |last5=Reckord |author6first6=C. |last6=Schneider |author7first7=S. |last7=Semmelroth |title=Using object scenarios for requirements analysis - an experience report|journal=Modellierung 2006|year=2006|pages=269–278}}</ref> People from other domains usually have difficulties to describe their needs in general terms (i.e. classes) and general rules (pseudocode). Similarly, normal people have problems to understand pseudocode or to judge, whether their needs are properly addressed or not. However, these people know their business very well and with the help of concrete examples and scenarios it is very easy for normal people to spot problematic cases and to judge whether their needs have been addressed properly.

Story Driven Modeling has matured since its beginning in 1997. In 2013 it is used for teaching e.g. in Kassel University, Paderborn University, Tartu University, Antwerp University, Nazarbayev University Astana, Hasso Platner Institute Potsdam, University of Victoria, ...

Line 70:

== See also ==

* [[Agile modeling]]

* [[Entity-control-boundary]]

* [[Agile software development]]

* [[Class-responsibility-collaboration card]]