DELEIVERABLE – 4

Livestock Management System

Group Members :
Ahsaan Ullah 17I-0133 C
Uzair Ibrar 17I-0300 C
Use Case Diagram :
 Use Cases

Use case: Register user

Actors: Seller, Buyer

Type: Primary

Description: By clicking the register button, the seller and buyer first register into the system and then
log-in. If the user is already registered, they can just log-in into the system with their specified log-in
details.

------

Use case: Log-in user

Actors: Seller, Buyer, Administrator

Type: Primary

Supporting: Seller, Buyer.

Description: By entering the log-in details, the user just log-in into the specified account type and
perform the functions/tasks according to the given registration details.

-------

Use case: Sell cattle

Actors: Seller

Type: Primary

Description: The seller will put the information on the cattle which he wants to sell like the cattle to be
sold, its breed, color, price etc. The seller will also have to pay the registration fees to get started with
the cattle system which will directly go to the administrator’s account.

-------

Use case: Buy Cattle

Actors: Buyer

Type: Primary

Description: The buyers will register in this module. Every customer will be given an id. The client will
register with his name, mobile number, e-mail and the address. He can put the requirement like the
cattle required, its breed, color etc. He can also choose any cattle among the animals available on the
website. The buyer will have to pay the registration fees to get started with the cattle system which will
directly go to the administrator’s account.
Use case: Payment

Actors: Buyer, Seller

Type: Primary

Description: Payment Entity stores the data about pay. Every payment data is here. The payment
process includes Payment ID, Registration ID, Date, Transaction no and Status. It also includes the
payment methods like COD, Credit or Debit card, or some third parties like Easy paisa or Jazz Cash
depends on the availability and business opportunities.

-------

Use case: Cattle

Actors: Seller, Buyer, Administrator

Type: Primary

Description: The user enter the cattle information to sell or buy as well to sell and find the desired
cattle. He can put the requirement like the cattle type, its breed, color etc. He can also choose any cattle
among the animals available on the website.

---------

Use case: Administrator login

Actors: Administrator

Type: Primary

Description: The administrator can view the cattle available for selling or purchase. He will also have a
unique interface where he can manage the data of animals available for sale/purchase. He can add new
cattle, update and also remove any animals from the system if it does not match the quality
requirements. Inventory will also be managed by Administrator to keep records accurate according to
sales and purchase stuff.

----------

Use case: Logout

Actors: Administrator, Seller, Buyer

Type: Primary

Description: The users can logout the system by just clicking the logout button.

--------------

Use case: Generate Reports

 Actors: Administrator, Seller, Buyer

Type: Secondary

Description: allow administrator, seller and buyer to know about statistics of animal that how much milk
is being produced, reports on food which is being consumed by animal and important one is the reports
based on health statistics of animal

Ranking Use Cases :

Characteristics for ranking use cases:
A. Significant impact (architecture) (10 Points)
B. Significant info (reports) (10 Points)
C. Risky, time critical, or complex (10 Points)
D. New, research oriented (10 Points)
E. Basic/Primary Process (10 Points)
F. Support increased revenue/decreased costs (10 Points)

Use Cases A B C D E F Total

Sign UP 7 5 1 0 7 4 24
Login 7 1 1 0 6 2 17
Sell Cattle 7 8 6 0 7 6 34
Buy Cattle 5 6 5 0 7 5 28
Cattle information 6 7 3 0 7 0 23
Cattle record 8 2 8 0 3 7 28
Milk per cattle 3 6 5 0 3 2 19
Record Disease 3 6 2 0 1 2 14
Vaccinations record 3 6 2 0 2 2 15
Cancel confirmation request 4 6 2 0 3 0 15
Perform confirmation 4 3 4 0 2 0 13
Update account 2 0 0 0 2 0 4
Log Out 1 0 0 0 1 0 2

Ran Use Case Justification

k
1-Sign Up 1-The user cannot login and control any functionality
without signing up.

2-Sell Cattle 2-Scores on most increased ranking criteria.

 High
3-User must have to make the payment to confirm his/her
3-Make payment confirmation.

4-Generate Report

5-Log in 6-User can’t make a confirmation without login.

6- Buy Cattle 6-The User can buy a cattle if he is interested in purchasing.

7- Cattle record 7-Staff must keep the record of all the sold and available
Med cattle.
ium 8-Cancel confirmation 8- No special effect on the process. User can use function if
Request needed.
9-Perform Cancelation 9-The staff must have to cancel the confirmation according
to policies if a user requests it.

10-ManageAccount 10- Minimal effect on architecture.

