The value of your business, industry or computer system can be explored in a use case.Use cases can be used to understand a system's ability to meet the needs of end users.Think through practical scenarios about product usefulness when designing software or a system.Product marketing use cases can be effective.There are some steps you can take to get through the writing process.
Step 1: A goal statement can be written.
The primary goal of implementing the technology or business process is briefly described in a sentence or two.Define the goals of the primary user.Any business process or piece of software can be described in a use case.You can write use cases about logging into a system, managing an account or creating a new order.
Step 2: The stakeholders can be identified.
The people in the organization care about the outcome of the process.They might not be in the process described by the use case.The system is supposed to satisfy their interests.List all of the stakeholders and their interest in the system.They should note any guarantees they get from the system.The stakeholders would include the bankers and the ATM owners if you were writing a use case about how an ATM machine works.When the user uses the ATM machine, they are not present.They need to be satisfied that systems are in place to verify the amount of money in the user's account and to create a log of transactions in case of a dispute.
Step 3: Define what is in and out of scope.
Leave out elements that are not part of the system that is being evaluated.In creating a spreadsheet containing an in/out list, it can be useful to define the scope of the project.You can create three columns.The left column has nothing to do with the system.In and Out are the next two columns.Determine which topics are in and which are out by going through the list.Producing reports about requests, merging requests to a purchase order, monitoring deliveries, and new and existing system software are topics that would be included in a use case implementing software to create purchase orders.Creating invoices and non-software parts of the system are topics that would be out.
Step 4: The use case should be defined.
Every use case requires all of these elements.There are use cases that accumulate scenarios.When a system succeeds, what happens when it fails, and how a user uses it.What happens as each step progresses is described in each scenario.The activities described in the use case will involve all of the people who are users.If you are writing a use case for logging into a software system, the users would be the ones who have to log in.Preconditions are the elements that need to be in place prior to the start of the use case.The system will recognize the usernames and passwords of users with permission to use it, if they entered the system ahead of time.The basic flow is the procedure the users use to achieve the primary goal and how the system responds to their actions.The system will allow the user in if they input a usernames and passwords.Less common actions can be explained by alternate flows.A user on a different computer has to answer a security question.When the user can't achieve the goal, the exception flows detail.An invalid user name or password can be input by the user.Post conditions must be present when the use case is finished.The user can use the software.
Step 5: Define how the user will use the technology.
Each thing the user does is a separate use case.There is a narrow scope of the use case.If a company is implementing new software to create purchase orders, you could write several use cases about this.One use case is about how users log in.It might be about how to run reports.Write a use case for each function of the new technology or business process you are analyzing.
Step 6: For each use case, describe the normal course of events.
The technology or process responds to actions the user does.In a use case about how users log into a software system, the normal course of events would state that the user enters a usernames and passwords.The software can either grant or deny access to the system.When there are obstacles to the goal, alternate and exception flows are written.If the system doesn't recognize her computer, she may be asked to verify her identity by answering a security question.If the user inputs an invalid password, she may be prompted to answer a security question and enter an e-mail address to receive new information.
Step 7: For all functions and users, repeat the steps.
Write use cases for the other functions of the software.Write the steps for the normal course of events if you identify the users for each function.When the goal can't be achieved, explain contingencies.Explain how the system responds to user actions.
Step 8: The technology or business process can be captured.
The use case explains how the technology works.A use case for logging in to software doesn't include how the code must be written or how technological components are connected.The focus is on what the user needs to do and how the software responds.Get the level of detail correct.Information about how the software responds to users should be included in a use case for implementing technology.Adding too much detail about how the software works is more like system design implementation than a use case.
Step 9: The use case should be primarily written.
Flow charts and visual diagrams are not required in use cases.Simple flow charts can be used to clarify.The use case should be based on words.The style of writing should be easy to understand and read.
Step 10: Understand the most relevant details.
A good use case can help you understand how a piece of software works.You and the reader are learing about the correct use of vocabulary.You know you're not using technological terms in a wrong way.It is possible to discuss technology and business processes in a way that is useful and valuable to others in the business community.