CSC/ECE 517 Fall 2007/wiki2 4 dj: Difference between revisions
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
==='''Likes'''=== | ==='''Likes'''=== | ||
Provides good basic understanding | Provides good basic understanding<br> | ||
Also provides Use case templates | Also provides Use case templates<br> | ||
Discusses benefits and limitations of use cases. | Discusses benefits and limitations of use cases.<br> | ||
Provides good references and External links. | Provides good references and External links.<br> | ||
==='''Drawbacks'''=== | ==='''Drawbacks'''=== | ||
Information maybe incorrect/ old | Information maybe incorrect/ old<br> | ||
No examples are provided to ease learning. | No examples are provided to ease learning.<br> | ||
==='''Review'''=== | ==='''Review'''=== | ||
| Line 20: | Line 20: | ||
==='''Likes'''=== | ==='''Likes'''=== | ||
Written by Alistair Cockburn. The author of Jolt Productivity Award winning book Writing Effective Use Cases. | Written by Alistair Cockburn. The author of Jolt Productivity Award winning book Writing Effective Use Cases.<br> | ||
Provides a more detailed yet practical view of Use Case usage. | Provides a more detailed yet practical view of Use Case usage.<br> | ||
Describes scenarios and howto control Scenario explosion | Describes scenarios and howto control Scenario explosion<br> | ||
Also talks about cases where goal-phrase structure can be used | Also talks about cases where goal-phrase structure can be used<br> | ||
Identifies shortcomings of Use Case | Identifies shortcomings of Use Case<br> | ||
==='''Drawbacks'''=== | ==='''Drawbacks'''=== | ||
Maybe too much information for some people. | Maybe too much information for some people.<br> | ||
Text is difficult to understand and read. | Text is difficult to understand and read.<br> | ||
Text is not formatted, to make it visually appealing | Text is not formatted, to make it visually appealing<br> | ||
==='''Review'''=== | ==='''Review'''=== | ||
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting. | A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting. | ||
Revision as of 18:37, 23 October 2007
Assignment
Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, what should (s)he do? Look at the first few hits in Google? I expect we can do better than that. Write a review of the use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview.
Use case Wikipedia
Likes
Provides good basic understanding
Also provides Use case templates
Discusses benefits and limitations of use cases.
Provides good references and External links.
Drawbacks
Information maybe incorrect/ old
No examples are provided to ease learning.
Review
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits an limitations. The page also provides references and external links
Structuring use cases with goals – AC
Likes
Written by Alistair Cockburn. The author of Jolt Productivity Award winning book Writing Effective Use Cases.
Provides a more detailed yet practical view of Use Case usage.
Describes scenarios and howto control Scenario explosion
Also talks about cases where goal-phrase structure can be used
Identifies shortcomings of Use Case
Drawbacks
Maybe too much information for some people.
Text is difficult to understand and read.
Text is not formatted, to make it visually appealing
Review
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.