Content deleted Content added
→Summary: rmv - link spam, promotional namedropping without textual context |
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 |
||
(7 intermediate revisions by 6 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|last1=Norbisrath|last2=Zündorf|last3=Jubeh|first1=Ulrich|first2=Albert|first3=Ruben|title=Story Driven Modeling|year=2013
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 8:
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 61:
== See also ==
* [[Agile modeling]]
* [[Entity–control–boundary]]
* [[Agile software development]]
* [[Class-responsibility-collaboration card]]
|