1 SYSTEMS ANALYSIS Pertemuan 7 s.d 12 Matakuliah: A0554/Analisa dan Perancangan Sistem Informasi Akuntansi Tahun: 2006.

Slides:



Advertisements
Similar presentations
A Business process approach
Advertisements

Reading System Documentation Using Flowchart Pertemuan Matakuliah: F0204 / Sistem Akuntansi Tahun: 2007.
Documenting Information Systems
Copyright © 2015 Pearson Education, Inc. Systems Documentation Techniques Chapter
Chapter 3 Data Modeling Copyright © 2014 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent.
Systems Documentation Techniques
Internal Control.
Chapter 5 Sales and Collections Business Process
Object-Oriented Analysis and Design
Chapter 4 – Documenting Information Systems
Conversation Form l One path through a use case that emphasizes interactions between an actor and the system l Can show optional and repeated actions l.
Pertemuan 5-6 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 4 IDENTIFYING RISKS AND CONTROLS IN BUSINESS PROCESSES
DOCUMENTING ACCOUNTING SYSTEMS
© 2005 Prentice Hall4-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Internal Control Pertemuan 05 s.d 06 Matakuliah: F0712 / Lab Sistem Informasi Akuntansi Tahun: 2007.
Chapter 9 Using Data Flow Diagrams
1 SYSTEMS INVESTIGATION Pertemuan 3 s.d 6 Matakuliah: A0554/Analisa dan Perancangan Sistem Informasi Akuntansi Tahun: 2006.
Requirements Analysis Activity Diagrams b511.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis.
1 SYSTEMS DESIGN Pertemuan 13 s.d 20 Matakuliah: A0554/Analisa dan Perancangan Sistem Informasi Akuntansi Tahun: 2006.
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.
COMP1007 Intro to Requirements Analysis © Copyright De Montfort University 2002 All Rights Reserved COMP1007 Introduction to Requirements Analysis Lecture.
Learning Objectives LO1 Explain the key risks of misstatement in production and payroll processes. LO2 Outline the production process: typical transactions,
Chapter 5 UNDERSTANDING AND DESIGNING ACCOUNTING DATA.
Chapter 7: The Object-Oriented Approach to Requirements
Auditing Purchases, Trade Payables and Payroll
Jones Rama Accounting information system A Business process approach FREDERICK L. JONES DASARATHA V. RAMA.
1 Chapter 2 Revision: Documentation DFD System FC.
BPMN By Hosein Bitaraf Software Engineering. Business Process Model and Notation (BPMN) is a graphical representation for specifying business processes.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Systems Analysis and Design in a Changing World, 6th Edition
From Use Cases to Test Cases 1. A Tester’s Perspective  Without use cases testers will approach the system to be tested as a “black box”. “What, exactly,
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Database Design Principles – Lecture 3
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Chapter 10 THE ACQUISITION CYCLE— PURCHASE INVOICES AND PAYMENTS.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
Systems Analysis and Design in a Changing World, 6th Edition
Use Case Diagram The purpose is to communicate the system’s functionality and behaviour to the customer or end user. Mainly used for capturing user requirements.
McGraw-Hill/Irwin © 2003 The McGraw-Hill Companies, Inc., All Rights Reserved. 6-1 Chapter 6 CHAPTER 6 INTERNAL CONTROL IN A FINANCIAL STATEMENT AUDIT.
1 Accounting systems design & evaluation Karen Lau 25 Feb 2002.
Systems Analysis and Design in a Changing World, Fourth Edition
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Domain Model A representation of real-world conceptual classes in a problem domain. The core of object-oriented analysis They are NOT software objects.
Analysis Yaodong Bi. Introduction to Analysis Purposes of Analysis – Resolve issues related to interference, concurrency, and conflicts among use cases.
USE CASE Pertemuan 7 Matakuliah: Konsep object-oriented Tahun: 2009.
Pertemuan 15 Business and Information Process Rules, Risks, and Controls Matakuliah: M0034 /Informasi dan Proses Bisnis Tahun: 2005 Versi: 01/05.
Accounting Information Systems: A Business Process Approach Chapter Three: Documenting Accounting Systems.
Chapter 6: Structuring Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
Identifying Risks & Controls in Business Processes By: Lea Sulaiman Saputra D1555.
Dokumentasi Sistem Dengan Activity Diagram Pertemuan 03 s.d 04 Matakuliah: F0712 / Lab Sistem Informasi Akuntansi Tahun: 2007.
Use Case Diagrams. Introduction In the previous Lecture, you saw a brief review of the nine UML diagrams. Now that you have the clear, you'll start to.
1 CHAPTER 5 - b INTERNAL CONTROL OVER FINANCIAL REPORTING.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
 Problem Analysis  Coding  Debugging  Testing.
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 3 DOCUMENTING ACCOUNTING SYSTEMS
Welcome to M301 P2 Software Systems & their Development
Chapter 5 UNDERSTANDING AND DESIGNING ACCOUNTING DATA
Accounting Information Systems: A Business Process Approach
Chapter 4: Business Process and Functional Modeling, continued
Chapter 11 Designing Inputs, Outputs, and Controls.
Use Case Model.
Accounting Information Systems: A Business Process Approach
Chapter 4: documenting information systems
Accounting Information Systems: A Business Process Approach
Presentation transcript:

