Dewey Cheatum and Howe (DCH) lawfirm provides multiple services to its customers.

The firm has grown quickly and is having difficulty keeping up with all of the various information needs of the firm.

DCH firm offers many services to its customers (such as Divorce, Bankruptcy, etc.). For each service, the name and

approximate legal hours is needed. Attorneys are identified by a timekeeper ID, but the system should also record

an attorney's name, home address, telephone and hourly fee. Attorneys are not able to practice all types of law,

but each one has a specialty and several seconday types of law that they practice. It is important to know what

types of law each attorney practices as well as knowing their primary area of law.

DCH firm has many customers. Each customer can have 1 active case of each type of law.

(For example, Customer Joe can have a Divorce case and a Bankruptcy case, but he cannot have 2 active Divorce

cases. Joe can have 2 divorce cases, but one must be inactive) It is important to know the customers name,

age (birthdate), address, telephone).

Each case can have 1 customer assigned to it. There can be up to 3 attorneys assigned.

Each attorney on the case has a designation. The attorney can be the responsible, working or originating attorney.

Each case can have 1 status. Each case can be only of a particular type of service (Divorce, Bankruptcy, etc..)

Time worked on a case is tracked. You need to know the date, case, amount worked for each case and which attorney

did the work. You can have multiple attorneys doing work on a case, but they need to be one of the

3 attorneys listed on the case. The dollar total for the total case depends on what attorney worked on

the case and what their hourly fee is .

1. Create the Implementation-ready UML class diagram for Dewey Cheatum and Howe lawfirm's

data needs in Microsoft Visio

2. Using the Tables to the left, what field could be used a a surrogate primary key to emp_id and why?

3. List all of the attributes of an attorney.

4. Is it possible to have a person appear in the staff table without appearing in the employee table?

Why or why not?

5. Why is using the employee's name as a primary key a bad idea?

6. What does splitting the employees into staff and attorneys say about the staff?

What is the purpose of doing this in a database?

PK Employee Emp_ID Lname Fname SSN Birth Date Hire Date Staff PK,FK1 Emp_ID PK,FK1 Attorney Emp_ID License BarGradDate MajorLawArea Dept WorkHours