just go for google and search by giving usecase template
if u didnt get then mail me
sateesh_t7101@yahoo.co.in

we get use caes in wwwoord format
that is the answer

Introduction
---------------
Describe a quick background of the use case.

Actors
---------
List the actors that interact and participate in this use 
case. 

Pre-conditions
----------------
Pre-conditions that need to be satisfied for the use case 
to perform. 

Post-conditions
------------------
Define the different states in which you expect the system 
to be in, after the use case executes.

Basic Flow
-------------
List the primary events that will occur when this use case 
is executed. 

Alternative flows?
--------------------
Any subsidiary events that can occur in the use case should 
be separately listed. List each such event as an 
alternative flow. A use case can have as many alternative 
flows as required. 

Special Requirements
------------------------
Business rules for the basic and alternative flows should 
be listed as special requirements in the use case 
narration. These business rules will also be used for 
writing test cases. Both success and failure scenarios 
should be described here.

Use case relationships
------------------------
For complex systems, it is recommended to document the 
relationships between use cases. Listing the relationships 
between use cases also provides a mechanism for 
traceability.

BRIEF DESCRIPTION 
1.2	ACTIVITY DIAGRAM
1.3             ACTORS LIST 
1.4	PRE-CONDITIONS
1.5	FLOW
1.5.1	Typical Flow
1.5.2	Alternate Flow
1.5.3	Exceptional Flow
1.6	POST-CONDITIONS
1.7	SPECIAL REQUIREMENTS
1.8	TABLES
1.8.1	Mandatory status
1.8.2	Validations
1.8.3	Descriptions
1.9	PARKING LOT
2.0	COMMENTS 
2.1            SCREENS