This link has been bookmarked by 133 people . It was first bookmarked on 26 Jun 2007, by senzafine3.
-
25 Jan 17
-
11 Jan 17
-
10 Apr 16
-
19 Dec 15
-
16 Dec 15
-
21 Aug 15
-
13 Apr 15
-
stating the need
-
User Story is the prelude to the use case
-
-
01 Apr 15
-
31 Jan 15
-
25 Dec 14
-
Your use cases are only as effective as the value someone's deriving from them. What seems obvious to you may not be to your developers or customers. The success measurement for an effective written use case is one that is easily understood, and ultimately the developers can build the right product the first time.
-
When it comes to writing effective use cases, you don't need to be a perfectionist and concern yourself with getting it right the first time. Developing use cases should be looked at as an iterative process where you work and refine
-
ny "object" or person that has behavior associated with it. Generally, the users are actors but often systems can be actors as well.
-
an actor is a Role.
-
You always want to focus on the sunny day scenarios first because you can then pivot off these and figure out your "rainy day" scenarios (or edge cases) late
-
Use the 80/20 rule -- if you write an exhaustive list of all possible use cases, typically 20% of the use cases will account for 80% of the activity. The other 80% of the use cases would support 20% of the activity.
-
fter you have a well-defined list of your primary use cases, you'll want to collect the list of edge cases (rainy-day) and with the help of the product manager or stake-holder, prioritize them in terms of likelyness. It should be a business question as far as how much software development costs do you want to spend on something that is not lik
-
What does the word general mean? Something is broad and not as detailed. Generalization is when you "inherit" from something general and then add more detail.
-
The basic flow of a use case represents the most important course of events or what happens most of the time, sometimes referred to as the 'Happy Day Scenario' because it is what occurs when everything goes well -- no errors or exceptions. Another reason why the basic flow is so critical is because it's much easier to fully comprehend the exceptions once the norm is understood and if the basic flow represents 70% of the system, the development staff is much more prone to implementing the correct code in the first pass.
-
An exception or error flow to any line item in your basic flow
- An additional flow, not necessarily error based, but a flow that COULD happen
The alternate flows providing the following:
-
he purpose of the use cases is for effective knowledge transfer from the domain expert to the software developer -- these use cases will serve as the software requirement specifications
-
hey don't make sense to the person building the software, they are not effectiv
-
-
02 Dec 14
-
13 Oct 14
-
19 Sep 14
-
What is a User Story? Simply put, written from the context of the user as a simple statement about their feature need. They should generally have this format. "As a -role-, I want -goal/desire- so that -benefit-"
-
How is a User Story different than a Use Case? While a use case is highly structured and tells a story, the User Story sets the stage by stating the need. A User Story is the prelude to the use case by stating the need before the use case tells the story.
-
How does the User Story fit into the process? User Stories are great as an activity in collecting and prioritizing the high level features. Getting this initial feedback from the customer is a simple way of trying to get all of their needs identified and prioritized. The User Stories will then morph themselves into the business requirements and use cases.
-
-
15 Jul 14
-
28 Mar 14
-
20 Mar 14
-
01 Oct 13
-
19 Jul 13
-
24 May 13
-
25 Mar 13
-
Use Case
-
13 killer tips to create effective use cases
-
easily understood
-
the developers can build the right product the first time
-
Any "object" or person that has behavior associated with it
-
An actor can be a system
-
-
26 Feb 13
-
14 Nov 12
-
05 Nov 12
-
24 Sep 12
-
03 Jul 12
-
22 Jun 12
-
28 Apr 12
-
11 Apr 12
-
11 Mar 12
-
Developing use cases should be looked at as an iterative process where you work and refine.
-
grass-roots
-
SELLERS
-
who are the basic users of Ebay?
-
UYERS
-
an actor is a Role
-
And a role in this case would be that of a buyer and that of a seller
-
An actor can be a system, because a system plays another role in the context of your new system and has goals and interacts with other actors
-
"Sunny Day" use cases, it is in reference to the use cases that are most likely going to occur when all goes well.
-
eferred to as your primary use cases.
-
"rainy day" scenarios (or edge cases) later
-
Generalization is when you "inherit" from something general and then add more detail.
-
A "person" is very general. A "man" is still general, but not as general as a "person". You can say that a "man" inherits behavior and atributes of a "person".
-
create an initial use case grid
-
After producing your initial visual list of use case actors and goals
-
basis for the use case index.
-
At the project level
-
priority
-
status
-
complexity
-
scope
-
attributes
-
The actual use case is a textual representation illustrating a sequence of events.
-
what is in the use case
-
Use Case Number
-
Application
-
Use Case Name
-
Use Case Description
-
Primary Actor
-
Precondition -
Trigger
-
Basic Flow
-
Alternate Flows
-
Use Case Number: 1 Use Case Name: Buyer Places a Bid Description: An EBAY buyer has identified an item they wish to buy, so they will place a bid for an item with the intent of winning the auction and paying for the item. -
what happens most of the time
-
basic flow of a use case
-
the most important course of events
-
'Happy Day Scenario
-
because it is what occurs when everything goes well -- no errors or exceptions.
-
such as "placing a bid"
-
what is the primary flow when everything goes as planned.
-
An effective use cases needs to have the basic flow before moving forward with writing the alternate flows.
-
alternate flows providing the following:
-
exception or error flow
-
a flow that COULD happen
-
additional flow
-
The purpose of the use cases is for effective knowledge transfer from the domain expert to the software developer
-
these use cases will serve as software requirements.
-
book by Alistair Cockburn.
-
Gatherspace.com
-
click the use case model sample now
-
hoopla
-
As a -role-, I want -goal/desire- so that -benefit-
-
have this format
-
User Story is the prelude to the use case
-
by stating the need before the use case tells the story.
-
-
31 Jul 11
-
04 Jun 11
-
03 May 11
-
27 Apr 11
-
11 Apr 11
-
05 Apr 11
-
16 Mar 11
-
01 Feb 11
-
02 Nov 10
-
12 Oct 10
-
03 Oct 10
-
28 Jul 10
-
06 May 10
-
Developing use cases should be looked at as an iterative process
-
You can always refine it later
-
basic users of Ebay? BUYERS and SELLERS
-
an actor is a Role
-
An actor can be a system, because a system plays another role in the context of your new system and has goals and interacts with other actors
-
the next logical step is to outline what the goals are of each actor
-
One you have established your actors and the goals of each actor, you have now created your initial list of high level use cases.
-
Generalization is when you "inherit" from something general and then add more detail.
-
Look at the requirements management use case diagram above and you will see there is duplicate behavior in both the buyer and seller which includes "create an account" and "search listings". Rather than have all of this duplication, we will have a more general user that has this behavior and then the actors will "inherit" this behavior from the new user.
-
The benefits of generalization are that you eliminate duplicate behavior and attributes that will ultimately make the system more understandable and flexible.
-
Every use case will have various attributes relating both to the use case iteself and to the project.
-
It will serve as a master inventory to help writ effective use cases for the requirements phase of the project.
-
Use Case Element Description Use Case Number ID to represent your use case Application What system or application does this pertain to Use Case Name The name of your use case, keep it short and sweet Use Case Description Elaborate more on the name, in paragraph form. Primary Actor Who is the main actor that this use case represents Precondition What preconditions must be met before this use case can start Trigger What event triggers this use case Basic Flow The basic flow should be the events of the use case when everything is perfect; there are no errors, no exceptions. This is the "happy day scenario". The exceptions will be handled in the "Alternate Flows" section. Alternate Flows The most significant alternatives and exceptions -
The basic flow of a use case represents the most important course of events or what happens most of the time, sometimes referred to as the 'Happy Day Scenario' because it is what occurs when everything goes well
-
An effective use cases needs to have the basic flow before moving forward with writing the alternate flows.
-
An exception or error flow to any line item in your basic flow
- An additional flow, not necessarily error based, but a flow that COULD happen
The alternate flows providing the following:
-
Gatherspace.com
-
-
17 Feb 10
-
14 Feb 10
-
23 Jan 10
-
21 Oct 09
-
19 Oct 09
-
31 Aug 09
-
01 Aug 09
-
23 Jul 09
-
20 Jul 09
-
17 Jul 09
-
15 Jul 09
-
16 Jun 09
-
04 May 09
srinivas garimellaArticle with a use case example using ebay to display the usage of use cases showing basic flows and alternate flows
-
17 Mar 09
-
09 Feb 09
-
06 Jan 09
-
20 Nov 08
-
25 May 08
Gerard Pruimhat does the word general mea
usecase uml design requirements usability programming use_case case
-
21 May 08
-
13 May 08
-
26 Mar 08
-
16 Feb 08
-
16 Nov 07
-
13 Sep 07
-
20 Aug 07
Alexander Kroonre you work and refine. You can always refine it later, so again, don't go for perfection from the get-go. Loosen up and have some
-
26 Jun 07
-
Generalization is when you "inherit" from something general and then add more detail.
-
-
09 Mar 07
-
21 Feb 07
-
28 Nov 06
-
04 Oct 06
-
01 Aug 06
Nils Davisa good, simple example of creating a use case (doesn't actually finish the example, but it's mostly there)
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.