Tables and Relationship suggestions

[silversun]

Hello all,
I've created a small, simple DB to store/track my daily task(s).
Each project can have one or more complaints. I will have to run some general tests for most of the cases before I run some specific tests according to each complaint(s) to confirm if the customer was right about their complaint or not.
Each complaint has a set of tests to run in the lab and most of the tests are common in most of the complaints. Therefore I have to perform general tests in the lab on each device before specific tests and store all the tests and complaint(s) per project in a table. Also in that table I will need to store the status of each test for future use. I will update this status every time I finish a test, (default value can be "Not done yet" for example).
After I finish all the tests I will update the taskCompleted column in t_projects.

Now I need you to help me relate the tables properly and create more tables where I need.

Please check the attached picture and DB and let me know if you need me to explain my question or DB more.

 

[jdraw]

Perhaps something along this set up

 

[XPS35]

This would be my suggestion

I don not see the need to have a many-to-many relationship between project and complaint. Each complaint belongs to just one project.
In t_test you find general descriptions of all possible tests. t_test_comp tells you which tests are run for a complaint.

I don't think taskCompleted should be in t_project. You never can tell. There always can occur new complaints. It could be a item in t_complaint but you do not really need it. If all tests are done the complaint is completed (?).

 

[mike60smart]

I agree with xps35 but I would also add a Test Date field to t_test_comp table

 

[mike60smart]

My suggestion is:-