DELIVERABLE-2

for

Aviary Management System

Prepared By:

BITF20A004

BITF20A009

BITF20A027

Date: 15-06-2022

Faculty of Computing and Information Technology (FCIT)

Use Case Diagram
 Use Case Specifications
1
ID and Name: UC-1 Maintain Bird Records on the Aviary
Primary Actor: Breeder Secondary Actors: Buyer, Shopkeeper
Description: The Breeder selects the Bird, determine its uniquely identifying ring,
extract its previous record and update it according to its need. Breeder
can also put it into ‘For Sale Birds’ icon by demanding a reasonable price
for it, if he wanted to sale that particular Bird.
Trigger: Breeder maintain the pedigree, breeding and health record of his birds.
Pre-Condition: PRE-1. Breeder must use login to access his Record.
PRE-2. Database must have updated the record of every bird successfully.
PRE-3. All the birds should be present in the Aviary List while only For
Sale Birds should be listed on the “Selling List”.
PRE-4. Birds which are sold out by breeder must be updated from
Present List to Sold List.
Normal Flow: 1.0 Maintain the record of total birds present in aviary
1. Choose a bird
2. Determine the ring number awarded to it.
3. Extract previous record against that ring.
4. Update the record.
5. Add a new record for new hatchlings.

Alternative Flow: 1.1 Sale a bird from aviary.

1. Select a particular bird to sale.
2. Add it to Sale items.
3. Add its pedigree, gender and other details to view for the viewer.
4. Add demand price for it.
5. Update aviary record.
6. Add the bird to Sold List from Aviary Birds.

Exceptions: 1.2 Breeder want to purchase a new bird.

1. Choose Buyer option instead of Breeder.
2. Select the required bird.
3. Check the pedigree and details of that bird.
4. Check for Price.
5. Make payment according to given method.
6. Add it to Breeder’s Aviary Bird’s List.
7. Add its Pedigree to Aviary’s database.

Priority: High
Frequency of Use: Breeder have to update the record of every Bird on weekly basis to be
updated about his birds. Moreover, he have to update record also when
a new bird is purchased or sold by him.
Other Information: The system must remain updated by the current condition of birds
regarding their health, breed, mutation and number of birds available for
sale, out of total birds present on the aviary.
Assumptions: The system must display the correct number of pairs if birds that are
currently present.

2
ID and Name: UC-2 Buy a Bird
Primary Actor: Buyer Secondary Actors: Breeder, Shopkeeper
Description: The Buyer selects the Birds which he requires and add them to his/her
cart and go for payment method. Then he selects the method of payment
and fill the details and specify his address and go for the confirmation of
the order.
Trigger: The Buyer need the birds so choose the birds of his own choice.
Pre-Condition: PRE-1. Buyer must use login to identify himself.
PRE-2. Buyer must use a valid Payment method to pay for his order.
PRE-3. The Birds he selects must be available in the Aviary.
Normal Flow: 2.0 Buy a Bird Using Aviary Management System App Online
6. View the Available bird in the app.
7. Choose the birds he wants.
8. Go for the Payment.
9. Give the required details.
10. Confirm the order.
11. The System send a request to Shopkeeper for the order.

Alternative Flow: 2.1 Buy a Bird by visiting the shop.

7. Buyer Went to the Shop.
8. Selects the Bird he wants by Viewing in different cages.
9. Ask the Shopkeeper to make the bill.
10. The shopkeeper makes the.
11. The Buyer pays the bill.
12. The Shopkeeper adds the sales in the system.

Exceptions: 2.2 Bird is not present in shop and system.

8. The system displays Bird out of stock that user require.
9. Buyer visit the Shop and ask for the shopkeeper for the bird.
10. If shopkeeper has no info about it he refers buyer to breeder.
11. The buyer asks the breeder whether the bird is present.
12. The Breeder Update him if the bird is present is not.
13. The Buyer purchase bird directly from breeder if available.
Priority: High
Frequency of Use: Many times, in a day or even week depending upon the level of business
and traffic on the system.
Other Information: The system must remain updated by latest bird that are present in the
Aviary and the new birds that are being delivered in it.
Assumptions: The system must display the correct number of pairs if birds that are
currently present.

ID and Name: UC-3 Buy and Sell Birds

Primary Actor: Shopkeeper Secondary Actors: Breeder Buyer
Description: The Shopkeeper maintain the stock of birds he have. When the buyer
comes for the bird first of all he checks the bird whether available or not.
Then shopkeeper tell the price of bird.
Trigger: The Shopkeeper maintain birds stock on his shop
Pre-Condition: PRE-1. Shopkeeper must have access to software.
PRE-2. Shopkeeper must have stock available.
PRE-3. Bird database must be online.
Normal Flow: 3.0 Shopkeeper maintain stock of bird by himself
1.View the birds quantity.
2.View the no. of birds sell today.
3.If specific bird not available then need to buy the bird.
4.Update the bird database .
5.Managing the payment procedure.
Alternative Flow: 3.1 When stock of bird maintain by support team.
13. Shopkeeper keep in touch with team.
14. Team tells him the birds quantity
15. Alarm message from them about bird shortage.
16. Database maintain by team.
17. Payment receipt.

