
	Where results make sense

Topic: Use case

Related Topics

Requirements analysis

Unified Modeling Language

Unified Process

Domain expert

Class (computer science)

Newbie

Free software

Open source

Software engineering

Coal gas

Error correction

Actor (UML)

Finite state machine

	Use case - Wikipedia, the free encyclopedia
		This is especially the case within the object-oriented community where they originated, but their applicability is not restricted to object-oriented systems, because use cases are not object oriented in nature.
		In this sense, use cases are for exploration, not documentation.
		Use case modeling (including the writing of use case specifications) is generally regarded as an excellent technique for capturing the functional requirements of a system.
	en.wikipedia.org /wiki/Use_case (2242 words)

	Use case diagram - Wikipedia, the free encyclopedia
		Use cases are represented by ovals and the Actors are represented by stick figures.
		This relationship indicates that the behavior of the extension use case may be inserted in the extended use case under some conditions.
		The notation is a dashed arrow from the extension to the extended use case, with the label «extend».
	en.wikipedia.org /wiki/Use_case_diagram (772 words)

	Introduction to System Use Cases
		A use case is a sequence of actions that provide a measurable value to an actor.
		Several advantages exist to this approach: the use case becomes easier to test because each statement is easier to understand and to validate; alternate courses are easier to write because it is easier to branch from a statement when it does one thing only.
		The use case text references several alternate courses, think of them simply as the use case way of doing if/then logic, one of which is described at the bottom of the use case.
	www.agilemodeling.com /artifacts/systemUseCase.htm (2670 words)

	Sparx Systems - UML 2 Tutorial - Use Case Diagram
		The notation for a use case is an ellipse.
		Use Cases may be included by one or more Use Case, helping to reduce the level of duplication of functionality by factoring out common behavior into Use Cases that are re-used many times.
		One Use Case may be used to extend the behavior of another; this is typically used in exceptional circumstances.
	sparxsystems.com.au /resources/uml2_tutorial/uml2_usecasediagram.html (625 words)

	Serlio Software - Use Case Benefits
		Use cases focus on the users of the system, not the system itself, thus the real system needs are brought to light early on.
		Each use case describes one way the system is used, but one of the big benefits of use case modeling is that it also describes all of the things that might go wrong.
		Finally, once a use case model has been developed, it can be used to drive many other aspects of software development, including project planning (cost, complexity and timing estimates), object models, test case definitions, and user documentation.
	www.serlio.com /casecomplete/UseCaseBenefits.aspx (360 words)

	Identifying Requirements Through Use Cases
		Use cases provide a way to decide what features are necessary, as opposed to building in specific features and hoping they let the users get their work done.
		One approach is to use the concept of "threads" to design and implement use cases incrementally, building new classes or modules as needed to support the functionality associated with new use cases.
		The use case approach is an efficient and effective technique for collecting essential requirements from a group of customers, helping to focus on their real needs, not just what they initially say they want.
	www.processimpact.com /articles/usecase.html (2341 words)

	Structuring use cases with goals - AC
		A use case is a collection of possible sequences of interactions between the system under discussion and its external actors, related to a particular goal.
		Thus the entire use case may be inserted into higher level scenarios in the same fashion - as a success line and as a failure line (and as a partial success line, if that is a separate case).
		A useful sequence is to have the highest level use cases be strategic, summary goals, which decompose to system, summary goals, which decompose to system-level, user goals, which reference system-level subfunctions (see Figure 8).
	alistair.cockburn.us /index.php/Structuring_use_cases_with_goals (7257 words)

	Visual Case - UML Tutorial - Use Case Diagram
		On a use case diagram, associations are drawn between actors and use cases to show that an actor carries out a use case.
		Use cases that generalize another use case should only specify an alternative, even exceptional, scenario to the use case being generalized.
		Your use case diagrams can be as simple or complex as you wish, however simpler, less cluttered diagrams are easier to understand, and are often more powerful in capturing the tasks of the system.
	www.visualcase.com /tutorials/use-case-diagram.htm (846 words)

	What is use case? - a definition from Whatis.com
		The use case is made up of a set of possible sequences of interactions between systems and users in a particular environment and related to a particular goal.
		A use case can be thought of as a collection of possible scenarios related to a particular goal, indeed, the use case and goal are sometimes considered to be synonymous.
		Use cases can be employed during several stages of software development, such as planning system requirements, validating design, testing software, and creating an outline for online help and user manuals.
	searchwinit.techtarget.com /sDefinition/0,,sid1_gci334062,00.html (306 words)

	DotnetCoders - UML : Use Case Diagrams
		Use Case diagrams identify the functionality provided by the system (use cases), the users who interact with the system (actors), and the association between the users and the functionality.
		Use Cases are used in the Analysis phase of software development to articulate the high-level requirements of the system.
		Behind each Use Case is a series of actions to achieve the proper functionality, as well as alternate paths for instances where validation fails, or errors occur.
	www.dotnetcoders.com /web/learning/uml/diagrams/usecase.aspx (517 words)

	Introduction to Essential (Abstract) Use Cases
		A fully documented essential use case is a structured narrative, expressed in the language of the application domain and of users, comprising a simplified, abstract, technology-free and implementation-independent description of one task or interaction.
		An essential use case is complete, meaningful, and well designed from the point-of-view of users in some role or roles in relation to a system and that embodies the purpose or intentions underlying the interaction.
		Essential use cases are typically written in two column format, the column on the left indicates the intention of the user/actor and the column on the right the system's responsibility to hopefully respond.
	www.agilemodeling.com /artifacts/essentialUseCase.htm (1163 words)

	Use Case
		The use case diagrams describe system functionality as a set of tasks that the system must carry out and actors who interact with the system to complete the tasks.
		Often, it is useful to look at the set of use cases that an actor has access to -- this defines the actor's overall role in the system.
		The use case that is extended is always referred to as the base use case and has one or more defined extension points.
	www.visualcase.com /kbase/use_case.htm (430 words)

	ReadySET Pro: Use Case Tutorial
		One goal of writing use cases is to specify the system to be built, so that the resulting specification can be handed off to someone else for implementation.
		A use case suite is an organized table of contents for your use cases: it simply lists the names of all use cases that you intend to write.
		One particularly good use case suite organization is to use a grid where the rows are classes of users and the columns are business objects.
	readysetpro.com /whitepapers/usecasetut.html (1521 words)

	Creating Use Case Diagrams
		Use case diagrams define the requirements of the system being modeled and hence are used to write test scripts for the modeled system.
		A use case diagram is quite simple in nature and depicts two types of elements: one representing the business roles and the other representing the business processes.
		Use case: A use case in a use case diagram is a visual representation of a distinct business functionality in a system.
	www.developer.com /design/article.php/2109801 (1347 words)

	Use Case
		Not only is the Use Case a valuable technique for developing requirements, but it is also used as the basis for building prototypes, test plans, training requirements, and configuration management.
		Use Cases model and describe sets of sequenced activities, including variations, that a system performs to produce an observable results that are of value to actors in a system.
		Use cases are what the system does to accomplish work by creating, using, and destroying resources.Activities are the verbs used to describe a Use Case or a Scenario and share the same symbol.
	www.ooguru.net /usecase.htm (650 words)

	Use Case Model
		The set of Use Cases an actor has access to defines their overall role in the system and the scope of their action.
		Scenarios are formal descriptions of the flow of events that occurs during a Use Case instance.
		A Use Case may be included by one or more Use Cases, so it helps to reduce duplication of functionality by factoring out common behaviour into Use Cases that are re-used many times.
	pipin.tmd.ns.ac.yu /uml/sparx-tut/use_case_model.htm (951 words)

	Use Case
		Use case is pronounced to rhyme with "deuce case"?
		Use cases are one of many perspectives that help fill this gap.
		Worse, the use cases described a level of detail and an implementation (the user logs on then selects a document and then chooses to view its properties and then...) which were never given as requirements.
	c2.com /cgi/wiki?UseCase (1384 words)

	Amazon.com: Writing Effective Use Cases: Books: Alistair Cockburn (Site not responding. Last check: 2007-10-30)
		Cockburn's approach to use cases will allow you to sidestep not only the more common problems associated with improper use cases, but hundreds more than will crop up unless the value and context of use cases in the development or project life cycle is understood.
		What I found extremely useful, given the complexity of the topic, is that the author presented a number of flexable approaches to developing a use case, stating that the environment and subject matter would determine what details needs to be preserved.
		Use cases are not only a great tool for designers they are a great tool for anybody involved in the development process.
	www.amazon.com /Writing-Effective-Cases-Alistair-Cockburn/dp/0201702258 (2340 words)

	UML Use Case Diagrams: Tips
		Using a UML Use Case Diagram, you can't.
		This is done by realizing that if the use case, or process that you are trying to represent can have two significantly different outcomes (success and failure, for example), then that means that you really have two different use cases: one in which the process succeeds, and one in which the process fails.
		I will say one last time that this use of extension is a bit of a reach, but it is an elegant way to express multiple behaviors of a single use case when the number of such behaviors is small.
	www.andrew.cmu.edu /course/90-754/umlucdfaq.html (2351 words)

	Use Case Alternate Intro (Site not responding. Last check: 2007-10-30)
		This Use Case Fundamentals mini-document was sent by someone who had read the article "Structuring Use Cases with Goals", and wrote a digest of it for his group (thanks, Peter).
		Use cases are goals (use cases and goals are used interchangeably) that are made up of scenarios.
		In addition the level at which the use case is operating at it is important to understand the scope it is addressing.
	members.aol.com /acockburn/papers/AltIntro.htm (1358 words)

	Amazon.com: Use Case Modeling: Books: Kurt Bittner,Ian Spence (Site not responding. Last check: 2007-10-30)
		In the preceding example, use cases reduce theambiguity of the requirements by specifying exactly when and under whatconditions certain behavior occurs; as such, the sequence of the behaviors canbe regarded as a requirement.
		Use cases are a simple yet powerfulway to express the behavior of the system in way that all stakeholders caneasily understand.
		Unlike other use case texts that emphasize use case structure, form, and analytically oriented techniques, this book presents sufficient attention to notational elements and invests significantly more in describing pragmatic activities focused on synthesizing use cases that can be effectively leveraged across the lifecycle.
	www.amazon.com /Use-Case-Modeling-Kurt-Bittner/dp/0201709139 (3096 words)

	Serlio Software - Use Case Training (Site not responding. Last check: 2007-10-30)
		Use case modeling is a technique for capturing requirements in a way that is understandable to both the problem-oriented and solution-oriented stakeholders of a project.
		Use cases are applicable to a wide array of software systems -- from enterprise-wide software to embedded real-time systems.
		The instructor guides the student through a proven process for specifying requirements, creating use cases and supplementatl artifacts for a sample software project.
	www.serlio.com /UseCases.aspx (194 words)

	Artifact: Use-Case Model
		The use-case model is used as an essential input to activities in analysis, design, and test.
		It can be used early in the inception phase to outline the scope of the system, as well as during the elaboration phase.
		An analyst is responsible for the integrity of the use-case model, and ensures that the use-case model as a whole is correct, consistent, and readable.
	www.upedu.org /upedu/process/artifact/ar_ucmod.htm (548 words)

	Basic use case template - AC
		The template has the sections: name (which is the goal), goal in context, scope, level, trigger, pre- and postconditions, main course, extensions, sub-variations, and other characteristic data for the use case.
		You will find that the collection of use cases is easier to work with in something like Lotus Notes than in a word processor.
		Use Case:
	alistair.cockburn.us /usecases/uctempla.htm (1265 words)

	Use Case Zone - How to write Software Requirements
		Welcome to the Use Case Zone - a site dedicated to providing links and information on use cases.
		Use cases are now an important feature of the Unified Modeling Language (UML).
		We also run use case training courses based on the ideas of Alistair Cockburn (because our experience has shown that his ideas work the best in real life).
	www.pols.co.uk /use-case-zone (219 words)

	Optimal Trace - Home
		Compuware Optimal Trace addresses this problem with an innovative approach called “structured requirements.” This approach captures software requirements from the perspective of the user, complete with visual storyboards and traceable relationships to business needs.
		Using structured requirements, IT organizations ensure that they are capturing the right requirements, communicating them effectively and dramatically improving their ability to deliver on the expectations of the business.
		Easy to use for business analysts and other non-technical users, with intuitive flow-charting and easy searching and editing, and access online or off-line
	www.steeltrace.com (297 words)

	Use Case Patterns (Site not responding. Last check: 2007-10-30)
		This site is a continuous work in progress and your comments are always welcomed.
		This web site is intended to encourage the use of and support the development of Use Case patterns by:
		a forum for discussing and critiquing the use case patterns.
	www.usecasepatterns.org (77 words)

	Enterprise Architect - Use Case Model
		Home > Resources > Tutorial > The Use Case Model
		A Use Case is a single unit of meaningful work; for example login to system, register with system and create order are all Use Cases.
		Includes i) pre-conditions that must be true before the use case is run -e.g.
	www.sparxsystems.com.au /resources/tutorial/use_case_model.html (973 words)

	Software Use Case - Compare Prices, Reviews and Buy at NexTag - Price - Review
		related searches:software use,case tool software,targus laptop case tld001us,ladies magenta u.s luggage business cases lightweight computer tote,software,us navy,us robotics,us1925,camera us,discount us appliance,apple store us,panasonic us,us weekly,use monitor,iodine use,us modular,8675-us,8230us,us med,maps of u.s
		Lantern is regulated for superior cold weather performance Push button Piezo ignition Case made of high-impact polyethylene Lantern adjusts from dim to bright Uses 16.4 ounce...
		Type II Uses of Technology in Education: Projects, Case Studies, and Software Appl...
	www.nextag.com /software-use-case/search-html (232 words)

Try your search on: Qwika (all wikis)