Tags |
|
|
Links |
|
|
Add You - How to Write Good Use Cases for Useful Business Analysis
More than a few dozen times, people say to me, 'I don't know how you fit it all in!' Sometimes even "I" don't know how I fit it all in, to be honest. However, not only did I realize early that if I wanted to accomplish the things in my life 'to do' list, I'd better take control of my time. I h
- Use Case Frequency
Document how often this use case is executed by the actors.
- Use Case Preconditions
Document any situations or conditions that must exist prior to the use case being invoked.
- Use Case Post-Conditions
Document any conditions that must be true or false after the use case is invoked.
-
If you read our last installment on medical billing, you probably noticed that it took an entire installment just to cover field number 62 of the GU0 record. If this surprised you, it shouldn't. The GU0 record is probably the most complicated CMN transmitted to a carrier of all the CMNs. In
The term "actor" is used to define a role that a person or some object plays in executing a use case. The actor might be a Customer Service Representative who is processing a refund request, or a server that processes credit card transactions.
Writing usable use cases is an excellent way to derive functional requirements and to the software development process as a whole.
Often times new analysts, or people finding themselves in an analyst's role with no training or experience, often wonder what should go into a good use case. Although some organizations may have strict requirements that conflict with the information presented in this article, you can safely assume that you'll cover all of the normal essential elements if you follow these tips:
- Use Descriptive Names The name of the use case should leave no doubt as to its purpose. A name like "Contact Past Due Customers" is better than "Collections".
- Assign a Unique identifier to Each Use Case
Assigning an identifier or label to each use case makes it easier to refer to a use case in other project artifacts.
- Create a use Case Summary
Creating an "executive" summary allows other stakeholders to gain a high-level understanding of the use case's purpose without having to read the entire document.
- Use Case Frequency
Document how often this use case is executed by the actors.
- Use Case Preconditions
Document any situations or conditions that must exist prior to the use case being invoked.
- Use Case Post-Conditions
Document any conditions that must be true or false after the use case is invoked.
- B
For this year’s corporate theme party, let’s travel back in time to the roaring twenties when prohibition, gambling, and gangsters ruled the world. Try to select a venue for the corporate get together that has a great 20s feel, a genuine art deco kind of location, if at all possible. Otherwi
Writing usable use cases is an excellent way to derive functional requirements and to the software development process as a whole.
Often times new analysts, or people finding themselves in an analyst's role with no training or experience, often wonder what should go into a good use case. Although some organizations may have strict requirements that conflict with the information presented in this article, you can safely assume that you'll cover all of the normal essential elements if you follow these tips:
- Use Descriptive Names The name of the use case should leave no doubt as to its purpose. A name like "Contact Past Due Customers" is better than "Collections".
- Assign a Unique identifier to Each Use Case
Assigning an identifier or label to each use case makes it easier to refer to a use case in other project artifacts.
- Create a use Case Summary
Creating an "executive" summary allows other stakeholders to gain a high-level understanding of the use case's purpose without having to read the entire document.
- Use Case Frequency
Document how often this use case is executed by the actors.
- Use Case Preconditions
Document any situations or conditions that must exist prior to the use case being invoked.
- Use Case Post-Conditions
Document any conditions that must be true or false after the use case is invoked.
-
Are you a homeowner or a business owner? If so, there is a good chance that you spend a good portion of your time cleaning up your home or your office. When doing so, do you wish that you could be doing something else; something other than cleaning? If so, you are definitely not alone; howe
- Use Descriptive Names The name of the use case should leave no doubt as to its purpose. A name like "Contact Past Due Customers" is better than "Collections".
- Assign a Unique identifier to Each Use Case
Assigning an identifier or label to each use case makes it easier to refer to a use case in other project artifacts.
- Create a use Case Summary
Creating an "executive" summary allows other stakeholders to gain a high-level understanding of the use case's purpose without having to read the entire document.
- Use Case Frequency
Document how often this use case is executed by the actors.
- Use Case Preconditions
Document any situations or conditions that must exist prior to the use case being invoked.
- Use Case Post-Conditions
Document any conditions that must be true or false after the use case is invoked.
-
Unnoticed in the spate of dramatic labor union events of the past week is a sudden acceleration in the "de-unionization" of America.The 111-day-old coal strike ended in a Pyrrhic victory for the miners - another such win will price them out of the energy market once again.The Fir
- Assign a Unique identifier to Each Use Case
Assigning an identifier or label to each use case makes it easier to refer to a use case in other project artifacts.
- Create a use Case Summary
Creating an "executive" summary allows other stakeholders to gain a high-level understanding of the use case's purpose without having to read the entire document.
- Use Case Frequency
Document how often this use case is executed by the actors.
- Use Case Preconditions
Document any situations or conditions that must exist prior to the use case being invoked.
- Use Case Post-Conditions
Document any conditions that must be true or false after the use case is invoked.
-
The primary advantage to formal configuration management is a resulting project with good change management, as evidenced through changes that are properly identified, structured, linked and owned. Configuration management provides the documentation explaining why the project changes occurred,
- Use Case Frequency
Document how often this use case is executed by the actors.
- Use Case Preconditions
Document any situations or conditions that must exist prior to the use case being invoked.
- Use Case Post-Conditions
Document any conditions that must be true or false after the use case is invoked.
- Basic Use Case Logic
Document the main or happy path that the user takes throughout the use case.
- Alternate Paths
Document all paths that exist as the result of exceptions or errors in the main or happy path.
- Group Memory
Document all critical decisions that were made during the creation of the use case in order to be able to ensure that the group memory is maintained.
HTTP = HTML link (for blogs, profiles,phorums):
<a href="http://www.addyou.info/article/3676/addyou-How-to-Write-Good-Use-Cases-for-Useful-Business-Analysis.html">How to Write Good Use Cases for Useful Business Analysis</a>
BB link (for phorums):
[url=http://www.addyou.info/article/3676/addyou-How-to-Write-Good-Use-Cases-for-Useful-Business-Analysis.html]How to Write Good Use Cases for Useful Business Analysis[/url]
Related Articles:
Stop Throwing Money Away In Your IT Department
Bookmark it:
|