Story-driven modeling: Difference between revisions

Revision as of 22:33, 31 August 2013

Revision as of 22:34, 31 August 2013

Line 1:

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|year=2004|month=January|pages=65–70}}</ref> is an improvement of [[Object-oriented modeling]] techniques.<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> [[Object-oriented modeling]] focuses 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.

Line 27:

#*Step 2: Putri brings salad for 9$. Peter adds this item, too. The app shows that by now the average share is 7$ and that Peng still have to bring these 7$ while Peter gets 5$ out and Putri gets 2$ out: <br/>[[File:WikipediaGoDutchMockup.png|WikipediaGoDutchMockup]][[File:WikepediaObjectDiagramGoDutchBarbeque.png|Object diagram modeling a go-Dutch barbecue]]

#*Step 3: ...

# '''Class diagram derivation''': Now it is fairly straight forward to derive a [[class diagram]] from the object diagrams used in the storyboards. <br/>[[File:WikipediaGoDutchClassDiag.png|Class diagram for a go-Dutch barbecue]]<br/>Note, the class diagram serves as a common reference for all object diagrams. This ensures that overall the same types and attributes are used. Using a [[Unified Modeling Language|UML]] tool, you may generate a first implementation from this class diagram.

# '''Algorithm design''': So far you have modeled and implemented that object structures that are deployed in your application. Now you need to add behavior, i.e. algorithms and method bodies. Programming the behavior of an application is a demanding task. To facilitate it, you should first outline the behavior in [[pseudocode]] notation. You might do this, e.g. with an object game. For example, to update the saldo attributes of all persons you look at our object structure and from the point of view of the GroupAccount object you do the following:

#: Update the saldo of all persons: