There are no industry standard templates for use cases. This means that from one organization to another templates will differ. That said, where possible it makes sense to use best practices and adopt as many of the conventions as applicable to your situation. Here is an example of a use case – you can use this as the beginnings of a template, you can adapt it to suit your needs.

Use Case ID:xxx (Unique Identifier)Use Case Name:Update Address Field (Short Active Verb)
Created by:Joe Bloggs (Name of Person)Last Updated by:Joette Bloggs (Name of Person)
Date Created:MM/DD/YYYY (Date Created)Date Last Updated:MM/DD/YYYY (Date Updated)
Actor:Customer Service Operator (The Role or User Class That Carries Out the Function)
Description:The Customer Service Operator actions a customer request to update their address details by entering the new details into the customer address fields. The system satisfies this request by updating the address information and places the information into a queue for authorization prior to updating the customer database.
Precondition(s):1.The customer holds an account with business.2.The customer making the request must be an authorized person on the account.3.Acceptable proof of the new address has been received.4.Customer Database is online
PostConditions:1.Request stored in the authorization queue pending authorization.
Basic / NormalCourse:1.Customer Services Operator enters the address data provided by the customer.2.System verifies that the information entered is a valid address.3.System displays the updated information and requests on screen verification of the address from the Customer Service Operator.4.Customer Services Operator confirms the update.5.System creates a log of the change.6.System places the change request in a supervisors queue for authorization.
AlternateCourses (Extensions):1.(Listing of any alternate routes that the scenario could take)
Exceptions:1.(Listing of the actions that would take place if the request was not valid or had to be aborted)
Includes:xxx (Any other Use Case ID that forms part of the Basic/Normal Course)
Priority:High/Medium/Low (Delete as appropriate according to system business criticality)
FrequencyOf Use:xxx number of times per week/month/year by User Class/Rolexxx number of times per week/month/year by User Class/Rolexxx number of times per week/month/year by user Class/Role
BusinessRules:xxx (Unique Identifier that relates back to specific business rule) plus the short description associates with the rule.xxx (Unique Identifier that relates back to specific business rule) plus the short description associates with the rule.xxx (Unique Identifier that relates back to specific business rule) plus the short description associates with the rule.
SpecialRequirements:1.(Anything that has not been previously mentioned that the system is required to do in this scenario)2.3.
Assumptions:1.(Anything assumptions that are made)2.3.
Notes andIssues:1.(Any outstanding issues that relate to the validity of the use case for example authorization level requirements. The notes should be specific and have an expected resolution date attached to them).2.3.