acct 479 accounting systems developmentweb-app.usc.edu/soc/syllabus/20143/14165.pdfآ  acct 479...

Download ACCT 479 Accounting Systems Developmentweb-app.usc.edu/soc/syllabus/20143/14165.pdfآ  ACCT 479 – Accounting

Post on 13-Mar-2020

0 views

Category:

Documents

0 download

Embed Size (px)

TRANSCRIPT

  • ACCT 479 Fall 2014

    1 of 12

    ACCT 479 – Accounting Systems Development

    Course Syllabus Fall Semester 2014 Section # 14165; Location – ACC205 Class Sessions – M & W: 4:00 – 5:50 pm Professor: Bob Kiddoo Office: ACC 114 Office Phone: 213.740.5024 E-mail: kiddoo@usc.edu Office Hours: M & W: 12:00 – 12:30 pm; 6:00 – 7:00 pm; and

    by appointment

    Course Description This is an advanced course covering project planning / management, system selection, enterprise system implementations, system security design, system cutover planning and system review and compliance requirements. Emphasis is placed on the strategies, methodologies and techniques used by professional managers and consultants to plan for, select, implement and control Enterprise Resource Planning (ERP) based accounting and reporting solutions in a variety of industries. During this course, you will learn how organizations perform project management tasks, build business cases to support management action, determine reporting requirements and develop their chart of accounts to support management decision making and meet overall business requirements. Upon completion of this course, you will have the ability to define and execute a project to select and implement an enterprise system solution that supports specific business needs. The research questions, deliverables and semester projects are designed to give you a theoretical and practical understanding of: enterprise financial systems; project management; financial system implementation requirements; financial systems technical design; and system documentation requirements.

    Learning Objectives Upon completion of this course, you should be able to:

     Describe and apply the System Development Life Cycle to a global organization by producing a detailed project plan for an ERP implementation project.

     Describe and demonstrate the steps required to build a formal business case to gain management approval for a global ERP based implementation project by developing and incorporating detailed project work schedules, project staffing budgets, technical designs and software selection criteria.

     List and describe in detail an inventory of system reports required to support management decision making at all levels by producing a report library and future state chart of accounts design for an ERP based financial system.

     Compare the current state business processes of an organization to ERP best practices by producing future state business process maps, data models and configuration documentation.

     Demonstrate the ability to document system security and testing required for proper audit compliance by producing system security matrices, test plans and test scripts.

     Compare system implementation project documentation to best practices by reviewing documentation and producing written audit observations / review notes in accordance with COBIT standards.

    mailto:kiddoo@usc.edu

  • ACCT 479 Fall 2014

    2 of 12

    To achieve these learning objectives, a combination of background reading and research, interactive discussion / lecture and your work on class deliverables will be utilized. Please note, the most important word in the sentence above is “interactive.” The reason is that research on learning indicates it is very difficult to gain anything more than a superficial understanding of material without practice and feedback. Therefore, you should expect our class sessions to incorporate a substantial amount of both. To demonstrate you achievement of the learning objectives stated above: 1) you will be required to demonstrate your knowledge by individually working problems during exams; and 2) you will be required to participate in completing group assignments throughout the semester.

    Required Materials The following books and software are available in the bookstore and will be used for both ACCT 478 and 479.

     Whitten, Bentley and Dittman, Systems Analysis and Design Methods, Seventh Ed. Irwin / McGraw Hill

     Microsoft Corporation’s Office Professional and Visio (Other tools can be substituted as long as the instructor grants prior approval.)

    As you already know, this is not the traditional: “lecture”; “read”; “problems”; “test” class. Our field requires us to maintain competence by keeping up with current events and innovations. If you stick with information technology as a career, your only guarantee is work will consist of a constantly changing set of solutions being applied to a variety of organizations and industries. The bad news is you’ll never know it all, but the good news is it won’t be boring.  To this end we will spend more time expanding your knowledge about information technology in general. During the semester, we will be concentrating on projects related to ERP software. However, other tools will also be discussed throughout the course.

    Prerequisites and Recommended Preparation The formal prerequisites for this course are:

     ACCT 478 (may be taken concurrently)

     A minimum grade point average of 2.5 must have been earned in previous accounting courses. (See LSOA Grading and Academic Standards for further information.)

    In addition, regularly reading a variety of periodicals will aid in your business process / systems consulting education. Lastly, as a senior level class, my expectation is you will incorporate the knowledge you acquired in other business classes (e.g., all accounting classes, finance, operations management, marketing, communications, etc.) in any answer you provide during class sessions and in competition of your course projects.

    Course Notes Distributed materials and other class information will be available through your Blackboard account.

  • ACCT 479 Fall 2014

    3 of 12

    Grading Policies Your grade in this class will be determined by your relative performance on a pair of exams, a technical presentation, an implementation review presentation, implementation documentation, a peer project evaluation, and class participation. The total class score will be weighted as follows:

    Points Weight

    Exam 100 20% (Individual)

    Technical Presentation 10 5% (Group)

    Implementation Presentation 10 5% (Group)

    Implementation Documentation 10 20% (Group)

    Peer Project Evaluation 10 30% (Group / Individual)

    Participation 10 20% (Individual)

    After each student’s weighted total points are determined for the semester, letter grades will be assigned on a curve according to Marshall School of Business grading guidelines. Final grades represent how you perform in the class relative to other students. Your grade will not be based on a mandated target, but on your performance. Historically, the average grade for this class is about a 3.3 (i.e., B+). Three items are considered when assigning final grades:

    1. Your score for each of the items above weighted by the appropriate factor and summed.

    2. Your overall percentage score for the course.

    3. Your ranking among all students in the course(s) taught by your instructor during the current semester.

    The grade of “W” is allowed only if a student withdraws after the third week but before the end of the twelfth week of the semester. The grade of incomplete (IN) can be assigned only if there is work not completed because of a documented illness or unforeseen emergency occurring after the 12th week of the semester that prevents the student from completing the semester. An “emergency” is defined as a serious documented illness, or an unforeseen situation that is beyond the student’s control, that prevents a student from completing the semester. Prior to the 12th week, the student still has the option of dropping the class. Arrangements for completing an IN must be initiated by the student and agreed to by the instructor prior to the final examination. All work required to replace the IN with a final grade must be completed within one calendar year from the date the IN was assigned. If the student does not complete the work within the year, the IN will automatically be converted to a grade of F.

    Assignments and Grading Detail Expectations regarding your performance on exams, acceptance presentations, design documentation and participation are as follows:

    Exam There will be one exam. No makeup exams will be given; the exam must be taken at the scheduled time. For the exam, you will be responsible for the research questions, lectures, class discussions and your semester project progress at the point of the exam. After the test is returned there is a one-week reflection period after which you will have one week to discuss your grade. Please be aware this discussion may result in an increase, decrease or no change to your score. After this time, grades on tests become final. All other grades are final once given. The exam dates for this fall are as follows:

    Exam Monday November 17 th

    Final exam Wednesday December 10 th (4:30pm – 6:30pm)

  • ACCT 479 Fall 2014

    4 of 12

    Presentations, Implementation Documentation and Deliverables There will be one semester long design documentation project and several deliverables. These must be done in teams consisting of four or five members as smaller teams have difficulty getting the work done while larger teams have difficulty getting together. T

Recommended

View more >