Professional Documents
Culture Documents
ebook download (eBook PDF) Accounting Information Systems Understanding Business Processes 5th all chapter
ebook download (eBook PDF) Accounting Information Systems Understanding Business Processes 5th all chapter
http://ebooksecure.com/product/ebook-pdf-accounting-information-
systems-understanding-business-processes-4th/
http://ebooksecure.com/product/ebook-pdf-accounting-information-
systems-controls-processes-3rd-edition/
http://ebooksecure.com/product/ebook-pdf-accounting-information-
systems-the-processes-controls-2nd/
http://ebooksecure.com/product/ebook-pdf-essentials-of-business-
processes-and-information-systems/
(eBook PDF) Accounting Information Systems: Controls
and Processes 4th Edition
http://ebooksecure.com/product/ebook-pdf-accounting-information-
systems-controls-and-processes-4th-edition/
http://ebooksecure.com/product/ebook-pdf-business-driven-
information-systems-5th-by-paige-baltzan/
http://ebooksecure.com/product/ebook-pdf-accounting-information-
systems-14th-edition/
http://ebooksecure.com/product/original-pdf-accounting-
information-systems-10th-australia/
http://ebooksecure.com/product/ebook-pdf-accounting-information-
systems-10th-edition/
PA R K E S | C O N S I D I N E | O L E S E N | B LO U N T
AC C O U N T I N G
INFORMATION
SYSTEMS
FIF T H ED I T I O N
5.3 Alternative systems development Reduced accounting time 251
approaches 218 Recognition by major accounting
Prototyping 219 software vendors 251
Agile/adaptive methods 220 Interchangeable data 252
5.4 Software selection for SMEs 221 Comparisons across companies 252
Pre-developed programs 221 Improved audit quality 252
Types of accounting packages 221 Stakeholder benefits 252
Software as a service 222 6.7 XBRL concepts 253
5.5 Typical problems of systems development 222 XML and XBRL compared to HTML 253
Conflict 222 XBRL specifications 255
Escalation of commitment 222 XBRL taxonomies 256
Project goal issues 223 Instance documents 258
Technical skills 223 Tagging accounts using XBRL 259
Interpersonal skills 223 6.8 Cloud computing 263
5.6 Systems development management tools 224 Cloud Infrastructure as a Service (IaaS) 263
Gantt charts 224 Cloud Platform as a Service (PaaS) 263
CASE 225 Software as a Service (SaaS) 263
Summary 225 6.9 Big data 265
Key terms 226 Other technologies 265
Discussion questions 227 AIS FOCUS 6.1
Self-test activities 228 Phablets for accountants? 266
Problems 229 Summary 267
AIS FOCUS 5.3 Key terms 268
An integrated medical record system 232 Discussion questions 269
Further reading 235 Self-test activities 270
Self-test answers 235 Problems 270
Endnotes 235 Further reading 273
Acknowledgements 237 Self-test answers 273
Endnotes 274
CHAPTER 6 Acknowledgements 274
Technology concepts 238 CHAPTER 7
Introduction 239
6.1 Why an ERP system? 240 Systems mapping and
6.2 Business processes supported by documentation 275
ERP systems 240 Introduction 276
6.3 ERP systems — SAP modules 242 7.1 The purpose of systems documentation 277
Financial accounting (FI) 242 7.2 Role of systems documentation in process
Controlling and profitability analysis (CO) 243 redesign and re-engineering 278
Human resources (HR) 243 7.3 Role of accountant in accurate reporting and
Sales and distribution (SD) 243 preserving corporate memory 278
Materials management (MM) 244 Auditing and systems documentation 279
6.4 XBRL and its role in reporting systems 7.4 The law and systems documentation 280
and decision making 245 7.5 Reading systems documentation 281
6.5 Different ways to apply XBRL tags 247 AIS FOCUS 7.1
XBRL tags in the accounting system 247 The role of software in systems
Tagging accounts after reports have been documentation 282
produced 248 Entities 282
6.6 Benefits of XBRL 249 The narrative 283
Reduced data manipulation 249 Process maps 286
Paperless reporting 251 Data flow diagrams 287
Industry-accepted standards 251 Systems flowcharts 293
vi CONTENTS
7.6 Balancing a data flow diagram 299 Summary 364
7.7 Drawing systems documentation 299 Key terms 365
Analysing the case 301 Discussion questions 366
Preparing a process map 303 Self-test activities 366
Preparing data flow diagrams 307 Problems 367
Further reading 368
7.8 Comparing the different documentation
Self-test answers 368
techniques 317
Endnotes 368
Summary 318
Acknowledgements 372
Key terms 319
Discussion questions 320 CHAPTER 9
Self-test activities 320
Problems 323 Internal controls II 373
Self-test answers 328 Introduction 374
Endnotes 328 9.1 Control activities, business processes and
Acknowledgements 329 accounting 375
9.2 Evaluation of control activities 376
CHAPTER 8
Preventive, detective and corrective controls 377
Internal controls I 330 AIS FOCUS 9.1
Introduction 331 Insider trading: the worst case in
8.1 Evolution of corporate governance 332 Australia? 379
What is corporate governance? 332 Input, processing and output controls 380
Brief history of corporate governance 333 9.3 COSO, COBIT and control activities 380
8.2 Principles of corporate governance in 9.4 Aims of a computerised accounting
Australia 335 information system 382
AIS FOCUS 8.1 Proper authorisation 382
Availability of information to shareholders 336 Proper recording 383
8.3 IT governance 339 Completeness 383
What is IT governance? 339 Timeliness 383
8.4 COBIT framework and principles 340 9.5 General controls 384
Australian IT governance 346 Physical controls 384
AIS FOCUS 8.2 Segregation of duties 385
Governance and accounting failure in Australia 346 User access 385
8.5 Significance of internal control 347 System development procedures 387
What is internal control? 347 User awareness of risks 387
8.6 Components of COSO internal control Data storage procedures 387
framework 349 AIS FOCUS 9.2
Control environment 349 Privilege vulnerabilities 388
Risk assessment 350 Security policies 389
AIS FOCUS 8.3 9.6 Application controls 389
Fuel prices and financials 350 Input controls 389
AIS FOCUS 8.4 AIS FOCUS 9.3
Disaster recovery options 351 Human error: the biggest problem 393
Control activities 353 Processing controls 395
Information and communication 353 Output controls 397
Monitoring 354 AIS FOCUS 9.4
8.7 Identifying and assessing risks 357 Controls in practice 398
Linking risks to financial statement assertions 358 9.7 Disaster recovery plans 399
8.8 Evaluating COSO and COBIT frameworks 361 Temporary sites 399
AIS FOCUS 8.5 Staffing 400
Corporate governance, financial reporting . . . what Restore business relationships 400
else? 363 9.8 Execution of internal control 400
CONTENTS vii
9.9 Documenting controls 401 Summary 467
Narrative descriptions 401 Key terms 468
Questionnaires and checklists 402 Discussion questions 469
Flowcharts 403 Self-test activities 470
Control matrix 404 Problems 471
Further reading 479
9.10 The limitations of controls 404
Self-test answers 479
Threats to an organisation’s objectives 404
Endnote 479
Threats to internal controls 406
Acknowledgements 480
Summary 407
Key terms 408 CHAPTER 11
Discussion questions 409
Self-test activities 410 Transaction cycle — the
Problems 410
Self-test answers 420
expenditure cycle 481
Endnotes 420 Introduction 482
Acknowledgements 422 11.1 Expenditure cycle overview and
key objectives 483
PART 3 Strategic implications of the expenditure
Systems in action 423 cycle 484
11.2 Technologies underpinning the
CHAPTER 10 expenditure cycle 485
AIS FOCUS 11.1
Transaction cycle — the Getting behind the scenes — managing
revenue cycle 426 your supply chain 486
Introduction 427 11.3 Data and decisions in the expenditure
10.1 Revenue cycle overview and key cycle 486
objectives 427 Data and the expenditure cycle 486
Strategic implications of the revenue cycle 429 Expenditure cycle business decisions 487
AIS FOCUS 10.1 AIS FOCUS 11.2
Simply Energy 430 Accounts payable processing at Telstra 488
10.2 Technologies underpinning the revenue 11.4 Expenditure cycle documentation 488
cycle 430 Expenditure cycle context 489
AIS FOCUS 10.2 Expenditure cycle logical data flows 490
Caffe Primo Chain 431 11.5 Expenditure cycle activities and related risks
10.3 Data and decisions in the revenue cycle 432 and controls 495
Data and the revenue cycle 432 Determine demand for goods — activities,
Revenue cycle business decisions 432 risks and controls 495
10.4 Revenue cycle documentation 433 Order goods — activities, risks and controls 499
Revenue cycle context 433 Receive goods — activities, risks and
Revenue cycle logical data flows 434 controls 505
10.5 Revenue cycle activities and related Pay for goods — activities, risks and controls 512
risks and controls 439 Physical DFD — determine demand for
Process the sales order — activities, risks and goods 520
controls 440 System flowchart — determine demand for
Pick, pack and ship the goods — activities, goods 521
risks and controls 448 11.6 Measuring expenditure cycle
Bill the customer — activities, risks and controls 450 performance 524
Receive and record payment — activities, Summary 524
risks and controls 459 Key terms 526
Physical DFD — process the sales order 463 Discussion questions 527
Systems flowchart — process the sales order 465 Self-test activities 527
10.6 Measuring revenue cycle performance 466 Problems 529
viii CONTENTS
Further reading 537 Self-test activities 583
Self-test answers 537 Problems 585
Endnote 537 Further reading 593
Acknowledgements 537 Self-test answers 593
Acknowledgements 594
CHAPTER 12
PART 4
Transaction cycle — the general
ledger and financial reporting Systems issues 595
cycle 538 CHAPTER 13
Introduction 539
12.1 General ledger and financial reporting cycle
Auditing and governance
overview and key objectives 539 of accounting information
Strategic implications of the general ledger and systems 596
financial reporting cycle 542
Introduction 597
12.2 Technologies underpinning the general ledger
13.1 Importance of the audit function 598
and financial reporting cycle 542
13.2 Internal auditing 598
AIS FOCUS 12.1
13.3 External auditing 599
Storm clouds ahead: some pros and cons of
data in the cloud 544 13.4 Audit committees 600
12.3 Data and decisions in the general ledger and 13.5 Influences on the auditor 601
financial reporting cycle 545 Benchmarks and best practice 602
Data and the general ledger and financial 13.6 Financial (statutory) audit 602
reporting cycle 545 Requirement for a financial audit 602
AIS FOCUS 12.2 Sarbanes–Oxley Act (SOX)
Online recruiter uses Xero for accounting requirements 603
online 547 13.7 Information systems audit 604
General ledger and financial reporting cycle Overview of the AIS audit 605
business decisions 547 AIS FOCUS 13.1
12.4 General ledger and financial reporting Cloud computing: assessing the risks 606
cycle documentation 549 Audit tools 608
General ledger and financial reporting AIS FOCUS 13.2
cycle context 549 COBIT and IT governance
General ledger and financial reporting cycle case studies 608
logical data flows 554 Planning the audit 613
12.5 General ledger and financial reporting cycle Fieldwork (performing the audit) 617
activities and related risks and controls 556 Analysis 618
Prepare budgets — activities, risks and AIS FOCUS 13.3
controls 556 Protecting customer data 620
Update the general ledger — activities, risks and Completion, review, monitoring and
controls 557 reporting 622
Record general ledger adjustments — activities, Audit of systems under development 623
risks and controls 565 Special purpose audits 623
Produce reports — activities, risks and Summary 624
controls 569 Key terms 624
Physical DFD — prepare budgets 575 Discussion questions 625
Systems flowchart — prepare budgets 576 Self-test activities 626
12.6 Measuring general ledger and financial Problems 627
reporting cycle performance 580 Further reading 630
Summary 580 Self-test answers 631
Key terms 582 Endnotes 631
Discussion questions 582 Acknowledgements 632
CONTENTS ix
CHAPTER 14 14.4 Cybercrime 649
Malware: viruses, worms, Trojans, bots 650
Ethics and cybercrime 633 Spam 650
Introduction 634 Identity crime 651
14.1 The importance of ethics 634 AIS FOCUS 14.3
Consequentialist theories 635 News of the World 652
Non-consequentialist theories 636 14.5 Fraud, online fraud and scams 652
Importance of ethics in AIS and Sales fraud or e-commerce fraud 654
accounting 637 14.6 Reducing the risk of cybercrime 655
Ethical issues in business 637 14.7 Future trends and issues with
14.2 Ethical decision making 638 new technologies 656
Applying the framework 639 Summary 657
14.3 Ethical issues in accounting information Key terms 658
systems 640 Discussion questions 659
Self-test activities 660
Customer protection and privacy 640
Problems 661
AIS FOCUS 14.1 Further reading 662
Data breaches 641 Self-test answers 663
AIS FOCUS 14.2 Endnotes 663
RFID: Asset tracking capabilities and more 643 Acknowledgements 666
x CONTENTS
PREFACE
The fifth edition of Accounting Information Systems offers a uniquely Australian and New Zealand
perspective of the business processes central to many organisations, and contains additional material
and improved chapter content from the third edition. In order to maximise the benefit of its Australian
and New Zealand context, this text uses, wherever possible, contemporary Australian and New Zealand
examples and issues as a basis for explaining and exploring the many issues associated with accounting
information systems (AIS).
For students
This text offers you an Australian and New Zealand perspective of the AIS discipline. Written by a team
of authors from Australia and New Zealand for a tertiary audience, this text guides you through your
studies in the AIS area. An understanding of accounting information systems is vital for all accounting
areas because throughout your working life you will be using and relying on the technologies and
systems described in this book, and also managing the processes discussed and explored. In recent years,
the need to be abreast of the areas covered in the text has been highlighted by corporate failures and
the financial crisis — each of which saw attention placed on the way organisations operate and the con-
trol structures that they employ. Another area of recent change relates to accounting technologies and
accounting data. In response to recent technological developments, additional materials have been intro-
duced to cover enterprise resource planning (ERP) systems, eXtensible Business Reporting Language
(XBRL), cloud computing, and the ‘big data’ or data analytics phenomenon. This text will help you
successfully complete your studies in the accounting information systems area; you will gain essential
skills and analytical approaches of benefit to you both now and well into the future.
For lecturers
The structure of the text allows teaching in several different ways, depending on the pedagogy of the
instructor and the focus of the course design. The partitioning of the text into four sections provides
flexibility of material delivery that makes sense in most sequence structures. Educationally, the text pro-
vides a range of assessment and learning material and additional end-of-chapter questions and problems.
Each chapter employs a range of small case vignettes to illustrate, using Australian and New Zealand
examples, the main ideas being conveyed in the chapter. Learning objectives relate to the major issues
and themes of the chapter, and are outlined at the commencement of the chapter and then emphasised
in the appropriate spot as each chapter proceeds. The end-of-chapter review materials and problems link
back to the learning objectives. This linkage allows for the setting of targeted questions based on the
emphasis adopted when delivering the material to students. From a student’s perspective, this structure
has definite benefits as well, providing a clear link between the requirements of the question material
and the theoretical concepts discussed throughout the chapter.
Central to the discussion throughout the book is the notion of the business process. As business
processes become increasingly important to the organisation, impacting on organisational design and
operation, the perspective adopted by the text makes it contemporary and relevant. The fifth edition
presents business processes with chapters on the revenue process (chapter 10), expenditure process
(chapter 11) and general ledger and financial reporting (chapter 12). Additional chapters from previous
editions covering the manufacturing process and the human resources management and payroll process
are available through Wiley Custom Select. The scope of these processes offers a complete and com-
prehensive coverage of the typical business processes within the organisation. In addition, the range of
processes included means that the instructor has flexibility in what processes are covered and the extent
of emphasis within the individual AIS course design.
PREFACE xi
Linked closely to the business process and systems materials is an overview of current technology
trends including XBRL, which introduces a new perspective on financial reporting and accounting infor-
mation systems design. The text also covers the emerging technologies of cloud computing and data
analytics, focusing particularly on how these technologies impact the accounting role. The coverage of
ERP systems has been greatly expanded in this fifth edition.
Overall, much content has been enhanced in the fifth edition, including a new technology concepts
chapter covering ERP, systems applications and products (SAP), cloud computing and big data. Chapters
on internal controls, systems development, and ethics and cybercrime have been extensively revised.
Process maps have been added throughout chapters 10, 11 and 12 to more clearly depict the processes
and create new options for classroom teaching and learning.
Links to the various areas of the typical undergraduate degree are borne out in many topics in the
text — for example, the chapters on systems documentation and systems development. The intent of this
is to reinforce that Accounting Information Systems is not a standalone unit — it has direct relevance to
the various areas of the professional accountant’s roles and responsibilities. This perspective means that
a comprehensive coverage of AIS issues is now offered by the text, as well as greater flexibility in the
selection and sequencing of topics over the course of the semester.
The text offers discussion questions, self-test activities in the form of multiple choice questions, and
problems at the end of each chapter. Much of this material has also been revised and updated for the fifth
edition, including an expanded set of end-of-chapter problems. Many of the AIS Focus vignettes have
been updated.
The authors are grateful for the contributions of colleagues who invested time and effort to prepare the
teaching and learning resources that accompany the text.
Each of the authors would welcome any comments or suggestions about the content of the text and
any suggested changes or improvements for later editions of the text.
Alison Parkes
Brett Considine
Karin Olesen
Yvette Blount
March 2016
xii PREFACE
PART 1
Systems
fundamentals
In part 1 of this text we introduce the fundamental ideas and principles underlying business
information systems. Business information systems are an integral part of any organisation,
providing a means of capturing, organising and sharing data. Accounting information systems are
a specialised form of business information system; they record transactional accounting data,
convert data into information, and provide information to external and internal decision makers.
In this section we also explore these ideas in detail by describing fundamental systems concepts,
explaining the historical development of accounting information systems and discussing a range of
systems-related issues.
Familiarisation with systems fundamentals provides the foundation for subsequent chapters,
which cover the business processes that exist in an organisation, along with the design and
documentation of these systems and processes. Part 1 concludes with an overview and
roadmap of the text and provides brief descriptions of each of the remaining chapters.
1 Introduction 2
CHAPTER 1
Introduction
LEA RN IN G OBJE CTIVE S
CHAPTER 1 Introduction 3
These simple everyday transactional systems not only directly affect the customer experience, but can
also create a valuable competitive advantage for the systems owner through the unique information they
generate. The value of an accounting information system is directly linked to the quality of information
generated by that system. A well-designed and controlled accounting information system records high-
quality data, provides valuable, insightful information, promotes sound decision making and ensures
ongoing high-level performance for the organisation.
Chapter 1 introduces you to the concept of an accounting information system and discusses some
general principles relevant to the study of accounting information systems, forming a foundation for
subsequent chapters.
Accounting
As a business student, no doubt you will have some concept of what accounting is and what it involves.
The traditional role of accounting and accountants was to record details of transactions occurring within
an organisation, summarise and adjust that data as necessary, and then to prepare and distribute financial
statements and reports. The traditional accounting cycle typically included the following steps:
1. transaction occurs
2. analyse transaction
3. journalise transaction
4. post journal to ledger
5. prepare trial balance
6. adjust entries
7. adjust trial balance
8. close entries
9. prepare financial statements.
The aim of the accounting cycle was to provide meaningful information for use by decision makers,
both internal and external to the organisation. The accounting process, and the accountants who used that
process, was functionally a data storage and classification system, with transactions tagged and classi-
fied based on the accounts they affected to determine which account to debit and credit when entering a
transaction into the subsidiary and/or general journals. A set or ‘chart’ of accounts was tailored for the
organisation and the total amounts posted to each of these accounts were reported in the form of a ‘trial
balance’ of the general ledger. The modern rules around debits, credits and double-entry accounting
are based on ideas from the Italian mathematician, Luca Pacioli,2 who devised a method of recording
business transactions for the merchants of Venice during the Italian Renaissance. Those early merchants
faced the same issues their modern-day counterparts grapple with. How much have I sold? What is my
profit? To whom do I owe money and when should I pay it?
The primary difference today is that these steps of the cycle are routinely handled by computers rather
than by quill and ink notations made in vellum account books. So the boring and often frustrating task
Enterprise systems are just one example of how traditional accounting roles have been revolution-
ised and broadened in scope to encompass tasks beyond the traditional accounting functions. Enterprise
systems also emphasise the role that technology has played in changing the perception and functioning
of accounting information systems in the organisation.
CHAPTER 1 Introduction 5
As computer systems have been developed to perform the recording and classification tasks
associated with business activities, the nature of accounting and the work of the accountant have also
been pushed in a new direction. Increasingly, the role of the accountant is seen to be to add value in
one of two ways: by active ownership and management of the accounting information system, and by
analysing and presenting information to the decision makers in organisations. As an example, look
at the following two quotes from the two major professional accounting bodies in Australia, CPA
Australia (certified practising accountants) and the Institute of Chartered Accountants in Australia
(ICAA).
Under the heading of ‘Why accounting?’, CPA Australia provides the following argument.4
Accounting studies give you the tools to understand how and why key business decisions are made, and
how to have input into those decisions. Having a qualification in accounting will open doors to career
opportunities within: finance and accounting, information technology, marketing, human resource man-
agement, e-commerce, international business, economics, running your own business, management,
strategy and business development.
bring[s] their analytic expertise to fields as diverse as strategic planning, market analysis, compliance,
change management and the use of information technology.
Some of the potential career paths associated with accounting are described in figure 1.2.
Forensic accountant
The detectives of the finance world. They track and analyse data to find missing funds, trace
illegal business activities and identify fraud. It’s a challenging and exciting field that could take you
anywhere.
Environmental accountant
Takes a ‘green’ approach to making money and finds ways to ensure a company is environmentally
responsible and profitable. They enjoy great professional rewards while helping the planet.
As shown in figure 1.2, the accountant’s role has extended beyond the task of capturing and recording
financial information about an organisation to being someone who provides information and solves prob-
lems for an organisation. The days of the accountant only being the one who maintains the books are
long gone. The career paths mentioned in figure 1.2, however, still rely on a knowledge of accounting.
Accounting is still an important skill to possess — it is just that what is done with those accounting
skills has changed.
Accountants are increasingly exposed to and working with technology and information systems; this
is the major theme of this text. Accountants of the twenty-first century must be comfortable with infor-
mation systems concepts as these systems play an important role in the management and functioning of
the organisation. This shift in definition of accounting and accountants towards a technology- based role
leads to the second component of the subject area: information.
CHAPTER 1 Introduction 7
all you had were the raw data in figure 1.3. It would be very time-consuming, difficult and potentially
inaccurate. So a way is needed to make the data useful.
Data become useful when they are subject to the application of rules or knowledge, which enables
us to convert data into information. Information is a guiding tool for decision making and can prompt
action. The sales data contained in the sales journal in figure 1.3 can be made useful by summarising
them in some meaningful way to support further analysis by decision makers. Examples of this could
include weekly sales summaries, sales by customer reports, profit margins per customer and so on.
Debit Credit
Date Customer Invoice # Accts Rec. COGS GST Payable Sales Inventory
To improve usability, the raw data records could also be summarised on the basis of sales by cus-
tomer, sales by geographic region (assuming geographic region data are available), sales by product type
and so on. When this is done, the data become more meaningful and easier to work with. Summarising
the data and turning it into information creates a useful tool to assist decision making. The concept of
data records and their creation and storage is explored in more detail in later chapters examining data-
bases and enterprise information systems.
One key issue with information is the potential to provide too much. This is described as information
overload, which happens when an individual has more information than they need, and as a result
experiences difficulty working through to a decision, which is obviously undesirable. Organisations need
to be conscious of what information they produce (whether reports or some other type of information)
and make sure that it is relevant to the needs of the people who will use it. Commonly in large organ-
isations, people will request reports for a specific problem. Over time, that problem may disappear, yet
the reports are still produced. In many cases, these reports will then just be filed away because ‘that’s
what has always been done’. So resources are wasted in generating the reports and the potential for
information overload and suboptimal decision making is created.
CHAPTER 1 Introduction 9
occurs, a new sales record is input. Transactions are often recorded initially on source documents that an
organisation generates and receives in its normal business operations. Examples of various source docu-
ments are described in detail in later chapters of this text. These source documents are used to provide
documentary evidence for transactions input into the accounting information system. Transactions can
be input into an accounting system in a number of different ways, including the following.
Most common
•• Manual keying. As the name suggests, manual keying requires a person to enter data into a system via a
keyboard. This could introduce errors in the data if items such as names and amounts were incorrectly
keyed. As any errors are the result of human error, mistakes in the data tend to be random and inconsistent.
•• Scanning through barcode technology. This involves scanning a barcode with a laser device. The
barcode number is then searched for on a database and appropriate details returned to the system.
Examples of this include scanners at a supermarket, where universal product codes are used. As errors
are the result of technology error, mistakes in the data tend to be systematic and consistent.
Less common
•• Scanning through image scanners. Image scanners are a useful input approach where the input is in
the form of a diagram or graphic image. Scanners are used to capture the image, which is then stored
electronically.
•• Magnetic ink character recognition (MICR). This technology is used on bank cheques. A special ink and
character set is used, with computers able to read the ink due to its magnetic properties. MICR offers a
security control for banks and provides a quick method for scanning information into a system.
•• Voice recognition. Using voice recognition technology allows a computer to convert spoken words and
commands into data inputs. Issues with voice recognition technology can include training the system
to recognise words and deal with accents and different voice intonations.
•• Optical mark readers. You have most probably used this technology when completing multiple-choice
exams at university. Data inputs are coded onto a sheet by colouring in the appropriate space, and the
sheet is then fed through a machine that identifies where the dots are and, based on their location,
converts them into data that can be stored electronically. All marks made on the sheet need to be
precise and unambiguous, otherwise high error rates can be experienced.
Processing refers to activities that are performed on the inputs into the system. Again using the sales
system as an example, once sales data are entered into the system, various processing is undertaken,
including checking format and validity, manipulating inputs, and finally storage. Examples of format and
validity checks are discussed in the chapters on the different transaction cycles, as well as the internal
controls chapter, but the basic aim of data processing is ensuring that data are correct and in a valid
format. Manipulations refer to the act of performing calculations and adjusting the data inputs. As an
example, if a sales order is entered and the unit prices and the quantity of units sold are keyed in, the
system can then manipulate these two figures to generate the total price (sales price × units sold). Other
checks and manipulations performed on the data can be hash checks, to ensure that inputs like credit
card numbers and customer numbers are valid. These are discussed in more detail in later chapters.
Outputs refer to what is obtained from a system, or the result of what the system does. In the sales
system, outputs will typically include reports for decision making. Some examples of outputs from the
sales system could be receipts and invoices that are given to customers when a sale is executed, or sales
summary reports used by management to assess performance. When designing a system, it is important
to consider what outputs will eventually be required to ensure sufficient data input to the system to meet
the end-user needs. If, for example, customer details are not gathered when sales data are input into the
sales system, then it will be impossible to generate a sales report that breaks sales down by customer.
Interacting with the inputs, processes and outputs is the control system, which is the set of checks
and balances that ensures that the system is running as expected and that there are no data errors or
exceptional circumstances. For example, if data for a new customer, including a customer number, is
entered into a system, the system could take the customer number data entered and check that it is in
the required format and is a valid number. If the system finds an error in the customer number (e.g. it
CHAPTER 1 Introduction 11
Another random document with
no related content on Scribd:
of which set closely enough together to keep fragments of shells
from going through should one hit and explode on deck.
On our battleships the main battery is generally made up of four
10 inch, 12 inch or 13 inch breech loading guns and these are
mounted in revolving turrets one of which is forward and one aft. The
Alabama had four 13 inch guns in the large turrets and twelve 6 inch
guns on the broadsides. I’m telling you that if Huerta had been at
Vera Cruz when we got there and taken a look into the muzzle of
one of our 13 inch guns he’d have saluted the flag without any more
of that mañana business. As it was he was safely out of range of our
guns for Mexico City is over 200 miles from Vera Cruz.
In the early days of wireless when every Tom, Dick and Harry was
getting up a “new” wireless system the Navy Department tried out all
of them. It would not use the Marconi system because the
government wanted to buy the apparatus outright while the policy of
the Marconi Company was to lease their apparatus.
The favorite type of wireless apparatus used by the Navy
Department was known as the Telefunken, a German getup that was
a combination of the Slaby-Arco and the Braun-Siemens and Halske
systems. The transmitter of our station was one of this kind and
consisted of an induction coil with a mercury turbine interruptor, an
electric motor to run it and the usual key, loose coupled tuning coil
and condensers.
The receiver was of a later type and had both a crystal detector
and a vacuum tube detector, the latter being the invention of Dr.
Fleming of England who has been Marconi’s technical adviser for
many years. This detector is really a small incandescent lamp bulb
with not only a filament but a metal plate sealed in it. The filament is
kept at a white heat by a current from a storage battery.
When the telephone receivers are connected to the hot filament
and the cold plate electrodes, the high frequency currents that are
set up in the aerial by the incoming electric waves are changed into
direct currents and the varying strength of these act on the head-
phones. This detector is very sensitive and needs no adjusting.
Many of the messages we sent and received were in straight
English but nearly all the important ones, especially those for and
from Washington, were in code, the purpose of which was to prevent
any one else, except our officers, from reading them and this kind of
message is not very interesting but we know that something is going
on anyway.
We anchored off Vera Cruz on the 21st and the natives must have
thought from the number of warships that hemmed them in that we
were going to blow them to smithereens. A few hours after our arrival
we landed a thousand marines and they drove back Huerta’s
soldiers and captured the customs house.
The chief reason this was done was because our government had
got wise to the fact that a couple of German ships were scheduled to
arrive at Vera Cruz with a cargo of guns and ammunition for Huerta,
and our Commander had received orders on the way down to
prevent this by seizing the customs house.
There was not much show of armed resistance on the part of
Huerta’s men but in the scuffle that took place four of our men were
killed and about twenty were wounded. I made up my mind right then
and there that if I ever got a chance I’d blow the sombrero off of
some greaser out of pure revenge.
The favorite method of warfare that is waged by the Mexicans is
sniping, that is, they hide behind something and take a shot now and
then at you. As a result of sniping a few days later the number of our
men that had been killed was brought up to eighteen and the number
of wounded to 71.
When things had quieted down Hart Douglas, another operator
and I got a six hour shore leave. We buckled on our holsters and
slipped our revolvers into them with small thought of having a
chance to use them. We took a look around the town and all went
well for awhile when zip, zip, a couple of bullets whizzed by my ear
and Hart dropped with a bullet in his lung.
I whipped out my gun and wheeled around just in time to spot a
couple of snipers lying on a near-by roof with their rifles pointing
toward us. I emptied the five chambers at them as fast as I could pull
the trigger. I got one of them; he raised himself to his feet and
pitched headlong into the street. But the other one got me for he
drew a bead on my gun arm which, also don’t forget, is my key arm.
A couple of marines put poor Hart on a stretcher and carried him
over to a field hospital. Another bound up my arm, walked with me
over to the launch and when I got aboard my ship the doctor dressed
it.
“I WHIPPED OUT MY GUN JUST IN TIME TO SPOT A COUPLE OF
SNIPERS”
No more shore leaves were granted the men because two
perfectly good operators had gone ashore and two miserable good-
for-nothing operators had returned. Hart hovered between life and
death for weeks but he finally pulled through though he never will be
as good a man as he was. I came along all right but my hand
seemed paralyzed from the wrist down and it was many a moon
before I could use a key again with my right hand. I guess you see
now why I like those greasers so well.
Our marines remained on duty until the end of the month when
General Funston arrived from Galveston with about four thousand
troops and took possession of the port. It was hard to see what turn
affairs would take next for Huerta had an army of 5,000 men not very
far from Vera Cruz. But I guess he had heard of General Funston
before and he didn’t care about being captured as Aguinaldo, the
Philippine leader, was.
Instead of having some small war the diplomats of the A B C
governments of South America, as Argentine, Brazil and Chile are
called, offered to try to negotiate a friendly settlement between the
United States and Mexico. President Wilson, who liked peace and
hated war, at once accepted their kind offer and agreed to send
representatives to their proposed conference. The following day
Huerta agreed to send his representatives to the A B C conference
which was to be held in the town of Niagara Falls on the Canadian
side of the river.
Finally, when all the representatives met, the first thing that was
done was to have an armistice signed by the United States and
Huerta’s government. As soon as this was done Huerta’s
representatives tried to have the United States withdraw its forces
from Vera Cruz and the United States forego the salute for the insult
to our flag. The representatives of the United States asked only that
Huerta resign.
After deliberating for five weeks the representatives of all the
countries agreed that a provisional government should be
established in Mexico, and that Huerta should resign; that the United
States should not ask Mexico to pay an indemnity nor to ask for a
salute or other apology for the insult to the flag at Tampico and that
our troops were to remain at Vera Cruz.
In the meantime Huerta was being hard pressed by Carranza on
the north and the rebel Zapata on the south and with our troops
occupying Vera Cruz it evidently suited him very well to resign. So on
the 10th of July Huerta appointed Chief Justice Corbajol to be
president in his place.
It was common talk among the blue-jackets on our ship that
Huerta had some 3,000,000 dollars deposited in banks somewhere
in Europe and that he planned to go there. Be that as it may he
handed in his resignation to the Chamber of Deputies a week later
and left for Puerto, Mexico, on a special train under heavy guard.
From there he sailed for Jamaica and thence for Europe.
Thus it was that Huerta, the Indian descendant of the Aztecs, who
always went one way and came back another, got out of saluting our
flag and probably saved his life.
CHAPTER IX—ON A SUBMARINE CHASER
Don’t think for a moment that Germany was the only country that had
a fleet of submarines. The reason that her U-boats came to be so
well known was because they had torpedoed the Lusitania and sunk
helpless ships right and left no matter who was on them or what they
carried.
England and France had fleets of submarines, too, but as their
warships had blockaded Germany’s ports there was nothing to
torpedo. And when we declared war on the Kaiser, Uncle Sam began
to build submarines just as he did chasers, merchant ships and
everything else. Except airplanes, did you say? There was no such
fizzle made of building submarines as for a time was made of
building airplanes in the beginning of the war. Within a short time
after we got started our Navy Department was able to turn out a
brand-new submarine every two weeks. Think of it! Once the kind
and the size of the submarine we needed had been agreed upon by
our naval experts, that is, standardized as it is called, machines and
jigs were made by which each part was stamped out of a solid sheet
of metal, and this was done, not in one or a dozen factories, but in
hundreds of factories scattered all over the country and each of
which made a single part.
These parts were shipped to docks at various ports on the Atlantic
seaboard and there artificers of all kinds were ready to assemble
them, that is, to put them together. Thus it was that in two weeks
after the ore was mined it was made into parts, assembled and the
submarine was ready for its perilous cruise.
While the building of submarines was thus speeded up there was
another factor that made for their efficiency as a destructive engine
of war which was just as important as the boats themselves and that
was the crews to man them. Aye, and there was the rub, for a crew
could not be trained for this highly specialized work in less than two
months’ time and sometimes it took three or four months.
Because the submarine job was considered an extra-hazardous
one, volunteers were called for to man the boats and as an
inducement for bluejackets to do so a good bonus, that is, extra pay
was offered. Now Bill Adams knew all about submarines, as I think I
told you before, for he had worked for the Holland Submarine Boat
Company long before the world-war started.
“Let’s me and you go to it, matey,” he said, in one of his bursts of
patriotism; “it isn’t quite as soft a snap as we’ve got on this here
chaser but we gets more time ashore and then we helps our Uncle
Sammy. Besides I’ve made up me mind to buy me mother a flivver;
all the washladies in our neighborhood is ridin’ to and from work in
them baby land-tanks of Mr. Ford’s, and I guess what they can do
she can do, eh, matey?”
“Why not?” I allowed. “She’s got a better right to ride in a motor
car than a lot of those high-falutin’ women who live in glass conning
towers on Fifth Avenue and never had a son to fight for Uncle Sam.
They take everything and they give nothing.”
“Well, I wouldn’t quite say that, matey,” Bill answered thinking hard
within the limits of his ability; “I used to be a kind of anarchist myself,
I guess, as I always felt as how I’d like to throw a bomb—no, not a
bum—into some of them swell places, but I’ve got all over it. Why?
Because if it wasn’t for them big bugs, them rich Janes, there
wouldn’t be any Red Cross, see? Every last one of ’em that is over
eight and under eighty is handin’ out the coin, givin’ the glad hand
and workin’ like gobs holystonin’ the decks and scrapin’ cable for us
guys what’s in the navy and army. But I’m askin’ you, as man to man,
matey, will you volunteer with me for submarine duty?”
“I’m willing to try anything once, Bill, and I’ll take a chance with
you on this submarine deal,” I told him.
So Bill and I signed up for submarine service and after the crew to
which we belonged had had intensive training for several weeks we
were assigned to the H-24 and we went down to Newport to man
her. There the first time I saw her she was swinging from a crane
high in the air for this was the way they launch these sea babies.
She was simply lifted bodily from the dock where she was
assembled, swung over the water and gently deposited on the
surface.