Introduction

A few basic design choices and ideas underline the scope, architecture and functionality of the software:

• It is limited in scope
• It divide the archaeological record into separate modules
• When possible, properties of records are limited to closed-ended lists of possible values
• A simple dependency system was devised to allow dependency of some properties on others

In the next sections we'll briefly consider each of these.