Documentation
Home Evaluation Summary for programmers Product limitations Goals of Axisbase Quick start Installation Using the launchpad and opening databases Connecting to a sample database Using building blocks Planning Define the purpose Define the requirements Borrow existing work Determine the architecture Design the data model Design the process model Deploy and maintain the product
Tutorials
building blocks
Performing a mailmerge Bulk e-mailing
Programming
Single-threaded progress indicator in c#
Reference
Database menu items
Import XML Save Copy As Integrity Check Change Password
Database Properties window
Opening the database properties window Record types tab Display types tab Roles and Users tabs Sidebar tab Database ID/Links tab Counters tab
Building blocks
Building blocks window Editing grids and cells Hyperlinks and nesting Data Subset window Data Outsource window List window Window window Report window Bulk Operation window Label Printer window Choosing a data source
Special topics
Expression syntax Browse records Storing building blocks within other building blocks Programming Using custom code in building blocks Using Axisbase as an embedded database Axis1.Util namespace reference Axis1.Data namespace reference (Fishnets) Axis1.Data namespace reference (other) Axis1.Forms namespace reference

Planning overview

These pages contain valuable advice on how to build a business data solution.

Following these steps will help structure your progress from an idea to a working system.

Steps

  1. define the purpose

  2. define the requirements

  3. borrow existing work

  4. determine the architecture - the pieces and how they connect

  5. design the data model - the database structure

  6. design process model - the user interface and other activities

  7. develop the product (use the reference tab for help on development)

  8. deploy and maintain the product

Advice

Advice for vendors and clients: If you are working for a client, consider specifying milestones at the end of each step (even if the steps take less than a day). Each milestone is a point in time when some document or other results (deliverables) will be agreed to by all parties. If you are a software buyer, you should demand these milestones and deliverables as a condition of payment. One of the most frequent causes of runaway expenses in software projects is the failure to demand structured milestones in the contract.

Advice for working for yourself: Treat yourself as a client, and provide the deliverables anyway, even if no one else reads them! That's a great way to keep yourself organized.

(c) 2014-2015 Divergent Labs, Inc.