Chapter 2 Accountants as Business Analysts

Slides:



Advertisements
Similar presentations
Steps of a Design Brief V Design Brief  Problem, identification, and definition Establish a clear idea of what is to be accomplished. Identify.
Advertisements

Database Systems: Design, Implementation, and Management Tenth Edition
Chapter 7 Structuring System Process Requirements
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
Introduction to Control Flow Patterns and BizAgi
Chapter 3 Data Modeling Copyright © 2014 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent.
Systems Documentation Techniques
1 Introduction to modeling Process modelling. 2 Where are we? #TitleDate 1Introduction ORM modeling Relational modeling
Chapter 5 Sales and Collections Business Process
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
SYSTEM ANALYSIS & DESIGN (DCT 2013)
Use Case Diagram © copyright 2001 SNU OOPSLA Lab..
© 2005 Prentice Hall4-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
1-1 Copyright © 2004 by Nelson, a division of Thomson Canada Limited. Introduction: The Role, History, and Direction of Management Accounting 1 PowerPresentation®
Chapter 9 Using Data Flow Diagrams
BPMN An Introduction ISIS. © ILOG, All Rights Reserved 2 Definition of BPMN Business Process Modeling Notation provides:  The capability of defining.
Task analysis 1 © Copyright De Montfort University 1998 All Rights Reserved Task Analysis Preece et al Chapter 7.
Chapter 4.
Copyright © 2015 Pearson Education, Inc. Systems Documentation Techniques Chapter
Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.
Business Plug-In B2 Business Process.
Systems Documentation Techniques
Department of Computer Science 1 CSS 496 Business Process Re-engineering for BS(CS)
Department of Computer Science 1 CSS 496 Business Process Re-engineering for BS(CS)
Copyright © 2016 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.
Chapter 7 Structuring System Process Requirements
Systems Analysis and Design: The Big Picture
Copyright 2002 Prentice-Hall, Inc. Managing the Information Systems Project 3.1 Chapter 3.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, All Rights Reserved Business Plug-In B15 Project Management.
12-1 Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.
© 2014 Cengage Learning. All Rights Reserved. May not be copied, scanned, or duplicated, in whole or in part, except for use as permitted in a license.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Process.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
McGraw-Hill/Irwin © 2006 The McGraw-Hill Companies, Inc. All rights reserved. BUSINESS DRIVEN TECHNOLOGY Business Plug-In B10 Project Management.
BPMN By Hosein Bitaraf Software Engineering. Business Process Model and Notation (BPMN) is a graphical representation for specifying business processes.
Copyright © 2016 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.
Chapter 7 Structuring System Process Requirements
Chapter 7 Using Data Flow Diagrams
Introduction to Operations Management Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written.
Database Systems: Design, Implementation, and Management Ninth Edition
Centro de Estudos e Sistemas Avançados do Recife PMBOK - Chapter 4 Project Integration Management.
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Rob and Coronel Adapted for INFS-3200.
SYSTEMS ANALYSIS AND DESIGN TOOLS DATA FLOW DIAGRAMS.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin Business Plug-In B2 Business Process (on OLC)
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design.
Business process models and its support in Visual Paradigm Zuzana Brťková.
Lecture 6: Test-based Use case & Process Modeling December 7, 2014.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
BPMN.  BPMN will provide businesses with the capability of understanding their internal business procedures in a graphical notation.
Systems Analysis and Design in a Changing World, Fourth Edition
Business Process and Functional Modeling
Information Delivery Manuals: Process Mapping
TECHNOLOGY PLUG-IN T12 BUSINESS PROCESS.
Introduction to Control Flow Patterns and BizAgi
Activity and State Transition Diagram
Systems Analysis and Design 5th Edition Chapter 4. Use Case Analysis
Systems Analysis and Design 5th Edition Chapter 4. Use Case Analysis
SYSTEMS ANALYSIS Chapter-2.
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design 5th Edition Chapter 4. Use Case Analysis
BPMN - Business Process Modeling Notations
Project Management Process Groups
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Chapter 3 Managing the Information Systems Project
Presentation transcript:

Chapter 2 Accountants as Business Analysts Copyright © 2014 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.

