Use case - Knowledge

1401:

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).

22: 1918:, 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. 3587: 1405: 1076: 1890:) 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. 2023: 4520: 2191: 1629: 4510: 1376:, 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." 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. 800:, 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. 1347:

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.

1937:

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

1624:

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

1355:

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

1346:

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

1992:

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

856:

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. The decomposition of the goal is performed from the point of view of the users, and independently

1400:

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

1379:

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

1751:

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

1387:

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). In turn, a User is both a "normal operator" (an actor using the system for

1371:

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

2070:

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

1866:

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

792:

Use cases are a technique for capturing, modeling, and specifying the requirements of a system. 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

1615:

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.

835:

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. This practice was developed with the aim of supporting the user-centric design and avoiding to induce bias

1905:

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,

1870:

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

1862:

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

771:

published in 2000 a goal-oriented use case practice based on text narratives and tabular specifications; Kurt Bittner and Ian Spence developed in 2002 advanced practices for analyzing functional requirements with use cases; Dean Leffingwell and Don Widrig proposed to apply use cases to change

839:

Use Case 2.0 to adapt the technique for the context of agile development methods. 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

1383:

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

1971:(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 827:

System use cases specify the requirements of a system to be developed. 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

1391:

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.

1388:

its intended purpose) and a "functional beneficiary" (a stakeholder who benefits from the use of the system). 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.

2154:) 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 1266:

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:

2173:) 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 1002: 2137:

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

2149:

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

1038: 987: 1056: 1020: 779:

to adapt the technique to an agile context, enriching it with incremental use case "slices", and promoting its use across the full development lifecycle after having presented the renewed approach at the annual

781: 831:

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

962:

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:

1803:

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.

