The goal of each application, regardless if it is an ERP system or just and administrative section of a website, is to facilitate the way users insert a certain number of “datasets” according to their work. Usually this would be described as „we need some type of a system to allow us to enter orders and to keep track of supplies”. However, all designers of such systems are aware of the fact that this is actually not a single object. To ensure proper data structuring, normalization and a variety of additional arguments, such systems usually reach hundreds of objects. As far as Elements treats all objects equally – e.g. each one has a list, an overview (which will be explained later), a data entry and an editing form, there should be a way of “prioritizing” the “main” objects and placing the other where they would not interfere with the work of the user. In the example above, the following objects are concerned:

• Contractor Type – typification of contractors to be able to separate them into customers or vendors later.
• Contractors – the common list of clients and vendors
• Client (Contractor) – there is no need to enter data about a customer for each order (as long as this is not a retailer), so it would be better to place them separately
• Vendor (Contractor) – goods are supplied and supplies should be monitored. Each vendor provides more than one product, and each product can be supplied by more than one vendor
• Order – this is the object from which other objects emerge. Details about the order itself are kept here – client, date, terms, payment options etc
• *Products ordered – an order can include more than one product. Here products are entered with details about volume, prices and vendors.
• Products – we need a taxonomy of products, to be able to choose them within an order
• Product Groups – it is recommended that the products are categorized into groups because they may reach large amounts
• Row from the price list – it describes which vendor, delivers which product and at what price (this object can also be used to keep additional information)
• Sales by customers by months – this is a query, whereby the user looks at sums, by client and by month. In this simple example there are a few main types of objects, which are used in the Elements platform:
• „Main” objects
• Category objects
• Context related objects
• Non-context related objects
• Queries