By:Niall Kennedy A use case details a flow of events that are executed in order to accomplish some business task. A use case can be as simple as documenting how a help ticket gets escalated or as complex as defining how a customer gets charged for shipping parts of an order to multiple addresses. 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. - 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. A use case details a flow of events that are executed in order to accomplish some business task. A use case can be as simple as documenting how a help ticket gets escalated or as complex as defining how a customer gets charged for shipping parts of an order to multiple addresses. 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. - 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. Article Source: http://www.redsofts.com/articles/ Niall Kennedy is an internet marketing consultant. Positive is a UK provider of professional Business Analysis Training. Contact Positive at www.Be-Positive.co.uk for more information about Writing Good Use Cases. All rights reserved. This article may be reprinted in full so long as the resource box and the live links are included intact. Copyright Be-Positive.co.uk More Articles from Business Category: How To Be More Successful By Using Effective Time Management Tools Team Working - Personality Profiling Can Help Are You Losing Focus? Use These Time Management Tips To Get It Back Is Your Company At Risk? Make Good Use Of A Certificate Of Insurance How Do You Avoid Online Survey Scams Partner Up In Business With A Joint Venture Agreement Learn to Control Your Retirement Investments, Earn Higher Returns, Invest in Real Estate, Franchises Available Mentoring Programs Why Are Online Surveys So Popular How Do You Create An Income From Online Surveys Tips To Starting A Successful Internet Business The Qualities Of An Effective Executive Summary Do Your Employees Know The Ground Rules? 5 Tips for Collecting on Past Due Accounts Helping Children to Understand Alternative Energy

Soft Categories
Audio & Mp3   Business & Finance   Desktop Enhancements   Games   Home & Education   Internet   Multimedia & Design   Security & Privacy   Software Development   System Utilities   Web Development