|This article is of interest to the following WikiProjects:|
I assessed this article based on 4+1 Architectural View Model since both techniques share enough similarities to be comparable in ends if not means.
The content of this entry has almost nothing to do with use case analysis. Instead of discussing how to produce use case models while performing requirements identification, this article instead talks about a way to create a more-or-less object-oriented design. This article needs to be totally rewritten so that it actually covers use case analysis. Donald Firesmith 30 October 2010
Proposal: Merge with Story-driven modeling
There is an article on Story-driven modeling In my experience story cards and use cases are the same things and from the current article on SDM it sounds like use cases to me. I propose that article be merged with Use-case analysis. --MadScientistX11 (talk) 03:31, 12 December 2013 (UTC)
Oppose SDM and Use-case analysis are not the same and should not be mixed or merged. Use-case analysis is a pretty informal step in e.g. the Rational Unified Process RUP. SDM is a much more technical approach that targets object oriented models. SDM uses a different kind of scenarios that is much more detailed and a different kind of derivation step to come up with an object model. Actually, the SDM people hate use cases and they hate to be mixed with them. Well, perhaps the two articles should refer to each other and discuss the distincion. A merge is like comparing apples and oranges. — Preceding unsigned comment added by Azuendorf (talk • contribs) 15:07, 12 January 2014 (UTC)