Integration Testing Case Study Use Case

Ver 1.0 Page No. 1

 Integration Testing Case Study Use Case

USE CASE UC01 Process a New Customer

Goal in Context Allow to enter new customer Details
Scope & Level This use case is limited to creating a new customer detail
Preconditions The Agent at Cargo office is able to access Login screen.
Success End Member creates a new Customer
Condition
Failed End N/A
Condition
Primary Actors Agents of Cargo Office
Secondary Actors Customer
Stakeholders and Customer - We are creating a new customer.
Interests Agent The agent of the Cargo office would process the addition of New Customer.
Trigger Customer coming or calling or mailing to book an order
Main Success Step Action
Scenario
1. The Agent in the Cargo office logs in to the system by providing his valid user name and password.

2. The customer approaches the agent in the cargo office.

3. The Agent checks the availability of the customer with the help of customer id.

4. If the customer id is not available, then the agent is popped with a screen of new customer.

5. The following details are maintained for customer which is as follows :

a. customer id (Int)
b. Customer Name (char)
c. Company name (char)
d. Region code (int)

Ver 1.0 Page No. 2

 Integration Testing Case Study Use Case
e. Type of Business (char)
f. Company Address (char

6. Region id entered is checked against the region master.

USE CASE UC02 Order entry

Goal in Context The use case is limited to the extent of the creation of the Order for the customer.
Scope & Level This use case is limited to the creation of a new order.
Preconditions UC01
Success End An order is booked.
Condition
Failed End An order is not booked if the cargo office does not have a route applicable for destination mentioned by
Condition customer.
Primary Actors Agent in cargo office
Secondary Actors Customer
Stakeholders and Agent is stake holder
Interests Order is booked
Trucks are to be employed for the order booked.
Trigger Customer coming or calling or mailing to book an order
Main Success Step Action
Scenario
1. We know that if the customer is valid. The Agent invokes the Order entry Screen.

2. The Agent enters the following details into the order entry screen.

3. The details in the order detail screen are as follows :

a. Order Date (date)
b. Delivery Date (Date)
c. Destination Id (Int)

Ver 1.0 Page No. 3

 Integration Testing Case Study Use Case
d. Origin Place (Int)
e. Orign Name (char)
f. Destination Name (char)
g. Customer Id (Int)
h. Product id (int)
i. Product Name (char)
j. Qty : Float
k. Order No. : Char (5) first three alphanumeric and rest numeric
l. Order Dt. (Date)
m. Region Code (int)
n. Truck id (int)
o. Truck name (char)
p. Truck type (char)
q. Truck capacity (int)

4. The Order date cannot be greater than System date

5. The Delivery Date cannot be less than the Order date

6. The Destination id is checked against the valid destination maintained in Location master

7. The orign ids are checked against the valid orign ids maintained in Location master

8. The region ids are checked against the region master

9. The Destination and origin ids are verified against the region selected for the origin and destination. The
destination name, orign name is displayed accordingly.
10. The user selects either O for Owned trucks and H for Hired Trucks.

11 On selecting O and also depending upon the product and Qty, the truck ids are displayed first of

Ver 1.0 Page No. 4

 Integration Testing Case Study Use Case
Company Owned trucks. On selection of truck id, the truck capacity, truck type is displayed.
12. On selecting H, the lists of agents are displayed and the trucks under them are displayed of hired trucks
and of what capacity. On selection of truck id, the truck capacity and type is displayed.
13. The truck name is displayed both of owned and hired trucks.
14 In the database the desired quantity of the Truck number / Id is saved and generates an Order No.
associate Challan Number. One order can have more than one challan. There is one challan prepared for
each truck.

Ver 1.0 Page No. 5