A use case diagram for the described system

Device Manufacturer

The owner of a company dealing with the design and sales of custom made devices plans to use an IT system to support his activity, based on the following requirements.

1. The planned system should contain information about the company's employees and clients, employees may also be individual clients.

2. For each employee remember: name, phone number, dates of employment, salaries and bonus. For the individual client - name, surname, telephone number, type of identity document, ID number, if provided . All employees work at the moment at the same address it may change in the future.

3. Employee bonuses are calculated based on the fixed bonus of 1,000 PLN for all employees and an additional sales bonus for each sold device.

4. For all clients, remember the contact details, with a unique REGON number additionally for a business client. If a client came to the company on the recommendation of another client, it should be remembered which client has done the recommendation.

5. The client can order the custom devices. The data of potential clients is not stored. If the customer orders a device, we store : date of placing order , colour in hex, amount of the product, actual date of shipment of the device, status ("placed",ready to ship, "cancelled", "completed"). An order can be only cancelled when the order isnt ready to ship.

6. For the device we store Power consumption (cant be higher than 2000W), device build date, the price calculated on the basis of the prices of the elements of which it is composed, status- ordered, built, ready, sold. Devices can be divided into grills, sandwich toasters, waffle maker and so on. For grills, we store information about whether the height can be adjusted, if so, we want to store the max height. For sandwich toasters we want to know their capacity - it can be 2, 4 .. pieces, and for the waffle iron, what shapes the waffle iron makes, at least 2. Sometimes it may happen that the customer wants one device that has all these functionalities.

7. The employees in the company sell the devices, 3 to 5 employees are assigned to sell a device. one of the employees with the highest seniority in the company oversees the others. Employees receive a 5% bonus from the price of the device they have sold.

8. The system stores information about the components that make up the device. a unique number is assigned to these components for each device. The device may consist of many components, but certainly not less than 2. Each component is described by type, catalogue number, name, security certificate, at least one of the materials, with which it is built. A component can be build from other components. We want to store the date when the specific component was added to the other.

9. The system should support the company in the implementation of functions such as:

a. Displaying the list of offered devices (all users);

b. Add new order (employee, owner);

c. Display information about a device (all users);

d. Displaying the list of employees assigned to a given device (owner) - also possible while displaying information about a given device;

e. Creation of a set of devices sold during a given period (owner) - along with a list of employees assigned to a given device;

f. Add a new device, where the algorithm depends on the type of device (owner);

g. Removal of cancelled orders (automatically, half a year after cancellation)