Professional Documents
Culture Documents
ABSTRACT
Water sport is a tourist attraction that operates alongside of Tanjung Benoa beach. It's operated by private company
in collaboration with local society under supervision of traditional village chief. The company run the business in the office
and the local society serve the services in the beach/sea. The company runs the business manually. Consequently, the service
runs slow, the possibility of fraud by employees and not well-organized financial ad min istration of the co mpany. To imp rove
company performance and reduce the occurrence of fraud, do computerization is the right solution. Thus, analyzing the
system requirement is the beginning of system development. By applying OOA/D as part of object -oriented development
system, the description, specification and design of system developed is identified. There are three types user of accounting
information system with different level privilege i.e. cashier, accounting and admin in lowest to highest order. The system
has four packages with a group of similar functions. The packages are Master, Cashier, Accounting and Report that linked
each other’s. By this system, the company can handle the accounting and financial transaction, includes managing contract
rate with the travel agencies, recording sales transactions, calculating sales commission, creating sales journal, managing
account receivable and generating financial report.
Keywords: water sport, accounting information systems, object-development systems, OOA/D.
B6.4-2
software requirements. similar and more related will be grouped in one package.
2. OOA (Object-Oriented Analysis); Analysis is a
process that emphasizes an investigation of the
problem and requirements , rather than a solution.
OO Analysis emphasis on finding and describing
the objects or concepts in the problem domain
(Coad & Yourdan, 1991).
3. OOD (Object-Oriented Design); Design is a process
that emphasizes a conceptual solution that fulfills
the requirements rather than its implementation. Figure-2. Packages of the System
OO Design emphasis on defining software
objects and how they collaborate to fulfill the Define Use Cases
requirements (Coad & Yourdon, 1991). As a result of the requirement analysis, the do main
This development process can be divided into 4 process of the system can be described into some s pecific
(four) steps as describe on Figure-1 (Larman, 2005). functions, and some functions are grouped into one
package. A description of related domain process named a
function can be written as use case. Use case is a simple
written story about the procedure or description of a
Figure-1. The development proces s process. To make it more understood, the UM L define a use
In step 1, use case is defined as reference of a case diagram to illustrate the names of use cases and actors,
function in the system. A function is a series activity to do a and their relationships (Douglas, 2001). Figure 3 – 6
certain job that result a certain output. A function is illustrate the use case diagram of each package of the
initiated by an actor and can be supported by another actor. system.
An actor can be human, machine or another system that In Figure-3, there are 3 (three) primary actors
relate or connect to the system. In this case, the system is grouped as User on the left, 3 (three) supporting actors on
divided into several functions (use cases). the right and 8 (eight) use cases of Master Package. The
Do main model is defined in step 2. Do main model explanation of the use cases as follows:
is a conceptual model represents ideas, things or objects 1. Manage Contract Rate: User record and manipulate
and its relationship each other in the real-world problem product price base on the contract signed by both
domain. company and agent.
The interaction diagrams that is defined in step 3, 2. Manage Agent Data: User record and manipulate
is a diagram that illustrate the interaction among the objects the agent and freelance guide personal data.
while a function executed. The interaction is about 3. Manage Employee Data: User record and
sending/receiving a message that will be converted as a manipulate the employee personal data.
method. A method is a process doing something. 4. Change Password: User change their password to
Design Class Diagrams is defined in step 4. It make more securely.
illustrates class in conjunction with other class as a 5. Manipulation User: Admin manipulate the user
structure of the software built. data, include change his password, and manage
user data.
6. Manage User Data: Admin record new user, edit
RESULTS AND DISCUSSION and delete existing user data. Admin has privilege
Base on the data and the information are collected to decide who can operate the system.
during the requirement analysis stage, the software 7. Manage Currency Rate: Admin and accounting staff
requirement can be described as follow. The system will be manipulate the currency rate that applied on
divided and be built into 4 (four) packages which are certain period.
Master, Cashier, Accounting and Report that connected 8. Manage Chart of Account: Admin and accounting
each other’s, as illustrated in Figure-2. The functions that staff manage the chart of account, list of account
B6.4-3
that relate to company accounting systems. then pays the bill. For the guest handled by travel
agent with contract, the bill will be recorded as
account receivable of travel agent.
2. Manage Commission: User preparing the
commission for the freelance guide or travel
agency who handle the guest. The commission
can be paid after the guest pay the bill.
3. Generate Daily Report: User generate the daily
report, which are daily sales report and daily
commission report.
4. Generate Commission Report: User generate daily
commission report, the amount of paid and
unpaid commission.
5. Generate Sales Report: User generates daily sales
report. Cashier generates report for personal daily
sales. Admin generate report for all daily
recorded sales.
B6.4-4
for agent.
7. Manage Employee Account Receivable: User
creates a list of transactions relate to the account
receivable for employee.
8. Generate Lost and Profit: User create lost and profit
report on certain month. The report has special
format for the company.
B6.4-5
diagram named interaction diagram. It shows the flow of
messages between software objects, and thus the invocation
of methods (Minhas, et al., 2015). The sequence diagram,
one type of interaction diagram, in Figure-8 and Figure-9
illustrates two essentials modules of the system, which are
recording reservation and paying commission by cashier.
B6.4-6
the cancellation can only be done by the
accounting staff or supervisor. The bill that
already paid can be used as a service voucher,
and will be signed by the officer if those services
are done. The completed services that have been
done of course cannot be canceled again. As a
result, possibilities for employees to cheat can be
reduced.
2. When guests who handled by the agent pay the
services directly and then the payment are taken
again by the agent, the system will automatically
record it as receivables to the agent. In this case,
the cashier cannot pay commission on these
reservation because it status been set
automatically as unpaid.
3. Besides handle diverse prices for certain products
and can be changed as agreed with the guest, the
system can also handle payments with multiple
Figure-10. Design Class Diagram of the System currencies and credit cards. Based on an agreed
contract, the company has a diverse product
prices for different agent. The system will record
every contract price, and will automatically apply
when cashier record a reservation for guest who
is handled by the agent. Prices are generally set in
IDR and USD, but payment can be made with a
variety of currencies, adjusted to the exchange
rate value. The system records the list of
permitted currency and the value of the exchange
rate to IDR.
4. The system only allows the cashier to pay a
commission on reservations that have been paid
and from guest who handled by agents or
freelance guide. Granting commissions to agents
tailored to the contract, whereas for freelance
guide, the commission is the difference between
the selling price and the cost of the company.
5. Guests who handled by the agent does not have to
Figure-10. Design Class Diagram of the System pay the product bought. The system will record
(Continue) the bill as receivables to an agent. The agent
would pay a month later, according to the
CONCLUSION contract.
By implementing the system, the problem This system is an integrated system that combines
described in the section of Introduce the Problem can be sales process until the publication of the financial
solved: statements. This system is operated by the three user groups
1. The cashier no longer is able to arbitrarily cancel by levels 1, 2 and 3 which show the scope of the operation
the reservation. Reservations that have been paid, of the system that can be done by the user. Level 3 is the
it can no longer be canceled. Even if there is, then cashier, level 2 is the accounting staff and level 1 is the
B6.4-7
supervisor or the owner. Cashier handles the sales process, Karma, I. G. M., 2014. The Integrated Reservation
from recording transactions, creation of bill, receive Information Systems of Travel Agency Company.
payments and pay commissions. At the end of working Denpasar, Politeknik Negeri Bali.
hours, the cashier then hands over the money and report Kutanıs, R. Ö. & Mesci, M., 2013. Information
sales to the accounting staff. The accounting staff and the Management and Business Performance in the Hotel
owners can monitor financial transactions through this Industry: Effects of Innovations. Journal of Travel and
system at any time. Tourism Research, pp. 18-38.
Larman, C., 2005. Applying UML and Patterns: An
ACKNOWLEDGMENTS Introduction to Object-Oriented Analysis and Design
On this occasion, I would like to say thanks to and Iterative Development. 3rd ed. USA: Prantice Hall.
Director of Bali State Polytechnic and Head of Accounting Minhas, N. M., Qazi, A. M., Shahzadi, S. & Ghafoor, S.,
Department of Bali State Polytechnic who have sponsored 2015. An Integration of UML Sequence Diagram with
me to do this research. Also thanks to Mr. Suamir, Mrs. Formal Speciication Methods - A Formal Solution
Aryaningsih, my families and colleagues that been Based on Z. Journal of Software Engineering and
supporting on finishing this paper. Applications, Volume 8, pp. 372-383.
Peslak, A. R., 2011. A Study of Information Technology
REFERENCES Integration. Journal of Information Systems Applied
Apergis, N., Artikis, G., Eleftheriou, S. & Sorros, J., 2011. Research (JISAR), 4(2), pp. 19-27.
Accounting Information and Cost of Capital: A Pressman, R. S., 2001. Software Engineering: A
Theoretical Approach. Modern Economy, Volu me 2, pp. Practitioner's Approach. 5th ed. USA: McGraw Hill.
589-596. PwC Indonesia, 2014. PSAK Pocket Guide 2014, Jakarta:
Bagranoff, N. A., Simkin, M. G. & Norman, C. S., 2010. PT Prima Wahana Caraka.
Core Concepts of Accounting Information Systems. Siau, K. & Cao, Q., 2001. Unified Modeling Language
USA: John Wiley & Sons, Inc.. (UML) - A Complexity Analysis. Journal of Database
Bhasin, M. L., 2013. Corporate Accounting Fraud: A Case Management, 12(1), pp. 26-34.
Study of Satyam Computers Limited. Open Journal of Wolf, A. & Hessel, C., 2012. Pricing Options on Foreign
Accounting, Volume 2, pp. 26-38. Currency with a Preset Exchange Rate. Journal of
Catenazzo, G. & Fragnière, E., 2010. Pricing Traditional Mathematical Finance, Volume 2, pp. 214-224.
Travel Agency Services: A Theatre-Based
Experimental Study. Service Science & Management,
Volume 3, pp. 272-280.
Coad, P. & Yourdan, E., 1991. Object-Oriented Analysis.
2nd ed. USA: Prentice-Hall, Inc..
Coad, P. & Yourdon, E., 1991. Object-Oriented Design.
USA: Printec-Hall, Inc..
Douglas, B. P., 2001. UML for Executable Specification.
EDN, 16 August, pp. 83-90.
Grande, E. U., Estébanez, R. P. & Colomina, C. M., 2011.
The Impact of Accounting Information Systems (AIS)
on Performance Measures: Empirical Evidence in
Spanish SMEs. The International Journal of Digital
Accounting Research, Volume 11, pp. 25-43.
Herrera, M. R. G. & Aranda, M. F., 2013. Rapid
Assessment of Tourism Impacts through Community
Participation - A Pilot Study in Cuba for Projecting
New Strategies of Management. Current Urban Studies,
1(3), pp. 36-47.
B6.4-8