Use case is a document that defines the functionality of the document.
Functional specification is almost perform the same function but some confusion arise.
when u define use case then functional specification need remain or use case is enough?
if functional specification required along with use case then which document develop first?
if not required and u r develop only one document then which is better approach use case or functional specification?
Thanks in advance.
There are more great ideas out then you think...
I believe that the main differences are scope and intended audience.
Use cases briefly describe narrowly-focused customer requirements. Most of the detailed specification occurs verbally because the number of involved parties is low and because they are in frequent, close contact with each other.
Functional specs typically provide fully-defined "official" requirements because the customer, development, and test groups are large and separated by distance or time.
Functional specs also provide a wider view into the inter-relatedness of each feature's use cases to other areas of the application.
Use cases work well for limited projects; functional specs work better (so far) for larger development groups and large projects because of the difficulty of getting everyone together at a moment's notice to discuss an impromptu idea, problem or solution.