• There are 8 tables in the database, 4 of them are based on the company target types and the other 4 are their respective tests.
• I decided to design the model in this way because each target type is different from the other, they have different codes and different physical characteristics, some of them are physically one and some others have more pieces, like a face and a body.
• The target types tables (CS-30, IBA, TR-30, and OtherTargets) are separated because it makes it easier to map the information and consults related to a single target type.
• The target types tables and the tests tables have a relationship of one to many, which means a single target can have multiple tests depending on the test quantity specified.
• I like to see this relationship based on the company's production system, the target type table is like a box with a specific code and lot number, and inside the box, there are single targets with their own codes and tests.

• I had the opportunity to choose what language and framework to use, I decided to use .NET because it let me develop a complex solution in a short time. As well because it is easy to deploy, it is easy to use, it is flexible with all its libraries, and the security Microsoft provides.
• I added dropdown menus to control the data entry to avoid misspelling mistakes, this helped employees to save time during production.
• The design makes it easier to display changes with the current date and time.
• The database makes it easy to understand the target flow through all its stages(Life Cycle).
• The tracking system helps to locate in real time where a certain target is and who is in charge of that target.
• The separate indexes make clear consults for target types and for their proper exams and results.
• The target data model of the database makes code easy to handle and understand, this lets future updates, improvements, and expansions be added.

Before the deployment of this database, the department database was more for inventory purposes. Their current diagrams for target flow and life cycle were too difficult to understand even for employees.
This database makes it easy to understand all those diagrams like a track system, showing the target flow in a linear way.
The Database will let the employees save time looking for a specific target through books and notes making them able to insert a keyword to locate a target status, code, or lot number to get all its information.
The proper use of the database will let keep on track and update all the information needed for decision making.