1 / 20

Accounting Information Systems: Planning and Analysis Introduction: The MOTE Approach

Slides 1. Accounting Information Systems: Planning and Analysis Introduction: The MOTE Approach. Oakland University Department of Accounting & Finance. History of IT. Phase I (circa ‘60s): Automating clerical functions by duplicating manual systems (e.g., payroll processing)

sybil-mcintyre
Download Presentation

Accounting Information Systems: Planning and Analysis Introduction: The MOTE Approach

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Slides 1 Accounting Information Systems: Planning and AnalysisIntroduction: The MOTE Approach Oakland University Department of Accounting & Finance

  2. History of IT • Phase I (circa ‘60s): Automating clerical functions by duplicating manual systems (e.g., payroll processing) • Phase II (circa ‘70s to ‘80s): Developing separate legacy systems • Phase III (‘90s): Cross-functional, event-driven, enterprise-wide systems

  3. History of Accountant’s Role in Systems Development • Accountant alone - manual system - described by Pacioli over 500 years ago • 1970s and 1980s: Generally unable to develop computer systems - hired systems personnel to develop and manage the systems • Role has been limited to that of user • Now, software engineers are developing accounting systems with or without input from accountants

  4. Traditional AIS “IT has benefited accounting ... primarily by automating 500-year-old pencil-and-paper systems instead of employing the unlimited potential of modern computer technology” (Walker & Denna, 1997)

  5. Calls for Change • VP of Lotus Development to AICPA: “CPAs who don’t keep up with this new technology are in danger of becoming road kill on the information highway” • Labor markets are demanding expanded role as designer, evaluator and manager of IS

  6. Current Environment • Lack of standardization for AIS Course • managerial to financial focus • from word processing and spreadsheet skills to systems design • conceptual skills only (no hands-on skills) • hands-on skills only (no framework)

  7. What should be done? • Summary of Problem: • No consistent approach to teaching • Accounting graduates have inadequate IS skills • Solution • MOTE (developed at OU) • Systems emphasis in AIS courses • Three- course AIS sequence, plus an Information Systems Audit and Control Course • Business Information Systems & Accounting Major

  8. Intent • Give Accounting Majors MIS skills • consulting track for CPA firms • AIS position in corporate setting • Give MIS majors accounting skills • Better systems analyst • Better systems designer

  9. New AICPA Directions • For IT assurance services identified by the AICPA: see http://www.aicpa.org/assurance/about/newsvc/index.htm

  10. MO - Model-Oriented: We use the SDLC logical framework: a systematic and orderly approach to systems development We implement this framework by using the IE set of methodologies(developed by James Martin, 1989) Curricular Strategy: The MOTE Approach

  11. Stages of the Systems Development Life Cycle Planning Analysis Design Construction

  12. Systems Planning • Also called Information Strategy Planning (ISP) • Concerned with top management goals, targets, and critical success factors • Concerned with how IT can be used to create new opportunities or competitive advantages • An overview model is created of the enterprise, its functions, data, and information needs • The overview model is split into areas appropriate for analysis

  13. Decide what processes are needed to implement business strategy Decide how processes interrelate Decide what data is needed Identify areas for systems design Involve users extensively Create activity models (AHD, ADD) Create a fully normalized data model (ERD) Create interaction models (REA) Identify PADs, which contain business logic to enforce business rules Remain independent of technology and current systems Systems Analysis

  14. Systems Design • External Design: Apply mapping rules to convert processes to procedures (to build windows, interfaces, dialogue boxes, forms, for activities that need to be automated) • Internal Design: Map to technical environment

  15. Systems Construction • Generates programming code which results in programs designed to perform specific tasks for users • Physically structures the database (by generating DDL)

  16. TE - Tool-Enhanced Software development tool used is COOL:Gen™ 5.1 (a competitor is Oracle Designer) Curricular Strategy: The MOTE Approach

  17. COOL:Gen™ Implements Entire Systems Development Life Cycle Phases: PLANNING ANALYSIS DESIGN - External DESIGN - Internal (Technological Environment Mapping) CONSTRUCTION Source: Adapted from Sterling Software, Inc., 1997, p. 17.

  18. Cool:Gen™ Tool Outputs Organization Hierarchy, ERD, AHD, ADD, PAD Planning & Analysis A PrAD Graphic User Interface Design Generated Code, DDL (COBOL, C++, web-enable) Construction

  19. Advantages of the MOTE Approach • rigorous, yet flexible framework • structured logic, but not language-specific • relational database, but not vendor-specific • support for varied technological environments, e.g., block mode, batch processing, client-server, web-enabled systems • produces IT-savvy graduates

  20. Desired Orientation • Systems Viewpoint • Input (resources), Process (convert), Storage (data), Output (product/service) (IPSO business template or pattern) • RDBMS vs. Legacy Systems • Tables vs. Journals & Ledgers • Signing Convention vs. Drs & Crs • Cross-functional vs. “Stovepipe” Systems • Diagramming vs. coding • A Focus on a Variety of User Needs • versus only what accountant wants

More Related