Story-driven modeling: Difference between revisions

Content deleted Content added
Monkbot (talk | contribs)
m Summary: spelling
Line 57:
Story driven modeling has proven to work very well for the cooperation with non IT experts.<ref>{{cite journal|last=Zündorf|first=Albert|author2=J. Leohold |author3=D. Müller |author4=R. Gemmerich |author5=C. Reckord |author6=C. Schneider |author7=S. 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 VictoraVictoria, ...
 
Story driven modeling is supported by various tools, e.g.