CINXE.COM

Use case - Wikipedia

<!DOCTYPE html> <html class="client-nojs vector-feature-language-in-header-enabled vector-feature-language-in-main-page-header-disabled vector-feature-page-tools-pinned-disabled vector-feature-toc-pinned-clientpref-1 vector-feature-main-menu-pinned-disabled vector-feature-limited-width-clientpref-1 vector-feature-limited-width-content-enabled vector-feature-custom-font-size-clientpref-1 vector-feature-appearance-pinned-clientpref-1 vector-feature-night-mode-enabled skin-theme-clientpref-day vector-sticky-header-enabled vector-toc-available" lang="en" dir="ltr"> <head> <meta charset="UTF-8"> <title>Use case - Wikipedia</title> <script>(function(){var className="client-js vector-feature-language-in-header-enabled vector-feature-language-in-main-page-header-disabled vector-feature-page-tools-pinned-disabled vector-feature-toc-pinned-clientpref-1 vector-feature-main-menu-pinned-disabled vector-feature-limited-width-clientpref-1 vector-feature-limited-width-content-enabled vector-feature-custom-font-size-clientpref-1 vector-feature-appearance-pinned-clientpref-1 vector-feature-night-mode-enabled skin-theme-clientpref-day vector-sticky-header-enabled vector-toc-available";var cookie=document.cookie.match(/(?:^|; )enwikimwclientpreferences=([^;]+)/);if(cookie){cookie[1].split('%2C').forEach(function(pref){className=className.replace(new RegExp('(^| )'+pref.replace(/-clientpref-\w+$|[^\w-]+/g,'')+'-clientpref-\\w+( |$)'),'$1'+pref+'$2');});}document.documentElement.className=className;}());RLCONF={"wgBreakFrames":false,"wgSeparatorTransformTable":["",""],"wgDigitTransformTable":["",""],"wgDefaultDateFormat":"dmy", "wgMonthNames":["","January","February","March","April","May","June","July","August","September","October","November","December"],"wgRequestId":"f76b744c-309e-4522-85c5-d0a32b4cebd4","wgCanonicalNamespace":"","wgCanonicalSpecialPageName":false,"wgNamespaceNumber":0,"wgPageName":"Use_case","wgTitle":"Use case","wgCurRevisionId":1275966836,"wgRevisionId":1275966836,"wgArticleId":300006,"wgIsArticle":true,"wgIsRedirect":false,"wgAction":"view","wgUserName":null,"wgUserGroups":["*"],"wgCategories":["Use dmy dates from August 2020","Articles with short description","Short description is different from Wikidata","All articles with unsourced statements","Articles with unsourced statements from March 2016","Articles with unsourced statements from October 2013","Articles to be expanded from July 2015","All articles to be expanded","All articles with specifically marked weasel-worded phrases","Articles with specifically marked weasel-worded phrases from March 2022", "Articles with unsourced statements from March 2022","Articles needing additional references from August 2013","All articles needing additional references","Software project management","Software requirements","Unified Modeling Language","Systems Modeling Language","1986 establishments in Sweden","1986 in computing","Swedish inventions","Agile software development","1986 neologisms"],"wgPageViewLanguage":"en","wgPageContentLanguage":"en","wgPageContentModel":"wikitext","wgRelevantPageName":"Use_case","wgRelevantArticleId":300006,"wgIsProbablyEditable":true,"wgRelevantPageIsProbablyEditable":true,"wgRestrictionEdit":[],"wgRestrictionMove":[],"wgNoticeProject":"wikipedia","wgCiteReferencePreviewsActive":false,"wgFlaggedRevsParams":{"tags":{"status":{"levels":1}}},"wgMediaViewerOnClick":true,"wgMediaViewerEnabledByDefault":true,"wgPopupsFlags":0,"wgVisualEditor":{"pageLanguageCode":"en","pageLanguageDir":"ltr","pageVariantFallbacks":"en"},"wgMFDisplayWikibaseDescriptions":{"search":true, "watchlist":true,"tagline":false,"nearby":true},"wgWMESchemaEditAttemptStepOversample":false,"wgWMEPageLength":40000,"wgEditSubmitButtonLabelPublish":true,"wgULSPosition":"interlanguage","wgULSisCompactLinksEnabled":false,"wgVector2022LanguageInHeader":true,"wgULSisLanguageSelectorEmpty":false,"wgWikibaseItemId":"Q613417","wgCheckUserClientHintsHeadersJsApi":["brands","architecture","bitness","fullVersionList","mobile","model","platform","platformVersion"],"GEHomepageSuggestedEditsEnableTopics":true,"wgGETopicsMatchModeEnabled":false,"wgGEStructuredTaskRejectionReasonTextInputEnabled":false,"wgGELevelingUpEnabledForUser":false};RLSTATE={"ext.globalCssJs.user.styles":"ready","site.styles":"ready","user.styles":"ready","ext.globalCssJs.user":"ready","user":"ready","user.options":"loading","ext.cite.styles":"ready","skins.vector.search.codex.styles":"ready","skins.vector.styles":"ready","skins.vector.icons":"ready","jquery.makeCollapsible.styles":"ready","ext.wikimediamessages.styles": "ready","ext.visualEditor.desktopArticleTarget.noscript":"ready","ext.uls.interlanguage":"ready","wikibase.client.init":"ready","ext.wikimediaBadges":"ready"};RLPAGEMODULES=["ext.cite.ux-enhancements","mediawiki.page.media","site","mediawiki.page.ready","jquery.makeCollapsible","mediawiki.toc","skins.vector.js","ext.centralNotice.geoIP","ext.centralNotice.startUp","ext.gadget.ReferenceTooltips","ext.gadget.switcher","ext.urlShortener.toolbar","ext.centralauth.centralautologin","mmv.bootstrap","ext.popups","ext.visualEditor.desktopArticleTarget.init","ext.visualEditor.targetLoader","ext.echo.centralauth","ext.eventLogging","ext.wikimediaEvents","ext.navigationTiming","ext.uls.interface","ext.cx.eventlogging.campaigns","ext.cx.uls.quick.actions","wikibase.client.vector-2022","ext.checkUser.clientHints","ext.growthExperiments.SuggestedEditSession"];</script> <script>(RLQ=window.RLQ||[]).push(function(){mw.loader.impl(function(){return["user.options@12s5i",function($,jQuery,require,module){mw.user.tokens.set({"patrolToken":"+\\","watchToken":"+\\","csrfToken":"+\\"}); }];});});</script> <link rel="stylesheet" href="/w/load.php?lang=en&amp;modules=ext.cite.styles%7Cext.uls.interlanguage%7Cext.visualEditor.desktopArticleTarget.noscript%7Cext.wikimediaBadges%7Cext.wikimediamessages.styles%7Cjquery.makeCollapsible.styles%7Cskins.vector.icons%2Cstyles%7Cskins.vector.search.codex.styles%7Cwikibase.client.init&amp;only=styles&amp;skin=vector-2022"> <script async="" src="/w/load.php?lang=en&amp;modules=startup&amp;only=scripts&amp;raw=1&amp;skin=vector-2022"></script> <meta name="ResourceLoaderDynamicStyles" content=""> <link rel="stylesheet" href="/w/load.php?lang=en&amp;modules=site.styles&amp;only=styles&amp;skin=vector-2022"> <meta name="generator" content="MediaWiki 1.44.0-wmf.16"> <meta name="referrer" content="origin"> <meta name="referrer" content="origin-when-cross-origin"> <meta name="robots" content="max-image-preview:standard"> <meta name="format-detection" content="telephone=no"> <meta name="viewport" content="width=1120"> <meta property="og:title" content="Use case - Wikipedia"> <meta property="og:type" content="website"> <link rel="preconnect" href="//upload.wikimedia.org"> <link rel="alternate" media="only screen and (max-width: 640px)" href="//en.m.wikipedia.org/wiki/Use_case"> <link rel="alternate" type="application/x-wiki" title="Edit this page" href="/w/index.php?title=Use_case&amp;action=edit"> <link rel="apple-touch-icon" href="/static/apple-touch/wikipedia.png"> <link rel="icon" href="/static/favicon/wikipedia.ico"> <link rel="search" type="application/opensearchdescription+xml" href="/w/rest.php/v1/search" title="Wikipedia (en)"> <link rel="EditURI" type="application/rsd+xml" href="//en.wikipedia.org/w/api.php?action=rsd"> <link rel="canonical" href="https://en.wikipedia.org/wiki/Use_case"> <link rel="license" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en"> <link rel="alternate" type="application/atom+xml" title="Wikipedia Atom feed" href="/w/index.php?title=Special:RecentChanges&amp;feed=atom"> <link rel="dns-prefetch" href="//meta.wikimedia.org" /> <link rel="dns-prefetch" href="login.wikimedia.org"> </head> <body class="skin--responsive skin-vector skin-vector-search-vue mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject mw-editable page-Use_case rootpage-Use_case skin-vector-2022 action-view"><a class="mw-jump-link" href="#bodyContent">Jump to content</a> <div class="vector-header-container"> <header class="vector-header mw-header"> <div class="vector-header-start"> <nav class="vector-main-menu-landmark" aria-label="Site"> <div id="vector-main-menu-dropdown" class="vector-dropdown vector-main-menu-dropdown vector-button-flush-left vector-button-flush-right" title="Main menu" > <input type="checkbox" id="vector-main-menu-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-main-menu-dropdown" class="vector-dropdown-checkbox " aria-label="Main menu" > <label id="vector-main-menu-dropdown-label" for="vector-main-menu-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only " aria-hidden="true" ><span class="vector-icon mw-ui-icon-menu mw-ui-icon-wikimedia-menu"></span> <span class="vector-dropdown-label-text">Main menu</span> </label> <div class="vector-dropdown-content"> <div id="vector-main-menu-unpinned-container" class="vector-unpinned-container"> <div id="vector-main-menu" class="vector-main-menu vector-pinnable-element"> <div class="vector-pinnable-header vector-main-menu-pinnable-header vector-pinnable-header-unpinned" data-feature-name="main-menu-pinned" data-pinnable-element-id="vector-main-menu" data-pinned-container-id="vector-main-menu-pinned-container" data-unpinned-container-id="vector-main-menu-unpinned-container" > <div class="vector-pinnable-header-label">Main menu</div> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-pin-button" data-event-name="pinnable-header.vector-main-menu.pin">move to sidebar</button> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-unpin-button" data-event-name="pinnable-header.vector-main-menu.unpin">hide</button> </div> <div id="p-navigation" class="vector-menu mw-portlet mw-portlet-navigation" > <div class="vector-menu-heading"> Navigation </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="n-mainpage-description" class="mw-list-item"><a href="/wiki/Main_Page" title="Visit the main page [z]" accesskey="z"><span>Main page</span></a></li><li id="n-contents" class="mw-list-item"><a href="/wiki/Wikipedia:Contents" title="Guides to browsing Wikipedia"><span>Contents</span></a></li><li id="n-currentevents" class="mw-list-item"><a href="/wiki/Portal:Current_events" title="Articles related to current events"><span>Current events</span></a></li><li id="n-randompage" class="mw-list-item"><a href="/wiki/Special:Random" title="Visit a randomly selected article [x]" accesskey="x"><span>Random article</span></a></li><li id="n-aboutsite" class="mw-list-item"><a href="/wiki/Wikipedia:About" title="Learn about Wikipedia and how it works"><span>About Wikipedia</span></a></li><li id="n-contactpage" class="mw-list-item"><a href="//en.wikipedia.org/wiki/Wikipedia:Contact_us" title="How to contact Wikipedia"><span>Contact us</span></a></li> </ul> </div> </div> <div id="p-interaction" class="vector-menu mw-portlet mw-portlet-interaction" > <div class="vector-menu-heading"> Contribute </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="n-help" class="mw-list-item"><a href="/wiki/Help:Contents" title="Guidance on how to use and edit Wikipedia"><span>Help</span></a></li><li id="n-introduction" class="mw-list-item"><a href="/wiki/Help:Introduction" title="Learn how to edit Wikipedia"><span>Learn to edit</span></a></li><li id="n-portal" class="mw-list-item"><a href="/wiki/Wikipedia:Community_portal" title="The hub for editors"><span>Community portal</span></a></li><li id="n-recentchanges" class="mw-list-item"><a href="/wiki/Special:RecentChanges" title="A list of recent changes to Wikipedia [r]" accesskey="r"><span>Recent changes</span></a></li><li id="n-upload" class="mw-list-item"><a href="/wiki/Wikipedia:File_upload_wizard" title="Add images or other media for use on Wikipedia"><span>Upload file</span></a></li><li id="n-specialpages" class="mw-list-item"><a href="/wiki/Special:SpecialPages"><span>Special pages</span></a></li> </ul> </div> </div> </div> </div> </div> </div> </nav> <a href="/wiki/Main_Page" class="mw-logo"> <img class="mw-logo-icon" src="/static/images/icons/wikipedia.png" alt="" aria-hidden="true" height="50" width="50"> <span class="mw-logo-container skin-invert"> <img class="mw-logo-wordmark" alt="Wikipedia" src="/static/images/mobile/copyright/wikipedia-wordmark-en.svg" style="width: 7.5em; height: 1.125em;"> <img class="mw-logo-tagline" alt="The Free Encyclopedia" src="/static/images/mobile/copyright/wikipedia-tagline-en.svg" width="117" height="13" style="width: 7.3125em; height: 0.8125em;"> </span> </a> </div> <div class="vector-header-end"> <div id="p-search" role="search" class="vector-search-box-vue vector-search-box-collapses vector-search-box-show-thumbnail vector-search-box-auto-expand-width vector-search-box"> <a href="/wiki/Special:Search" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only search-toggle" title="Search Wikipedia [f]" accesskey="f"><span class="vector-icon mw-ui-icon-search mw-ui-icon-wikimedia-search"></span> <span>Search</span> </a> <div class="vector-typeahead-search-container"> <div class="cdx-typeahead-search cdx-typeahead-search--show-thumbnail cdx-typeahead-search--auto-expand-width"> <form action="/w/index.php" id="searchform" class="cdx-search-input cdx-search-input--has-end-button"> <div id="simpleSearch" class="cdx-search-input__input-wrapper" data-search-loc="header-moved"> <div class="cdx-text-input cdx-text-input--has-start-icon"> <input class="cdx-text-input__input" type="search" name="search" placeholder="Search Wikipedia" aria-label="Search Wikipedia" autocapitalize="sentences" title="Search Wikipedia [f]" accesskey="f" id="searchInput" > <span class="cdx-text-input__icon cdx-text-input__start-icon"></span> </div> <input type="hidden" name="title" value="Special:Search"> </div> <button class="cdx-button cdx-search-input__end-button">Search</button> </form> </div> </div> </div> <nav class="vector-user-links vector-user-links-wide" aria-label="Personal tools"> <div class="vector-user-links-main"> <div id="p-vector-user-menu-preferences" class="vector-menu mw-portlet emptyPortlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> </ul> </div> </div> <div id="p-vector-user-menu-userpage" class="vector-menu mw-portlet emptyPortlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> </ul> </div> </div> <nav class="vector-appearance-landmark" aria-label="Appearance"> <div id="vector-appearance-dropdown" class="vector-dropdown " title="Change the appearance of the page&#039;s font size, width, and color" > <input type="checkbox" id="vector-appearance-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-appearance-dropdown" class="vector-dropdown-checkbox " aria-label="Appearance" > <label id="vector-appearance-dropdown-label" for="vector-appearance-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only " aria-hidden="true" ><span class="vector-icon mw-ui-icon-appearance mw-ui-icon-wikimedia-appearance"></span> <span class="vector-dropdown-label-text">Appearance</span> </label> <div class="vector-dropdown-content"> <div id="vector-appearance-unpinned-container" class="vector-unpinned-container"> </div> </div> </div> </nav> <div id="p-vector-user-menu-notifications" class="vector-menu mw-portlet emptyPortlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> </ul> </div> </div> <div id="p-vector-user-menu-overflow" class="vector-menu mw-portlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="pt-sitesupport-2" class="user-links-collapsible-item mw-list-item user-links-collapsible-item"><a data-mw="interface" href="https://donate.wikimedia.org/?wmf_source=donate&amp;wmf_medium=sidebar&amp;wmf_campaign=en.wikipedia.org&amp;uselang=en" class=""><span>Donate</span></a> </li> <li id="pt-createaccount-2" class="user-links-collapsible-item mw-list-item user-links-collapsible-item"><a data-mw="interface" href="/w/index.php?title=Special:CreateAccount&amp;returnto=Use+case" title="You are encouraged to create an account and log in; however, it is not mandatory" class=""><span>Create account</span></a> </li> <li id="pt-login-2" class="user-links-collapsible-item mw-list-item user-links-collapsible-item"><a data-mw="interface" href="/w/index.php?title=Special:UserLogin&amp;returnto=Use+case" title="You&#039;re encouraged to log in; however, it&#039;s not mandatory. [o]" accesskey="o" class=""><span>Log in</span></a> </li> </ul> </div> </div> </div> <div id="vector-user-links-dropdown" class="vector-dropdown vector-user-menu vector-button-flush-right vector-user-menu-logged-out" title="Log in and more options" > <input type="checkbox" id="vector-user-links-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-user-links-dropdown" class="vector-dropdown-checkbox " aria-label="Personal tools" > <label id="vector-user-links-dropdown-label" for="vector-user-links-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only " aria-hidden="true" ><span class="vector-icon mw-ui-icon-ellipsis mw-ui-icon-wikimedia-ellipsis"></span> <span class="vector-dropdown-label-text">Personal tools</span> </label> <div class="vector-dropdown-content"> <div id="p-personal" class="vector-menu mw-portlet mw-portlet-personal user-links-collapsible-item" title="User menu" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="pt-sitesupport" class="user-links-collapsible-item mw-list-item"><a href="https://donate.wikimedia.org/?wmf_source=donate&amp;wmf_medium=sidebar&amp;wmf_campaign=en.wikipedia.org&amp;uselang=en"><span>Donate</span></a></li><li id="pt-createaccount" class="user-links-collapsible-item mw-list-item"><a href="/w/index.php?title=Special:CreateAccount&amp;returnto=Use+case" title="You are encouraged to create an account and log in; however, it is not mandatory"><span class="vector-icon mw-ui-icon-userAdd mw-ui-icon-wikimedia-userAdd"></span> <span>Create account</span></a></li><li id="pt-login" class="user-links-collapsible-item mw-list-item"><a href="/w/index.php?title=Special:UserLogin&amp;returnto=Use+case" title="You&#039;re encouraged to log in; however, it&#039;s not mandatory. [o]" accesskey="o"><span class="vector-icon mw-ui-icon-logIn mw-ui-icon-wikimedia-logIn"></span> <span>Log in</span></a></li> </ul> </div> </div> <div id="p-user-menu-anon-editor" class="vector-menu mw-portlet mw-portlet-user-menu-anon-editor" > <div class="vector-menu-heading"> Pages for logged out editors <a href="/wiki/Help:Introduction" aria-label="Learn more about editing"><span>learn more</span></a> </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="pt-anoncontribs" class="mw-list-item"><a href="/wiki/Special:MyContributions" title="A list of edits made from this IP address [y]" accesskey="y"><span>Contributions</span></a></li><li id="pt-anontalk" class="mw-list-item"><a href="/wiki/Special:MyTalk" title="Discussion about edits from this IP address [n]" accesskey="n"><span>Talk</span></a></li> </ul> </div> </div> </div> </div> </nav> </div> </header> </div> <div class="mw-page-container"> <div class="mw-page-container-inner"> <div class="vector-sitenotice-container"> <div id="siteNotice"><!-- CentralNotice --></div> </div> <div class="vector-column-start"> <div class="vector-main-menu-container"> <div id="mw-navigation"> <nav id="mw-panel" class="vector-main-menu-landmark" aria-label="Site"> <div id="vector-main-menu-pinned-container" class="vector-pinned-container"> </div> </nav> </div> </div> <div class="vector-sticky-pinned-container"> <nav id="mw-panel-toc" aria-label="Contents" data-event-name="ui.sidebar-toc" class="mw-table-of-contents-container vector-toc-landmark"> <div id="vector-toc-pinned-container" class="vector-pinned-container"> <div id="vector-toc" class="vector-toc vector-pinnable-element"> <div class="vector-pinnable-header vector-toc-pinnable-header vector-pinnable-header-pinned" data-feature-name="toc-pinned" data-pinnable-element-id="vector-toc" > <h2 class="vector-pinnable-header-label">Contents</h2> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-pin-button" data-event-name="pinnable-header.vector-toc.pin">move to sidebar</button> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-unpin-button" data-event-name="pinnable-header.vector-toc.unpin">hide</button> </div> <ul class="vector-toc-contents" id="mw-panel-toc-list"> <li id="toc-mw-content-text" class="vector-toc-list-item vector-toc-level-1"> <a href="#" class="vector-toc-link"> <div class="vector-toc-text">(Top)</div> </a> </li> <li id="toc-Definition" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#Definition"> <div class="vector-toc-text"> <span class="vector-toc-numb">1</span> <span>Definition</span> </div> </a> <ul id="toc-Definition-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-History" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#History"> <div class="vector-toc-text"> <span class="vector-toc-numb">2</span> <span>History</span> </div> </a> <ul id="toc-History-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-General_principle" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#General_principle"> <div class="vector-toc-text"> <span class="vector-toc-numb">3</span> <span>General principle</span> </div> </a> <button aria-controls="toc-General_principle-sublist" class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-toc-toggle"> <span class="vector-icon mw-ui-icon-wikimedia-expand"></span> <span>Toggle General principle subsection</span> </button> <ul id="toc-General_principle-sublist" class="vector-toc-list"> <li id="toc-Variations" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Variations"> <div class="vector-toc-text"> <span class="vector-toc-numb">3.1</span> <span>Variations</span> </div> </a> <ul id="toc-Variations-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Scope" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Scope"> <div class="vector-toc-text"> <span class="vector-toc-numb">3.2</span> <span>Scope</span> </div> </a> <ul id="toc-Scope-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Usage" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Usage"> <div class="vector-toc-text"> <span class="vector-toc-numb">3.3</span> <span>Usage</span> </div> </a> <ul id="toc-Usage-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-Templates" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#Templates"> <div class="vector-toc-text"> <span class="vector-toc-numb">4</span> <span>Templates</span> </div> </a> <button aria-controls="toc-Templates-sublist" class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-toc-toggle"> <span class="vector-icon mw-ui-icon-wikimedia-expand"></span> <span>Toggle Templates subsection</span> </button> <ul id="toc-Templates-sublist" class="vector-toc-list"> <li id="toc-Cockburn_style" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Cockburn_style"> <div class="vector-toc-text"> <span class="vector-toc-numb">4.1</span> <span>Cockburn style</span> </div> </a> <ul id="toc-Cockburn_style-sublist" class="vector-toc-list"> <li id="toc-Design_scopes" class="vector-toc-list-item vector-toc-level-3"> <a class="vector-toc-link" href="#Design_scopes"> <div class="vector-toc-text"> <span class="vector-toc-numb">4.1.1</span> <span>Design scopes</span> </div> </a> <ul id="toc-Design_scopes-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Goal_levels" class="vector-toc-list-item vector-toc-level-3"> <a class="vector-toc-link" href="#Goal_levels"> <div class="vector-toc-text"> <span class="vector-toc-numb">4.1.2</span> <span>Goal levels</span> </div> </a> <ul id="toc-Goal_levels-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Fully_dressed" class="vector-toc-list-item vector-toc-level-3"> <a class="vector-toc-link" href="#Fully_dressed"> <div class="vector-toc-text"> <span class="vector-toc-numb">4.1.3</span> <span>Fully dressed</span> </div> </a> <ul id="toc-Fully_dressed-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Casual" class="vector-toc-list-item vector-toc-level-3"> <a class="vector-toc-link" href="#Casual"> <div class="vector-toc-text"> <span class="vector-toc-numb">4.1.4</span> <span>Casual</span> </div> </a> <ul id="toc-Casual-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-Fowler_style" class="vector-toc-list-item vector-toc-level-2"> <a class="vector-toc-link" href="#Fowler_style"> <div class="vector-toc-text"> <span class="vector-toc-numb">4.2</span> <span>Fowler style</span> </div> </a> <ul id="toc-Fowler_style-sublist" class="vector-toc-list"> </ul> </li> </ul> </li> <li id="toc-Actors" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#Actors"> <div class="vector-toc-text"> <span class="vector-toc-numb">5</span> <span>Actors</span> </div> </a> <ul id="toc-Actors-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Business_use_case" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#Business_use_case"> <div class="vector-toc-text"> <span class="vector-toc-numb">6</span> <span>Business use case</span> </div> </a> <ul id="toc-Business_use_case-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Visual_modeling" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#Visual_modeling"> <div class="vector-toc-text"> <span class="vector-toc-numb">7</span> <span>Visual modeling</span> </div> </a> <ul id="toc-Visual_modeling-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Examples" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#Examples"> <div class="vector-toc-text"> <span class="vector-toc-numb">8</span> <span>Examples</span> </div> </a> <ul id="toc-Examples-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Advantages" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#Advantages"> <div class="vector-toc-text"> <span class="vector-toc-numb">9</span> <span>Advantages</span> </div> </a> <ul id="toc-Advantages-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Limitations" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#Limitations"> <div class="vector-toc-text"> <span class="vector-toc-numb">10</span> <span>Limitations</span> </div> </a> <ul id="toc-Limitations-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Misconceptions" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#Misconceptions"> <div class="vector-toc-text"> <span class="vector-toc-numb">11</span> <span>Misconceptions</span> </div> </a> <ul id="toc-Misconceptions-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Tools" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#Tools"> <div class="vector-toc-text"> <span class="vector-toc-numb">12</span> <span>Tools</span> </div> </a> <ul id="toc-Tools-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-See_also" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#See_also"> <div class="vector-toc-text"> <span class="vector-toc-numb">13</span> <span>See also</span> </div> </a> <ul id="toc-See_also-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-References" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#References"> <div class="vector-toc-text"> <span class="vector-toc-numb">14</span> <span>References</span> </div> </a> <ul id="toc-References-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-Further_reading" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#Further_reading"> <div class="vector-toc-text"> <span class="vector-toc-numb">15</span> <span>Further reading</span> </div> </a> <ul id="toc-Further_reading-sublist" class="vector-toc-list"> </ul> </li> <li id="toc-External_links" class="vector-toc-list-item vector-toc-level-1 vector-toc-list-item-expanded"> <a class="vector-toc-link" href="#External_links"> <div class="vector-toc-text"> <span class="vector-toc-numb">16</span> <span>External links</span> </div> </a> <ul id="toc-External_links-sublist" class="vector-toc-list"> </ul> </li> </ul> </div> </div> </nav> </div> </div> <div class="mw-content-container"> <main id="content" class="mw-body"> <header class="mw-body-header vector-page-titlebar"> <nav aria-label="Contents" class="vector-toc-landmark"> <div id="vector-page-titlebar-toc" class="vector-dropdown vector-page-titlebar-toc vector-button-flush-left" title="Table of Contents" > <input type="checkbox" id="vector-page-titlebar-toc-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-page-titlebar-toc" class="vector-dropdown-checkbox " aria-label="Toggle the table of contents" > <label id="vector-page-titlebar-toc-label" for="vector-page-titlebar-toc-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only " aria-hidden="true" ><span class="vector-icon mw-ui-icon-listBullet mw-ui-icon-wikimedia-listBullet"></span> <span class="vector-dropdown-label-text">Toggle the table of contents</span> </label> <div class="vector-dropdown-content"> <div id="vector-page-titlebar-toc-unpinned-container" class="vector-unpinned-container"> </div> </div> </div> </nav> <h1 id="firstHeading" class="firstHeading mw-first-heading"><span class="mw-page-title-main">Use case</span></h1> <div id="p-lang-btn" class="vector-dropdown mw-portlet mw-portlet-lang" > <input type="checkbox" id="p-lang-btn-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-p-lang-btn" class="vector-dropdown-checkbox mw-interlanguage-selector" aria-label="Go to an article in another language. Available in 28 languages" > <label id="p-lang-btn-label" for="p-lang-btn-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--action-progressive mw-portlet-lang-heading-28" aria-hidden="true" ><span class="vector-icon mw-ui-icon-language-progressive mw-ui-icon-wikimedia-language-progressive"></span> <span class="vector-dropdown-label-text">28 languages</span> </label> <div class="vector-dropdown-content"> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li class="interlanguage-link interwiki-af mw-list-item"><a href="https://af.wikipedia.org/wiki/President_(use_case)" title="President (use case) – Afrikaans" lang="af" hreflang="af" data-title="President (use case)" data-language-autonym="Afrikaans" data-language-local-name="Afrikaans" class="interlanguage-link-target"><span>Afrikaans</span></a></li><li class="interlanguage-link interwiki-ar mw-list-item"><a href="https://ar.wikipedia.org/wiki/%D8%AD%D8%A7%D9%84%D8%A9_%D8%A7%D9%84%D8%A7%D8%B3%D8%AA%D8%AE%D8%AF%D8%A7%D9%85_(%D9%87%D9%86%D8%AF%D8%B3%D8%A9_%D8%A7%D9%84%D8%A8%D8%B1%D9%85%D8%AC%D9%8A%D8%A7%D8%AA)" title="حالة الاستخدام (هندسة البرمجيات) – Arabic" lang="ar" hreflang="ar" data-title="حالة الاستخدام (هندسة البرمجيات)" data-language-autonym="العربية" data-language-local-name="Arabic" class="interlanguage-link-target"><span>العربية</span></a></li><li class="interlanguage-link interwiki-ca mw-list-item"><a href="https://ca.wikipedia.org/wiki/Cas_d%27%C3%BAs" title="Cas d&#039;ús – Catalan" lang="ca" hreflang="ca" data-title="Cas d&#039;ús" data-language-autonym="Català" data-language-local-name="Catalan" class="interlanguage-link-target"><span>Català</span></a></li><li class="interlanguage-link interwiki-cs mw-list-item"><a href="https://cs.wikipedia.org/wiki/P%C5%99%C3%ADpad_u%C5%BEit%C3%AD" title="Případ užití – Czech" lang="cs" hreflang="cs" data-title="Případ užití" data-language-autonym="Čeština" data-language-local-name="Czech" class="interlanguage-link-target"><span>Čeština</span></a></li><li class="interlanguage-link interwiki-da mw-list-item"><a href="https://da.wikipedia.org/wiki/Use_case" title="Use case – Danish" lang="da" hreflang="da" data-title="Use case" data-language-autonym="Dansk" data-language-local-name="Danish" class="interlanguage-link-target"><span>Dansk</span></a></li><li class="interlanguage-link interwiki-de mw-list-item"><a href="https://de.wikipedia.org/wiki/Anwendungsfall" title="Anwendungsfall – German" lang="de" hreflang="de" data-title="Anwendungsfall" data-language-autonym="Deutsch" data-language-local-name="German" class="interlanguage-link-target"><span>Deutsch</span></a></li><li class="interlanguage-link interwiki-es mw-list-item"><a href="https://es.wikipedia.org/wiki/Caso_de_uso" title="Caso de uso – Spanish" lang="es" hreflang="es" data-title="Caso de uso" data-language-autonym="Español" data-language-local-name="Spanish" class="interlanguage-link-target"><span>Español</span></a></li><li class="interlanguage-link interwiki-eo mw-list-item"><a href="https://eo.wikipedia.org/wiki/Uzokazo" title="Uzokazo – Esperanto" lang="eo" hreflang="eo" data-title="Uzokazo" data-language-autonym="Esperanto" data-language-local-name="Esperanto" class="interlanguage-link-target"><span>Esperanto</span></a></li><li class="interlanguage-link interwiki-eu mw-list-item"><a href="https://eu.wikipedia.org/wiki/Erabilpen_kasu" title="Erabilpen kasu – Basque" lang="eu" hreflang="eu" data-title="Erabilpen kasu" data-language-autonym="Euskara" data-language-local-name="Basque" class="interlanguage-link-target"><span>Euskara</span></a></li><li class="interlanguage-link interwiki-fa mw-list-item"><a href="https://fa.wikipedia.org/wiki/%D9%85%D9%88%D8%B1%D8%AF_%DA%A9%D8%A7%D8%B1%D8%A8%D8%B1%D8%AF" title="مورد کاربرد – Persian" lang="fa" hreflang="fa" data-title="مورد کاربرد" data-language-autonym="فارسی" data-language-local-name="Persian" class="interlanguage-link-target"><span>فارسی</span></a></li><li class="interlanguage-link interwiki-fr mw-list-item"><a href="https://fr.wikipedia.org/wiki/Cas_d%27utilisation" title="Cas d&#039;utilisation – French" lang="fr" hreflang="fr" data-title="Cas d&#039;utilisation" data-language-autonym="Français" data-language-local-name="French" class="interlanguage-link-target"><span>Français</span></a></li><li class="interlanguage-link interwiki-ko mw-list-item"><a href="https://ko.wikipedia.org/wiki/%EC%9C%A0%EC%8A%A4_%EC%BC%80%EC%9D%B4%EC%8A%A4" title="유스 케이스 – Korean" lang="ko" hreflang="ko" data-title="유스 케이스" data-language-autonym="한국어" data-language-local-name="Korean" class="interlanguage-link-target"><span>한국어</span></a></li><li class="interlanguage-link interwiki-it mw-list-item"><a href="https://it.wikipedia.org/wiki/Caso_d%27uso_(informatica)" title="Caso d&#039;uso (informatica) – Italian" lang="it" hreflang="it" data-title="Caso d&#039;uso (informatica)" data-language-autonym="Italiano" data-language-local-name="Italian" class="interlanguage-link-target"><span>Italiano</span></a></li><li class="interlanguage-link interwiki-he mw-list-item"><a href="https://he.wikipedia.org/wiki/%D7%AA%D7%A8%D7%97%D7%99%D7%A9_%D7%A9%D7%99%D7%9E%D7%95%D7%A9" title="תרחיש שימוש – Hebrew" lang="he" hreflang="he" data-title="תרחיש שימוש" data-language-autonym="עברית" data-language-local-name="Hebrew" class="interlanguage-link-target"><span>עברית</span></a></li><li class="interlanguage-link interwiki-nl mw-list-item"><a href="https://nl.wikipedia.org/wiki/Usecase" title="Usecase – Dutch" lang="nl" hreflang="nl" data-title="Usecase" data-language-autonym="Nederlands" data-language-local-name="Dutch" class="interlanguage-link-target"><span>Nederlands</span></a></li><li class="interlanguage-link interwiki-ja mw-list-item"><a href="https://ja.wikipedia.org/wiki/%E3%83%A6%E3%83%BC%E3%82%B9%E3%82%B1%E3%83%BC%E3%82%B9" title="ユースケース – Japanese" lang="ja" hreflang="ja" data-title="ユースケース" data-language-autonym="日本語" data-language-local-name="Japanese" class="interlanguage-link-target"><span>日本語</span></a></li><li class="interlanguage-link interwiki-no mw-list-item"><a href="https://no.wikipedia.org/wiki/Bruksm%C3%B8nster" title="Bruksmønster – Norwegian Bokmål" lang="nb" hreflang="nb" data-title="Bruksmønster" data-language-autonym="Norsk bokmål" data-language-local-name="Norwegian Bokmål" class="interlanguage-link-target"><span>Norsk bokmål</span></a></li><li class="interlanguage-link interwiki-pl mw-list-item"><a href="https://pl.wikipedia.org/wiki/Przypadek_u%C5%BCycia" title="Przypadek użycia – Polish" lang="pl" hreflang="pl" data-title="Przypadek użycia" data-language-autonym="Polski" data-language-local-name="Polish" class="interlanguage-link-target"><span>Polski</span></a></li><li class="interlanguage-link interwiki-pt mw-list-item"><a href="https://pt.wikipedia.org/wiki/Caso_de_uso" title="Caso de uso – Portuguese" lang="pt" hreflang="pt" data-title="Caso de uso" data-language-autonym="Português" data-language-local-name="Portuguese" class="interlanguage-link-target"><span>Português</span></a></li><li class="interlanguage-link interwiki-ru mw-list-item"><a href="https://ru.wikipedia.org/wiki/%D0%A1%D1%86%D0%B5%D0%BD%D0%B0%D1%80%D0%B8%D0%B9_%D0%B8%D1%81%D0%BF%D0%BE%D0%BB%D1%8C%D0%B7%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D1%8F" title="Сценарий использования – Russian" lang="ru" hreflang="ru" data-title="Сценарий использования" data-language-autonym="Русский" data-language-local-name="Russian" class="interlanguage-link-target"><span>Русский</span></a></li><li class="interlanguage-link interwiki-sq mw-list-item"><a href="https://sq.wikipedia.org/wiki/Use_case" title="Use case – Albanian" lang="sq" hreflang="sq" data-title="Use case" data-language-autonym="Shqip" data-language-local-name="Albanian" class="interlanguage-link-target"><span>Shqip</span></a></li><li class="interlanguage-link interwiki-sk mw-list-item"><a href="https://sk.wikipedia.org/wiki/Pr%C3%ADpad_pou%C5%BEitia" title="Prípad použitia – Slovak" lang="sk" hreflang="sk" data-title="Prípad použitia" data-language-autonym="Slovenčina" data-language-local-name="Slovak" class="interlanguage-link-target"><span>Slovenčina</span></a></li><li class="interlanguage-link interwiki-fi mw-list-item"><a href="https://fi.wikipedia.org/wiki/K%C3%A4ytt%C3%B6tapaus" title="Käyttötapaus – Finnish" lang="fi" hreflang="fi" data-title="Käyttötapaus" data-language-autonym="Suomi" data-language-local-name="Finnish" class="interlanguage-link-target"><span>Suomi</span></a></li><li class="interlanguage-link interwiki-sv mw-list-item"><a href="https://sv.wikipedia.org/wiki/Anv%C3%A4ndningsfall" title="Användningsfall – Swedish" lang="sv" hreflang="sv" data-title="Användningsfall" data-language-autonym="Svenska" data-language-local-name="Swedish" class="interlanguage-link-target"><span>Svenska</span></a></li><li class="interlanguage-link interwiki-tr mw-list-item"><a href="https://tr.wikipedia.org/wiki/Kullan%C4%B1m_senaryosu" title="Kullanım senaryosu – Turkish" lang="tr" hreflang="tr" data-title="Kullanım senaryosu" data-language-autonym="Türkçe" data-language-local-name="Turkish" class="interlanguage-link-target"><span>Türkçe</span></a></li><li class="interlanguage-link interwiki-uk mw-list-item"><a href="https://uk.wikipedia.org/wiki/%D0%A1%D1%86%D0%B5%D0%BD%D0%B0%D1%80%D1%96%D0%B9_%D0%B2%D0%B8%D0%BA%D0%BE%D1%80%D0%B8%D1%81%D1%82%D0%B0%D0%BD%D0%BD%D1%8F" title="Сценарій використання – Ukrainian" lang="uk" hreflang="uk" data-title="Сценарій використання" data-language-autonym="Українська" data-language-local-name="Ukrainian" class="interlanguage-link-target"><span>Українська</span></a></li><li class="interlanguage-link interwiki-vi mw-list-item"><a href="https://vi.wikipedia.org/wiki/Tr%C6%B0%E1%BB%9Dng_h%E1%BB%A3p_s%E1%BB%AD_d%E1%BB%A5ng" title="Trường hợp sử dụng – Vietnamese" lang="vi" hreflang="vi" data-title="Trường hợp sử dụng" data-language-autonym="Tiếng Việt" data-language-local-name="Vietnamese" class="interlanguage-link-target"><span>Tiếng Việt</span></a></li><li class="interlanguage-link interwiki-zh mw-list-item"><a href="https://zh.wikipedia.org/wiki/%E7%94%A8%E4%BE%8B" title="用例 – Chinese" lang="zh" hreflang="zh" data-title="用例" data-language-autonym="中文" data-language-local-name="Chinese" class="interlanguage-link-target"><span>中文</span></a></li> </ul> <div class="after-portlet after-portlet-lang"><span class="wb-langlinks-edit wb-langlinks-link"><a href="https://www.wikidata.org/wiki/Special:EntityPage/Q613417#sitelinks-wikipedia" title="Edit interlanguage links" class="wbc-editpage">Edit links</a></span></div> </div> </div> </div> </header> <div class="vector-page-toolbar"> <div class="vector-page-toolbar-container"> <div id="left-navigation"> <nav aria-label="Namespaces"> <div id="p-associated-pages" class="vector-menu vector-menu-tabs mw-portlet mw-portlet-associated-pages" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="ca-nstab-main" class="selected vector-tab-noicon mw-list-item"><a href="/wiki/Use_case" title="View the content page [c]" accesskey="c"><span>Article</span></a></li><li id="ca-talk" class="vector-tab-noicon mw-list-item"><a href="/wiki/Talk:Use_case" rel="discussion" title="Discuss improvements to the content page [t]" accesskey="t"><span>Talk</span></a></li> </ul> </div> </div> <div id="vector-variants-dropdown" class="vector-dropdown emptyPortlet" > <input type="checkbox" id="vector-variants-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-variants-dropdown" class="vector-dropdown-checkbox " aria-label="Change language variant" > <label id="vector-variants-dropdown-label" for="vector-variants-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet" aria-hidden="true" ><span class="vector-dropdown-label-text">English</span> </label> <div class="vector-dropdown-content"> <div id="p-variants" class="vector-menu mw-portlet mw-portlet-variants emptyPortlet" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> </ul> </div> </div> </div> </div> </nav> </div> <div id="right-navigation" class="vector-collapsible"> <nav aria-label="Views"> <div id="p-views" class="vector-menu vector-menu-tabs mw-portlet mw-portlet-views" > <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="ca-view" class="selected vector-tab-noicon mw-list-item"><a href="/wiki/Use_case"><span>Read</span></a></li><li id="ca-edit" class="vector-tab-noicon mw-list-item"><a href="/w/index.php?title=Use_case&amp;action=edit" title="Edit this page [e]" accesskey="e"><span>Edit</span></a></li><li id="ca-history" class="vector-tab-noicon mw-list-item"><a href="/w/index.php?title=Use_case&amp;action=history" title="Past revisions of this page [h]" accesskey="h"><span>View history</span></a></li> </ul> </div> </div> </nav> <nav class="vector-page-tools-landmark" aria-label="Page tools"> <div id="vector-page-tools-dropdown" class="vector-dropdown vector-page-tools-dropdown" > <input type="checkbox" id="vector-page-tools-dropdown-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-page-tools-dropdown" class="vector-dropdown-checkbox " aria-label="Tools" > <label id="vector-page-tools-dropdown-label" for="vector-page-tools-dropdown-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet" aria-hidden="true" ><span class="vector-dropdown-label-text">Tools</span> </label> <div class="vector-dropdown-content"> <div id="vector-page-tools-unpinned-container" class="vector-unpinned-container"> <div id="vector-page-tools" class="vector-page-tools vector-pinnable-element"> <div class="vector-pinnable-header vector-page-tools-pinnable-header vector-pinnable-header-unpinned" data-feature-name="page-tools-pinned" data-pinnable-element-id="vector-page-tools" data-pinned-container-id="vector-page-tools-pinned-container" data-unpinned-container-id="vector-page-tools-unpinned-container" > <div class="vector-pinnable-header-label">Tools</div> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-pin-button" data-event-name="pinnable-header.vector-page-tools.pin">move to sidebar</button> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-unpin-button" data-event-name="pinnable-header.vector-page-tools.unpin">hide</button> </div> <div id="p-cactions" class="vector-menu mw-portlet mw-portlet-cactions emptyPortlet vector-has-collapsible-items" title="More options" > <div class="vector-menu-heading"> Actions </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="ca-more-view" class="selected vector-more-collapsible-item mw-list-item"><a href="/wiki/Use_case"><span>Read</span></a></li><li id="ca-more-edit" class="vector-more-collapsible-item mw-list-item"><a href="/w/index.php?title=Use_case&amp;action=edit" title="Edit this page [e]" accesskey="e"><span>Edit</span></a></li><li id="ca-more-history" class="vector-more-collapsible-item mw-list-item"><a href="/w/index.php?title=Use_case&amp;action=history"><span>View history</span></a></li> </ul> </div> </div> <div id="p-tb" class="vector-menu mw-portlet mw-portlet-tb" > <div class="vector-menu-heading"> General </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="t-whatlinkshere" class="mw-list-item"><a href="/wiki/Special:WhatLinksHere/Use_case" title="List of all English Wikipedia pages containing links to this page [j]" accesskey="j"><span>What links here</span></a></li><li id="t-recentchangeslinked" class="mw-list-item"><a href="/wiki/Special:RecentChangesLinked/Use_case" rel="nofollow" title="Recent changes in pages linked from this page [k]" accesskey="k"><span>Related changes</span></a></li><li id="t-upload" class="mw-list-item"><a href="//en.wikipedia.org/wiki/Wikipedia:File_Upload_Wizard" title="Upload files [u]" accesskey="u"><span>Upload file</span></a></li><li id="t-permalink" class="mw-list-item"><a href="/w/index.php?title=Use_case&amp;oldid=1275966836" title="Permanent link to this revision of this page"><span>Permanent link</span></a></li><li id="t-info" class="mw-list-item"><a href="/w/index.php?title=Use_case&amp;action=info" title="More information about this page"><span>Page information</span></a></li><li id="t-cite" class="mw-list-item"><a href="/w/index.php?title=Special:CiteThisPage&amp;page=Use_case&amp;id=1275966836&amp;wpFormIdentifier=titleform" title="Information on how to cite this page"><span>Cite this page</span></a></li><li id="t-urlshortener" class="mw-list-item"><a href="/w/index.php?title=Special:UrlShortener&amp;url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FUse_case"><span>Get shortened URL</span></a></li><li id="t-urlshortener-qrcode" class="mw-list-item"><a href="/w/index.php?title=Special:QrCode&amp;url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FUse_case"><span>Download QR code</span></a></li> </ul> </div> </div> <div id="p-coll-print_export" class="vector-menu mw-portlet mw-portlet-coll-print_export" > <div class="vector-menu-heading"> Print/export </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="coll-download-as-rl" class="mw-list-item"><a href="/w/index.php?title=Special:DownloadAsPdf&amp;page=Use_case&amp;action=show-download-screen" title="Download this page as a PDF file"><span>Download as PDF</span></a></li><li id="t-print" class="mw-list-item"><a href="/w/index.php?title=Use_case&amp;printable=yes" title="Printable version of this page [p]" accesskey="p"><span>Printable version</span></a></li> </ul> </div> </div> <div id="p-wikibase-otherprojects" class="vector-menu mw-portlet mw-portlet-wikibase-otherprojects" > <div class="vector-menu-heading"> In other projects </div> <div class="vector-menu-content"> <ul class="vector-menu-content-list"> <li id="t-wikibase" class="wb-otherproject-link wb-otherproject-wikibase-dataitem mw-list-item"><a href="https://www.wikidata.org/wiki/Special:EntityPage/Q613417" title="Structured data on this page hosted by Wikidata [g]" accesskey="g"><span>Wikidata item</span></a></li> </ul> </div> </div> </div> </div> </div> </div> </nav> </div> </div> </div> <div class="vector-column-end"> <div class="vector-sticky-pinned-container"> <nav class="vector-page-tools-landmark" aria-label="Page tools"> <div id="vector-page-tools-pinned-container" class="vector-pinned-container"> </div> </nav> <nav class="vector-appearance-landmark" aria-label="Appearance"> <div id="vector-appearance-pinned-container" class="vector-pinned-container"> <div id="vector-appearance" class="vector-appearance vector-pinnable-element"> <div class="vector-pinnable-header vector-appearance-pinnable-header vector-pinnable-header-pinned" data-feature-name="appearance-pinned" data-pinnable-element-id="vector-appearance" data-pinned-container-id="vector-appearance-pinned-container" data-unpinned-container-id="vector-appearance-unpinned-container" > <div class="vector-pinnable-header-label">Appearance</div> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-pin-button" data-event-name="pinnable-header.vector-appearance.pin">move to sidebar</button> <button class="vector-pinnable-header-toggle-button vector-pinnable-header-unpin-button" data-event-name="pinnable-header.vector-appearance.unpin">hide</button> </div> </div> </div> </nav> </div> </div> <div id="bodyContent" class="vector-body" aria-labelledby="firstHeading" data-mw-ve-target-container> <div class="vector-body-before-content"> <div class="mw-indicators"> </div> <div id="siteSub" class="noprint">From Wikipedia, the free encyclopedia</div> </div> <div id="contentSub"><div id="mw-content-subtitle"></div></div> <div id="mw-content-text" class="mw-body-content"><div class="mw-content-ltr mw-parser-output" lang="en" dir="ltr"><p class="mw-empty-elt"> </p> <div class="shortdescription nomobile noexcerpt noprint searchaux" style="display:none">Potential scenario for use of a system</div> <figure class="mw-halign-right" typeof="mw:File/Thumb"><a href="/wiki/File:UseCase_actor_Edit_an_article_scenario.svg" class="mw-file-description"><img alt="UseCase Actor Edit an article scenario" src="//upload.wikimedia.org/wikipedia/commons/thumb/3/3f/UseCase_actor_Edit_an_article_scenario.svg/400px-UseCase_actor_Edit_an_article_scenario.svg.png" decoding="async" width="400" height="123" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/3/3f/UseCase_actor_Edit_an_article_scenario.svg/600px-UseCase_actor_Edit_an_article_scenario.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/3/3f/UseCase_actor_Edit_an_article_scenario.svg/800px-UseCase_actor_Edit_an_article_scenario.svg.png 2x" data-file-width="602" data-file-height="185" /></a><figcaption>A very simple <a href="/wiki/Use_case_diagram" title="Use case diagram">use case diagram</a> of a <a href="/wiki/Wiki" title="Wiki">Wiki</a> system. Registered user of Wiki edits an article.</figcaption></figure> <style data-mw-deduplicate="TemplateStyles:r1236090951">.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}</style><div role="note" class="hatnote navigation-not-searchable">For a personalized fictional character created to represent a potential end user, see <a href="/wiki/Persona_(user_experience)" title="Persona (user experience)">Persona (user experience)</a>.</div> <style data-mw-deduplicate="TemplateStyles:r1129693374">.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}</style><style data-mw-deduplicate="TemplateStyles:r1246091330">.mw-parser-output .sidebar{width:22em;float:right;clear:right;margin:0.5em 0 1em 1em;background:var(--background-color-neutral-subtle,#f8f9fa);border:1px solid var(--border-color-base,#a2a9b1);padding:0.2em;text-align:center;line-height:1.4em;font-size:88%;border-collapse:collapse;display:table}body.skin-minerva .mw-parser-output .sidebar{display:table!important;float:right!important;margin:0.5em 0 1em 1em!important}.mw-parser-output .sidebar-subgroup{width:100%;margin:0;border-spacing:0}.mw-parser-output .sidebar-left{float:left;clear:left;margin:0.5em 1em 1em 0}.mw-parser-output .sidebar-none{float:none;clear:both;margin:0.5em 1em 1em 0}.mw-parser-output .sidebar-outer-title{padding:0 0.4em 0.2em;font-size:125%;line-height:1.2em;font-weight:bold}.mw-parser-output .sidebar-top-image{padding:0.4em}.mw-parser-output .sidebar-top-caption,.mw-parser-output .sidebar-pretitle-with-top-image,.mw-parser-output .sidebar-caption{padding:0.2em 0.4em 0;line-height:1.2em}.mw-parser-output .sidebar-pretitle{padding:0.4em 0.4em 0;line-height:1.2em}.mw-parser-output .sidebar-title,.mw-parser-output .sidebar-title-with-pretitle{padding:0.2em 0.8em;font-size:145%;line-height:1.2em}.mw-parser-output .sidebar-title-with-pretitle{padding:0.1em 0.4em}.mw-parser-output .sidebar-image{padding:0.2em 0.4em 0.4em}.mw-parser-output .sidebar-heading{padding:0.1em 0.4em}.mw-parser-output .sidebar-content{padding:0 0.5em 0.4em}.mw-parser-output .sidebar-content-with-subgroup{padding:0.1em 0.4em 0.2em}.mw-parser-output .sidebar-above,.mw-parser-output .sidebar-below{padding:0.3em 0.8em;font-weight:bold}.mw-parser-output .sidebar-collapse .sidebar-above,.mw-parser-output .sidebar-collapse .sidebar-below{border-top:1px solid #aaa;border-bottom:1px solid #aaa}.mw-parser-output .sidebar-navbar{text-align:right;font-size:115%;padding:0 0.4em 0.4em}.mw-parser-output .sidebar-list-title{padding:0 0.4em;text-align:left;font-weight:bold;line-height:1.6em;font-size:105%}.mw-parser-output .sidebar-list-title-c{padding:0 0.4em;text-align:center;margin:0 3.3em}@media(max-width:640px){body.mediawiki .mw-parser-output .sidebar{width:100%!important;clear:both;float:none!important;margin-left:0!important;margin-right:0!important}}body.skin--responsive .mw-parser-output .sidebar a>img{max-width:none!important}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-list-title,html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle{background:transparent!important}html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle a{color:var(--color-progressive)!important}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-list-title,html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle{background:transparent!important}html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle a{color:var(--color-progressive)!important}}@media print{body.ns-0 .mw-parser-output .sidebar{display:none!important}}</style><table class="sidebar sidebar-collapse nomobile"><tbody><tr><td class="sidebar-pretitle">Part of a series on</td></tr><tr><th class="sidebar-title-with-pretitle"><a href="/wiki/Software_development" title="Software development">Software development</a></th></tr><tr><td class="sidebar-content"> <div class="sidebar-list mw-collapsible mw-collapsed"><div class="sidebar-list-title" style="color: var(--color-base)">Core activities</div><div class="sidebar-list-content mw-collapsible-content hlist"> <ul><li><a href="/wiki/Data_modeling" title="Data modeling">Data modeling</a></li> <li><a href="/wiki/Software_development_process" title="Software development process">Processes</a></li> <li><a href="/wiki/Requirements_analysis" title="Requirements analysis">Requirements</a></li> <li><a href="/wiki/Software_design" title="Software design">Design</a></li> <li><a href="/wiki/Software_construction" title="Software construction">Construction</a></li> <li><a href="/wiki/Software_engineering" title="Software engineering">Engineering</a></li> <li><a href="/wiki/Software_testing" title="Software testing">Testing</a></li> <li><a href="/wiki/Debugging" title="Debugging">Debugging</a></li> <li><a href="/wiki/Software_deployment" title="Software deployment">Deployment</a></li> <li><a href="/wiki/Software_maintenance" title="Software maintenance">Maintenance</a></li></ul></div></div></td> </tr><tr><td class="sidebar-content"> <div class="sidebar-list mw-collapsible mw-collapsed"><div class="sidebar-list-title" style="color: var(--color-base)">Paradigms and models</div><div class="sidebar-list-content mw-collapsible-content hlist"> <ul><li><a href="/wiki/Agile_software_development" title="Agile software development">Agile</a></li> <li><a href="/wiki/Cleanroom_software_engineering" title="Cleanroom software engineering">Cleanroom</a></li> <li><a href="/wiki/Incremental_build_model" title="Incremental build model">Incremental</a></li> <li><a href="/wiki/Software_prototyping" title="Software prototyping">Prototyping</a></li> <li><a href="/wiki/Spiral_model" title="Spiral model">Spiral</a></li> <li><a href="/wiki/V-model_(software_development)" title="V-model (software development)">V model</a></li> <li><a href="/wiki/Waterfall_model" title="Waterfall model">Waterfall</a></li></ul></div></div></td> </tr><tr><td class="sidebar-content"> <div class="sidebar-list mw-collapsible mw-collapsed"><div class="sidebar-list-title" style="color: var(--color-base)"><a href="/wiki/Software_development_methodology" class="mw-redirect" title="Software development methodology">Methodologies</a> and frameworks</div><div class="sidebar-list-content mw-collapsible-content hlist"> <ul><li><a href="/wiki/Adaptive_software_development" title="Adaptive software development">ASD</a></li> <li><a href="/wiki/Disciplined_agile_delivery" title="Disciplined agile delivery">DAD</a></li> <li><a href="/wiki/DevOps" title="DevOps">DevOps</a></li> <li><a href="/wiki/Dynamic_systems_development_method" title="Dynamic systems development method">DSDM</a></li> <li><a href="/wiki/Feature-driven_development" title="Feature-driven development">FDD</a></li> <li><a href="/wiki/Iterative_and_incremental_development" title="Iterative and incremental development">IID</a></li> <li><a href="/wiki/Kanban_(development)" title="Kanban (development)">Kanban</a></li> <li><a href="/wiki/Lean_software_development" title="Lean software development">Lean SD</a></li> <li><a href="/wiki/Scrum_(software_development)#Large-scale_Scrum" title="Scrum (software development)">LeSS</a></li> <li><a href="/wiki/Model-driven_development" class="mw-redirect" title="Model-driven development">MDD</a></li> <li><a href="/wiki/Microsoft_Solutions_Framework" title="Microsoft Solutions Framework">MSF</a></li> <li><a href="/wiki/Personal_software_process" title="Personal software process">PSP</a></li> <li><a href="/wiki/Rapid_application_development" title="Rapid application development">RAD</a></li> <li><a href="/wiki/Rational_unified_process" title="Rational unified process">RUP</a></li> <li><a href="/wiki/Scaled_agile_framework" title="Scaled agile framework">SAFe</a></li> <li><a href="/wiki/Scrum_(software_development)" title="Scrum (software development)">Scrum</a></li> <li><a href="/wiki/SEMAT" title="SEMAT">SEMAT</a></li> <li><a href="/wiki/Test-driven_development" title="Test-driven development">TDD</a></li> <li><a href="/wiki/Team_software_process" title="Team software process">TSP</a></li> <li><a href="/wiki/Unified_process" title="Unified process">UP</a></li> <li><a href="/wiki/Extreme_programming" title="Extreme programming">XP</a></li></ul></div></div></td> </tr><tr><td class="sidebar-content"> <div class="sidebar-list mw-collapsible mw-collapsed"><div class="sidebar-list-title" style="color: var(--color-base)">Supporting disciplines</div><div class="sidebar-list-content mw-collapsible-content hlist"> <ul><li><a href="/wiki/Software_configuration_management" title="Software configuration management">Configuration management</a></li> <li><a href="/wiki/Deployment_management#Computer_science" title="Deployment management">Deployment management</a></li> <li><a href="/wiki/Software_documentation" title="Software documentation">Documentation</a></li> <li><a href="/wiki/Software_project_management" title="Software project management">Project management</a></li> <li><a href="/wiki/Software_quality_assurance" title="Software quality assurance">Quality assurance</a></li> <li><a href="/wiki/User_experience" title="User experience">User experience</a></li></ul></div></div></td> </tr><tr><td class="sidebar-content"> <div class="sidebar-list mw-collapsible mw-collapsed"><div class="sidebar-list-title" style="color: var(--color-base)">Practices</div><div class="sidebar-list-content mw-collapsible-content hlist"> <ul><li><a href="/wiki/Acceptance_test-driven_development" title="Acceptance test-driven development">ATDD</a></li> <li><a href="/wiki/Behavior-driven_development" title="Behavior-driven development">BDD</a></li> <li><a href="/wiki/Extreme_programming_practices#Collective_code_ownership" title="Extreme programming practices">CCO</a></li> <li><a href="/wiki/Continuous_delivery" title="Continuous delivery">CD</a></li> <li><a href="/wiki/Continuous_integration" title="Continuous integration">CI</a></li> <li><a href="/wiki/Domain-driven_design" title="Domain-driven design">DDD</a></li> <li><a href="/wiki/Pair_programming" title="Pair programming">PP</a></li> <li><a href="/wiki/Specification_by_example" title="Specification by example">SBE</a></li> <li><a href="/wiki/Stand-up_meeting" title="Stand-up meeting">Stand-up</a></li> <li><a href="/wiki/Test-driven_development" title="Test-driven development">TDD</a></li></ul></div></div></td> </tr><tr><td class="sidebar-content"> <div class="sidebar-list mw-collapsible mw-collapsed"><div class="sidebar-list-title" style="color: var(--color-base)"><a href="/wiki/Programming_tool" title="Programming tool">Tools</a></div><div class="sidebar-list-content mw-collapsible-content hlist"> <ul><li><a href="/wiki/Build_automation" title="Build automation">Build automation</a></li> <li><a href="/wiki/Compiler" title="Compiler">Compiler</a></li> <li><a href="/wiki/Debugger" title="Debugger">Debugger</a></li> <li><a href="/wiki/Graphical_user_interface_builder" title="Graphical user interface builder">GUI builder</a></li> <li><a href="/wiki/Integrated_development_environment" title="Integrated development environment">IDE</a></li> <li><a href="/wiki/Infrastructure_as_code" title="Infrastructure as code">Infrastructure as code</a></li> <li><a href="/wiki/Profiling_(computer_programming)" title="Profiling (computer programming)">Profiler</a></li> <li><a href="/wiki/Application-release_automation" title="Application-release automation">Release automation</a></li> <li><a href="/wiki/UML_tool" title="UML tool">UML Modeling</a></li></ul></div></div></td> </tr><tr><td class="sidebar-content"> <div class="sidebar-list mw-collapsible mw-collapsed"><div class="sidebar-list-title" style="color: var(--color-base)">Standards and bodies of knowledge</div><div class="sidebar-list-content mw-collapsible-content hlist"> <ul><li><a href="/wiki/Capability_Maturity_Model_Integration" title="Capability Maturity Model Integration">CMMI</a></li> <li><a href="/wiki/IEEE_Standards_Association" title="IEEE Standards Association">IEEE standards</a></li> <li><a href="/wiki/International_Requirements_Engineering_Board" title="International Requirements Engineering Board">IREB</a></li> <li><a href="/wiki/ISO_9001" class="mw-redirect" title="ISO 9001">ISO 9001</a></li> <li><a href="/wiki/ISO/IEC_JTC_1/SC_7" title="ISO/IEC JTC 1/SC 7">ISO/IEC standards</a></li> <li><a href="/wiki/ITIL" title="ITIL">ITIL</a></li> <li><a href="/wiki/Object_Management_Group" title="Object Management Group">OMG</a></li> <li><a href="/wiki/Project_Management_Body_of_Knowledge" title="Project Management Body of Knowledge">PMBOK</a></li> <li><a href="/wiki/Software_Engineering_Body_of_Knowledge" title="Software Engineering Body of Knowledge">SWEBOK</a></li></ul></div></div></td> </tr><tr><td class="sidebar-content"> <div class="sidebar-list mw-collapsible mw-collapsed"><div class="sidebar-list-title" style="color: var(--color-base)">Glossaries</div><div class="sidebar-list-content mw-collapsible-content hlist"> <ul><li><a href="/wiki/Glossary_of_artificial_intelligence" title="Glossary of artificial intelligence">Artificial intelligence</a></li> <li><a href="/wiki/Glossary_of_computer_science" title="Glossary of computer science">Computer science</a></li> <li><a href="/wiki/Glossary_of_electrical_and_electronics_engineering" title="Glossary of electrical and electronics engineering">Electrical and electronics engineering</a></li></ul></div></div></td> </tr><tr><td class="sidebar-content"> <div class="sidebar-list mw-collapsible mw-collapsed"><div class="sidebar-list-title" style="color: var(--color-base)">Outlines</div><div class="sidebar-list-content mw-collapsible-content hlist"> <ul><li><a href="/wiki/Outline_of_software_development" title="Outline of software development">Outline of software development</a></li></ul></div></div></td> </tr><tr><td class="sidebar-navbar"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374"><style data-mw-deduplicate="TemplateStyles:r1239400231">.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}</style><div class="navbar plainlinks hlist navbar-mini"><ul><li class="nv-view"><a href="/wiki/Template:Software_development_process" title="Template:Software development process"><abbr title="View this template">v</abbr></a></li><li class="nv-talk"><a href="/wiki/Template_talk:Software_development_process" title="Template talk:Software development process"><abbr title="Discuss this template">t</abbr></a></li><li class="nv-edit"><a href="/wiki/Special:EditPage/Template:Software_development_process" title="Special:EditPage/Template:Software development process"><abbr title="Edit this template">e</abbr></a></li></ul></div></td></tr></tbody></table> <p>In <a href="/wiki/Software_engineering" title="Software engineering">software</a> and <a href="/wiki/Systems_engineering" title="Systems engineering">systems engineering</a>, a <b>use case</b> is a potential scenario in which a system receives an external request (such as user input) and responds to it. A use case is a list of actions or event steps typically defining the interactions between a role (known in the <a href="/wiki/Unified_Modeling_Language" title="Unified Modeling Language">Unified Modeling Language</a> (UML) as an <i><a href="/wiki/Actor_(UML)" title="Actor (UML)">actor</a></i>) and a system to achieve a goal. The actor can be a human or another external system. In systems engineering, use cases are used at a higher level than within <a href="/wiki/Software_engineering" title="Software engineering">software engineering</a>, often representing missions or <a href="/wiki/Project_stakeholder" title="Project stakeholder">stakeholder</a> goals. The detailed requirements may then be captured in the <a href="/wiki/Systems_Modeling_Language" class="mw-redirect" title="Systems Modeling Language">Systems Modeling Language</a> (SysML) or as contractual statements. </p> <meta property="mw:PageProp/toc" /> <div class="mw-heading mw-heading2"><h2 id="Definition">Definition</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=1" title="Edit section: Definition"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>In <a href="/wiki/Software_engineering" title="Software engineering">software</a> and <a href="/wiki/Systems_engineering" title="Systems engineering">systems engineering</a>, the phrase use case is a <a href="/wiki/Polysemy" title="Polysemy">polyseme</a> with two <a href="/wiki/Word_sense" title="Word sense">senses</a>: </p> <ol><li>A usage scenario for a piece of software; often used in the plural to suggest situations where a piece of software may be useful.</li> <li>A potential scenario in which a system receives an external request (such as user input) and responds to it.</li></ol> <p>This article discusses the latter sense. <span class="selfreference">(For more on the other sense, see <i><a href="/wiki/Persona_(user_experience)" title="Persona (user experience)">Persona (user experience)</a></i>.)</span> </p> <div class="mw-heading mw-heading2"><h2 id="History">History</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=2" title="Edit section: History"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>In 1987, <a href="/wiki/Ivar_Jacobson" title="Ivar Jacobson">Ivar Jacobson</a> presented the first article on use cases at the <a href="/wiki/OOPSLA" title="OOPSLA">OOPSLA</a>'87 conference.<sup id="cite_ref-:1_1-0" class="reference"><a href="#cite_note-:1-1"><span class="cite-bracket">&#91;</span>1<span class="cite-bracket">&#93;</span></a></sup> He described how this technique was used at <a href="/wiki/Ericsson" title="Ericsson">Ericsson</a> to capture and specify requirements of a system using textual, structural, and <a href="/wiki/Visual_modeling" title="Visual modeling">visual modeling</a> techniques to drive object-oriented analysis and design.<sup id="cite_ref-:2_2-0" class="reference"><a href="#cite_note-:2-2"><span class="cite-bracket">&#91;</span>2<span class="cite-bracket">&#93;</span></a></sup> Originally he had used the terms <i>usage scenarios</i> and <i>usage case</i> – the latter a direct translation of his Swedish term <i>användningsfall</i> – but found that neither of these terms sounded natural in English, and eventually he settled on <i>use case</i>.<sup id="cite_ref-Cockburn_3-0" class="reference"><a href="#cite_note-Cockburn-3"><span class="cite-bracket">&#91;</span>3<span class="cite-bracket">&#93;</span></a></sup> </p><p>In 1992 he co-authored the book <i>Object-Oriented Software Engineering - A Use Case Driven Approach</i>,<sup id="cite_ref-:3_4-0" class="reference"><a href="#cite_note-:3-4"><span class="cite-bracket">&#91;</span>4<span class="cite-bracket">&#93;</span></a></sup> which laid the foundation of the <a href="/wiki/Object-oriented_software_engineering" class="mw-redirect" title="Object-oriented software engineering">OOSE</a> system engineering method and helped to popularize use cases for capturing <a href="/wiki/Functional_requirements" class="mw-redirect" title="Functional requirements">functional requirements</a>, especially in <a href="/wiki/Software_development" title="Software development">software development</a>. In 1994 he published a book about use cases and object-oriented techniques applied to <a href="/wiki/Business_model" title="Business model">business models</a> and <a href="/wiki/Business_process_re-engineering" title="Business process re-engineering">business process reengineering</a>.<sup id="cite_ref-:4_5-0" class="reference"><a href="#cite_note-:4-5"><span class="cite-bracket">&#91;</span>5<span class="cite-bracket">&#93;</span></a></sup> </p><p>At the same time, <a href="/wiki/Grady_Booch" title="Grady Booch">Grady Booch</a> and <a href="/wiki/James_Rumbaugh" title="James Rumbaugh">James Rumbaugh</a> worked at unifying their <a href="/wiki/Object-oriented_analysis_and_design" title="Object-oriented analysis and design">object-oriented analysis and design</a> methods, the <a href="/wiki/Booch_method" class="mw-redirect" title="Booch method">Booch method</a> and <a href="/wiki/Object-modeling_technique" title="Object-modeling technique">Object Modeling Technique (OMT)</a> respectively. In 1995 Ivar Jacobson joined them and together they created the <a href="/wiki/Unified_Modeling_Language" title="Unified Modeling Language">Unified Modelling Language (UML)</a>, which includes use case modeling. UML was standardized by the <a href="/wiki/Object_Management_Group" title="Object Management Group">Object Management Group (OMG)</a> in 1997.<sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">&#91;</span>6<span class="cite-bracket">&#93;</span></a></sup> Jacobson, Booch and Rumbaugh also worked on a refinement of the <a href="/wiki/Objectory" title="Objectory">Objectory</a> software development process. The resulting <a href="/wiki/Unified_Process" class="mw-redirect" title="Unified Process">Unified Process</a> was published in 1999 and promoted a use case driven approach.<sup id="cite_ref-:5_7-0" class="reference"><a href="#cite_note-:5-7"><span class="cite-bracket">&#91;</span>7<span class="cite-bracket">&#93;</span></a></sup> </p><p>Since then, many authors have contributed to the development of the technique, notably: <a href="/wiki/Larry_Constantine" title="Larry Constantine">Larry Constantine</a> developed in 1995, in the context of <a href="/wiki/Usage-centered_design" title="Usage-centered design">usage-centered design</a>, so called "essential use-cases" that aim to describe user intents rather than sequences of actions or scenarios which might constrain or bias the design of user interface;<sup id="cite_ref-:6_8-0" class="reference"><a href="#cite_note-:6-8"><span class="cite-bracket">&#91;</span>8<span class="cite-bracket">&#93;</span></a></sup> <a href="/wiki/Alistair_Cockburn" title="Alistair Cockburn">Alistair Cockburn</a> published in 2000 a goal-oriented use case practice based on text narratives and tabular specifications;<sup id="cite_ref-:7_9-0" class="reference"><a href="#cite_note-:7-9"><span class="cite-bracket">&#91;</span>9<span class="cite-bracket">&#93;</span></a></sup> Kurt Bittner and Ian Spence developed in 2002 advanced practices for analyzing functional requirements with use cases;<sup id="cite_ref-:8_10-0" class="reference"><a href="#cite_note-:8-10"><span class="cite-bracket">&#91;</span>10<span class="cite-bracket">&#93;</span></a></sup> Dean Leffingwell and Don Widrig proposed to apply use cases to change management and stakeholder communication activities;<sup id="cite_ref-11" class="reference"><a href="#cite_note-11"><span class="cite-bracket">&#91;</span>11<span class="cite-bracket">&#93;</span></a></sup> Gunnar Overgaard proposed in 2004 to extend the principles of design patterns to use cases.<sup id="cite_ref-12" class="reference"><a href="#cite_note-12"><span class="cite-bracket">&#91;</span>12<span class="cite-bracket">&#93;</span></a></sup> </p><p>In 2011, Jacobson published with Ian Spence and Kurt Bittner the ebook <i>Use Case 2.0</i> to adapt the technique to an agile context, enriching it with incremental use case "slices", and promoting its use across the full development lifecycle<sup id="cite_ref-:0_13-0" class="reference"><a href="#cite_note-:0-13"><span class="cite-bracket">&#91;</span>13<span class="cite-bracket">&#93;</span></a></sup> after having presented the renewed approach at the annual <a href="/w/index.php?title=International_Institute_of_Business_Analysis&amp;action=edit&amp;redlink=1" class="new" title="International Institute of Business Analysis (page does not exist)">IIBA</a> conference.<sup id="cite_ref-14" class="reference"><a href="#cite_note-14"><span class="cite-bracket">&#91;</span>14<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-15" class="reference"><a href="#cite_note-15"><span class="cite-bracket">&#91;</span>15<span class="cite-bracket">&#93;</span></a></sup> </p> <div class="mw-heading mw-heading2"><h2 id="General_principle">General principle</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=3" title="Edit section: General principle"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Use cases are a technique for capturing, modeling, and specifying the requirements of a system.<sup id="cite_ref-:8_10-1" class="reference"><a href="#cite_note-:8-10"><span class="cite-bracket">&#91;</span>10<span class="cite-bracket">&#93;</span></a></sup> A use case corresponds to a set of behaviors that the system may perform in interaction with its actors, and which produces an observable result that contributes to its goals. Actors represent the role that human users or other systems have in the interaction. </p><p>In the <a href="/wiki/Requirements_analysis" title="Requirements analysis">requirement analysis</a>, at their identification, a use case is named according to the specific user goal that it represents for its primary actor. The case is further detailed with a textual description or with additional graphical models that explain the general sequence of activities and events, as well as variants such as special conditions, exceptions, or error situations. </p><p>According to the <a href="/wiki/Software_Engineering_Body_of_Knowledge" title="Software Engineering Body of Knowledge">Software Engineering Body of Knowledge (SWEBOK)</a>,<sup id="cite_ref-16" class="reference"><a href="#cite_note-16"><span class="cite-bracket">&#91;</span>16<span class="cite-bracket">&#93;</span></a></sup> use cases belong to the scenario-based <a href="/wiki/Requirements_elicitation" title="Requirements elicitation">requirement elicitation</a> techniques, as well as the <a href="/wiki/Model-based_systems_engineering" title="Model-based systems engineering">model-based analysis</a>, techniques. But the use cases also support narrative-based requirement gathering, incremental requirement acquisition, system documentation, and acceptance testing.<sup id="cite_ref-:1_1-1" class="reference"><a href="#cite_note-:1-1"><span class="cite-bracket">&#91;</span>1<span class="cite-bracket">&#93;</span></a></sup> </p> <div class="mw-heading mw-heading3"><h3 id="Variations">Variations</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=4" title="Edit section: Variations"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>There are different kinds of use cases and variations in the technique: </p> <ul><li>System use cases specify the requirements of a system to be developed.<sup id="cite_ref-:2_2-1" class="reference"><a href="#cite_note-:2-2"><span class="cite-bracket">&#91;</span>2<span class="cite-bracket">&#93;</span></a></sup> They identify in their detailed description not only the interactions with the actors but also the entities that are involved in the processing. They are the starting point for further analysis models and design activities.</li> <li>Business use cases focus on a business organization instead of a software system. They are used to specify business models and business process requirements in the context of business process reengineering initiatives.<sup id="cite_ref-:4_5-1" class="reference"><a href="#cite_note-:4-5"><span class="cite-bracket">&#91;</span>5<span class="cite-bracket">&#93;</span></a></sup></li> <li>Essential use cases, also called abstract use cases, describe the potential intents of the actors and how the system addresses these, without defining any sequence or describing a scenario.<sup id="cite_ref-:6_8-1" class="reference"><a href="#cite_note-:6-8"><span class="cite-bracket">&#91;</span>8<span class="cite-bracket">&#93;</span></a></sup> This practice was developed with the aim of supporting the user-centric design and avoiding to induce bias about the user interface in the early stage of the system specifications.<sup id="cite_ref-:5_7-1" class="reference"><a href="#cite_note-:5-7"><span class="cite-bracket">&#91;</span>7<span class="cite-bracket">&#93;</span></a></sup></li> <li>Use Case 2.0 to adapt the technique for the context of agile development methods.<sup id="cite_ref-:1_1-2" class="reference"><a href="#cite_note-:1-1"><span class="cite-bracket">&#91;</span>1<span class="cite-bracket">&#93;</span></a></sup> This technique enriches the requirement-gathering practice with support for user-story narratives. It also provides use case "slices" to facilitate incremental elicitation of requirements and enable incremental implementation.</li></ul> <div class="mw-heading mw-heading3"><h3 id="Scope">Scope</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=5" title="Edit section: Scope"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>The scope of a use case can be defined by a subject and by goals: </p> <ul><li>The subject identifies the system, sub-system, or component that will provide the interactions.<sup id="cite_ref-:9_17-0" class="reference"><a href="#cite_note-:9-17"><span class="cite-bracket">&#91;</span>17<span class="cite-bracket">&#93;</span></a></sup></li> <li>The goals can be structured hierarchically, taking into account the organizational level interested in the goal (e.g. company, department, user), and the decomposition of the user's goal into sub-goals.<sup id="cite_ref-:7_9-1" class="reference"><a href="#cite_note-:7-9"><span class="cite-bracket">&#91;</span>9<span class="cite-bracket">&#93;</span></a></sup> The decomposition of the goal is performed from the point of view of the users, and independently of the system, which differs from traditional functional decomposition.<sup id="cite_ref-:8_10-2" class="reference"><a href="#cite_note-:8-10"><span class="cite-bracket">&#91;</span>10<span class="cite-bracket">&#93;</span></a></sup> &#160;</li></ul> <div class="mw-heading mw-heading3"><h3 id="Usage">Usage</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=6" title="Edit section: Usage"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Use cases are known to be applied in the following contexts: </p> <ul><li><a href="/wiki/Object-oriented_software_engineering" class="mw-redirect" title="Object-oriented software engineering">Object Oriented Software Engineering (OOSE)</a>, as driving element;<sup id="cite_ref-:3_4-1" class="reference"><a href="#cite_note-:3-4"><span class="cite-bracket">&#91;</span>4<span class="cite-bracket">&#93;</span></a></sup></li> <li><a href="/wiki/Unified_Modeling_Language" title="Unified Modeling Language">Unified Modeling Language</a> (UML), as a behavioral modelling instrument;<sup id="cite_ref-:9_17-1" class="reference"><a href="#cite_note-:9-17"><span class="cite-bracket">&#91;</span>17<span class="cite-bracket">&#93;</span></a></sup></li> <li><a href="/wiki/Unified_Process" class="mw-redirect" title="Unified Process">Unified Software Development Process (UP)</a> and its fore-runner, the <a href="/wiki/IBM" title="IBM">IBM</a> <a href="/wiki/Rational_Unified_Process" class="mw-redirect" title="Rational Unified Process">Rational Unified Process (RUP)</a>;<sup id="cite_ref-:5_7-2" class="reference"><a href="#cite_note-:5-7"><span class="cite-bracket">&#91;</span>7<span class="cite-bracket">&#93;</span></a></sup></li> <li>up-front documentation of <a href="/wiki/Software_requirements_specification" title="Software requirements specification">software requirements specification</a> (SRS), as an alternative structure for the functional requirements;<sup id="cite_ref-18" class="reference"><a href="#cite_note-18"><span class="cite-bracket">&#91;</span>18<span class="cite-bracket">&#93;</span></a></sup></li> <li>deriving the design from the requirements using the <a href="/wiki/Entity%E2%80%93control%E2%80%93boundary" title="Entity–control–boundary">entity–control–boundary</a> approach;<sup id="cite_ref-:5_7-3" class="reference"><a href="#cite_note-:5-7"><span class="cite-bracket">&#91;</span>7<span class="cite-bracket">&#93;</span></a></sup></li> <li>and <a href="/wiki/Agile_software_development" title="Agile software development">agile development</a>.<sup id="cite_ref-:1_1-3" class="reference"><a href="#cite_note-:1-1"><span class="cite-bracket">&#91;</span>1<span class="cite-bracket">&#93;</span></a></sup><sup id="cite_ref-19" class="reference"><a href="#cite_note-19"><span class="cite-bracket">&#91;</span>19<span class="cite-bracket">&#93;</span></a></sup></li></ul> <div class="mw-heading mw-heading2"><h2 id="Templates">Templates</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=7" title="Edit section: Templates"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>There are many ways to write a use case in the text, from <i>use case brief</i>, <i>casual</i>, <i>outline</i>, to <i>fully dressed</i> etc., and with varied templates. Writing use cases in templates devised by various vendors or experts is a common industry practice to get high-quality functional system requirements. </p> <div class="mw-heading mw-heading3"><h3 id="Cockburn_style">Cockburn style</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=8" title="Edit section: Cockburn style"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>The template defined by <a href="/wiki/Alistair_Cockburn" title="Alistair Cockburn">Alistair Cockburn</a> in his book <i>Writing Effective Use Cases</i> has been one of the most widely used writing styles of use cases.<sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed"><span title="This claim needs references to reliable sources. (March 2016)">citation needed</span></a></i>&#93;</sup> </p> <div class="mw-heading mw-heading4"><h4 id="Design_scopes">Design scopes</h4><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=9" title="Edit section: Design scopes"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Cockburn suggests annotating each use case with a symbol to show the "Design Scope", which may be black-box (internal detail is hidden) or white box (internal detail is shown). Five symbols are available:<sup id="cite_ref-20" class="reference"><a href="#cite_note-20"><span class="cite-bracket">&#91;</span>20<span class="cite-bracket">&#93;</span></a></sup> </p> <table class="wikitable"> <tbody><tr> <th>Scope</th> <th>Icon</th> <th> </th></tr> <tr> <td>Organization (black-box)</td> <td>Filled House</td> <td><span class="mw-default-size" typeof="mw:File"><a href="/wiki/File:Scope-icons-filled-house.png" class="mw-file-description" title="Scope-icons-filled-house"><img alt="Scope-icons-filled-house" src="//upload.wikimedia.org/wikipedia/commons/f/fd/Scope-icons-filled-house.png" decoding="async" width="52" height="52" class="mw-file-element" data-file-width="52" data-file-height="52" /></a></span> </td></tr> <tr> <td>Organization (white-box)</td> <td>Unfilled House</td> <td><figure class="mw-default-size mw-halign-center" typeof="mw:File"><a href="/wiki/File:Scope-icons-unfilled-house.png" class="mw-file-description" title="Scope-icons-unfilled-house"><img alt="Scope-icons-unfilled-house" src="//upload.wikimedia.org/wikipedia/commons/c/c8/Scope-icons-unfilled-house.png" decoding="async" width="52" height="52" class="mw-file-element" data-file-width="52" data-file-height="52" /></a><figcaption>Scope-icons-unfilled-house</figcaption></figure> </td></tr> <tr> <td>System (black-box)</td> <td>Filled Box</td> <td><figure class="mw-default-size mw-halign-center" typeof="mw:File"><a href="/wiki/File:Scope-icons-filled-box.png" class="mw-file-description" title="Scope-icons-filled-box"><img alt="Scope-icons-filled-box" src="//upload.wikimedia.org/wikipedia/commons/2/2a/Scope-icons-filled-box.png" decoding="async" width="52" height="52" class="mw-file-element" data-file-width="52" data-file-height="52" /></a><figcaption>Scope-icons-filled-box</figcaption></figure> </td></tr> <tr> <td>System (white-box)</td> <td>Unfilled Box</td> <td><figure class="mw-default-size mw-halign-center" typeof="mw:File"><a href="/wiki/File:Scope-icons-unfilled-box.png" class="mw-file-description" title="Scope-icons-unfilled-box"><img alt="Scope-icons-unfilled-box" src="//upload.wikimedia.org/wikipedia/commons/c/c8/Scope-icons-unfilled-box.png" decoding="async" width="52" height="52" class="mw-file-element" data-file-width="52" data-file-height="52" /></a><figcaption>Scope-icons-unfilled-box</figcaption></figure> </td></tr> <tr> <td>Component</td> <td>Screw or Bolt</td> <td><figure class="mw-default-size mw-halign-center" typeof="mw:File"><a href="/wiki/File:Scope-icons-screw-bolt.png" class="mw-file-description" title="Scope-icons-screw-bolt"><img alt="Scope-icons-screw-bolt" src="//upload.wikimedia.org/wikipedia/commons/9/93/Scope-icons-screw-bolt.png" decoding="async" width="52" height="52" class="mw-file-element" data-file-width="52" data-file-height="52" /></a><figcaption>Scope-icons-screw-bolt</figcaption></figure> </td></tr></tbody></table> <div style="clear:both;" class=""></div> <p>Other authors sometimes call use cases at the Organization level "Business use cases".<sup id="cite_ref-21" class="reference"><a href="#cite_note-21"><span class="cite-bracket">&#91;</span>21<span class="cite-bracket">&#93;</span></a></sup> </p> <div class="mw-heading mw-heading4"><h4 id="Goal_levels">Goal levels</h4><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=10" title="Edit section: Goal levels"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <figure class="mw-default-size" typeof="mw:File/Thumb"><a href="/wiki/File:Cockburnstyle_use_cases.svg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/8/82/Cockburnstyle_use_cases.svg/220px-Cockburnstyle_use_cases.svg.png" decoding="async" width="220" height="110" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/8/82/Cockburnstyle_use_cases.svg/330px-Cockburnstyle_use_cases.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/8/82/Cockburnstyle_use_cases.svg/440px-Cockburnstyle_use_cases.svg.png 2x" data-file-width="1600" data-file-height="800" /></a><figcaption>Hierarchy of goal levels</figcaption></figure> <p>Cockburn suggests annotating each use case with a symbol to show the "Goal Level";<sup id="cite_ref-22" class="reference"><a href="#cite_note-22"><span class="cite-bracket">&#91;</span>22<span class="cite-bracket">&#93;</span></a></sup> the preferred level is "User-goal" (or colloquially "sea level"<sup id="cite_ref-Fowler_23-0" class="reference"><a href="#cite_note-Fowler-23"><span class="cite-bracket">&#91;</span>23<span class="cite-bracket">&#93;</span></a></sup><sup class="reference nowrap"><span title="Page / location: 101">&#58;&#8202;101&#8202;</span></sup>). </p> <table class="wikitable"> <tbody><tr> <th>Goal Level</th> <th>Icon</th> <th>Symbol</th> <th> </th></tr> <tr> <td>Very High Summary</td> <td>Cloud</td> <td>++</td> <td><figure class="mw-default-size mw-halign-center" typeof="mw:File"><a href="/wiki/File:Goal-level-icons-cloud.png" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/c/c6/Goal-level-icons-cloud.png" decoding="async" width="52" height="52" class="mw-file-element" data-file-width="52" data-file-height="52" /></a><figcaption></figcaption></figure> </td></tr> <tr> <td>Summary</td> <td>Flying Kite</td> <td>+</td> <td><figure class="mw-default-size mw-halign-center" typeof="mw:File"><a href="/wiki/File:Goal-level-icons-flying-kite.png" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/4/41/Goal-level-icons-flying-kite.png" decoding="async" width="52" height="52" class="mw-file-element" data-file-width="52" data-file-height="52" /></a><figcaption></figcaption></figure> </td></tr> <tr> <td>User Goal</td> <td>Waves at Sea</td> <td>!</td> <td><figure class="mw-default-size mw-halign-center" typeof="mw:File"><a href="/wiki/File:Goal-level-icons-waves-at-sea.png" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/b/bb/Goal-level-icons-waves-at-sea.png" decoding="async" width="52" height="52" class="mw-file-element" data-file-width="52" data-file-height="52" /></a><figcaption></figcaption></figure> </td></tr> <tr> <td>Subfunction</td> <td>Fish</td> <td>-</td> <td><figure class="mw-default-size mw-halign-center" typeof="mw:File"><a href="/wiki/File:Goal-level-icons-fish.png" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/e/ec/Goal-level-icons-fish.png" decoding="async" width="52" height="52" class="mw-file-element" data-file-width="52" data-file-height="52" /></a><figcaption></figcaption></figure> </td></tr> <tr> <td>Too Low</td> <td>Seabed Clam-Shell</td> <td>--</td> <td><figure class="mw-default-size mw-halign-center" typeof="mw:File"><a href="/wiki/File:Goal-level-icons-seabed-clam-shell.png" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/2/21/Goal-level-icons-seabed-clam-shell.png" decoding="async" width="52" height="52" class="mw-file-element" data-file-width="52" data-file-height="52" /></a><figcaption></figcaption></figure> </td></tr></tbody></table> <div style="clear:both;" class=""></div> <p>Sometimes in text writing, a use case name followed by an alternative text symbol (! +, -, etc.) is a more concise and convenient way to denote levels, e.g. <i>place an order!</i>, <i>login-</i>. </p> <div class="mw-heading mw-heading4"><h4 id="Fully_dressed">Fully dressed</h4><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=11" title="Edit section: Fully dressed"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Cockburn describes a more detailed structure for a use case but permits it to be simplified when less detail is needed. His fully dressed use case template lists the following fields:<sup id="cite_ref-Cockburn120_24-0" class="reference"><a href="#cite_note-Cockburn120-24"><span class="cite-bracket">&#91;</span>24<span class="cite-bracket">&#93;</span></a></sup> </p> <ul><li>Title: "an active-verb goal phrase that names the goal of the primary actor"<sup id="cite_ref-25" class="reference"><a href="#cite_note-25"><span class="cite-bracket">&#91;</span>25<span class="cite-bracket">&#93;</span></a></sup></li> <li>Primary Actor</li> <li>Goal in Context</li> <li>Scope</li> <li>Level</li> <li>Stakeholders and Interests</li> <li>Precondition</li> <li>Minimal Guarantees</li> <li>Success Guarantees</li> <li>Trigger</li> <li>Main Success Scenario</li> <li>Extensions</li> <li>Technology &amp; Data Variations List</li></ul> <p>In addition, Cockburn suggests using two devices to indicate the nature of each use case: icons for design scope and goal level. </p><p>Cockburn's approach has influenced other authors; for example, Alexander and Beus-Dukic generalize Cockburn's "Fully dressed use case" template from software to systems of all kinds, with the following fields differing from Cockburn:<sup id="cite_ref-26" class="reference"><a href="#cite_note-26"><span class="cite-bracket">&#91;</span>26<span class="cite-bracket">&#93;</span></a></sup> </p> <ul><li>Variation scenarios "(maybe branching off from and maybe returning to the main scenario)"</li> <li>Exceptions "i.e. exception events and their exception-handling scenarios"</li></ul> <div class="mw-heading mw-heading4"><h4 id="Casual">Casual</h4><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=12" title="Edit section: Casual"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Cockburn recognizes that projects may not always need detailed "fully dressed" use cases. He describes a Casual use case with the fields:<sup id="cite_ref-Cockburn120_24-1" class="reference"><a href="#cite_note-Cockburn120-24"><span class="cite-bracket">&#91;</span>24<span class="cite-bracket">&#93;</span></a></sup> </p> <ul><li>Title (goal)</li> <li>Primary Actor</li> <li>Scope</li> <li>Level</li> <li>(Story): the body of the use case is simply a paragraph or two of text, informally describing what happens.</li></ul> <div class="mw-heading mw-heading3"><h3 id="Fowler_style">Fowler style</h3><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=13" title="Edit section: Fowler style"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p><a href="/wiki/Martin_Fowler_(software_engineer)" title="Martin Fowler (software engineer)">Martin Fowler</a> states "There is no standard way to write the content of a use case, and different formats work well in different cases."<sup id="cite_ref-Fowler_23-1" class="reference"><a href="#cite_note-Fowler-23"><span class="cite-bracket">&#91;</span>23<span class="cite-bracket">&#93;</span></a></sup><sup class="reference nowrap"><span title="Page / location: 100">&#58;&#8202;100&#8202;</span></sup> He describes "a common style to use" as follows:<sup id="cite_ref-Fowler_23-2" class="reference"><a href="#cite_note-Fowler-23"><span class="cite-bracket">&#91;</span>23<span class="cite-bracket">&#93;</span></a></sup><sup class="reference nowrap"><span title="Page / location: 101">&#58;&#8202;101&#8202;</span></sup> </p> <ul><li>Title: "goal the use case is trying to satisfy"<sup id="cite_ref-Fowler_23-3" class="reference"><a href="#cite_note-Fowler-23"><span class="cite-bracket">&#91;</span>23<span class="cite-bracket">&#93;</span></a></sup><sup class="reference nowrap"><span title="Page / location: 101">&#58;&#8202;101&#8202;</span></sup></li> <li>Main Success Scenario: numbered list of steps<sup id="cite_ref-Fowler_23-4" class="reference"><a href="#cite_note-Fowler-23"><span class="cite-bracket">&#91;</span>23<span class="cite-bracket">&#93;</span></a></sup><sup class="reference nowrap"><span title="Page / location: 101">&#58;&#8202;101&#8202;</span></sup> <ul><li>Step: "a simple statement of the interaction between the actor and a system"<sup id="cite_ref-Fowler_23-5" class="reference"><a href="#cite_note-Fowler-23"><span class="cite-bracket">&#91;</span>23<span class="cite-bracket">&#93;</span></a></sup><sup class="reference nowrap"><span title="Page / location: 101">&#58;&#8202;101&#8202;</span></sup></li></ul></li> <li>Extensions: separately numbered lists, one per Extension<sup id="cite_ref-Fowler_23-6" class="reference"><a href="#cite_note-Fowler-23"><span class="cite-bracket">&#91;</span>23<span class="cite-bracket">&#93;</span></a></sup><sup class="reference nowrap"><span title="Page / location: 101">&#58;&#8202;101&#8202;</span></sup> <ul><li>Extension: "a condition that results in different interactions from .. the main success scenario". An extension from main step 3 is numbered 3a, etc.<sup id="cite_ref-Fowler_23-7" class="reference"><a href="#cite_note-Fowler-23"><span class="cite-bracket">&#91;</span>23<span class="cite-bracket">&#93;</span></a></sup><sup class="reference nowrap"><span title="Page / location: 101">&#58;&#8202;101&#8202;</span></sup></li></ul></li></ul> <p>The Fowler style can also be viewed as a simplified variant of the Cockburn template. This variant is called a <a href="/wiki/User_story" title="User story">user story</a>. </p><p>Alistair Cockburn stated:<sup id="cite_ref-wiki.c2.com_27-0" class="reference"><a href="#cite_note-wiki.c2.com-27"><span class="cite-bracket">&#91;</span>27<span class="cite-bracket">&#93;</span></a></sup> </p> <style data-mw-deduplicate="TemplateStyles:r1244412712">.mw-parser-output .templatequote{overflow:hidden;margin:1em 0;padding:0 32px}.mw-parser-output .templatequotecite{line-height:1.5em;text-align:left;margin-top:0}@media(min-width:500px){.mw-parser-output .templatequotecite{padding-left:1.6em}}</style><blockquote class="templatequote"><p>Think of a User Story as a Use Case at 2 bits of precision. Bit 1 of precision names the goal of the use case, and Bit 2 adds the main scenario. Bit 3 adds the failure conditions, Bit 4 adds the failure actions. Bit 5 adds a data description of the in/out data. I would put Catalysis at the 6th bit of precision, as they include a model also of the recipient of the message. In the CrystalMethodology family, differently founded projects use cases at different levels of precision. A methodologically light project uses User Stories, a methodologically heavier project uses Use Cases to 4 bits of precision, and Catalysis uses 6 bits of precision.</p></blockquote> <p>Martin Fowler stated:<sup id="cite_ref-wiki.c2.com_27-1" class="reference"><a href="#cite_note-wiki.c2.com-27"><span class="cite-bracket">&#91;</span>27<span class="cite-bracket">&#93;</span></a></sup> </p> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1244412712"><blockquote class="templatequote"><p>It is all about how people use cases. I've seen many people use cases in a very formalized manner. Kent does his UserStories in a much more approachable manner. I do use cases the way Kent does User Stories. I call them to use cases to better communicate with other developers and to influence them to use a more lightweight approach.</p></blockquote> <div class="mw-heading mw-heading2"><h2 id="Actors">Actors</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=14" title="Edit section: Actors"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236090951"><div role="note" class="hatnote navigation-not-searchable">Main article: <a href="/wiki/Actor_(UML)" title="Actor (UML)">Actor (UML)</a></div> <p>A use case defines the interactions between external actors and the system under consideration to accomplish a goal. Actors must be able to make decisions, but need not be human: "An actor might be a person, a company or organization, a computer program, or a computer system—hardware, software, or both."<sup id="cite_ref-Cockburn53_28-0" class="reference"><a href="#cite_note-Cockburn53-28"><span class="cite-bracket">&#91;</span>28<span class="cite-bracket">&#93;</span></a></sup> Actors are always <a href="/wiki/Project_stakeholder" title="Project stakeholder">stakeholders</a>, but not all stakeholders are actors, since they may "never interact directly with the system, even though they have the right to care how the system behaves."<sup id="cite_ref-Cockburn53_28-1" class="reference"><a href="#cite_note-Cockburn53-28"><span class="cite-bracket">&#91;</span>28<span class="cite-bracket">&#93;</span></a></sup> For example, "the owners of the system, the company's board of directors, and regulatory bodies such as the Internal Revenue Service and the Department of Insurance" could all be stakeholders but are unlikely to be actors.<sup id="cite_ref-Cockburn53_28-2" class="reference"><a href="#cite_note-Cockburn53-28"><span class="cite-bracket">&#91;</span>28<span class="cite-bracket">&#93;</span></a></sup> </p><p>Similarly, a person using a system may be represented as a different actor because of playing different roles. For example, user "Joe" could be playing the role of a Customer when using an Automated Teller Machine to withdraw cash from his own account or playing the role of a Bank Teller when using the system to restock the cash drawer on behalf of the bank. </p><p>Actors are often working on behalf of someone else. Cockburn writes that "These days I write 'sales rep for the customer' or 'clerk for the marketing department' to capture that the user of the system is acting for someone else." This tells the project that the "user interface and security clearances" should be designed for the sales rep and clerk, but that the customer and marketing department are the roles concerned about the results.<sup id="cite_ref-Cockburn55_29-0" class="reference"><a href="#cite_note-Cockburn55-29"><span class="cite-bracket">&#91;</span>29<span class="cite-bracket">&#93;</span></a></sup> </p><p>A stakeholder may play both an active and an inactive role: for example, a Consumer is both a "mass-market purchaser" (not interacting with the system) and a User (an actor, actively interacting with the purchased product).<sup id="cite_ref-AB39_30-0" class="reference"><a href="#cite_note-AB39-30"><span class="cite-bracket">&#91;</span>30<span class="cite-bracket">&#93;</span></a></sup> In turn, a User is both a "normal operator" (an actor using the system for its intended purpose) and a "functional beneficiary" (a stakeholder who benefits from the use of the system).<sup id="cite_ref-AB39_30-1" class="reference"><a href="#cite_note-AB39-30"><span class="cite-bracket">&#91;</span>30<span class="cite-bracket">&#93;</span></a></sup> For example, when user "Joe" withdraws cash from his account, he is operating the Automated Teller Machine and obtaining a result on his own behalf. </p><p>Cockburn advises looking for actors among the stakeholders of a system, the primary and supporting (secondary) actors of a use case, the system under design (SuD) itself, and finally among the "internal actors", namely the components of the system under design.<sup id="cite_ref-Cockburn53_28-3" class="reference"><a href="#cite_note-Cockburn53-28"><span class="cite-bracket">&#91;</span>28<span class="cite-bracket">&#93;</span></a></sup> </p> <div class="mw-heading mw-heading2"><h2 id="Business_use_case">Business use case</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=15" title="Edit section: Business use case"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div><p> In the same way that a use case describes a series of events and interactions between a user (or other types of Actor) and a system, in order to produce a result of value (goal), a business use case describes the more general interaction between a business system and the users/actors of that system to produce business results of value. The primary difference is that the system considered in a business use case model may contain people in addition to technological systems. These "people in the system" are called business workers. In the example of a restaurant, a decision must be made whether to treat each person as an actor (thus outside the system) or a business worker (inside the system). If a waiter is considered an actor, as shown in the example below, then the restaurant system does not include the waiter, and the model exposes the interaction between the waiter and the restaurant. An alternative would be to consider the waiter as a part of the restaurant system (a business worker) while considering the client to be outside the system (an actor).<sup id="cite_ref-31" class="reference"><a href="#cite_note-31"><span class="cite-bracket">&#91;</span>31<span class="cite-bracket">&#93;</span></a></sup></p><figure class="mw-halign-center" typeof="mw:File/Thumb"><a href="/wiki/File:Use_case_restaurant_model.svg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/1/1d/Use_case_restaurant_model.svg/320px-Use_case_restaurant_model.svg.png" decoding="async" width="320" height="320" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/1/1d/Use_case_restaurant_model.svg/480px-Use_case_restaurant_model.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/1/1d/Use_case_restaurant_model.svg/640px-Use_case_restaurant_model.svg.png 2x" data-file-width="496" data-file-height="496" /></a><figcaption>A business <a href="/wiki/Use_case_diagram" title="Use case diagram">Use case diagram</a> depicts a model of several <i>business use cases</i> (goals) which represents the interactions between a restaurant (the business system) and its primary stakeholders (<i>business actors</i> and <i>business workers</i>).</figcaption></figure> <div class="mw-heading mw-heading2"><h2 id="Visual_modeling">Visual modeling</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=16" title="Edit section: Visual modeling"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374"><style data-mw-deduplicate="TemplateStyles:r1126788409">.mw-parser-output .plainlist ol,.mw-parser-output .plainlist ul{line-height:inherit;list-style:none;margin:0;padding:0}.mw-parser-output .plainlist ol li,.mw-parser-output .plainlist ul li{margin-bottom:0}</style><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1246091330"><table class="sidebar nomobile nowraplinks"><tbody><tr><th class="sidebar-title" style="background-color:#eecd9c"><a href="/wiki/Unified_Modeling_Language#Diagrams" title="Unified Modeling Language">UML diagram types</a></th></tr><tr><th class="sidebar-heading" style="background-color:#FFDEAD"> Structural UML diagrams</th></tr><tr><td class="sidebar-content plainlist" style="text-align:left"> <ul><li><a href="/wiki/Class_diagram" title="Class diagram">Class diagram</a></li> <li><a href="/wiki/Component_diagram" title="Component diagram">Component diagram</a></li> <li><a href="/wiki/Composite_structure_diagram" title="Composite structure diagram">Composite structure diagram</a></li> <li><a href="/wiki/Deployment_diagram" title="Deployment diagram">Deployment diagram</a></li> <li><a href="/wiki/Object_diagram" title="Object diagram">Object diagram</a></li> <li><a href="/wiki/Package_diagram" title="Package diagram">Package diagram</a></li> <li><a href="/wiki/Profile_diagram" title="Profile diagram">Profile diagram</a></li></ul></td> </tr><tr><th class="sidebar-heading" style="background-color:#FFDEAD"> Behavioral UML diagrams</th></tr><tr><td class="sidebar-content plainlist" style="text-align:left"> <ul><li><a href="/wiki/Activity_diagram" title="Activity diagram">Activity diagram</a></li> <li><a href="/wiki/Communication_diagram" title="Communication diagram">Communication diagram</a></li> <li><a href="/wiki/Interaction_overview_diagram" title="Interaction overview diagram">Interaction overview diagram</a></li> <li><a href="/wiki/Sequence_diagram" title="Sequence diagram">Sequence diagram</a></li> <li><a href="/wiki/UML_state_machine" title="UML state machine">State diagram</a></li> <li><a href="/wiki/Timing_diagram_(Unified_Modeling_Language)" title="Timing diagram (Unified Modeling Language)">Timing diagram</a></li> <li><a href="/wiki/Use_case_diagram" title="Use case diagram">Use case diagram</a></li></ul></td> </tr><tr><td class="sidebar-navbar"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1239400231"><div class="navbar plainlinks hlist navbar-mini"><ul><li class="nv-view"><a href="/wiki/Template:UML_diagram_types" title="Template:UML diagram types"><abbr title="View this template">v</abbr></a></li><li class="nv-talk"><a href="/w/index.php?title=Template_talk:UML_diagram_types&amp;action=edit&amp;redlink=1" class="new" title="Template talk:UML diagram types (page does not exist)"><abbr title="Discuss this template">t</abbr></a></li><li class="nv-edit"><a href="/wiki/Special:EditPage/Template:UML_diagram_types" title="Special:EditPage/Template:UML diagram types"><abbr title="Edit this template">e</abbr></a></li></ul></div></td></tr></tbody></table> <p>Use cases are not only texts but also diagrams if needed. In the <a href="/wiki/Unified_Modeling_Language" title="Unified Modeling Language">Unified Modeling Language</a>, the relationships between use cases and actors are represented in <a href="/wiki/Use_case_diagram" title="Use case diagram">use case diagrams</a> originally based upon <a href="/wiki/Ivar_Jacobson" title="Ivar Jacobson">Ivar Jacobson</a>'s <a href="/wiki/Objectory" title="Objectory">Objectory</a> notation. <a href="/wiki/SysML" class="mw-redirect" title="SysML">SysML</a> uses the same notation at a system block level. </p><p>In addition, other behavioral UML diagrams such as <a href="/wiki/Activity_diagram" title="Activity diagram">activity diagrams</a>, <a href="/wiki/Sequence_diagram" title="Sequence diagram">sequence diagrams</a>, <a href="/wiki/Communication_diagram" title="Communication diagram">communication diagrams</a>, and <a href="/wiki/UML_state_machine" title="UML state machine">state machine diagrams</a> can also be used to visualize use cases accordingly. Specifically, a <a href="/wiki/System_Sequence_Diagram" class="mw-redirect" title="System Sequence Diagram">System Sequence Diagram</a> (SSD) is a sequence diagram often used to show the interactions between the external actors and the system under design (SuD), usually for visualizing a particular scenario of a use case. </p><p>Use case analysis usually starts by drawing use case diagrams. For agile development, a requirement model of many UML diagrams depicting use cases plus some textual descriptions, notes, or <i>use case briefs</i> would be very lightweight and just enough for small or easy project use. As good complements to use case texts, the visual diagram representations of use cases are also effective facilitating tools for the better understanding, communication, and design of complex system behavioral requirements. </p> <div class="mw-heading mw-heading2"><h2 id="Examples">Examples</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=17" title="Edit section: Examples"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Below is a sample use case written with a slightly modified version of the Cockburn-style template. Note that there are no buttons, controls, forms, or any other UI elements and operations in the basic use case description, where only user goals, subgoals, or intentions are expressed in every step of the basic flow or extensions. This practice makes the requirement specification clearer and maximizes the flexibility of the design and implementation. </p> <figure class="mw-default-size mw-halign-center" typeof="mw:File"><a href="/wiki/File:Edit_an_article.svg" class="mw-file-description"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/9/9d/Edit_an_article.svg/261px-Edit_an_article.svg.png" decoding="async" width="261" height="74" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/9/9d/Edit_an_article.svg/392px-Edit_an_article.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/9/9d/Edit_an_article.svg/522px-Edit_an_article.svg.png 2x" data-file-width="261" data-file-height="74" /></a><figcaption></figcaption></figure> <p><b>Use Case</b>: Edit an article </p><p><b>Primary Actor</b>: Member <i>(Registered User)</i> </p><p><b>Scope</b>: a <a href="/wiki/Wiki" title="Wiki">Wiki</a> system </p><p><b>Level</b>:&#160;! <i>(User goal or sea level)</i> </p><p><b>Brief</b>: <i>(equivalent to a <a href="/wiki/User_story" title="User story">user story</a> or an epic)</i> </p> <dl><dd>The member edits any part (the entire article or just a section) of an article they are reading. Preview and changes comparison are allowed during the editing.</dd></dl> <p><b>Stakeholders</b> </p><p>... </p><p><b>Postconditions</b> </p> <dl><dd><b>Minimal Guarantees</b>:</dd> <dd><b>Success Guarantees</b>: <ul><li>The article is saved and an updated view is shown.</li> <li>An edit record for the article is created by the system, so watchers of the article can be informed of the update later.</li></ul></dd></dl> <p><b>Preconditions</b>: </p> <dl><dd>The article with editing enabled is presented to the member.</dd></dl> <p><b>Triggers</b>: </p> <dl><dd>The member invokes an edit request (for the full article or just one section) on the article.</dd></dl> <p><b>Basic flow</b>: </p> <ol><li>The system provides a new editor area/box filled with all the article's relevant content with an informative edit summary for the member to edit. If the member just wants to edit a section of the report, only the original content of the section is shown, with the section title automatically filled out in the edit summary.</li> <li>The member modifies the article's content until the member is satisfied.</li> <li>The member fills out the edit summary, tells the system if they want to watch this article, and submits the edit.</li> <li>The system saves the article, logs the edit event, and finishes any necessary post-processing.</li> <li>The system presents the updated view of the article to the member.</li></ol> <p><b>Extensions</b>: </p><p>2–3. </p> <dl><dd>a. Show preview: <ol><li>The member selects <i>Show preview</i> which submits the modified content.</li> <li>The system reruns step 1 with the addition of the rendered updated content for preview, and informs the member that his/her edits have not been saved yet, then continues.</li></ol></dd> <dd>b. Show changes: <ol><li>The member selects <i>Show changes</i> which submits the modified content.</li> <li>The system reruns step 1 with the addition of showing the results of comparing the differences between the current edits by the member and the most recent saved version of the article, then continues.</li></ol></dd> <dd>c. Cancel the edit: <ol><li>The member selects <i>Cancel</i>.</li> <li>The system discards any change the member has made, then goes to step 5.</li></ol></dd></dl> <p>4a. Timeout: </p><p>... </p> <div class="mw-heading mw-heading2"><h2 id="Advantages">Advantages</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=18" title="Edit section: Advantages"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Since the inception of the agile movement, the <a href="/wiki/User_story" title="User story">user story</a> technique from <a href="/wiki/Extreme_Programming" class="mw-redirect" title="Extreme Programming">Extreme Programming</a> has been so popular that many think it is the only and best solution for the agile requirements of all projects. <a href="/wiki/Alistair_Cockburn" title="Alistair Cockburn">Alistair Cockburn</a> lists five reasons why he still writes use cases in <a href="/wiki/Agile_development" class="mw-redirect" title="Agile development">agile development</a>.<sup id="cite_ref-32" class="reference"><a href="#cite_note-32"><span class="cite-bracket">&#91;</span>32<span class="cite-bracket">&#93;</span></a></sup> </p> <ol><li>The list of goal names provides the <i>shortest</i> summary of what the system will offer (even then user stories). It also provides a project planning skeleton, to be used to build initial priorities, estimates, team allocation, and timing.</li> <li>The main success scenario of each use case provides everyone involved with an agreement as to what the system will basically do and what it will not do. It provides the context for each specific line item requirement (e.g. fine-grained user stories), a context that is very hard to get anywhere else.</li> <li>The extension conditions of each use case provide a framework for investigating all the little, niggling things that somehow take up 80% of the development time and budget. It provides a look-ahead mechanism, so the stakeholders can spot issues likely to take a long time to get answers for. These issues can and should then be put ahead of the schedule so that the answers can be ready when the development team gets around to working on them.</li> <li>The use case extension scenario fragments provide answers to the many detailed, often tricky, and ignored business questions: "What are we supposed to do in this case?" It is a thinking/documentation framework that matches the if...then...else statement that helps the programmers think through issues. Except it is done at investigation time, not programming time.</li> <li>The full use case set shows that the investigators have thought through every user's needs, every goal they have with respect to the system, and every business variant involved.</li></ol> <p>In summary, specifying system requirements in use cases have these apparent benefits compared with traditional or other approaches: </p><p><b>User focused</b> </p><p>Use cases constitute a powerful, user-centric tool for the software requirements specification process.<sup id="cite_ref-33" class="reference"><a href="#cite_note-33"><span class="cite-bracket">&#91;</span>33<span class="cite-bracket">&#93;</span></a></sup> Use case modeling typically starts from identifying key stakeholder roles (<i>actors</i>) interacting with the system, and their goals or objectives the system must fulfill (an outside perspective). These user goals then become the ideal candidates for the names or titles of the use cases which represent the desired functional features or services provided by the system. This user-centered approach ensures that what has real business value and the user really want is developed, not those trivial functions speculated from a developer or system (inside) perspective. </p><p>Use case authoring has been an important and valuable analysis tool in the domain of <a href="/wiki/User-centered_design" title="User-centered design">User-Centered Design (UCD)</a> for years. </p><p><b>Better communication</b> </p><p>Use cases are often written in natural languages with structured templates. This narrative textual form (legible requirement stories), understandable by almost everyone, and complemented by visual UML diagrams fosters better and deeper communications among all stakeholders, including customers, end-users, developers, testers, and managers. Better communications result in quality requirements and thus quality systems delivered. </p><p><b>Quality requirements by structured exploration</b> </p><p>One of the most powerful things about use cases resides in the formats of the use case <a href="#Templates">templates</a>, especially the main success scenario (basic flow) and the extension scenario fragments (extensions, exceptional and alternative flows). Analyzing a use case step by step from preconditions to postconditions, exploring and investigating every action step of the use case flows, from basic to extensions, to identify those tricky, normally hidden and ignored, seemingly trivial but realistically often costly requirements (as Cockburn mentioned above), is a structured and beneficial way to get clear, stable and quality requirements systematically. </p><p>Minimizing and optimizing the action steps of a use case to achieve the user goal also contribute to a better <a href="/wiki/Interaction_design" title="Interaction design">interaction design</a> and <a href="/wiki/User_experience_design" title="User experience design">user experience</a> of the system. </p><p><b>Facilitate testing and user documentation</b> </p><p>With content based upon an action or event flow structure, a model of well-written use cases also serves as excellent groundwork and valuable guidelines for the design of test cases and user manuals of the system or product, which is an effort-worthy investment up-front. There are obvious connections between the flow paths of a use case and its test cases. Deriving functional test cases from a use case through its scenarios (running instances of a use case) is straightforward.<sup id="cite_ref-34" class="reference"><a href="#cite_note-34"><span class="cite-bracket">&#91;</span>34<span class="cite-bracket">&#93;</span></a></sup> </p> <div class="mw-heading mw-heading2"><h2 id="Limitations">Limitations</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=19" title="Edit section: Limitations"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <p>Limitations of use cases include: </p> <ul><li>Use cases are not well suited to capturing non-interaction-based requirements of a system (such as algorithm or mathematical requirements) or <a href="/wiki/Non-functional_requirements" class="mw-redirect" title="Non-functional requirements">non-functional requirements</a> (such as platform, performance, timing, or safety-critical aspects). These are better specified declaratively elsewhere.</li> <li>As there are no fully standard definitions of use cases, each project must form its own interpretation.</li> <li>Some use case relationships, such as <i>extends</i>, are ambiguous in interpretation and can be difficult for stakeholders to understand as pointed out by Cockburn (Problem #6)<sup id="cite_ref-35" class="reference"><a href="#cite_note-35"><span class="cite-bracket">&#91;</span>35<span class="cite-bracket">&#93;</span></a></sup><sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed"><span title="This claim needs references to reliable sources. (October 2013)">citation needed</span></a></i>&#93;</sup></li> <li>Use case developers often find it difficult to determine the level of <a href="/wiki/User_interface" title="User interface">user interface</a> (UI) dependency to incorporate in a use case. While use case theory suggests that UI not be reflected in use cases, it can be awkward to abstract out this aspect of design, as it makes the use cases difficult to visualize. In software engineering, this difficulty is resolved by applying <a href="/wiki/Requirements_traceability" title="Requirements traceability">requirements traceability</a>, for example with a <a href="/wiki/Traceability_matrix" title="Traceability matrix">traceability matrix</a>. Another approach to associate UI elements with use cases is to attach a UI design to each step in the use case. This is called a use case storyboard.</li> <li>Use cases can be over-emphasized. <a href="/wiki/Bertrand_Meyer" title="Bertrand Meyer">Bertrand Meyer</a> discusses issues such as driving system design too literally from use cases, and using use cases to the exclusion of other potentially valuable requirements analysis techniques.<sup id="cite_ref-36" class="reference"><a href="#cite_note-36"><span class="cite-bracket">&#91;</span>36<span class="cite-bracket">&#93;</span></a></sup></li> <li>Use cases are a starting point for test design,<sup id="cite_ref-37" class="reference"><a href="#cite_note-37"><span class="cite-bracket">&#91;</span>37<span class="cite-bracket">&#93;</span></a></sup> but since each test needs its own success criteria, use cases may need to be modified to provide separate post-conditions for each path.<sup id="cite_ref-38" class="reference"><a href="#cite_note-38"><span class="cite-bracket">&#91;</span>38<span class="cite-bracket">&#93;</span></a></sup></li> <li>Though use cases include goals and contexts, whether these goals and motivations behind the goals (stakeholders' concerns and their assessments including non-interaction) conflict or negatively/positively affect other system goals are subject of goal-oriented requirement modeling techniques (such as <a href="/wiki/Business_Motivation_Model" title="Business Motivation Model">BMM</a>, <a href="/wiki/I*" title="I*">I*</a>, <a href="/wiki/KAOS_(software_development)" title="KAOS (software development)">KAOS</a> and <a href="/wiki/ArchiMate" title="ArchiMate">ArchiMate</a> ARMOR).</li></ul> <div class="mw-heading mw-heading2"><h2 id="Misconceptions">Misconceptions</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=20" title="Edit section: Misconceptions"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <style data-mw-deduplicate="TemplateStyles:r1251242444">.mw-parser-output .ambox{border:1px solid #a2a9b1;border-left:10px solid #36c;background-color:#fbfbfb;box-sizing:border-box}.mw-parser-output .ambox+link+.ambox,.mw-parser-output .ambox+link+style+.ambox,.mw-parser-output .ambox+link+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+style+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+link+.ambox{margin-top:-1px}html body.mediawiki .mw-parser-output .ambox.mbox-small-left{margin:4px 1em 4px 0;overflow:hidden;width:238px;border-collapse:collapse;font-size:88%;line-height:1.25em}.mw-parser-output .ambox-speedy{border-left:10px solid #b32424;background-color:#fee7e6}.mw-parser-output .ambox-delete{border-left:10px solid #b32424}.mw-parser-output .ambox-content{border-left:10px solid #f28500}.mw-parser-output .ambox-style{border-left:10px solid #fc3}.mw-parser-output .ambox-move{border-left:10px solid #9932cc}.mw-parser-output .ambox-protection{border-left:10px solid #a2a9b1}.mw-parser-output .ambox .mbox-text{border:none;padding:0.25em 0.5em;width:100%}.mw-parser-output .ambox .mbox-image{border:none;padding:2px 0 2px 0.5em;text-align:center}.mw-parser-output .ambox .mbox-imageright{border:none;padding:2px 0.5em 2px 0;text-align:center}.mw-parser-output .ambox .mbox-empty-cell{border:none;padding:0;width:1px}.mw-parser-output .ambox .mbox-image-div{width:52px}@media(min-width:720px){.mw-parser-output .ambox{margin:0 10%}}@media print{body.ns-0 .mw-parser-output .ambox{display:none!important}}</style><table class="box-Expand_section plainlinks metadata ambox mbox-small-left ambox-content" role="presentation"><tbody><tr><td class="mbox-image"><span typeof="mw:File"><a href="/wiki/File:Wiki_letter_w_cropped.svg" class="mw-file-description"><img alt="[icon]" src="//upload.wikimedia.org/wikipedia/commons/thumb/1/1c/Wiki_letter_w_cropped.svg/20px-Wiki_letter_w_cropped.svg.png" decoding="async" width="20" height="14" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/1/1c/Wiki_letter_w_cropped.svg/30px-Wiki_letter_w_cropped.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/1/1c/Wiki_letter_w_cropped.svg/40px-Wiki_letter_w_cropped.svg.png 2x" data-file-width="44" data-file-height="31" /></a></span></td><td class="mbox-text"><div class="mbox-text-span">This section <b>needs expansion</b>. You can help by <a class="external text" href="https://en.wikipedia.org/w/index.php?title=Use_case&amp;action=edit&amp;section=">adding to it</a>. <span class="date-container"><i>(<span class="date">July 2015</span>)</i></span></div></td></tr></tbody></table> <p>Common misunderstandings about use cases are: </p><p><b>User stories are agile; use cases are not.</b> </p><p>Agile and <a href="/wiki/Scrum_(development)" class="mw-redirect" title="Scrum (development)">Scrum</a> are neutral on requirement techniques. As the Scrum Primer<sup id="cite_ref-39" class="reference"><a href="#cite_note-39"><span class="cite-bracket">&#91;</span>39<span class="cite-bracket">&#93;</span></a></sup> states, </p> <blockquote><p><i> Product Backlog items are articulated in any way that is clear and sustainable. Contrary to popular misunderstanding, the Product Backlog does not contain "user stories"; it simply contains items. Those items can be expressed as user stories, use cases, or any other requirements approach that the group finds useful. But whatever the approach, most items should focus on delivering value to customers.</i></p></blockquote><p> Use case techniques have evolved to take Agile approaches into account by using use case slices to incrementally enrich a use case.<sup id="cite_ref-:0_13-1" class="reference"><a href="#cite_note-:0-13"><span class="cite-bracket">&#91;</span>13<span class="cite-bracket">&#93;</span></a></sup> </p><p><b>Use cases are mainly diagrams.</b> </p><p><a href="/wiki/Craig_Larman" title="Craig Larman">Craig Larman</a> stresses that "use cases are not diagrams, they are text".<sup id="cite_ref-40" class="reference"><a href="#cite_note-40"><span class="cite-bracket">&#91;</span>40<span class="cite-bracket">&#93;</span></a></sup> </p><p><b>Use cases have too much UI-related content.</b> </p><p>As some put it,<sup class="noprint Inline-Template" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Manual_of_Style/Words_to_watch#Unsupported_attributions" title="Wikipedia:Manual of Style/Words to watch"><span title="The material near this tag possibly uses too-vague attribution or weasel words. (March 2022)">who?</span></a></i>&#93;</sup> </p> <blockquote><p><i> Use cases will often contain a level of detail (i.e. naming of labels and buttons) which make it not well suited for capturing the requirements for a new system from scratch.</i></p></blockquote> <p>Novice misunderstandings. Each step of a well-written use case should present <i>actor</i> goals or intentions (the essence of functional requirements), and normally it should not contain any user interface details, e.g. naming of labels and buttons, UI operations, etc., which is a <i>bad</i> practice and will unnecessarily complicate the use case writing and limit its implementation. </p><p>As for capturing requirements for a new system from scratch, <i>use case diagrams</i> plus <i>use case briefs</i> are often used as handy and valuable tools, at least as lightweight as user stories. <sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed"><span title="This claim needs references to reliable sources. (March 2022)">citation needed</span></a></i>&#93;</sup> </p><p><b>Writing use cases for large systems is tedious and a waste of time.</b> </p><p>As some put it,<sup class="noprint Inline-Template" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Manual_of_Style/Words_to_watch#Unsupported_attributions" title="Wikipedia:Manual of Style/Words to watch"><span title="The material near this tag possibly uses too-vague attribution or weasel words. (March 2022)">who?</span></a></i>&#93;</sup> </p> <blockquote><p><i> The format of the use case makes it difficult to describe a large system (e.g. CRM system) in less than several hundred pages. It is time-consuming and you will find yourself spending time doing an unnecessary amount of rework.</i></p></blockquote><p><sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed"><span title="This claim needs references to reliable sources. (March 2022)">citation needed</span></a></i>&#93;</sup> </p><p>Spending much time writing tedious use cases which add no or little value and result in a lot of rework is a <i>bad smell</i> indicating that the writers are not well skilled and have little knowledge of how to write quality use cases both efficiently and effectively. Use cases should be authored in an iterative, incremental, and evolutionary (<i>agile</i>) way. Applying use case templates does not mean that all the fields of a use case template should be used and filled out comprehensively from up-front or during a special dedicated stage, i.e. the requirement phase in the traditional <i>waterfall</i> development model. </p><p>In fact, the use case formats formulated by <a href="#Templates">those popular template styles</a>, e.g. the RUP's and the Cockburn's (also adopted by <a href="/wiki/Oracle_Unified_Method" class="mw-redirect" title="Oracle Unified Method">the OUM method</a>), etc., have been proved in practice as valuable and helpful tools for capturing, analyzing and documenting complex requirements of large systems. The quality of a good use case documentation (<i>model</i>) should not be judged largely or only by its size. It is possible as well that a quality and comprehensive use case model of a large system may finally evolve into hundreds of pages mainly because of the inherent complexity of the <i>problem</i> in hand, not because of the poor writing skills of its authors. <sup class="noprint Inline-Template Template-Fact" style="white-space:nowrap;">&#91;<i><a href="/wiki/Wikipedia:Citation_needed" title="Wikipedia:Citation needed"><span title="This claim needs references to reliable sources. (March 2022)">citation needed</span></a></i>&#93;</sup> </p> <div class="mw-heading mw-heading2"><h2 id="Tools">Tools</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=21" title="Edit section: Tools"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1251242444"><table class="box-Unreferenced_section plainlinks metadata ambox ambox-content ambox-Unreferenced" role="presentation"><tbody><tr><td class="mbox-image"><div class="mbox-image-div"><span typeof="mw:File"><a href="/wiki/File:Question_book-new.svg" class="mw-file-description"><img alt="" src="//upload.wikimedia.org/wikipedia/en/thumb/9/99/Question_book-new.svg/50px-Question_book-new.svg.png" decoding="async" width="50" height="39" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/en/thumb/9/99/Question_book-new.svg/75px-Question_book-new.svg.png 1.5x, //upload.wikimedia.org/wikipedia/en/thumb/9/99/Question_book-new.svg/100px-Question_book-new.svg.png 2x" data-file-width="512" data-file-height="399" /></a></span></div></td><td class="mbox-text"><div class="mbox-text-span">This section <b>does not <a href="/wiki/Wikipedia:Citing_sources" title="Wikipedia:Citing sources">cite</a> any <a href="/wiki/Wikipedia:Verifiability" title="Wikipedia:Verifiability">sources</a></b>.<span class="hide-when-compact"> Please help <a href="/wiki/Special:EditPage/Use_case" title="Special:EditPage/Use case">improve this section</a> by <a href="/wiki/Help:Referencing_for_beginners" title="Help:Referencing for beginners">adding citations to reliable sources</a>. Unsourced material may be challenged and <a href="/wiki/Wikipedia:Verifiability#Burden_of_evidence" title="Wikipedia:Verifiability">removed</a>.</span> <span class="date-container"><i>(<span class="date">August 2013</span>)</i></span><span class="hide-when-compact"><i> (<small><a href="/wiki/Help:Maintenance_template_removal" title="Help:Maintenance template removal">Learn how and when to remove this message</a></small>)</i></span></div></td></tr></tbody></table> <p>Text editors and/or <a href="/wiki/Word_processor" title="Word processor">word processors</a> with template support are often used to write use cases. For large and complex system requirements, dedicated use case tools are helpful. </p><p>Some of the well-known use case tools include: </p> <ul><li><a href="/wiki/CaseComplete" title="CaseComplete">CaseComplete</a></li> <li><a href="/wiki/Enterprise_Architect_(software)" title="Enterprise Architect (software)">Enterprise Architect</a></li> <li><a href="/wiki/MagicDraw" title="MagicDraw">MagicDraw</a></li> <li><a href="/wiki/Rational_Software" title="Rational Software">Rational Software</a>'s RequisitePro - one of the early, well-known use case and requirement management tools in the 1990s.</li> <li><a href="/wiki/Software_Ideas_Modeler" title="Software Ideas Modeler">Software Ideas Modeler</a></li> <li><a href="/wiki/Wiki_software" title="Wiki software">Wiki software</a> - good tools for teams to author and manage use cases collaboratively.</li></ul> <p>Most <a href="/wiki/List_of_UML_tools" class="mw-redirect" title="List of UML tools">UML tools</a> support both the text writing and visual modeling of use cases. </p> <div class="mw-heading mw-heading2"><h2 id="See_also">See also</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=22" title="Edit section: See also"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <ul><li><a href="/wiki/Abuse_case" title="Abuse case">Abuse case</a></li> <li><a href="/wiki/Business_case" title="Business case">Business case</a></li> <li><a href="/wiki/Entity%E2%80%93control%E2%80%93boundary" title="Entity–control–boundary">Entity–control–boundary</a></li> <li><a href="/wiki/Event_partitioning" title="Event partitioning">Event partitioning</a></li> <li><a href="/wiki/Software_feature" title="Software feature">Feature</a></li> <li><a href="/wiki/List_of_UML_tools" class="mw-redirect" title="List of UML tools">List of UML tools</a></li> <li><a href="/wiki/Misuse_case" title="Misuse case">Misuse case</a></li> <li><a href="/wiki/Requirement" title="Requirement">Requirement</a></li> <li><a href="/wiki/Requirements_elicitation" title="Requirements elicitation">Requirements elicitation</a></li> <li><a href="/wiki/Scenario_(computing)" title="Scenario (computing)">Scenario</a></li> <li><a href="/wiki/Storyboard" title="Storyboard">Storyboard</a></li> <li><a href="/wiki/Test_case" title="Test case">Test case</a></li> <li><a href="/wiki/Use_case_points" title="Use case points">Use case points</a></li></ul> <div class="mw-heading mw-heading2"><h2 id="References">References</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=23" title="Edit section: References"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <style data-mw-deduplicate="TemplateStyles:r1239543626">.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}</style><div class="reflist"> <div class="mw-references-wrap mw-references-columns"><ol class="references"> <li id="cite_note-:1-1"><span class="mw-cite-backlink">^ <a href="#cite_ref-:1_1-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:1_1-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-:1_1-2"><sup><i><b>c</b></i></sup></a> <a href="#cite_ref-:1_1-3"><sup><i><b>d</b></i></sup></a></span> <span class="reference-text"><style data-mw-deduplicate="TemplateStyles:r1238218222">.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("//upload.wikimedia.org/wikipedia/commons/6/65/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("//upload.wikimedia.org/wikipedia/commons/d/d6/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("//upload.wikimedia.org/wikipedia/commons/a/aa/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("//upload.wikimedia.org/wikipedia/commons/4/4c/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}</style><cite id="CITEREFDr._Ivar_JacobsonIan_SpenceKurt_Bittner2011" class="citation web cs1">Dr. Ivar Jacobson; Ian Spence; Kurt Bittner (December 2011). <a rel="nofollow" class="external text" href="https://www.ivarjacobson.com/publications/white-papers/use-case-ebook">"Use-Case 2.0 ebook"</a>. <i>Ivar Jacobson International</i>. p.&#160;4<span class="reference-accessdate">. Retrieved <span class="nowrap">9 August</span> 2020</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=unknown&amp;rft.jtitle=Ivar+Jacobson+International&amp;rft.atitle=Use-Case+2.0+ebook&amp;rft.pages=4&amp;rft.date=2011-12&amp;rft.au=Dr.+Ivar+Jacobson&amp;rft.au=Ian+Spence&amp;rft.au=Kurt+Bittner&amp;rft_id=https%3A%2F%2Fwww.ivarjacobson.com%2Fpublications%2Fwhite-papers%2Fuse-case-ebook&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-:2-2"><span class="mw-cite-backlink">^ <a href="#cite_ref-:2_2-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:2_2-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFJacobson1987" class="citation journal cs1">Jacobson, Ivar (1 December 1987). <a rel="nofollow" class="external text" href="http://portal.acm.org/citation.cfm?doid=38807.38824">"Object-oriented development in an industrial environment"</a>. <i>ACM SIGPLAN Notices</i>. <b>22</b> (12): <span class="nowrap">183–</span>191. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F38807.38824">10.1145/38807.38824</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=ACM+SIGPLAN+Notices&amp;rft.atitle=Object-oriented+development+in+an+industrial+environment&amp;rft.volume=22&amp;rft.issue=12&amp;rft.pages=%3Cspan+class%3D%22nowrap%22%3E183-%3C%2Fspan%3E191&amp;rft.date=1987-12-01&amp;rft_id=info%3Adoi%2F10.1145%2F38807.38824&amp;rft.aulast=Jacobson&amp;rft.aufirst=Ivar&amp;rft_id=http%3A%2F%2Fportal.acm.org%2Fcitation.cfm%3Fdoid%3D38807.38824&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-Cockburn-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-Cockburn_3-0">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFCockburn2002" class="citation web cs1">Cockburn, Alistair (March 2002). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20080915162727/http://alistair.cockburn.us/index.php/Use_cases%2C_ten_years_later">"Use cases, ten years later"</a>. <i>Alistair.cockburn.us</i>. Alistair Cockburn. Archived from <a rel="nofollow" class="external text" href="http://alistair.cockburn.us/index.php/Use_cases%2C_ten_years_later">the original</a> on 15 September 2008<span class="reference-accessdate">. Retrieved <span class="nowrap">17 April</span> 2013</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=unknown&amp;rft.jtitle=Alistair.cockburn.us&amp;rft.atitle=Use+cases%2C+ten+years+later&amp;rft.date=2002-03&amp;rft.aulast=Cockburn&amp;rft.aufirst=Alistair&amp;rft_id=http%3A%2F%2Falistair.cockburn.us%2Findex.php%2FUse_cases%252C_ten_years_later&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-:3-4"><span class="mw-cite-backlink">^ <a href="#cite_ref-:3_4-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:3_4-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFJacobson_IvarChristerson_MagnusJonsson_PatrikÖvergaard_Gunnar1992" class="citation book cs1">Jacobson Ivar; Christerson Magnus; Jonsson Patrik; Övergaard Gunnar (1992). <i>Object-oriented software engineering: a use case driven approach</i>. ACM Press. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/0-201-54435-0" title="Special:BookSources/0-201-54435-0"><bdi>0-201-54435-0</bdi></a>. <a href="/wiki/OCLC_(identifier)" class="mw-redirect" title="OCLC (identifier)">OCLC</a>&#160;<a rel="nofollow" class="external text" href="https://search.worldcat.org/oclc/26132801">26132801</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=book&amp;rft.btitle=Object-oriented+software+engineering%3A+a+use+case+driven+approach&amp;rft.pub=ACM+Press&amp;rft.date=1992&amp;rft_id=info%3Aoclcnum%2F26132801&amp;rft.isbn=0-201-54435-0&amp;rft.au=Jacobson+Ivar&amp;rft.au=Christerson+Magnus&amp;rft.au=Jonsson+Patrik&amp;rft.au=%C3%96vergaard+Gunnar&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-:4-5"><span class="mw-cite-backlink">^ <a href="#cite_ref-:4_5-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:4_5-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFJacobson,_Ivar.Ericsson,_MariaJacobson,_Agneta1995" class="citation book cs1">Jacobson, Ivar.; Ericsson, Maria; Jacobson, Agneta (1995). <i>The object advantage&#160;: business process reengineering with object technology</i>. Addison-Wesley. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/0-201-42289-1" title="Special:BookSources/0-201-42289-1"><bdi>0-201-42289-1</bdi></a>. <a href="/wiki/OCLC_(identifier)" class="mw-redirect" title="OCLC (identifier)">OCLC</a>&#160;<a rel="nofollow" class="external text" href="https://search.worldcat.org/oclc/32276135">32276135</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=book&amp;rft.btitle=The+object+advantage+%3A+business+process+reengineering+with+object+technology&amp;rft.pub=Addison-Wesley&amp;rft.date=1995&amp;rft_id=info%3Aoclcnum%2F32276135&amp;rft.isbn=0-201-42289-1&amp;rft.au=Jacobson%2C+Ivar.&amp;rft.au=Ericsson%2C+Maria&amp;rft.au=Jacobson%2C+Agneta&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.omg.org/spec/UML/#spec-versions-formal">"About the Unified Modeling Language Specification Version 2.5.1"</a>. <i>www.omg.org</i><span class="reference-accessdate">. Retrieved <span class="nowrap">9 August</span> 2020</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=unknown&amp;rft.jtitle=www.omg.org&amp;rft.atitle=About+the+Unified+Modeling+Language+Specification+Version+2.5.1&amp;rft_id=https%3A%2F%2Fwww.omg.org%2Fspec%2FUML%2F%23spec-versions-formal&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-:5-7"><span class="mw-cite-backlink">^ <a href="#cite_ref-:5_7-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:5_7-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-:5_7-2"><sup><i><b>c</b></i></sup></a> <a href="#cite_ref-:5_7-3"><sup><i><b>d</b></i></sup></a></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFJacobson,_IvarBooch,_GradyRumbaugh,_Jim1999" class="citation book cs1">Jacobson, Ivar; Booch, Grady; Rumbaugh, Jim (1999). <i>The unified software development process</i>. Reading, Massachusetts: Addison-Wesley. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/0-201-57169-2" title="Special:BookSources/0-201-57169-2"><bdi>0-201-57169-2</bdi></a>. <a href="/wiki/OCLC_(identifier)" class="mw-redirect" title="OCLC (identifier)">OCLC</a>&#160;<a rel="nofollow" class="external text" href="https://search.worldcat.org/oclc/636807532">636807532</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=book&amp;rft.btitle=The+unified+software+development+process&amp;rft.place=Reading%2C+Massachusetts&amp;rft.pub=Addison-Wesley&amp;rft.date=1999&amp;rft_id=info%3Aoclcnum%2F636807532&amp;rft.isbn=0-201-57169-2&amp;rft.au=Jacobson%2C+Ivar&amp;rft.au=Booch%2C+Grady&amp;rft.au=Rumbaugh%2C+Jim&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-:6-8"><span class="mw-cite-backlink">^ <a href="#cite_ref-:6_8-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:6_8-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFConstantine1995" class="citation journal cs1">Constantine, Larry L. (1 April 1995). <a rel="nofollow" class="external text" href="http://portal.acm.org/citation.cfm?doid=205350.205356">"Essential modeling: use cases for user interfaces"</a>. <i>Interactions</i>. <b>2</b> (2): <span class="nowrap">34–</span>46. <a href="/wiki/Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F205350.205356">10.1145/205350.205356</a>. <a href="/wiki/S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a>&#160;<a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:17209049">17209049</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=article&amp;rft.jtitle=Interactions&amp;rft.atitle=Essential+modeling%3A+use+cases+for+user+interfaces&amp;rft.volume=2&amp;rft.issue=2&amp;rft.pages=%3Cspan+class%3D%22nowrap%22%3E34-%3C%2Fspan%3E46&amp;rft.date=1995-04-01&amp;rft_id=info%3Adoi%2F10.1145%2F205350.205356&amp;rft_id=https%3A%2F%2Fapi.semanticscholar.org%2FCorpusID%3A17209049%23id-name%3DS2CID&amp;rft.aulast=Constantine&amp;rft.aufirst=Larry+L.&amp;rft_id=http%3A%2F%2Fportal.acm.org%2Fcitation.cfm%3Fdoid%3D205350.205356&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-:7-9"><span class="mw-cite-backlink">^ <a href="#cite_ref-:7_9-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:7_9-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFCockburn,_Alistair.2001" class="citation book cs1">Cockburn, Alistair. (2001). <a rel="nofollow" class="external text" href="https://www.academia.edu/57581336"><i>Writing effective use cases</i></a>. Addison-Wesley. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/0-201-70225-8" title="Special:BookSources/0-201-70225-8"><bdi>0-201-70225-8</bdi></a>. <a href="/wiki/OCLC_(identifier)" class="mw-redirect" title="OCLC (identifier)">OCLC</a>&#160;<a rel="nofollow" class="external text" href="https://search.worldcat.org/oclc/44046973">44046973</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=book&amp;rft.btitle=Writing+effective+use+cases&amp;rft.pub=Addison-Wesley&amp;rft.date=2001&amp;rft_id=info%3Aoclcnum%2F44046973&amp;rft.isbn=0-201-70225-8&amp;rft.au=Cockburn%2C+Alistair.&amp;rft_id=https%3A%2F%2Fwww.academia.edu%2F57581336&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-:8-10"><span class="mw-cite-backlink">^ <a href="#cite_ref-:8_10-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:8_10-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-:8_10-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFBittner,_Kurt2003" class="citation book cs1">Bittner, Kurt (2003). <i>Use case modeling</i>. Spence, Ian. Addison Wesley. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/0-201-70913-9" title="Special:BookSources/0-201-70913-9"><bdi>0-201-70913-9</bdi></a>. <a href="/wiki/OCLC_(identifier)" class="mw-redirect" title="OCLC (identifier)">OCLC</a>&#160;<a rel="nofollow" class="external text" href="https://search.worldcat.org/oclc/50041546">50041546</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=book&amp;rft.btitle=Use+case+modeling&amp;rft.pub=Addison+Wesley&amp;rft.date=2003&amp;rft_id=info%3Aoclcnum%2F50041546&amp;rft.isbn=0-201-70913-9&amp;rft.au=Bittner%2C+Kurt&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-11"><span class="mw-cite-backlink"><b><a href="#cite_ref-11">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFLeffingwell,_Dean.2003" class="citation book cs1">Leffingwell, Dean. (2003). <i>Managing software requirements&#160;: a use case approach</i>. Widrig, Don. (2nd&#160;ed.). Addison-Wesley. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/0-321-12247-X" title="Special:BookSources/0-321-12247-X"><bdi>0-321-12247-X</bdi></a>. <a href="/wiki/OCLC_(identifier)" class="mw-redirect" title="OCLC (identifier)">OCLC</a>&#160;<a rel="nofollow" class="external text" href="https://search.worldcat.org/oclc/51653240">51653240</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=book&amp;rft.btitle=Managing+software+requirements+%3A+a+use+case+approach&amp;rft.edition=2nd&amp;rft.pub=Addison-Wesley&amp;rft.date=2003&amp;rft_id=info%3Aoclcnum%2F51653240&amp;rft.isbn=0-321-12247-X&amp;rft.au=Leffingwell%2C+Dean.&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-12">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFÖvergaardPalmkvist2005" class="citation book cs1">Övergaard, Gunnar; Palmkvist, Karin (2005). <i>Use cases&#160;: patterns and blueprints</i>. Indianapolis, Ind.: Addison-Wesley. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/0-13-145134-0" title="Special:BookSources/0-13-145134-0"><bdi>0-13-145134-0</bdi></a>. <a href="/wiki/OCLC_(identifier)" class="mw-redirect" title="OCLC (identifier)">OCLC</a>&#160;<a rel="nofollow" class="external text" href="https://search.worldcat.org/oclc/59554401">59554401</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=book&amp;rft.btitle=Use+cases+%3A+patterns+and+blueprints&amp;rft.place=Indianapolis%2C+Ind.&amp;rft.pub=Addison-Wesley&amp;rft.date=2005&amp;rft_id=info%3Aoclcnum%2F59554401&amp;rft.isbn=0-13-145134-0&amp;rft.aulast=%C3%96vergaard&amp;rft.aufirst=Gunnar&amp;rft.au=Palmkvist%2C+Karin&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-:0-13"><span class="mw-cite-backlink">^ <a href="#cite_ref-:0_13-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:0_13-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"> <link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFJacobsonSpenceBittner2011" class="citation web cs1"><a href="/wiki/Ivar_Jacobson" title="Ivar Jacobson">Jacobson, Ivar</a>; <a href="/w/index.php?title=Ian_Spence_(software_engineer)&amp;action=edit&amp;redlink=1" class="new" title="Ian Spence (software engineer) (page does not exist)">Spence, Ian</a>; Bittner, Kurt (December 2011). <a rel="nofollow" class="external text" href="http://www.ivarjacobson.com/download.ashx?id=1282">"Use Case 2.0: The Guide to Succeeding with Use Cases"</a>. Ivar Jacobson International<span class="reference-accessdate">. Retrieved <span class="nowrap">5 May</span> 2014</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=unknown&amp;rft.btitle=Use+Case+2.0%3A+The+Guide+to+Succeeding+with+Use+Cases&amp;rft.pub=Ivar+Jacobson+International&amp;rft.date=2011-12&amp;rft.aulast=Jacobson&amp;rft.aufirst=Ivar&amp;rft.au=Spence%2C+Ian&amp;rft.au=Bittner%2C+Kurt&amp;rft_id=http%3A%2F%2Fwww.ivarjacobson.com%2Fdownload.ashx%3Fid%3D1282&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-14"><span class="mw-cite-backlink"><b><a href="#cite_ref-14">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20130617191510/https://irmuk.co.uk/BA2011/">"Business Analysis Conference Europe 2011 - 26-28 September 2011, London, UK"</a>. Irmuk.co.uk. Archived from <a rel="nofollow" class="external text" href="http://www.irmuk.co.uk/BA2011/">the original</a> on 17 June 2013<span class="reference-accessdate">. Retrieved <span class="nowrap">17 April</span> 2013</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=unknown&amp;rft.btitle=Business+Analysis+Conference+Europe+2011+-+26-28+September+2011%2C+London%2C+UK&amp;rft.pub=Irmuk.co.uk&amp;rft_id=http%3A%2F%2Fwww.irmuk.co.uk%2FBA2011%2F&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-15"><span class="mw-cite-backlink"><b><a href="#cite_ref-15">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20200923204540/https://www.ivarjacobson.com/publications/presentations/use-case-20-presentation">"Use-Case 2.0 Presentation"</a>. <i>Ivar Jacobson International</i>. 27 September 2011. Archived from <a rel="nofollow" class="external text" href="https://www.ivarjacobson.com/publications/presentations/use-case-20-presentation">the original</a> on 23 September 2020<span class="reference-accessdate">. Retrieved <span class="nowrap">9 August</span> 2020</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=unknown&amp;rft.jtitle=Ivar+Jacobson+International&amp;rft.atitle=Use-Case+2.0+Presentation&amp;rft.date=2011-09-27&amp;rft_id=https%3A%2F%2Fwww.ivarjacobson.com%2Fpublications%2Fpresentations%2Fuse-case-20-presentation&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-16"><span class="mw-cite-backlink"><b><a href="#cite_ref-16">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFBourque,_PierreFairley,_R._E._(Richard_E.)2014" class="citation book cs1">Bourque, Pierre; Fairley, R. E. (Richard E.) (2014). <i>SWEBOK: guide to the software engineering body of knowledge</i> (Version 3.0&#160;ed.). IEEE Computer Society. pp.&#160;1-6 to 1-8. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/978-0-7695-5166-1" title="Special:BookSources/978-0-7695-5166-1"><bdi>978-0-7695-5166-1</bdi></a>. <a href="/wiki/OCLC_(identifier)" class="mw-redirect" title="OCLC (identifier)">OCLC</a>&#160;<a rel="nofollow" class="external text" href="https://search.worldcat.org/oclc/880350861">880350861</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=book&amp;rft.btitle=SWEBOK%3A+guide+to+the+software+engineering+body+of+knowledge&amp;rft.pages=1-6+to+1-8&amp;rft.edition=Version+3.0&amp;rft.pub=IEEE+Computer+Society&amp;rft.date=2014&amp;rft_id=info%3Aoclcnum%2F880350861&amp;rft.isbn=978-0-7695-5166-1&amp;rft.au=Bourque%2C+Pierre&amp;rft.au=Fairley%2C+R.+E.+%28Richard+E.%29&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-:9-17"><span class="mw-cite-backlink">^ <a href="#cite_ref-:9_17-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-:9_17-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFObject_Management_Group2017" class="citation web cs1"><a href="/wiki/Object_Management_Group" title="Object Management Group">Object Management Group</a> (2017). <a rel="nofollow" class="external text" href="https://www.omg.org/spec/UML/2.5.1">"Unified Modeling Language Specification Version 2.5.1"</a>. <i>www.omg.org</i><span class="reference-accessdate">. Retrieved <span class="nowrap">16 August</span> 2020</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=unknown&amp;rft.jtitle=www.omg.org&amp;rft.atitle=Unified+Modeling+Language+Specification+Version+2.5.1&amp;rft.date=2017&amp;rft.au=Object+Management+Group&amp;rft_id=https%3A%2F%2Fwww.omg.org%2Fspec%2FUML%2F2.5.1&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-18"><span class="mw-cite-backlink"><b><a href="#cite_ref-18">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFWiegers,_Karl_Eugene2010" class="citation book cs1">Wiegers, Karl Eugene (2010). <i>More about software requirements: thorny issues and practical advice</i>. Microsoft Press. pp.&#160;Chapter 11. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/978-0-7356-2267-8" title="Special:BookSources/978-0-7356-2267-8"><bdi>978-0-7356-2267-8</bdi></a>. <a href="/wiki/OCLC_(identifier)" class="mw-redirect" title="OCLC (identifier)">OCLC</a>&#160;<a rel="nofollow" class="external text" href="https://search.worldcat.org/oclc/73814167">73814167</a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=book&amp;rft.btitle=More+about+software+requirements%3A+thorny+issues+and+practical+advice&amp;rft.pages=Chapter+11&amp;rft.pub=Microsoft+Press&amp;rft.date=2010&amp;rft_id=info%3Aoclcnum%2F73814167&amp;rft.isbn=978-0-7356-2267-8&amp;rft.au=Wiegers%2C+Karl+Eugene&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-19"><span class="mw-cite-backlink"><b><a href="#cite_ref-19">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFAmbler,_Scott2004" class="citation web cs1"><a href="/wiki/Scott_Ambler" title="Scott Ambler">Ambler, Scott</a> (2004). <a rel="nofollow" class="external text" href="http://agilemodeling.com/artifacts/systemUseCase.htm">"System Use Cases: An Agile Introduction"</a>. <i>agilemodeling.com</i><span class="reference-accessdate">. Retrieved <span class="nowrap">16 August</span> 2020</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=unknown&amp;rft.jtitle=agilemodeling.com&amp;rft.atitle=System+Use+Cases%3A+An+Agile+Introduction&amp;rft.date=2004&amp;rft.au=Ambler%2C+Scott&amp;rft_id=http%3A%2F%2Fagilemodeling.com%2Fartifacts%2FsystemUseCase.htm&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-20"><span class="mw-cite-backlink"><b><a href="#cite_ref-20">^</a></b></span> <span class="reference-text">Cockburn, 2001. Inside front cover. Icons "Design Scope".</span> </li> <li id="cite_note-21"><span class="mw-cite-backlink"><b><a href="#cite_ref-21">^</a></b></span> <span class="reference-text">Suzanne Robertson. <i>Scenarios in Requirements Discovery</i>. Chapter 3 in Alexander and Maiden, 2004. Pages 39-59.</span> </li> <li id="cite_note-22"><span class="mw-cite-backlink"><b><a href="#cite_ref-22">^</a></b></span> <span class="reference-text">Cockburn, 2001. Inside front cover. Icons "Goal Level".</span> </li> <li id="cite_note-Fowler-23"><span class="mw-cite-backlink">^ <a href="#cite_ref-Fowler_23-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Fowler_23-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-Fowler_23-2"><sup><i><b>c</b></i></sup></a> <a href="#cite_ref-Fowler_23-3"><sup><i><b>d</b></i></sup></a> <a href="#cite_ref-Fowler_23-4"><sup><i><b>e</b></i></sup></a> <a href="#cite_ref-Fowler_23-5"><sup><i><b>f</b></i></sup></a> <a href="#cite_ref-Fowler_23-6"><sup><i><b>g</b></i></sup></a> <a href="#cite_ref-Fowler_23-7"><sup><i><b>h</b></i></sup></a></span> <span class="reference-text">Fowler, 2004.</span> </li> <li id="cite_note-Cockburn120-24"><span class="mw-cite-backlink">^ <a href="#cite_ref-Cockburn120_24-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Cockburn120_24-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">Cockburn, 2001. Page 120.</span> </li> <li id="cite_note-25"><span class="mw-cite-backlink"><b><a href="#cite_ref-25">^</a></b></span> <span class="reference-text">Cockburn, 2001. Inside rear cover. Field "Use Case Title".</span> </li> <li id="cite_note-26"><span class="mw-cite-backlink"><b><a href="#cite_ref-26">^</a></b></span> <span class="reference-text">Alexander and Beus-Dukic, 2009. Page 121</span> </li> <li id="cite_note-wiki.c2.com-27"><span class="mw-cite-backlink">^ <a href="#cite_ref-wiki.c2.com_27-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-wiki.c2.com_27-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://wiki.c2.com/?UserStoryAndUseCaseComparison">"User Story And Use Case Comparison"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">19 January</span> 2024</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=unknown&amp;rft.btitle=User+Story+And+Use+Case+Comparison&amp;rft_id=http%3A%2F%2Fwiki.c2.com%2F%3FUserStoryAndUseCaseComparison&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-Cockburn53-28"><span class="mw-cite-backlink">^ <a href="#cite_ref-Cockburn53_28-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Cockburn53_28-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-Cockburn53_28-2"><sup><i><b>c</b></i></sup></a> <a href="#cite_ref-Cockburn53_28-3"><sup><i><b>d</b></i></sup></a></span> <span class="reference-text">Cockburn, 2001. Page 53.</span> </li> <li id="cite_note-Cockburn55-29"><span class="mw-cite-backlink"><b><a href="#cite_ref-Cockburn55_29-0">^</a></b></span> <span class="reference-text">Cockburn, 2001. Page 55.</span> </li> <li id="cite_note-AB39-30"><span class="mw-cite-backlink">^ <a href="#cite_ref-AB39_30-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-AB39_30-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">Alexander and Beus-Dukic, 2009. Page 39.</span> </li> <li id="cite_note-31"><span class="mw-cite-backlink"><b><a href="#cite_ref-31">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFEriksson2000" class="citation book cs1">Eriksson, Hans-Erik (2000). <span class="id-lock-registration" title="Free registration required"><a rel="nofollow" class="external text" href="https://archive.org/details/businessmodeling00erik/page/52"><i>Business Modeling with UML</i></a></span>. New York: Wiley Computer Publishing. pp.&#160;<a rel="nofollow" class="external text" href="https://archive.org/details/businessmodeling00erik/page/52">52</a>. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/0-471-29551-5" title="Special:BookSources/0-471-29551-5"><bdi>0-471-29551-5</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=book&amp;rft.btitle=Business+Modeling+with+UML&amp;rft.place=New+York&amp;rft.pages=52&amp;rft.pub=Wiley+Computer+Publishing&amp;rft.date=2000&amp;rft.isbn=0-471-29551-5&amp;rft.aulast=Eriksson&amp;rft.aufirst=Hans-Erik&amp;rft_id=https%3A%2F%2Farchive.org%2Fdetails%2Fbusinessmodeling00erik%2Fpage%2F52&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-32"><span class="mw-cite-backlink"><b><a href="#cite_ref-32">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFCockburn2008" class="citation web cs1">Cockburn, Alistair (9 January 2008). <a rel="nofollow" class="external text" href="http://alistair.cockburn.us/Why+I+still+use+use+cases">"Why I still use cases"</a>. <i>alistair.cockburn.us</i>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=unknown&amp;rft.jtitle=alistair.cockburn.us&amp;rft.atitle=Why+I+still+use+cases&amp;rft.date=2008-01-09&amp;rft.aulast=Cockburn&amp;rft.aufirst=Alistair&amp;rft_id=http%3A%2F%2Falistair.cockburn.us%2FWhy%2BI%2Bstill%2Buse%2Buse%2Bcases&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-33"><span class="mw-cite-backlink"><b><a href="#cite_ref-33">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFKarl_Wiegers1997" class="citation web cs1">Karl Wiegers (March 1997). <a rel="nofollow" class="external text" href="http://www.processimpact.com/articles/usecase.html">"Listening to the Customer's Voice"</a>. <i>Process Impact</i>. Software Development.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=unknown&amp;rft.jtitle=Process+Impact&amp;rft.atitle=Listening+to+the+Customer%27s+Voice&amp;rft.date=1997-03&amp;rft.au=Karl+Wiegers&amp;rft_id=http%3A%2F%2Fwww.processimpact.com%2Farticles%2Fusecase.html&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-34"><span class="mw-cite-backlink"><b><a href="#cite_ref-34">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFPeter_Zielczynski2006" class="citation web cs1">Peter Zielczynski (May 2006). <a rel="nofollow" class="external text" href="http://www.ibm.com/developerworks/rational/library/04/r-3217/">"Traceability from Use Cases to Test Cases"</a>. IBM developerWorks.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=unknown&amp;rft.btitle=Traceability+from+Use+Cases+to+Test+Cases&amp;rft.pub=IBM+developerWorks&amp;rft.date=2006-05&amp;rft.au=Peter+Zielczynski&amp;rft_id=http%3A%2F%2Fwww.ibm.com%2Fdeveloperworks%2Frational%2Flibrary%2F04%2Fr-3217%2F&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-35"><span class="mw-cite-backlink"><b><a href="#cite_ref-35">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://alistair.cockburn.us/Structuring+use+cases+with+goals">"Alistair.Cockburn.us - Structuring use cases with goals"</a>. <i>alistair.cockburn.us</i><span class="reference-accessdate">. Retrieved <span class="nowrap">16 March</span> 2018</span>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Ajournal&amp;rft.genre=unknown&amp;rft.jtitle=alistair.cockburn.us&amp;rft.atitle=Alistair.Cockburn.us+-+Structuring+use+cases+with+goals&amp;rft_id=http%3A%2F%2Falistair.cockburn.us%2FStructuring%2Buse%2Bcases%2Bwith%2Bgoals&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-36"><span class="mw-cite-backlink"><b><a href="#cite_ref-36">^</a></b></span> <span class="reference-text">Meyer, 2000. (page needed)</span> </li> <li id="cite_note-37"><span class="mw-cite-backlink"><b><a href="#cite_ref-37">^</a></b></span> <span class="reference-text">Armour and Miller, 2000. (page needed)</span> </li> <li id="cite_note-38"><span class="mw-cite-backlink"><b><a href="#cite_ref-38">^</a></b></span> <span class="reference-text">Denney, 2005. (page needed)</span> </li> <li id="cite_note-39"><span class="mw-cite-backlink"><b><a href="#cite_ref-39">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFPete_DeemerGabrielle_BenefieldCraig_LarmanBas_Vodde2012" class="citation web cs1">Pete Deemer; Gabrielle Benefield; Craig Larman; Bas Vodde (17 December 2012). <a rel="nofollow" class="external text" href="http://www.infoq.com/minibooks/Scrum_Primer">"The Scrum Primer: A Lightweight Guide to the Theory and Practice of Scrum (Version 2.0)"</a>. InfoQ.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=unknown&amp;rft.btitle=The+Scrum+Primer%3A+A+Lightweight+Guide+to+the+Theory+and+Practice+of+Scrum+%28Version+2.0%29&amp;rft.pub=InfoQ&amp;rft.date=2012-12-17&amp;rft.au=Pete+Deemer&amp;rft.au=Gabrielle+Benefield&amp;rft.au=Craig+Larman&amp;rft.au=Bas+Vodde&amp;rft_id=http%3A%2F%2Fwww.infoq.com%2Fminibooks%2FScrum_Primer&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> <li id="cite_note-40"><span class="mw-cite-backlink"><b><a href="#cite_ref-40">^</a></b></span> <span class="reference-text"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1238218222"><cite id="CITEREFLarman2005" class="citation book cs1">Larman, Craig (2005). <i>Applying UML and patterns</i>. Prentice Hall. pp.&#160;<span class="nowrap">63–</span>64. <a href="/wiki/ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&#160;<a href="/wiki/Special:BookSources/0-13-148906-2" title="Special:BookSources/0-13-148906-2"><bdi>0-13-148906-2</bdi></a>.</cite><span title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Abook&amp;rft.genre=book&amp;rft.btitle=Applying+UML+and+patterns&amp;rft.pages=%3Cspan+class%3D%22nowrap%22%3E63-%3C%2Fspan%3E64&amp;rft.pub=Prentice+Hall&amp;rft.date=2005&amp;rft.isbn=0-13-148906-2&amp;rft.aulast=Larman&amp;rft.aufirst=Craig&amp;rfr_id=info%3Asid%2Fen.wikipedia.org%3AUse+case" class="Z3988"></span></span> </li> </ol></div></div> <div class="mw-heading mw-heading2"><h2 id="Further_reading">Further reading</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=24" title="Edit section: Further reading"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <ul><li>Alexander, Ian, and Beus-Dukic, Ljerka. <i>Discovering Requirements: How to Specify Products and Services</i>. Wiley, 2009.</li> <li>Alexander, Ian, and Maiden, Neil. <i>Scenarios, Stories, Use Cases</i>. Wiley 2004.</li> <li>Armour, Frank, and Granville Miller. <i>Advanced Use Case Modeling: Software Systems</i>. Addison-Wesley, 2000.</li> <li>Kurt Bittner, Ian Spence, <i>Use Case Modeling</i>, Addison-Wesley Professional, 20 August 2002.</li> <li>Cockburn, Alistair. <i>Writing Effective Use Cases.</i> Addison-Wesley, 2001.</li> <li>Larry Constantine, Lucy Lockwood, <i>Software for Use: A Practical Guide to the Essential Models and Methods of Usage-Centered Design</i>, Addison-Wesley, 1999.</li> <li>Denney, Richard. <i>Succeeding with Use Cases: Working Smart to Deliver Quality</i>. Addison-Wesley, 2005.</li> <li>Fowler, Martin. <i>UML Distilled (Third Edition)</i>. Addison-Wesley, 2004.</li> <li>Jacobson Ivar, Christerson M., Jonsson P., Övergaard G., <i>Object-Oriented Software Engineering - A Use Case Driven Approach</i>, Addison-Wesley, 1992.</li> <li>Jacobson Ivar, Spence I., Bittner K. <i>Use Case 2.0: The Guide to Succeeding with Use Cases</i>, IJI SA, 2011.</li> <li>Dean Leffingwell, Don Widrig, <i>Managing Software Requirements: A Use Case Approach</i>, Addison-Wesley Professional. 7 December 2012.</li> <li>Kulak, Daryl, and Eamonn Guiney. <i>Use cases: requirements in context.</i> Addison-Wesley, 2012.</li> <li>Meyer, Bertrand. <i>Object-Oriented Software Construction</i>. (2nd edition). Prentice Hall, 2000.</li> <li>Schneider, Geri and Winters, Jason P. <i>Applying Use Cases 2nd Edition: A Practical Guide</i>. Addison-Wesley, 2001.</li> <li>Wazlawick, Raul S. <i>Object-Oriented Analysis and Design for Information Systems: Modeling with UML, OCL, and IFML</i>. Morgan Kaufmann, 2014.</li></ul> <div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Use_case&amp;action=edit&amp;section=25" title="Edit section: External links"><span>edit</span></a><span class="mw-editsection-bracket">]</span></span></div> <ul><li><a rel="nofollow" class="external text" href="http://alistair.cockburn.us/Use+cases">Use case column</a> and <a rel="nofollow" class="external text" href="http://alistair.cockburn.us/index.php/Basic_use_case_template">Basic Use Case Template</a> by <a href="/wiki/Alistair_Cockburn" title="Alistair Cockburn">Alistair Cockburn</a></li> <li><a rel="nofollow" class="external text" href="https://www.usability.gov/how-to-and-tools/methods/use-cases.html">Use Cases</a> at <a href="/wiki/General_Services_Administration" title="General Services Administration">GSA</a>'s Usability.gov</li> <li><a rel="nofollow" class="external text" href="https://www.academia.edu/1354848/PROJECT_ICARUS_STAKEHOLDER_SCENARIOS_FOR_AN_INTERSTELLAR_EXPLORATION_PROGRAM">Application of use cases for stakeholder analysis "Project Icarus"</a> at <a href="/wiki/Academia.edu" title="Academia.edu">Academia.edu</a></li> <li><a rel="nofollow" class="external text" href="https://developer.ibm.com/?s=use+case">Search for "use case"</a> at IBM Developer</li></ul> <div class="navbox-styles"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374"><style data-mw-deduplicate="TemplateStyles:r1236075235">.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}</style></div><div role="navigation" class="navbox" aria-labelledby="Unified_Modeling_Language80" style="padding:3px"><table class="nowraplinks mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="3"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1239400231"><div class="navbar plainlinks hlist navbar-mini"><ul><li class="nv-view"><a href="/wiki/Template:Unified_Modeling_Language" title="Template:Unified Modeling Language"><abbr title="View this template">v</abbr></a></li><li class="nv-talk"><a href="/wiki/Template_talk:Unified_Modeling_Language" title="Template talk:Unified Modeling Language"><abbr title="Discuss this template">t</abbr></a></li><li class="nv-edit"><a href="/wiki/Special:EditPage/Template:Unified_Modeling_Language" title="Special:EditPage/Template:Unified Modeling Language"><abbr title="Edit this template">e</abbr></a></li></ul></div><div id="Unified_Modeling_Language80" style="font-size:114%;margin:0 4em"><a href="/wiki/Unified_Modeling_Language" title="Unified Modeling Language">Unified Modeling Language</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">Actors</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><i>Organizations</i> <ul><li><a href="/wiki/Object_Management_Group" title="Object Management Group">Object Management Group</a></li> <li><a href="/wiki/UML_Partners" title="UML Partners">UML Partners</a></li></ul></li> <li><i>Persons</i> <ul><li><a href="/wiki/Grady_Booch" title="Grady Booch">Grady Booch</a></li> <li><a href="/wiki/Ivar_Jacobson" title="Ivar Jacobson">Ivar Jacobson</a></li> <li><a href="/wiki/James_Rumbaugh" title="James Rumbaugh">James Rumbaugh</a></li></ul></li></ul> </div></td><td class="noviewer navbox-image" rowspan="5" style="width:1px;padding:0 0 0 2px"><div><span typeof="mw:File"><a href="/wiki/Use_case_diagram" title="Use case diagram"><img src="//upload.wikimedia.org/wikipedia/commons/thumb/1/1d/Use_case_restaurant_model.svg/100px-Use_case_restaurant_model.svg.png" decoding="async" width="100" height="100" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/1/1d/Use_case_restaurant_model.svg/150px-Use_case_restaurant_model.svg.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/1/1d/Use_case_restaurant_model.svg/200px-Use_case_restaurant_model.svg.png 2x" data-file-width="496" data-file-height="496" /></a></span></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Concepts</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%">Object oriented</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Object-oriented_programming" title="Object-oriented programming">Object-oriented programming</a></li> <li><a href="/wiki/Object-oriented_analysis_and_design" title="Object-oriented analysis and design">Object-oriented analysis and design</a></li> <li><a href="/wiki/Object-oriented_modeling" title="Object-oriented modeling">Object-oriented modeling</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Structure</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Actor_(UML)" title="Actor (UML)">Actor</a></li> <li><a href="/wiki/Attribute_(computing)" title="Attribute (computing)">Attribute</a></li> <li><a href="/wiki/Artifact_(UML)" class="mw-redirect" title="Artifact (UML)">Artifact</a></li> <li><a href="/wiki/Class_(computer_programming)" title="Class (computer programming)">Class</a></li> <li><a href="/wiki/Component_(UML)" title="Component (UML)">Component</a></li> <li><a href="/wiki/Protocol_(object-oriented_programming)" class="mw-redirect" title="Protocol (object-oriented programming)">Interface</a></li> <li><a href="/wiki/Object_(computer_science)" title="Object (computer science)">Object</a></li> <li><a href="/wiki/Package_(UML)" title="Package (UML)">Package</a></li> <li><a href="/wiki/Profile_diagram" title="Profile diagram">Profile diagram</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Behavior</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Activity_(UML)" title="Activity (UML)">Activity</a></li> <li><a href="/wiki/Event_(UML)" title="Event (UML)">Event</a></li> <li><a href="/wiki/Message_passing" title="Message passing">Message</a></li> <li><a href="/wiki/Method_(computer_programming)" title="Method (computer programming)">Method</a></li> <li><a href="/wiki/State_(computer_science)" title="State (computer science)">State</a></li> <li><a class="mw-selflink selflink">Use case</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Relationships</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Association_(object-oriented_programming)" title="Association (object-oriented programming)">Association</a></li> <li><a href="/wiki/Object_composition" title="Object composition">Composition</a></li> <li><a href="/wiki/Coupling_(computer_programming)" title="Coupling (computer programming)">Dependency</a></li> <li><a href="/wiki/Generalization" title="Generalization">Generalization</a> (or <a href="/wiki/Inheritance_(object-oriented_programming)" title="Inheritance (object-oriented programming)">Inheritance</a>)</li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Extensibility</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Profile_(UML)" title="Profile (UML)">Profile</a></li> <li><a href="/wiki/Stereotype_(UML)" title="Stereotype (UML)">Stereotype</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Other</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Class_diagram#Multiplicity" title="Class diagram">Multiplicity</a></li></ul> </div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Diagrams</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%">Structure</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Class_diagram" title="Class diagram">Class</a></li> <li><a href="/wiki/Component_diagram" title="Component diagram">Component</a></li> <li><a href="/wiki/Composite_structure_diagram" title="Composite structure diagram">Composite structure</a></li> <li><a href="/wiki/Deployment_diagram" title="Deployment diagram">Deployment</a></li> <li><a href="/wiki/Object_diagram" title="Object diagram">Object</a></li> <li><a href="/wiki/Package_diagram" title="Package diagram">Package</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Behaviour</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Activity_diagram" title="Activity diagram">Activity</a></li> <li><a href="/wiki/UML_state_machine" title="UML state machine">State Machine</a></li> <li><a href="/wiki/Use_case_diagram" title="Use case diagram">Use case</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Interaction</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Communication_diagram" title="Communication diagram">Communications</a></li> <li><a href="/wiki/Sequence_diagram" title="Sequence diagram">Sequence</a></li> <li><a href="/wiki/Interaction_overview_diagram" title="Interaction overview diagram">Interaction overview</a></li> <li><a href="/wiki/Timing_diagram_(Unified_Modeling_Language)" title="Timing diagram (Unified Modeling Language)">Timing</a></li></ul> </div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Derived languages</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Systems_Modeling_Language" class="mw-redirect" title="Systems Modeling Language">Systems Modeling Language (SysML)</a></li> <li><a href="/wiki/UXF" title="UXF">UML eXchange Format (UXF)</a></li> <li><a href="/wiki/XML_Metadata_Interchange" title="XML Metadata Interchange">XML Metadata Interchange (XMI)</a></li> <li><a href="/wiki/Executable_UML" title="Executable UML">Executable UML (xUML)</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Other topics</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Glossary_of_Unified_Modeling_Language_terms" title="Glossary of Unified Modeling Language terms">Glossary of UML terms</a></li> <li><a href="/wiki/Rational_Unified_Process" class="mw-redirect" title="Rational Unified Process">Rational Unified Process</a></li> <li><a href="/wiki/List_of_Unified_Modeling_Language_tools" title="List of Unified Modeling Language tools">List of Unified Modeling Language tools</a></li> <li><a href="/wiki/Object_Modeling_in_Color" title="Object Modeling in Color">Object Modeling in Color</a></li></ul> </div></td></tr></tbody></table></div> <div class="navbox-styles"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236075235"></div><div role="navigation" class="navbox" aria-labelledby="Software_engineering318" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1239400231"><div class="navbar plainlinks hlist navbar-mini"><ul><li class="nv-view"><a href="/wiki/Template:Software_engineering" title="Template:Software engineering"><abbr title="View this template">v</abbr></a></li><li class="nv-talk"><a href="/wiki/Template_talk:Software_engineering" title="Template talk:Software engineering"><abbr title="Discuss this template">t</abbr></a></li><li class="nv-edit"><a href="/wiki/Special:EditPage/Template:Software_engineering" title="Special:EditPage/Template:Software engineering"><abbr title="Edit this template">e</abbr></a></li></ul></div><div id="Software_engineering318" style="font-size:114%;margin:0 4em"><a href="/wiki/Software_engineering" title="Software engineering">Software engineering</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">Fields</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Computer_programming" title="Computer programming">Computer programming</a></li> <li><a href="/wiki/DevOps" title="DevOps">DevOps</a></li> <li><a href="/wiki/Empirical_software_engineering" title="Empirical software engineering">Empirical software engineering</a></li> <li><a href="/wiki/Experimental_software_engineering" title="Experimental software engineering">Experimental software engineering</a></li> <li><a href="/wiki/Formal_methods" title="Formal methods">Formal methods</a></li> <li><a href="/wiki/Requirements_engineering" title="Requirements engineering">Requirements engineering</a></li> <li><a href="/wiki/Search-based_software_engineering" title="Search-based software engineering">Search-based software engineering</a></li> <li><a href="/wiki/Site_reliability_engineering" title="Site reliability engineering">Site reliability engineering</a></li> <li><a href="/wiki/Social_software_engineering" title="Social software engineering">Social software engineering</a></li> <li><a href="/wiki/Software_deployment" title="Software deployment">Software deployment</a></li> <li><a href="/wiki/Software_design" title="Software design">Software design</a></li> <li><a href="/wiki/Software_maintenance" title="Software maintenance">Software maintenance</a></li> <li><a href="/wiki/Software_testing" title="Software testing">Software testing</a></li> <li><a href="/wiki/Systems_analysis" title="Systems analysis">Systems analysis</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Concepts</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Abstraction_(computer_science)" title="Abstraction (computer science)">Abstraction</a></li> <li><a href="/wiki/CI/CD" title="CI/CD">CI/CD</a></li> <li><a href="/wiki/Computer_compatibility" title="Computer compatibility">Compatibility</a> <ul><li><a href="/wiki/Backward_compatibility" title="Backward compatibility">Backward compatibility</a></li> <li><a href="/wiki/Compatibility_layer" title="Compatibility layer">Compatibility layer</a></li> <li><a href="/wiki/Compatibility_mode" title="Compatibility mode">Compatibility mode</a></li> <li><a href="/wiki/Forward_compatibility" title="Forward compatibility">Forward compatibility</a></li> <li><a href="/wiki/Software_incompatibility" title="Software incompatibility">Software incompatibility</a></li></ul></li> <li><a href="/wiki/Component-based_software_engineering" title="Component-based software engineering">Component-based software engineering</a></li> <li><a href="/wiki/Data_modeling" title="Data modeling">Data modeling</a></li> <li><a href="/wiki/Enterprise_architecture" title="Enterprise architecture">Enterprise architecture</a></li> <li><a href="/wiki/Functional_specification" title="Functional specification">Functional specification</a></li> <li><a href="/wiki/Modeling_language" title="Modeling language">Modeling language</a></li> <li><a href="/wiki/Programming_paradigm" title="Programming paradigm">Programming paradigm</a></li> <li><a href="/wiki/Software" title="Software">Software</a></li> <li><a href="/wiki/Software_archaeology" title="Software archaeology">Software archaeology</a></li> <li><a href="/wiki/Software_architecture" title="Software architecture">Software architecture</a></li> <li><a href="/wiki/Software_configuration_management" title="Software configuration management">Software configuration management</a></li> <li><a href="/wiki/Software_development_process" title="Software development process">Software development process/methodology</a></li> <li><a href="/wiki/Software_quality" title="Software quality">Software quality</a></li> <li><a href="/wiki/Software_quality_assurance" title="Software quality assurance">Software quality assurance</a></li> <li><a href="/wiki/Software_system" title="Software system">Software system</a></li> <li><a href="/wiki/Software_verification_and_validation" title="Software verification and validation">Software verification and validation</a></li> <li><a href="/wiki/Structured_analysis" title="Structured analysis">Structured analysis</a> <ul><li><a href="/wiki/Essential_systems_analysis" title="Essential systems analysis">Essential analysis</a></li></ul></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Orientations</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Agile_software_development" title="Agile software development">Agile</a></li> <li><a href="/wiki/Aspect-oriented_programming" title="Aspect-oriented programming">Aspect-oriented</a></li> <li><a href="/wiki/Object-oriented_programming" title="Object-oriented programming">Object orientation</a></li> <li><a href="/wiki/Ontology_(information_science)" title="Ontology (information science)">Ontology</a></li> <li><a href="/wiki/Systems_development_life_cycle" title="Systems development life cycle">SDLC</a></li> <li><a href="/wiki/Service-oriented_architecture" title="Service-oriented architecture">Service orientation</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Models</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;">Developmental</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Agile_software_development" title="Agile software development">Agile</a></li> <li><a href="/wiki/Enterprise_unified_process" title="Enterprise unified process">EUP</a></li> <li><a href="/wiki/Executable_UML" title="Executable UML">Executable UML</a></li> <li><a href="/wiki/Incremental_build_model" title="Incremental build model">Incremental model</a></li> <li><a href="/wiki/Iterative_and_incremental_development" title="Iterative and incremental development">Iterative model</a></li> <li><a href="/wiki/Software_prototyping" title="Software prototyping">Prototype model</a></li> <li><a href="/wiki/Rapid_application_development" title="Rapid application development">RAD</a></li> <li><a href="/wiki/Scrum_(software_development)" title="Scrum (software development)">Scrum</a></li> <li><a href="/wiki/Spiral_model" title="Spiral model">Spiral model</a></li> <li><a href="/wiki/Unified_process" title="Unified process">UP</a></li> <li><a href="/wiki/V-model_(software_development)" title="V-model (software development)">V-model</a></li> <li><a href="/wiki/Waterfall_model" title="Waterfall model">Waterfall model</a></li> <li><a href="/wiki/Extreme_programming" title="Extreme programming">XP</a></li> <li><a href="/wiki/Model-driven_engineering" title="Model-driven engineering">Model-driven engineering</a></li> <li><a href="/wiki/Round-trip_engineering" title="Round-trip engineering">Round-trip engineering</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;">Other</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Capability_Maturity_Model_Integration" title="Capability Maturity Model Integration">CMMI</a></li> <li><a href="/wiki/Data_model" title="Data model">Data model</a></li> <li><a href="/wiki/Entity%E2%80%93relationship_model" title="Entity–relationship model">ER model</a></li> <li><a href="/wiki/Function_model" title="Function model">Function model</a></li> <li><a href="/wiki/Information_model" title="Information model">Information model</a></li> <li><a href="/wiki/Metamodeling" title="Metamodeling">Metamodeling</a></li> <li><a href="/wiki/Object_model" title="Object model">Object model</a></li> <li><a href="/wiki/ISO/IEC_15504" title="ISO/IEC 15504">SPICE</a></li> <li><a href="/wiki/Systems_modeling" title="Systems modeling">Systems model</a></li> <li><a href="/wiki/View_model" title="View model">View model</a></li></ul> </div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%;font-weight:normal;">Languages</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/IDEF" title="IDEF">IDEF</a></li> <li><a href="/wiki/Systems_modeling_language" title="Systems modeling language">SysML</a></li> <li><a href="/wiki/Unified_Modeling_Language" title="Unified Modeling Language">UML</a></li> <li><a href="/wiki/Universal_Systems_Language" title="Universal Systems Language">USL</a></li></ul> </div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Related fields</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"> <ul><li><a href="/wiki/Computer_engineering" title="Computer engineering">Computer engineering</a></li> <li><a href="/wiki/Computer_science" title="Computer science">Computer science</a></li> <li><a href="/wiki/Information_science" title="Information science">Information science</a></li> <li><a href="/wiki/Project_management" title="Project management">Project management</a></li> <li><a href="/wiki/Risk_management" title="Risk management">Risk management</a></li> <li><a href="/wiki/Systems_engineering" title="Systems engineering">Systems engineering</a></li></ul> </div></td></tr><tr><td class="navbox-abovebelow" colspan="2" style="font-weight:bold;"><div> <ul><li><span class="noviewer" typeof="mw:File"><span title="Category"><img alt="" src="//upload.wikimedia.org/wikipedia/en/thumb/9/96/Symbol_category_class.svg/16px-Symbol_category_class.svg.png" decoding="async" width="16" height="16" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/en/thumb/9/96/Symbol_category_class.svg/23px-Symbol_category_class.svg.png 1.5x, //upload.wikimedia.org/wikipedia/en/thumb/9/96/Symbol_category_class.svg/31px-Symbol_category_class.svg.png 2x" data-file-width="180" data-file-height="185" /></span></span> <a href="/wiki/Category:Software_engineering" title="Category:Software engineering">Category</a></li> <li><span class="noviewer" typeof="mw:File"><span title="Commons page"><img alt="" src="//upload.wikimedia.org/wikipedia/en/thumb/4/4a/Commons-logo.svg/12px-Commons-logo.svg.png" decoding="async" width="12" height="16" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/en/thumb/4/4a/Commons-logo.svg/18px-Commons-logo.svg.png 1.5x, //upload.wikimedia.org/wikipedia/en/thumb/4/4a/Commons-logo.svg/24px-Commons-logo.svg.png 2x" data-file-width="1024" data-file-height="1376" /></span></span> <a href="https://commons.wikimedia.org/wiki/Category:Software_engineering" class="extiw" title="commons:Category:Software engineering">Commons</a></li></ul> </div></td></tr></tbody></table></div> <div class="navbox-styles"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1129693374"><link rel="mw-deduplicated-inline-style" href="mw-data:TemplateStyles:r1236075235"></div><div role="navigation" class="navbox authority-control" aria-label="Navbox581" style="padding:3px"><table class="nowraplinks hlist navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="row" class="navbox-group" style="width:1%"><a href="/wiki/Help:Authority_control" title="Help:Authority control">Authority control databases</a>: National <span class="mw-valign-text-top noprint" typeof="mw:File/Frameless"><a href="https://www.wikidata.org/wiki/Q613417#identifiers" title="Edit this at Wikidata"><img alt="Edit this at Wikidata" src="//upload.wikimedia.org/wikipedia/en/thumb/8/8a/OOjs_UI_icon_edit-ltr-progressive.svg/10px-OOjs_UI_icon_edit-ltr-progressive.svg.png" decoding="async" width="10" height="10" class="mw-file-element" srcset="//upload.wikimedia.org/wikipedia/en/thumb/8/8a/OOjs_UI_icon_edit-ltr-progressive.svg/15px-OOjs_UI_icon_edit-ltr-progressive.svg.png 1.5x, //upload.wikimedia.org/wikipedia/en/thumb/8/8a/OOjs_UI_icon_edit-ltr-progressive.svg/20px-OOjs_UI_icon_edit-ltr-progressive.svg.png 2x" data-file-width="20" data-file-height="20" /></a></span></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><span class="uid"><a rel="nofollow" class="external text" href="https://d-nb.info/gnd/1299587100">Germany</a></span></li><li><span class="uid"><a rel="nofollow" class="external text" href="https://id.loc.gov/authorities/sh98004228">United States</a></span></li><li><span class="uid"><a rel="nofollow" class="external text" href="https://www.nli.org.il/en/authorities/987007532654505171">Israel</a></span></li></ul></div></td></tr></tbody></table></div> <!-- NewPP limit report Parsed by mw‐api‐int.codfw.main‐5b65fffc7d‐xw2n6 Cached time: 20250216031615 Cache expiry: 2592000 Reduced expiry: false Complications: [vary‐revision‐sha1, show‐toc] CPU time usage: 0.776 seconds Real time usage: 0.931 seconds Preprocessor visited node count: 6067/1000000 Post‐expand include size: 149635/2097152 bytes Template argument size: 6802/2097152 bytes Highest expansion depth: 16/100 Expensive parser function count: 11/500 Unstrip recursion depth: 1/20 Unstrip post‐expand size: 149527/5000000 bytes Lua time usage: 0.444/10.000 seconds Lua memory usage: 7407393/52428800 bytes Number of Wikibase entities loaded: 1/400 --> <!-- Transclusion expansion time report (%,ms,calls,template) 100.00% 779.972 1 -total 28.98% 226.033 1 Template:Reflist 16.12% 125.747 14 Template:Cite_web 11.83% 92.232 1 Template:Software_development_process 11.51% 89.775 1 Template:Sidebar_with_collapsible_lists 10.50% 81.920 7 Template:Fix 9.44% 73.597 5 Template:Citation_needed 9.20% 71.736 8 Template:Rp 8.43% 65.760 5 Template:Navbox 8.38% 65.382 8 Template:R/superscript --> <!-- Saved in parser cache with key enwiki:pcache:300006:|#|:idhash:canonical and timestamp 20250216031615 and revision id 1275966836. Rendering was triggered because: api-parse --> </div><!--esi <esi:include src="/esitest-fa8a495983347898/content" /> --><noscript><img src="https://login.wikimedia.org/wiki/Special:CentralAutoLogin/start?useformat=desktop&amp;type=1x1&amp;usesul3=0" alt="" width="1" height="1" style="border: none; position: absolute;"></noscript> <div class="printfooter" data-nosnippet="">Retrieved from "<a dir="ltr" href="https://en.wikipedia.org/w/index.php?title=Use_case&amp;oldid=1275966836">https://en.wikipedia.org/w/index.php?title=Use_case&amp;oldid=1275966836</a>"</div></div> <div id="catlinks" class="catlinks" data-mw="interface"><div id="mw-normal-catlinks" class="mw-normal-catlinks"><a href="/wiki/Help:Category" title="Help:Category">Categories</a>: <ul><li><a href="/wiki/Category:Software_project_management" title="Category:Software project management">Software project management</a></li><li><a href="/wiki/Category:Software_requirements" title="Category:Software requirements">Software requirements</a></li><li><a href="/wiki/Category:Unified_Modeling_Language" title="Category:Unified Modeling Language">Unified Modeling Language</a></li><li><a href="/wiki/Category:Systems_Modeling_Language" title="Category:Systems Modeling Language">Systems Modeling Language</a></li><li><a href="/wiki/Category:1986_establishments_in_Sweden" title="Category:1986 establishments in Sweden">1986 establishments in Sweden</a></li><li><a href="/wiki/Category:1986_in_computing" title="Category:1986 in computing">1986 in computing</a></li><li><a href="/wiki/Category:Swedish_inventions" title="Category:Swedish inventions">Swedish inventions</a></li><li><a href="/wiki/Category:Agile_software_development" title="Category:Agile software development">Agile software development</a></li><li><a href="/wiki/Category:1986_neologisms" title="Category:1986 neologisms">1986 neologisms</a></li></ul></div><div id="mw-hidden-catlinks" class="mw-hidden-catlinks mw-hidden-cats-hidden">Hidden categories: <ul><li><a href="/wiki/Category:Use_dmy_dates_from_August_2020" title="Category:Use dmy dates from August 2020">Use dmy dates from August 2020</a></li><li><a href="/wiki/Category:Articles_with_short_description" title="Category:Articles with short description">Articles with short description</a></li><li><a href="/wiki/Category:Short_description_is_different_from_Wikidata" title="Category:Short description is different from Wikidata">Short description is different from Wikidata</a></li><li><a href="/wiki/Category:All_articles_with_unsourced_statements" title="Category:All articles with unsourced statements">All articles with unsourced statements</a></li><li><a href="/wiki/Category:Articles_with_unsourced_statements_from_March_2016" title="Category:Articles with unsourced statements from March 2016">Articles with unsourced statements from March 2016</a></li><li><a href="/wiki/Category:Articles_with_unsourced_statements_from_October_2013" title="Category:Articles with unsourced statements from October 2013">Articles with unsourced statements from October 2013</a></li><li><a href="/wiki/Category:Articles_to_be_expanded_from_July_2015" title="Category:Articles to be expanded from July 2015">Articles to be expanded from July 2015</a></li><li><a href="/wiki/Category:All_articles_to_be_expanded" title="Category:All articles to be expanded">All articles to be expanded</a></li><li><a href="/wiki/Category:All_articles_with_specifically_marked_weasel-worded_phrases" title="Category:All articles with specifically marked weasel-worded phrases">All articles with specifically marked weasel-worded phrases</a></li><li><a href="/wiki/Category:Articles_with_specifically_marked_weasel-worded_phrases_from_March_2022" title="Category:Articles with specifically marked weasel-worded phrases from March 2022">Articles with specifically marked weasel-worded phrases from March 2022</a></li><li><a href="/wiki/Category:Articles_with_unsourced_statements_from_March_2022" title="Category:Articles with unsourced statements from March 2022">Articles with unsourced statements from March 2022</a></li><li><a href="/wiki/Category:Articles_needing_additional_references_from_August_2013" title="Category:Articles needing additional references from August 2013">Articles needing additional references from August 2013</a></li><li><a href="/wiki/Category:All_articles_needing_additional_references" title="Category:All articles needing additional references">All articles needing additional references</a></li></ul></div></div> </div> </main> </div> <div class="mw-footer-container"> <footer id="footer" class="mw-footer" > <ul id="footer-info"> <li id="footer-info-lastmod"> This page was last edited on 16 February 2025, at 03:16<span class="anonymous-show">&#160;(UTC)</span>.</li> <li id="footer-info-copyright">Text is available under the <a href="/wiki/Wikipedia:Text_of_the_Creative_Commons_Attribution-ShareAlike_4.0_International_License" title="Wikipedia:Text of the Creative Commons Attribution-ShareAlike 4.0 International License">Creative Commons Attribution-ShareAlike 4.0 License</a>; additional terms may apply. By using this site, you agree to the <a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Terms_of_Use" class="extiw" title="foundation:Special:MyLanguage/Policy:Terms of Use">Terms of Use</a> and <a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Privacy_policy" class="extiw" title="foundation:Special:MyLanguage/Policy:Privacy policy">Privacy Policy</a>. Wikipedia® is a registered trademark of the <a rel="nofollow" class="external text" href="https://wikimediafoundation.org/">Wikimedia Foundation, Inc.</a>, a non-profit organization.</li> </ul> <ul id="footer-places"> <li id="footer-places-privacy"><a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Privacy_policy">Privacy policy</a></li> <li id="footer-places-about"><a href="/wiki/Wikipedia:About">About Wikipedia</a></li> <li id="footer-places-disclaimers"><a href="/wiki/Wikipedia:General_disclaimer">Disclaimers</a></li> <li id="footer-places-contact"><a href="//en.wikipedia.org/wiki/Wikipedia:Contact_us">Contact Wikipedia</a></li> <li id="footer-places-wm-codeofconduct"><a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Universal_Code_of_Conduct">Code of Conduct</a></li> <li id="footer-places-developers"><a href="https://developer.wikimedia.org">Developers</a></li> <li id="footer-places-statslink"><a href="https://stats.wikimedia.org/#/en.wikipedia.org">Statistics</a></li> <li id="footer-places-cookiestatement"><a href="https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:Cookie_statement">Cookie statement</a></li> <li id="footer-places-mobileview"><a href="//en.m.wikipedia.org/w/index.php?title=Use_case&amp;mobileaction=toggle_view_mobile" class="noprint stopMobileRedirectToggle">Mobile view</a></li> </ul> <ul id="footer-icons" class="noprint"> <li id="footer-copyrightico"><a href="https://wikimediafoundation.org/" class="cdx-button cdx-button--fake-button cdx-button--size-large cdx-button--fake-button--enabled"><img src="/static/images/footer/wikimedia-button.svg" width="84" height="29" alt="Wikimedia Foundation" lang="en" loading="lazy"></a></li> <li id="footer-poweredbyico"><a href="https://www.mediawiki.org/" class="cdx-button cdx-button--fake-button cdx-button--size-large cdx-button--fake-button--enabled"><picture><source media="(min-width: 500px)" srcset="/w/resources/assets/poweredby_mediawiki.svg" width="88" height="31"><img src="/w/resources/assets/mediawiki_compact.svg" alt="Powered by MediaWiki" width="25" height="25" loading="lazy"></picture></a></li> </ul> </footer> </div> </div> </div> <div class="vector-header-container vector-sticky-header-container"> <div id="vector-sticky-header" class="vector-sticky-header"> <div class="vector-sticky-header-start"> <div class="vector-sticky-header-icon-start vector-button-flush-left vector-button-flush-right" aria-hidden="true"> <button class="cdx-button cdx-button--weight-quiet cdx-button--icon-only vector-sticky-header-search-toggle" tabindex="-1" data-event-name="ui.vector-sticky-search-form.icon"><span class="vector-icon mw-ui-icon-search mw-ui-icon-wikimedia-search"></span> <span>Search</span> </button> </div> <div role="search" class="vector-search-box-vue vector-search-box-show-thumbnail vector-search-box"> <div class="vector-typeahead-search-container"> <div class="cdx-typeahead-search cdx-typeahead-search--show-thumbnail"> <form action="/w/index.php" id="vector-sticky-search-form" class="cdx-search-input cdx-search-input--has-end-button"> <div class="cdx-search-input__input-wrapper" data-search-loc="header-moved"> <div class="cdx-text-input cdx-text-input--has-start-icon"> <input class="cdx-text-input__input" type="search" name="search" placeholder="Search Wikipedia"> <span class="cdx-text-input__icon cdx-text-input__start-icon"></span> </div> <input type="hidden" name="title" value="Special:Search"> </div> <button class="cdx-button cdx-search-input__end-button">Search</button> </form> </div> </div> </div> <div class="vector-sticky-header-context-bar"> <nav aria-label="Contents" class="vector-toc-landmark"> <div id="vector-sticky-header-toc" class="vector-dropdown mw-portlet mw-portlet-sticky-header-toc vector-sticky-header-toc vector-button-flush-left" > <input type="checkbox" id="vector-sticky-header-toc-checkbox" role="button" aria-haspopup="true" data-event-name="ui.dropdown-vector-sticky-header-toc" class="vector-dropdown-checkbox " aria-label="Toggle the table of contents" > <label id="vector-sticky-header-toc-label" for="vector-sticky-header-toc-checkbox" class="vector-dropdown-label cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only " aria-hidden="true" ><span class="vector-icon mw-ui-icon-listBullet mw-ui-icon-wikimedia-listBullet"></span> <span class="vector-dropdown-label-text">Toggle the table of contents</span> </label> <div class="vector-dropdown-content"> <div id="vector-sticky-header-toc-unpinned-container" class="vector-unpinned-container"> </div> </div> </div> </nav> <div class="vector-sticky-header-context-bar-primary" aria-hidden="true" ><span class="mw-page-title-main">Use case</span></div> </div> </div> <div class="vector-sticky-header-end" aria-hidden="true"> <div class="vector-sticky-header-icons"> <a href="#" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only" id="ca-talk-sticky-header" tabindex="-1" data-event-name="talk-sticky-header"><span class="vector-icon mw-ui-icon-speechBubbles mw-ui-icon-wikimedia-speechBubbles"></span> <span></span> </a> <a href="#" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only" id="ca-subject-sticky-header" tabindex="-1" data-event-name="subject-sticky-header"><span class="vector-icon mw-ui-icon-article mw-ui-icon-wikimedia-article"></span> <span></span> </a> <a href="#" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only" id="ca-history-sticky-header" tabindex="-1" data-event-name="history-sticky-header"><span class="vector-icon mw-ui-icon-wikimedia-history mw-ui-icon-wikimedia-wikimedia-history"></span> <span></span> </a> <a href="#" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only mw-watchlink" id="ca-watchstar-sticky-header" tabindex="-1" data-event-name="watch-sticky-header"><span class="vector-icon mw-ui-icon-wikimedia-star mw-ui-icon-wikimedia-wikimedia-star"></span> <span></span> </a> <a href="#" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only" id="ca-edit-sticky-header" tabindex="-1" data-event-name="wikitext-edit-sticky-header"><span class="vector-icon mw-ui-icon-wikimedia-wikiText mw-ui-icon-wikimedia-wikimedia-wikiText"></span> <span></span> </a> <a href="#" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only" id="ca-ve-edit-sticky-header" tabindex="-1" data-event-name="ve-edit-sticky-header"><span class="vector-icon mw-ui-icon-wikimedia-edit mw-ui-icon-wikimedia-wikimedia-edit"></span> <span></span> </a> <a href="#" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--icon-only" id="ca-viewsource-sticky-header" tabindex="-1" data-event-name="ve-edit-protected-sticky-header"><span class="vector-icon mw-ui-icon-wikimedia-editLock mw-ui-icon-wikimedia-wikimedia-editLock"></span> <span></span> </a> </div> <div class="vector-sticky-header-buttons"> <button class="cdx-button cdx-button--weight-quiet mw-interlanguage-selector" id="p-lang-btn-sticky-header" tabindex="-1" data-event-name="ui.dropdown-p-lang-btn-sticky-header"><span class="vector-icon mw-ui-icon-wikimedia-language mw-ui-icon-wikimedia-wikimedia-language"></span> <span>28 languages</span> </button> <a href="#" class="cdx-button cdx-button--fake-button cdx-button--fake-button--enabled cdx-button--weight-quiet cdx-button--action-progressive" id="ca-addsection-sticky-header" tabindex="-1" data-event-name="addsection-sticky-header"><span class="vector-icon mw-ui-icon-speechBubbleAdd-progressive mw-ui-icon-wikimedia-speechBubbleAdd-progressive"></span> <span>Add topic</span> </a> </div> <div class="vector-sticky-header-icon-end"> <div class="vector-user-links"> </div> </div> </div> </div> </div> <div class="vector-settings" id="p-dock-bottom"> <ul></ul> </div><script>(RLQ=window.RLQ||[]).push(function(){mw.config.set({"wgHostname":"mw-web.codfw.main-b766959bd-8qrxf","wgBackendResponseTime":160,"wgPageParseReport":{"limitreport":{"cputime":"0.776","walltime":"0.931","ppvisitednodes":{"value":6067,"limit":1000000},"postexpandincludesize":{"value":149635,"limit":2097152},"templateargumentsize":{"value":6802,"limit":2097152},"expansiondepth":{"value":16,"limit":100},"expensivefunctioncount":{"value":11,"limit":500},"unstrip-depth":{"value":1,"limit":20},"unstrip-size":{"value":149527,"limit":5000000},"entityaccesscount":{"value":1,"limit":400},"timingprofile":["100.00% 779.972 1 -total"," 28.98% 226.033 1 Template:Reflist"," 16.12% 125.747 14 Template:Cite_web"," 11.83% 92.232 1 Template:Software_development_process"," 11.51% 89.775 1 Template:Sidebar_with_collapsible_lists"," 10.50% 81.920 7 Template:Fix"," 9.44% 73.597 5 Template:Citation_needed"," 9.20% 71.736 8 Template:Rp"," 8.43% 65.760 5 Template:Navbox"," 8.38% 65.382 8 Template:R/superscript"]},"scribunto":{"limitreport-timeusage":{"value":"0.444","limit":"10.000"},"limitreport-memusage":{"value":7407393,"limit":52428800}},"cachereport":{"origin":"mw-api-int.codfw.main-5b65fffc7d-xw2n6","timestamp":"20250216031615","ttl":2592000,"transientcontent":false}}});});</script> <script type="application/ld+json">{"@context":"https:\/\/schema.org","@type":"Article","name":"Use case","url":"https:\/\/en.wikipedia.org\/wiki\/Use_case","sameAs":"http:\/\/www.wikidata.org\/entity\/Q613417","mainEntity":"http:\/\/www.wikidata.org\/entity\/Q613417","author":{"@type":"Organization","name":"Contributors to Wikimedia projects"},"publisher":{"@type":"Organization","name":"Wikimedia Foundation, Inc.","logo":{"@type":"ImageObject","url":"https:\/\/www.wikimedia.org\/static\/images\/wmf-hor-googpub.png"}},"datePublished":"2003-08-19T18:56:58Z","dateModified":"2025-02-16T03:16:09Z","headline":"list of actions or event steps typically defining the interactions between a user role and a system to achieve a goal"}</script> </body> </html>

Pages: 1 2 3 4 5 6 7 8 9 10