Chapter 5 UNDERSTANDING AND DESIGNING ACCOUNTING DATA.

Slides:



Advertisements
Similar presentations
BUSINESS DRIVEN TECHNOLOGY Plug-In T4 Designing Database Applications.
Advertisements

Chapter 3 Data Modeling Copyright © 2014 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent.
Chapter 6 UNDERSTANDING AND DESIGNING QUERIES AND REPORTS.
Copyright © 2015 Pearson Education, Inc. Database Design Chapters 17 and
Accounting System Design
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 5-1 Accounting Information Systems 9 th Edition Marshall.
Chapter 7 UNDERSTANDING AND DESIGNING FORMS. Input Forms: Content and Organization Need for forms Event analysis and forms Relationship between input.
Databases and Processing Modes. Fundamental Data Storage Concepts and Definitions What is an entity? An entity is something about which information is.
Accounting Databases Chapter 2 The Crossroads of Accounting & IT
Database Design Chapter 3.
1 SYSTEMS INVESTIGATION Pertemuan 3 s.d 6 Matakuliah: A0554/Analisa dan Perancangan Sistem Informasi Akuntansi Tahun: 2006.
Database Design Chapter 2. Goal of all Information Systems  To add value –Reduce costs –Increase sales or revenue –Provide a competitive advantage.
1 SYSTEMS DESIGN Pertemuan 13 s.d 20 Matakuliah: A0554/Analisa dan Perancangan Sistem Informasi Akuntansi Tahun: 2006.
Chapter 3: Data Modeling
Implementing an REA Model in a Relational Database
Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 18-1.
Chapter 9 THE ACQUISITION CYCLE— PURCHASING AND RECEIVING
Chapter 9 THE ACQUISITION CYCLE— PURCHASING AND RECEIVING.
Chapter 4 IDENTIFYING RISKS AND CONTROLS IN BUSINESS PROCESSES.
Computer Science & Engineering 2111 Introduction to Database Management Systems Relationships and Database Creation 1 CSE 2111 Introduction to Database.
Page 1 ISMT E-120 Introduction to Microsoft Access & Relational Databases The Influence of Software and Hardware Technologies on Business Productivity.
Introduction to Databases
LOGO Chapter 5 UNDERSTANDING AND DESIGNING ACCOUNTING DATA King Saud University Noura Al.Madi 1.
Databases & Data Warehouses Chapter 3 Database Processing.
Page 1 ISMT E-120 Desktop Applications for Managers Introduction to Microsoft Access.
PHASE 3: SYSTEMS DESIGN Chapter 7 Data Design.
With Microsoft Office 2007 Intermediate© 2008 Pearson Prentice Hall1 PowerPoint Presentation to Accompany GO! with Microsoft ® Office 2007 Intermediate.
With Microsoft Access 2007 Volume 1© 2008 Pearson Prentice Hall1 PowerPoint Presentation to Accompany GO! with Microsoft ® Access 2007 Volume 1 Chapter.
DAY 15: ACCESS CHAPTER 2 Larry Reaves October 7,
1 Accounting Information Systems: A Business Process Approach Chapter Five: Understanding and Designing Accounting Data.
Introduction to Accounting Information Systems
Chapter 1 Overview of Database Concepts Oracle 10g: SQL
1 Chapter 1 Overview of Database Concepts. 2 Chapter Objectives Identify the purpose of a database management system (DBMS) Distinguish a field from a.
The REA Model. The REA model provides structure for developing an accounting database It helps to identify It helps to The REA Model.
Accounting Information Systems 9th Edition
Microsoft Access 2003 Define some key Access terminology: Field – A single characteristic or attribute of a person, place, object, event, or idea. Record.
Lecture 2 An Overview of Relational Database IST 318 – DB Admin.
MS Access: Creating Relational Databases Instructor: Vicki Weidler Assistant: Joaquin Obieta.
© 2008 The McGraw-Hill Companies, Inc. All rights reserved. ACCESS 2007 M I C R O S O F T ® THE PROFESSIONAL APPROACH S E R I E S Lesson 9 – Building Links,
Acct 316 Acct 316 Acct 316 Data Modeling and Database Design 5 UAA – ACCT 316 Accounting Information Systems Dr. Fred Barbee Chapter.
Implementing an REA Model in a Relational Database
Access Chapter 2: Relational Database Objectives Design data Create tables Understand table relationships Understand data types, key, & field properties.
1 Relational Databases and SQL. Learning Objectives Understand techniques to model complex accounting phenomena in an E-R diagram Develop E-R diagrams.
Chapter 1Introduction to Oracle9i: SQL1 Chapter 1 Overview of Database Concepts.
CIS 210 Systems Analysis and Development Week 6 Part II Designing Databases,
Chapter 5 Flowcharting Copyright © 2010 by The McGraw-Hill Companies, Inc. All rights reserved.McGraw-Hill/Irwin.
Implementing an REA Model in a Relational Database
Enhancing Forms with OLE Fields, Hyperlinks, and Subforms – Project 5.
Exploring Microsoft Access Chapter 6 Many-to-Many Relationships: A More Complex System.
Introduction to Database using Microsoft Access 2013 Part 7 November 19, 2014.
INFORMATION TECHNOLOGY DATABASE MANAGEMENT. Adding a new field 1Right click the table name and select design view 2Type the field information at the end.
Description and exemplification of entity-relationship modelling.
Jozef Kuper.  Describe a Database  Entities  Atributes  Relationships.
Relational Theory and Design
Lesson 2: Designing a Database and Creating Tables.
1 CHƯƠNG 4 Creating Relational Databases Understanding Table Relationships Example: This database tracks customers and their orders in two separate.
BSA206 Database Management Systems Lecture 2: Introduction to Oracle / Overview of Database Concepts.
Database Relationships Objective 5.01 Understand database tables used in business.
Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 18-1.
Database Planning Database Design Normalization.
XP Chapter 1 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 1 Level 2 Objectives: Understanding and Creating Table.
Chapter 5 UNDERSTANDING AND DESIGNING ACCOUNTING DATA
Implementing an REA Model in a Relational Database
Implementing an REA Model in a Relational Database
CIS 155 Table Relationship
Implementing an REA Model in a Relational Database
Accounting System Design
Accounting System Design
Database Design Chapter 7.
Presentation transcript:

