ABN: 87 256 031 938   

 GI Busines Data Solutions - We can assist with planning your Access Database solutions and data management systems Free Access Database planning guide to assist in your database developemnt

Database development guide - database planning - Melbourne Sydney Brisbane Australia

Database development guide - database planning guide - Melbourne Sydney Brisbane Australia

Home  |   About Us  |   Custom Software  |   Redevelopment  |   Data Recovery  |   Fee Schedule  |   Downloads  |   Request Info


Database Planning and Development Guide

Your business data can be a wealth of information, and provide valuable insight into the way your business is operating. However, this is only true when you are able to properly collect, collate, interrogate and report on the data that you capture.

Experts say that, 'To properly manage your business you must first manage your data. Any Data Management System that  you implement must take into account the specific and unique needs of your business.'

This is why the planning phase is so important, and is something that you should seriously consider before embarking on any form of implementation. To assist you in identifying the key factors that you should consider during the planning process we have put together the following list of what we consider are the key aspects of any good database.

 
1.   Purpose
  Why do you need a database?
  What information will you need to store, process and retrieve?
  What are the functional requirements, including outputs?
   

2.   User Requirements

  Who, and how many will use the database?
  Will there be common categories into which users can be grouped? What are they?
  What functions do the user groups now perform that can be incorporated into the database?
  What user groups will need to:- add new records, edit existing records, add new data to existing records, or view only.
  What new functions could be incorporated in the database to enhance productivity?
   
3.   Database definition
  Will the database be compatible with your current systems?
  What databases do you need? e.g. Users, Events, Locations, Costs
  What are the characteristics of each database?
  How should the databases be related to each other?
  How do you want them to interact?
   
4.   Security
  Will different user groups require differing access levels? If so, what are they?
  How sensitive is the data?
  Does the underlying program code need to be protected? Who are the possible sources of threat and how sophisticated is that threat?
  Will audit trails be required to validate data integrity?
   
5.   User Interaction
  In what format do you want the database access presented? e.g. Corporate style
  What are the processes that the users are required to perform?
  Are there limitations as to how users may need to access or display data?
  Will users access the data via the exiting network?
  Are emails messages to be generated in response to the addition or change of data? How is this flow to occur?
   
6.   Training & Implementation
  Will training be required? Can training be minimised by incorporating an intuitive user interface?
  Have relevant policies and procedures been developed?
  How are users going to receive training on using the database?
  What user documentation is required? How will it be distributed?
  Will a parallel "trial system" enable users to become familiar with it before "going live"?
  Are users systems compatible with browser and email requirements?
   
7.   Timing & Budget
  When does the database need to be fully operational?
  What are the budgetary limitations?
  Can costs be apportioned across user groups?
  Who is going to manage the implementation and operation of the database?
  What services need to be included within the budget? How is this flow to occur?
 

Back to Top

Copyright 2004. - www.galleryimage.com.au - All Rights Reserved .