Question

Imagine that you are a junior member of a research lab and your PI has heard that you have database experience. He asks you to create a database that will store data about ticks and the results of tests that show what organism(s) infect the ticks. You are very happy for the opportunity, but whenever you attempt to meet with him to discuss the requirements, you are told to “look at the current system” which is an Excel spreadsheet, and work from that.

Discuss how you would explain to your PI the importance of a thorough design and the need to discuss the details. Make up one or more examples to illustrate what you might want to ask the PI.

Answer 1

Looking at the excel sheet may not end up with a clear-cut understanding of requirements for database design. It does provide an overview but not the complete clarity of it.

I would explain him below scenarios.
-> Scheduling a meeting helps to determine exactly the functional and non-functional requirements needed to build the system. These requirements play a significant role in determining the type of table structure that needs to be constructed, amount of data, relationships between the structure etc.

-> It helps to come up with the schematic structure of a database with necessary constraints and compliances. It would help to understand better the architecture of a system with the need of interaction between the multiple components of a system.

Please do comment for any doubts or modifications.