Talk:Use-case analysis

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software.

Systems Mid‑importance

	Systems science portal This article is within the scope of WikiProject Systems, which collaborates on articles related to systems and systems science.SystemsWikipedia:WikiProject SystemsTemplate:WikiProject SystemsSystems articles
Mid	This article has been rated as Mid-importance on the project's importance scale.
	This article is within the field of Software engineering.

Wikiproject assessment[edit]

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.

Ghaag (talk) 05:00, 18 March 2009 (UTC)[reply]

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[edit]

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)[reply]

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)[reply]

Use-case or use case?[edit]

Why is different spelling being used throughout the article? I didn't want to go ahead and edit anything, since it's unclear to me which spelling would be the right one... — Preceding unsigned comment added by 193.3.234.5 (talk) 13:00, 19 January 2018 (UTC)[reply]

Update the Scenario[edit]

Who shops at a store to rent a video these days? Please update the scenario. — Preceding unsigned comment added by 173.20.158.184 (talk) 00:43, 31 January 2018 (UTC)[reply]