Talk:Use-case analysis
![]() | This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||
Please add the quality rating to the {{WikiProject banner shell}} template instead of this project banner. See WP:PIQA for details.
Please add the quality rating to the {{WikiProject banner shell}} template instead of this project banner. See WP:PIQA for details.
|
Wikiproject assessment
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)
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 merges with Use-case analysis. --MadScientistX11 (talk) 03:31, 12 December 2013 (UTC)
- All unassessed articles
- Stub-Class Computing articles
- Low-importance Computing articles
- Stub-Class software articles
- Unknown-importance software articles
- Stub-Class software articles of Unknown-importance
- All Software articles
- All Computing articles
- Stub-Class Systems articles
- Mid-importance Systems articles
- Systems articles in software engineering
- WikiProject Systems articles