Skip to Navigation   |   Skip to Main Content

Amon Consulting

PO Box 952, Nelson, New Zealand

www.amon.co.nz   info@amon.co.nz

Please Note:

This web site makes extensive use of CSS for styling . If you can read this message, it is probably because your browser does not properly support CSS or you have disabled this yourself.

Although the content looks better with
CSS 'turned on', this site is perfectly readable either way.

One oddity you may notice (with CSS turned off) is the display of text that is intended for PRINTERS ONLY

Revelation Data Migration
Revelation application prototyping, redevelopment and data migration

logo: ExportR

Amon Consulting provides a migration service from Revelation applications to most other common platforms

Our customers can request the latest documentation and source code at any time and are therefore able to assess software standards and software development progress whenever required

This will also allow customers to take back control of ongoing development at any stage.

Since 1998 we have migrated over 200 Revelation and OpenInsight applications

Our involvement has ranged from providing our ExportR software to users for their own use in-house through to full application redevelopment incorporating new functionality

Procedure

Our usual sequence of Revelation application redevelopment involves the following steps:

  1. Extraction of all data into CSV or MS Access format so that relevant tables, fields and field data types can be determined
  2. Production of an application Entity Relationship Diagram so that active application tables and relationships between table data can be determined
    The diagram allows users to assist in confirming assumptions, clarifying understanding, removing ambiguity and standardizing terminology
  3. Creating a glossary of terminology may be necessary so that definitions for application terminology can be agreed upon.
    This is recommended, more so if this is technical application
    Each glossary entry would show the term used in the current system and, if it differs, the term to be used in the new application
  4. A data model may also be developed at this time to show all table attributes (fields)
  5. Generation of critical application reports, within an MS Access prototype application, to ensure that the data extracted can be used to reproduce the same information as that output in the live system i.e. stock levels, price books, sales analysis, time tables etc.
  6. A comprehensive cross-reference table may be generated using our specialised software to show which tables, fields, programs, reports, menu items and windows (screens) are in use and their navigation paths
    Time can be saved by eliminating functions and items which have become redundant
    If the application code is unavailable then the information generated by this process is limited but active menu items will still be able to be identified
  7. Further prototyping (input windows, further reporting etc) can then be developed in the MS Access environment as required
  8. The decision for the final platform can then made. Whether this will be a continuation of the MS Access application, limited redevelopment (eg. Reporting only), migration to an existing application, complete redevelopment or a hybrid solution
    At this point the customer may decide to continue development without our assistance, either using in-house resources, out-sourcing to a local software house or passing control to a third-party software provider
    We will continue to assist with the conversion and development process as required, either on a quote basis or hourly rate
  9. Where our assistance is required to redevelop the final application we can either do the work in-house or source suitable developers locally
    Where we use outside developers, we will continue to take responsibility for the final product and ensure it meets our standards of ease of use, functionality, adherence to standards and documentation
    Functionality will be agreed with the customer before the work begins with quotes given for each stage of development
    We do not support the 'big bang scenario' of software development
    We prefer that the users are regularly updated with the software as it is developed so that there are no surprises
    This also allows for regular user feedback to ensure that development is on the right track

This page was last updated on 8 June 2008
Te ra ake tenei wharangi, i tera ikei runga te 8 o Pipiri te tau 2008 te ra