Learning Objectives LO#1 Describe the roles of the accounting/finance function in business and why those roles require knowledge of technology and business processes. LO#2 Understand the importance of business process documentation. LO#3 Recognize the value of business models. LO#4 Articulate the characteristics of activity models. LO#5 Understand and apply the building blocks for BPMN (activity) diagrams.

Roles of Accountants in Business LO# 1 Roles of Accountants in Business Stewardship and Reporting Accounting/Finance Operations Business Management Support Regulatory compliance Finance and accounting processes Management information Tax returns Financial close Planning budgeting and forecasting Stakeholder assurance Financial reporting and analysis Performance measurement Investor relations Providing management information Performance management Raising capital and loans People management Risk management – from strategic to operational including fraud risk Board reports Using IT to make finance and accounting processes more efficient and effective Investment appraisal Statutory reporting Cost management Supply chain management

Changing Roles of Accountants in Business LO# 1 Changing Roles of Accountants in Business To prepare for their changing roles accountants must: Understand the business and how it collects summarizes and communicates business information Understand how the business delivers value to its customers Understand the risks that the business faces and the internal controls in place to mitigate those risks Understand how accounting information systems collect summarize and report business process information

LO# 2 Definitions Business Process: a defined sequence of business activities that use resources to transform specific inputs into specific outputs to achieve a business goal. Business Analysis: the process of defining business process requirements and evaluating potential improvements.   Business Model: a simple abstract representation of one or more business processes. Documentation: explains how business processes and business systems work; a tool for information transmission and communication

Importance of Business Process Documentation LO# 2 Importance of Business Process Documentation Documentation includes: Business process models Business rules User manuals training manuals Product specifications Software manuals Schedules Organization charts Strategic plans

Value of Business Models LO# 3 Value of Business Models Graphical representations present information more concisely and clearly than a written description Manage complexity by incorporating only the essential elements Elicit requirements when used to interview involved parties Reconcile viewpoints by providing an integrated view Simulate potential changes Specify requirements for the actual business process

Types of Business Models LO# 3 Types of Business Models

LO# 4 Activity Models Variety of activity models – changing as technology changes Flowcharts Data flow diagrams Business process maps IDEF0 functional models

Activity Models - Must be Able to Describe LO# 4 Activity Models - Must be Able to Describe Events that start, change, or stop flow in the process Activities and tasks within the process The sequence of flow between tasks Decision points that affect the flow Division of activity depending on organizational roles

BPMN for Activity Diagrams LO# 5 BPMN for Activity Diagrams BPMN stands for business process modeling notation The Object Management Group maintains the BPMN specification First specification issued in 2004 widely adopted Specifically designed for process modeling Designed to be understood by business people Software available to support modeling and subsequent process simulation

BPMN Building Blocks - Events Events include start, intermediate, and end events. Intermediate events affect the flow of a process, but do not start or end the process.

BPMN Building Blocks - Activities Activities represent specific steps in the business process. Basic activities are modeled as rounded rectangles Each activity is described with a short verb phrase

BPMN Building Blocks – Sequence Flows Represented by arrows to indicate the progression of activity within the process

BPMN Building Blocks – Gateways Show process branching and merging as the result of decisions Usually gateways appear as pairs on the diagram. The first gateway shows the branching and the second gateway shows merging of the process branches.

LO# 5 BPMN Example

BPMN Pools and Swimlanes LO# 5 BPMN Pools and Swimlanes Identify participants in a business process Pools identify organizations Swimlanes identify departments or individuals Activities are assigned to one participant to show responsibility Each pool must include one start and at least one end The sequence flow must not break between the start and end

BPMN Pools and Swimlanes - Example LO# 5 BPMN Pools and Swimlanes - Example

BPMN Pools and Message Flows Exchanges between two participants (pools) in the same process are represented as message flows Message flows are shown as dashed lines with an arrow on the destination end and a small circle on the source end Message flow content should be described with text

BPMN Pools and Message Flows - Example

BPMN Modeling – Best Practices LO# 5 BPMN Modeling – Best Practices Focus on one business process at a time. Clearly identify the events that start and end the process. Include essential elements, but avoid distracting detail. Think about a token flowing from the start event through the process to the end event; the flow of the token should be clear for all paths through the process. Label activities clearly with a verb and an object, e.g., pay invoice. Model iteratively, getting feedback to improve accuracy and clarity.