Professional Documents
Culture Documents
Name: Class Number: Section: Schedule: Date:: Lesson Title: Introduction To Transaction Processing Lesson Objectives
Name: Class Number: Section: Schedule: Date:: Lesson Title: Introduction To Transaction Processing Lesson Objectives
Challenges are what make life interesting. Overcoming them is what makes life
meaningful. – Joshua J. Marine
Please read the learning targets before you proceed to the succeeding activities. The learning
targets are your goals. Remember, you need to achieve your learning targets at the end of
the lesson.
B. MAIN LESSON
1) Activity 2: Content Notes
Documentation Techniques
The old saying that a picture is worth a thousand words is extremely applicable when it comes to
documenting systems. A written description of a system can be wordy and difficult to follow.
Experience has shown that a visual image can convey vital system information more effectively and
efficiently than words. As both systems designers and auditors, accountants use system
documentation routinely. The ability to document systems in graphic form is thus an important skill for
accountants to master.
Cardinalities
Represent the numerical mapping between entities:
✓ one-to-one
✓ one-to-many
✓ many-to-many
diagrams are related through data; each data store in the DFD represents a corresponding data entity
in the ER diagram.
FLOWCHARTS
A flowchart is a graphical representation of a system that describes the physical relationships between
its key entities. Flowcharts can be used to represent manual activities, computer processing activities,
or both. A document flowchart is used to depict the elements of a manual system, including accounting
records (documents, journals, ledgers, and files), organizational departments involved in the process,
and activities (both clerical and physical) that are performed in the departments.
Document Flowcharts
To demonstrate the preparation of a document flowchart, let’s assume that an auditor needs to
flowchart a sales order system to evaluate its internal controls and procedures. The auditor will begin
by interviewing individuals involved in the sales order process to determine what they do. This
information will be captured in a set of facts like those below. Keep in mind that the purpose here is
to demonstrate flowcharting. Thus, for clarity, the system facts are intentionally simplistic.
1. A clerk in the sales department receives customer orders by mail and prepares four copies of
a sales order.
2. Copy 1 of the sales order is sent to the credit department for approval. The other three copies
and the original customer order are filed temporarily, pending credit approval.
3. The credit department clerk validates the customer’s order against credit records kept in the
credit department. The clerk signs Copy 1 to signify approval and returns it to the salesclerk.
4. When the salesclerk receives credit approval, he or she files Copy 1 and the customer order
in the department. The clerk sends Copy 2 to the warehouse and Copies 3 and 4 to the
shipping department.
5. The warehouse clerk picks the products from the shelves, records the transfer in the stock
records, and sends the products and Copy 2 to the shipping department.
6. The shipping department receives Copy 2 and the goods from the warehouse, attaches Copy
2 as a packing slip, and ships the goods to the customer. Finally, the clerk files Copies 3 and
4 in the shipping department.
Based on these facts, the auditor can create a flowchart of this partial system. It is important to note
that flowcharting is as much an art form as it is a technical skill, giving the flowchart author a great
deal of license. Nevertheless, the primary objective should be to provide an unambiguous description
of the system. Certain rules and conventions need to be observed:
1. The flowchart should be labeled to clearly identify the system that it represents.
2. The correct symbols should be used to represent the entities in the system.
3. All symbols on the flowchart should be labeled.
4. Lines should have arrowheads to clearly show the process flow and sequence of events.
5. If complex processes need additional explanation for clarity, a text description should be included
on the flowchart or in an attached document referenced by the flowchart.
System Flowcharts
✓ illustrate the relationship among processes and the documents that flow between them
✓ contain more details than data flow diagrams
✓ clearly depict the separation of functions in a system
Program Flowcharts
Every program represented in a system flowchart should have a supporting program flowchart that
describes its logic.
Accountants sometimes use program flowcharts to verify the correctness of program logic. They
compare flowcharts to the actual program code to determine whether the program is doing what the
documentation describes. Program flowcharts provide essential details for conducting information
technology (IT) audits.
Program Flowchart Symbols
3. Document flowcharts
a) depict logical tasks that are being performed, but not who is performing them
b) illustrate the relationship between processes, and the documents that flow between
them and trigger activities
c) represent relationships between key elements of the computer system
d) describe the logic of the process
10. Auditors may prepare program flowcharts to verify the correctness of program logic.
a) True
b) False
C. LESSON WRAP-UP
1) Activity 6: Thinking about Learning
A. Work Tracker
You are done with this session! Let’s track your progress. Shade the session number you just
completed.
P1 P2 P3
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
KEY TO CORRECTIONS:
Activity 3:
ANS:
a. Symbol 1 is a terminal showing the source or destination of a document or report; symbol 2 is source
document or report.
b. Symbols 3 and 4 depict the entry of data in real time into a system from a computer terminal
c. Symbols 4 and 5 depict the storage/retrieval of data to/from a computer disk
10
d. Symbols 6,8 and 9 depict the processing of a source document and its placement into a file.
Activity 5:
1. A 2. A 3. B 4. B 5. D
6. A 7. B 8. D 9. A 10. A
FAQs
1. Is a DFD an effective documentation technique for identifying who or what performs a particular
task?
ANS:
No. A DFD shows which tasks are being performed, but not who performs them. It depicts the logical
system.
11