|
Every Access database lands somewhere on the
development life cycle. Perhaps your database exists only
as a notion. Perhaps it’s in full production. Or maybe
it’s already in use, but bursting at the seams, awaiting
migration to SQL Server.
Regardless of the details, all databases go
through development. It’s up to you to decide the degree
of formality in the process. It’s up to us to carry it
out.
This is the clipboard phase, when no computers
are on and lots of questions are asked. What information do
you need, and when? Who gets the data? What have you done
in the past? From these conversations an image emerges as
to the shape and scope of the database.
We’ve taken a good look; now it’s
time to paint a portrait of your database. Using Dr. Codd’s
relational model, we diagram your data and its interrelationships
in a series of boxes with connecting lines. After receiving
confirmation that the model accurately describes your needs,
GopherData proceeds to development.
Now it’s time to create the tables and
hook them together. These tables are where the data collected
by your organization is pooled and stored. They also serve
as the foundation for your forms and reports, which are created
next. This process requires close collaboration between the
developer and the user.
Along the way, we conduct rigorous testing to
ensure the accuracy of results, and to ensure that the user
interface accords with expectations.
Training can occur either concurrently with
development, or as a formal next step via sit-down instruction.
GopherData has extensive experience in user training, and
is available to tailor sessions to your preferences.
Subsequent to final deployment and training,
GopherData remains available for ad hoc requests – from
functionality extensions to further training.
|
