NUR AMYZAH NAFISAH BINTI ZAIDI

62213219449

AC10

QUIZ 1 - AIS

1. Briefly explain the concept of duality as denoted by give and receive events in an REA
diagram.
Duality means an economic transaction that consists of two agents, one is internal
(Employee) and other external (Customer), each exchange resource with another resource.
Duality consists of dual events which is first one is give event and another one is receive
event. Both are opposite to each other. One is outflow and another one is inflow. Duality
consists only economic events not support events. Economic exchange does not require
duality events occur simultaneously.

REA sematic features are derived from the elements of an economic transaction. The
rationale behind an economic transaction is that two agents each give other a resources in
exchange for another resource. In actual, the exchange is pair of economic events, which is
expressed via the duality association on the REA diagram. In other words, each economic
events is mirrored by associated economic event in the opposite direction. In REA diagram
expands the basic REA model to illustrate the connection between this dual events: the given
event and receive event. From the perspective of the organization function being modelled,
the give half of the exchange decrease the economic resources, as representative by outflow
association. The receive half of exchange increase the economic resources, represented by
an inflow association

2. Unlike the inflows/outflows of inventories and other resources, employee time is not
displayed in an REA diagram, despite the fact that it is also considered as a resource to an
organisation. Briefly explain and give example.
Employee time is a resource, but cannot be shown in REA diagram as it has no
relationship with the other entities or resources in the REA diagram. It can be considered as
an intangible economic resource. Also no one can show the flow of time in the diagram and it
cannot be stored. This is not required in database and hence not showing that in REA
 diagram. Also, a resource in REA is used with the trading partners in economic exchanges and
are either decreased or increased by exchange.
The time worked event must be linked to a particular employee and supervisor for a
(1,1) cardinality. However, each agent can be linked to zero or many time worked events.
The zero minimum allows for inclusion of a new employee or supervisor who has not yet
been involved in a time recording. A similar situation exists with the disburse cash event. (We
regard each individual paycheck as a separate cash disbursement.) The assumption is made
that employees record time worked on a daily basis. Time worked is therefore linked to a
maximum of one cash disbursement, since employees aren’t paid for half a day on one
paycheck and the other half of the day on another check. For each cash disbursement,
however, there are one-to-many time worked events. In other words, a paycheck could pay
an employee for anywhere from one day’s work to many. The employee time entity requires
some explanation. The resource being acquired by the time worked event is the use of an
employee’s skills and knowledge for a particular period of time. Time is different from
inventory and other assets in that it cannot be stored. There are only a few relevant
attributes about employee time such as hours worked and how the time was used. The time
worked and disburse cash events capture all the information about employee time that it is
practical to collect and monitor. Consequently, the employee time resource entity is almost
never implemented in an actual database, which is why it is depicted with dotted lines.

3. Why are denormalized tables used in data warehouses?

Because of the vast size of a data warehouse, performance inefficiency can be
devastating. a three-way join between many thousands table in a large data warehouse may
take an unacceptably long time to complete and may be unnecessary. in the data warehouse
model, the relationship among attributes does not change. because historical data are static
in nature, nothing is gained by constructing normalized tables with dynamic links.

This data warehousing strategy is used to enhance the functionality of a database

infrastructure. Denormalization calls redundant data to a normalized data warehouse to
minimize the running time of specific database queries that unite data from many tables into
one.
 In fact, the interpretation of denormalization depends on normalization, which is
characterized as the act of arranging a database into tables by removing repetitions to
implement a given use case. Denormalized database should never be mistaken for a
database which was never normalized.

4. Briefly explain why data warehouse needs to be separated from the operational database
Operational database needs to be separate from data warehouse for achieving high
performance of both systems. Operational database has huge amount of stored data which
capabilities of indexing and hashing using primary key and also optimizing pre recorded
queries, on other hand data warehouse queries are very complex and stores large group of
data at summarized level and may require organized data, data access and specialized
implementation methods based on multi dimensional views.
Decision support system is very important in ERP it requires stored historical data
and operational database does not store historical data, it only store large amount of raw
data which is not organized as of data warehouse. Finally separation of operational data base
from data warehouse is based on different structures, contents of these databases and use
of data in both systems.
Since, both systems data warehouse and operational databases provide different
functionalities and different kinds of data therefore keeping these two systems separate is
recommended.

5. An organisation is rationally expected to expand its operation over a period of time. In this
situation, there are several important issues related to its system scalability that should be
considered so that business growth will not be disrupted. Explain.
The creation of unnecessary roles. The fundamental objectives of RBAC is to provide
access in accordance with an organization's needs, which derive from defined tasks rather
than an individual's wants. Managers in ERP environments, however, have significant
discretion in creating new roles for individuals. This may be done for employees who needs
access to resources for special and/or one time projects.
The rules of least access. Access privileges (permissions) should be granted on a
need-to-know basis but users tend to accumulate unneeded permissions over time. The
managers fail to exercise adequate care in assignment permissions and tend to be better at
issuing privileges than removing them. The policies should require due diligence in assigning
permissions.
 Monitoring role creation and permission- granting activities. Effective RBAC
management demands procedures that monitoring role creation and permission granting to
ensure compliance with internal control objectives. Role-based governance systems allow
managers to view roles, permissions and individual assignments; identify violations; and
verify that changes have been implemented successfully.
Contingencies planning. The implementation of an ERP creates an environment with
a single point of failure, which places the organization at risk from equipment. Organizations
need a contingency plan than can be invoked quickly in the event of a disaster.