How to write good use cases for business analysis practices

A use case details a flow of events that are performed in order to carry out a task work. A use case can be as simple as documenting a request for assistance is increased or as complex as the definition of how a customer is charged for the shipment of parts of an order to multiple addresses.

The term "actor" is used to define a role that a person or an object held in execution of a use case. The actor could be a customer service representative who is processing a request for a refund, or a server that processes credit card transactions.

Write use cases can be used is a great way to derive the functional requirements and the software development process as a whole.

Often new analysts, or people who find themselves in the role of an analyst, with no training or experience, I often wonder what should go into a good use case. Although some organizations may have strict requirements in conflict with information presented in this article, you can safely assume that you cover all the essential normal if you follow these tips:

- Use descriptive names
The name of the use case should leave no doubt about its purpose. A name such as "Contact past customers Two" is better than "Collections".

- Assign a unique identifier for each use case

Assignment of an identifier or label every use case makes it easy to refer to a case of use in other project artifacts.

- Create a summary use case

Create a brief "executive" enables other parties to achieve a high level of understanding of the purpose of the use case, without having to read the entire document.

- Frequency use Case

Documenting how often this use case is performed by actors.

- Use Cases Requirements

Document any situations or conditions that must exist before the use case invoked.

- Use Case Post-conditions

Document the conditions that must be true or false after the use case is invoked.

- Basic Use Case Logic

Document the main route or happy that you take all the use case.

- Alternative routes

Document all existing paths as the result of errors or exceptions in the main path or happy.

- Group Memory

Document all critical decisions that were made during the creation of the use case to be able to guarantee that the memory group is maintained. How to write good use cases for business analysis practices

A use case details a flow of events that are performed in order to carry out a task work. A use case can be as simple as documenting a request for assistance is increased or as complex as the definition of how a customer is charged for the shipment of parts of an order to multiple addresses.

The term "actor" is used to define a role that a person or an object held in execution of a use case. The actor could be a customer service representative who is processing a request for a refund, or a server that processes credit card transactions.

Write use cases can be used is a great way to derive the functional requirements and the software development process as a whole.

Often new analysts, or people who find themselves in the role of an analyst, with no training or experience, I often wonder what should go into a good use case. Although some organizations may have strict requirements in conflict with information presented in this article, you can safely assume that you cover all the essential normal if you follow these tips:

- Use descriptive names
The name of the use case should leave no doubt about its purpose. A name such as "Contact past customers Two" is better than "Collections".

- Assign a unique identifier for each use case

Assignment of an identifier or label every use case makes it easy to refer to a case of use in other project artifacts.

- Create a summary use case

Create a brief "executive" enables other parties to achieve a high level of understanding of the purpose of the use case, without having to read the entire document.

- Frequency use Case

Documenting how often this use case is performed by actors.

- Use Cases Requirements

Document any situations or conditions that must exist before the use case invoked.

- Use Case Post-conditions

Document the conditions that must be true or false after the use case is invoked.

- Basic Use Case Logic

Document the main route or happy that you take all the use case.

- Alternative routes

Document all existing paths as the result of errors or exceptions in the main path or happy.

- Group Memory

Document all critical decisions that were made during the creation of the use case to be able to guarantee that the memory group is maintained .......