I am creating a design for an application which requires the following.
There are multiple projects.
For each project, the app collects data from multiple sources.
For each project, the app performs calculations based on the input data and produces results.
Each project will have different sets of inputs, hence different sets of outputs.
a Total Revenue this week ($56,000)
b Total Products sold this week (5673)
c Total Unique Products sold (123)
a Total number of Active Employees (234)
b Total new Employees (13)
c Total terminated Employees (4)
As you can see, the projects are never related to each other.
But since the app should allow multiple projects to be created.
I can not create sep table for each project since the projects will be created
over time and this app should be able to handle this without creating new tables.
This is what I thought ... I am sure that there has to be a better way out there.
I am "suspicious" of this requirement: if no 2 projects have anything in common, then how will the app know how to perform the calculations for each project's unique sets of data? Surely you'll need a new app for each project (or a new module in the app).
This smacks of a lack of analysis to find out what the requirements really are and what they have in common, and/or an attempt to build the One Great Database that will somehow meet all possible current and future requirements for anything without modification. If that were possible we'd all have one!