 |
|
Each group will
complete a project based on a local business
identified by group members. The name of the
proposed client, together with the name, address
and telephone number of a client contact person,
and a letter from the prospective client agreeing
to participate in the project, are due by October 2. The six stages of the project also
form the basis for group presentations on the due
dates.
|
The project will be
completed in six stages and a final report as
follows:
|
| |
 Due dates
|
|
| 1 |
October 16 |
Document the
existing information system for the purchases,
conversion and revenue processes.
|
| |
|
This first stage will involve
significant interaction with the client. You will
need to supply:
|
| |
|
|
an introduction to the client and the
products or services they provide to create value
for their organization
|
| |
|
|
an overview of their business strategy, key
business processes and competition
|
| |
|
|
an organization chart and brief details of
staffing levels
|
| |
|
|
narrative and flowchart documentation of the
purchases, conversion and revenue cycles. |
| |
| 2 |
October 23 |
Design
event-oriented (R.E.A.) models for the purchase,
conversion and revenue processes - Part1.
|
| |
|
This stage will involve the first
six steps in the process discussed in Chapter 8
of our textbook. Most of the client-related
information should already have been gained
during stage 1 of the project, but it is possible
that you may have to contact them for
supplementatary information.
|
| |
| 3 |
November 1 |
Design
event-oriented (R.E.A.) models for the purchases,
conversion and revenue processes - Part 2.
|
| |
|
Steps seven and eight of the
process described in Chapter 8 of the textbook
will be completed at this stage, concluding the
logical and physical design of the system.
|
| |
| 4 |
November 6 |
Document the
existing internal control structure for the
client as it relates to ONE OF the purchases,
conversion and revenue processes cycles, and
recommend additional desirable controls.
|
| |
|
The main issues to be explored in
this stage of the project will be covered in
Chapter 10 of our textbook. The format of the
documentation of controls will be discussed in
class. In brief, you will be asked to list
existing controls, classify them in accordance
with various categories, and explain their
purpose; additionally, you will be required to
propose further control procedures, categorize
them, and identify the potential benefits of
implementing them.
|
| |
| 5 |
November 27 |
Prepare Computer
Audit Plans for both the client's existing and
your proposed new information systems for your
selected cycle.
|
| |
|
This will be a simple word
processed document based on the material in
Chapter 11 of our textbook.
|
| |
| 6 |
December 4 |
Implement your
event-oriented information system for your
selected cycle using Microsoft ACCESS and enter
fictitious data to as to be able to generate the
various reports.
|
|
| 7 |
December 13 |
Complete any necessary
reworking of the project and produce the
final report |
| |
The final report for
the completed project including all phases is due
by the beginning of class on December 13. You
will need to describe remaining work that would
be necessary to implement the re-designed system
for use in the client's business, conclude as to
the advantages and disadvantages for the client
of potentially adopting your revised system, and
report on the lessons learned by group members
during the course of the project. Handwritten
materials will not be accepted or graded for any
of the project stages. Text must be produced
using a word processor, and other forms of
documentation (tables, flowcharts, diagrams,
etc.) must be produced using appropriate software
tools.
|
| |
|