The data to be stored are relatively few but with a high complexity of relations between them. Therefore it is mandatory that the design of the data model, including later additions and modifications, be object-oriented. This does not necessarily prejudice the choice of an OO database, provided that the mapping of classes into the relations of a relational DB is straightforward enough to allow conceptual changes, designed in the OO model, to be reflected in the database schema. If necessary, the availability of Java on the browser can be taken for granted. HTML interface automatic Redesign of the data model must not normally involve a redesign of the HTML interface that accesses the data.
Minor adaptations are acceptable.
Access to existing Oracle database Some attributes of the objects involved are already stored in existing Oracle databases. They should not be duplicated but accessed from these DBs. This does not necessarily require but at least strongly favour a solution where the objects are themselves stored in an Oracle database. Access via Java programs possible Java programs shall be able to work on the objects stored in the database. The data to be stored consists of few thousand objects belonging into few tens of classes.