1 / 27

Computer-Based Accounting Information Systems Design

Computer-Based Accounting Information Systems Design. ACC 419/619 Joe Callaghan. Oakland University Accounting & Finance Department. Introduction/Overview. Review Tentative Course Syllabus Prerequisites Instructor Info Ways to Communicate Course Resources Grading

vlad
Download Presentation

Computer-Based Accounting Information Systems Design

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. Computer-Based Accounting Information Systems Design ACC 419/619 Joe Callaghan Oakland University Accounting & Finance Department

  2. Introduction/Overview • Review Tentative Course Syllabus • Prerequisites • Instructor Info • Ways to Communicate • Course Resources • Grading • Other Handouts/Readings • Questions?

  3. Technical Issues • Oracle Designer/Developer • RDBMS: Oracle 8i, ODBC • Code: PL/SQL, Java • Student Models • E-mail, Web-page, etc. • Oracle accounts • Production server • Development server

  4. Modeling Business 1 (IPSO) • Overview of Business Enterprise $ $ Suppliers Enterprise Customers Resources/ Factors Products/ Services Convert/ Value-Add

  5. Modeling Business 2 • Outline the Various Cycles Cash Disburse Cash Receipts $ $ Suppliers Enterprise Customers Materials (I/C) Labor (Payroll) Overhead O/E & Sales Job Cost I/C

  6. Systems Development Life-Cycle • Top-Down, Divide and Conquer • Other Methods • Bottom-Up (Reverse Engineering) • Rapid Application Development • Object-Oriented Systems • ERP (Enterprise Resource Packages)

  7. Information Engineering Stages(James Martin) Information Strategy Planning Analysis Design Construction

  8. Curricular Strategy:Model-Oriented Tool-Enhanced (MOTE) • Using IE and MOTE • rigorous, yet flexible framework • structured logic, but no specific language • relational, but not vendor-specific • support for varied environments, e.g.. Block Mode, GUI, Batch, and Client-Server

  9. Information Engineering Stages(Sterling Software™) ISP Bus. Area Analysis Bus. Sys. Design Technical Design Construc- tion Transition Production

  10. Analysis and Design Tool Outputs ERD, AHD, ADD, PAD Analysis Oracle Models Design Generated Code, DDL (PL/SQL Java) Construction

  11. Oracle Designer: Main

  12. Gen to Designer

  13. Purposes of InformationStrategy Planning (ISP) • To link IT Planning to Strategic Business Planning • To create an architectural framework that individual systems can fit into • To set priorities for Business Area Analysis

  14. Analysis Tasks Data Analysis Interaction Analysis Analysis Model Confirmation Design Planning Activity Analysis Current System Analysis

  15. Data & Activity Analysis • Done in parallel • Developed iteratively • Ask User • Document • Feedback • Refine • Deliverables - Entity Relationship Diagram, Function Hierarchy Diagram, Process Models

  16. Interaction Analysis • Examines the relationships and interactions between data and processes • Three techniques • REA analysis • Entity type life cycle analysis • Process logic analysis

  17. Current Systems Analysis • Provides validation of understanding • Planning for transition • Preparation for conversion • Identification of reusable components

  18. Model Confirmation • Checks business area model for correctness and completeness • Comparison with current systems • Stability analysis

  19. Overview of Design

  20. Introduction • Analysis precedes it and is prerequisite to it • Construction and Implementation is next stage • Consists of two parts • External • Internal or Technical

  21. Prerequisites to Design • Analysis Deliverables: • Data Model: ERD • Activity Model: AHD, ADD • Interaction model: REA • Use Belgium Chocolate • Website link • See models and Access database

  22. Design • External • Goal: develop system as it appears to users • Who are the users? • What are the locations? • What are the technical possibilities? • Internal (Technical) • transform logical data model into a physical representation of the database • transform activity models into executable system

  23. Tasks • Choose Application Style • GUI • Client Server • Terminal based • Batch, perhaps using legacy systems • Designing the Dialog • Data Flow Diagrams • Design the Interface • Windows, Dialog boxes, controls • Design the Procedure Logic (PrAD) • Triggers, Procedures and Reports • Design the Data Structure

  24. Design Deliverables • Interface Layouts, using views and Interface Design Tool (Forms Developer) • A Set of Procedural Logic • Report requirements (Reports Developer) • Data Structure List

  25. GUIs • Create Window • Specify Window characteristics • Exercise to re-enforce learning • Add menu items to a window • Specify menu items • Create Controls • Add controls that implement views • Add other controls, e.g. OK, Cancel • Map Import/Export Views • Add Events, invocation of PrAD logic

  26. Client/Server • Presentation logic, Data manipulation logic, Data Management • Remote Presentation (Presentation management only on Client, all logic on Server) • Distributed Process (Presentation Logic on Client, others on Server) • Remote Data Access (Only Data management on Server)

  27. Next Session • Review Oracle Tutorial • Incorporation of REAL Modeling • Review Belgium Chocolate • Show Analysis Examples

More Related