dileepdon

 Profile Answers by dileepdon 

• Jun 11th, 2006

 

The functional and System Requirements are described by BA in terms of USE CASE.

Every usecase describes a functionality in terms of inputs, process and outputs. Through these usecases we prepare test cases called as Business Logic Based Test Cases. 

raghuramsuravarapu

 Profile Answers by raghuramsuravarapu Questions by raghuramsuravarapu

• Jun 11th, 2006

 

Use case's are the functional description of each and every feature,how the user is supposed to use in the application/product. It is not mandatory to use use case's to derive test case's.It depends on the company level strategy.Test case's can be derived by using Software Requirements Specification and Functional Specification document also.

General Use Case Format :

->Use Case Name :

->Purpose :

->Description :

->Actors :

->Precondition :

->Cross References :

->Main Flow :

    (a) Entry Fields :

    (b) Display Fields :

    (c) Actions :

    (d) Alternate Flow :

->Sub Flow :

    (a) Entry Fields :

    (b) Display Fields :

    (c) Actions :

    (d) Alternate Flow :

->Buisiness Rules :

->Validations :

->Post Conditions :

Sujatars

 Profile Answers by Sujatars 

• Feb 27th, 2007

 

An use case is a functional & sytem requirement of how a user (or another system)uses the system being designed to perform a given task . A Use case can provide a powerful means of communication between customer,developer , tester & other persons.
The information about each use case that needs to be determined for defining the case follows:
• Use Case Name or ID
A short phrase in business terms or identifier that identifies and describes the use case.
• Actor
Anything that needs to exchange information with the system. Often it is a role played
by the user of the system or it could be another system.
• Objective
A description of what a use case accomplishes given a defined set of conditions.
• Preconditions
The entrance criteria or state that the system must be in for the use case to execute.
• Results
The expected completion criteria of the use case.
• Detailed Description
• The sequence of steps (performed by the actor) necessary to execute the use case.
• The model (system) response of each step.
• This is the basic course of events that support the precondition and results.
• The description is from a user’s (“black-box”) point of view and does not include
details about the events of the internal system.
• Exceptions
Errors or deviations that may occur that cause the actor to deviate from the basic
course.
• Alternative Courses
• A deviation from the step-by-step event so the Detailed Description that generally
inserts extra steps or omits steps.
• These are valid events, but are not the basic course of events.