Exceptions: 3.2 Specific not found from buyer then contact with breeder
14. The system displays Bird out of stock.
15. Shopkeeper contact with breeder.
16. Breeder tells about specific bird available or not.
17. Then shopkeeper directed the buyer with breeder.

Priority: High
Frequency of Use: Many times, in a day or even week depending upon the level of business
and traffic on the system.
Other Information: The system must remain updated by latest bird that are present in the
Aviary and the new birds that are being delivered in it.
Assumptions: The system must display the correct number of birds if birds that are
currently present.

4
ID and Name: UC-4 Backend support
Primary Actor: Support team Secondary Actors:
Breeder, Shopkeeper
Description: The Support team maintain the software on backend. They fix all issues
that come from breeder, shopkeeper. They keep in touch with breeder,
shopkeeper regularly.
Trigger: The Support team clear all issues from backend.
Pre-Condition: PRE-1. Support team must have access to software.
PRE-2. Support team must have contact details of users.
PRE-3. Support must have the permission from users
Normal Flow: 4.0 Support team fixing issues when user contact them.
1.When user found any issue/problem relating software.
2.There is option of help at bottom-right .
3.By selecting the option, you write message about the problem you
are facing.
4.When support team see your message, they contact for further
information
5.Problem solved.
Alternative Flow: 4.1 Issues solved automatically by Support Team.
1.Support team continuously take an eye if any issue arise.
2.Support team contact user and update them.
3.After getting permission, they resolve the issue.
4.Message sent to user after fixing issue.

Exceptions: 4.2 User want to add new feature.

1.If user want to add some feature.
2.User contact with support team and tells them about new feature.
3.Support team determine whether the feature is useful or not.
4.If the feature is useful, then they implement them.
5.They keep in touch with user for requirements.
Priority: Low
Frequency of Use: Once in a week if important otherwise when user contact them.
Other Information: Support team is the team which was working on the time of software
making and also working after project complete.
Assumptions: Support team keep on working until validity expires.
 5
ID and Name: UC-5 Delivery Agent delivers the Bird
Primary Actor: Delivery Agent Secondary Actors: Breeder, Buyer, Shopkeeper
Description: Delivery Agent pick the bird from Breeder or Shopkeeper, deliver it to the
buyer and notify the Breeder and Shopkeeper that his/her bird is
delivered at destination. Sometimes he also do Cash on Delivery if
needed.
Trigger: Delivery Agent delivers the Bird for Buyer.
Pre-Condition: PRE-1. Delivery agent must be awarded a uniquely identifying ID.
PRE-2.

Normal Flow: 1.0 Deliver the Bird to Buyer for Online Payment
12. Pick the Bird.
13. Verify the Order.
14. Check the payment status.
15. Reach the shipping address.
16. Verify the Buyer’s ID.
17. Take buyer’s signature.
18. Notify the Shopkeeper/Breeder.

Alternative Flow: 1.1 Deliver the Bird to Buyer for Cash on Delivery
1. Pick the Bird.
2. Verify the Order.
3. Reach the shipping address.
4. Verify the Buyer’s ID.
5. Take the charges against delivery.
6. Take buyer’s signature.
7. Mark the payment status.
8. Notify the Shopkeeper/Breeder.
Exceptions: 1.2 Wrong shipping address OR Buyer not found
18. Pick the Bird.
19. Verify the Order.
20. Reach the shipping address.
21. Address/Buyer not fount
22. Notify the Shopkeeper/Breeder.
23. Return Bird back to Breeder/Shopkeeper.

Priority: High
Frequency of Use: Every time a Buyer orders the Bird online, Delivery agent have to deliver
it to the buyer.
Other Information: The system must notify all the stakeholders (Buyer/Shopkeeper/Breeder)
for all successful and unsuccessful dealings and also notify if there is any
issue or problem.
Assumptions: Delivery Agent must be registered first before providing services.

User Stories

Stakeholder Use Case User Story

Shopkeeper Check Birds Status As a Shopkeeper, I want to check which
birds are currently present in Aviary.

Breeder Add New Birds As a Breeder, I want to add new birds

which are delivered in aviary along with
their specie and number of pairs.

Breeder Remove Birds As a Breeder, I want to delete/remove

record of birds that are being sold and
out of stock.

Buyer View Birds As a Buyer, I want to View the birds

along with their specie that are currently
present in the Aviary.

Buyer Pay for Order As a Buyer, I want to make Payment for

the birds which I selected.

Shopkeeper Receive Payment As a Shopkeeper, I want to receive the

payment that the buyer had paid for the
order.
Swimlane Diagram
Activity Diagram
Data Flow Diagram

Level 0
Level 1
Level 2

Event
User enter wrong password
User select “Enter bird data”
option
User select “Searching” option
User want to change password
Event Response Table
System State
Invalid password message
displayed on screen
Display message appear on
screen
Message appear on screen
Password successfully changed
message display on screen
System Response
1.Enter password again
1.Data which user enters store
to database
1.searching from database if
data available and show
2.If data not found, no found
data appear on screen
1.Enter current password and
then new password
2.Enter phone number and
confirmation message send to
your phone
Prototypes