Chapter 5 UNDERSTANDING AND DESIGNING ACCOUNTING DATA

Identifying and Documenting Files Transaction files: Used to record information about events in a business process

Identifying and Documenting Files Transaction files: Attributes include: Transaction date Agents associated with transaction Description of products/services associated with event

Identifying and Documenting Files Master files: Store reference data Store summary data

Identifying and Documenting Files Events and transaction files: First, identify the events in the business process Then, identify the need for transaction files in the AIS

Documenting Transaction Files UML class diagram: Shows relationships between transaction and master files Each box represents a file Connecting lines between files indicate file relationships

Documenting Transaction Files UML class diagram: Can be used to document: Tables in an AIS Relationships between tables Attributes of tables

Documenting Transaction Files Guidelines for identifying need for transaction tables: 1: Determine the events in the process 2: Exclude events that do not need to be recorded in the computer system

Documenting Transaction Files Guidelines for identifying need for transaction tables: 3: Exclude query and reporting events because they involve using data that have already been recorded in the AIS 4: Exclude maintenance events

Documenting Transaction Files Events and master tables: Typical master tables: Products/services - master tables Describe products/services offered Identify costs and/or prices of products/services Agents - master tables describe External agents Internal agents

Documenting Transaction Files Events and master tables: Typical master tables Cash - master file describes where cash is stored General ledger master file - needed if general ledger system is Automated and Integrated with the revenue or acquisition cycle

Documenting Transaction Files Events and master tables: Generally, master tables are used to store relatively permanent data about an entity

Documenting Transaction Files Benefits of master tables: Save data entry time Save storage space Simplify making changes to data Simplify deleting transaction records

Attributes and Relationships 3 important concepts Primary keys Linking attributes (foreign keys) Relationship cardinalities

Attributes and Relationships Primary key: Attribute(s) that uniquely identifies a record in a table

Attributes and Relationships Foreign key: A field in a table that is the primary key in some other table Used to link one table to another Link event records to master records Link two events that occur in a sequence

Attributes and Relationships Cardinality of the relationship: (covered in the text) One-to-one relationships (1,1) - not nearly as common as one-to-many relationships One-to-many relationships (1,m) - common in accounting systems Many-to-many relationships (m,m) - can be converted into two one-to-many relationships by adding a “junction table”

Attributes and Relationships Cardinality of the relationship: Important in designing a database Represents how many occurrences of one type of entity are associated with another type of entity

Attributes and Relationships Significance of concepts for database applications: Implementing documents and reports

Attributes and Relationships Significance of concepts for database applications: Implementing input forms Input forms are used to make data entry more accurate/efficient Form designs rely on primary and foreign keys and relationships between tables

Attributes and Relationships Significance of concepts for database applications: Controlling AIS data – referential integrity For one-to-many relationships Can specify if want referential integrity enforced on relationship Control most effective with two other controls: Segregation of duties and Access controls

Designing Data with a UML Class Diagram Developing a data design using a UML class diagram: Four basic steps Step 1: Place the required transaction tables (files) on the UML class diagram. Identify events in a business process. Decide which events will need transaction tables. Start the UML class diagram by showing a box for each event requiring transaction tables.

Designing Data with a UML Class Diagram Developing a data design using a UML class diagram: Four basic steps Step 2: Place required master tables (files) on UML class diagram For each event on the diagram (from Step 1), determine related goods, services, or agent entities Determine which identified entities require master tables

Designing Data with a UML Class Diagram Developing a data design using a UML class diagram: Four basic steps Step 2 (continued): Consider using master tables to track location of cash and effect of events on account balances in the general ledger Add required master tables to appropriate side of the UML class diagram

Designing Data with a UML Class Diagram Developing a data design using a UML class diagram: Four basic steps Step 3: Determine required relationship between tables For each connecting lines, determine cardinality of the relationship between tables

Designing Data with a UML Class Diagram Developing a data design using a UML class diagram: Four basic steps Step 3 (continued): Write cardinalities next to line between entities If there are any many-to- many relationships, convert them to one-to- many relationships by adding junction table

Designing Data with a UML Class Diagram Developing a data design using a UML class diagram: Four basic steps Step 4: Determine required attributes by: Assigning a primary key to each tables Linking related tables by adding a foreign key to one of the pair in the relationship Linkage depends on cardinality of the relationship

Designing Data with a UML Class Diagram Additional data design implementation issues: Suggestions One master table instead of two One event table instead of two Option A: Two records in two tables Option B: One record in one table Eliminate redundant relationships Add relationships not involving event records

Designing Data with a UML Class Diagram Communicating the data design: Guidelines in preparing documentation Be consistent in naming entities Name boxes so can easily correlate UML diagram with preceding documentation Help reader understand how each part of the documentation relates to other parts

Designing Data with a UML Class Diagram Communicating the data design: Guidelines in preparing documentation - Proper layout can also enhance readability Start each part on a separate page Clearly label each part Write a brief explanation of the information obtainable by reviewing diagram Use bulleted lists to explain linkages between diagrams Use same style throughout

Keyterms Attributes Cardinality Database Database management system Foreign key Primary key Referential integrity Relational database UML class diagram