Professional Documents
Culture Documents
Strategi
Pengembangan SIA
Wahdan Arum Inawati
Accounting Information System & Internal Control
Contents
01
Purchasing
Prewritten Software
01. Purchasing Prewritten Software Accounting Information System & Internal Control
Selecting a Vendor
Approaches to Comparing
System Performace
Benchmark Requirements
Point Scoring
Problem Costing
01. Purchasing Prewritten Software Accounting Information System & Internal Control
Benchmark Problem
✓ The new AIS performs a data processing task with input, processing,
and output jobs typical of what would be required of the new system.
✓ Processing times are calculated and compared.
✓ The AIS with the lowest time is judged most efficient.
Point Scoring
Zorba examined the packages offered by the three vendors and rated
them based on these three criteria. Ratings were from 1–5 with 5
being the highest score.
01. Purchasing Prewritten Software Accounting Information System & Internal Control
Point Scoring
The weighted scores are then computed by multiplying the rating given
to each vendor on each criterion times the weight assigned to that
criterion.
Requirements Costing
Requirements costing:
❑ Estimates cost of purchasing or developing features
that are not included in a particular AIS.
❑ The total AIS cost is calculated by adding the
acquisition cost to the purchasing and development
costs.
❑ Total cost = cost of system with all required features.
Accounting Information System & Internal Control
02
Developing
Software In
House
02. Developing Software In House Accounting Information System & Internal Control
03
Outsource The
System
03. Outsource The System Accounting Information System & Internal Control
Technical
Help desk
Support
03. Outsource The System Accounting Information System & Internal Control
04
Prototyping
04. Prototyping Accounting Information System & Internal Control
01 03
Identify basic Repeated
requirements 02 iterations
Develop an
04
initial prototype Use the system
04. Prototyping Accounting Information System & Internal Control
FIRST STEP
The first step is to identify basic
requirements by meeting with users to
agree on the size and scope of the system
and decide what it should include and
exclude.
The developer must ensure:
❑ User expectations are realistic.
❑ Their basic information requirements
are met.
The designer uses the information
requirements to develop cost, time, and
feasibility estimates for alternative AIS
solutions.
04. Prototyping Accounting Information System & Internal Control
THRID STEP
The third step involves repeated
iterations of:
• Users identifying changes.
• Developers making the
changes.
• The system being turned back
to users for next round.
This step continues until users are
satisfied—usually 4 to 6 iterations.
04. Prototyping Accounting Information System & Internal Control
FOURTH STEP
Thanks!
Do you have any
questions?