B
BMM
Hi. I have a dumb question. Is a database an application? And, in the
context of a data-driven web-enabled application, is the database still an
application? I have a project lead who says it is. In fact, he says that our
web application is a set of "distributed applications" because
* the database is an application, and
* clients connecting to our web app will connect with a web browser (an
application) and may put data pulled from the database into a spreadsheet
program like Excel (an application).
Thus, "distributed applications".
I realize that a database is an example of "application software" -- as
opposed to "system software". And that it is shrink-wrappable. (see def here
http://en.wikipedia.org/wiki/Database#Applications_of_databases)
But in the context of a web app a database is most definitely /not/ an
application. It is a data store. And I know that a web app is one that has a
multi-tiered architecture... and that it has distributed application
/components/. But how can I convince the project lead (who believes he knows
everything about software because he has a degree in, um, orbital mechanics)
of this and prevent our specifications documents -- which are in the process
of being written -- from incorrectly referring to our web application as a
"set of applications".
Brian
context of a data-driven web-enabled application, is the database still an
application? I have a project lead who says it is. In fact, he says that our
web application is a set of "distributed applications" because
* the database is an application, and
* clients connecting to our web app will connect with a web browser (an
application) and may put data pulled from the database into a spreadsheet
program like Excel (an application).
Thus, "distributed applications".
I realize that a database is an example of "application software" -- as
opposed to "system software". And that it is shrink-wrappable. (see def here
http://en.wikipedia.org/wiki/Database#Applications_of_databases)
But in the context of a web app a database is most definitely /not/ an
application. It is a data store. And I know that a web app is one that has a
multi-tiered architecture... and that it has distributed application
/components/. But how can I convince the project lead (who believes he knows
everything about software because he has a degree in, um, orbital mechanics)
of this and prevent our specifications documents -- which are in the process
of being written -- from incorrectly referring to our web application as a
"set of applications".
Brian