Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a228f884ff5b4e12

Jump to content

Talk:Use-case analysis

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 1 year ago by Trdta4 in topic merging with use case article

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 (talkcontribs) 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

merging with use case article

[edit]

while updating this article in an effort to improve understandability and expand to the systems engineering realm, I realized most of the information is described in the Use case article. I therefore plan to merge the articles. Would appreciate any feedback.

Trdta4 (talk) 08:53, 26 May 2025 (UTC)Reply