this is the information for relationship Final Table: 1. Billing (billing_ID, billing_Date, time_Period) 2. Payment (payment_ID, billing_ID, project_ID, payment_Date, project_Descript, balance, amount) 3. Project (project_ID, project_Total_Cost, date_Installed) 4. Client (client_ID, client_First_Name, client_Last_Name, phone, email, fax) 5. Address (address_ID, address, city, state, zip) 6. Employee (employee_ID, employee_First_Name, employee_Last_Name) 7. EmployeeSpecialty (employee_ID, specialty) example of how class diagram should be Payments and Billing Landscape designers and contractors purchase items for other customers. As a result, Orange Blossom maintains accounts for its major clients. Ultimately, the contractors and designers are responsible for payment, but it takes time to install a project and collect money from the end customers. Orange Blossom allows clients to identify a project when making a payment and tracks their spending for them. Consequently, the accounting manager tracks payments based on projects and be able to send billing notices to the contractors. Additionally, expensive plants, special orders, and large orders require down payments. Some clients make payments over time-particularly as a project progresses. As shown in Figure 2, Orange Blossom sends a monthly billing statement that lists the balance at the start of the period, new purchases, and any payments received. The Balance of the payment is the difference between the project total cost and the amount that has already been paid. Finally, the employees at Orange Blossom have multiple specialties, therefore the company wants to keep track on the database of all specialties each employee has. Furthermore, to save the amount of data stored on the database, Orange Blossom requested that no computed values should be stored. Figure 2: Orange Blossom Billing Form [1:*] 111 Orderltem [1:*] 0.11 Item.

1. this is the information for relationship
Final Table:
1. Billing (billing_ID, billing_Date, time_Period)
2. Payment (payment_ID, billing_ID, project_ID, payment_Date, project_Descript, balance,
amount)
3. Project (project_ID, project_Total_Cost, date_Installed)
4. Client (client_ID, client_First_Name, client_Last_Name, phone, email, fax)
5. Address (address_ID, address, city, state, zip)
6. Employee (employee_ID, employee_First_Name, employee_Last_Name)
7. EmployeeSpecialty (employee_ID, specialty)
example of how class diagram should be
Payments and Billing Landscape designers and contractors purchase items for other customers.
As a result, Orange Blossom maintains accounts for its major clients. Ultimately, the contractors
and designers are responsible for payment, but it takes time to install a project and collect money
from the end customers. Orange Blossom allows clients to identify a project when making a
payment and tracks their spending for them. Consequently, the accounting manager tracks
payments based on projects and be able to send billing notices to the contractors. Additionally,
expensive plants, special orders, and large orders require down payments. Some clients make
payments over time-particularly as a project progresses. As shown in Figure 2, Orange Blossom
sends a monthly billing statement that lists the balance at the start of the period, new purchases,
and any payments received. The Balance of the payment is the difference between the project
total cost and the amount that has already been paid. Finally, the employees at Orange Blossom
have multiple specialties, therefore the company wants to keep track on the database of all
specialties each employee has. Furthermore, to save the amount of data stored on the database,
Orange Blossom requested that no computed values should be stored. Figure 2: Orange Blossom
Billing Form
[1:*] 111 Orderltem [1:*] 0.11 Item