Professional Documents
Culture Documents
Learning Outcomes
Describe the model of business process Integrate the whole model of business process
3
Bina Nusantara
4
Bina Nusantara
COPYRIGHT 2009 South-Western, a division of Cengage Learning. Cengage Learning and South-Western are trademarks used herein under license
and REA modeling The structure of an REA diagram Create an REA diagram by applying the view modeling steps to a business case Create an entity-wide REA diagram by applying the view integration steps to a business case
in resources.
a source of detailed data in the REA approach
to databases
resources
Customers
Suppliers, vendors Departments, teams
Participates
Economic Resource
Stock Flow
Economic Event
Duality
Participates
Participates
Resource A
Out Flow
Participates
Give Activity
Internal Agent
Duality
Receive Activity
Participates
Resource B
Internal Agent
Inflow
Participates
External Agent
Arrangement of entities
ERDs determined by cardinality and readability READs organized into constellations by class
Sequencing of events
ERDs static READs chronological sequence of business processes
Naming conventions ERDs all nouns READs nouns (Rs and As) and verbs (Es)
in the model
Include at least two economic events (duality) May include support events
Focus on value chain events Do not such invalid events such as:
bookkeeping tasks accounting artifacts, e.g., accounts receivable
Events
Order of Events
Verify Availability
Take Order
Ship Product
Receive Cash
Resources
Events
Agents
Customer Services Clerk
Inventory
Customer
Cash Receive Cash Cash Receipts Clerk
two entities
Represented by the labeled line connecting the entities
Cardinality the degree of association between the entities Describes the number of possible occurrences in one entity that are associated with a single occurrence in a related entity Cardinality reflects the business rules that are in play for a
particular organization.
Sometimes the rules are obvious and are the same for all
organizations. Sometimes the rules differ, e.g., whether inventory items are tracked individually or as quantity on hand.
Respond to Customer
Verify Availability
Customer
Process Order
Inventory
Reserves
Take Order
Sales Representative
Causes
Ships
Shipping Clerk
Reduces
Ship Product
Receives
Duality
Customer
Remits
Increases
Cash
Receive Cash
Processes Remittance
Many-to-Many Associations
Many-to-many (M:M) associations cannot
be directly implemented into relational databases. They require the creation of a new linking table.
This process splits the M:M association into
two 1:M associations. The linking table requires a composite primary key.
Inventory-Verify Link
Verify Availability
Customer
Places Order
Process Order
Inventory
InventoryOrder Link
Take Order
Sales Representative
Causes
Ships
Shipping Clerk
Inventory-Ship Link
Ship Product
Receives
Customer
REA diagrams into a single enterprise-wide model The three steps involved in view integration are:
consolidate the individual models 2. define primary keys, foreign keys, and attributes 3. construct physical database and produce user views
1.
a thorough understanding of the business processes and entities involved in the models. Individual models are consolidated or linked together based on shared entities.
For example, procurement (expenditures) and sales
Verify Availability
Supplier Request
Customer
Receiving Clerk (Employee) Receive Product
Supplier
Shipping Clerk
Cash Disb Clerk (Employee)
Disburse Cash
(Employee)
Ship Product
Payroll Clerk (Employee)
Customer
Worker (Employee)
Cash
Receive Cash
Supervisor (Employee)
Get Time
entity (i.e., each row in the table) Foreign key the primary key embedded in the related table so that the two tables can be linked Attribute a characteristic of the entity to be recorded in the table
by an attribute that is common to both tables in the relation. Assignment of foreign keys: if 1 to 1 (1:1) association, either of the tables primary key may be the foreign key if 1 to many (1:m) association, the primary key on one of the sides is embedded as the foreign key on the other side if many to many (m:m) association, create a separate linking table with a composite primary key
Attributes
Using the customer as an example, these data include:
Financial Customer name Customer address Customer telephone number Amount owed by customer Value of total sales to date Terms of trade offered
Nonfinancial Customer credit rating Damaged goods record On-time payment record Customer volume record EDI access Internet access
relational tables using software. Once the tables have been constructed, some of them must be populated with data.
Resource and Agent tables
before data can be entered. The resulting database should support the information needs of all users.
SQL is used to generate reports, computer screens, and documents
for users.
User-Views
User-View #1
Past Due Accounts Name Amount James $500.00 Henry $100.00
User-View #2
Sales Report
REA Database
primary activities (create value) and support activities (assist performing primary activities). REA provides a model for identifying and differentiating between these activities. Prioritizing Strategy: Focus on primary activities; eliminate or outsource support activities.
Primary Activities
Increasing productivity via elimination of non-value added activities generates excess capacity
same central database reduces multiple data collection, data storage, and maintenance.
accurate information.
leading to better customer service, higher-quality products, and flexible production processes
Continued to session 09
Thank you
39
Bina Nusantara