Content deleted Content added
m →See also: cap |
Citation bot (talk | contribs) Alter: title, template type. Added chapter. Removed parameters. | Use this bot. Report bugs. | Suggested by Headbomb | Linked from Wikipedia:WikiProject_Academic_Journals/Journals_cited_by_Wikipedia/Sandbox2 | #UCB_webform_linked 189/217 |
||
(11 intermediate revisions by 8 users not shown) | |||
Line 1:
{{Multiple issues|{{more footnotes|date=February 2014}}{{essay-like|date=February 2014}}}}
'''Story-driven modeling'''<ref name=SDMBook>{{cite book|
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|
may be represented as [[object diagram]]s and how these object diagrams evolve during scenario execution.
==
Story-driven modeling proposes the following software development approach:
Line 55:
== Summary ==
Story driven modeling has proven to work very well for the cooperation with non IT experts.<ref>{{cite journal|
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, ...
== See also ==
* [[Agile modeling]]
* [[Entity–control–boundary]]
* [[Agile software development]]
* [[Class-responsibility-collaboration card]]
|