1193: 2169:), 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 ( 2109:

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

1153: 1133: 1859:

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.

1611:

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

1608:(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. 1989:

Use cases are a starting point for test design, but since each test needs its own success criteria, use cases may need to be modified to provide separate post-conditions for each path.

1219:

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:

1113: 938:

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.

1173: 1545: 1938:

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.

2815: 1886:

Use cases constitute a powerful, user-centric tool for the software requirements specification process. Use case modeling typically starts from identifying key stakeholder roles (

1986:

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.

1874:

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.

2100:

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.

767:, 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; 1311:

states "There is no standard way to write the content of a use case, and different formats work well in different cases." He describes "a common style to use" as follows:

1788:

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.

815:, techniques. But the use cases also support narrative-based requirement gathering, incremental requirement acquisition, system documentation, and acceptance testing. 638:) 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 1683:

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.

571: 1203:

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.

3519: 1625:

the basic flow or extensions. This practice makes the requirement specification clearer and maximizes the flexibility of the design and implementation.

1979:. 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. 525: 1384:

clearances" should be designed for the sales rep and clerk, but that the customer and marketing department are the roles concerned about the results.

1329:

Extension: "a condition that results in different interactions from .. the main success scenario". An extension from main step 3 is numbered 3a, etc.

1083:

Cockburn suggests annotating each use case with a symbol to show the "Goal Level"; the preferred level is "User-goal" (or colloquially "sea level").

1867:

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.

772:

management and stakeholder communication activities; Gunnar Overgaard proposed in 2004 to extend the principles of design patterns to use cases.

3482: 2457: 3996: 1950:

Use cases are not well suited to capturing non-interaction-based requirements of a system (such as algorithm or mathematical requirements) or

492: 2255:

with template support are often used to write use cases. For large and complex system requirements, dedicated use case tools are helpful.

1283:

Cockburn recognizes that projects may not always need detailed "fully dressed" use cases. He describes a Casual use case with the fields:

3948: 1552: 3897: 1906:

end-users, developers, testers, and managers. Better communications result in quality requirements and thus quality systems delivered.

1521: 564: 344: 3750: 3731: 2076:

Use case techniques have evolved to take Agile approaches into account by using use case slices to incrementally enrich a use case.

1878:

In summary, specifying system requirements in use cases have these apparent benefits compared with traditional or other approaches:

3958: 3512: 1263:

In addition, Cockburn suggests using two devices to indicate the nature of each use case: icons for design scope and goal level.

608:

A usage scenario for a piece of software; often used in the plural to suggest situations where a piece of software may be useful.

4564: 3659: 804: 482: 334: 4513: 4379: 4308: 2967: 2902: 1964:, are ambiguous in interpretation and can be difficult for stakeholders to understand as pointed out by Cockburn (Problem #6) 557: 457: 213: 198: 4544: 4202: 4105: 870: 698: 477: 4579: 3613: 896: 729: 515: 1954:(such as platform, performance, timing, or safety-critical aspects). These are better specified declaratively elsewhere. 1716:

An edit record for the article is created by the system, so watchers of the article can be informed of the update later.

4559: 4554: 3989: 3505: 424: 188: 4182: 4049: 4034: 3328: 3183: 2784: 2751: 2718: 2680: 2600: 2535: 2499: 2238: 1308: 291: 2220: 2867: 1416:(goals) which represents the interactions between a restaurant (the business system) and its primary stakeholders ( 414: 409: 165: 3741: 3476: 2267: 1843:

has been so popular that many think it is the only and best solution for the agile requirements of all projects.

1758:

The member fills out the edit summary, tells the system if they want to watch this article, and submits the edit.

812: 714: 543: 1001: 4549: 4338: 4265: 4255: 4100: 4029: 2216: 1335:

The Fowler style can also be viewed as a simplified variant of the Cockburn template. This variant is called a

434: 147: 127: 1921:

Minimizing and optimizing the action steps of a use case to achieve the user goal also contribute to a better

1436: 296: 4523: 4389: 4318: 4260: 3982: 3705: 2145:

Spending much time writing tedious use cases which add no or little value and result in a lot of rework is a

233: 223: 173: 1037: 986: 611:

A potential scenario in which a system receives an external request (such as user input) and responds to it.

4328: 4187: 4054: 3892: 3649: 1506: 1299:(Story): the body of the use case is simply a paragraph or two of text, informally describing what happens. 520: 248: 64: 4574: 4250: 4245: 4059: 3825: 3608: 2841: 2002: 1951: 1460: 339: 311: 2396: 2071:

group finds useful. But whatever the approach, most items should focus on delivering value to customers.

1055: 1019: 4569: 4445: 4293: 4288: 4240: 4217: 4197: 1957:

As there are no fully standard definitions of use cases, each project must form its own interpretation.

1538: 910: 462: 306: 193: 183: 122: 2280:'s RequisitePro - one of the early, well-known use case and requirement management tools in the 1990s. 4450: 4440: 3917: 3664: 3528: 2465: 2212: 1994: 1972: 1566: 876: 741: 737: 647: 629: 628:

is a list of actions or event steps typically defining the interactions between a role (known in the

617: 228: 208: 3472: 4353: 4152: 4135: 4044: 3963: 3953: 3927: 3710: 3618: 2348: 2201: 889: 808: 369: 238: 218: 4303: 4147: 3547: 2929: 2318: 2205: 1605: 903: 745: 702: 686:– but found that neither of these terms sounded natural in English, and eventually he settled on 497: 379: 258: 132: 3463: 3384:

Software for Use: A Practical Guide to the Essential Models and Methods of Usage-Centered Design

3238: 4358: 4115: 4110: 3252: 2283: 2034: 1926: 853:

The subject identifies the system, sub-system, or component that will provide the interactions.

439: 349: 301: 243: 2113:

practice and will unnecessarily complicate the use case writing and limit its implementation.

1761:

The system saves the article, logs the edit event, and finishes any necessary post-processing.

4177: 4130: 3882: 3639: 3447:

Object-Oriented Analysis and Design for Information Systems: Modeling with UML, OCL, and IFML

3175: 3168: 2489: 2166: 1740:

The member invokes an edit request (for the full article or just one section) on the article.

1597: 1501: 797: 764: 263: 79: 69: 4475: 4313: 4172: 4162: 4074: 4019: 4005: 2353: 1894: 706: 639: 585: 359: 203: 137: 104: 84: 45: 3788: 759:

Since then, many authors have contributed to the development of the technique, notably:

674:

techniques to drive object-oriented analysis and design. Originally he had used the terms

8: 4495: 4480: 4348: 4212: 4120: 4064: 3306:"The Scrum Primer: A Lightweight Guide to the Theory and Practice of Scrum (Version 2.0)" 2062: 1976: 1840: 1373: 1271:

Variation scenarios "(maybe branching off from and maybe returning to the main scenario)"

643: 589: 354: 273: 99: 21: 3200: 2628: 709:. In 1994 he published a book about use cases and object-oriented techniques applied to 4485: 4125: 3830: 3736: 2995: 2648: 2323: 1922: 1914:

One of the most powerful things about use cases resides in the formats of the use case

1465: 1067:

Other authors sometimes call use cases at the Organization level "Business use cases".

615:

This article discusses the latter sense. (For more on the other sense, see for example

472: 2426: 2124:

are often used as handy and valuable tools, at least as lightweight as user stories.

4399: 4157: 3861: 3820: 3467: 3324: 3219: 3179: 2973: 2963: 2908: 2898: 2790: 2780: 2757: 2747: 2724: 2714: 2686: 2676: 2606: 2596: 2559: 2541: 2531: 2505: 2495: 2333: 2296: 2277: 1893:

Use case authoring has been an important and valuable analysis tool in the domain of

1848: 1844: 1601: 1516: 1455: 1192: 947: 768: 760: 3108: 2819: 2652: 4470: 4414: 4192: 4084: 4079: 3887: 3866: 3856: 3772: 3586: 3303: 2640: 2438: 2328: 1593: 1589: 1570: 1526: 1511: 1496: 1409: 429: 392: 374: 364: 89: 26: 4490: 4343: 4323: 4207: 4069: 3840: 3700: 3674: 3654: 2528:

The object advantage : business process reengineering with object technology

2368: 1480: 1475: 882: 753: 671: 316: 268: 152: 74: 1152: 4394: 4298: 4039: 3932: 3835: 3746: 3690: 3644: 3574: 2252: 1983: 1968: 1470: 1132: 740:

respectively. In 1995 Ivar Jacobson joined them and together they created the

725: 710: 670:

to capture and specify requirements of a system using textual, structural, and

3305: 3304:

Pete Deemer; Gabrielle Benefield; Craig Larman; Bas Vodde (17 December 2012).

2525: 2105:

Novice misunderstandings. Each step of a well-written use case should present

857:

of the system, which differs from traditional functional decomposition.

4538: 4374: 4142: 3815: 3767: 3669: 3569: 2912: 2842:"Business Analysis Conference Europe 2011 - 26-28 September 2011, London, UK" 2811: 2610: 2313: 2288: 1574: 1450: 659: 59: 3497: 2977: 2794: 2761: 2728: 2690: 2545: 2509: 2490:

Jacobson Ivar; Christerson Magnus; Jonsson Patrik; Övergaard Gunnar (1992).

1404: 1321:

Step: "a simple statement of the interaction between the actor and a system"

1223:

Title: "an active-verb goal phrase that names the goal of the primary actor"

4409: 4404: 4333: 3552: 3486: 2991: 2262: 2084: 733: 701:

system engineering method and helped to popularize use cases for capturing

142: 2892: 2644: 1075: 3695: 3634: 3564: 2343: 2338: 1366: 1274:

Exceptions "i.e. exception events and their exception-handling scenarios"

1112: 836:

about the user interface in the early stage of the system specifications.

748:

in 1997. Jacobson, Booch and Rumbaugh also worked on a refinement of the

721: 634: 3491: 3459: 2442: 2022: 1818:

The system discards any change the member has made, then goes to step 5.

1755:

The member modifies the article's content until the member is satisfied.

1172: 823:

There are different kinds of use cases and variations in the technique:

4419: 4384: 3974: 2590: 2394: 2358: 2308: 1836: 1675: 1336: 775:

In 2011, Jacobson published with Ian Spence and Kurt Bittner the ebook

601: 2291:- good tools for teams to author and manage use cases collaboratively. 1967:

Use case developers often find it difficult to determine the level of

1871:

issues. Except it is done at investigation time, not programming time.

2933: 2363: 2272: 2006: 1604:

can also be used to visualize use cases accordingly. Specifically, a

1578: 749: 94: 2960:

More about software requirements: thorny issues and practical advice

2897:(Version 3.0 ed.). IEEE Computer Society. pp. 1-6 to 1-8. 2670: 2190: 1569:, the relationships between use cases and actors are represented in 4167: 2128:

Writing use cases for large systems is tedious and a waste of time.

2065:

are neutral on requirement techniques. As the Scrum Primer states,

899:(SRS), as an alternative structure for the functional requirements; 667: 597: 467: 419: 404: 399: 3483:

Application of use cases for stakeholder analysis "Project Icarus"

1764:

The system presents the updated view of the article to the member.

1628: 954:

has been one of the most widely used writing styles of use cases.

849:

The scope of a use case can be defined by a subject and by goals:

3405:

Object-Oriented Software Engineering - A Use Case Driven Approach

2845: 2560:"About the Unified Modeling Language Specification Version 2.5.1" 2177:

in hand, not because of the poor writing skills of its authors.

1565:

Use cases are not only texts but also diagrams if needed. In the

695:

Object-Oriented Software Engineering - A Use Case Driven Approach

2492:

Object-oriented software engineering: a use case driven approach

2299:

support both the text writing and visual modeling of use cases.

744:, which includes use case modeling. UML was standardized by the 4024: 756:

was published in 1999 and promoted a use case driven approach.

663: 178: 3349:

Discovering Requirements: How to Specify Products and Services

4224: 2395:

Dr. Ivar Jacobson; Ian Spence; Kurt Bittner (December 2011).

2116:

As for capturing requirements for a new system from scratch,

1582: 1380:

the system to restock the cash drawer on behalf of the bank.

866:

Use cases are known to be applied in the following contexts:

646:

goals. The detailed requirements may then be captured in the

253: 1729:

The article with editing enabled is presented to the member.

666:'87 conference. He described how this technique was used at 4435: 3391:

Succeeding with Use Cases: Working Smart to Deliver Quality

2895:

SWEBOK: guide to the software engineering body of knowledge

2526:

Jacobson, Ivar.; Ericsson, Maria; Jacobson, Agneta (1995).

2087:

stresses that "use cases are not diagrams, they are text".

1654: 793:

that human users or other systems have in the interaction.

487: 30: 3086:

Cockburn, 2001. Inside rear cover. Field "Use Case Title".

2427:"Object-oriented development in an industrial environment" 922:

There are many ways to write a use case in the text, from

3922: 3403:

Jacobson Ivar, Christerson M., Jonsson P., Övergaard G.,

3253:"Alistair.Cockburn.us - Structuring use cases with goals" 3019:

Cockburn, 2001. Inside front cover. Icons "Design Scope".

2744:

Managing software requirements : a use case approach

1326:

Extensions: separately numbered lists, one per Extension

886: 3041:

Cockburn, 2001. Inside front cover. Icons "Goal Level".

3032:. Chapter 3 in Alexander and Maiden, 2004. Pages 39-59. 2934:"Unified Modeling Language Specification Version 2.5.1" 2928: 1998: 2820:"Use Case 2.0: The Guide to Succeeding with Use Cases" 682:– the latter a direct translation of his Swedish term 2893:

Bourque, Pierre; Fairley, R. E. (Richard E.) (2014).

2810: 2165:, e.g. the RUP's and the Cockburn's (also adopted by 3412:

Use Case 2.0: The Guide to Succeeding with Use Cases

2957: 2591:

Jacobson, Ivar; Booch, Grady; Rumbaugh, Jim (1999).

1847:

lists five reasons why he still writes use cases in

902:

deriving the design from the requirements using the

3419:

Managing Software Requirements: A Use Case Approach

2668: 2629:"Essential modeling: use cases for user interfaces" 1588:In addition, other behavioral UML diagrams such as 3167: 2774: 2741: 1713:The article is saved and an updated view is shown. 3440:Applying Use Cases 2nd Edition: A Practical Guide 3236: 33:system. Registered user of Wiki edits an article. 4536: 3174:. New York: Wiley Computer Publishing. pp. 1585:uses the same notation at a system block level. 662:presented the first article on use cases at the 3421:, Addison-Wesley Professional. 7 December 2012. 2746:. Widrig, Don. (2nd ed.). Addison-Wesley. 2258:Some of the well-known use case tools include: 1835:Since the inception of the agile movement, the 1315:Title: "goal the use case is trying to satisfy" 805:Software Engineering Body of Knowledge (SWEBOK) 3372:, Addison-Wesley Professional, 20 August 2002. 3103: 3101: 3073: 3071: 2053:Common misunderstandings about use cases are: 1910:Quality requirements by structured exploration 1318:Main Success Scenario: numbered list of steps 3990: 3527: 3513: 3131: 3129: 3127: 3125: 2990: 2708: 1546: 565: 3363:Advanced Use Case Modeling: Software Systems 3217: 2775:Övergaard, Gunnar; Palmkvist, Karin (2005). 2161:In fact, the use case formats formulated by 879:(UML), as a behavioral modelling instrument; 752:software development process. The resulting 3239:"Traceability from Use Cases to Test Cases" 3098: 3068: 2626: 2219:. Unsourced material may be challenged and 2091:Use cases have too much UI-related content. 871:Object Oriented Software Engineering (OOSE) 3997: 3983: 3520: 3506: 3138: 3122: 2595:. Reading, Massachusetts: Addison-Wesley. 2057:User stories are agile; use cases are not. 1553: 1539: 572: 558: 3061: 3059: 3057: 3055: 3053: 3051: 3049: 3047: 2996:"System Use Cases: An Agile Introduction" 2239:Learn how and when to remove this message 1933:Facilitate testing and user documentation 883:Unified Software Development Process (UP) 807:, use cases belong to the scenario-based 4188:Software development process/methodology 4004: 3347:Alexander, Ian, and Beus-Dukic, Ljerka. 3198: 3165: 3156:Alexander and Beus-Dukic, 2009. Page 39. 3095:Alexander and Beus-Dukic, 2009. Page 121 2962:. Microsoft Press. pp. Chapter 11. 2777:Use cases : patterns and blueprints 2593:The unified software development process 2455: 2424: 1403: 1074: 20: 3959:List of Unified Modeling Language tools 3152: 3150: 2449: 4537: 3438:Schneider, Geri and Winters, Jason P. 3318: 3285:Armour and Miller, 2000. (page needed) 3044: 2779:. Indianapolis, Ind.: Addison-Wesley. 2627:Constantine, Larry L. (1 April 1995). 650:(SysML) or as contractual statements. 526:Electrical and electronics engineering 3978: 3501: 3435:. (2nd edition). Prentice Hall, 2000. 3433:Object-Oriented Software Construction 3410:Jacobson Ivar, Spence I., Bittner K. 3361:Armour, Frank, and Granville Miller. 3199:Cockburn, Alistair (9 January 2008). 2924: 2922: 2806: 2804: 2704: 2702: 2700: 1960:Some use case relationships, such as 1259:Technology & Data Variations List 763:developed in 1995, in the context of 4509: 4203:Software verification and validation 4106:Component-based software engineering 3147: 3109:"User Story And Use Case Comparison" 2664: 2662: 2622: 2620: 2586: 2584: 2582: 2580: 2521: 2519: 2485: 2483: 2420: 2418: 2390: 2388: 2386: 2384: 2217:adding citations to reliable sources 2184: 2017: 1855:The list of goal names provides the 1395: 787: 3614:Object-oriented analysis and design 3426:Use cases: requirements in context. 3220:"Listening to the Customer's Voice" 3030:Scenarios in Requirements Discovery 2464:. Alistair Cockburn. Archived from 1800:which submits the modified content. 1785:which submits the modified content. 897:software requirements specification 730:object-oriented analysis and design 697:, which laid the foundation of the 13: 3382:Larry Constantine, Lucy Lockwood, 3354:Alexander, Ian, and Maiden, Neil. 3341: 2919: 2801: 2697: 2425:Jacobson, Ivar (1 December 1987). 1982:Use cases can be over-emphasized. 1946:Limitations of use cases include: 1627: 1428: 1191: 1171: 1151: 1131: 1111: 1054: 1036: 1018: 1000: 14: 4591: 4183:Software configuration management 4050:Search-based software engineering 4035:Experimental software engineering 3918:Systems Modeling Language (SysML) 3453: 3424:Kulak, Daryl, and Eamonn Guiney. 3323:. Prentice Hall. pp. 63–64. 2818:; Bittner, Kurt (December 2011). 2659: 2617: 2577: 2516: 2480: 2456:Cockburn, Alistair (March 2002). 2415: 2381: 2013: 941: 642:, often representing missions or 452:Standards and bodies of knowledge 4519: 4518: 4508: 3585: 2189: 2021: 1356:use a more lightweight approach. 1214: 985: 957: 742:Unified Modelling Language (UML) 693:In 1992 he co-authored the book 3312: 3297: 3288: 3279: 3270: 3245: 3230: 3211: 3192: 3159: 3089: 3080: 3035: 3022: 3013: 2984: 2951: 2886: 2860: 2834: 2768: 2735: 2713:. Spence, Ian. Addison Wesley. 1303: 738:Object Modeling Technique (OMT) 544:Outline of software development 4030:Empirical software engineering 3928:XML Metadata Interchange (XMI) 3417:Dean Leffingwell, Don Widrig, 3237:Peter Zielczynski (May 2006). 2552: 2162: 2080:Use cases are mainly diagrams. 1941: 1915: 1070: 890:Rational Unified Process (RUP) 715:business process reengineering 1: 4565:1986 establishments in Sweden 3398:UML Distilled (Third Edition) 3356:Scenarios, Stories, Use Cases 2958:Wiegers, Karl Eugene (2010). 2844:. Irmuk.co.uk. Archived from 2822:. Ivar Jacobson International 2374: 2163:those popular template styles 1830: 818: 746:Object Management Group (OMG) 4055:Site reliability engineering 3377:Writing Effective Use Cases. 3166:Eriksson, Hans-Erik (2000). 2669:Cockburn, Alistair. (2001). 2458:"Use cases, ten years later" 1507:Interaction overview diagram 917: 7: 4545:Software project management 4060:Social software engineering 3609:Object-oriented programming 3294:Denney, 2005. (page needed) 3218:Karl Wiegers (March 1997). 2872:Ivar Jacobson International 2868:"Use-Case 2.0 Presentation" 2742:Leffingwell, Dean. (2003). 2672:Writing effective use cases 2401:Ivar Jacobson International 2302: 1952:non-functional requirements 1619: 1461:Composite structure diagram 1412:depicts a model of several 952:Writing Effective Use Cases 811:techniques, as well as the 10: 4596: 4580:Agile software development 4198:Software quality assurance 3368:Kurt Bittner, Ian Spence, 3276:Meyer, 2000. (page needed) 3170:Business Modeling with UML 1895:User-Centered Design (UCD) 1364: 1342:Alistair Cockburn stated: 1238:Stakeholders and Interests 1005:Scope-icons-unfilled-house 895:up-front documentation of 653: 307:Software quality assurance 4560:Systems Modeling Language 4555:Unified Modeling Language 4504: 4463: 4428: 4367: 4281: 4274: 4233: 4093: 4012: 3941: 3923:UML eXchange Format (UXF) 3910: 3875: 3849: 3808: 3801: 3781: 3760: 3724: 3683: 3627: 3601: 3594: 3583: 3535: 3529:Unified Modeling Language 3321:Applying UML and patterns 3077:Cockburn, 2001. Page 120. 1973:requirements traceability 1567:Unified Modeling Language 1372:both." Actors are always 1360: 1278: 885:and its fore-runner, the 877:Unified Modeling Language 728:worked at unifying their 648:Systems Modeling Language 630:Unified Modeling Language 4354:Model-driven engineering 4153:Functional specification 4136:Software incompatibility 4045:Requirements engineering 3964:Object Modeling in Color 3954:Rational Unified Process 3619:Object-oriented modeling 3449:. Morgan Kaufmann, 2014. 3144:Cockburn, 2001. Page 55. 3135:Cockburn, 2001. Page 53. 2349:Requirements elicitation 2180: 1752:out in the edit summary. 1665:(User goal or sea level) 1079:Hierarchy of goal levels 1041:Scope-icons-unfilled-box 994:Organization (white-box) 979:Organization (black-box) 946:The template defined by 861: 844: 292:Configuration management 18:Polyseme with two senses 4148:Enterprise architecture 3548:Object Management Group 3464:Basic Use Case Template 3442:. Addison-Wesley, 2001. 3407:, Addison-Wesley, 1992. 3400:. Addison-Wesley, 2004. 3393:. Addison-Wesley, 2005. 3386:, Addison-Wesley, 1999. 3365:. Addison-Wesley, 2000. 3226:. Software Development. 3201:"Why I still use cases" 2930:Object Management Group 2319:Entity-control-boundary 1606:System Sequence Diagram 1489:Behavioral UML diagrams 1443:Structural UML diagrams 904:entity-control-boundary 809:requirement elicitation 703:functional requirements 516:Artificial intelligence 4359:Round-trip engineering 4116:Backward compatibility 4111:Software compatibility 3319:Larman, Craig (2005). 2709:Bittner, Kurt (2003). 2284:Software Ideas Modeler 2141: 2103: 2074: 1632: 1602:state machine diagrams 1598:communication diagrams 1573:originally based upon 1425: 1358: 1351:Martin Fowler stated: 1349: 1196: 1176: 1156: 1136: 1116: 1080: 1060: 1059:Scope-icons-screw-bolt 1042: 1024: 1023:Scope-icons-filled-box 1006: 440:Infrastructure as code 286:Supporting disciplines 34: 4550:Software requirements 4178:Software architecture 4131:Forward compatibility 3949:Glossary of UML terms 3933:Executable UML (xUML) 3492:Search for "use case" 3428:Addison-Wesley, 2012. 3379:Addison-Wesley, 2001. 3241:. IBM developerWorks. 2645:10.1145/205350.205356 2134: 2097: 2067: 1975:, for example with a 1631: 1502:Communication diagram 1407: 1353: 1344: 1253:Main Success Scenario 1195: 1175: 1155: 1135: 1115: 1078: 1058: 1040: 1022: 1004: 873:, as driving element; 765:usage-centered design 297:Deployment management 24: 4476:Computer engineering 4173:Software archaeology 4163:Programming paradigm 4075:Software maintenance 4020:Computer programming 4006:Software engineering 3893:Interaction overview 3445:Wazlawick, Raul S. 3375:Cockburn, Alistair. 3257:alistair.cockburn.us 3205:alistair.cockburn.us 2468:on 15 September 2008 2462:Alistair.cockburn.us 2397:"Use-Case 2.0 ebook" 2268:Enterprise Architect 2251:Text editors and/or 2213:improve this section 1901:Better communication 1808:c. Cancel the edit: 813:model-based analysis 798:requirement analysis 707:software development 640:software engineering 117:Paradigms and models 46:Software development 4496:Systems engineering 4481:Information science 4261:Service orientation 4213:Structured analysis 4121:Compatibility layer 4065:Software deployment 3826:Composite structure 3028:Suzanne Robertson. 2874:. 27 September 2011 2443:10.1145/38807.38824 2431:ACM SIGPLAN Notices 2158:development model. 1977:traceability matrix 1841:Extreme Programming 1811:The member selects 1796:The member selects 1781:The member selects 590:systems engineering 40:Part of a series on 4575:Swedish inventions 4486:Project management 4251:Object orientation 4218:Essential analysis 4126:Compatibility mode 2675:. Addison-Wesley. 2530:. Addison-Wesley. 2324:Event partitioning 2033:. You can help by 1923:interaction design 1708:Success Guarantees 1702:Minimal Guarantees 1638:: Edit an article 1633: 1466:Deployment diagram 1426: 1414:business use cases 1247:Success Guarantees 1244:Minimal Guarantees 1197: 1177: 1157: 1137: 1117: 1081: 1061: 1043: 1030:System (white-box) 1025: 1012:System (black-box) 1007: 720:At the same time, 435:Release automation 312:Project management 35: 4570:1986 in computing 4532: 4531: 4459: 4458: 4400:Information model 4304:Incremental model 4158:Modeling language 3972: 3971: 3911:Derived languages 3906: 3905: 3797: 3796: 3468:Alistair Cockburn 3431:Meyer, Bertrand. 3389:Denney, Richard. 3370:Use Case Modeling 3000:agilemodeling.com 2969:978-0-7356-2267-8 2904:978-0-7695-5166-1 2711:Use case modeling 2334:List of UML tools 2278:Rational Software 2249: 2248: 2241: 2118:use case diagrams 2051: 2050: 1849:agile development 1845:Alistair Cockburn 1793:b. Show changes: 1778:a. Show preview: 1674:(equivalent to a 1646:(Registered User) 1594:sequence diagrams 1590:activity diagrams 1571:use case diagrams 1563: 1562: 1456:Component diagram 1437:UML diagram types 1396:Business use case 1201: 1200: 1185:Seabed Clam-Shell 1102:Very High Summary 1065: 1064: 948:Alistair Cockburn 911:agile development 803:According to the 788:General principle 769:Alistair Cockburn 761:Larry Constantine 582: 581: 473:ISO/IEC standards 4587: 4522: 4521: 4512: 4511: 4471:Computer science 4279: 4278: 4193:Software quality 4085:Systems analysis 4080:Software testing 3999: 3992: 3985: 3976: 3975: 3806: 3805: 3599: 3598: 3589: 3522: 3515: 3508: 3499: 3498: 3494:at IBM Developer 3479:'s Usability.gov 3396:Fowler, Martin. 3335: 3334: 3316: 3310: 3309: 3301: 3295: 3292: 3286: 3283: 3277: 3274: 3268: 3267: 3265: 3263: 3249: 3243: 3242: 3234: 3228: 3227: 3215: 3209: 3208: 3196: 3190: 3189: 3173: 3163: 3157: 3154: 3145: 3142: 3136: 3133: 3120: 3119: 3117: 3115: 3105: 3096: 3093: 3087: 3084: 3078: 3075: 3066: 3063: 3042: 3039: 3033: 3026: 3020: 3017: 3011: 3010: 3008: 3006: 2988: 2982: 2981: 2955: 2949: 2948: 2946: 2944: 2926: 2917: 2916: 2890: 2884: 2883: 2881: 2879: 2864: 2858: 2857: 2855: 2853: 2838: 2832: 2831: 2829: 2827: 2808: 2799: 2798: 2772: 2766: 2765: 2739: 2733: 2732: 2706: 2695: 2694: 2666: 2657: 2656: 2624: 2615: 2614: 2588: 2575: 2574: 2572: 2570: 2556: 2550: 2549: 2523: 2514: 2513: 2487: 2478: 2477: 2475: 2473: 2453: 2447: 2446: 2422: 2413: 2412: 2410: 2408: 2392: 2244: 2237: 2233: 2230: 2224: 2193: 2185: 2132:As some put it, 2095:As some put it, 2046: 2043: 2025: 2018: 1555: 1548: 1541: 1527:Use case diagram 1512:Sequence diagram 1497:Activity diagram 1433: 1432: 1422:business workers 1410:Use case diagram 1086: 1085: 989: 966: 965: 705:, especially in 574: 567: 560: 521:Computer science 430:Build automation 37: 36: 27:use case diagram 4595: 4594: 4590: 4589: 4588: 4586: 4585: 4584: 4535: 4534: 4533: 4528: 4500: 4491:Risk management 4455: 4424: 4363: 4344:Waterfall model 4314:Prototype model 4309:Iterative model 4270: 4246:Aspect-oriented 4229: 4208:Software system 4089: 4070:Software design 4008: 4003: 3973: 3968: 3937: 3902: 3871: 3845: 3793: 3777: 3756: 3720: 3679: 3675:Profile diagram 3623: 3602:Object oriented 3590: 3581: 3531: 3526: 3460:Use case column 3456: 3414:, IJI SA, 2011. 3344: 3342:Further reading 3339: 3338: 3331: 3317: 3313: 3302: 3298: 3293: 3289: 3284: 3280: 3275: 3271: 3261: 3259: 3251: 3250: 3246: 3235: 3231: 3216: 3212: 3197: 3193: 3186: 3164: 3160: 3155: 3148: 3143: 3139: 3134: 3123: 3113: 3111: 3107: 3106: 3099: 3094: 3090: 3085: 3081: 3076: 3069: 3064: 3045: 3040: 3036: 3027: 3023: 3018: 3014: 3004: 3002: 2989: 2985: 2970: 2956: 2952: 2942: 2940: 2927: 2920: 2905: 2891: 2887: 2877: 2875: 2866: 2865: 2861: 2851: 2849: 2848:on 17 June 2013 2840: 2839: 2835: 2825: 2823: 2809: 2802: 2787: 2773: 2769: 2754: 2740: 2736: 2721: 2707: 2698: 2683: 2667: 2660: 2625: 2618: 2603: 2589: 2578: 2568: 2566: 2558: 2557: 2553: 2538: 2524: 2517: 2502: 2488: 2481: 2471: 2469: 2454: 2450: 2437:(12): 183–191. 2423: 2416: 2406: 2404: 2393: 2382: 2377: 2369:Use case points 2305: 2253:word processors 2245: 2234: 2228: 2225: 2210: 2194: 2183: 2122:use case briefs 2047: 2041: 2038: 2031:needs expansion 2016: 1944: 1929:of the system. 1927:user experience 1839:technique from 1833: 1622: 1613:use case briefs 1559: 1481:Profile diagram 1476:Package diagram 1431: 1429:Visual modeling 1418:business actors 1398: 1369: 1363: 1306: 1281: 1229:Goal in Context 1217: 1205:place an order! 1073: 960: 944: 920: 864: 847: 840:implementation. 821: 790: 754:Unified Process 711:business models 684:användningsfall 676:usage scenarios 672:visual modeling 656: 578: 549: 548: 539: 531: 530: 511: 503: 502: 453: 445: 444: 395: 385: 384: 330: 322: 321: 317:User experience 287: 279: 278: 169: 158: 157: 118: 110: 109: 55: 54:Core activities 19: 12: 11: 5: 4593: 4583: 4582: 4577: 4572: 4567: 4562: 4557: 4552: 4547: 4530: 4529: 4527: 4526: 4516: 4505: 4502: 4501: 4499: 4498: 4493: 4488: 4483: 4478: 4473: 4467: 4465: 4464:Related fields 4461: 4460: 4457: 4456: 4454: 4453: 4448: 4443: 4438: 4432: 4430: 4426: 4425: 4423: 4422: 4417: 4412: 4407: 4402: 4397: 4395:Function model 4392: 4387: 4382: 4377: 4371: 4369: 4365: 4364: 4362: 4361: 4356: 4351: 4346: 4341: 4336: 4331: 4326: 4321: 4316: 4311: 4306: 4301: 4299:Executable UML 4296: 4291: 4285: 4283: 4276: 4272: 4271: 4269: 4268: 4263: 4258: 4253: 4248: 4243: 4237: 4235: 4231: 4230: 4228: 4227: 4222: 4221: 4220: 4210: 4205: 4200: 4195: 4190: 4185: 4180: 4175: 4170: 4165: 4160: 4155: 4150: 4145: 4140: 4139: 4138: 4133: 4128: 4123: 4118: 4108: 4103: 4097: 4095: 4091: 4090: 4088: 4087: 4082: 4077: 4072: 4067: 4062: 4057: 4052: 4047: 4042: 4040:Formal methods 4037: 4032: 4027: 4022: 4016: 4014: 4010: 4009: 4002: 4001: 3994: 3987: 3979: 3970: 3969: 3967: 3966: 3961: 3956: 3951: 3945: 3943: 3939: 3938: 3936: 3935: 3930: 3925: 3920: 3914: 3912: 3908: 3907: 3904: 3903: 3901: 3900: 3895: 3890: 3885: 3883:Communications 3879: 3877: 3873: 3872: 3870: 3869: 3864: 3859: 3853: 3851: 3847: 3846: 3844: 3843: 3838: 3833: 3828: 3823: 3818: 3812: 3810: 3803: 3799: 3798: 3795: 3794: 3792: 3791: 3785: 3783: 3779: 3778: 3776: 3775: 3770: 3764: 3762: 3758: 3757: 3755: 3754: 3747:Generalization 3744: 3739: 3734: 3728: 3726: 3722: 3721: 3719: 3718: 3713: 3708: 3703: 3698: 3693: 3687: 3685: 3681: 3680: 3678: 3677: 3672: 3667: 3662: 3657: 3652: 3647: 3642: 3637: 3631: 3629: 3625: 3624: 3622: 3621: 3616: 3611: 3605: 3603: 3596: 3592: 3591: 3584: 3582: 3580: 3579: 3578: 3577: 3575:James Rumbaugh 3572: 3567: 3557: 3556: 3555: 3550: 3539: 3537: 3533: 3532: 3525: 3524: 3517: 3510: 3502: 3496: 3495: 3489: 3480: 3470: 3455: 3454:External links 3452: 3451: 3450: 3443: 3436: 3429: 3422: 3415: 3408: 3401: 3394: 3387: 3380: 3373: 3366: 3359: 3352: 3351:. Wiley, 2009. 3343: 3340: 3337: 3336: 3329: 3311: 3296: 3287: 3278: 3269: 3244: 3229: 3224:Process Impact 3210: 3191: 3184: 3158: 3146: 3137: 3121: 3097: 3088: 3079: 3067: 3043: 3034: 3021: 3012: 2983: 2968: 2950: 2918: 2903: 2885: 2859: 2833: 2812:Jacobson, Ivar 2800: 2785: 2767: 2752: 2734: 2719: 2696: 2681: 2658: 2616: 2601: 2576: 2551: 2536: 2515: 2500: 2479: 2448: 2414: 2379: 2378: 2376: 2373: 2372: 2371: 2366: 2361: 2356: 2351: 2346: 2341: 2336: 2331: 2326: 2321: 2316: 2311: 2304: 2301: 2293: 2292: 2286: 2281: 2275: 2270: 2265: 2247: 2246: 2197: 2195: 2188: 2182: 2179: 2167:the OUM method 2049: 2048: 2028: 2026: 2015: 2014:Misconceptions 2012: 2011: 2010: 1990: 1987: 1984:Bertrand Meyer 1980: 1969:user interface 1965: 1958: 1955: 1943: 1940: 1876: 1875: 1872: 1868: 1864: 1860: 1832: 1829: 1822: 1821: 1820: 1819: 1816: 1806: 1805: 1804: 1801: 1791: 1790: 1789: 1786: 1766: 1765: 1762: 1759: 1756: 1753: 1742: 1741: 1731: 1730: 1720: 1719: 1718: 1717: 1714: 1705: 1696:Postconditions 1685: 1684: 1621: 1618: 1561: 1560: 1558: 1557: 1550: 1543: 1535: 1532: 1531: 1530: 1529: 1524: 1522:Timing diagram 1519: 1514: 1509: 1504: 1499: 1491: 1490: 1486: 1485: 1484: 1483: 1478: 1473: 1471:Object diagram 1468: 1463: 1458: 1453: 1445: 1444: 1440: 1439: 1430: 1427: 1397: 1394: 1365:Main article: 1362: 1359: 1333: 1332: 1331: 1330: 1324: 1323: 1322: 1316: 1305: 1302: 1301: 1300: 1297: 1294: 1291: 1288: 1280: 1277: 1276: 1275: 1272: 1261: 1260: 1257: 1254: 1251: 1248: 1245: 1242: 1239: 1236: 1233: 1230: 1227: 1224: 1216: 1213: 1199: 1198: 1189: 1186: 1183: 1179: 1178: 1169: 1166: 1163: 1159: 1158: 1149: 1146: 1143: 1139: 1138: 1129: 1126: 1123: 1119: 1118: 1109: 1106: 1103: 1099: 1098: 1096: 1093: 1090: 1072: 1069: 1063: 1062: 1052: 1049: 1045: 1044: 1034: 1031: 1027: 1026: 1016: 1013: 1009: 1008: 998: 997:Unfilled House 995: 991: 990: 983: 980: 976: 975: 973: 970: 959: 956: 943: 942:Cockburn style 940: 924:use case brief 919: 916: 915: 914: 907: 900: 893: 880: 874: 863: 860: 859: 858: 854: 846: 843: 842: 841: 837: 833: 829: 820: 817: 789: 786: 726:James Rumbaugh 655: 652: 613: 612: 609: 580: 579: 577: 576: 569: 562: 554: 551: 550: 547: 546: 540: 537: 536: 533: 532: 529: 528: 523: 518: 512: 509: 508: 505: 504: 501: 500: 495: 490: 485: 480: 475: 470: 465: 463:IEEE standards 460: 454: 451: 450: 447: 446: 443: 442: 437: 432: 427: 422: 417: 412: 407: 402: 396: 391: 390: 387: 386: 383: 382: 377: 372: 367: 362: 357: 352: 347: 342: 337: 331: 328: 327: 324: 323: 320: 319: 314: 309: 304: 299: 294: 288: 285: 284: 281: 280: 277: 276: 271: 266: 261: 256: 251: 246: 241: 236: 231: 226: 221: 216: 211: 206: 201: 196: 191: 186: 181: 176: 170: 168:and frameworks 164: 163: 160: 159: 156: 155: 150: 145: 140: 135: 130: 125: 119: 116: 115: 112: 111: 108: 107: 102: 97: 92: 87: 82: 77: 72: 67: 62: 56: 53: 52: 49: 48: 42: 41: 25:A very simple 17: 9: 6: 4: 3: 2: 4592: 4581: 4578: 4576: 4573: 4571: 4568: 4566: 4563: 4561: 4558: 4556: 4553: 4551: 4548: 4546: 4543: 4542: 4540: 4525: 4517: 4515: 4507: 4506: 4503: 4497: 4494: 4492: 4489: 4487: 4484: 4482: 4479: 4477: 4474: 4472: 4469: 4468: 4466: 4462: 4452: 4449: 4447: 4444: 4442: 4439: 4437: 4434: 4433: 4431: 4427: 4421: 4418: 4416: 4415:Systems model 4413: 4411: 4408: 4406: 4403: 4401: 4398: 4396: 4393: 4391: 4388: 4386: 4383: 4381: 4378: 4376: 4373: 4372: 4370: 4366: 4360: 4357: 4355: 4352: 4350: 4347: 4345: 4342: 4340: 4337: 4335: 4332: 4330: 4327: 4325: 4322: 4320: 4317: 4315: 4312: 4310: 4307: 4305: 4302: 4300: 4297: 4295: 4292: 4290: 4287: 4286: 4284: 4282:Developmental 4280: 4277: 4273: 4267: 4264: 4262: 4259: 4257: 4254: 4252: 4249: 4247: 4244: 4242: 4239: 4238: 4236: 4232: 4226: 4223: 4219: 4216: 4215: 4214: 4211: 4209: 4206: 4204: 4201: 4199: 4196: 4194: 4191: 4189: 4186: 4184: 4181: 4179: 4176: 4174: 4171: 4169: 4166: 4164: 4161: 4159: 4156: 4154: 4151: 4149: 4146: 4144: 4143:Data modeling 4141: 4137: 4134: 4132: 4129: 4127: 4124: 4122: 4119: 4117: 4114: 4113: 4112: 4109: 4107: 4104: 4102: 4099: 4098: 4096: 4092: 4086: 4083: 4081: 4078: 4076: 4073: 4071: 4068: 4066: 4063: 4061: 4058: 4056: 4053: 4051: 4048: 4046: 4043: 4041: 4038: 4036: 4033: 4031: 4028: 4026: 4023: 4021: 4018: 4017: 4015: 4011: 4007: 4000: 3995: 3993: 3988: 3986: 3981: 3980: 3977: 3965: 3962: 3960: 3957: 3955: 3952: 3950: 3947: 3946: 3944: 3940: 3934: 3931: 3929: 3926: 3924: 3921: 3919: 3916: 3915: 3913: 3909: 3899: 3896: 3894: 3891: 3889: 3886: 3884: 3881: 3880: 3878: 3874: 3868: 3865: 3863: 3862:State Machine 3860: 3858: 3855: 3854: 3852: 3848: 3842: 3839: 3837: 3834: 3832: 3829: 3827: 3824: 3822: 3819: 3817: 3814: 3813: 3811: 3807: 3804: 3800: 3790: 3787: 3786: 3784: 3780: 3774: 3771: 3769: 3766: 3765: 3763: 3761:Extensibility 3759: 3752: 3748: 3745: 3743: 3740: 3738: 3735: 3733: 3730: 3729: 3727: 3725:Relationships 3723: 3717: 3714: 3712: 3709: 3707: 3704: 3702: 3699: 3697: 3694: 3692: 3689: 3688: 3686: 3682: 3676: 3673: 3671: 3668: 3666: 3663: 3661: 3658: 3656: 3653: 3651: 3648: 3646: 3643: 3641: 3638: 3636: 3633: 3632: 3630: 3626: 3620: 3617: 3615: 3612: 3610: 3607: 3606: 3604: 3600: 3597: 3593: 3588: 3576: 3573: 3571: 3570:Ivar Jacobson 3568: 3566: 3563: 3562: 3561: 3558: 3554: 3551: 3549: 3546: 3545: 3544: 3543:Organizations 3541: 3540: 3538: 3534: 3530: 3523: 3518: 3516: 3511: 3509: 3504: 3503: 3500: 3493: 3490: 3488: 3484: 3481: 3478: 3474: 3471: 3469: 3465: 3461: 3458: 3457: 3448: 3444: 3441: 3437: 3434: 3430: 3427: 3423: 3420: 3416: 3413: 3409: 3406: 3402: 3399: 3395: 3392: 3388: 3385: 3381: 3378: 3374: 3371: 3367: 3364: 3360: 3358:. Wiley 2004. 3357: 3353: 3350: 3346: 3345: 3332: 3330:0-13-148906-2 3326: 3322: 3315: 3307: 3300: 3291: 3282: 3273: 3258: 3254: 3248: 3240: 3233: 3225: 3221: 3214: 3206: 3202: 3195: 3187: 3185:0-471-29551-5 3181: 3177: 3172: 3171: 3162: 3153: 3151: 3141: 3132: 3130: 3128: 3126: 3110: 3104: 3102: 3092: 3083: 3074: 3072: 3065:Fowler, 2004. 3062: 3060: 3058: 3056: 3054: 3052: 3050: 3048: 3038: 3031: 3025: 3016: 3001: 2997: 2993: 2992:Ambler, Scott 2987: 2979: 2975: 2971: 2965: 2961: 2954: 2939: 2935: 2931: 2925: 2923: 2914: 2910: 2906: 2900: 2896: 2889: 2873: 2869: 2863: 2847: 2843: 2837: 2821: 2817: 2813: 2807: 2805: 2796: 2792: 2788: 2786:0-13-145134-0 2782: 2778: 2771: 2763: 2759: 2755: 2753:0-321-12247-X 2749: 2745: 2738: 2730: 2726: 2722: 2720:0-201-70913-9 2716: 2712: 2705: 2703: 2701: 2692: 2688: 2684: 2682:0-201-70225-8 2678: 2674: 2673: 2665: 2663: 2654: 2650: 2646: 2642: 2638: 2634: 2630: 2623: 2621: 2612: 2608: 2604: 2602:0-201-57169-2 2598: 2594: 2587: 2585: 2583: 2581: 2565: 2561: 2555: 2547: 2543: 2539: 2537:0-201-42289-1 2533: 2529: 2522: 2520: 2511: 2507: 2503: 2501:0-201-54435-0 2497: 2494:. ACM Press. 2493: 2486: 2484: 2467: 2463: 2459: 2452: 2444: 2440: 2436: 2432: 2428: 2421: 2419: 2402: 2398: 2391: 2389: 2387: 2385: 2380: 2370: 2367: 2365: 2362: 2360: 2357: 2355: 2352: 2350: 2347: 2345: 2342: 2340: 2337: 2335: 2332: 2330: 2327: 2325: 2322: 2320: 2317: 2315: 2314:Business case 2312: 2310: 2307: 2306: 2300: 2298: 2290: 2289:Wiki software 2287: 2285: 2282: 2279: 2276: 2274: 2271: 2269: 2266: 2264: 2261: 2260: 2259: 2256: 2254: 2243: 2240: 2232: 2222: 2218: 2214: 2208: 2207: 2203: 2198:This section 2196: 2192: 2187: 2186: 2178: 2176: 2172: 2168: 2164: 2159: 2157: 2153: 2148: 2143: 2140: 2139: 2133: 2130: 2129: 2125: 2123: 2119: 2114: 2112: 2108: 2102: 2101: 2096: 2093: 2092: 2088: 2086: 2082: 2081: 2077: 2073: 2072: 2066: 2064: 2059: 2058: 2054: 2045: 2036: 2032: 2029:This section 2027: 2024: 2020: 2019: 2008: 2004: 2000: 1996: 1991: 1988: 1985: 1981: 1978: 1974: 1970: 1966: 1963: 1959: 1956: 1953: 1949: 1948: 1947: 1939: 1935: 1934: 1930: 1928: 1924: 1919: 1917: 1912: 1911: 1907: 1903: 1902: 1898: 1896: 1891: 1889: 1884: 1883: 1879: 1873: 1869: 1865: 1861: 1858: 1854: 1853: 1852: 1850: 1846: 1842: 1838: 1828: 1825: 1824:4a. Timeout: 1817: 1814: 1810: 1809: 1807: 1802: 1799: 1795: 1794: 1792: 1787: 1784: 1780: 1779: 1777: 1776: 1775: 1772: 1770: 1763: 1760: 1757: 1754: 1750: 1749: 1748: 1746: 1739: 1738: 1737: 1735: 1728: 1727: 1726: 1724: 1723:Preconditions 1715: 1712: 1711: 1709: 1706: 1703: 1700: 1699: 1698: 1697: 1693: 1690: 1689: 1682: 1681: 1680: 1679: 1677: 1671: 1667: 1666: 1662: 1658: 1656: 1652: 1648: 1647: 1643: 1642:Primary Actor 1639: 1637: 1630: 1626: 1617: 1614: 1609: 1607: 1603: 1599: 1595: 1591: 1586: 1584: 1580: 1576: 1575:Ivar Jacobson 1572: 1568: 1556: 1551: 1549: 1544: 1542: 1537: 1536: 1534: 1533: 1528: 1525: 1523: 1520: 1518: 1517:State diagram 1515: 1513: 1510: 1508: 1505: 1503: 1500: 1498: 1495: 1494: 1493: 1492: 1488: 1487: 1482: 1479: 1477: 1474: 1472: 1469: 1467: 1464: 1462: 1459: 1457: 1454: 1452: 1451:Class diagram 1449: 1448: 1447: 1446: 1442: 1441: 1438: 1435: 1434: 1423: 1419: 1415: 1411: 1406: 1402: 1393: 1389: 1385: 1381: 1377: 1375: 1368: 1357: 1352: 1348: 1343: 1340: 1338: 1328: 1327: 1325: 1320: 1319: 1317: 1314: 1313: 1312: 1310: 1309:Martin Fowler 1298: 1295: 1292: 1290:Primary Actor 1289: 1286: 1285: 1284: 1273: 1270: 1269: 1268: 1264: 1258: 1255: 1252: 1249: 1246: 1243: 1240: 1237: 1234: 1231: 1228: 1226:Primary Actor 1225: 1222: 1221: 1220: 1215:Fully dressed 1212: 1210: 1206: 1194: 1190: 1187: 1184: 1181: 1180: 1174: 1170: 1167: 1164: 1161: 1160: 1154: 1150: 1147: 1144: 1141: 1140: 1134: 1130: 1127: 1124: 1121: 1120: 1114: 1110: 1107: 1104: 1101: 1100: 1097: 1094: 1091: 1088: 1087: 1084: 1077: 1068: 1057: 1053: 1051:Screw or Bolt 1050: 1047: 1046: 1039: 1035: 1032: 1029: 1028: 1021: 1017: 1014: 1011: 1010: 1003: 999: 996: 993: 992: 988: 984: 981: 978: 977: 974: 971: 968: 967: 964: 958:Design scopes 955: 953: 949: 939: 937: 936:fully dressed 933: 929: 925: 912: 908: 905: 901: 898: 894: 891: 888: 884: 881: 878: 875: 872: 869: 868: 867: 855: 852: 851: 850: 838: 834: 830: 826: 825: 824: 816: 814: 810: 806: 801: 799: 794: 785: 783: 778: 773: 770: 766: 762: 757: 755: 751: 747: 743: 739: 735: 732:methods, the 731: 727: 723: 718: 716: 712: 708: 704: 700: 696: 691: 689: 685: 681: 677: 673: 669: 665: 661: 660:Ivar Jacobson 651: 649: 645: 641: 637: 636: 631: 627: 622: 620: 619: 610: 607: 606: 605: 603: 599: 595: 592:, the phrase 591: 587: 575: 570: 568: 563: 561: 556: 555: 553: 552: 545: 542: 541: 535: 534: 527: 524: 522: 519: 517: 514: 513: 507: 506: 499: 496: 494: 491: 489: 486: 484: 481: 479: 476: 474: 471: 469: 466: 464: 461: 459: 456: 455: 449: 448: 441: 438: 436: 433: 431: 428: 426: 423: 421: 418: 416: 413: 411: 408: 406: 403: 401: 398: 397: 394: 389: 388: 381: 378: 376: 373: 371: 368: 366: 363: 361: 358: 356: 353: 351: 348: 346: 343: 341: 338: 336: 333: 332: 326: 325: 318: 315: 313: 310: 308: 305: 303: 302:Documentation 300: 298: 295: 293: 290: 289: 283: 282: 275: 272: 270: 267: 265: 262: 260: 257: 255: 252: 250: 247: 245: 242: 240: 237: 235: 232: 230: 227: 225: 222: 220: 217: 215: 212: 210: 207: 205: 202: 200: 197: 195: 192: 190: 187: 185: 182: 180: 177: 175: 172: 171: 167: 166:Methodologies 162: 161: 154: 151: 149: 146: 144: 141: 139: 136: 134: 131: 129: 126: 124: 121: 120: 114: 113: 106: 103: 101: 98: 96: 93: 91: 88: 86: 83: 81: 78: 76: 73: 71: 68: 66: 63: 61: 60:Data modeling 58: 57: 51: 50: 47: 44: 43: 39: 38: 32: 28: 23: 16: 4410:Object model 4405:Metamodeling 4334:Spiral model 4234:Orientations 3942:Other topics 3789:Multiplicity 3715: 3559: 3553:UML Partners 3542: 3487:Academia.edu 3446: 3439: 3432: 3425: 3418: 3411: 3404: 3397: 3390: 3383: 3376: 3369: 3362: 3355: 3348: 3320: 3314: 3299: 3290: 3281: 3272: 3260:. Retrieved 3256: 3247: 3232: 3223: 3213: 3204: 3194: 3169: 3161: 3140: 3112:. Retrieved 3091: 3082: 3037: 3029: 3024: 3015: 3003:. Retrieved 2999: 2986: 2959: 2953: 2941:. Retrieved 2937: 2894: 2888: 2876:. Retrieved 2871: 2862: 2850:. Retrieved 2846:the original 2836: 2824:. Retrieved 2776: 2770: 2743: 2737: 2710: 2671: 2639:(2): 34–46. 2636: 2633:Interactions 2632: 2592: 2567:. Retrieved 2563: 2554: 2527: 2491: 2470:. Retrieved 2466:the original 2461: 2451: 2434: 2430: 2405:. Retrieved 2400: 2294: 2263:CaseComplete 2257: 2250: 2235: 2226: 2211:Please help 2199: 2174: 2170: 2160: 2155: 2151: 2146: 2144: 2142: 2136: 2135: 2131: 2127: 2126: 2121: 2117: 2115: 2110: 2106: 2104: 2099: 2098: 2094: 2090: 2089: 2085:Craig Larman 2083: 2079: 2078: 2075: 2069: 2068: 2060: 2056: 2055: 2052: 2039: 2035:adding to it 2030: 1961: 1945: 1936: 1932: 1931: 1920: 1913: 1909: 1908: 1904: 1900: 1899: 1892: 1887: 1885: 1882:User focused 1881: 1880: 1877: 1856: 1834: 1826: 1823: 1812: 1798:Show changes 1797: 1783:Show preview 1782: 1773: 1768: 1767: 1744: 1743: 1733: 1732: 1722: 1721: 1707: 1701: 1695: 1694: 1691: 1688:Stakeholders 1687: 1686: 1673: 1669: 1668: 1664: 1660: 1659: 1650: 1649: 1645: 1641: 1640: 1635: 1634: 1623: 1612: 1610: 1587: 1564: 1421: 1417: 1413: 1399: 1390: 1386: 1382: 1378: 1374:stakeholders 1370: 1354: 1350: 1345: 1341: 1334: 1307: 1304:Fowler style 1287:Title (goal) 1282: 1265: 1262: 1241:Precondition 1218: 1208: 1204: 1202: 1145:Waves at Sea 1082: 1066: 1033:Unfilled Box 982:Filled House 961: 951: 950:in his book 945: 935: 931: 927: 923: 921: 865: 848: 832:initiatives. 822: 802: 795: 791: 784:conference. 777:Use Case 2.0 776: 774: 758: 734:Booch method 719: 694: 692: 687: 683: 679: 675: 657: 633: 632:(UML) as an 625: 623: 618:user persona 616: 614: 593: 583: 420:UML Modeling 415:GUI designer 80:Construction 70:Requirements 15: 4101:Abstraction 3876:Interaction 3751:Inheritance 3737:Composition 3732:Association 3565:Grady Booch 2938:www.omg.org 2816:Spence, Ian 2564:www.omg.org 2403:. p. 4 2344:Requirement 2339:Misuse case 2229:August 2013 1942:Limitations 1897:for years. 1678:or an epic) 1408:A business 1367:Actor (UML) 1162:Subfunction 1125:Flying Kite 1071:Goal levels 828:activities. 722:Grady Booch 644:stakeholder 138:Prototyping 133:Incremental 105:Maintenance 85:Engineering 4539:Categories 4420:View model 4385:Data model 3831:Deployment 3773:Stereotype 3742:Dependency 3114:19 January 2375:References 2359:Storyboard 2309:Abuse case 2061:Agile and 1837:user story 1831:Advantages 1769:Extensions 1745:Basic flow 1676:user story 1581:notation. 1337:user story 1256:Extensions 1089:Goal Level 1015:Filled Box 819:Variations 680:usage case 510:Glossaries 100:Deployment 4429:Languages 3850:Behaviour 3821:Component 3809:Structure 3660:Interface 3655:Component 3640:Attribute 3628:Structure 3473:Use Cases 3005:16 August 2943:16 August 2913:880350861 2611:636807532 2364:Test case 2297:UML tools 2273:MagicDraw 2200:does not 2156:waterfall 2147:bad smell 2042:July 2015 2007:ArchiMate 1916:templates 1663:: ! 1644:: Member 1579:Objectory 1142:User Goal 1048:Component 918:Templates 906:approach; 750:Objectory 658:In 1987, 600:with two 329:Practices 153:Waterfall 128:Cleanroom 95:Debugging 65:Processes 4524:Category 4390:ER model 4256:Ontology 4168:Software 4094:Concepts 3888:Sequence 3867:Use case 3857:Activity 3802:Diagrams 3716:Use case 3691:Activity 3684:Behavior 3645:Artifact 3595:Concepts 3308:. InfoQ. 3262:16 March 2994:(2004). 2978:73814167 2932:(2017). 2878:9 August 2852:17 April 2795:59554401 2762:51653240 2729:50041546 2691:44046973 2653:17209049 2569:9 August 2546:32276135 2510:26132801 2472:17 April 2407:9 August 2354:Scenario 2303:See also 1857:shortest 1734:Triggers 1636:Use Case 1620:Examples 688:use case 668:Ericsson 626:use case 598:polyseme 594:use case 586:software 538:Outlines 468:ISO 9001 410:Profiler 405:Debugger 400:Compiler 375:Stand-up 4514:Commons 4339:V-model 3841:Package 3768:Profile 3701:Message 3670:Package 3560:Persons 2329:Feature 2221:removed 2206:sources 2175:problem 2138:rework. 2009:ARMOR). 1962:extends 1657:system 1250:Trigger 1182:Too Low 1122:Summary 932:outline 796:In the 654:History 209:Lean SD 148:V model 90:Testing 4275:Models 4025:DevOps 4013:Fields 3898:Timing 3836:Object 3706:Method 3665:Object 3536:Actors 3327: 3182: 2976: 2966: 2911: 2901: 2793: 2783: 2760: 2750: 2727: 2717: 2689: 2679: 2651: 2609: 2599: 2544: 2534: 2508: 2498: 1888:actors 1813:Cancel 1600:, and 1361:Actors 1279:Casual 1209:login- 1095:Symbol 928:casual 664:OOPSLA 602:senses 483:SWEBOK 204:Kanban 179:DevOps 143:Spiral 75:Design 4451:SysML 4375:SPICE 4368:Other 4329:Scrum 4289:Agile 4241:Agile 4225:CI/CD 3816:Class 3782:Other 3711:State 3696:Event 3650:Class 3635:Actor 2826:5 May 2649:S2CID 2295:Most 2181:Tools 2171:model 2152:agile 2120:plus 2107:actor 2063:Scrum 1863:else. 1774:2–3. 1670:Brief 1661:Level 1651:Scope 1583:SysML 1296:Level 1293:Scope 1235:Level 1232:Scope 1105:Cloud 969:Scope 934:, to 862:Usage 845:Scope 635:actor 596:is a 478:PMBOK 393:Tools 254:SEMAT 249:Scrum 123:Agile 29:of a 4436:IDEF 4380:CMMI 4266:SDLC 3749:(or 3462:and 3325:ISBN 3264:2018 3180:ISBN 3116:2024 3007:2020 2974:OCLC 2964:ISBN 2945:2020 2909:OCLC 2899:ISBN 2880:2020 2854:2013 2828:2014 2791:OCLC 2781:ISBN 2758:OCLC 2748:ISBN 2725:OCLC 2715:ISBN 2687:OCLC 2677:ISBN 2607:OCLC 2597:ISBN 2571:2020 2542:OCLC 2532:ISBN 2506:OCLC 2496:ISBN 2474:2013 2409:2020 2204:any 2202:cite 2005:and 2003:KAOS 1925:and 1827:... 1692:... 1655:Wiki 1653:: a 1420:and 1165:Fish 1092:Icon 972:Icon 909:and 782:IIBA 736:and 724:and 713:and 699:OOSE 678:and 588:and 493:IREB 488:ITIL 458:CMMI 335:ATDD 244:SAFe 214:LeSS 189:DSDM 31:Wiki 4446:USL 4441:UML 4319:RAD 4294:EUP 3485:at 3477:GSA 3475:at 3466:by 2641:doi 2439:doi 2215:by 2111:bad 2037:. 1995:BMM 1577:'s 887:IBM 621:). 584:In 498:OMG 425:IDE 380:TDD 370:SBE 360:DDD 345:CCO 340:BDD 264:TSP 259:TDD 239:RUP 234:RAD 229:PSP 224:MSF 219:MDD 199:IID 194:FDD 184:DAD 174:ASD 4541:: 4349:XP 4324:UP 3255:. 3222:. 3203:. 3178:. 3176:52 3149:^ 3124:^ 3100:^ 3070:^ 3046:^ 2998:. 2972:. 2936:. 2921:^ 2907:. 2870:. 2814:; 2803:^ 2789:. 2756:. 2723:. 2699:^ 2685:. 2661:^ 2647:. 2635:. 2631:. 2619:^ 2605:. 2579:^ 2562:. 2540:. 2518:^ 2504:. 2482:^ 2460:. 2435:22 2433:. 2429:. 2417:^ 2399:. 2383:^ 2001:, 1999:I* 1997:, 1851:. 1771:: 1747:: 1736:: 1725:: 1710:: 1672:: 1596:, 1592:, 1424:). 1339:. 1211:. 1207:, 1188:-- 1108:++ 930:, 926:, 717:. 690:. 624:A 604:: 365:PP 355:CD 350:CI 274:XP 269:UP 3998:e 3991:t 3984:v 3753:) 3521:e 3514:t 3507:v 3333:. 3266:. 3207:. 3188:. 3118:. 3009:. 2980:. 2947:. 2915:. 2882:. 2856:. 2830:. 2797:. 2764:. 2731:. 2693:. 2655:. 2643:: 2637:2 2613:. 2573:. 2548:. 2512:. 2476:. 2445:. 2441:: 2411:. 2242:) 2236:( 2231:) 2227:( 2223:. 2209:. 2150:( 2044:) 2040:( 1815:. 1704:: 1554:e 1547:t 1540:v 1168:- 1148:! 1128:+ 913:. 892:; 573:e 566:t 559:v

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

Index