A Quick Review of Analysis Stages of the Systems Development Life Cycle Planning Analysis Design Construction.

Slides:



Advertisements
Similar presentations
Database Design Using the REA Data Model
Advertisements

Business Processes, Data Modeling and Information Systems
Chapter 3 Data Modeling Copyright © 2014 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent.
ERD diagram Data Design - Mr. Ahmad Al-Ghoul
Copyright © 2015 Pearson Education, Inc. Database Design Chapters 17 and
Systems Development Life Cycle
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 5-1 Accounting Information Systems 9 th Edition Marshall.
FIS 431/631 Financial Information Systems: Analysis and Design REA Modeling Joe Callaghan Oakland University Department of Accounting & Finance.
Criticisms of the Traditional Accounting System Architecture and a Solution Slides 2.
Figure 1-A COOL:Gen™ Implements Entire Systems Development Life Cycle PLANNING ANALYSIS DESIGN - External DESIGN - Internal (Technological Environment.
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart1 of 121 C HAPTER 16 Implementing an REA Model in a Relational.
PROCESS MODELING Transform Description. A model is a representation of reality. Just as a picture is worth a thousand words, most models are pictorial.
Department of Accounting & Finance
Technology Review-II Professor Martin Professor Xiong CSUS
The Systems Development Life Cycle and Information Engineering: An Introduction Slides 3.
The Relational Database Model:
FIS 431/631 Financial Information Systems: Analysis and Design Process Modeling Joe Callaghan Oakland University Department of Accounting & Finance.
1 The Accounting REA Model as an Information Engineering Interaction Model Slides 5.
FIS 431/631 Financial Information Systems: Analysis and Design ERD & Normalization Joe Callaghan Oakland University Department of Accounting & Finance.
The Islamic University of Gaza
System Analysis and Design
Chapter 3: Data Modeling
Database Design Using the REA Data Model
Hall, Accounting Information Systems, 7e ©2011 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly.
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart1 of 138 C HAPTER 15 Database Design Using the REA Data Model.
Entity-Relationship Design
Practical tips for creating entity relationship diagrams (ERDs) Chitu Okoli Associate Professor in Business Technology Management John Molson School of.
Modeling Systems Requirements: Events and Things.
1. 2 Data Modeling 3 Process of creating a logical representation of the structure of the database The most important task in database development E-R.
Database Design Using the REA Data Model
Systems Analysis and Design in a Changing World, Fifth Edition
Chapter 17 Database Design Using the REA Data Model Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 17-1.
Chapter 17 Database Design Using the REA Data Model Copyright © 2012 Pearson Education 17-1.
ACCOUNTING TRANSACTION CYCLE
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart1 of 138 C HAPTER 15 Database Design Using the REA Data Model.
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
DATABASEMODELSDATABASEMODELS  A database model ◦ defines the logical design of data. ◦ Describes the relationships between different parts of data.
Clients (and the interface level) Application Server (and the application level) Database Server (and the Database level)
Entity Relationship Diagrams (ERDs). Entity Relationship Diagram (ERD) documentation technique to represent relationship between entities in system. Think.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Rob and Coronel Adapted for INFS-3200.
Database Design Principles – Lecture 3
Implementing an REA Model in a Relational Database
1 Entity-Relationship Diagram. 2 Components of ERD: –Entity –Relationship –Cardinality –Attributes.
1 Systems Analysis & Design Business Modeling IS 431: Lecture 5B CSUN Information Systems
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
5 Systems Analysis and Design in a Changing World, Fifth Edition.
IT 21103/41103 System Analysis & Design. Chapter 04 Data Modeling.
IFS310: Module 6 3/1/2007 Data Modeling and Entity-Relationship Diagrams.
Information Access Mgt09/12/971 Entity-Relationship Design Information Level Design.
Lecture 91 Introduction to Data Analysis and Logic Specification Objectives l Draw an entity-relationship diagram, and explain the types of entity relationships.
EntityRelationshipDiagrams. Entity Relationship Models The E-R (entity-relationship) data model views the real world as a set of basic objects (entities)
Detailed Data Modeling. Outline Data Modeling Modeling Constructs –Entities –Relationships –Cardinality Model Basic Rules Advanced Rules Prototyping Process.
2 1 Database Systems: Design, Implementation, & Management, 7 th Edition, Rob & Coronel Data Models Why data models are important About the basic data-modeling.
1 Information System Analysis Topic-3. 2 Entity Relationship Diagram \ Definition An entity-relationship (ER) diagram is a specialized graphic that illustrates.
IS 4420 Database Fundamentals Chapter 3: Modeling Data in the Organization Leon Chen.
MODELING BUSINESS PROCESSES.  Every organization has three basic business processes.  Acquisition/payment Business Process. Organizations can acquire.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
Database Design Chapters 17 and 18.
Database Development Lifecycle
Introduction to Transaction Processing
Data Dictionaries ER Diagram.
Accounting Information Systems 9th Edition
Database Design Using the REA Data Model
Systems Analysis & Design
Database Design Chapters 17 and 18.
Introduction to FIS 318/618: Financial Systems & Databases
Entity-Relationship Design
Presentation transcript:

A Quick Review of Analysis

Stages of the Systems Development Life Cycle Planning Analysis Design Construction

Modeling A model is a representation of reality Systems analysts try to understand a business by drawing “pictures” or models of the business and its workings. Three primary types of models: (1) activity models, (2) data models, and (3) interaction models

Business Modeling In Planning and Analysis: An Overview of the MIS Approach Data Model Activity Models Interaction Models Systems Design ERD FHD, PM PLD, ELC

Analysis Tasks with REAL Interaction Modeling Systems Design Activity Analysis Interaction Analysis 1 Interaction Analysis 2 PLD, ELC FHD, PM REA Data Analysis ERD

Types of Models Activity models: Records the activities of interest to the business (i.e., the things the business does or should do) Involves decomposition of business processes from the highest level (AMP of Resources, Conversion Processes, MSC Processes) to the lowest (elementary processes) Also involves the specification of process dependency events, to refine decomposition of the processes

HEART OF ORGANIZATION Conversio n Processes Customers Finished Goods and Services to Customers MSC Processes Supply goods and services Receive payment Activity Models: Template for Decomposition of Business Processes (IPSO) Suppliers AMP Processes Input Resources to the Organization Request input resources Pay for input resources Adds value RBMS Source: Hollander, Denna & Cherrington (2000), adapted

Business Processes AMP Processes Human Resources Financial Resources Supplies Inventories Property, Plant and Equipment Conversion Processes Operations Varies widely depending upon the industry MSC Processes Marketing Sales Collection and Credit

Business Process: Simple MS Process and Events Ship goods Take customer order

Figure 6 FHD: Partial Business Function Decomposition

Types of Models Interaction models: Define how things the business does (activities/events) affect things of interest to the business (data) Faculty at OU have combined the IE notation of an interaction model with the accounting REAL model Formal interaction modeling facilitates the transition from systems analysis to systems design.

REAL Model of A Business Event: The Event and Surrounding RALs What happened? - event When did it happen?- sequence Who was involved?-agents What resources were involved? – resource(s) Where did it occur? – loc. Event Internal Agent Resource External Agent Location Source: Hollander, Denna & Cherrington, 1996

REAL modeling is an aid in analyzing an organization and its activities (helps develop activity models by identifying lowest level of decomposition) Helps decide what data to collect (helps develop data models) Enhances your ability to evaluate business processes

REA Template With Two Events Resource Internal Agent External Agent External Agent Location Event 1: Take customer order Internal Agent Resource Event 2: Ship goods Event 2: Ship goods Location External Agent External Agent

Business Rules Narrative descriptions of policies, procedures, or principles in an organization Simple Examples: –Each purchase order must have only one vendor –Each vendor may have one or more purchase orders

Relationships Data modeling term that indicates an association between tables: How the things of significance are related (A FK must match to an existing PK, or else be NULL) This controlled redundancy allows linking of tables (hence “relational”) Entity-Relationship Diagram (ERD): A data model (at the conceptual level) that shows the relationships enforcing business rules between entities (tables) in a database environment

Connectivity or Cardinality One-to-One (PK ---> PK) - Generally indicates that your data model has two entity types that can be collapsed into one One-to-Many (PK ---> FK) - Most common Many-to-Many (FK ---> FK) - Not enforceable by RDMS; generally indicates that a modeling error has occurred - this type of relationship means that your model is missing an entity type

Cardinality of Relationships Mandatory - an instance of an entity in one table does require a associated record in another table (as defined by a relationship) Optional - an instance of an entity in one table does not require a associated record in a another table (as defined by a relationship)

Validate The REAL Model With Business Persons Those who understand the details and objectives of the business process and events being modeled should perform the validation. Validation sessions should result in either the confirmation of the model’s accuracy or modification of the model.

Events Most events are easy to identify because the business records data on forms or files. Events are characterized by the fact that they happen or have duration –For activity and REAL models, they are characterized by at least a verb and a noun, but could have an adjective, take customer order, deliver customer order, pay supplier –For data models (converting REAL to ERD), they are characterized by a noun, e.g., Order header, Order detail, Sales header, Sales detail, Cash receipt

Surrounding RALS RESOURCES Entity types that describe tangible things. EQUIPMENT, INVENTORY, CASH, MACHINE, MATERIAL, PART, PRODUCT, VEHICLE, but they can also be Informational Resources, e.g., PRODUCT CATALOG

Surrounding RALs AGENTS Entity types that describe roles played in a system. They usually represent people or organizations. APPLICANT, BORROWER, CLIENT, CREDITOR, EMPLOYEE, EMPLOYER, INSTRUCTOR, MANAGER, SALESPERSON, VENDOR

Surrounding RALs LOCATIONS Entity types that describe locations BRANCH, BUILDING, CAMPUS, CITY, COUNTRY, COUNTY, SALES REGION, WAREHOUSE, STORE, FRANCHISEE

A REAL Interaction Model for MSC Function Sell Goods Customer Inventory Salesperson Department Receive Payment Cashier Cash Store

Types of Models Data model: One type is the ERD that depicts data (entities, attributes) and the relationships enforcing business rules between entities. The primary goal is to accurately portray the fundamental elements of the business information system. The data model is implemented as a database in a developed system (central to the IS)

ERD with Normalization