Professional Documents
Culture Documents
Management System
Design Document
Version 1.0
1
Revision History
Date Version Description Author
(dd/mm/yyyy)
13-09-2023 1.0 Design document includes BC190201751
introduction, ERD, Sequence
diagram, Conceptual diagram
GUI and Test cases
2
Table of Contents
6. Database Design---------------------------------------------------------------11
7. Interface Design---------------------------------------------------------------13
8. Test Cases----------------------------------------------------------------16
time, people may have excess food that may be good but may be wasted due to lack of organizations
catering to needy people. In such times, it is of great help if there are places that can store these
products and distributing them amongst the needy. Our system works to get food from such donors
and help people. Our network moves the food making sure the donated food and groceries reach
where they are needed the most. We are assuming the donor approaches our organization to make
the donations. We register the donor and accept donations. The donations accepted are then added to
the inventory-by-inventory clerk by updating their expiry date. We are assuming that needy
organizations contact us when they are in need of food, once they approach we register those
organization so as to make them part of our system. The organizations are categorized on the basis of
people they cater. E.g.: old people. Once the registered organization logs onto the system, they will
find a product list suitable to their needs. They can add the product from the list and then logout.
To ensure that there is an optimum efficiency of the food that is delivered to the organization, an
algorithm is implemented that calculates the math and determines if the product will pass its expiry
date within the delivery time frame also food products catering to the specific age group are
4
3. Sequence Diagrams
5
Admin manages user
6
User / Admin LogIn
7
Admin/User Add/view Food Collection
8
4. Conceptual Diagram
9
5. Class Diagram
10
6. Database Design
11
7. Interface Design
12
13
14
15
8. Test Cases
Test case 1:
User sign up
Preconditions: User sign up the system
Actions: Click on the button.
System opens the option.
Expected result: Operation is completed successfully.
Tested by: ASMA AFRAQ
Result: pass
Test case 2:
User login:
Preconditions: User log in
Actions: Click on the button.
System opens the option.
Expected result: Operation is completed successfully.
Tested by: ASMA AFRAQ
Result: pass
Test case 3:
Admin/ user View food
Precondition: Admin/ users log in the system
Actions: Admin/User clicks on the button “Food”
System opens the option.
Admin/User View available food
Expected result: Operation is completed successfully.
Tested by: ASMA AFRAQ
Test case 4:
Check Food Quantity
Preconditions: Users Click on details
Actions: Clicks on the Details button.
System opens the option.
User view property information.
Expected result: Operation is completed successfully.
Tested by: ASMA AFRAQ
Result: pass
16
Test case 5:
Distribute Food
Preconditions: User buy a property
Actions: Clicks on the Distribute button.
System opens the option.
User get food
Expected result: Operation is completed successfully.
Tested by: ASMA AFRAQ
Result: pass
Test case 6:
Admin provide “Contact Us” page
Preconditions: User log in the system
Actions: Click on the button.
System opens the option.
Expected result: Operation is completed successfully.
Tested by: ASMA AFRAQ
Result: pass
Test case 7:
User log out
Preconditions: User log out the system
Actions: Click on the button.
System opens the option.
Expected result: Operation is completed successfully.
Tested by: ASMA AFRAQ
Result: pass
17