\"Business Rules In Data\" Based on your experience, identify one example of a b
ID: 673088 • Letter: #
Question
"Business Rules In Data"
Based on your experience, identify one example of a business function/operation. Explain the business function /operation in the context of business data models. 2. Identify the business rules associated with your selected business function/operation. Explain the manner in which such business rules would impact the design of a database. 3. Explain atleast one way in which the business function or operation would be affected if these business rules were not adhered to in the development of the database.
Explanation / Answer
2)
A business rule is a statement that defines or constrains some aspect of the business. It is intended to assert business structure or to control or influence the behavior of the business. The business rules that concern the project are atomic -- that is, they cannot be broken down further.
For our purposes, this may be viewed from two perspectives. From the business ('Zachman row-2') perspective, it pertains to any of the constraints that apply to the behavior of people in the enterprise, from restrictions on smoking to procedures for filling out a purchase order. From the information system ('Zachman row-3') perspective, it pertains to the facts that are recorded as data and constraints on changes to the values of those facts. That is, the concern is what data may, or may not, be recorded in the information system.
The GUIDE Business Rules Project decided to address the information system perspective first, and this paper reflects that orientation. Accordingly, a business rule expresses specific constraints on the creation, updating, and removal of persistent data in an information system. For example, the record of a purchase order may not be entered if the customer's credit rating is not adequate.
While this may appear closely related to the business ('row two') rule that says that "we will not sell anything to a customer with a bad credit rating," the perspectives are subtly different. Adopting this constrained scope provided three practical benefits to the project:
First, the focus on the information system perspective has made the problem tractable. It has been possible to understand and model business rules as constraints on data. It will be much more difficult to make equally clear assertions about business rules as they are practiced in the business.
Secondly, the project has intentionally not dealt with entire categories of issues pertaining to the behavior of people in an organization. These include:
It is the project team's intention that a follow-on project will address these issues, as well as delving deeper into the issues of inferences and action-influencing assertions.
Finally, by dealing solely with issues of information structure, the project has not had to deal explicitly with events. From the perspective of an information system, an event only manifests itself by virtue of the fact that persistent data have come into existence or been modified. The business rules described here control whether or not such data may be created or changed, and the implications when this occurs.
Categories of Business Rule:
A statement of a business rule falls into one of four categories:
Business rules are gathered in these situations:
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.