Every business object has characteristics that describe it. Customers, employees, students, and suppliers, for example, will have names, addresses, phone numbers, and so on. Products will have names, prices, descriptions, and so on. Appointments will have times, dates, and so on. In fact, if you cannot identify two or more characteristics of a business object, there is
a strong possibility it is not a business object at all. Below is a list of sample business objects and their characteristics, appropriate to a wide range of databases.
The characteristics of business objects are converted into the attributes of entities in the logical design stage. Attributes, in turn, are ultimately translated into table fields with SQL.
Relationships between business objects
Business objects relate to each other in some form or fashion. Customers place orders, employees take orders, orders are for products, products come from suppliers.
Relationships between objects can be complex, so establishing relationships at this point in the design process is quite preliminary. It is important to note, however, what objects are generally related, especially in the existing database(s).
As part of Requirements Analysis, database designers list and document
the business objects stored in the clients existing database(s), along with their characteristics and a preliminary idea of how they are related. The next lesson describes business rules.
Identify Business Objects - Exercise
Before moving on to the next lesson, click the exercise link below to test your skills in identifying business objects and their characteristics. Identify Business Objects - Exercise
attribute: A characteristic of an entity; data that identifies or describes an entity. Usually represented as a column in a table, attributes store data values.