1 SYSTEMS ANALYSIS Pertemuan 7 s.d 12 Matakuliah: A0554/Analisa dan Perancangan Sistem Informasi Akuntansi Tahun: 2006

2 Models and Techniques Systems analysis –Workflow table –Activity diagram –Use case diagram –Use case description –Risks analysis –Types of internal control

3 The UML Activity Diagram The UML activity diagram plays the role of a ‘map’ in understanding business process by showing the sequence of activities in the process.

4 Overview & Detailed Activity Diagrams The overview diagram presents a high level view of the business process by documenting the key events, the sequence of these events & the information flows among these events. The detailed diagram is similar to a map of a city or town. It provides a more detailed representation of the activities associated with one or two events shown on the overview diagram.

5 Preparing Overview Activity Diagrams Preliminary steps: Read the narrative & identify key events Annotate the narrative to clearly show event boundaries & event names Steps for preparing the activity diagram: Represent agents participating in the business process using swimlanes Diagram each event. Show the sequence of these events Draw documents created & used in the business process draw tables (files) created & used in the business process

6 Preparing Detailed Activity Diagrams Steps for preparing overview activity diagrams: Annotate narrative to show activities Prepare a workflow table Identify necessary detailed diagrams For each detailed diagram, perform the following substeps: –Set up swimlanes for the agents participating in the event or events represent in the detailed diagram –Add a rounded rectangle for each activity in the events) being documented in that detailed diagram –Use continuous lines to show the sequence of the activities

7 –Set up any documents created or used by the activities in that diagram –Use dotted lines to connect activities & documents –Document any tables created, modified or used by the activities in the diagram in the computer column –Use dotted lines to connect activities & tables

8 WORKFLOW TABLE The actors performing specific activities are listed in the column on the left. The corresponding activities are listed on the right. The activities have been listed using verbs in active voice (e.g., arrives, records, etc).

9 USE CASE DIAGRAM A use case is a sequence of steps that occur when an ‘actor’ is interacting with the system for a particular purpose. Use case diagram is A list of use cases that occur in an application and that indicate the actor responsible for each use case.

10 USE CASE DESCRIPTION A description of a use case, typically represented as a sequence of numbered steps. Use case descriptions may also be used for documenting internal control.

11 RISKS ANALYSIS Risk assessment is the identification & analysis of risks that interfere with the accomplishment of internal control objectives. Control activities are the policies & procedures developed by the organization to address the risks to the achievement of the organization’s objectives.

12 RISK TYPE Execution risks Information system risks

13 EXECUTION RISK Execution risks : Risks that transaction will not be executed properly. Five steps are useful in understanding & assessing execution risk: Achieve an understanding of the organization’s processes. Identify the goods or services provided & cash received that are at risk.

14 Restate each generic risk to describe the execution risk more precisely for the particular process under study. Exclude any risks that are irrelevant or obviously immaterial. Assess the significance of the remaining risks. For significant risks, identify factors that contribute to the risk. The events in the process can be used to systematically identify these factors.

15 INFORMATION SYSTEM RISKS IS Risks : Risks of improper recording, updating, or reporting of data in an information system. 2 categories of IS Risks : -Recording risks -Update risks

16 RECORDING RISKS Recording risks : Risks that event information is not captured accurately in an organization’s IS. 3 steps are useful in identifying recording risks : Achieve an understanding of the process under study. Identify the events. Review the events, and identify instances where data are recorded in a source document or in a transaction file. For each event where data are recorded in a source document or transaction record, consider the preceding generic recording risks.

17 UPDATE RISKS Update risks : Risks that summary fields in master records are not properly updated. 3 steps are useful in identifying update risks: Identify recording risks. Identify the events that include update activity. Identify the summary fields in master files that are updated. For each event where a master file is updated, consider the preceding generic update risks.

18 TYPES OF INTERNAL CONTROL Types of control activities: Workflow controls Input controls General controls Performance reviews

19 WORKFLOW CONTROLS Controls that help manage a process at it moves from one event to the next. Include : segregation of duties, required sequence of events, prenumbered documents, reconciliation of records with assets, and others.

20 INPUT CONTROL Used to control the input of data into computer systems. Include : drop down or look up menus, format checks to limit data, validation rules, confirmation of data, and others.

21 GENERAL CONTROLS Broader controls that apply to multiple processes. Include : IS planning, organizing the IT function, and others.

22 PERFORMANCE REVIEW Activities involving analysis of performance including the comparison of actual results with budgets, forecasts, standards and prior period data.