Relational databases can look very confusing with the many tables, records, and fields. Databases are used to hold large amounts of data. This means navigating through all that data can be difficult for users. Therefore, we use forms, reports, and navigation to help the end users.
For end users to easily insert (append), update, and delete data forms are required. These will have titles, labels, inputs, and buttons.
For users to easily understand the data there should be the ability to create reports to turn the data into information (information is data organised, so it is readable by humans).
We use Structured Query Language (SQL) to generate reports.
There may be a requirement for some database visual interfaces to have some kind of navigation menu to allow access to the forms and reports.
If you are using Microsoft Access for your course the concept of forms, reports, and navigation is obvious. What might not be obvious are the websites you use that also have the same concepts. Facebook, for example, has all of these. You post content to the site – this is a form that stores information in a database. You look through your feed – this is a report of all content posted by others that relate to you (SQL will be generating this). You click on various parts of the menu to get to your profile (which is recorded in a database) and particular pages or groups (which again are stored in a database) – the menu is your navigation.
The majority of large websites you visit have a database behind them. A common software platform used for this is WordPress. Wordpress is a Content Management System (CMS). This provides forms (web pages), reports (webpages), and navigation (menu on a webpage) for a database.
When designing a visual interface you should consider readability, navigation, logical order, and inclusivity.
Readability involves ensuring the text for the visual interface is easily readable and understandable by the user.
Navigation involves not only a menu but also other links within the visual interface, such as update and delete buttons for example.
Logical order relates to ordering form elements, navigation, or report content in appropriate order. If an update button is at the top of a page before the form elements this would not be logical.
Inclusivity of visual interfaces requires the design to not exclude any minorities based on their race, gender, or disability. If someone has a sight disability the visual interface should ensure it is accessible to them.