| What We
Database I: II
| Using a database should be easy.
Put data in - get data out. If that's all there is, why do people have
so many problems using databases? To DC, the answer centers not on whether
the system can manage information (Filemaker/Access/SqlServer, among others,
do this very well.) but rather on not understanding how a company does
business because manipulating data without relevancy to a given company's
business practices insures that the system envisioned will not do the
job for which it is intended. Because DC understands workflow, interface
design and communications, the approach we take on building databases
starts with learning how a company does business FIRST and THEN designing
a system to support that business process.
As an example of this approach, seen below is an Invoice view of an Investment Banker system designed to work with online Pershing data to enable IBs to pull out information needed to bill accounts. Because the system is keyed to IB business operations, the time it takes to get people up to speed running this
environment is minimal.
Top of page