Story-driven modeling: Difference between revisions

Revision as of 07:18, 9 January 2014

Revision as of 10:55, 30 January 2014

Line 1:

{{Merge to|Use-case_analysis|discuss=Talk:Use-case_analysis#Proposal: Merge with Story-driven modeling|date=December 2013}}Story-driven modeling<ref name=SDMBook>{{cite book|last=Norbisrath Zündorf Jubeh|first=Ulrich Albert Ruben|title=Story Driven Modeling|year=2013|publisher=Amazon Createspace|isbn=9781483949253|pages=333|url=http://www.amazon.de/Story-Driven-Modeling-Ulrich-Norbisrath/dp/1483949257}}</ref><ref name=ZSW99>{{cite journal|last=Zündorf|first=Albert|coauthors=A. Schürr, A. J. 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|last=Diethelm|first=Ira|coauthors=L. Geiger, A. Zündorf|title=Systematic story driven modeling: a case study|journal=Third International Workshop on Scenarios and State Machines|yeardate=January 2004|month=January|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|last=Eickhoff|first=Christoph|coauthors=N. Geiger, M. Hahn, A. 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.