11 Milk per 11- Staff can keep milk per cattle record if necessary. Has no
cattle effect on the process.

Low 12-Vaccinations Record 12-Staff must keep the vaccination record to keep it easy for
veterinary surgeon for further vaccination.

13-Record Disease 13-Staff must keep the disease record to keep it easy for
veterinary surgeon for treatment.
14-Manage Staff 14- Minimal effect on architecture.

15-Log Out 15-Not necessarily important. Has no effect on the process.

Fully Dressed Use Case

Use case UC1: Sell Cattle
Primary Actor: Seller
Supporting Actors: Bank
Pre-conditions: The seller must have an account in that system.
Post-conditions: Seller can successfully upload the ad/info of the cattle, sell the cattle and
successfully get the payment from buyer.
Stakeholders and Interests/Goals:
Seller: Seller should successfully sell the cattle and get the desired payment.
Bank: Verify the payment and approve the transaction.
Success Guarantee:
The cattle can sell successfully and the seller get the required amount.
Main success scenario (or basic flow):
 The seller log-in into the account if already registered, if not registered than log-
in first.
 Seller add the info about the cattle in post ad option like the cattle type, its breed,
color etc.
 Ad is successfully post.
 If the cattle is sold, the seller get the payment successfully (depending upon which
payment method is used.)
 Log out from the system successfully.

Extensions:
 If invalid login is entered, display a message.
 If the cattle information is not complete/empty, display a message.

Requirements:
LMS system.
--------------------------------
Use case UC2: Buy Cattle
Primary Actor: Buyer
Supporting Actors: Bank
Pre-conditions: The buyer must have an account in that system.
Post-conditions: Buyer can successfully search the cattle by adding info of the cattle required,
buy the cattle and successfully transfer the amount to the given transactions details from seller.
Stakeholders and Interests/Goals:
Buyer: Buyer should successfully buy the cattle and get the desired cattle.
Bank: Verify the payment and approve the transaction.
Success Guarantee:
The buyer can successfully buy the cattle and make the transaction.
Main success scenario (or basic flow):
 The buyer log-in into the account if already registered, if not registered than log-
in first.
 Buyer add the info about the cattle in search option like the cattle type, its breed,
color etc.
 Got the required cattle and then click on buy option.
 Buyer transfer the payment successfully (depending upon which payment method is
used.)
 Log out from the system successfully.

Extensions:
 If invalid login is entered, display a message.
 If the cattle information is not complete/empty, display a message.
 Payment information is not correct, display a message.

Requirements:
LMS system.

------------------------------------------

Use case UC3: Administrator

Primary Actor: Administrator
Supporting Actors: Seller and Buyer
Pre-conditions: The administrator must have an account in that system.
Post-conditions: Administrator
Stakeholders and Interests/Goals:
Administrator: The administrator manages the inventory system and can perform the
CRUD operations also.
Success Guarantee:
The administrator can successfully perform the CRUD operations and manages
the inventory.
Main success scenario (or basic flow):
  The administrator log-in into the account with the given login
information.
 The administrator can view the cattle available for selling or purchase.
 He will also have a unique interface where he can manage the data of animals available
for sale/purchase.
 He can perform CRUD operations on any animals from the system.
 Inventory will also be managed by Administrator to keep records accurate according
to sales and purchase stuff.
 Log out from the system successfully.

Extensions:
 If invalid login is entered, display a message.
 If the cattle information is not complete/empty, display a message.

Requirements:
LMS system.

------------------------------
Use case UC4: Payment
Primary Actor: Seller, Buyer.
Supporting Actors: Bank.
Pre-conditions: The seller and buyer must have an account in that bank.
Post-conditions: Seller and Buyer can successfully make the transaction.
Stakeholders and Interests/Goals:
Seller: Seller should receive the amount successfully.
Buyer: Buyer can transfer the money successfully to the seller’s account
Bank: Verify the customer identity and approve the transaction.
Success Guarantee:
The required amount is successfully transact.
Main success scenario (or basic flow):
 The seller/buyer enter the correct information to verify identity.
 Seller/Buyer select the account type in which he/she wants to transact the money
and enters the amount of money in PKR.
  The bank/system verify the account to accept money.
 If the transaction is approved, the bank transact the amount.
 After the amount transaction and displays a message.
 Seller/Buyer cancel the transaction at any time.
Extensions:
 If invalid transact information entered, display an error.
 If system cannot find the account, display a message.
 If the entered amount not match the deposit cash, display an error.
 If transaction is successful, display a message.
Requirements:
Bank/System (Easypaisa,JazzCash).