CSC/ECE 517 Summer 2008/wiki2 4 uc: Difference between revisions
No edit summary |
|||
| (30 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=Use Cases= | =Use Cases= | ||
This page provides a review of the Use Case sites on the web. | This page provides a review of the [http://en.wikipedia.org/wiki/Use_case Use Case] sites on the web. After an introductory discussion of Use Cases, including their purpose, applications, and techniques for their use, links to some of the best web sites for learning about Use cases are discussed, including the sites with the most instructive examples, and those teaching advanced concepts that might not be apparent from a quick search of the web. | ||
=Overview= | =Overview= | ||
Use Cases are a modeling aid used in software design to describe a sequence of events in a way that both the end users of a system, and the system designers and developers, can each understand completely. Use cases typically describe an event initiated by either a human user or another application, however the event and response are usually external, to maintain separation of responsibility between the designer and the user. The users should not have to be concerned about thread synchronization, for example, and the users should not need to care how the feature will be implemented. By communicating in a common language, end users may indicate what they require from the system, and designers may understand how those externaly visible requirements from the users translate into derived requirements internal to the system, in modules and subsystems not necessarily visible to the users. Most Use Cases simply describe a flow of events from input, or request, to output, or response. A typical use case for purchasing a ticket could be described by a user as follows: | |||
*# Customer requests ticket | |||
*# Agent determines if space is available and informs customer | |||
*# Customer purchases ticket, or declines price offered | |||
*# Agent accepts payment and delivers ticket, or terminates | |||
*# Customer terminates | |||
Even an example as simple as the one shown above can help designers understand the implications, in terms of the system design, so that the system will satisfy the requirements. For example, there are multiple potential exception processing points in this use case; the Agent could determine there is no ticket available, or the price offered may be more than the Customer wants to pay. The Customer may decide not to purchase a ticket for any reason. Both the Customer and Agent will have to be designed to handle these exception cases. After satisfactorily working through the use case with the user, the designer will understand the user expects to be able to refuse to purchase the ticket, and the designer can then flow that requirement into the system internals. | |||
Just as use cases help to identify Actors, Roles, and resources, they also help expose internal state and corner cases that designers may miss without this valuable input from the users. In addition, a well developed set of use cases can help designers make the system more robust, by enforcing restrictions on what users are allowed to do at certain points (for example, not allowing a subsequent missile launch, until the user presses a button on the firing panel indicating the previous launch was successful). | |||
= | =History= | ||
Use Cases were initially developed in the late 1960s by [http://en.wikipedia.org/wiki/Ivar_Jacobson Ivar Jacobsen]. [http://www.ivarjacobson.com/resources.cfm Jacobsen continues to develop] use case theory and applications to the present day, hosting many presentations and research articles on his [http://www.ivarjacobson.com/ website] (most of the documents require a free registration by email address, however it should be well worth the cost to learn about use cases from the inventor). Wikipedia has a good writeup on [http://en.wikipedia.org/wiki/Ivar_Jacobson Jacobson's] contributions. | |||
[http://alistair.cockburn.us/ Alistair Cockburn] is another important authority in use case theory and application; on his web site he describes the [http://alistair.cockburn.us/index.php/Use_cases%2C_ten_years_later history of use cases], from before they were invented, until the present day, and hosts many [http://alistair.cockburn.us/index.php/Resources_for_writing_use_cases resources for use cases] from his site. | |||
Another heavy hitter on use cases from the software development community is [http://c2.com/cgi/wiki?UseCases Ward Cunningham], the inventor of the wiki. Ward Cunningham has a page linked from his site that describes [http://c2.com/cgi/wiki?UserStories User Stories], which are different from use cases. [http://c2.com/ Ward's main site] is full of valuable information from one of the pioneers of software development. | |||
= | =Review of Use Case sites on the Web= | ||
Because many sites related to use cases exist on the web, we want to categorize some of the best sites here, to help someone wanting to learn about use cases find the most relevant information. | |||
http://www.developer.com/design/article.php/2109801 | ==Introductory Sites on Use Cases== | ||
[http://www.developer.com/design/article.php/2109801 developer.com] has a practical overview of Use Case Diagrams and how they are used to represent use cases. Wikipedia of course has many useful pages related to use cases, including [http://en.wikipedia.org/wiki/Activity_diagrams Activity Diagrams]. A very good place to begin learning about use cases is Alistair Cockburn's page on [http://alistair.cockburn.us/index.php/Use_case_fundamentals Use case fundamentals]. | |||
http://www. | ==How Use Cases Fit Into Development Processes== | ||
If you want to understand the relationship between use cases and UML, this site shows [http://en.wikipedia.org/wiki/Unified_Modeling_Language#Modeling how use cases fit into the Unified Modeling Language]. Use case application to the Essential Unified Process is described on this [http://en.wikipedia.org/wiki/Essential_Unified_Process site]. The site http://www.agilemodeling.com/ has, in addition to plenty of information about agile methods, a page on [http://www.agilemodeling.com/artifacts/systemUseCase.htm use cases within agile processes]. | |||
http://www. | ==Use Case Tutorials== | ||
Among the many use case tutorials on the web, some of the more useful to this reviewer are [http://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/use_case.htm Kennesaw State University's Object Oriented Analysis and Design page], and [http://www.andrew.cmu.edu/course/90-754/umlucdfaq.html this page at Carnegie Mellon]. In addition, this page from [http://faculty.washington.edu/jtenenbg/courses/360/f02/project/usecaseguidelines.html University of Washington] presents some of Alistair Cockburn's use case wisdom in a tutorial format. | |||
http://www. | For those just getting started, here is what the US Government has to say about [http://www.usability.gov/methods/usecases.html capturing user requirements with use cases]. | ||
http:// | ==Advanced Use Case Topics== | ||
This paper from [http://msdn.microsoft.com/en-us/library/cc194881.aspx Microsoft] presents some of the finer points of use case application, showing how designers can make a system more reliable by understanding how users can get into trouble, and yet avoiding disaster. | |||
http:// | For some striking accounts of how use cases can really matter to the utmost, enter the world of [http://en.wikipedia.org/wiki/Embedded_System embedded systems]. This article begins the discussion of what can go wrong [http://embedded.com/98/9805br.htm when use cases are ignored], including the failure of the [http://en.wikipedia.org/wiki/Patriot_Missile#Failure_at_Dhahran Patriot missile], where designers did not expect the control system to remain running for more than a few hours. Another disaster described in the article the case of the [http://en.wikipedia.org/wiki/Therac-25 Therac-25], a medical treatment device that, due to the failure of the designers to guarantee certain use case outcomes, allowed operators to deliver fatal doses of radiation to patients. | ||
==Sites of the Major Players in Use Case Theory and Application== | |||
Ivar Jacobson, Alistair Cockburn, and Andy Pols are all big names in the Use Case world, and their sites host many papers, articles, and links to more information on introductory and advanced topics. | |||
http://www. | Ivar Jacobson has many interesting papers on use cases, however these stand out as especially useful (free email registration required): | ||
[http://www.ivarjacobson.com/resources/module/publications_action-download/file_id-172/ Agile Requirements with Use Cases] | |||
http:// | [http://www.ivarjacobson.com/resources/module/publications_action-download/file_id-167/ Use Case Essentials - More Than Just Requirements] | ||
http://www. | [http://www.ivarjacobson.com/resources/module/publications_action-download/file_id-171/ Use Cases and Architecture] | ||
Alistair Cockburn also provides much useful material for those interested in learning about use cases: | |||
http:// | [http://alistair.cockburn.us/index.php/Writing_Effective_Use_Cases_course Writing Use Cases Course] | ||
http:// | [http://alistair.cockburn.us/index.php/Resources_for_writing_use_cases Resources for Writing Use Cases] | ||
http:// | [http://alistair.cockburn.us/index.php/Basic_use_case_template Use Case Template] | ||
http:// | [http://alistair.cockburn.us/index.php/Use_case_fundamentals Use Case Fundamentals] | ||
http://alistair.cockburn.us/index.php/ | [http://alistair.cockburn.us/index.php/Resources_for_writing_use_cases#Articles_online Articles Online] | ||
http:// | [http://alistair.cockburn.us/index.php/Resources_for_writing_use_cases#Presentations_online Presentations Online] | ||
http:// | [http://alistair.cockburn.us/images/Usecasesintheoryandpractice180.ppt Use Cases in Theory and Practice] | ||
http:// | [http://alistair.cockburn.us/index.php/Resources_for_writing_use_cases#Other_sites_with_information_about_use_cases Other Sites With Information About Use Cases] | ||
http://www. | Another big player in use case application and theory is [http://www.pols.co.uk/ Andy Pols], who maintains a resource site known as the [http://www.pols.co.uk/use-case-zone Use Case Zone], hosting many [http://www.pols.co.uk/use-case-zone/use-case-papers use case papers]. | ||
=Summary= | |||
Use cases are one of the most effective tools a designer can employ to bridge the gap between technical know-how of the developer and the domain knowledge of the user's requirements and expectations. The web has plenty of resources on Use Cases, and this page should provide a good starting point for learning about them. | |||
Latest revision as of 01:13, 1 July 2008
Use Cases
This page provides a review of the Use Case sites on the web. After an introductory discussion of Use Cases, including their purpose, applications, and techniques for their use, links to some of the best web sites for learning about Use cases are discussed, including the sites with the most instructive examples, and those teaching advanced concepts that might not be apparent from a quick search of the web.
Overview
Use Cases are a modeling aid used in software design to describe a sequence of events in a way that both the end users of a system, and the system designers and developers, can each understand completely. Use cases typically describe an event initiated by either a human user or another application, however the event and response are usually external, to maintain separation of responsibility between the designer and the user. The users should not have to be concerned about thread synchronization, for example, and the users should not need to care how the feature will be implemented. By communicating in a common language, end users may indicate what they require from the system, and designers may understand how those externaly visible requirements from the users translate into derived requirements internal to the system, in modules and subsystems not necessarily visible to the users. Most Use Cases simply describe a flow of events from input, or request, to output, or response. A typical use case for purchasing a ticket could be described by a user as follows:
- Customer requests ticket
- Agent determines if space is available and informs customer
- Customer purchases ticket, or declines price offered
- Agent accepts payment and delivers ticket, or terminates
- Customer terminates
Even an example as simple as the one shown above can help designers understand the implications, in terms of the system design, so that the system will satisfy the requirements. For example, there are multiple potential exception processing points in this use case; the Agent could determine there is no ticket available, or the price offered may be more than the Customer wants to pay. The Customer may decide not to purchase a ticket for any reason. Both the Customer and Agent will have to be designed to handle these exception cases. After satisfactorily working through the use case with the user, the designer will understand the user expects to be able to refuse to purchase the ticket, and the designer can then flow that requirement into the system internals.
Just as use cases help to identify Actors, Roles, and resources, they also help expose internal state and corner cases that designers may miss without this valuable input from the users. In addition, a well developed set of use cases can help designers make the system more robust, by enforcing restrictions on what users are allowed to do at certain points (for example, not allowing a subsequent missile launch, until the user presses a button on the firing panel indicating the previous launch was successful).
History
Use Cases were initially developed in the late 1960s by Ivar Jacobsen. Jacobsen continues to develop use case theory and applications to the present day, hosting many presentations and research articles on his website (most of the documents require a free registration by email address, however it should be well worth the cost to learn about use cases from the inventor). Wikipedia has a good writeup on Jacobson's contributions.
Alistair Cockburn is another important authority in use case theory and application; on his web site he describes the history of use cases, from before they were invented, until the present day, and hosts many resources for use cases from his site.
Another heavy hitter on use cases from the software development community is Ward Cunningham, the inventor of the wiki. Ward Cunningham has a page linked from his site that describes User Stories, which are different from use cases. Ward's main site is full of valuable information from one of the pioneers of software development.
Review of Use Case sites on the Web
Because many sites related to use cases exist on the web, we want to categorize some of the best sites here, to help someone wanting to learn about use cases find the most relevant information.
Introductory Sites on Use Cases
developer.com has a practical overview of Use Case Diagrams and how they are used to represent use cases. Wikipedia of course has many useful pages related to use cases, including Activity Diagrams. A very good place to begin learning about use cases is Alistair Cockburn's page on Use case fundamentals.
How Use Cases Fit Into Development Processes
If you want to understand the relationship between use cases and UML, this site shows how use cases fit into the Unified Modeling Language. Use case application to the Essential Unified Process is described on this site. The site http://www.agilemodeling.com/ has, in addition to plenty of information about agile methods, a page on use cases within agile processes.
Use Case Tutorials
Among the many use case tutorials on the web, some of the more useful to this reviewer are Kennesaw State University's Object Oriented Analysis and Design page, and this page at Carnegie Mellon. In addition, this page from University of Washington presents some of Alistair Cockburn's use case wisdom in a tutorial format.
For those just getting started, here is what the US Government has to say about capturing user requirements with use cases.
Advanced Use Case Topics
This paper from Microsoft presents some of the finer points of use case application, showing how designers can make a system more reliable by understanding how users can get into trouble, and yet avoiding disaster.
For some striking accounts of how use cases can really matter to the utmost, enter the world of embedded systems. This article begins the discussion of what can go wrong when use cases are ignored, including the failure of the Patriot missile, where designers did not expect the control system to remain running for more than a few hours. Another disaster described in the article the case of the Therac-25, a medical treatment device that, due to the failure of the designers to guarantee certain use case outcomes, allowed operators to deliver fatal doses of radiation to patients.
Sites of the Major Players in Use Case Theory and Application
Ivar Jacobson, Alistair Cockburn, and Andy Pols are all big names in the Use Case world, and their sites host many papers, articles, and links to more information on introductory and advanced topics.
Ivar Jacobson has many interesting papers on use cases, however these stand out as especially useful (free email registration required):
Agile Requirements with Use Cases
Use Case Essentials - More Than Just Requirements
Use Cases and Architecture
Alistair Cockburn also provides much useful material for those interested in learning about use cases:
Writing Use Cases Course
Resources for Writing Use Cases
Use Case Template
Use Case Fundamentals
Articles Online
Presentations Online
Use Cases in Theory and Practice
Other Sites With Information About Use Cases
Another big player in use case application and theory is Andy Pols, who maintains a resource site known as the Use Case Zone, hosting many use case papers.
Summary
Use cases are one of the most effective tools a designer can employ to bridge the gap between technical know-how of the developer and the domain knowledge of the user's requirements and expectations. The web has plenty of resources on Use Cases, and this page should provide a good starting point for learning about them.